Zero Trust Engineering — Secure software supply chain

/02 About

Applications and workloads engineering reference for secure software supply chain, including policy, logical interfaces, recovery and assurance.

Purpose: Secure software supply chain. Domain: Applications and workloads. Family: assurance. Scenario trigger: Assess code-to-production artifact provenance. Input assurance: Source attestation, isolated build records and dependencies. Evaluation: Validate source integrity, policy scans and artifact provenance. Governing policy: Secure engineering pipeline and deployment trust policy. Resource-side obligation: Reject unverified build or publish signed immutable artifact. Protected concern: Enterprise software artifact repository. Logical interface: Source revision build context dependency inventory signature and SBOM. Evidence: Build provenance dependency report and release approval. Failure: Compromised build runner or untrusted dependency. Required recovery: Quarantine affected artifact and rebuild from trusted inputs. Architectural invariant: Deployment requires independent verification of software provenance 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 · 29 elements · 33 relationships · validated on publish