Who this roadmap suits
This path suits people who enjoy building and automating, not only investigating. A background in software engineering, DevOps, or systems administration transfers well here.
Prerequisite skills
- Strong scripting or programming ability (Python, Bash, or similar).
- Solid systems administration across Linux and/or Windows, including automation tools.
- Working knowledge of networking and, ideally, cloud infrastructure basics.
- General security fundamentals (CIA triad, least privilege, defense in depth).
Staged learning path
1. Foundations
Make sure your scripting and systems administration skills are solid -- this role is more hands-on-keyboard building than most entry security roles.
2. Core skills
- Secure system design: applying least privilege and segmentation when designing infrastructure.
- Identity and access management concepts: authentication, authorization, and single sign-on.
- Vulnerability management: scanning, prioritizing, and remediating at scale.
- Secure software development practices if you work close to application code.
3. Tools
- Infrastructure-as-code tools for repeatable, auditable configuration.
- Vulnerability scanners and configuration management tools.
- SIEM and logging pipelines, from the engineering side of building and maintaining them.
- Version control and CI/CD pipelines, since security engineering increasingly overlaps with DevOps.
4. Practice
Build a small piece of security automation -- for example, a script that checks a set of servers against a hardening baseline and reports drift.
5. Portfolio
A GitHub repository with a documented automation project (with no real credentials or sensitive data) demonstrates this role's skills better than a resume line.
6. Interview readiness
Be ready to whiteboard a simple secure architecture -- for example, how you would segment a small web application's network -- and explain your reasoning.
Key concepts to master
- Zero trust principles and network segmentation.
- Secrets management and avoiding hardcoded credentials.
- Patch and vulnerability management lifecycles.
- The shared responsibility model if working with cloud infrastructure.
Hands-on labs to attempt
- Automate a configuration check across a small set of lab virtual machines.
- Set up centralized logging for a lab environment from scratch.
- Try our Cloud Security Monitoring and SIEM Monitoring Lab project ideas in Projects & Labs.
Certifications worth considering
General security certifications remain useful as a knowledge baseline, and cloud-provider security certifications can be valuable if you are targeting cloud-heavy environments. Match any certification to the specific infrastructure you want to work with.
How to know you are ready to apply
- You have built and can explain at least one piece of security automation.
- You can reason about trade-offs in a proposed architecture, not just recite terminology.
- You are comfortable reading and writing infrastructure configuration, not only using a GUI.