Security Engineering (IaC) Overview
A defender's reference for cloud and host infrastructure: what to deploy, what to review, and how to respond.
Cloud incidents are decided by what was set up before they started. Logs nobody can delete. Evidence that survives autoscaling. Keys that can be switched off. Guardrails that refuse the dangerous call. This site explains each one in plain language and ends every template with a check that proves the result. It gives working Terraform, Ansible, and Argo CD for four clouds, Kubernetes, and Linux, macOS, and Windows hosts. It is written for responders who advise the teams that build, and for engineers learning what responders need.
- 29 templateswith working code
- 13 platformsclouds, Kubernetes, hosts, GitHub, and identity services
- 185 alertsacross 11 platforms
- 18 responder lessonsfor cloud, container, and host incidents
- 273 levels Readychecked on every change and every week
Browse by platform
Each page lists everything here for one platform: its templates and their levels, its alerts, its incident response lessons, its refreshers, and the log planner.
Where to start
Evidence that survives autoscaling, containment on every cloud, Kubernetes attack paths, and what to ask the teams who build.
Every alert the templates create, by platform: what fires it, the log it reads, and how someone hears about it.
Plain explanations with diagrams and real output, written for someone who has never opened one of these files. About twenty minutes end to end.
Each one names the problem, what you need first, the part that catches people, and a command that proves the result.
Two planners. One lists every step of a Terraform pipeline for your tools. The other lists every log source your platforms need, and how long each is kept.
Every template
29 of the 29 templates listed here have working code. Each comes at three levels: Quick start to try, Standard to keep, and Hardened for audit. What each level includes.
Ready every check passed on the main branch Draft code exists, waiting for CI on the main branch Planned no code yet
| Template | Tool | Platforms | Levels Ready |
|---|---|---|---|
| A safe place to keep Terraform statePipeline and state | Terraform | AWS, Azure, Google Cloud, Oracle Cloud | All 12 |
| Evidence that survives terminationLogging and evidence | Terraform, Argo CD | AWS, Azure, Google Cloud, Oracle Cloud, Kubernetes | All 15 |
| Evidence from a compromised containerLogging and evidence | Terraform | AWS, Azure, Google Cloud, Oracle Cloud | All 12 |
| Audit logs nobody can deleteLogging and evidence | Terraform | AWS, Azure, Google Cloud, Oracle Cloud | All 12 |
| Lock SSH down to keys onlyHosts | Ansible | Linux, Windows | All six |
| Send host logs off the machineHosts | Ansible | Linux, Windows | All six |
| Record what investigations ask firstHosts | Ansible | Linux | All three |
| Ask every host the same questionsHosts | Ansible | Linux, macOS, Windows | All nine |
| Catch attackers at work on a serverHosts | Ansible | Linux | All three |
| Block the changes you never wantGuardrails and compliance | Terraform | AWS, Azure, Google Cloud, Oracle Cloud | All 12 |
| Check every resource against your rules, all the timeGuardrails and compliance | Terraform | AWS, Azure, Google Cloud, Oracle Cloud | All 12 |
| Get cloud logs into your SIEMLogging and evidence | Terraform | AWS, Azure, Google Cloud, Oracle Cloud | All 12 |
| Emergency access that works when login is brokenIdentity and access | Terraform | AWS, Azure, Google Cloud, Oracle Cloud | All 12 |
| Shell access without opening a portIdentity and access | Terraform | AWS, Azure, Google Cloud, Oracle Cloud | All 12 |
| Somewhere to keep secrets that rotates themIdentity and access | Terraform | AWS, Azure, Google Cloud, Oracle Cloud | All 12 |
| Encryption keys you control and can switch offIdentity and access | Terraform | AWS, Azure, Google Cloud, Oracle Cloud | All 12 |
| Keep network records long enough to be usefulLogging and evidence | Terraform | AWS, Azure, Google Cloud, Oracle Cloud | All 12 |
| Point Argo CD at a repositoryKubernetes | Argo CD | Kubernetes | All three |
| See what containers are doing while they runKubernetes | Argo CD | Kubernetes | All three |
| An analysis machine that cannot reach productionLogging and evidence | Terraform | AWS, Azure, Google Cloud, Oracle Cloud | All 12 |
| Cloud access for pipelines and pods without stored keysIdentity and access | Terraform | AWS, Azure, Google Cloud, Oracle Cloud | All 12 |
| Stop risky pods before they startKubernetes | Argo CD | Kubernetes | All three |
| A record of every action against the cluster APIKubernetes | Terraform | AWS, Azure, Google Cloud, Oracle Cloud | All 12 |
| Pipeline security findings in front of respondersPipeline and state | Terraform | GitHub | All three |
| Data that cannot leave your organisationGuardrails and compliance | Terraform | AWS, Azure, Google Cloud, Oracle Cloud | All 12 |
| Notice data walking out the doorDetection and response | Terraform | AWS, Azure, Google Cloud, Oracle Cloud | All 12 |
| Know who is using your AI modelsAI | Terraform | AWS, Azure, Google Cloud, Oracle Cloud | All 12 |
| Catch account takeover at the identity providerDetection and response | Terraform | Okta, Entra ID, Google Workspace, Microsoft 365 | All 12 |
| Encrypt and authorise every call between servicesKubernetes | Argo CD | Kubernetes | All three |
273 ready, zero draft, zero planned, out of 273 combinations of template, platform, and level. A platform with a level that is not Ready names that level.
Why the checks matter
Infrastructure code copied from the internet usually fails in one of two ways. It was written for an older version of the provider, or it never worked and nobody said so. Every template here runs through automatic checks on every change and again once a week, because providers change underneath code that nobody touched. What the checks look for.