Greg Castle
Principal Security Engineer at Google
Seattle, Washington, United States
Summary
🤩
RockstarGreg Castle is a Principal Security Engineer at Google with 12 years at the company and 19 years in industry focused on Kubernetes and cloud platform security. As tech lead for GKE security, he founded the Kubernetes Container Identity Working Group and led teams that delivered OIDC support, Secrets Encryption, and RuntimeClass, now foundational to secure cloud-native workloads. He’s shifted attention to securing AI/ML workloads on Kubernetes, bridging platform hardening, runtime security, and developer-facing identity controls. A former pentester and DFIR practitioner, Greg brings hands-on incident response and forensic expertise to large-scale product security and policy work. He’s an active open-source contributor to notable projects like GRR Rapid Response and ForensicArtifacts, combining quality-focused testing with backend improvements that improve incident response tooling. Based in Seattle, he’s a frequent speaker at KubeCon, Black Hat, and other industry events, known for translating deep technical detail into pragmatic, production-ready security controls.
12 years of coding experience
Stackoverflow
1reputation
0reached
0answers
0questions
Github Skills (11)
unit-testing10
api10
python10
apidoc10
protobuffer10
protobuf10
yaml9
computer-forensics9
filesystem9
javascript9
windows-gui8
Programming languages (10)
Github contributions (5)
google/grr
Aug 2013 - Mar 2017
GRR Rapid Response: remote live forensics for incident response
Role in this project:
Back-end Developer
Back-end DeveloperContributions:3 releases, 229 commits, 49 PRs in 3 years 7 months
Contributions summary:Greg contributed to bug fixes and improvements related to the GRR project's core functionality. They addressed issues within the GUI's JavaScript, corrected bugs related to file management, and modified code related to HTTP API and client communication. Additionally, the user was involved in performance optimizations by improving code related to the ProtoDict and file transfer.
incident-responseforensicsgrrrapidrapid-response
ForensicArtifacts/artifacts
Nov 2014 - Jun 2017
Digital Forensics artifact repository
Role in this project:QA Engineer / Test Automation Engineer
QA Engineer / Test Automation EngineerContributions:3 releases, 80 commits, 127 PRs in 2 years 7 months
Contributions summary:Greg primarily contributed to the quality assurance of the project, focusing on testing the artifact definitions. Their work involved writing and modifying test cases, with an emphasis on validating supported operating systems, labels, and overall artifact definition formats. Furthermore, the user implemented tests for command artifacts and ensured the correct functionality of the artifact registry.
securitycybersecurityartifact-repositoryforensicsdigital-forensics
Find and Hire Top DevelopersWe’ve analyzed the programming source code of over 60 million software developers on GitHub and scored them by 50,000 skills. Sign-up on Prog,AI to search for software developers.