Cluster mode
Version, endpoint, nodes, metadata and administrative access.
Cloud security
Google Kubernetes Engine security review
Review GKE modes, workload identity, network boundaries, admission policy and operational 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.
Identity
Workload Identity Federation for GKE, RBAC and service accounts.
Policy
Pod security, Binary Authorization and admission controls.
Runtime
Network policy, secrets, logging, detection 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
- 01GKE trust-boundary map
- 02Cluster and workload findings
- 03Policy and manifest remediation
- 04Operations and retest record
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