About
Secret Squirrel
Anonymous Security Practitioner
Field-tested perspectives on offensive security, SecOps, healthcare security, AI & automation, and leadership.
This publication also documents the long-term journey toward executive security leadership through continuous learning, technical depth, and practical experience.
People · Process · Technology
Focus Areas
Offensive Security
Adversary simulation, red team methodology, APT tradecraft, and using offensive perspective to build defenses that hold against real-world attacks.
SecOps
Detection engineering, threat intelligence, vulnerability research, and security operations at enterprise scale. Building programs that find what scanners miss.
Healthcare Security
HIPAA compliance, clinical environment threat modeling, PHI protection at scale, and building security programs that don't break the workflows clinicians depend on.
Security Leadership
Board communication, risk framing, security program governance, team building, and the practitioner-to-executive path documented in real time.
AI & Automation
Safely enabling AI in regulated environments, DLP for GenAI tools, automation strategy, and the security implications of emerging AI capabilities.
The Journey
Documenting the continuous pursuit of becoming a stronger security leader — transparently, in real time, from Director toward CISO.
Mission
SecretSquirrel.cloud exists because the best security writing comes from people who are doing the work — not from vendors with a product to sell or agencies with clients to protect. This publication shares what I actually build, break, find, and learn.
The goal is to be useful to the practitioner who needs real answers, and to the emerging security leader who wants to understand what the path forward looks like from someone actively walking it.
Why Anonymous?
The anonymity is intentional — not to create mystery, but to enable honesty. Writing as a named professional at a named organization creates constraints. Certain lessons, mistakes, observations, and opinions can't be shared openly. The anonymous format removes those constraints.
The content is real. The experiences are real. The author's name will be attached to this site when the timing is right.
Values
-
Practitioner first
Content written by someone doing the work, not summarizing other people's work. If I haven't built it, broken it, or deployed it, I don't write about it as if I have.
-
No vendor content
No sponsored posts. No product placements. No "partner" content. The recommendations here are based on what actually works in production environments, not what pays a commission.
-
Responsible disclosure
CVE research and vulnerability findings are disclosed to vendors before publication. IOCs are shared with relevant ISACs. PoC code is withheld or sanitized until patches are widely deployed.
-
Continuous learning
Security leadership is a practice, not a destination. This publication documents the learning as it happens — including the failures and course corrections.
Contact
- PGP
- Key available on request
- Signal
- Available to vetted contacts