Custom-Rule Application During a Forced Full Rescan

Custom rules are applied only during the initial codebase scan and during a forced full rescan. During the forced full rescan, if a previously scanned file now matches a new custom rule, the existing system-generated inventory item for that file is overwritten with the custom-rule data. The following two scenarios describe this over-write process.

Note:Custom rules affect only system-generated inventory items that have not been manually updated. The rules have no impact on manually-created (custom) inventory items and on system-generated inventory items that users have updated.

Scenario 1: New Custom-Rule Data Identifying the Same Component Version and License as the Existing Inventory Item

In this case, the scan applies the custom rule by updating the existing inventory item as follows:

•

Appends new detection notes to reflect the custom rule.

•

Updates the Created by field value for the inventory item to High Confidence Custom Auto-WriteUp Rule in the Analysis Workbench.

Note that, in this scenario, the scan retains the Audit Notes, As-Found License Text, or Notices Text content defined in the existing inventory item. It does not append custom-rule data to these fields.

Scenario 2: New Custom-Rule Data Identifying a Component Version and License Different from the Existing Inventory Item

In this case, the scan applies the custom rule as follows:

•

Creates a new inventory item based on the custom-rule data.

•

Retains the existing inventory item, but disassociates its files and adds them to the new inventory item.

•

Applies the status and priority of the existing inventory to the new inventory item.

•

Appends any Audit Notes, As-Found License Text, or Notices Text content defined in the custom rule.