Frequently Asked Questions
These answers explain how an engagement runs in practice: how scope and authority are established, what each method can demonstrate, how evidence is protected, and what a report can and cannot certify. They also separate three commonly confused claims: a demonstrated weakness, an exercised attack path and evidence of a past intrusion. Use them to prepare for a specific risk decision. The signed proposal defines the work you commission.
Editorial review: November 2026
120 of 120 questions
Getting started and scoping
Authority, scope, and the information needed to quote honestly.
Engagement process and methodology
How the work runs, who performs it, and how interruption is handled.
Coverage and testing depth
What each discipline examines, and what it deliberately leaves alone.
Red team and adversary emulation
Objectives, deconfliction, and the measurement of defensive response.
Web, mobile and API testing
Application surfaces, including the layers beneath the interface.
Source code review and AppSec
Source, dependencies, and the definitions that configure infrastructure.
Network, cloud and identity
Perimeter exposure, internal authority, cloud configuration and identity.
GenAI and AI system security
Retrieval, tool authority, approval boundaries and measured effects.
Reporting, remediation and retesting
Evidence, severity, verified correction and documented disagreement.
Commercial, legal and confidentiality
Terms, confidentiality, insurance and the limits of compliance evidence.
Still have a question?
Describe the decision, the technology and the constraint the published answer does not resolve. A scoping discussion can identify the evidence that would settle it, the specialist requirements it implies and the limitations the proposal must state. Bring the part you are unsure about; an incomplete question is more useful than a polished one.
