Additional settings for domain separation

For precise execution and results, the following precautions and settings are required for domain separation in Vulnerability Response, Application Vulnerability Response, Container Vulnerability Response, and Configuration Compliance.

Don’t modify the business logics and processes in the global domain to avoid any issues so that all the latest changes are updated for every upgrade. Duplicate all the business logics and processes in each domain separately and ensure that they are inactive in the global domain. Otherwise, the business logics and processes in the global domain take precedence over the child domain. Suppose, you created a risk rule in a child domain and the global domain also has a similar risk rule then the global domain's rule takes precedence over the child domain's rule.

Reevaluation of calculators and rules

Prior to v20.0, when you reapply calculators or rules, the rerun flag is set to true and a business rule is triggered to run a schedule job that reapplies the calculators and rules. Starting from v20.0, you need not depend on the rerun flag. When you click on the Reapply Calculator button, a background job is triggered that reapplies the calculators and rules. This enables you to create calculators and rules for all the domains.

Settings for rollup calculators

In a domain, only one roll up calculator must be active for a table. For example, consider the Remediation Task table, sn_vul_vulnerability with the roll up calculator, Remediation Task Rollup in the global domain. If you duplicate this roll up calculator by changing the weights for the same table in the same domain, there will be discrepancies in the roll up calculations. Therefore, ensure to activate only one rollup calculator if there are two or more roll up calculators for a table in the same domain.