feat(zero-trust-assessment): add private app connector fail-open gates#2756
Closed
zeroknowledge0x wants to merge 1 commit into
Closed
feat(zero-trust-assessment): add private app connector fail-open gates#2756zeroknowledge0x wants to merge 1 commit into
zeroknowledge0x wants to merge 1 commit into
Conversation
- Add ZT-NET-12 through ZT-NET-16 findings for connector fail-open gaps - Add Private App Connector Fail-Open Readiness Assessment section (6 factors) Addresses UnitOneAI#2744: ZTNA designs that silently route around connectors, fall back to VPN, or leave internal apps reachable from trusted networks violate zero trust. New gates verify fail-closed behavior, policy sync, DNS enforcement, bypass governance, direct route testing, and audit trail.
github-actions
Bot
added
the
needs-approved-issue
|
Thanks for the submission! 🙏 SecuritySkills is now issue-first: contributions need a linked issue that a maintainer has marked approved before a PR is opened. Please open an issue describing the skill, wait for the |
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
1 participant
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.
Summary
Addresses #2744 — adds private app connector fail-open gates to the
zero-trust-assessmentskill.Changes
Networks pillar findings (ZT-NET-12 through ZT-NET-16):
ZT-NET-12: Private app connector fails open — traffic bypasses connector on outage instead of failing closedZT-NET-13: Emergency bypass for private apps persists after outage resolution (no expiry, no owner, no audit trail)ZT-NET-14: Split DNS exposes internal app addresses directly when connector is downZT-NET-15: Connector health check passes but policy sync is stale or failing silentlyZT-NET-16: Private apps reachable from "trusted" network segments without policy enforcementNew section: Private App Connector Fail-Open Readiness
6 readiness factors covering fail-closed behavior, policy sync validation, DNS enforcement, bypass governance, direct route testing, and audit trail.
Why
Some ZTNA designs silently route around connectors when they fail, fall back to VPN, or leave internal apps reachable from "trusted" networks — effectively degrading zero trust into implicit trust. These gates verify that connector failures result in controlled denial (fail-closed), not silent bypass.
Closes #2744