Methodology
How I Work
How an assessment starts, exactly what you receive, and the steps common to every project.
The way of working is the same on every project, whatever its size: a clear scope, systematic execution, an actionable report, then a re-test that proves the fix worked.
The path in five stages
- Scoping. One session to fix what is in scope and what is not, the environment (production or staging), allowed time windows, the communication channel, and emergency limits if something breaks. The output is a signed scope document.
- Assessment. Execution against standard methodologies: OWASP WSTG for web applications, PTES and NIST SP 800-115 for assessment, mapping findings to MITRE ATT&CK where applicable. Everything performed is logged so results stay reproducible.
- Reporting. Two reports, not one: an executive report for the decision-maker (risk, impact, priority) and a technical report for the team (reproduction steps, evidence, root cause). Each finding carries a severity rating, remediation guidance and verification steps.
- Remediation & knowledge transfer. On request I implement fixes or help the team implement them, then run a knowledge-transfer session: why the issue appeared and how to prevent the whole class rather than the single instance.
- Re-test. The stage that closes the file: testing the fixed issues to prove closure, with a short re-test report showing what is closed and what remains open.
What you receive, exactly
- A scope document that fixes responsibilities and boundaries before any work begins.
- An executive report in plain language you can read in ten minutes.
- A technical report with reproduction steps, evidence and references per finding.
- A remediation plan ordered by priority and impact, not by what is easiest to fix.
- A knowledge-transfer session with your owning team.
- A re-test report after remediation.
- Deliverables in your language: Arabic and English.
Confidentiality & ownership
- An NDA signed before any access to your data.
- Work against a staging copy wherever possible, with least privilege.
- No data leaves your environment without written approval, and all test copies are deleted after delivery.
- No engagement is referenced publicly without your consent; the case studies on this site never name clients.
Frequently asked questions
How long does a full security assessment take?
A standard assessment of a mid-sized web application takes 5 to 10 working days, fixed precisely after the first scoping session. Larger programmes are split into weekly cycles with a report after each.
How is my data kept confidential?
An NDA before starting, least-privilege access, no transfer of your data outside your environment without written approval, and deletion of all test copies after delivery.
Do you work with in-house teams rather than replacing them?
Yes — that is the preferred model: test, run a knowledge-transfer session, then re-test after fixes, so the team owns the knowledge rather than depending on me.
Do you fix the vulnerabilities yourself?
I deliver implementable remediation steps and can implement fixes on request. The default is that your owning team applies them, since they know the system best.
Can you produce a formal report for an auditor?
Yes — a report formatted for an audit body or end client, with an executive summary and measurable risk ratings.
What is out of scope?
Social engineering against employees, denial-of-service attacks, testing systems outside the agreed scope, and any access to real user data.
Next step
All I need to start is a short brief: what the system is, what it is built with, and what worries you about it. From there we fix scope and timeline. Reach me through the contact section.