External attack surface
Public IP addresses, domains, subdomains, open services, VPN, RDP, SSH, mail and web services.
Reduce infrastructure risk before an audit, NIS2 preparation or important network changes. We assess what an attacker can see from the internet and what possible attack scenarios appear after gaining access to the internal network.
Public IP addresses, domains, subdomains, open services, VPN, RDP, SSH, mail and web services.
Servers, workstations, network segments, access paths, services and possible internal movement routes.
AD configuration, privilege paths, accounts, groups, weak passwords and credentials exposure.
Public services, administration panels, TLS/SSL configuration and infrastructure misconfigurations.
When network risks, priorities and preparation steps need to be clearly understood.
When VPN, firewalls, servers, cloud services, segmentation or access rules have changed.
When you need to assess what an attacker can see from the internet and what could happen after internal access.
Define scope
Get access
Perform testing
Deliver report
Review recommendations
We agree whether the assessment covers the external network, internal network, Active Directory, cloud services or a specific infrastructure area.
We align IP ranges, domains, testing windows, VPN or internal access, user permissions and actions that must not be performed.
We check public services, known CVEs, configuration, AD risks, privilege paths, segmentation and possible lateral movement.
You receive prioritized findings, reproduction steps, organizational impact and clear remediation recommendations.
We discuss what to fix first, how to reduce risk and how to plan retesting after remediation.
We clearly show which services, domains, IP addresses and configurations are visible from the internet.
Risks are ordered by organizational impact and likelihood of exploitation.
The technical team sees how the issue was validated and under which conditions it appears.
We explain what the risk means for access, data, business continuity and incident likelihood.
If internal movement paths are found, we provide recommendations to reduce lateral movement risk.
After remediation, important network and infrastructure issues can be retested.
Yes. You can start with external attack surface assessment: public IPs, domains, subdomains, open services and configuration checks.
It depends on scope. Usually VPN or agreed internal access, a testing window and clear boundaries for prohibited actions are needed.
Timeline depends on scope: a small external IP or domain set can take a few days, while a broader internal network or Active Directory environment is scoped individually.
The report includes scope, methodology, risk priorities, technical findings and recommendations, so it can support audit preparation or internal risk management.
Send a short description of IP ranges, domains, network or Active Directory scope. We will respond with a realistic testing scope and a practical starting point.