Home/Templates/All templates
All templates
Every template on the site, named after what you end up with and grouped by the job it does.
To see only the templates for one platform, pick it here.
Logging and evidence
One tag or label keeps a machine alive, captures its disks and, on AWS, its memory, and cuts it off, in that order, on four clouds and Kubernetes.
One script keeps a pod's node alive, records the pod, snapshots the node's disks, and cuts the pod off, on GKE, EKS, AKS, or OKE.
Send cloud audit logs to storage that refuses deletes for a set number of days.
A delivery pipe from cloud logging to the place your detections actually run.
Traffic records stored cheaply for months, in a format you can query.
A clean-room virtual machine for looking at suspicious files, with no route to anything live, on four clouds.
Identity and access
A separate account that does not depend on your identity provider, and shouts every time it is used.
Reach a server for troubleshooting with nothing listening on the internet, and a recording of the session.
A managed store with scheduled rotation, a record of every read, and a way to take access away.
Your own keys, rotated on a schedule, with a usage log and an off switch.
Pipelines and pods prove who they are with short-lived tokens, so there is no cloud key to leak.
Guardrails and compliance
Policies that make dangerous actions fail outright, so there is nothing to alert on afterwards.
Continuous evaluation that flags a resource the moment it stops matching the standard.
Perimeter policies so stolen credentials cannot copy data to an attacker's own account or project.
Hosts
Turn off password logins and root logins, and check the config before restarting so you cannot lock yourself out.
Forward system logs to a collector so they outlive the machine that wrote them.
auditd rules on Linux for account changes, sudo rights, SSH keys, persistence, kernel modules, and commands people ran as root.
osquery on Linux, macOS, and Windows, logging changes to accounts, keys, persistence, listening ports, and drivers.
Falco on plain Linux hosts, alerting on web shells, credential theft, and new programs in system folders.
Kubernetes
The first Application, which then manages every other application from Git.
Runtime alerts installed by the same pipeline that ships the workloads, so they cannot fall behind.
Admission policies refuse privileged pods, host mounts, and unsigned images, and report every refusal.
Cluster audit logs sent where responders can search them, so exec into a pod or a new role binding is never invisible.
Mutual TLS between every service, and a deny-by-default rule for which service may call which.
Detection and response
Alerts on the moves someone makes on the way out with data: sharing it outside, reading far more than usual, changing who can decrypt it, and quieting the logs.
Alerts in Okta, Entra ID, Google Workspace, and Microsoft 365 on the moves that turn one stolen account into many. They cover admin rights granted, sign-in rules changed, MFA removed, mail forwarded out, and a log feed going quiet.
AI
Model call records on Bedrock, Vertex AI, Azure OpenAI, and OCI Generative AI, with alerts when logging or guardrails are turned off, or stolen keys go looking for models.
Pipeline and state
The state file contains secrets in plain text. This stores it encrypted, versioned, and locked while a run is in progress.
Secret scanning, push protection, and dependency alerts switched on and sent to the SIEM, so a leaked key is an incident.