Offensive security · Cybersecurity
Ethical Hacking
Offensive security analysis on the target you define, run under the OWASP Testing Guide and classified with OWASP Top 10, CWE and CVSS 3.1.
- Modes
- White box, grey box or black box
- Report
- The next business day after closing
- Retest
- Up to six months afterwards
- Engagement
- By project or annual hour bank
The problem
This is the root service of the whole folder: someone attacks your systems with authorization, before someone without it does. Depending on how much information you hand over, the exercise leans closer to an exhaustive audit or to a real attack.
What it includes
White box
Full or partial access to systems, resources and services: you hand over credentials, source code and architecture diagrams. It is the mode that achieves the most coverage per hour invested.
Grey box
Only the minimum needed to analyse the flows of the targets under assessment. The usual balance between realism and depth.
Black box
A one hundred percent real simulation: the same activities a group of cybercriminals with no prior knowledge of your organisation would carry out.
Technical report
Delivered the business day after the offensive assessment ends. You can request a preliminary progress meeting before the final delivery.
Advisory meeting
A session explaining the report with all or part of the pentesting team, where questions requiring technical detail are answered.
Retest of findings
Within the following six months you can request a new test of the reported vulnerabilities to confirm the mitigation worked.
Hour bank
Annual hours at your disposal for ethical hacking activities, used when you need them instead of contracting project by project.
How we work
- 01Scope and authorizationObjectives, execution windows, emergency contacts and signed rules of engagement.
- 02ReconnaissanceInventory of assets, technologies, versions and exposed surface.
- 03Controlled exploitationManual testing assisted by tooling, with no destructive techniques.
- 04Report and meetingDelivery of the report and a review session with your technical team.
- 05RetestVerification of the corrected findings and closure record.
Deliverables
| Document | Length |
|---|---|
| Executive report Business risk in non-technical language. | 8-12 pp |
| Technical report Finding, impact, CVSS, CWE and remediation. | 40-90 pp |
| Proof of concept Reproducible step by step for each finding. | included |
| Retest record Final status of each finding. | included |
Nothing is executed without written authorization. We work only on assets authorised by the client, in agreed windows, with no destructive techniques and no denial of service. Evidence is encrypted and destroyed 90 days after closing.