Services
Security assessment
Assessment process
Scoping
Confirm the assets, user roles, environments, test window, exclusions and escalation contacts. Authority to test is recorded before work starts.
OutputWritten scope and rules of engagement
Mapping
Identify entry points, roles, trust boundaries and the workflows that carry business risk.
OutputCoverage map and test plan
Review
Manual review supported by tooling. Relevant security testing guidance informs the checklist; scanner output is treated as a lead, not a finding.
OutputValidated observations
Validation
Reproduce each issue with the minimum evidence needed to explain it. Stop and notify the agreed contact if availability or sensitive data is put at risk.
OutputConfirmed findings and reproduction steps
Reporting
Document the affected behavior, prerequisites, impact and remediation. Critical issues are raised during the assessment, not held for the final report.
OutputPrioritized report and technical handover
Retesting
Where included, recheck the agreed fixes and document any residual limitations.
OutputRetest update
Deliverables
Executive summary
The main risks, their business context and the order in which to address them.
Technical findings
Affected assets, prerequisites, reproduction steps, redacted evidence and severity rationale.
Remediation guidance
Practical fixes and verification advice for the engineering team.
Handover and retest
A technical walkthrough and a retest update when retesting is in scope.
The assessment is time-bounded. Duration and effort are agreed during scoping and stated in the proposal. It is not a guarantee that a system has no vulnerabilities, a compliance certification or a substitute for ongoing security work.
Scope and authorization
Rules of engagement
- Written authorization from the system owner before any request is sent.
- Agreed assets, test window, request limits and stop conditions.
- A named contact for critical findings or unexpected service impact.
- Defined evidence handling, report recipients and retention arrangements.
Excluded by default
- Denial-of-service testing and destructive changes.
- Social engineering and physical access.
- Access to unrelated customer data.
- Anything outside the agreed scope.
Staging with representative test data is preferred. Any exception to the exclusions requires explicit written agreement.
Start a scoping discussion
Send a short description of the systems, the environment, approximate size, user roles and preferred dates. Do not include credentials or sensitive data in the initial email.
Assessment work begins only after written authorization from the system owner. Timing and availability are confirmed once the scope is clear. This page describes my assessment approach and does not imply endorsement by my employers.
For background, see my CV and project work.