01
Network review
We collect configuration, connection, application, VPN and licence information. We check dependencies and identify rules whose removal needs the service owner’s decision.
Network edge protection
Business firewall deployment
We select and configure firewalls to control connections between the Internet, your company network and its separate segments. Equipment replacement is planned with critical-service tests and a way to restore the previous configuration.
Trusted by
Companies and institutions that need stable IT.
Who can connect to what?
As a company adds applications, firewall rules from old projects can remain in place. We help establish which connections are needed, who approves them and what can be disabled. We separate access for employees, guests, servers and administrators. The work can involve a new firewall, equipment replacement or a review and cleanup of the existing configuration.
Related network protection work
Replacing a firewall may require changes to the network or remote access. We agree the scope of those changes separately.
Network deployment
Design and configuration of LAN, Wi-Fi and separate segments for employees, guests and systems.VPN deployment
Connections for remote employees and branch offices, with a defined scope of access.Network audit
Review of existing connections, configuration and permissions before changes are agreed.IT monitoring
Checks on firewall and service availability, with notifications sent to agreed contacts.ISO 27001 · TÜV NORD Polska
TÜV NORD Polska has certified Virtline’s information security management system to PN-EN ISO/IEC 27001:2023-08. The published certificate states its scope and validity.
View Virtline’s certificateFirewall implementation process
Before switching over, we agree which services must work, when the change can take place and who will accept the result.
02
Design and preparation
We select a solution and define zones and access. We prepare the configuration, a backup of current settings, the test plan and a way to reverse the change.
03
Migration and tests
We switch the agreed scope during a maintenance window. Together with the application contacts, we verify important connections and handle problems under the agreed plan.
04
Acceptance and handover
We discuss results, hand over documentation and record outstanding tasks. We agree an initial configuration review and the scope of further support.
Practical scope
What we hand over
At acceptance, we check the agreed services and record limitations and outstanding work.
A firewall with the agreed zones, routes, access rules and NAT. We document the purpose of important rules, their approvers and the duration of exceptions. Filtering and IPS functions depend on the scope and licences.
We check the specified applications, VPN connections and Internet-facing services. Failover is tested if that arrangement is part of the project. Results and any limitations are documented.
We hand over a configuration backup, details of administrative access and a way to restore the previous settings. We agree where documentation is kept and how credentials are transferred securely.
We describe change requests, rule reviews, updates and alert recipients. Maintenance by Virtline, support hours and response times require a separate agreement. We can agree forwarding security logs through syslog or an available connector to SIEM. The test checks that a selected event arrives and can be read; monitoring firewall availability alone does not verify this integration.
Choosing equipment and features
We work with Fortinet, Palo Alto, Cisco, pfSense and OPNsense. We check the specific model, version, vendor support, licences and performance with the required features enabled. Encrypted traffic inspection requires a separate agreement on scope and application impact. A firewall does not replace endpoint protection, backups or incident response. Before TLS inspection, we also agree privacy safeguards, exclusions for sensitive traffic categories, access to results and their retention. The designated people responsible for data and security approve these rules.
Firewall deployment questions
Will replacing the firewall interrupt our work?
+
It may require an interruption. Its extent depends on the equipment, connections and switchover method. Before migration, we agree a maintenance window, tests and conditions for restoring the previous configuration. We do not promise a zero-downtime migration before examining the environment.
Do we need to buy a new firewall?
+
Not always. We first check the current model, support status, licences, performance and required features. If configuration changes are sufficient, we can propose that scope instead of replacing the equipment.
What determines the cost?
+
The number of sites, rules and VPN tunnels, required performance, licences, tests and migration scope. We separate equipment and licence costs from implementation work and subsequent maintenance.
Can you manage the firewall afterwards?
+
Yes. Under an agreed scope, we can handle rule changes, updates, configuration backups and reviews. The agreement defines service hours, response times, responsibilities and how to request work.
Let’s plan your network change
Tell us the current firewall model, number of sites and reason for the change. Include your target date if you have one. Do not send passwords or a full configuration through the form.
Discuss firewall deployment