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.
Home / Services / Penetration Testing
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 authorized 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.
Taken alone, none of the three findings is alarming. Together they add up to a break-in.
What the scanner reports
Three single findings, none of them urgent. The chain appears on no list.
What the tester makes of it
The same three findings as a path: from the first machine to your last backup.
Illustrative, simplified.
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?
| Method | Approach | Finds | You receive |
|---|---|---|---|
| Vulnerability scan | Automated, against lists of known flaws | Missing patches, outdated versions, open services | A long list sorted by severity |
| Penetration test | By hand, with an attacker's methods | Misconfigurations, logic flaws, and rights that chain into a break-in | Proven attack paths and an order in which to close them |
At every point you know what is being tested and whom to reach.
Every reachable system, VPN gateway, web application, and interface. We test what a stranger reaches without credentials.
We start with the access of an ordinary workstation and test how far it carries: segmentation, shares, services.
Kerberoasting, excessive rights on objects, unprotected service accounts, NTLM relay. We show the paths on which the domain can be taken over.
The configuration of your cloud environment, and whether an attacker with admin rights could reach and delete your backup.
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.
The report documents method, period, scope, and every finding so that a third party can follow it. NIST CSF 2.0 asks organizations to identify improvements from security tests and exercises, and many customer security reviews ask for a recent independent test. Whether a given test is enough is for your auditor or your customer to decide.
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).
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