Skip to content

Penetration Testing

Internal and External Network Penetration Testing

From the perimeter to the domain controller

How far would an attacker get – first from the internet, then inside your internal network? With network penetration testing, we assess firewalls and VPN, mail, and web servers as well as Active Directory and network segmentation, and show you the real attack paths to your critical systems.

  • Fixed price after scoping
  • Free retest
  • Quote within 24 hours

Definition

What is network penetration testing?

In network penetration testing – often also called an infrastructure pentest – we carry out targeted attacks on your IT infrastructure on your behalf: servers, clients, network services, firewalls, and directory services. The test doesn’t stop at a list of theoretical weaknesses – we demonstrate which vulnerabilities can actually be exploited and where they would lead an attacker.

We distinguish between two starting points. From the outside, everything that is reachable from the internet counts – VPN gateways, mail and web servers, remote access, but also systems no one has on their radar anymore. From the inside, what counts is what happens after the first successful step: an attacker is already in the corporate network – via a phishing email, a compromised laptop, or as a malicious insider. How far can they get from there?

It’s especially on the inside that you see how vulnerable an organization really is. Many ransomware attacks follow the same pattern: initial access, lateral movement through the network, takeover of Active Directory, and encryption of servers and backups. An internal pentest shows where you can break this chain – through hardening, better segmentation, and clean privilege management.

Our approach is based on the penetration testing guideline of the BSI (Germany’s Federal Office for Information Security), PTES, OSSTMM, and NIST SP 800-115; we map attack techniques to MITRE ATT&CK. The results support your evidence under Art. 32 GDPR, ISO/IEC 27001:2022 (Annex A 8.8 and 8.20 to 8.22), NIS2, DORA, or PCI DSS 4.0.1 (Requirement 11.4). As a company that is independent of vendors and service providers, we assess your infrastructure objectively.

Our approach

How an infrastructure pentest works

It all starts with the question of what an attacker sees. Externally, we map your public IP ranges, DNS records, subdomains, and certificates and identify reachable services and their versions. Internally, we start from a realistic position – a network port in the office, a standard user account, or a prepared client – and map networks, systems, shares, and the relationships in your Active Directory.

Automated scans only provide leads. We verify every relevant finding manually, rule out false positives, and chain individual vulnerabilities into attack paths: from an intercepted password hash via a poorly protected service account all the way to domain admin rights. Our certified pentesters proceed in a controlled manner – we agree on risky steps on critical systems with you in advance.

Discuss your requirements
We don’t just show vulnerabilities – we show the path an attacker would take.

Common vulnerabilities

Common network and infrastructure vulnerabilities

Vulnerable VPN gateways and firewalls

Edge devices with known, unpatched vulnerabilities are among the preferred entry points because they are directly reachable from the internet. If multi-factor authentication is also missing, a guessed or leaked password is all it takes to get into the corporate network.

Unnecessarily exposed services

RDP, SMB, databases, or the admin interfaces of firewalls, hypervisors, and NAS systems are reachable from the internet even though no one needs them there. Attackers search automatically for exactly these services and try default passwords and known exploits.

LLMNR/NBT-NS poisoning and NTLM relay

When a Windows machine queries an unknown name via LLMNR or NBT-NS, any device on the same network segment can respond – including an attacker’s. The machine then authenticates to it and hands over NTLM hashes that can be cracked offline. If SMB signing isn’t enforced or LDAP signing and channel binding are missing, the attacker can even relay these authentications directly to other systems.

Weak service accounts

Accounts with a service principal name and a weak password can be cracked offline via Kerberoasting, and accounts without Kerberos pre-authentication via AS-REP roasting. Service accounts in particular often have far-reaching privileges.

Misconfigured Active Directory Certificate Services

Insecure certificate templates allow a regular user account to request certificates for arbitrary identities – up to and including domain administrator. Coerced authentications from domain controllers can sometimes be relayed to the certificate authority as well.

Identical local administrator passwords

Without LAPS (Local Administrator Password Solution), many machines share the same admin password. A single compromised client then opens the way to all the others via pass-the-hash.

Credentials in shares and scripts

Passwords in logon scripts, configuration files, spreadsheets, or old Group Policies are often readable by all domain users on network drives or in SYSVOL.

Flat networks without effective segmentation

If clients, servers, production systems, and management interfaces sit on the same network or firewall rules are too permissive, an attacker can spread almost unhindered.

Scope

What we test in a network pentest

We decide together during scoping which areas we test – from a compact perimeter test to a comprehensive assessment of multiple sites.

Test types

External, internal, segmentation – three views of your network

Each test type can be ordered individually. They’re most effective in combination, because real attacks combine an entry from outside with lateral movement inside.

  • External

    External penetration test

    We attack your infrastructure from the internet – just as an attacker would who specifically targets your company.

    • Public IP ranges, DNS, and subdomains
    • VPN, mail, web, and remote access
    • Exposed administration interfaces
    • Can be performed entirely remotely
  • Internal · Assumed breach

    Internal penetration test

    We start inside the network – with a network port, a standard account, or a prepared client – and test how far an attacker can get from there.

    • Active Directory, Kerberos, and NTLM
    • Lateral movement and privilege escalation
    • Access to servers, data, and backups
    • On site or remotely via VPN or a provided test system
  • Segmentation

    Segmentation test

    We verify whether your network zones are actually separated the way your network design intends.

    • Client, server, guest, OT, and management networks
    • Firewall rules and ACLs from an attacker’s perspective
    • Proof of network separation, e.g., for PCI DSS 4.0.1

