You are about to hand a stranger the keys for a week. Check who they are, how they work and what they do with what they find.
Wardline is a fictional business, so nothing here has been audited or issued. Every entry is a demo sample showing how a real firm would list its own.

Attestation report on how we store test evidence.
Certificate for our information security management system.
Another firm tests our systems once a year. Summary letter under NDA.
Hands-on exam against live machines, with a written report.
Hands-on web exploitation, the skill behind our Web and API tests.
Penetration testing method and legal limits.
Broad security knowledge, held by our engagement leads.
Demo content. No certificate, attestation or audit exists for this fictional business.
Nothing here is a house method. Each framework has a set place in the report, so your auditor can find it without asking.
Framework | How we use it | Report |
NIST SP 800-115 | Plans the test and sets out how we run it and report on it. | Report§2 |
PTES | Gives the phases, from pre-engagement through to reporting. | Report§2, §3 |
MITRE ATT&CK | Names each technique on the attack path, so your defenders can look for it. | Report§3 |
OWASP ASVS | The checklist behind every Web and API test. | Report§4 |
CVSS | Scores each finding, so Critical means the same thing every time. | Report§4 |

Proof of a way in is sensitive until it is fixed. It stays encrypted, with the named testers only, then it goes.
Evidence kept after the retest, then wiped. Sample.
Test tools left behind. Each one is listed and removed.
From your named contact stops the test at any time.
Professional liability cover. Sample.
The same format your board would get, redacted. Here is what is inside.
§1 | Summary for the board | p. 3 |
§2 | Scope and rules | p. 6 |
§3 | Attack path | p. 9 |
§4 | Findings and proof | p. 14 |
§5 | Fix plan | p. 31 |
§6 | Retest record | p. 36 |
Redacted demo sample, by email, with no sales call attached.
Rather talk? +1-555-0187 · [email protected]