SecurityInsight settings · Settings > Data & retention
Runs before a CI is retired
| Key | SI_Pro_CmdbSql_RetireAfterRuns |
|---|---|
| Where | Settings > Data & retention > SQL CMDB connector |
| Type | int |
| Default | 2 runs |
| Edition | pro |
What it does
How many complete runs in a row an asset must be missing before the SQL CMDB connector retires its CI.
When set
Higher keeps CIs of assets that drop out now and then, but marks really removed assets as retired later. A retired CI is kept with its history and comes back if the asset is seen again. A run that reads the same snapshot as the last one does not count. Below 1 is raised to 1; non-numbers use 2.
When blank or default
Left blank, the default applies: 2 runs
Risk and how to reverse it
Changes how long data is kept or how quickly assets are treated as gone. Shortening a retention DELETES older data at the next clean-up and that cannot be undone; shortening a grace period retires assets (and closes their findings) sooner. Lengthening is safe but uses more storage.
Requires
A SecurityInsight Pro licence.
Recommended
Keep the default. Change it when: Raise it if CIs are retired and reactivated for assets that are still there.
Documented for SecurityInsight 3.0.79. Written by the SecurityInsight team; Invardia publishes it. · All settings · Security review pack