Remediation Aging
Age remediation findings against a caller-supplied target.
Description
Remediation aging compares an issue’s age with a selected target.
Remediation aging compares an issue’s age with a selected target. Closed status takes precedence over lateness.1
Age remediation findings against a caller-supplied target.
When to use Remediation Aging
Use this tool to age remediation findings against a caller-supplied target.
Prepare the documented facts, aligned totals or expected/observed evidence labels requested. Choose applicable requirements and thresholds separately before interpreting a planning screen.
How to use Remediation Aging and understand its results
- Prepare the documented facts, aligned totals or expected/observed evidence labels requested. Choose applicable requirements and thresholds separately before interpreting a planning screen.
- Enter findingDate, asOfDate, targetRemediationDays, remediationComplete, highSeverity using the field table and calculation rules, then run the tool.
- Read findingAgeDays, daysPastTarget, status. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| findingDate | Finding date | string | Required |
| asOfDate | As-of date | string | Required |
| targetRemediationDays | Target remediation days | integer; minimum: 0 | Required |
| remediationComplete | Remediation complete | boolean | Required |
| highSeverity | High-severity finding | boolean | Required |
Enter UTC-midnight date strings ordered asOf≥finding, nonnegative integer target and flags. Return age/past days; closed if complete, on-track if not late, otherwise critical-overdue if high severity or overdue.
age=floor((asOf−finding)/day); past=max(0,age−target) Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| findingAgeDays | Finding age (days) | integer; minimum: 0 |
| daysPastTarget | Days past target (days) | integer; minimum: 0 |
| status | Remediation status | string; one of "closed", "on-track", "overdue", "critical-overdue" |
{
"input": {
"findingDate": "2025-01-01",
"asOfDate": "2025-02-15",
"targetRemediationDays": 30,
"remediationComplete": false,
"highSeverity": true
},
"output": {
"findingAgeDays": 45,
"daysPastTarget": 15,
"status": "critical-overdue"
}
}Limitations and assumptions
Native date normalization applies. No completion evidence or universal remediation deadline is verified.
Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Extremely large text inputs are rejected. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.
Alternative or Complementary methods
Use Cold-Review Escalation: Route post-signoff cold-review findings by impact and remediation status. For a complementary task, use Pentest Remediation: Measure penetration-test remediation and retest completion.
References
-
Remediation Aging — tool.io
Similar or alternative tools
- Cold-Review Escalation
Route post-signoff cold-review findings by impact and remediation status.
- Pentest Remediation
Measure penetration-test remediation and retest completion.