Playbooks

What to do when it actually happens.

Step-by-step playbooks for the attacks Gen0Sec is built to stop. Each one opens with the answer, walks through the steps with the rules and commands to use, says where the approach stops working, and ends in a lab where you run it: change the request or the rules and watch where it stops.

Playbooks
16
Steps
86
Rules, configs and commands
64

Every step is in the docs. The playbooks follow the use cases and feature pages on docs.gen0sec.com, so the rule you copy here is the rule the agent loads, and the limits are the ones the docs admit to. Where a playbook goes beyond the docs, it says so.

Detection and response (4)

Agent or proxy, on Linux

Act on a model verdict

When you want to catch what no signature or feed knows, turn on Cortex's models, watch what they flag, and act only when a model and a second signal agree. The probabilities are uncalibrated, so set your own threshold, and read the model card before a verdict decides a block.

6 steps · labCortexSmart firewall
Agent or proxyT1046

Turn detections into kernel blocks

When a client is known by how it behaves rather than where it comes from, write the rule over fingerprints, flow shape, model verdicts and IDS context. Prove it in log mode, put your exceptions above it, and promote it to drop. The block lands in the kernel, scoped to an address or to the fingerprint itself.

6 steps · labSmart firewallHillock
Agent or proxyT1190

Detect known exploits with Suricata rules

When the security community already has a signature for an attack, run it on the host. Thalamus loads Suricata-compatible rules unchanged, across thirty-plus protocols. Tell it what your network is, read the alerts as EVE JSON, and decide what a hit does: alert only, ban the source with ids.enforce_block, or act on it in a smart firewall rule.

6 steps · labThalamusSmart firewall
Agent or proxy

Block what the fleet already saw

When an address one of your agents banned reaches another, let the fleet's evidence count. Each agent reports what it blocked; the platform corroborates across the deployment, and every agent pulls the set back. Run it advisory first, read the numbers, then enforce where they hold up.

6 steps · labFleet bansHillock

Applications (4)

Proxy

Block malware in uploads

When users upload files into your service, scan what they send before it reaches storage or a worker. Arm ClamAV, aim it with a WAF rule at the upload paths only, decide what happens to files you cannot scan, and alert when the scanner fails, because it fails open.

5 steps · labWAFContent scanning
ProxyT1190

Protect an app before the patch lands

When a flaw in your stack is being exploited and the fix is not deployed, because the vendor has not shipped it or you cannot roll it out this week, move the boundary in front of the app. Put Synapse in proxy mode in front of the unchanged app, write a WAF rule for the exact request shape that reaches the flaw, order your exceptions above it, and make the proxy the only way in.

5 steps · labWAFFirewall rules
ProxyT1190Not in the docs yet

Compile rules from your own code

When hand-written rules no longer match what the application serves, take the rules from the application itself. Microglia reads its routes, parameter types, auth boundaries and egress, and compiles positive WAF, IDS and firewall rules from them. Review the surface, put your exceptions above the compiled rules, and let the rules ship with the code.

6 steps · labMicrogliaWAFIDSFirewall rules
Proxy, as the ingress controllerT1190

Protect Kubernetes services at the ingress

When your services already sit behind Ingress objects, make Synapse the ingress controller. The operator turns Ingress and Gateway API resources into Synapse's routes and hot-reloads them; the smart firewall, WAF and IDS then run on the same path as every route, with no sidecar and no second hop.

5 steps · labSynapse OperatorWAFIDS

Read it, then run it.

Every playbook ends in a lab: the same request, the same rules, evaluated in your browser. A demo does it on your own traffic.