Scanner and virtual patching are the path from a flaw in the application to a block that does not require a code change. Scanner is on the Enterprise plan.
A classic scan starts from scan_schedule. Scanner collects links on each active target and checks them with the scanning modules. Findings are sent to API and listed by get_vulns. An empty schedule means the classic scan is not started. The behavior is in Scanning.
Recheck asks whether an event already recorded by Mikiri WAF can be reproduced. It stays enabled, does not use scan_schedule and can run while a classic scan is running. Events are placed in the queue by set_recheck. get_recheck_status returns true when the vulnerability is confirmed and false when it is not. The description is Recheck.
Virtual patching blocks attempts to exploit a known vulnerability without changing the application. A patch is a request processing rule, created in WMC or through the API, or generated by the Mikiri AI module. The description is Virtual patching. The rule fields are Request processing rules.
Run recheck again for the same event. A request that matches the new rule is blocked by Filter and does not reach the vulnerable behavior. The test signature mikiri-waf-test remains the separate check that signature blocking itself is on: A test request is not blocked.