Add patch deferral revalidation gates#1453
Open
jddark62 wants to merge 2 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Skill Improvement ($50-150 Bounty)
Skill Modified
Skill name:
patch-prioritizationSkill path:
skills/vuln-management/patch-prioritization/What Was Wrong
Fixes #1401.
The skill documented compensating controls, risk exceptions, expiration dates, and review dates, but did not require event-driven revalidation while a vulnerability remained deferred or under exception. That can make a previously valid exception look safe after the vendor releases a patch, the CVE enters CISA KEV, EPSS surges, exploit code becomes public, asset exposure changes, or compensating controls fail.
What This PR Fixes
Evidence
Before (false positive patch posture):
The old skill could leave this exception valid until the scheduled review date.
After (now correctly handled):
The skill requires immediate revalidation when patch availability, KEV/BOD, EPSS, exploitability, exposure, scanner/source freshness, or compensating-control evidence changes. The report must record triggers checked, evidence freshness, mandatory due dates, control retest state, resulting action, new deadline when applicable, and human approval for continued risk acceptance.
Test Cases Added/Updated
skills/vuln-management/patch-prioritization/tests/deferred-revalidation-gates.mdValidation performed:
YAML.safe_loadparsed all 7 YAML fixturesgit diff --checkBounty Tier
Bounty Info
Bounty Info
/claim #1401