Guided labs
Full step-by-step manuals: architecture, prerequisites, commands, expected results and troubleshooting. You learn the workflow end to end.
Labs
You build the environment. That is the point.
PrimeSec labs are professional lab manuals, not click-through simulators. You stand up the VMs, the containers and the cloud resources yourself, work through the manual, and capture evidence of what you built. Troubleshooting your own environment is part of the skill.
PrimeSec does not provision hosted virtual machines, attack boxes or cloud tenants. Cloud labs run in your own account and include cleanup instructions.
Progression
Guided → Assisted → Challenge → Capstone
Support is removed deliberately as you improve, so the last thing you build is something you solved on your own.
Assisted labs
The same objectives with the hand-holding removed. Key steps are outlined; you fill in the configuration and verify your own results.
Challenge labs
Objectives, requirements and an architecture target — limited guidance. You research, build and defend your approach independently.
Capstone projects
Design, implement, secure, test, document and present a larger environment. The work becomes portfolio evidence.
Inside a lab manual
Written like documentation you would get on the job
Every manual is structured the same way, so you always know what you are building, how to verify it, and what to keep as evidence.
- Objectives & learning outcomes
- Architecture diagram
- Prerequisites & system requirements
- Setup, commands and scripts
- Expected results & verification
- Troubleshooting guide
- Evidence checkpoints & knowledge checks
- Portfolio documentation & cleanup
Lab domains
Where the practical work happens
Labs are attached to the modules of each course and learning path rather than sold as a separate catalogue.
Cloud security
Identity, networking, logging, posture management and workload hardening in Azure, AWS and Google Cloud.
IAM & identity
Entra ID, Active Directory, SSO and federation, Conditional Access, PIM, RBAC and least privilege.
SOC & detection
Log pipelines, SIEM queries, detection rules, alert triage, investigation and incident documentation.
AI security
LLM application security, prompt injection defence, RAG and vector store hardening, agent and MCP security.
DevSecOps
Policy as code, pipeline security, container and image signing, secrets management and IaC scanning.
GRC & governance
Control mapping, risk assessment, threat models, policy writing and AI governance documentation.
What you build labs on
Each manual lists exact prerequisites and system requirements before you start, so you know what a lab needs before you commit time to it.
- Your own laptop or workstation
- Hyper-V, VMware or VirtualBox
- Docker & Docker Compose
- Linux and Windows VMs
- Azure (your own tenant)
- AWS (your own account)
- Google Cloud (your own project)
- GitHub for documentation
Cloud labs can generate charges in your own account. Follow the cleanup section at the end of every cloud lab.
Every lab leaves evidence behind
Labs are documented, not just completed. The artefacts you produce become the portfolio you show an employer.
- README and architecture diagrams
- Screenshots and configuration exports
- Terraform, PowerShell, Python, Bash and KQL
- Detection rules, policies and findings
- Incident, risk and remediation write-ups
Never publish credentials, secrets, proprietary data or vulnerable production configuration to a public repository.
Labs come with the course.
Choose a learning path or a course and the lab manuals unlock alongside the modules they belong to.