wiki

Knowledge base served at wiki.breachcraftsecurity.com. Subdomain, not a separate domain, so authority stays on the apex.

Reference material for the data sources this practice uses in an engagement: what each provider is, what its shapes and errors are, what it costs, where it lies, and how to turn it off. Written to be read by someone who has never seen the project.

Layout

| Path | Contents | | — | — | | catalogue/ | Source inventory and per-provider quick pages, grouped by capability. Start here for “which source answers which question”. | | reference/ | Encyclopaedic page per provider: request and response shapes, error tables, limits, personal data, revocation, verification log. | | capabilities/ | How a class of question is answered end to end, and what it does not prove. | | runbooks/ | How a piece of delivery actually runs. | | notes/ | One note per finding class, with tests, traps and revocation. | | method/ | Scoring contract, evidence rules, legal position. | Published baselines live in the standards repository and are served at https://breachcraft.org/. | tools.md | The tool box contract and per-tool refusals. | | handoff.md, backlog.md | State of play inside the research work, and what is outstanding. |

How to read a page

Every factual claim carries a date and a state: verified (called from our host on that date), documented (vendor documentation only), or unverified (nobody has checked). A shape copied from a doc is labelled documented and is not evidence that it works.

A 404 that means “no record” is never conflated with a 404 that means “wrong route”. “Not found” and “not authorised” are different answers and are written separately.

Conventions

Adding or correcting a page

Take an existing page as the template and keep the section order. If a provider changes shape, correct the page and move its state to verified with the date; do not leave a stale claim in place. If a page is wrong, the correction is worth more than a new page.