Roadmaps Security roadmaps IT security and infrastructure

Infrastructure Hardening and Configuration

Set servers, hypervisors, virtual desktops and storage up securely, keep them that way, and spot drift and tampering.

Estimated time: 15–26 months · At about 10 hours a week.

Learning path

Click a topic to see what to learn and where. Mark topics as you go; your progress is saved in this browser only.

  • Core topic
  • Optional
  1. Beginner · 2–3 months Secure configuration foundations
  2. Intermediate · 3–5 months Automation and virtualisation
  3. Advanced · 4–6 months Drift, integrity and scale
  4. Expert · 6–12 months Strategy and leadership

All topics in detail

BeginnerTime: 2–3 months

Secure configuration foundations

Skills

  • Harden a Windows and a Linux server against a benchmark.
  • Secure common services such as a web server and a database.
  • Keep an accurate asset and configuration inventory.

Hands-on projects and labs

  • Harden a Linux server with Lynis and a Windows server against a CIS Benchmark, and record your scores.
  • Configure TLS on a web server to a modern standard and test it.

Done when you can…

  • Explain the main hardening steps for a server and a common service.
  • Show benchmark scores before and after hardening.

Beginner

Why configuration matters

Default settings favour convenience over security. Learn how attackers use default accounts, open services and weak settings, and what hardening removes.

Resources

Beginner

Benchmarks and standards

CIS Benchmarks, DISA STIGs and vendor guides give tested, specific settings for each system. Learn to read them and choose the right profile.

Resources

Beginner

Server hardening

Minimal install, no unused services, least privilege, strong authentication, logging and a host firewall. The same ideas on Windows and Linux servers.

Resources

Beginner

Hardening services

Web servers, databases and other services each have their own secure configuration: TLS, authentication, limits and safe defaults.

Resources

Beginner

Asset and configuration management

You cannot harden what you do not track. Keep an accurate inventory and a record of how each system should be configured.

Resources

IntermediateTime: 3–5 months

Automation and virtualisation

Skills

  • Apply hardened configuration as code across many systems.
  • Build and maintain hardened golden images.
  • Secure hypervisors, VDI and storage.
  • Scan the estate for benchmark compliance automatically.

Hands-on projects and labs

  • Write an Ansible playbook that hardens a Linux server to a benchmark and re-applies on drift.
  • Build a hardened image, scan it with OpenSCAP, and fix the findings.

Done when you can…

  • Show new systems built hardened from code, not by hand.
  • Produce a compliance report across several systems.

Intermediate

Configuration as code

Define hardened configuration in code and apply it automatically with Ansible, Puppet or DSC, so every system is built the same way.

Resources

Intermediate

Hardened golden images

Build secure base images once and deploy from them, so new systems start hardened. Rebuild and re-scan them regularly.

Resources

Intermediate

Hypervisor and virtualisation security

The hypervisor controls every VM on it, and its management plane is a prime target. Harden it, isolate management, and patch it quickly.

Resources

Intermediate

Virtual desktop security

VDI concentrates many users on shared infrastructure. Harden the images, isolate sessions and control what leaves the virtual desktop.

Resources

Intermediate

Automated compliance scanning

Scan systems against benchmarks on a schedule with OpenSCAP or CIS-CAT, and report which systems drift from the standard.

Resources

AdvancedTime: 4–6 months

Drift, integrity and scale

Skills

  • Detect and remediate configuration drift automatically.
  • Monitor file integrity on critical systems.
  • Bake hardening into build pipelines.
  • Secure administrative access to infrastructure.

Hands-on projects and labs

  • Set up file integrity monitoring and trigger it with a configuration change.
  • Build a Packer pipeline that produces a hardened, scanned image.

Done when you can…

  • Show drift detected and corrected automatically across an estate.
  • Demonstrate that admin access requires a separate account and path.

Advanced

Configuration drift detection

Systems slowly diverge from the standard. Detect drift and either alert on it or automatically bring the system back.

Resources

Advanced

File integrity monitoring

Watch critical files and configuration for unauthorised change, a strong signal of compromise or a mistake.

Resources

Advanced

Secure build pipelines

