Closed signal policy
Signals outside policy are refused rather than retained.
Turn minimized posture evidence into explained access decisions.
Publish immutable device-health policy versions, accept only required signals, distinguish verified from self-reported evidence, and react when posture degrades.
- Closed signal policy
- Attestation distinction
- Explained findings
What you can evaluate
Posture without unnecessary collection.
Attestation distinction
Self-reported health is evidence, not trusted proof.
Explained findings
Every failure includes impact, remediation, and policy source.
Continuous response
Posture degradation triggers downstream re-evaluation.
Follow Device Trust from identity to evidence.
Each consequential action moves through the same six control points. See where 2AYE evaluates authority, requests human review, and preserves the outcome.
- 01IdentityWho or what is acting
- 02IntentSigned purpose and limits
- 03PolicyDeterministic evaluation
- 04ApprovalA named human when required
- 05ExecutionSingle-use grant, redeemed at the resource
- 06EvidenceReceipt joined to the audit chain
A practical adoption path
Start with one consequential workflow. Prove the boundary before expanding.
Assess
Document the environment, threat model, and integration boundary.
Design
Select protocols, signals, policies, and failure behavior.
Validate
Test vendor-specific APIs, tenant isolation, and abuse paths.
Release
Mark available only after deployed end-to-end verification.
What this includes
- Immutable device-health policy versions
- A closed signal set that refuses anything outside policy
- Verified evidence distinguished from self-report
- Explained findings with impact, remediation and policy source