Pentest Remediation
Measure penetration-test remediation and retest completion.
Description
Remediation and retesting are separate stages in validating penetration-test fixes.
Remediation and retesting are separate stages in validating penetration-test fixes.1
Measure penetration-test remediation and retest completion.
When to use Pentest Remediation
Use this tool to measure penetration-test remediation and retest completion.
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 Pentest Remediation 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 findingCount, remediatedCount, retestedCount, passedRetestCount using the field table and calculation rules, then run the tool.
- Read remediationPercent, retestCoveragePercent, retestPassPercent, unvalidatedRemediations. 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 |
|---|---|---|---|
| findingCount | Penetration-test findings | integer; minimum: 0 | Required |
| remediatedCount | Remediated findings | integer; minimum: 0 | Required |
| retestedCount | Retested findings | integer; minimum: 0 | Required |
| passedRetestCount | Findings passing retest | integer; minimum: 0 | Required |
Enter positive findings and nested integer counts passed≤retested≤fixed≤findings. Return percentages, pass percentage (zero when no retests) and fixed−retested count.
remediation%=100fixed/findings; coverage%=100retested/fixed Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| remediationPercent | Remediation percentage (%) | number; minimum: 0; maximum: 100 |
| retestCoveragePercent | Retest coverage (%) | number; minimum: 0; maximum: 100 |
| retestPassPercent | Retest pass percentage (%) | number; minimum: 0; maximum: 100 |
| unvalidatedRemediations | Remediations not retested | integer; minimum: 0 |
{
"input": {
"findingCount": 10,
"remediatedCount": 8,
"retestedCount": 8,
"passedRetestCount": 7
},
"output": {
"remediationPercent": 80,
"retestCoveragePercent": 100,
"retestPassPercent": 87.5,
"unvalidatedRemediations": 0
}
} Limitations and assumptions
Zero fixed causes a nonfinite retest-coverage result and is rejected by output validation. No testing or verified fixes are performed.
Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.
Alternative or Complementary methods
Use Remediation Aging: Age remediation findings against a caller-supplied target. For a complementary task, use Failover Evidence Coverage: Audit disaster-recovery failover evidence.
References
-
Pentest Remediation — tool.io
Similar or alternative tools
- Remediation Aging
Age remediation findings against a caller-supplied target.
- Failover Evidence Coverage
Audit disaster-recovery failover evidence.