I
On premises
The protection components run in your infrastructure. Your team inspects traffic, keeps the event record and decides what is blocked.
Why Mikiri
Run traffic inspection and event storage in your infrastructure. Your team sees each security decision and can change it.
I
The protection components run in your infrastructure. Your team inspects traffic, keeps the event record and decides what is blocked.
II
Combine the checks available in the selected product and enabled for the host: request signatures, OpenAPI validation on Mikiri API Firewall and Mikiri WAAP, and a model of the application's own traffic on Mikiri WAF and Mikiri WAAP. Detection modes and exclusions control whether a match blocks the request.
III
Investigate recorded attacks in WMC and through the API, using the blocking type and the detection details. The zone, rule or reason available depends on the mechanism that detected the event.
Fit
Evaluate Mikiri when traffic inspection must stay inside your infrastructure. Your team runs the components and decides what is blocked.
If the rule set you already run meets the need, replacing it needs a measurable benefit. Evaluate whether Mikiri's console, API, behavioral models and shared cluster settings reduce the work of investigating events and maintaining protection. Replay the same test cases and compare false positives and operator effort.
Keep authentication, routing and application authorization in their existing layers. Evaluate Mikiri API Firewall or Mikiri WAAP for OpenAPI contract validation; check for overlap with validation your gateway already provides. Mikiri WAF does not include the API firewall.
Mikiri WAAP adds response inspection and blocking, plus an integrated vulnerability scanner and attack verification. Evaluate those capabilities against your current scanner and response controls. Response blocking can contain recognized data leaks; it does not undo a compromise or replace remediation.
See a two-node license example
Detection
Known attack patterns from the shared request signature set in the path, query, body, cookies and headers. The request is decoded before it is checked, including repeated URL encoding, base64 and UTF-16. On Mikiri API Firewall, this set runs only for virtual hosts that have a loaded OpenAPI specification.
Exampleid=1 union select null from users in the query is blocked as SQL injection.
Requests are validated against the OpenAPI specification of the application. Specifications in other formats are converted to OpenAPI 3.1.
ExampleWith blocking enabled, a call with the wrong method or parameter type is blocked. An unknown path passes the contract check by default; the host's Block paths not defined by this specification option can block it.
Inventory distinguishes Discovered (an autogenerated path matching a specification path), Shadow (a path seen in traffic on a host with a loaded specification but absent from that specification), and Rogue (an autogenerated path on a host without a loaded specification).
One model per protected virtual host, trained on that host's own traffic and applied on every filtering node of the cluster. Requests that no signature blocked are compared with it.
ExampleA parameter value that this application never receives is blocked, although it matches no signature.
On Mikiri WAF and Mikiri WAAP, MLC analyzes traffic from the filtering nodes for brute force, flood, application-layer DDoS and web scraping. Enable and configure the analysis for your hosts and URLs.
ExampleA brute-force rule counts matching sign-in requests within its analysis interval; it does not determine whether a login succeeded. Configure the host's Rate limit of blocked requests to enable temporary address blocking on detection, subject to detection-mode settings. CAPTCHA unblocking can be configured for visitors.
The client is checked with JavaScript in the browser. A passed check is shared by every filtering node in the cluster and stays valid for 24 hours.
ExampleA scraper built on an HTTP library that cannot run JavaScript gets the check page instead of the content.
A request processing rule that blocks exploitation of a known vulnerability, or limits access by path, User-Agent and similar, without changing the application. Rules are created manually in WMC and through the API on every product, including Mikiri API Firewall. On Mikiri WAF and Mikiri WAAP, they can also be created automatically by the Mikiri AI module.
ExampleSee how the PHP-CGI soft hyphen is blocked.
Scope
Mikiri WAF blocks attacks of these classes that are visible in HTTP traffic, such as injection, path traversal and server-side request forgery. Flaws in design or access control logic are made harder to exploit, but the lasting fix is in the application.
On Mikiri WAF and Mikiri WAAP, configured traffic analysis can detect HTTP-level floods and DDoS. The host's Rate limit of blocked requests enables temporary address blocking, subject to detection-mode settings. Volumetric network attacks need upstream capacity and a separate network-layer mitigation service.
The license sets no limit on traffic volume or request rate. Throughput depends on the hardware of each filtering node and on the traffic profile. Sizing guidance is in the documentation.
Added latency depends on the hardware, the methods enabled and the traffic. Measure it on your own traffic during the evaluation.
Products
Mikiri API Firewall
API protection only — OpenAPI contract enforcement, with request signatures on hosts that have a specification.
API firewall, request signatures on hosts with a specification, request processing rules, OpenAPI upload, autogeneration and Shadow API.
Mikiri WAF
Web application protection only — signatures, machine learning and bot protection.
Signatures, behavioral models, bot protection and virtual patching, with host and URL settings controlling which checks apply. OpenAPI contract enforcement is available on Mikiri API Firewall and Mikiri WAAP.
Mikiri WAAP
Enterprise web application and API protection — API firewall, response analysis, the vulnerability scanner and more.
Everything in Mikiri API Firewall and Mikiri WAF, plus response inspection, the integrated scanner with attack verification, CSP, and request and traffic statistics.
| Capability | Mikiri API Firewall | Mikiri WAF | Mikiri WAAP |
|---|---|---|---|
| Platform | |||
| On-premises deployment | Included | Included | Included |
| No license limit on traffic volume or request rate | Included | Included | Included |
| IP geolocation database and threat intelligence feed | Included | Included | Included |
| Linux packages, Docker images and Kubernetes manifests | Included | Included | Included |
| Deployment and scaling | |||
| Reverse-proxy mode | Included | Included | Included |
| Active-active and active-passive clustering | Included | Included | Included |
| Fault-tolerant component operation | Included | Included | Included |
| Multi-node deployment | Included | Included | Included |
| Multi-tenancy | Included | Included | Included |
| Canary rollout of settings across server groups | Included | Included | Included |
| Attack detection | |||
| API firewall | Included | — | Included |
| Per-endpoint API request quotas | Included | — | Included |
| OpenAPI upload, autogeneration and Shadow API | Included | — | Included |
| Request signatures / OWASP-class threats | On hosts with a specification | Included | Included |
| Machine-learning analysis | — | Included | Included |
| Detection of unknown attacks by the behavioral model | — | Included | Included |
| Malicious bot protection | — | Included | Included |
| Anti-bot mode with intelligent client verification | — | Included | Included |
| Web scraping protection | — | Included | Included |
| Client behavior analysis | — | Included | Included |
| Brute-force, flood and L7 DDoS analysis | — | Included | Included |
| Basic rate limits on Filter | Included | Included | Included |
| Request processing rules / manual virtual patching | Included | Included | Included |
| Virtual patches created by the Mikiri AI module | — | Included | Included |
| Retrospective traffic analysis | — | Included | Included |
| Request inspection | |||
| HTTP/1.1, HTTP/2, and HTTP/3 | Included | Included | Included |
| WebSocket, gRPC, REST, and SOAP over HTTP | Included | Included | Included |
| HTML5, JSON, XML, GraphQL, and multipart/form-data | Included | Included | Included |
| Request blocking based on attack indicators | Included | Included | Included |
| RFC compliance checks | Included | Included | Included |
| Multi-stage normalization and deep inspection | Included | Included | Included |
| Hardware-accelerated SSL/TLS termination | Included | Included | Included |
| Integrations | |||
| Third-party threat intelligence feeds | Included | Included | Included |
| Third-party anti-DDoS services | — | Included | Included |
| Third-party antivirus via ICAP | Included | Included | Included |
| Any CAPTCHA provider | — | Included | Included |
| Additional capabilities | |||
| Detailed IP address intelligence | Included | Included | Included |
| Customizable block page | Included | Included | Included |
| Data masking | Included | Included | Included |
| Vulnerability detection and attack verification with the built-in scanner | — | — | Included |
| Request statistics: response codes, block types, cache hits, allow and deny lists | — | — | Included |
| Inbound and outbound traffic statistics | — | — | Included |
| Logs and events | |||
| Centralized collection of attacks and anomalies | Included | Included | Included |
| Attack and anomaly data via the console and API | Included | Included | Included |
| Component logs via the console and API | Included | Included | Included |
| Event forwarding to third-party systems | Included | Included | Included |
| Server resource status via the console and API | Included | Included | Included |
| Response inspection | |||
| HTTP/1.1, HTTP/2, and HTTP/3 | — | — | Included |
| WebSocket, gRPC, REST, and SOAP over HTTP | — | — | Included |
| HTML5, JSON, XML, and multipart/form-data | — | — | Included |
| Response blocking based on attack indicators | — | — | Included |
| Block attacker access to a compromised application | — | — | Included |
Deploy Mikiri on premises and evaluate it in your own environment. Evaluation is free, and application traffic stays on premises.