Secure Deployment Pipeline

When to Use

Use this skill when:

• You need to verify that the code running in production is the code you assume it is
• You are designing or auditing a CI/CD pipeline for insider threat resistance
• You want to implement binary provenance so artifact origins are traceable after security incidents
• You are moving from signature-based to provenance-based deployment policies
• You need to establish breakglass procedures that are auditable and rare enough to distinguish from attacks

Prerequisite: The secure-code-review skill must already be applied. Code review is the foundational mitigation — it is the multi-party authorization control that increases the cost of introducing malicious changes before they reach the pipeline. All pipeline controls assume reviewed code enters the source control system.

Step 1: Define Your Adversary Scope

Before mapping threats to mitigations, identify which adversary types apply to your organization. The threat model has three types: