Deterministic secret redaction
Passwords, API keys, PEM certificates, and tokens are stripped and replaced with typed redaction placeholders before any model reads source files, producing an Ed25519-signed SHA-256 intake manifest.
Raw model outputs are treated as unverified hypotheses. Each candidate must pass eight deterministic and negative-control checks across Gates A–H before it is signed with your organisation's Ed25519 keypair.
{
"gate": "H_READINESS_SEAL",
"verdict": "READY",
"signer": "tenant:acme-prod:ed25519",
"signature": "sig:ed25519:9f2a77d1c48e...c71b"
}
Every candidate surfaced during a scan is evaluated sequentially across the six stages below. Candidates that fail a check are recorded as Disproven or held with a specific evidence request.
Passwords, API keys, PEM certificates, and tokens are stripped and replaced with typed redaction placeholders before any model reads source files, producing an Ed25519-signed SHA-256 intake manifest.
Questor verifies that every cited file and symbol exists in the repository snapshot and maps entry points, auth middleware, and privileged sinks. Dead code and test-only fixtures are filtered out early.
The call path is verified end-to-end across function calls, package boundaries, and linked HTTP services
rather than inferred from an isolated snippet. Every hop records exact file:line coordinates.
Questor evaluates the strongest false-positive argument against upstream type coercion, ORM parameterization, and auth middleware. Candidates blocked by existing controls are logged as Disproven.
Scores lowest required privilege, affected data scope, CVSS 3.1 vector, OWASP Top 10, and CWE classification alongside any practical runtime preconditions.
Findings that satisfy all six readiness criteria are signed with your organisation's Ed25519 keypair and published to the Case Registry and append-only audit log.
When a candidate does not pass every gate, Questor logs the exact reason rather than discarding it silently or promoting it as a low-confidence alert.
Passed all eight gates (A through H), including negative controls. Includes the
source-to-sink trace, static exploitability check, and calibrated impact needed to remediate the flaw.
Initial discovery flagged a candidate, but Gate D or Gate F confirmed that an upstream sanitizer, ORM parameterizer, or auth guard prevents exploitation. Recorded for AppSec review without cluttering developer queues.
The code path is reachable in source, but exploitability depends on configuration outside the repository (such as an ingress gateway rule or WAF header). Questor raises a specific evidence request instead of assuming impact.
Traditional scanners report alert counts without tracking false-positive dismissal rates. Questor records every candidate inspected, held, confirmed, or disproven across each scan.
Run a scan to review the complete Ed25519-signed gate ledger, source-to-sink traces, and disproven metrics.