Zero Trust Engineering — Artifact provenance and admission

/02 About

Applications and workloads engineering reference for artifact provenance and admission, including policy, logical interfaces, recovery and assurance.

Purpose: Artifact provenance and admission. Domain: Applications and workloads. Family: decision. Scenario trigger: Promote software artifact to runtime environment. Input assurance: Immutable artifact digest, chain of custody and policy evidence. Evaluation: Verify signed attestation, approved publisher and vulnerability posture. Governing policy: Artifact admission and exception expiration policy. Resource-side obligation: Admit trusted artifact or deny deployment. Protected concern: Production application runtime. Logical interface: Artifact digest signer attestation builder policy decision and time. Evidence: Artifact verification, signature chain and admission result. Failure: Attestation absent, signer revoked or source mismatch. Required recovery: Block promotion and invalidate affected artifact versions. Architectural invariant: Artifact tags cannot replace cryptographically verifiable content identity 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