A plan based on your requirements
Before testing begins, the system owner must approve the targets, methods and timing. We discuss access requirements, sensitive information, communication and boundaries. Findings should explain the issue, relevant evidence and practical steps to reduce the risk.
What the work can include
- Written agreement on authorized targets and boundaries
- Testing and review against the agreed assessment scope
- Documented findings with supporting evidence
- Risk-based remediation priorities
- Discussion of fixes and any separately agreed verification work
How scope and cost are determined
The number and complexity of targets, testing depth, access arrangements and reporting requirements affect the scope. An assessment does not guarantee that a system is free from every vulnerability.
Questions before you start
Can you test a website without the owner’s permission?
No. Testing requires authorization from the owner or an authorized representative and a clearly agreed scope.
Will the report explain how to fix the findings?
The assessment should provide understandable remediation guidance and priorities. Implementation and retesting should be agreed as part of the engagement or separately.
