Audit

Penetration test: find vulnerabilities before attackers do

Before go-live, for ISO 27001, NIS‑2, DORA or TISAX®, or as evidence for your customer: we attack your systems with the methods of real attackers, rate each vulnerability by risk and tell you exactly what to do.

Free and without obligation. You will receive your proposal within 48 hours.

What our pentest covers

Our penetration tests are suitable for:

  • Web applications and APIs
  • AI applications such as chatbots and LLM integrations
  • Mobile applications
  • SAP systems
  • OT and SCADA systems
  • AWS, Azure and Google Cloud

On request, we also review the source code.

Your penetration test results

Afterwards, you know which vulnerabilities to fix first:

  • Report with the identified vulnerabilities and their risk rating
  • Concrete recommendations for remediation
  • Follow-up assessment after the measures are implemented
  • Evidence for customers, auditors and authorities

How your penetration test works

From scoping to retest in five steps:

  1. Planning and scoping of the project
  2. Automated vulnerability scan of the IT or OT systems
  3. In-depth security analysis of the systems through penetration testing
  4. Risk assessment of the vulnerabilities and recommended measures
  5. Follow-up assessment after implementation

Why Securitects

  • Certified attack expertise: GIAC-certified pentesters (GWAPT for web applications, GCPN for cloud)
  • From web app to control system: web, APIs, AI, mobile, SAP, cloud, and OT and SCADA systems
  • Retest included: the follow-up assessment shows whether your measures work
  • Testing during live operations: we agree time windows and test depth with you, especially for OT

More about our team and its qualifications

Frequently asked questions about penetration testing

The effort depends on the number and complexity of the systems and the test depth you need. After scoping, you receive a proposal with a fixed scope.

Yes. We agree time windows and test depth so that your operations keep running, especially for OT systems.

Yes, on request we combine the pentest with a source code audit.

At least before every major release and after significant changes to systems or infrastructure. Many frameworks and customers also expect regular tests, usually once a year.

The duration depends on the scope: the number of applications, interfaces and user roles, the size of the cloud or OT environment and the test depth you need. Reporting and the retest after your remediation come on top. For OT systems, the schedule also follows your maintenance windows. We plan the test period with you during scoping; dates and effort are set out in the proposal.

The terms describe how much we know about your systems before the test:

  • Black box: no prior information, like an external attacker
  • Grey box: test accounts and basic information, for example on user roles
  • White box: full access to documentation and configuration

For most applications we recommend grey box, because it lets us test more functions and permissions in the same time. We clarify which approach fits your goal during scoping.

The pentest report shows that you test the effectiveness of your technical security measures. NIS‑2 requires procedures to assess the effectiveness of cyber security risk management, DORA calls for regular testing of digital operational resilience, and for TISAX® such tests are also common evidence. During scoping, we align the scope and report with your framework. Threat-led penetration testing (TLPT) under DORA is a separate format with specific requirements. We do not offer TLPT ourselves, but can be brought in as a service provider in a TLPT.

For the test to run efficiently, we need:

  • Written authorisation with the scope, time window and IP addresses or URLs
  • Test accounts for the agreed user roles
  • A technical contact who is available during the test
  • For hosted systems, clarification of whether your hosting or cloud provider must give consent

Ideally, we test in a production-like test environment. If that is not possible, we agree the approach on the production system closely with you.

Plan your pentest

In the free initial conversation, we define the scope and test depth.