Services & Packages
Three clear packages with scope, deliverables and duration — and the out-of-scope stated too.
Three clear packages instead of "contact me to discuss". Each states scope, deliverables, duration — and what is out of scope, plainly.
Quick review
A first read on risk in the least time
- One web application, clearly bounded scope.
- Focus on the ten riskiest paths and the common sources (OWASP Top 10).
- Executive report plus a findings list with severities.
- One review session.
Full assessment
Systematic testing with a re-test
- Assessment against OWASP WSTG and PTES for an agreed scope.
- Executive report plus technical report with reproduction steps and evidence.
- Remediation plan ordered by impact, with verification criteria per finding.
- Knowledge-transfer session with your team.
- Re-test after remediation with a closure report.
Continuous watch
Continuity after remediation
- Periodic review of new assets and changes.
- Digital reputation and impersonation monitoring.
- A monthly report in executive style with a risk summary.
- A direct channel for new incidents.
What you receive, exactly
- Executive report in plain language: risk by impact and priority, readable in ten minutes.
- Technical report: reproduction steps, evidence, root cause and a reference standard per item.
- Remediation plan ordered by impact rather than by what is easiest.
- Knowledge-transfer session with your owning team so the vulnerability class does not return.
- Re-test report showing what is closed and what remains open.
- All deliverables in Arabic and English.
How we start
- A short brief: what the system is, its stack, and what worries you about it.
- A scoping session (30–45 minutes): environment, allowed windows, communication channel and emergency limits.
- NDA + signed scope document — before any access to anything.
- Execution against the methodology published on the How I work page.
- Delivery + session, then a re-test in the full package.
Always out of scope
- Social engineering against employees.
- Denial-of-service attacks against real systems.
- Testing any system outside the scope agreed in writing.
- Any access to real user data, or bypassing anyone else's protections.
Book a call instead
The decision is usually made on a call, not in a form. Send a request through the contact form mentioning "call" and your available times, and you will get a reply proposing a workable slot. Go to the contact form
Request a quote
All I need to price the work: the type and size of the system, whether you have an in-house team, and which package you mean. Pricing follows the scoping session, because it depends on the surface tested rather than hours alone.