Control plane
Cluster configuration, upgrades, audit logs and administrative paths.
Cloud security
Kubernetes security assessment
Review cluster boundaries, workload identity, admission controls, secrets, networks and runtime visibility. 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.
Workloads
Pod security, service accounts, capabilities and image provenance.
Network
Ingress, egress, network policy and sensitive service exposure.
Operations
Secrets, admission policy, detection, backup and recovery.
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
- 01Cluster threat and trust-boundary map
- 02Evidence-backed workload findings
- 03Policy and manifest remediation
- 04Retest and operating checklist
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