Cybersecurity expert & IT lawyer working where law, infrastructure, and security meet.
CISO by day, security tinkerer and homelab enthusiast by night.

• Design and run information security programs with a strong blue-team mindset
• Translate regulatory and legal requirements into practical, secure architectures
• Focus on privacy by design, security by default, and evidence-based decisions

My background as both a CISO and IT lawyer helps bridge the gap between “what the regulation says” and “what we can actually build and operate.”

• OSCAL & Compliance as Code
  Modeling controls, systems, and evidence in a way that:

  • is machine-readable
  • is version-controlled
  • can be integrated into CI/CD and infrastructure workflows

• Audit automation
  Exploring how far we can push:

  • automated evidence collection
  • continuous control monitoring
  • fully automated audit reporting

  Most of this work is internal/experimental for now, but it strongly influences how I think about security architecture and documentation.

• Home cluster & GitOps
  Migrating a classic Docker-based home server to a Kubernetes-based home cluster:

  • GitOps-driven management
  • declarative everything
  • secure-by-default setup, even “just” for a homelab

Note
Do not use any code or configuration from my repositories in an operational or production environment without first:

• testing it thoroughly in a non-operational environment, and
• reviewing it for your specific use case, risk appetite, and legal/regulatory context.

Security and compliance are always context-dependent.

If my projects or write-ups are useful to you and you’d like to say thanks:

• GitHub Sponsors (one-time or recurring):
  👉 https://github.com/sponsors/cypr0

Even a virtual ☕ helps justify spending more time on open work.