Build
Minimal bases, reproducible builds, secrets and dependency controls.
Cloud security
Container security engineering
Secure how container images are built, stored, admitted and run without adding an unusable release gate. Reduce cloud attack paths without making routine engineering depend on a security ticket.
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.
Registry
Access, immutability, signing, retention and provenance.
Admission
Allowed sources, signature verification and policy exceptions.
Runtime
Capabilities, filesystems, identities and behavioural signals.
02 / Method
Reduce cloud attack paths without making routine engineering depend on a security ticket.
Scope and access are agreed before the work begins. Decisions, changes and residual risk remain visible throughout the engagement.
Map the boundary
Start with evidence, owners and the constraints that shape the safe solution.
Validate the risky paths
Prioritise by practical impact and implement with the people who operate the system.
Implement and verify
Test the changed path, document the decision and hand over a backlog that still makes sense.
03 / What remains
- 01Container build and registry review
- 02Image policy and exception rules
- 03Pipeline and admission-control changes
- 04Runtime hardening backlog
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