Process

From scoping to retest

An infrastructure pentest touches your live operations. That’s why we plan every step transparently and with clear agreements – following our proven approach to penetration testing.

  1. 01

    Scoping & rules of engagement

    We define IP ranges, sites, the starting point for the internal test, testing windows, exclusions, and contacts for questions during the test. You receive your fixed-price quote within 24 hours of scoping (on business days).

  2. 02

    Reconnaissance & mapping

    Externally, we map your attack surface; internally, we map networks, systems, services, shares, and permission structures in Active Directory.

  3. 03

    Vulnerability analysis

    We combine automated scans with manual verification, filter out false positives, and assess every finding in the context of your environment.

  4. 04

    Exploitation & attack paths

    We exploit vulnerabilities in a controlled manner, chain them together, and demonstrate lateral movement and privilege escalation – as far as the agreed rules of engagement allow.

  5. 05

    Report & debrief

    You receive an executive summary, findings with CVSS ratings, documented attack paths, and prioritized measures. On request, we present the results to your team.

  6. 06

    Retest & test certificate

    Once you’ve remediated the findings, we retest the affected vulnerabilities free of charge. After the test is complete, you also receive a test certificate.

Your benefits

Why choose Rootsektor for your infrastructure pentest

  • Attack paths instead of scanner lists

    We show how vulnerabilities can be chained together – and where you can break the path with the least effort.

  • Fixed price after scoping

    Predictable costs with no hidden items and no additional charges for the agreed scope – even across multiple sites.

  • Free retest

    We check whether your hardening measures are effective – without any new costs for you.

  • Test certificate

    Proof for customers, partners, insurers, and auditors – for example, in ISO 27001 audits or supplier assessments.

NETWORK & INFRASTRUCTURE · INTERNAL & EXTERNAL

Reporting

A report that sets priorities

An infrastructure pentest often produces a long list of findings. What matters is what needs fixing first. Our report rates every finding using CVSS and by its role in the attack path, and it distinguishes quick, immediate fixes from structural improvements such as a tiering model for administrative accounts.

  • Executive summary for senior management and IT leadership
  • Findings with CVSS ratings, evidence, and affected systems
  • Clearly documented attack paths
  • Prioritized recommendations, from immediate fixes to structural hardening
  • Debrief on request
  • Free retest and test certificate

Do you know what an attacker sees in your network?

A pentest gives you the answer – with concrete evidence and a clear plan for the next steps. Request your fixed-price quote now.

FAQ

Frequently asked questions about network penetration testing

Didn’t find your question? Call us at +49 2932 465265-0 or email info@rootsektor.de.

What is the difference between an internal and an external penetration test?

The two tests answer different questions. The external test determines whether an attacker on the internet can find a way in at all – through an unpatched VPN gateway or an open remote access point, for example. The internal test starts where the external one ends: it assumes successful initial access and shows which systems, data, and privileges can be reached from there – up to and including a takeover of Active Directory.

Do we need both tests?

In most cases, yes. An external test alone leaves open what happens after a successful phishing attack; an internal test alone says nothing about the attack surface of your perimeter. If your budget is limited, we’ll advise you on which perspective makes the most sense first for your risk situation.

What does “assumed breach” mean?

In an assumed breach scenario, we assume that an attacker already has a foot in the door – for example, via a compromised laptop or a stolen user account. Instead of spending time on initial access, the test focuses on what happens next. That’s realistic, because phishing and stolen credentials are common ways in.

Can an internal pentest be performed remotely?

Yes. We perform the internal test either on site or remotely – via VPN access or a provided, preconfigured test system in your network. For segmentation tests at multiple sites or in production environments, an on-site visit can make sense – we work for you in Germany and internationally.

Is a network pentest the same as a vulnerability scan?

No. A vulnerability scan finds known vulnerabilities automatically and is suited to ongoing monitoring – for example, with solutions from our partner Greenbone. A penetration test goes further: we check manually whether findings can be exploited and chained together, and we uncover misconfigurations that no scanner detects. Learn more on our vulnerability assessment page.

Will the test affect our operations?

We work in a controlled manner and agree on testing windows, exclusions, and contacts in advance. We don’t perform denial-of-service tests unless they are explicitly agreed, and risky steps on critical systems only take place after consultation. For sensitive environments such as production networks, we plan with particular care.

How often should we have our network tested?

We recommend at least one test per year plus additional assessments after major changes, such as a firewall migration, a new VPN solution, changes to Active Directory, or an acquisition. PCI DSS 4.0.1, for example, requires internal and external penetration tests at least every twelve months and after significant changes.

How much does a network penetration test cost?

The price depends on the number of IP addresses and sites, the size of your Active Directory, and the depth of testing you need. After scoping, you receive a fixed-price quote within 24 hours (on business days) – with no hidden costs and including a free retest.

Have your infrastructure tested

Tell us which sites, systems, and goals you have in mind. We’ll get back to you to arrange a no-obligation initial consultation and send you a fixed-price quote within 24 hours of scoping (on business days).

Fields marked with * are required.

For questions or a callback

We will get in touch and, if you wish, sign the non-disclosure agreement before our first conversation – including on the basis of your own template.

We use your information solely to process your request. For more information, see our privacy policy. Please do not send passwords or login credentials through this form.