Aligned with NIST SP 800-115

Methodology

Your auditor will ask which methodology was used. This page documents how every engagement is carried out and can be shared as is.

01

Planning

NIST SP 800-115 §3

Written rules of engagement before anything is touched: assets in scope, explicit exclusions, testing window and your escalation contact. Every host is checked programmatically against that list before a single request is sent, with anchored matching, so a similar-looking domain cannot slip into scope by accident.

02

Discovery

NIST SP 800-115 §4

Passive first: certificate transparency, passive DNS and public datasets, which do not touch your infrastructure. Then live-host verification and path discovery. Enumeration always draws on several independent sources, because any single source misses assets the others find.

03

Attack

NIST SP 800-115 §5

Every candidate is verified by hand before it becomes a finding, and every verification has its own control: a positive control proving the instrument works, and a negative control against a path that cannot exist, proving the server is not answering 200 to everything. Nothing destructive, nothing outside the window, and none of your data moved, altered or deleted.

04

Reporting

NIST SP 800-115 §6

A plain-language executive summary and a technical body with reproduction steps your engineers can follow line by line. Severity is ranked by real reach, not by CVSS alone, followed by the remediation retest and a dated attestation letter for your audit file.

Reference frameworks

NIST SP 800-115Structure of technical testing and assessment
OWASP WSTG and ASVSWeb application testing and verification
OWASP API Security Top 10API testing
OWASP Top 10 for LLM ApplicationsAI and language model assessments
MITRE ATT&CKMapping of attacker techniques
CVSS v4.0, EPSS and CISA KEVSeverity and remediation priority

The coverage statement

Every report closes with what could not be measured, and why: a host behind bot protection, a flow that required credentials that were not provided, a check that timed out.

This is not a disclaimer; it is the point. A scanner that cannot reach a host reports nothing, and the page looks clean. A 403 from a bot manager and a host with no service produce exactly the same silence, and only one of them is safe.

A gap that is written down can be managed. A gap that is hidden is a blank space you are trusting.

What your auditor receives

  • The named methodology and its reference standard (NIST SP 800-115)
  • Scope and testing window, as agreed in writing
  • Findings with severity, evidence and reproduction steps
  • Remediation retest, with the date it was confirmed
  • A dated attestation letter

Need this methodology applied to your environment?

Request a quote