Release 3.9

September 03, 2024

What's New?

New Token Support for Alerts

With this release, we have enhanced Alerting in Certificate View. For Alerting,  you can define the conditions, significant findings, or events that should trigger the rules and send you alerts. This functionality is accessible in the Responses tab. We have added support for the following tokens in the search query while creating Rule.  

• certificate:(type: ) - Use the values Intermediate | Leaf | Root to find these certificate types.
• asset:(wasUrl: ) - Use a text value ##### to specify the WAS URL to search certificates on the assets scanned by WAS.

The alert is generated based on the Rules Query, and you are notified when the query criteria are matched.

Improvement in Asset Details Page

We have enhanced the naming convention of Operating Systems (OS) for assets. Previously, the OS names were displayed in a shortened format. To achieve consistency across Qualys applications, we have now updated the functionality so that the same Operating System name, as displayed in CSAM and AssetView, i.e., the reconciled operating system name, is shown. Following the launch of a new scan, the displayed OS name for a specific asset is updated to reflect these changes. 

New Value for Instance Source Token

With this release, you can use the instance:(sources: ) token to search the certificates or assets scanned by EASM on the Certificates or Assets tab.

instance:(sources: EASM)

When this token is used in the Assets tab, the search query displays assets scanned by EASM. When used in the Certificates tab, it displays certificates on assets scanned by EASM.

Filters for Sources

For easier navigation, the left pane of the Certificates and Assets tab now has Sources filters. These filters display the count of assets based on their sources, such as  IP Scanner, Cloud Agent, WAS, and EASM .

Issues Addressed

• We fixed an issue where the user could see internal sites listed in the External Sites tab.
• We fixed an issue with the report based on tags; the report runs for a few minutes and then shows the status incomplete. This issue was created because of the '#' in the tag's name. We made relevant code changes to fix this issue.