Home / Services / Penetration Testing

We find the way into your network before an attacker does.

Penetration testing for networks, Active Directory, web applications, and cloud, done by hand.

A scanner works through a list of known holes. An attacker chains three small mistakes into domain admin. Our testers walk the same path by hand, the way attackers did in the ransomware cases our responders have worked.

A penetration test is an authorised attack on your own IT: testers use an attacker's methods to get into systems and escalate their privileges. Identiqa tests the external attack surface, the internal network, Active Directory, cloud configuration, and backup locks, and shows for every finding how far an attacker gets with it and how you close the path.

Three small mistakes. One path to domain admin.

Taken alone, none of the three findings is alarming. Together they add up to a break-in.

What the scanner reports

  1. Missing patch: medium
  2. Weak password: low
  3. Excessive rights: informational

Three single findings, none of them urgent. The chain appears on no list.

What the tester makes of it

  1. Workstation through the missing patch
  2. Service account with the weak password
  3. Domain admin through the excessive rights
  4. Access to the backup

The same three findings as a path: from the first machine to your last backup.

Illustrative, simplified.

Scan or penetration test: what you get from each.

Both have their place. The scan runs all the time and costs little. The test answers the question your board cares about: can someone get through?

Vulnerability scan and penetration test compared
MethodApproachFindsYou receive
Vulnerability scanAutomated, against lists of known flawsMissing patches, outdated versions, open servicesA long list sorted by severity
Penetration testBy hand, with an attacker's methodsMisconfigurations, logic flaws, and rights that chain into a break-inProven attack paths and an order in which to close them

How the test runs.

At every point you know what is being tested and whom to reach.

  1. BeforeAgree scope, time windows, and emergency contacts
  2. TestReconnaissance and attack by hand, from outside and inside
  3. DuringWe report critical findings during the test, not weeks later in the report
  4. ReportSummary for leadership, evidence for IT
  5. AfterDebrief with the testers, actions in order of urgency

What we test.

From outside: what the internet sees of you

Every reachable system, VPN gateway, web application, and interface. We test what a stranger reaches without credentials.

EXTERNAL ATTACK SURFACE

From inside: the attacker is already in

We start with the access of an ordinary workstation and test how far it carries: segmentation, shares, services.

INTERNAL NETWORK

Active Directory: the road to domain admin

Kerberoasting, excessive rights on objects, unprotected service accounts, NTLM relay. We show the paths on which the domain can be taken over.

ACTIVE DIRECTORY

Cloud and backup: does the last line hold?

The configuration of your cloud environment, and whether an attacker with admin rights could reach and delete your backup.

CLOUD · BACKUP LOCKS

Common questions

Can a penetration test disrupt our operations?

The risk can be kept small. No serious test can rule it out. That is why we agree scope, time windows, and emergency contacts with your IT team in advance, run no load tests against production systems without explicit agreement, and stay in direct contact with your team throughout.

Does the report work as evidence for auditors and regulators?

The report documents method, period, scope, and every finding so that a third party can follow it. Under the FCA and PRA operational resilience rules, firms must test their ability to remain within their impact tolerances, and EU DORA names penetration tests in Article 25. Whether a given test is enough is for your auditor or your regulator to decide.

How often should we run a penetration test?

After every major change to the network, Active Directory, or an important application, and otherwise at least once a year. Financial entities under EU DORA must test the systems that support critical or important functions at least yearly (Article 24).

Scope first, then the quote.

Tell us what should be tested: network, Active Directory, an application, or your cloud. In the architecture briefing we settle scope and time windows. After that you receive a written quote.

Architecture briefing & advisory