iac.htora.dev · security templates

Home/By platform/Everything for Azure

Everything for Azure

Every template, lesson, refresher, and planner on this site that applies to Azure, in one place.

The list includes Entra ID and Microsoft 365, which use the same sign-in and logging services.

To compare the four clouds with each other, service by service, read The four clouds side by side.

Alerts

The templates below create 70 alerts for Azure. Each link opens the alerts table filtered to one platform, with what fires each alert, the log it reads, and how someone hears.

Standard and Hardened also install 30 saved queries for working a case. The incident response lesson lists them, with the template that installs each one.

Templates

19 templates have code for Azure, written for Terraform. All 60 levels are Ready. What each level includes.

TemplatePlatformQuick startStandardHardenedRefresher
Evidence that survives terminationLogging and evidenceAzureReadyReadyReadyOne page
Evidence from a compromised containerLogging and evidenceAzureReadyReadyReadyOne page
Audit logs nobody can deleteLogging and evidenceAzureReadyReadyReadyOne page
Get cloud logs into your SIEMLogging and evidenceAzureReadyReadyReadyOne page
Keep network records long enough to be usefulLogging and evidenceAzureReadyReadyReadyOne page
An analysis machine that cannot reach productionLogging and evidenceAzureReadyReadyReadyOne page
Emergency access that works when login is brokenIdentity and accessAzureReadyReadyReadyOne page
Shell access without opening a portIdentity and accessAzureReadyReadyReadyOne page
Somewhere to keep secrets that rotates themIdentity and accessAzureReadyReadyReadyOne page
Encryption keys you control and can switch offIdentity and accessAzureReadyReadyReadyOne page
Cloud access for pipelines and pods without stored keysIdentity and accessAzureReadyReadyReadyOne page
Block the changes you never wantGuardrails and complianceAzureReadyReadyReadyOne page
Check every resource against your rules, all the timeGuardrails and complianceAzureReadyReadyReadyOne page
Data that cannot leave your organisationGuardrails and complianceAzureReadyReadyReadyOne page
A record of every action against the cluster APIKubernetesAzureReadyReadyReadyOne page
Notice data walking out the doorDetection and responseAzureReadyReadyReadyOne page
Catch account takeover at the identity providerDetection and responseEntra IDReadyReadyReadyOne page
Catch account takeover at the identity providerDetection and responseMicrosoft 365ReadyReadyReadyOne page
Know who is using your AI modelsAIAzureReadyReadyReadyOne page
A safe place to keep Terraform statePipeline and stateAzureReadyReadyReadyOne page

Incident response

The lessons to read before an incident on Azure, the most specific first, and to keep open during one.

Incident response on Azure

Activity Log and Entra log defaults, reading callers and sign-ins, containment, VM forensics, and Defender.

Leading a cloud incident

Phases, scoping, containment per cloud, preserving evidence, incident command, and reviews.

Containers on AKS and OKE

Audit logs, pod and node identities, disks, and managed modes on AKS and OKE, and how to respond on each.

Stolen credentials running AI models

One LLMjacking case from alert to containment, the record each cloud keeps, the saved queries, and how to size the bill and the data exposure.

Running a cloud incident as an organisation

Roles adapted from the Incident Command System, the first hour and operational periods, decision records, disclosure clocks, NIST SP 800-61r3, and a maturity ladder.

One-page refreshers

Each prints on one page. Every template in the table above links its own.

Incident response on Azure

What Azure records by default, how to read a caller or a sign-in, and the first moves for each kind of compromise.

Leading a cloud incident: the first hour

The same phases as any incident, with evidence that disappears faster, more ways for an attacker to come back, and most actions taken through APIs.

Containment by what was compromised

The fastest safe way to cut an attacker off, by what they have, and what each move leaves open.

Containers on AKS and OKE

What each service records about a cluster, what a pod can reach on its node, and how to keep the node's disks.

Incident command: roles and rhythm

Five roles adapted from the Incident Command System, the rhythm they work to, and how they pass from one person to a team.

The four clouds

AWS, Azure, Google Cloud, and Oracle Cloud share the same building blocks under different names.

Terraform and OpenTofu

A tool that creates and changes cloud resources to match .tf files. OpenTofu is its open-source fork, and takes the same files with tofu in place of terraform.

Log planning

The log source planner lists every log source to turn on, how long each is kept by default, and what it costs. This link opens it set to Azure, AKS, Entra ID, and Microsoft 365.

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.