External network penetration test
How vulnerable is your network from the internet?
From remote working access to public servers: we examine where an attacker could gain entry, what they could reach and which measures are needed first.
From the outside in
Three questions we answer
- Which systems are accessible?
- Which vulnerabilities can demonstrably be exploited?
- Which measures should take priority?
When is this relevant?
Which systems are accessible from the internet after a change?
A new firewall, remote working access or an additional supplier: your environment changes. We examine which systems become accessible from outside as a result.
- You want to know which services are accessible from the internet.
- You have changed VPN access, servers or other external access.
- A customer, auditor or internal review requires insight into security.
- You want to support remediation measures with demonstrable risks.
The assessment
What do we assess?
Your environment and assessment question determine the content. We agree in advance which elements we will examine.
01
Internet-accessible systems and services
We map the agreed IP addresses, domains and publicly accessible services. Where it fits the scope, we use public technical information to supplement the picture.
02
Access and configuration
We examine VPN portals, administration interfaces and other access points, among other things. What information do they reveal, how is access configured and which settings could allow misuse?
03
Vulnerabilities and attack paths
Our ethical hackers use technical tools and manually test whether a vulnerability can actually be exploited. We demonstrate what access is possible and what the consequences could be.
04
Impact and priorities
You receive an evidence-based order for remediation. We explain what needs attention first, which measures are connected and which questions need further investigation.
Defining the scope together
A scope that fits your question.
We agree in advance which systems we will examine, from which perspective and with what access. This also covers testing windows, contacts and arrangements for serious findings.
What do we agree in advance?
- Domains, IP addresses and external services in scope.
- Black-box testing or an assessment with additional information and, where relevant, test accounts.
- Permission and conditions from the administrators and suppliers involved.
- Test schedule, permitted activities and availability during testing.
Would you also like us to examine processes within a web application, API authorisation or the internal network environment? We then combine the appropriate assessments in the proposal.
The result
From a finding to a targeted measure.
01
A clear assessment
A summary of the assessment, the main risks and what they mean for your organisation.
02
Findings with evidence
Technical findings with supporting evidence, impact and practical remediation advice for IT and administrators.
03
Managing the follow-up
Priorities and an explanation from the specialists. Any retest is agreed separately.
Our approach
From the initial question to follow-up.
01
Intake and scope
We discuss your reason for the assessment, your external environment and the desired outcome.
02
Assessment
Our ethical hackers carry out the agreed assessment. We discuss serious findings immediately.
03
Report and explanation
You receive the findings and advice, with time to go through the results together.
04
Follow-up
You implement improvements. If required, we then examine whether the risk has been sufficiently addressed.
Frequently asked questions
What you need to know in advance.
How does this differ from a vulnerability scan?
A scan helps identify potential vulnerabilities. In this penetration test, our specialists investigate the findings further and test what is actually possible within the scope. The connections between findings and their impact determine the advice.
Is an external penetration test also a full web application test?
An externally accessible application portal can be part of the external environment. For an in-depth assessment of roles, business logic and API authorisation, we define the scope of a web application or API test separately.
How long does the assessment take?
That depends on the size of the environment, the accessible services and the depth of the question. We define the scope during intake; the proposal sets out the effort required and the schedule.
Can you test our production environment?
We discuss this in advance. We adapt testing to the environment and agree on testing windows, contacts and stopping tests if unexpected effects occur. Tests that disrupt availability are outside the standard scope.
What happens after the report?
You can act on the remediation advice. We explain the results and can arrange a retest. The penetration test assesses the scope examined at the time of testing.
Our approach
From assessment to clear next steps.
Read how we define the scope, carry out the assessment and discuss the results with you. With a dedicated secure data room and evidence-based reporting.
Discuss your situation
Know what is accessible from outside.
Tell us which environment you want assessed and why. Together, we define the scope and the next step.
The form is currently unavailable. Use our general contact form or call 036 5367 573.
We use your details to handle your enquiry. Read our privacy policy.