20+ years breaking and hardening systems.
Pragmatic by design. Function over form.

I approach systems with an offensive mindset: dissect → exploit → harden.

Focused on cloud security architecture (Azure/AWS), DevSecOps, and application security.
I design for real-world failure scenarios, not theoretical models.

I value:

• Simple, resilient architectures
• Automation over manual control
• Security as a system property, not a layer

• Cloud Security

  • Azure / AWS architecture
  • IAM, Zero Trust, network segmentation
  • Logging, monitoring, detection engineering

• Application Security

  • Threat modeling
  • Secure design & code review
  • SAST / DAST / SCA integration

• DevSecOps

  • CI/CD hardening
  • Policy as Code
  • Secure software supply chain

• Infrastructure as Code

  • Terraform (modular design, reusable secure baselines)
  • Policy enforcement (OPA, Sentinel)
  • Drift detection & state management strategies

• Containers & Orchestration

  • Docker (image hardening, minimal base images)
  • Kubernetes (RBAC, network policies, pod security, secrets management)
  • Secure workload isolation patterns

• Platform Security

  • Identity as control plane (IAM-first design)
  • Secrets management (rotation, scoping, vault integration)
  • Network architecture (private endpoints, segmentation, egress control)

• Observability & Detection

  • Centralized logging pipelines
  • SIEM integration patterns
  • Detection-as-code mindset

• Languages

  • Python (automation, security tooling, scripting)
  • Bash / Shell
  • ASM

• Cloud

  • Azure, AWS

• Infrastructure

  • Terraform, Docker, Kubernetes

• Security Tooling

  • SAST / DAST / SCA tools
  • Dependency & supply chain security
  • IAM frameworks and policy engines

• DevSecOps

  • CI/CD (GitHub Actions, Azure DevOps, etc.)
  • Pipeline security & enforcement

• Security is emergent from design, not tooling
• Complexity is a risk multiplier
• Automation reduces human attack surface
• If you can’t detect it, you don’t control it
• Build systems assuming they will fail

• Cloud-native security patterns (Azure / AWS)
• Identity-centric architecture (IAM as control plane)
• Secure-by-default platform design
• Detection and response integration in DevSecOps

• LinkedIn: https://linkedin.com/in/gdeangelg

Systems are meant to be tested, broken, and rebuilt stronger.