What problem does it solve? Security testers need a disciplined way to confirm whether database backups, logs, configuration files, or admin consoles are publicly exposed without ever connecting to the database or using credentials, and without producing false positives from stale caches or error pages. ## Core Features & Use Cases - Evidence-Gated Validation: Enforces a fixed baseline → single-variable probe → post-baseline → oracle → evidence workflow so every finding is reproducible and in-scope. - Strict Safety Boundaries: Stops immediately on database connections, credential use, data export, or admin operations; suspected credentials are recorded only as field names and hashes. - False-Positive Filtering: Treats WAF blocks, timeouts, scanner hits, empty files, and historical archives as INCONCLUSIVE rather than confirmed exposure. - Use Case: During an authorized assessment, you discover a URL hinting at a database backup file. Use this Skill to verify ownership, scope, and accessibility of your own canary artifact, then capture URL, hash, ACL, and a minimal redacted excerpt as evidence. ## Quick Start Use $hunt-database-exposure to plan an evidence-gated, authorized validation path for a suspected exposed database backup file.
