Reactive last line of defense

The reflex your security
stack is missing.

Every attack, however clever, eventually has to burn CPU, fill a disk, or move bytes out. Cordon watches for exactly that — and contains it in seconds.

Linux & Kubernetes · single-file agent · deploys on Railway
The idea

You can't predict the next attack. You can predict its physics.

Cordon is a reflex, not a brain. It doesn't out-think the attacker at the door — it assumes the door is already open, and reads the one thing no attacker can hide: the load they put on real hardware.

Ransomware
Disk I/O storm · file entropy ≈ 8.0
Cryptojacking
CPU pinned, sustained
Data exfiltration
Anomalous egress to a rare host
Fork bomb
Process count explodes
Reverse shell
New listener · C2 beacon
Log tampering
The record itself is truncated
How it works

Watch. Cordon. Get a human.

Watch, locally, always

A dependency-free agent snapshots CPU, memory, disk, I/O, processes and network every few seconds — plus file entropy, auth failures and kernel surface — and evaluates your thresholds on the box itself.

Containment never waits on a round-trip.

Cordon off the threat

On red, reversible containment fires automatically: snapshot the evidence, freeze the process, sever its network, lock the data it's rewriting, and camouflage your crown jewels behind decoys.

Nothing destroyed — every step is reversible.

Get a human. Record everything.

Killing a process or taking a box down is held for a one-click approval down your escalation path. Every signal and action lands in a hash-chained, off-host black box.

Tampering is detectable — even from inside the DB.
The platform

A control plane for the whole fleet.

Live defense panel

One color-coded screen — green calm, amber stress, red under attack. Watch a metric spike and the containment ladder drop it back down in real time.

Attack simulator

Rehearse the real thing without risk. Six scenarios drive the real engine — real incident, real audit, exact commands — and nothing is actually killed.

Scripts → Hosts

Author a protection script once; drop its installer on any number of servers. Each one self-registers, reporting hostname, IP, OS and kernel.

Roles & escalation

Company → teams → members. Only responders and up can approve. Incidents climb an escalation path until someone acknowledges.

Tamper-evident black box

Append-only, hash-chained, off-host. Verify integrity in one click — because the first thing a real attacker does is erase the logs.

Learns your normal

Static thresholds out of the box; switch on learned baselines to catch the low-and-slow — and it refuses to be taught the attack.

Coverage

Every attack maps to a signature and a response.

Cordon meets each one where it lands — on the hardware — with a playbook of reversible moves and a gated last resort.

Attack
Resource signature
Response
Ransomware
Disk-I/O storm + entropy jump + mass rewrites
freeze → lock → camouflage → hold kill
Database exfiltration
Bulk row egress to an external client
cut egress → terminate session → hold disable-role
Cryptojacking
CPU pinned, sustained; miner beacon
freeze → sever → hold kill
Reverse shell / C2
New listener; web process spawns a shell
sever C2 → freeze → hold kill
Log tampering
The agent's own record is truncated
escalate directly — treated as an attack
Why it's different

Detection notices. Cordon acts.

✓

Reversible first, destructive only with a human

A false positive costs you a frozen process, not an outage.

✓

Survives the machine it protects

Local evaluation works when the network is cut; the record lives off-host.

✓

Always reaches you

If the control plane goes dark — which may be the attack — the agent alerts a human directly.

✓

Camouflage, not just alarms

Hide what the attacker came for, and turn their next move into a tripwire.

✓

Deploys in a minute

One script per server, or a DaemonSet for your cluster.

✓

Explainable by design

Static thresholds you can read, and exact commands in every log line.

The promise
You'll get breached someday. Cordon decides what it costs.

Four minutes of encryption, or four seconds and a frozen process. A quiet overnight miner, or a page at 2:03 a.m. with the offender already contained. A cover-up, or a signed, unbroken record of exactly what happened.