Zero Trust Engineering — Workload identity and attestation

/02 About

Applications and workloads engineering reference for workload identity and attestation, including policy, logical interfaces, recovery and assurance.

Purpose: Workload identity and attestation. Domain: Applications and workloads. Family: decision. Scenario trigger: Present workload attestation for service admission. Input assurance: Identity credential, measured workload image and issuer chain. Evaluation: Validate runtime provenance, issuer trust and workload audience. Governing policy: Workload enrollment, attestation freshness and assurance policy. Resource-side obligation: Bind admitted workload to revocable machine principal. Protected concern: Runtime workload security boundary. Logical interface: Image digest environment measurement principal issuer nonce and validity. Evidence: Workload attestation verdict credential mapping and expiry. Failure: Untrusted image, replayed attestation or lost signing authority. Required recovery: Refuse admission and isolate affected workload. Architectural invariant: Workload identity must be cryptographically bound to verifiable runtime claims Adoption: replace reference roles with concrete owner-controlled services. Specify exact provider/consumer identities, schema fields and classifications, signal provenance and freshness, idempotency, authorization lifetime, timeout/retry limits, observation and tamper evidence. A denied or failed operation must not silently become a permitted one. Scope: original vendor-neutral, implementation-agnostic technical reference model. Illustrative logical components and behaviors are neither a deployed system nor evidence of regulatory compliance. Package identities remain stable within the package; cross-package semantic reconciliation requires separate explicit registry support.

Curated · other · unspecified · Published by Lattix · 28 elements · 34 relationships · validated on publish