Change policies based on security summary tables
-
- UpdatedJan 30, 2025
- 1 minute read
- Yokohama
- DevOps
You can use the security conditions that are available in the base system or customize them based on your requirement.
The vulnerability severity conditions are present in the Fetch Risk Sonar Security and Incident data action in the DevOps Gather Change Policy Data subflow of the DevOps Default Change
Request flow.
If the severity condition is classified as HIGH or VERY HIGH from Veracode or Checkmarx, then the change request is automatically rejected.
If you are an upgrading customer and you want to customize the conditions with any additional security data or change the existing conditions, you must update the script in the Fetch Risk Sonar Security and Incident data action in the change flow. Ensure that you are referring to the Application Vulnerability Scan Summary Details (sn_vul_app_vul_scan_summary_details) table in the script when you customize. For more information, see Security scan results.