SecurityInsight settings · Settings > Data & retention
Days to fix a critical finding
| Key | SI_Pro_FindingSla_CriticalDays |
|---|---|
| Where | Settings > Data & retention |
| Type | int |
| Default | 15 days |
| Edition | pro |
What it does
How many days a critical finding has to be fixed, counted from when it was first found (or found again after it was fixed).
When set
Sets the due date of every critical finding. A finding past its due date is shown as overdue on the CI page, the service views and the trend. 0 = critical findings have no due date.
When blank or default
Left blank, the default applies: 15 days
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: Set it to the deadline your security policy gives critical findings.
Documented for SecurityInsight 3.0.79. Written by the SecurityInsight team; Invardia publishes it. · All settings · Security review pack