Penetration testing

We test your defences with the same techniques attackers use – in a controlled way, within an agreed scope and with clear rules.

What we test

  • External infrastructure – services and systems reachable from the internet,
  • internal network – what an attacker who got inside can do,
  • Active Directory and Microsoft Entra ID – permissions, dangerous combinations of rights, forgotten accounts,
  • web applications and APIs – vulnerabilities in applications and their interfaces,
  • Wi-Fi and network segmentation.
Source code on a dark screen

Process

How a penetration test works

1

Scope and rules

Together we define the targets, scope, schedule and contact persons. Everything is confirmed in writing.

2

Testing

We combine automated tools with manual verification. Critical findings are reported immediately.

3

Report

An executive summary for management and a technical description of the vulnerabilities with recommendations for IT.

4

Retest

After remediation we verify that the vulnerabilities have really been fixed.

Why test regularly

A penetration test reveals vulnerabilities before someone else finds them. It is also evidence that you verify your security measures – which helps in an inspection under the Cybersecurity Act, in an ISO/IEC 27001 audit and with DORA's requirements for digital operational resilience testing.

Deliverables

What you get

Management

Executive summary

An overall assessment, the most serious findings and their impact on operations, explained clearly for management.

IT

Technical report

A description of each vulnerability with a severity rating, how it was verified and a specific remediation recommendation.

Presentation

Walk-through of the results

We go through the results with you and help set the order of fixes.

Retest

Fix verification

After remediation we check that the vulnerabilities are gone and issue a confirmation.

Questions about penetration testing

Will the test disrupt our operations?

We plan the test so that it does not put your operations at risk – risky steps are agreed in advance and, if needed, carried out outside working hours or in a test environment.

How often should we test?

We recommend at least once a year and always after a significant change – a new application, a move to the cloud or a network change.

What do you need from us?

A written authorisation for the test, a defined scope and a contact person. For external tests also the consent of your hosting providers, where required.

Let's agree on the scope of your test

Write to us