Bake hardening and scanning into the pipeline that builds images and infrastructure, so security is automatic and tested.

Resources

Advanced

Network device hardening

Routers, switches and firewalls need hardening too: management access, secure protocols, logging and configuration backups.

Resources

Advanced

Securing administrative access

Admin access to infrastructure is the real prize. Use jump hosts, just-in-time access and separate admin accounts and workstations.

Resources

Advanced

Measuring coverage

Track how much of the estate meets the standard, where drift happens most and how long it takes to fix. Numbers drive improvement.

Resources

ExpertTime: 6–12 months

Strategy and leadership

Skills

  • Set secure configuration strategy for an organisation.
  • Govern standards and exceptions.

Hands-on projects and labs

  • Write a server hardening standard with profiles and an exception process.
  • Design an immutable backup and tested recovery scheme for a lab environment.

Done when you can…

  • Run a hardening programme with measured estate coverage.
  • Lead a major hardening or configuration-management rollout.

Expert

Standards and exceptions

Publish the standard, approve exceptions with end dates, and make the hardened path the easiest path for engineers.

Resources

Overview

Most breaches do not need a clever exploit; they need a server that was set up quickly and never locked down. Infrastructure hardening is the discipline of configuring servers, hypervisors, virtual desktops and storage securely from the start, and keeping them that way as they change.

The work mixes benchmarks and standards, automation to apply and enforce them, and monitoring to catch drift and tampering. It is quiet, high-value work: a well-hardened estate removes whole categories of attack before any detection is needed.

Why it matters

Misconfiguration is one of the most common root causes of breaches. Organisations need people who can turn benchmarks into a hardened, monitored reality across hundreds of systems.

Typical job roles

  • EntrySystem administrator Builds and maintains servers to a secure standard.
  • Mid-levelInfrastructure security engineer Creates and enforces hardened baselines across the estate.
  • Mid-levelVirtualisation security engineer Secures hypervisors, virtual desktops and the management plane.
  • SeniorSenior infrastructure security engineer Designs hardening and configuration management at scale.
  • LeadHead of infrastructure security Owns secure configuration strategy and standards.

Prerequisites

  • Solid Windows and Linux server administration.
  • Networking and how services talk to each other.
  • Scripting (PowerShell, Bash) and ideally a configuration tool.
  • The Endpoint and Operating System Security roadmap helps.

Foundations of computer science Cybersecurity

Tools and technologies

  • Ansible Open source Apply and enforce configuration as code.
  • OpenSCAP Open source Scan systems against security benchmarks.
  • Lynis Open source Security auditing and hardening for Linux.
  • CIS-CAT Pro Commercial Checks systems against CIS Benchmarks (a free Lite edition exists).
  • Packer Open source Build hardened machine images.
  • Wazuh Open source File integrity monitoring and compliance.

Certifications

Take them in roughly this order. Costs and details for the ones marked with a link are on the Certifications page.

  1. Entry Security+ CompTIAA common baseline.Cost and exam details
  2. Advanced Certified Kubernetes Administrator (CKA) Linux Foundation (CNCF)Infrastructure automation skills.Cost and exam details
  3. Intermediate GIAC Certified UNIX Security Administrator (GCUX) GIACUnix and Linux hardening (check current availability).

Resources

Frameworks and standards

  • CIS Benchmarks Free, consensus hardening guides for operating systems, cloud accounts, network devices and software.
  • CIS Critical Security Controls A prioritised list of 18 practical defences, grouped so smaller organisations know what to do first.
  • NIST Cybersecurity Framework (CSF) 2.0 A common way to describe and improve an organisation's security, organised as Govern, Identify, Protect, Detect, Respond and Recover.
  • NIST SP 800-53 Rev. 5 The large catalogue of security and privacy controls that many other frameworks map to.

All frameworks and standards

Career path

A common progression. Titles vary between companies.

  1. System administrator0–3 years
  2. Infrastructure security engineer3–6 years
  3. Senior infrastructure security engineer6–9 years
  4. Head of infrastructure security10+ years

Related domains to move into

All security roadmaps Back to top

Last reviewed: . Found a mistake, or want a roadmap written sooner? Contact