Manage definition properties

You can configure additional capabilities and configuration options for the definition ruleset.

For these options to be editable, at least one instance itself must be defined under My instances. Users can synchronize definition overrides and custom definitions between non-production and production instances. Ensuring a consistent ruleset is being applied throughout the instance stack.

Scan Engine admins can remove the checkbox on the active field, or, change the value of the boolean Active field to false without requiring an override.

Table 1. Definition deactivation scenarios

Scenario	Behavior
Direct deactivation of base system definition	The definition is deactivated via UI or API without creating an override record. No override is recorded in the system.
Quota impact check after deactivation	Deactivated base system definitions are excluded from active definition counts. They do not count toward custom definition quotas. System recalculates entitlements accurately when definitions change status.
Override-then-deactivate existing workflow	When a base system definition is overridden and then deactivated, the behavior remains unchanged. The deactivated override does not count as a custom definition.
Entitlement hashing integrity	All combinations of base system and overridden definitions in active or inactive states produce consistent entitlement hash results. No regressions occur for states that existed before this feature was introduced.

Note:

Deactivating a definition does not remove it from the system. It only changes the active status. If you need to completely remove a definition, contact your system administrator.