No testing without written authorization
Trust and delivery
A methodology designed to produce evidence people can act on
VAPT Experts adapts techniques to the target, but the quality controls remain consistent. Every engagement begins with written authorization, separates observation from confirmed risk and records the limitations that affect how the result should be used.
- Manual validation
- Secure evidence
- Practical remediation
Process
Assessment lifecycle
Each step creates a clear record for the next stage.
- 01
Scope
Confirm assets, identities, objectives, dates, exclusions and third-party permissions.
- 02
Authorize
Approve rules of engagement, safe techniques, communication and stop conditions.
- 03
Map
Understand attack surface, roles, objects, data flows and control boundaries.
- 04
Test
Use safe automation for discovery and manual work for validation and abuse paths.
- 05
Review
Peer-review high-impact evidence, remove duplicates and consider compensating controls.
- 06
Report
Write executive and technical findings with scope, impact, evidence and remediation.
- 07
Retest
Repeat the relevant attack path and record verified closure or remaining exposure.
Coverage
Quality principles
These controls apply regardless of the technology being tested.
No production credential exchange through public forms
Urgent findings communicated through named contacts
Material findings supported by evidence
Unconfirmed observations labelled clearly
Severity based on practical context
Sensitive evidence minimized and controlled
Scope limitations disclosed
Retest traceable to the original finding
What this means
Standards
Web and API work may draw from OWASP testing guidance. Infrastructure work may use PTES and NIST SP 800-115 concepts. Mobile reviews may use OWASP MASVS and MASTG. Platform and vendor guidance is added where relevant. These references support coverage, but the actual test plan follows the target's roles, architecture and business risks.
At a glance
Severity decisions
CVSS can support consistency, but business context remains necessary.
| Factor | Questions considered |
|---|---|
| Exploitability | What access, knowledge and conditions are required? |
| Technical impact | What confidentiality, integrity or availability effect is proven? |
| Business consequence | Which customers, transactions or operations are affected? |
| Affected population | Is the issue isolated or systemic? |
| Compensating controls | Do monitoring, approval or network controls reduce practical exposure? |
| Confidence | Is impact confirmed, likely or dependent on missing context? |
Common questions
Common questions before you decide
Do you follow OWASP?
Yes, where relevant, but OWASP categories are not used as a substitute for application-specific threat modelling and business-logic testing.
Are all findings exploited?
Only to the safe level needed to demonstrate impact and within the agreed rules. Destructive or high-risk actions require explicit authorization.
How are disagreements handled?
Client context and compensating controls are reviewed with the technical team. Any severity change remains evidence-based and is documented.
Related
Continue planning
Next step
Turn the requirement into a clear, testable scope
Share the asset type, important roles or environments, testing deadline and the decision the report needs to support. You can begin without sending credentials or sensitive evidence.
- 01Describe the need
- 02Confirm scope and safety
- 03Receive clear commercial terms
