My focus is on the five chokepoints where security succeeds or fails: IAM (who gets in), Key Management (who holds the secrets), Zero Trust (who can move inside), Logging (what happened), and Incident Response (how systems recover). Every lab, certification, and project strengthens one of these pillars as I keep leveling up.
Developing control across networking, OS management, cloud, Linux, and security — the core domains every enterprise fortress depends on. Each step is another brick toward Security Engineering and Architecture.
Working through TryHackMe’s Security Engineer learning track — building foundations in threats, risk, network security, software security, IAM, cryptography, and incident response. This path forms the base layer of my future work in cloud security and secure architecture
Learning core AWS concepts — IAM, S3 security, VPC networking, encryption, and cloud monitoring. Building the fundamentals for my path into Cloud Security Engineering.
Who can move inside. Proved enforcement of conditional access, device compliance, and micro segmentation to block lateral movement.
Monitored sign-ins, audit logs, and device compliance to prove visibility into who did what, when.
Enforced authentication and authorization by controlling users, groups, and policies.
Secured encryption keys and secrets to prove who holds the keys controls the system.
Built and continuously expanding identity-first access control across AWS IAM and Microsoft Entra ID, enforcing users, groups, RBAC, and least-privilege as a living security control layer.
