Pentest
Specialists attack your applications, APIs and infrastructure the way an attacker would, 70 to 80% of the time by hand. You get every flaw with proof of exploitation and the way to fix it, not a list of tool alerts.
- Area
- Offensive Security
- Scope areas
- 8
- Phases
- 6
- Reports
- 5

Scope
Web applications
Authentication, session, access control and business logic, following the OWASP WSTG. Manual work is combined with autonomous AI pentesting to widen coverage.
APIs
REST and GraphQL: object- and function-level authorization, data exposure and rate limits, following the OWASP API Security Top 10.
Android and iOS mobile
The app package, its traffic, local storage and its conversation with the APIs, following the OWASP MASTG.
Internal and external infrastructure
From the internet or from inside the network, with a focus on Active Directory. Black Box or Gray Box, with or without a user account.
Cloud and Kubernetes
Permissions, storage and exposed services, cluster configuration, and the path from a container to the cloud account.
Wireless
Corporate and guest Wi-Fi: authentication, segmentation and what a visitor can reach.
Hardware, ATMs and payment terminals
Debug interfaces, firmware and device communication.
SCADA, OT and ICS
Industrial environments, with agreed windows and limits so operations are not affected.
How it works
- 01
Scope and rules
We agree with you on the targets, the type of test, the windows and the emergency contacts.
- 02
Information gathering
We map what is exposed and how the systems work. You provide access and test users when the scope calls for them.
- 03
Analysis and planning
We cross-check the weaknesses found and plan the most likely attack scenarios.
- 04
Controlled exploitation
We run the scenarios by hand, chaining flaws like a real attacker, with every step documented.
- 05
Reports
You follow progress through a weekly status and receive the technical, executive and financial risk reports.
- 06
Retest
After the fixes, we test again and issue the retest report.
What you get
Weekly status
during the testEvery vulnerability found, with evidence and the fix, for the project team.
Technical
at the endExploitation steps, evidence and recommendations, for the people who fix.
Executive and financial risk
at the endBusiness risks, financial impact and an action plan, for the board.
Retest
after the fixesWe confirm what was fixed and what is still open.
Leonnes / Executive report / Exemplo S.A.02 / Follow-up
From the first status to the retest
Open vulnerabilities, report by report
- Found
- Open
A peak of 9 open at the end of the test; 1 at the retest, of the 12 found.
| Moment | Found | Open |
|---|---|---|
| W1 (Weekly status) | 3 | 3 |
| W2 (Weekly status) | 6 | 6 |
| W3 (Weekly status) | 9 | 8 |
| W4 (Technical and executive) | 12 | 9 |
| W5 (Follow-up) | 12 | 6 |
| W6 (Follow-up) | 12 | 3 |
| Retest (Retest) | 12 | 1 |
ConfidentialFictitious data
In practice
Digital identity and facial biometrics
Specialized penetration tests of the web and mobile applications, APIs and facial biometrics solutions of a leading digital identity company whose technology is used by 8 in 10 Brazilian banks, finding vulnerabilities and assessing risk in solutions critical to the financial sector.
Frequently asked questions
What is the difference between a pentest and a vulnerability scan?
A scan is automatic and lists known flaws without confirming whether they can be exploited. In a pentest, specialists exploit each flaw and chain several of them to show how far an attacker would get.
Can the test take my systems down?
Tests are controlled: before we start, we agree on windows, limits and what stays out of scope. Production and industrial environments get techniques and hours set with you.
How long does it take?
It depends on the scope: how many applications, APIs and networks, and the type of test. The proposal sets the timeline after the scoping conversation.
What do you need from my team?
A technical contact, the list of targets and, for Gray Box tests, test users with the roles that matter. We agree on the rest at kick-off.
Is the retest part of the project?
Yes. Retesting the fixes closes the reporting cycle, and the proposal sets out how it works in your case.
See what an attacker would see first
We reply within one business day.


