SecurityInsight settings · Settings > Data & retention
Days unseen before a CI may be retired
| Key | SI_Cmdb_RetireAfterDays |
|---|---|
| Where | Settings > Data & retention > SQL CMDB connector |
| Type | int |
| Default | 7 days |
| Edition | pro |
| Confirmation | SecurityInsight asks you to confirm before it is switched on. |
What it does
The least number of days an asset must go unseen before its CI is retired -- in the CI table and in the state handed to ServiceNow. A brake under every other rule: whatever decided the retirement (the grace period, the runs missing, an early retirement on the Not seen anymore page), the CI waits until its asset has been unseen this long.
When set
Higher keeps CIs of assets that are away for a while; a CI retired too early is the one mistake that does not heal by itself. No grace period can be shorter than this. Below 1 is raised to 1; non-numbers use 7.
When blank or default
Left blank, the default applies: 7 days
Risk and how to reverse it
A lower value lets a CI retire sooner after its asset was last seen -- a device that is only offline for a few days can lose its CI (in the CI table and in ServiceNow). A CI retired by mistake does not heal by itself until the asset is seen again. Reversible for the future.
Requires
A SecurityInsight Pro licence.
Recommended
7 days (the brake against CIs retired by mistake).
Documented for SecurityInsight 3.0.79. Written by the SecurityInsight team; Invardia publishes it. · All settings · Security review pack