Add zero trust decision continuity gates#1304
Open
MAUROCERON wants to merge 1 commit into
Open
Conversation
4 tasks
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:
zero-trust-assessmentSkill path:
skills/identity/zero-trust-assessment/What Was Wrong
The skill had strong NIST SP 800-207 and CISA ZTMM pillar coverage, but it did not require reviewers to prove what happens when the policy engine, policy administrator, policy enforcement point, or trust-signal sources are unavailable or stale.
That can overstate maturity in zero trust deployments where:
What This PR Fixes
Closes #1303.
Step 7: Policy Decision Continuity and Fail-Secure Behavior.ZT-CONT-*checks for undocumented outage behavior, fail-open PEP behavior, stale trust signals, revocation propagation gaps, unbounded degraded mode, and untested decision continuity.skills/identity/zero-trust-assessment/tests/decision-continuity-edge-cases.mdwith vulnerable cached-allow and benign bounded-degraded scenarios.Evidence
Before (skill misses this):
The previous skill could record policy-engine and device-posture concepts, but did not force the reviewer to classify this as fail-open or stale-signal access.
After (now correctly handled):
The new
ZT-CONT-*checks require failure mode, cache/token TTL, stale-signal action, revocation propagation, outage test result, and break-glass boundary before maturity is scored.Test Cases Added/Updated
skills/identity/zero-trust-assessment/tests/decision-continuity-edge-cases.mdValidation
SKILL.md: 24 fences, balanced.tests/decision-continuity-edge-cases.md: 4 fences, balanced.SKILL.md.Policy Decision Continuity and Fail-Secure BehaviorDecision Continuity MatrixZT-CONT-01ZT-CONT-10SC-24 Fail in Known Statetests/decision-continuity-edge-cases.mdSources Checked
Duplicate Check
Checked open issues/PRs for:
zero-trust-assessmentdevice posture freshnesscoverage denominatorPE/PA/PEPfail-open fail-closedpolicy engine outagestale signal deny by defaultExisting related work covers source freshness/pillar evidence (#85), workload identity (#441), EO 14028 metadata (#609), device posture freshness/CAE (#670), and coverage denominators/exceptions (#1005). This PR is distinct because it focuses on policy-decision continuity, fail-secure/fail-open behavior, cache/token TTL, stale trust-signal action, and revocation propagation during PE/PA/PEP or signal-source outages.
Bounty Tier
Bounty Info