feat(zero-trust-assessment): add unmanaged device browser isolation gates#2755
Closed
zeroknowledge0x wants to merge 4 commits into
Closed
feat(zero-trust-assessment): add unmanaged device browser isolation gates#2755zeroknowledge0x wants to merge 4 commits into
zeroknowledge0x wants to merge 4 commits into
Conversation
…nce gates Addresses review feedback from UnitOneAI#2724: - Add Suppression Risk Tiers (Safe/Moderate/Risky/Dangerous) to distinguish evidence-backed, time-bounded, owner-approved suppressions from blanket indefinite exclusions - Add Safe Suppression Requirements with mandatory fields: named owner, expiry date, scope, evidence, and auto-reopen triggers - Add Drift Evidence Gates (6 gates): suppression age, plugin update, asset exposure change, package change, compensating control status, quarterly review - Add Suppression Inventory and Drift Gate Audit to Output Format sections - Enforce critical distinction: compensated risk != confirmed false positive - Update FP Validation Workflow disposition to require lifecycle compliance - Update Prompt Injection Safety Notice with suppression lifecycle constraints - Add pitfalls UnitOneAI#6 (indefinite suppressions) and UnitOneAI#7 (compensated risk as FP) Closes UnitOneAI#2724
…ift evidence gates
…cle model - Remove duplicated 'Indefinite (no expiry)' and 'Compensated risk misclassified as FP' lines in output - Suppression lifecycle model with risk tiers, drift gates, and evidence requirements - Enforce FP vs compensated-risk disambiguation throughout - Add drift evidence gates: plugin update, exposure change, package change, control removal - Common pitfalls UnitOneAI#6 (indefinite suppressions) and UnitOneAI#7 (compensated-as-FP) Closes UnitOneAI#2724
…ates - Add browser isolation controls to BYOD/Unmanaged maturity row (Devices pillar) - Add ZT-DEV-11 through ZT-DEV-15 findings for isolation gaps - Add Browser Isolation Readiness Assessment section with 7 readiness factors Addresses UnitOneAI#2743: unmanaged device access needs isolation gates to constrain BYOD access and make it testable. Covers data movement controls (clipboard, download, print, local storage), session cleanup, file URL handling, mobile browser coverage, negative testing, and app sensitivity mapping.
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 #2743 — adds unmanaged device browser isolation gates to the
zero-trust-assessmentskill.Changes
Devices pillar maturity table (BYOD/Unmanaged row):
New findings (ZT-DEV-11 through ZT-DEV-15):
ZT-DEV-11: Unmanaged/BYOD devices access sensitive apps without browser isolationZT-DEV-12: Browser isolation deployed but without data movement controls (clipboard, download, print, local storage)ZT-DEV-13: No negative tests验证 isolation effectiveness (screenshot bypass, copy/paste, mobile browser differences)ZT-DEV-14: Isolated browser session lacks automatic cleanup on device state change or session terminationZT-DEV-15: Unmanaged devices can open direct file URLs outside isolated browser contextNew section: Browser Isolation Readiness Assessment
7 readiness factors covering isolation mode, data movement controls, session cleanup, file URL handling, mobile browser coverage, negative testing, and app sensitivity mapping.
Why
The original skill assessed BYOD at a high level ("risk-based access") but didn't verify how unmanaged device access is constrained. Browser isolation is the primary control for BYOD scenarios — without verified isolation gates (clipboard/download/print blocking, session cleanup, negative testing), "browser isolation enabled" is not enough evidence of effective data movement controls.
Closes #2743