Popular searches
Hamburger Menu
    //

    Penetration tests for your IT systems

    From web applications to IT infrastructure to production networks. We simulate targeted attacks on your systems – with over 100 completed pentests under our belt.

    Illustration: 3 Personen und Hund in relaxter Bürosituation, davor Ritter, der mit Schild einen Drachen abwehrt.
    //

    Ethical hacking reveals the worth of the security existing on paper.

    Firewalls, patches, policies: many companies believe they're well protected. Until someone actually tests it. That's when it becomes clear that misconfigured systems, forgotten access points, or untested interfaces are real entry points that remain invisible during normal operations.

    Ethical hacking does exactly that: we think like attackers, act like attackers, and in the end don't hand you a list of attacks – but a clear action plan.

    //

    Tailored penetration tests for every use case

    From web apps to critical OT networks: every environment has its own vulnerabilities. That's why we don't offer off-the-shelf pentests, but targeted simulations tailored to your systems.

    Web application penetration test

    Find vulnerabilities in your web apps before attackers do

    Your web app is publicly accessible – and the first thing an attacker sees. We don't just check what a scanner finds, but also what only a human can find: flawed business logic, insecure data flows, complex attack scenarios.

    What we test:

    • Methodical review: analysis based on the OWASP Top 10 and the Web Security Testing Guide
    • Business logic: we don't just test automatable gaps, but also manual and complex attack scenarios
    • Application architecture and data flows: in-depth review of technical and abstract vectors

    Possible test scenarios:

    • White-box approach: Based on extensive in-depth knowledge of the application; code reviews and interviews with developers are possible
    • Grey-box approach: Based on limited background information about the application, such as login credentials, diagrams, and small code snippets
    • Black-box approach: No information about the application’s internal processes is available; only publicly accessible information is used

    IT infrastructure penetration test

    Uncover vulnerabilities, misconfigurations, and attack paths

    The most dangerous gaps in networks often do not arise from ignorance, but from grown complexity. We expose what's lurking in your system landscape.

    What we test:

    • Focus on Network components: routers, switches, firewalls, load balancers
    • Active directory: permissions, delegation, attack vectors
    • Identity & access management (IAM): verifying that access rights are truly restricted. If we find gaps here, our Keycloak experts can directly assist with remediation
    • Shadow IT: identification of all reachable systems in the network

    Our test scenarios:

    • Insider simulation: what happens if someone with physical access acts maliciously?
    • Assumed breach: we simulate the takeover of an endpoint and test how far an attacker can penetrate the network
    • External attacker: how secure are your externally reachable services?

    OT infrastructure penetration test

    Testing OT environments in a controlled manner

    Production networks are no longer isolated islands. Connectivity with office IT creates new attack surfaces and a production outage is more costly than any security test. We test OT environments in a controlled, step-by-step manner without risk to ongoing operations.

    Why OT pentests are different:

    • Availability comes first: we don't use automated scans that could overload PLCs or SCADA systems
    • Controlled sequence: every step is coordinated in advance with your system administrators
    • Interface check: special attention is paid to the transitions between office network and production

    How we minimize operational risks:

    • Joint determination of which systems are actively tested and where passive analysis is used
    • No blind testing: we never test without prior coordination with your maintenance team

    Threat-led penetration test

    Putting your entire defense strategy to the test

    Classic pentests evaluate technology. Threat-led pentesting examines whether your entire defense strategy can withstand a targeted professional attack. The next step once the technical foundation is in place.

    What we test:

    • Attacker tactics: we use the same methods as real attacker groups, not standard mistakes
    • Detection & response: does your security team notice our intrusion attempts? How quickly do emergency plans kick in?
    • All levels: technology, people, and processes

    When it makes sense:

    • Regular pentests have already been conducted
    • The technical foundation is solid and the overall strategy now needs to be validated
    • Regulatory proof of resilience is required, e.g. for DORA

    All details on methodology and process on our red teaming page.

    //

    Security requires an honest outside perspective

    Marc Lenze

    IT-Security Business Development Lead

    People who defend their own networks tend to develop tunnel vision when it comes to network security. As a result, they may become fixated on certain aspects while completely overlooking others. In penetration tests, we notice time and again that it’s often only an independent, outside perspective that reveals vulnerabilities in this regard.

    Marc Lenze

    IT-Security Business Development Lead

    //

    Why codecentric as your penetration testing provider?

    Training icon: Weightlifter lifting large barbell

    Practical recommendations

    Not just finding problems, but delivering concrete solutions.

    Individual test scenarios

    Tailored to your specific system landscape.

    Review icon: Clipboard with indicated list, with a rating star on it

    Best practice standards

    OWASP Top 10, WSTG, PTES – we work according to established frameworks, not gut feeling.

    Certified expertise

    Certifications such as OSCP+, OSEP, OSCE, and CRTO prove it: our ethical hackers have carried out real attacks, they did not just study theory.

    Four eyes see more than two

    Every pentest is conducted by two experts and reviewed internally.

    Icon: Gehirn mit Stern oben rechts als Zeichen für KI

    NIS2- and compliance-ready

    Our reports provide the documentation you need for NIS2, ISO 27001, and internal audits.

    //

    Certified expertise for your IT security

    //

    Use case: vulnerability in a third-party software library

    Background

    Many web applications use third-party software libraries to avoid developing every feature from scratch. If such a library is used on a publicly accessible website and contains a known vulnerability, it creates a potential entry point – accessible to any internet user.

    Attack scenario

    An attacker identifies the vulnerable library and uses a specially crafted request to exploit the vulnerability. For known vulnerabilities, ready-made exploits often already exist, meaning even attackers without deep technical knowledge can carry out the attack. More complex vulnerabilities, however, require solid expertise for manual exploitation.

    Potential impact

    The damage potential depends heavily on the specific vulnerability and the underlying infrastructure. In this case, an attacker could: gain access to sensitive data stored server-side, use the vulnerability as an entry point into the internal network, plan and prepare further attack steps on that basis, and in the worst case, compromise the entire internal infrastructure.

    //

    Frequently asked questions about pentesting

    Can systems go down during the test?
    Safety comes first. We use controlled testing methods and coordinate closely with your system administrators – especially in OT environments. This minimizes the risk to ongoing operations to an absolute minimum.
    What information do you need from me to carry out a penetration test?
    For a pentest, a walkthrough of the application is helpful to better understand its processes. It's also important for us to know about any special considerations such as maintenance windows or critical legacy systems. We decide together with you how the test should be conducted – as a blackbox, greybox, or whitebox pentest.
    What is the difference between a standard pentest and threat-led pentesting (TLPT)?
    A classic pentest looks for technical vulnerabilities in a defined system (e.g. a web app). It is a focused, in-depth review. TLPT, on the other hand, is scenario-based: we take on the role of a specific attacker and attempt by all means available (technology, social engineering, processes) to reach a predefined objective – for example, gaining access to executive management data. It tests not only the IT, but also how well your detection teams notice and respond to a real attack.
    Is our company already ready for threat-led pentesting?
    TLPT is the supreme discipline of IT security. It makes sense when you have already conducted regular pentests and largely completed your technical homework (patch management, firewall configuration, IAM). Once the basic security foundation is in place, TLPT helps you validate the coordination of your defense teams and the effectiveness of your security strategy under real-world conditions.
    What does a penetration test cost?
    The cost of a penetration test depends directly on the scope – and that's different for every company.
    The key factors are: how complex is the application or infrastructure? How large is the attack surface? Which test scenario fits the situation? We discuss the exact scope in a free initial consultation.
    What is ethical hacking?
    Ethical hacking refers to the targeted, authorized testing of IT systems using the same methods that real attackers would use – with the difference that you commission the work and receive an action plan at the end instead of damage. Penetration tests are the most well-known form of ethical hacking.
    What is the difference between a blackbox, greybox, and whitebox pentest?
    In a blackbox pentest, we start without any prior knowledge, just like an external attacker. In a greybox pentest, we have partial information, such as credentials or an architectural overview. The whitebox pentest gives us full insight into the code and architecture and enables the most in-depth review.

    Find the gaps before attackers do.

    No system is secure by definition. But with a penetration test, you at least know where you really stand.

    Marc Lenze

    IT-Security Business Development Lead

    Marc Lenze

    IT-Security Business Development Lead