First Shield Test
The Shield Tests panel runs a battery of known attack payloads against your shield configuration to validate that detection rules are working correctly.
Running the Test Suite
- Navigate to Shield Tests from the sidebar (under SECURITY)
- Click Run All Tests
- The suite executes each test in sequence, sending crafted payloads and checking expected verdicts
Reading Results
Each test shows a PASS (green) or FAIL (red) badge:
- PASS — the shield detected the attack and returned the expected verdict
- FAIL — the shield did not return the expected verdict
Click any test to expand its details:
- Payload description — what type of attack was simulated
- Expected verdict — usually BLOCK
- Actual verdict — what the shield returned
- Rules fired — which specific rules caught the payload
Interpreting Failures
Advanced test failures are expected and informational. The suite intentionally includes cutting-edge obfuscation and novel encoding tricks that push beyond current rule coverage. These are research targets, not emergencies.
What should concern you:
- Basic tests failing — if the shield misses a straightforward jailbreak or plaintext credential, investigate immediately. A rule may be misconfigured or a whitelist entry may be too broad.
- All tests failing — the shield engine may not be running. Check Infrastructure panel.
What is normal:
- Some advanced tests failing (encoding obfuscation, multi-step injection chains)
- Test results changing after whitelist modifications
When to Run
- After whitelist changes
- After platform updates
- Before switching from OBSERVE to BLOCK mode
- After reconstruction or fresh deployment
- As a periodic confidence check