01 / Scope
Agree targets and a safe approach
Targets, identities, time windows and prohibited actions are agreed before authorised testing starts.
Find out how an attacker could most easily enter your organisation. An authorised test reveals the most significant weaknesses and shows what to address first.
Within the agreed scope, a Blackhat test checks whether the weaknesses connect and where the path can be broken.

Authorised penetration testing
Testing has clear boundaries and evidence for each finding. Retesting can follow remediation when included in the proposal.
01 / Scope
Targets, identities, time windows and prohibited actions are agreed before authorised testing starts.
02 / Evidence
Each finding connects prerequisites, steps and minimal evidence with impact. Testing is a bounded engagement.
03 / Retest
Where included, retesting verifies original conditions and identifies residual risk or new limitations.
A Blackhat test combines an attacker's perspective with an understanding of defence. The aim is to find weaknesses that could genuinely harm your organisation, rather than produce the longest possible list of issues.
We propose a scope based on your environment and objectives. We clarify in advance what we will verify technically, which organisational questions we will assess and what the test will not cover.
A broader assessment of the organisation's main risks. Suitable as a first step and a basis for further decisions.
Verifies in depth what can be exploited in a specific application, API or infrastructure. The scope is precisely defined.
Quickly identifies potential known vulnerabilities. It does not replace manual verification, contextual assessment or business logic testing.
Before testing, we confirm objectives, authorised systems, testing windows, prohibited techniques and escalation contacts. Where agreed, a critical finding is reported promptly rather than waiting for the final report.
The report has two levels: a management summary and technical details for administrators. Each finding includes evidence, impact, recommended remediation and the limitations of the verification performed.
We adapt the rules to your environment. We agree the scope, intensity, prohibited techniques and an immediate stop procedure in advance.
Not automatically. Remediation assistance and retesting can follow the test; their scope and terms are set out in the proposal.
No. Do not send passwords, keys, source code or sensitive data through the form. We request technical information later, through a secure channel, when defining the engagement.
You do not need to know whether you need a test, a technology or a consultation. We will suggest a suitable next step based on your situation.