I'm a privileged access and cloud security engineer working where PAM meets cloud infrastructure. The accounts, secrets, and escalation paths that most tooling treats as two separate problems, I treat as one.
I learn by building the thing and writing down where it broke. Everything below is a real lab: a real environment stood up, real tooling run against it, and honest notes on what failed. Right now I'm building secrets management patterns that put a CyberArk/Idira lens on cloud native tooling. That is my main focus.
- PAM x Cloud Labs: 11 hands on labs across CyberArk/Idira, Linux, AWS, and Azure. Each documents what I built, what broke, and what I would do differently.
- Conjur to Terraform secrets injection: provisioning AWS with zero credentials in Terraform state, proven by an automated check.
- Shadow admin audit: scoring CyberArk's SkyArk against known escalation paths in AWS and Azure.
- Secrets Manager as a PAM control plane: a CyberArk engineer's honest evaluation of the cloud native alternative to a vault.
- Full index in the labs repo: Kubernetes RBAC, RHEL 9 hardening, Sentinel detections, IAM least privilege, and more.
Privileged Access Management · Secrets Management · IAM least privilege · Policy as code · Cloud security posture · Infrastructure as code
Privileged Access, CyberArk/Idira
Linux, Red Hat
Identity and Security
Education
