Security testing starts with authorization, ownership verification and rules of engagement. We agree the target systems, methods, schedule and reporting process before testing begins.
What an engagement can include
- Written scope and rules of engagement
- Agreed application or infrastructure testing
- Findings with impact and remediation guidance
- Retesting where included in the engagement
How we work
- Understand your goals and current environment.
- Agree the deliverables, responsibilities and boundaries.
- Build or assess in reviewable stages.
- Test, document and hand over the agreed work.
Scope and cost drivers
Testing is limited to explicitly authorized systems. Availability protections, exclusions and handling of sensitive evidence are agreed before work starts.
Before we start
Tell us what you need to achieve, who will use the system and what already exists. We will discuss the requirements before proposing a scope. Please do not send passwords or confidential system information through the public form.