Topics Discussed

Select Region on Agent Installation Page


Armor Customers now have the ability to select region in a dropdown when installing Agents such that all of their Services and Subagents data go into that Region as long as the Customer is Enabled for it.


Regions API Service Integration with Firehost Services for Trend


Armor Partner Customers (including Rackspace) will be able to register Trend agent on to different Trend nodes based on the Customer’s allowed region.


Initial release of Armor Ticketing System (ATS) application programming interfaces (APIs)


Armor now offers several new API endpoints that customers can use to build rich interactions with the Armor Ticketing System (ATS) platform. These API endpoints are documented on developer.armor.com and function the same as other Armor APIs. This includes being able to control their use via permission assignments. Functions available through the API include:

  • Retrieve a list of tickets visible to a specific user

  • Retrieve a list of all tickets for a single account

  • Retrieve an individual ticket’s details

  • Transition tickets through the available next statuses

  • Add and retrieve comments for individual tickets

For additional information on the above functions, review the Armor API Guide and our API documentation at developer.armor.com.


Self-service ability to resync Coalfire scan targets


A new feature has been added which allows users to self-remediate scan target sync issues. The new feature is made available when an IP address assignment changes fail to be reflected within the CoalfireOne dashboard. Additional details on this feature and how to use it are available within the Vulnerability Scanning for Compliance article.

Regarding billing, this should keep Coalfire subscriptions from falling into an error state, because the overall account status is separate. This should show in fewer issues appearing in the billing audit.


Improved validation of Advanced Backup Policy configurations


Within Advanced Backup, there is a maximum number of retained snapshots per calendar year, which might be exceeded depending on how frequent your Take/Keep values are defined within Policy configurations. The API and UI will now provide guidance as you approach this threshold, so you don’t inadvertently configure invalid Policies.