Source
Repository access, branch controls, review and signing.
DevSecOps
Software supply chain security
Protect source, builds, dependencies and artifacts from unauthorised change through deployment. Put useful security controls close to the change and give every actionable failure an owner.
01 / Scope
Work on the system, not around it.
The engagement starts with the architecture and working constraints already in place. We agree the risky paths, make the changes visible and leave ownership with the team running the system.
Build
Runner isolation, credentials, dependencies and reproducibility.
Artifact
SBOM, provenance, signing, registry policy and promotion.
Deployment
Verification, admission, exceptions and incident response.
02 / Method
Put useful security controls close to the change and give every actionable failure an owner.
Scope and access are agreed before the work begins. Decisions, changes and residual risk remain visible throughout the engagement.
Baseline the signal
Start with evidence, owners and the constraints that shape the safe solution.
Tune for material risk
Prioritise by practical impact and implement with the people who operate the system.
Enforce in stages
Test the changed path, document the decision and hand over a backlog that still makes sense.
03 / What remains
- 01Supply-chain threat model
- 02Build and artifact findings
- 03Signing and verification implementation
- 04Dependency and exception workflow
Related work
Continue with the adjacent problem.
04 / Talk to Gritt
What is happening in the system?
Send the cloud, workload or deadline. An engineer will reply and tell you whether this is the right scope.
email