A penetration test, or pentest, is an audit which purpose is to check the security of a resource (IP subnet, website or web application, mobile application, internal network...) from an attacker point of view. It is the best way to concretly assert the efficiency of the protection measures that were put in place.
We evaluate the security of the perimeter that was defined with you folowing a methodological approach and a technical process specific to the tested assets, which takes inspiration notably from the PTES (Penetration Testing Execution Standard), as well as essential resources such as OWASP.
A clear and detailed audit report is written at the end of the engagement to list the security defects, but also mention positive aspectsas well as necessary corrective actions to fix or mitigate the potential vulnerabilities. The restitution of this report is a phone or visio call, or a meeting within your office, and is organized in two parts:
We suggest you to check the list of our audit services in order to have more detailed information about our pentests.
Before the penetration testing, we define the perimeter of the audit with you. It can be your company website, specific web applications, a group of devices, an IP range, physical buildings...
We also define the level of information that our auditors have at the beginning of the tests:
On the day of the audit, we organize a launch meeting with your technical team, then after a last confirmation, we start the technical tests.
In a black box setting, our pentests typically start by a passive reconnaissance phase where we gather information about the target, without establishing any connection to it. Then follows a fingerprinting phase that starts by enumerating exposed services and ports.
For every service exposed, we search for known vulnerabilities, configuration vulnerabilities, and we also identify user entry points we could exploit to compromise the perimeter.
In a grey box setting, where we generally have one or more accounts to our disposal, we also check that the functionnalities and data are correctly compartmentalized (access controls), and that a lateral deplacement or a privilege escalation are not possible.
In a white box setting, we check the access controls of the admin account, but we also check that the privileges granted to this kind of account are not permissive enough to escape from the app and take control of the server.
If we have the source code at our disposal, we perform a brief source code audit from a security perspective, in order to discover more vulnerabilities.
We then sum up the main results of the audit during a brief phone call with your team, before finishing by writing the deliverables.
Our quality methodological approach offers:
Specialists in information security in Lyon, Paris, Grenoble and Saint-Etienne in France
You've enabled "Do Not Track" in your browser, we respect that choice and don't track your visit on our website.