Overview
Access rules know addresses. The WAF knows requests, and only in proxy mode. Between them sits everything else Synapse knows about a client: its fingerprints, how its flows behave, and what the models and the IDS concluded.
The smart firewall is a wirefilter rule engine over all of it, evaluated by Amygdala on every agent. A match installs a block in the kernel, so enforcement costs a map lookup rather than a request.
When you see this
- A scanner or tool keeps changing its address.
- One source touches many ports or hosts in a short time.
- A detection should become a block automatically, without a ticket.
Steps
- 01
Pick the fields
The scheme carries 87 fields, all optional: fingerprints, flow behaviour, ML verdicts, IDS context, threat intelligence and Kubernetes identity. A rule that names a field nothing populates never matches, which is the usual reason a rule seems to do nothing.
- 02
Write the rule in log mode
A log rule records what it would have done and enforces nothing, so you can prove it on live traffic first.
Smart firewall rule, action log flow.unique_dst_ports ge 25 and flow.flows_per_min ge 100 - 03
Choose what a drop blocks
IP scope blocks the source address. IP and source port blocks that pair. Fingerprint scope blocks every connection presenting the fingerprint, whatever its address.
DecisionDo legitimate clients share the fingerprint?Yes Scope the drop to the address, or combine the fingerprint with an address condition.
No Fingerprint scope follows the tool across every address it uses.
- 04
Put your exceptions above it
The first matching rule wins, and if no rule matches the traffic is allowed. An allow placed below a broad drop never runs.
Smart firewall rule, action allow, placed above ip.src in {192.0.2.50/32} - 05
Promote it, then check the log
Switch the action to drop. Blocks carry a TTL and are swept when it expires, so a source seen once does not stay in a kernel map for ever. An expression that does not parse is skipped with a log line, not rejected, so check the agent log after shipping a rule.
- 06
Automate it
A SOAR playbook or your own automation can add a rule through the Signal API. The expression is validated when it arrives, and every agent receives the rule from the platform.
Signal API v2 curl -X POST https://api.gen0sec.com/v2/signal \ -H "Authorization: Bearer $GEN0SEC_API_KEY" \ -H "Content-Type: application/json" \ -d '[{"schema_version":2,"kind":"smart_firewall_rule","op":"upsert", "rule_ref":"sweep-198-51-100-66","expires_in":86400, "reason":"Port sweep","rule":{"name":"Port sweep","type":"custom", "expression":"ip.src in 198.51.100.66/32","action":"block"}}]'
Common mistakes
- Placing an allow below the drop it was meant to escape.
- Reading ids.severity as a magnitude. 1 is the most severe; prefer ids.score, where higher is worse.
- Dropping a common browser fingerprint at fingerprint scope, which blocks everyone on that browser.
Escalate when
- A rule that would block addresses in your own ranges.
- The same fingerprint dropped on many agents at once.
Where this stops working
- Only a ja4t rule stops the first connection. For every other match the first connection completes, and the source is blocked from then on.
- Rules come from the platform: an agent that cannot reach it keeps the ruleset it last received.
- Invalid expressions fail quietly, with a log line on the agent.