SecurityInsight settings · Settings > Risk Analysis reports
Patch cycle: catch-up after
| Key | SI_PatchCycle_CatchUpDays |
|---|---|
| Where | Settings > Risk Analysis reports > Vulnerability (CVE) filters |
| Type | int |
| Default | 30 days. |
| Edition | Community |
What it does
When a finding counts as catch-up instead of being fixed in the monthly patch cycle: its fix was released (the month a "October 2026 Security Updates" text names -> that month's Patch Tuesday), or -- without one dated update -- the finding was first detected, more than this many days before the collection.
When set
The Patch cycle column of every finding (In monthly cycle / Catch-up / No fix available / Unknown) and its filter use this number from the next Risk Analysis run; findings already stored keep the value they were given.
When blank or default
Left blank, the default applies: 30 days.
Risk and how to reverse it
Changes what the Risk Analysis reports show, how findings are filtered or scored, or where reports go, from the next run; earlier reports are unchanged. Hiding findings can make real exposure invisible to readers. Reversible: change it back.
Requires
Nothing else.
Recommended
Keep the default. Change it when: Match your patch policy: e.g. 45 when monthly patches are allowed six weeks.
Documented for SecurityInsight 3.0.79. Written by the SecurityInsight team; Invardia publishes it. · All settings · Security review pack