0
13.12.3
Australia, Zurich, Yokohama, Xanadu
Standalone Application
Common functionality for Security Operations integrations. Dependency for Vulnerability Response and Security Incident Response applications.
The Security Integration Framework includes the following key features:
- Allows you to use existing features and functionality without having to re-implement them.
- This framework is a dependency for Vulnerability Response and Security Incident Response.
New:
- Administrators can now configure a Configuration Item (CI) lookup strategy at the individual integration level, overriding the global system property. A new CI Lookup Strategy field has been added to the integration form with three options: Use System Property (default, preserves existing behavior using the global sn_vul.use_product_model property), Force CI Lookup (always creates configuration items for scanned applications — required for integrations such as Tenable WAS), and Force Product Model (always creates a Product Model). All existing integrations default to Use System Property, ensuring no errors occur as a result of an upgrade.
Fixed:
- Resolved an issue where the vulnerability integration related list appeared twice in the admin section of each integration, causing duplicate tabs to display in the integration implementation configuration.
- Resolved an issue where users in Global scope could not configure or save credentials for integrations. Configuration attempts would silently fail with no indication of the problem. A scope warning is now displayed, guiding users to switch to the correct application scope before configuring the integration.
Permissions and roles
- Role required: System Admin (admin) or Vulnerability Admin (sn_vul.vulnerability_admin)