Policy Audit Release 1.1.0

July 7, 2025

View Audit Command

With this release, you can view the Audit Command for a particular type of Technology used in a Control. This provides visibility into how the actual value for a Control is derived.

Previously, this information was not accessible. By displaying Audit Commands, you now have better visibility of the Actual Value and can also understand how it is derived.

To view Audit Commands, navigate to Policies > Controls > Quick Actions > Info > Technologies Included.

Updated Authentication Vault Name for BeyondTrust PBPS 

In this release, we updated the authentication vault name for BeyondTrust PowerBroker Password Safe (PBPS) to BeyondTrust to reflect the current BeyondTrust branding. You can view the revised name in the following places:

Authentication Tab

You can create or edit an Authentication Vault (Scans > Authentication > New > Authentication Vaults > New > BeyondTrust) 

Authentication Vault List Page

Once an authentication vault is created, you can view the details of BeyondTrust in the BeyondTrust Information page by selecting Info/Edit from the Quick Actions menu.

When you create an authentication record by using authentication type as vault, you can view the BeyondTrust option in the list under Vault Type.

End of Support for the Hash Type MD5

With this release, support for the Message Digest Algorithm 5 (MD5) hash type has been discontinued for File Integrity Check and Data Integretity Check. The SHA-1 algorithm is now set as the default.

This change applies to both creating new policies and editing existing ones. 

If you import a Control XML file that displays the hash type as MD5 (considering you are using an old XML file), it is automatically converted to SHA-1 after import.

To set SHA-1 as the Hash Type for a new policy, navigate to New > Control > Unix or Windows Control Types > File Integrity Check or Data Integretity Check > Scan Parameters > Hash Type

To check the Hash Type for an existing Policy, navigate to Quick Actions > Edit > Scan Parameters > Digest > Hash Type

Policies that previously used MD5 as the selected hash type have been updated to use SHA-1.

Issues Addressed

The following reported and notable customer issues are fixed in this release:

Component/Category	Application	Description
PA / PC - Reports	Policy Audit / Policy Compliance	When the user with PC agent and SCA scanner enabled for their account attempted to generate a Policy Compliance report, they observed that details for non-SCA controls were missing. Relevant code changes have been made to fix the issue.
PA / PC - Report Template	Policy Audit / Policy Compliance	When the Scanner user attempted to create a STIG report template they received an error. Relevant code changes have been done to fix the issue.
PA / PC - Policy Editor	Policy Audit / Policy Compliance	When user attempted to view the Activity log, the width for the details column was unusually wide. This was because the variable which was being used to include the fixed value for control was not getting reset, resulting into many concatenation of fixed value resulting into large column width. Relevant code changes have been done to fix the issue.
PA / PC - Authentication Records	Policy Audit / Policy Compliance	When the user attempted to run a compliance scan, the scan failed due to incorrect values being passed for the SSL_VERIFY parameter in the authentication XML. Instead of true or false, the values were incorrectly set as 1 or 0, which were not recognized. This resulted in an error - ORA-28860: Fatal SSL error. Relevant code changes have been done to fix the issue.