iac.htora.dev · security templates

Home

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.

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

Responding to cloud incidents Cloud detection and response

Evidence that survives autoscaling, containment on every cloud, Kubernetes attack paths, and what to ask the teams who build.

Writing or tuning detections What alerts you get

Every alert the templates create, by platform: what fires it, the log it reads, and how someone hears about it.

New to Terraform, Ansible, or Argo CD Start with what the tools do

Plain explanations with diagrams and real output, written for someone who has never opened one of these files. About twenty minutes end to end.

Already use them Go straight to the templates

Each one names the problem, what you need first, the part that catches people, and a command that proves the result.

Planning for your own setup Plan your pipeline and your logs

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

TemplateToolPlatformsLevels Ready
A safe place to keep Terraform statePipeline and stateTerraformAWS, Azure, Google Cloud, Oracle CloudAll 12
Evidence that survives terminationLogging and evidenceTerraform, Argo CDAWS, Azure, Google Cloud, Oracle Cloud, KubernetesAll 15
Evidence from a compromised containerLogging and evidenceTerraformAWS, Azure, Google Cloud, Oracle CloudAll 12
Audit logs nobody can deleteLogging and evidenceTerraformAWS, Azure, Google Cloud, Oracle CloudAll 12
Lock SSH down to keys onlyHostsAnsibleLinux, WindowsAll six
Send host logs off the machineHostsAnsibleLinux, WindowsAll six
Record what investigations ask firstHostsAnsibleLinuxAll three
Ask every host the same questionsHostsAnsibleLinux, macOS, WindowsAll nine
Catch attackers at work on a serverHostsAnsibleLinuxAll three
Block the changes you never wantGuardrails and complianceTerraformAWS, Azure, Google Cloud, Oracle CloudAll 12
Check every resource against your rules, all the timeGuardrails and complianceTerraformAWS, Azure, Google Cloud, Oracle CloudAll 12
Get cloud logs into your SIEMLogging and evidenceTerraformAWS, Azure, Google Cloud, Oracle CloudAll 12
Emergency access that works when login is brokenIdentity and accessTerraformAWS, Azure, Google Cloud, Oracle CloudAll 12
Shell access without opening a portIdentity and accessTerraformAWS, Azure, Google Cloud, Oracle CloudAll 12
Somewhere to keep secrets that rotates themIdentity and accessTerraformAWS, Azure, Google Cloud, Oracle CloudAll 12
Encryption keys you control and can switch offIdentity and accessTerraformAWS, Azure, Google Cloud, Oracle CloudAll 12
Keep network records long enough to be usefulLogging and evidenceTerraformAWS, Azure, Google Cloud, Oracle CloudAll 12
Point Argo CD at a repositoryKubernetesArgo CDKubernetesAll three
See what containers are doing while they runKubernetesArgo CDKubernetesAll three
An analysis machine that cannot reach productionLogging and evidenceTerraformAWS, Azure, Google Cloud, Oracle CloudAll 12
Cloud access for pipelines and pods without stored keysIdentity and accessTerraformAWS, Azure, Google Cloud, Oracle CloudAll 12
Stop risky pods before they startKubernetesArgo CDKubernetesAll three
A record of every action against the cluster APIKubernetesTerraformAWS, Azure, Google Cloud, Oracle CloudAll 12
Pipeline security findings in front of respondersPipeline and stateTerraformGitHubAll three
Data that cannot leave your organisationGuardrails and complianceTerraformAWS, Azure, Google Cloud, Oracle CloudAll 12
Notice data walking out the doorDetection and responseTerraformAWS, Azure, Google Cloud, Oracle CloudAll 12
Know who is using your AI modelsAITerraformAWS, Azure, Google Cloud, Oracle CloudAll 12
Catch account takeover at the identity providerDetection and responseTerraformOkta, Entra ID, Google Workspace, Microsoft 365All 12
Encrypt and authorise every call between servicesKubernetesArgo CDKubernetesAll 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.

Registry 0.23.0. Built 2026-11-17.

Made by Habibullah Tora. Source on GitHub. Code under the MIT licence, writing under CC BY 4.0.