Coverage notes
Coverage notes by attack surface
These coverage notes describe each attack surface at a high level. So every note covers scope, authorisation, safety and what the report shows, rather than technique.
What every engagement shares
Every engagement starts with a written scope that the system owner signs. Then one fixed fee is agreed, so the price does not move mid-project.
The report is written by the penetration hacker who ran the work, and the retest is included. Also, a bounded Attack Surface Diagnostic exists for organisations that need one clear answer first.
How to use these coverage notes
Start with the surface that worries you most. Then read its safety section. That is what your operations team will ask about first. Finally, send a technical brief that names the systems and what you are trying to prevent. Each note explains what to include, so one written message is usually enough to receive a scope and a fixed fee.
Coverage notes for networks and pipelines
Inside the network, and the systems that ship your software.
Coverage notes for devices and sites
Connected products, industrial networks and buildings.
Coverage notes for applications and infrastructure
Services and remote access come first. Then voice, firewalls and chains. Each needs its own rules. So each has its own note.
Send a technical brief
Tell us what is in scope and what you are trying to prevent. The penetration hacker who would lead the work replies with a written scope and one fixed fee.
Send the brief