Observe before blocking
A new site starts in detection mode: everything is inspected and recorded, nothing is blocked. A report shows what would have been refused before you switch to blocking.
Rules and WAF protection
Readable detectors and rules, an anomaly score, modes per site, per rule and per path, narrow exceptions, virtual patches and a progressive rollout. You observe first, block later, and can always go back.
Where to find it in the console : Protection menu: Rules, Exceptions and Policies; Analysis menu: False positives; the Protection tab of a site.
What it is for
Decisions that explain themselves
Each event says which rule reacted, where (parameter, header, body), with which score and which action. No black box: you can replay a request and see the decision.
Fix a false positive without weakening the site
An exception targets one rule, one parameter, one path and one address, with an expiry date. The rest of the protection does not change.
Change the rules without taking a risk
Simulation on past traffic, rollout to a share of the nodes or of the requests, comparable versions and rollback in one step.
How ToutWAF decides
Every request goes through the same steps. The result is a decision, recorded with its evidence.
Detectors and rules
The built-in detectors (injections, deserialization, request smuggling, uploads, protocol), the OWASP CRS and your own rules look at the request. The catalogue documents more than 300 TW- error codes.
An anomaly score
Each detection adds points according to its severity: 5 for critical, 4 for error, 3 for warning, 2 for notice. The default inbound threshold is 5: one critical detection blocks, two warnings (3 + 3) block, a single warning is only logged.
The mode decides the action
Off, detection or blocking, depending on the site, the rule, the path and the method. Some rules act on their own without going through the score, for example a fake Googlebot or an unsigned JWT.
Three modes, at every level
Gratuito
The mode is set for the whole site, but also for one rule, a family of rules, a path or a method. A rule can also change its action: log, challenge, slow down, decoy, block or redirect.
- A new site is in detection: events carry the action that would have been taken, without it being applied.
- Paranoia levels from 1 to 4 (1 by default), per site or per path. You go up one level at a time, in detection, and read the report before blocking.
- A percentage of the requests can enforce blocking (ENFORCE_PERCENT): a canary at request level.
- If the engine fails or exceeds its time budget, the site chooses to let requests through or to refuse them (per site). Choose refuse for a payment, let through for a brochure site.
OWASP CRS and SecLang
Gratuito
The OWASP Core Rule Set v4 is evaluated by ToutWAF's own SecLang parser and evaluator, with the plug-ins that match the technology detected on your site.
- The definitions catalogue holds about 85 sources, checked every hour, verified before use and rolled back if they fail.
- Starting templates: generic, WordPress, Laravel, Symfony, Django, Spring, Node and single-page application.
- You can target a CRS identifier or a range (for example 942100-942999) in a mode or an exception.
The complete CRS v4 was only tested on a reduced fixture.
Your own rules
Gratuito
A readable condition language, with a visual editor and a text editor that stay in sync.
- Rule tester: replay a request against the current policy and see the decision.
- Dry run on real traffic: the rule is replayed on seven days of recorded requests, without enforcing anything.
- Rule tests that run in continuous integration, with JUnit output.
The console validator and the engine accept slightly different subsets of the language: always verify a rule with a test.
Narrow exceptions and rule overrides
Gratuito
When a rule reacts wrongly, you work around it as narrowly as possible instead of switching it off.
- An exception covers one rule, one parameter (argument, header, cookie, JSON field or body), a path prefix and an address, with an expiry and a reason.
- From an event, the button « This is a false positive » proposes the narrowest exception and shows its effect on the recorded events before creating it.
- ToutWAF also suggests exceptions from the traffic: you accept or dismiss them.
- A rule override changes the mode or action of a rule, a tag or a family, for a path and methods. Every change is versioned, compared and audited.
Example of rule overrides, in the policy of a site
YAML
rule_overrides:
- { rule: tw-sqli-orderby-probe, mode: detect }
- { rule: "tag:attack-xss", mode: block, path_prefix: /checkout }
- { rule: "family:4xxx", action: challenge, methods: [POST] }A policy that is inherited
Gratuito
Settings go from general to specific: global, then per organisation, per site and per path. The more specific one wins.
- Every change is a version: structured difference, history and rollback in one step.
- Four-eyes approval: a second reviewer approves a version before it goes live.
- Policy as code: export, validate, compare and apply YAML or JSON from your continuous integration.
Put a rule live without risk
The recommended path is: observe, review, simulate, switch, watch, and keep the rollback ready.
Draft
You change the policy in a draft; nothing is published.
Simulation
The policy is replayed on past traffic: requests that would be newly blocked or allowed.
Canary
A share of the nodes, a share of the requests or a single rule; you watch, then extend.
Publication and rollback
Publication is automatic and fast; if a node refuses the policy, it goes back to the last accepted version.
Virtual patches
Gratuito
A known vulnerability is blocked at the WAF while the application waits for its fix.
- A built-in catalogue covers Log4Shell, Spring4Shell and Confluence flaws, among others, and can be switched on per site.
- Emerging Threats Open signatures are converted only when the translation is exact; they log by default.
- CISA KEV advisories are informational until a verified pattern exists: they block nothing.
Automatic rules
GratuitoPro e superiori
ToutWAF settles its false positives and moves from observation to blocking, with evidence you audit and undo.
- Free: the self-test of a site, the false-positive estimate per rule group, the « Ready to block » indicator and the decisions journal.
- Licence required: the Automatic profile (log, challenge, then block one rule group at a time) and the automatic exceptions, narrow and time-limited.
- Guardrails: only protocol and web-injection rules can be worked around automatically, never by switching the rule off, and everything can be undone in one click.
What is not done, or not proven
We prefer to say it plainly.
- Loading the complete CRS v4 was only tested on a reduced fixture.
- Automatic rules were exercised by tests and a local bench, not on production traffic.
- The only detection and performance figures published are in the documentation: they come from the project's own synthetic corpus, are not independent measurements and do not rank ToutWAF against any other product. This page gives none.
- A WAF reduces risk, it does not replace fixing the application: keep your code's updates and access controls.
Use cases
Take a shop live without interruption
A week of detection, the report suggests a few narrow exceptions, you switch to blocking and keep the rollback ready.
React to a known vulnerability
A virtual patch blocks the exploit while the application waits for its update.
A rich-text editor triggers a rule
An exception limited to this field, this path and thirty days settles the case without touching the rest.
What is included, by edition
The basics are free; the advanced options need a paid offer. An option under licence stays visible in the console, locked, never hidden.
EdizioneGratuito Incluso in tutte le offerte, comprese le due gratuite (Free e Free +)Pro e superiori Offerte a pagamento: visibile nella console, bloccata senza licenza. Da Pro, salvo indicazione Agency o Enterprise
Protezione delle applicazioni
- SQL injection riconosciuta dalla struttura dei token e non da elenchi di parole chiave, per cinque dialettiGratuito
- NoSQL injection: operatori e JavaScript lato server in query, moduli e corpi JSONGratuito
- Cross-site scripting: tokenizer HTML con rilevatori di contesto, SVG, sink DOM e poliglottiGratuito
- Command injection ed esecuzione di codice: shell, PowerShell, interpreti e valutazione di linguaggiGratuito
- Inclusione di file e path traversal, con decodifica a più passaggi delle codificheGratuito
- SSRF: richieste verso indirizzi interni, metadati del cloud o schemi esoticiGratuito
- XXE ed espansione di entità XML, injection XPathGratuito
- Template injection: Jinja2, Twig, Freemarker, Velocity, ThymeleafGratuito
- Deserializzazione non sicura: Java, PHP, .NET, Python, YAMLGratuito
- LDAP, linguaggi di espressione (OGNL, SpEL), CRLF, open redirect e prototype pollutionGratuito
- HTTP request smuggling, framing rigoroso RFC 9112 e limiti contro gli abusi di HTTP/2Gratuito
- Un corpo più grande della finestra di ispezione viene rifiutato o segnalato, mai inoltrato senza essere stato vistoGratuito
- Upload di file: estensione, doppia estensione, magic bytes, webshell, macro, scansione ClamAV facoltativaGratuito
- Protezione dei CMS: WordPress, Drupal, Joomla, PrestaShop, Magento, NextcloudGratuito
- Scanner e strumenti offensivi (sqlmap, Nikto, Nuclei, Burp) ed enumerazione tramite raffiche di 404Gratuito
- CSRF: controllo di Origin e Referer, iniezione di un token nei moduliGratuito
- Protezione delle sessioni: fixation, hijacking, cifratura dei cookieGratuito
- Parsing limitato: limiti di profondità, dimensione e numero di parametri, espressioni regolari a tempo lineareGratuito
Regole, policy e rollout
- OWASP CRS v4 caricato così com'è, con il parser e l'evaluatore SecLang propri di ToutWAFGratuito
- Livelli di paranoia da 1 a 4, per sito o per percorsoGratuito
- Punteggio di anomalia con soglie in ingresso e in uscitaGratuito
- Modalità disattivato, rilevamento o blocco per sito, per regola e per percorso, con sostituzione dell'azioneGratuito
- Linguaggio di regole leggibile per scrivere le tue regoleGratuito
- Eccezioni granulari per regola, parametro, percorso e indirizzo, con scadenza e anteprima dell'impattoGratuito
- Patch virtuali per vulnerabilità note (Log4Shell, Spring4Shell, Confluence e altre), attivabili per sitoGratuito
- Falsi positivi: dall'evento all'eccezione più stretta con un clic, con spiegazione in linguaggio chiaroGratuito
- Simulazione: riprodurre il traffico passato contro una policy in bozzaGratuito
- Rapporto di rilevamento al termine del periodo di osservazione, con le eccezioni proposteGratuito
- Rollout progressivo: una parte dei nodi, una parte delle richieste o una sola regolaGratuito
- Ereditarietà della policy: globale, organizzazione, sito, percorsoGratuito
- Modelli: generico, WordPress, Laravel, Symfony, Django, Spring, Node, applicazione a pagina singolaGratuito
- Versioni, differenza strutturata e rollback in un passaggioGratuito
- Approvazione a quattro occhi prima della messa in produzione di una versioneGratuito
- Policy come codice: esportare, convalidare, confrontare e applicare YAML o JSON dalla CIGratuito
- Test delle regole eseguibili in CI, con output JUnitGratuito
- Pubblicazione automatica: ogni modifica viene compilata, convalidata e inviata ai nodi in pochi secondi, con rollback automatico se un nodo la rifiutaGratuito
Regole automatiche
- Autotest del sito: richieste ordinarie valutate dal tuo data plane prima di bloccare qualsiasi cosaGratuito
- Tasso stimato di falsi positivi per gruppo di regole e indicatore «Pronto a bloccare»Gratuito
- Plug-in CRS per la tecnologia rilevata sul tuo sitoGratuito
- Registro delle decisioni automatiche con le prove e annullamento con un clicGratuito
- Profilo Automatico: solo registrazione, poi sfida, poi blocco, un gruppo di regole alla voltaPro e superiori
- Eccezioni automatiche: strette, a scadenza, create solo da prove solide nel traffico realePro e superiori
- Rollback automatico di un aggiornamento di regole che blocca richieste ordinariePro e superiori
Tornare al valore predefinito di un'opzione avanzata è sempre possibile. Che cosa accade alla fine di una licenza a pagamento è descritto nelle domande frequenti sui prezzi: 48 ore di tolleranza, 48 ore di sola lettura, poi la protezione WAF viene disattivata fino al rinnovo.
Metti oggi stesso uno scudo davanti alle tue applicazioni
Installalo sul tuo server, oppure scrivici per parlare di licenze.