Anonymous automation is challenged; verified agents pass; spoofed claims are refused
AGENT-EDGE-003 · v1.0
Computed by Scovant Cloud — this check needs Scovant's own agent-identity fetch, which the open-source engine does not perform.
What it detects
The edge challenged the anonymous request, admitted the correctly signed request, and refused the request whose signature could not be verified.
Why it matters
This is the recommended posture — identity-aware, verification-gated, fail-closed — and is recorded as evidence rather than as a readiness failure.
How to fix
No action needed. This is recorded as evidence of the recommended posture: anonymous automation is challenged, a correctly signed request is admitted, and a request whose signature cannot be verified is refused. Keep this identity-aware, verification-gated, fail-closed configuration as-is, and check it again after any change to your edge/WAF rules.
Example
GET / (anonymous) -> 403; GET / (valid sig) -> 200; GET / (INVALID sig) -> 403
References
Last reviewed: 2026-09-01 · rule v1.0