01
Scope agreement
We discuss the objective, environment and restrictions. We confirm authorisation, access arrangements, dates and how results will be delivered.
Network pentesting
Network penetration testing
We check whether internet-facing services or the company network allow unauthorised access to systems and data. You receive a description of confirmed findings, their business impact and recommended fixes.
Trusted by
Companies and institutions that need stable IT.
A test tailored to your infrastructure
A penetration test is a controlled examination of possible attack paths. Before work starts, we agree the objective, permitted activities and specific addresses, locations and systems. Scanning identifies areas for investigation; we manually verify findings within the agreed scope.
What we can test
We select the areas you need. An external test does not automatically include the internal network or Wi-Fi. The form offers three standard scopes: web application or API, network and servers — external testing, and network and servers — internal testing. We discuss Wi-Fi, VPN, OT systems and combined or custom scopes in a consultation before preparing a quote.
Internet-facing services
We examine the agreed public addresses and services for exposed administration interfaces, information disclosure, vulnerabilities and configuration issues.Internal network
We check which resources can be reached from an agreed starting point. This includes segmentation, permissions and access to servers, files and backups.VPN and remote access
We examine sign-in controls, additional authentication requirements and the access granted after connection, including employee and supplier accounts.Wi-Fi networks
We assess the agreed wireless networks, authentication and separation of guests and devices from company systems.What you receive after the test
The report separates findings confirmed during testing from areas we could not assess.
Management summary
The main findings, potential business consequences and recommended priorities, without requiring managers to interpret raw scanner output.Technical findings
Vulnerabilities, affected resources, reproduction conditions, test results and recommended changes, delivered through the agreed secure channel.Remediation tasks
A list of fixes and priorities. We discuss implementation responsibilities with your team and identify changes worth testing again.ISO 27001 · TÜV NORD Polska
Virtline’s information security management system is certified by TÜV NORD Polska. The published certificate specifies its scope and validity.
View Virtline’s certificateHow our cooperation process works
The scope and schedule depend on the systems and scenarios agreed, rather than a single fixed package.
02
Discovery and verification
We identify services and potential vulnerabilities. We manually verify findings and agreed scenarios for reaching other resources.
03
Report and discussion
We describe confirmed findings, test limitations and recommendations. We communicate serious findings through the agreed channel and discuss remediation priorities.
04
Checking fixes
Where included in the agreed scope, we reassess specified findings after changes have been implemented and update their status.
Practical scope
Ground rules before testing begins
No test can be guaranteed entirely risk-free. Agreed restrictions and communication with administrators help manage the risk.
We confirm permission to test, in-scope addresses and systems, and excluded resources, including those belonging to other providers.
We agree working hours, contact people and circumstances in which testing must stop immediately.
We agree test accounts, permitted information access and how test evidence will be protected and transferred.
Industrial equipment and critical systems require separately agreed methods and restrictions with their owners.
Checking again after remediation
A retest addresses specified previous findings, not automatically the entire network. We agree its scope, timing and cost in the proposal or separately. The results identify issues that have been resolved, mitigated or remain open.
Questions about penetration testing
Does the test include the internal network?
+
Yes, if it is included in the agreed scope. We define the access point, segments and systems to assess and any accounts required. Testing public addresses alone does not replace an internal test.
Could testing disrupt the business?
+
That risk exists. Before work starts, we agree permitted techniques, testing hours, excluded systems and stopping conditions. Activities involving sensitive services require agreement with their owners.
Is checking the fixes included in the price?
+
This depends on the agreed proposal. Before testing, we specify whether a retest is included and which findings it covers. If ordered separately, we agree its cost and timing before carrying out the work.
How does a penetration test differ from a network audit?
+
A penetration test checks whether vulnerabilities can be exploited in agreed scenarios. An audit more broadly assesses architecture, settings, documentation and network management. They can complement each other; the choice depends on your objective.
Let us define your network test
Tell us the approximate number of public addresses, locations and segments, and whether you need internal, VPN or Wi-Fi testing. Include your preferred timing and important operational restrictions. Do not send passwords or confidential documentation.
Discuss a network test