ShieldProbe Defend / in-app protection
Protect while you fix.
Virtual patching stops a proven exploit while the code fix is still on its way. Defend does it inside your app: when ShieldProbe proves an exploit in a supported finding, Defend turns the approved finding into a targeted rule. Rules start in log-only mode. Your team decides when one blocks.
Log-only is the default. Switch to Enforce to see the block.
GET /search?q=<script>…In-process middleware, inside your application.
Logged, not blocked
The SDK records the match. Log-only mode allows the request to continue.
Rules start in log-only mode. Check the rule against normal traffic, then turn on blocking.
Illustrative rule for SP-015
- Rule
- /search, q parameter
- Action
- Block
- State
- Staged, then Enforced by your team
Which findings can Defend cover?
Can be blocked
A proven exploit with a specific endpoint and request pattern, such as the SP-015 script payload on /search. A rule can allow, block, add a response header, or rewrite or mask the response.
Logged only, fixed in code
Findings a request rule cannot decide, such as whether a user owns an order (SP-014), or attacks that need state the middleware does not have. Rules cannot read sessions or the database.
Rules are generated from the finding, and a consultant approves the finding before its rule reaches your app. You don't write rules by hand.
You control the rollout.
Observe first.
Enforce when ready.
Every rule starts in log-only mode. See what it would have blocked, confirm normal traffic gets through, and switch enforcement off again at any time.
- Log-only
Install and observe
Deploy the supported SDK. Record matches while requests continue to the application.
- Review
Check the behavior
Replay the attack and normal requests against the rule, and see exactly which route and action it covers.
- Your decision
Enable and monitor
An admin on your team moves the app and the rule from Staged to Enforced. A rule blocks only when both are enforced, and either can go back to Staged at any time. You can also choose to enforce new rules as they arrive; that setting is off by default.
Will it fit my app?
- We confirm your stack is supported during scoping.
- Installed from your private ShieldProbe package registry and registered before your routes.
- Runs inside your process. No proxy, sidecar or DNS change. Rules sync from ShieldProbe and are evaluated inside your app.
- If the SDK cannot reach ShieldProbe, it lets traffic through by default.
Defend is purchased separately. Your team installs the SDK and decides when to turn on blocking.
How the portal shows a finding Defend can log but not block. Fictional SP-014 ownership finding.
Read the ownership evidence
Defend / Observe the request
GET /api/orders/order-b07- Integration
- Defend SDK installed
- Rule limits
- No session or database access
- Protection mode
- Log only (ownership finding)
The request is logged, not blocked. The application must check ownership.
Defend logs the request but can’t tell who owns the order, so the fix belongs in the code.
The rule is visible. So are its limits.
Some findings need the code fix.
This portal view shows a different sample finding: cross-customer order access. Defend logs it but cannot block it, because a rule cannot read sessions or the database to decide ownership.
The fix belongs in your authorization code, and Fix can help write it.
Start with a supported finding.