What is the difference between external and internal testing?

External testing looks at what anyone on the internet can reach. Internal testing assumes an attacker already has a foothold inside, such as a compromised laptop, and measures how far they can get from there.

Will testing disrupt our systems?

We agree rules of engagement before starting, including what is off limits, testing windows and who to call if something looks wrong. Disruptive techniques are only used with explicit approval.

Network and Infrastructure Penetration Testing

Network and infrastructure penetration testing

Network penetration testing finds the ways into and across your infrastructure. HYDN tests external perimeters for exposed services and weak access, and internal networks for misconfigurations, weak credentials, unpatched systems and lateral movement paths, starting where an attacker would and going as far as the agreed scope allows.

External testing

Discovery of internet-facing hosts, services and forgotten assets.
Exposed management interfaces, remote access gateways and VPNs.
Weak or default credentials and credential stuffing exposure.
Unpatched services with known exploits.
Email security and DNS configuration.

Internal testing

Active Directory. Weak configurations, excessive privileges, Kerberos attacks and paths to domain admin.
Segmentation. Whether networks that should be separate can reach each other.
Credentials. Passwords in scripts and shares, reuse between systems, and hashes that can be cracked or relayed.
Lateral movement. How far an attacker can travel from one compromised machine.
Unpatched and legacy systems that are still reachable.

For crypto and fintech teams

The machines that sign transactions, run nodes and hold keys sit on these networks. Many of the largest crypto thefts started with a compromised internal system rather than a contract bug. For that scenario, see assumed breach testing.