Firewall and VPN

We design, install, and configure next-generation firewalls, together with VPN for site-to-site and remote access.

When you need it

When your current firewall is no longer enough

Any one of these is reason enough to redesign the protection of your network perimeter.

  1. Expired vendor support

    Once vendor support for the device has ended, or is about to, it no longer receives security updates.

  2. Encrypted traffic filtered blind

    Most traffic today is TLS. If the hardware cannot keep up with inspecting encrypted traffic, it is effectively filtering that traffic blind.

  3. Port-based rules only

    An older device sees ports and addresses. A next-generation firewall also recognizes the application, so you can write rules for that as well.

  4. A rule set that has grown out of control

    If nobody dares to touch the rules anymore, nobody knows the real state of your perimeter defense either.

Rollout

How a firewall project is structured

A firewall is only as good as the fit between its rule set and the traffic your organization really needs. That is why we spend more time on design than on installation.

  1. Traffic analysis and zone design

    We map who actually communicates with whom and which services need to be reachable. The design builds on that: the zones of the network and the traffic allowed between them.

  2. Installation and rule building

    We deliver and install the devices, then build the rule set from the design on the principle of least privilege: anything not explicitly allowed is denied.

  3. VPN configuration

    We configure the VPN that links your sites and accepts connections from remote users.

  4. Go-live and fine-tuning

    After go-live we fine-tune the rules based on real traffic and, if you need it, feed the firewall logs into the SIEM. Finally, we hand the system over to your administrators along with the documentation.

VPN

Connecting sites and remote users

A VPN builds an encrypted channel across the public internet. A VPN running on the firewall is also the entrance to your network, so we design its protection together with the firewall.

  1. Site-to-site VPN

    Branch networks and sites reach headquarters, and each other, through an encrypted tunnel.

  2. Remote access

    IPSec or SSL VPN for remote work and for the maintenance channels of external suppliers.

  3. Multi-factor authentication

    Of all the services reachable from outside, the VPN is the first one where MFA is worth turning on. If a password leaks, it is not enough on its own to log in.

  4. Access governed by rules

    A user who connects over the VPN lands on the network. Firewall rules and segmentation decide what they can reach from there.

Deliverables

What you get at the end

items handed over

  • Requirements assessment and solution design
  • Equipment delivery, installation, and rule set
  • VPN with multi-factor authentication
  • 30 days of tuning, administrator handover, and documentation

Technologies and references

What we use and where

Our design work is vendor-independent: we choose the solution to fit your environment and the equipment you already have. We have active partnerships and deployment experience with the vendors below.

References

Hungarian Dance University
FortiGateWe deployed a new firewall system with full UTP functionality. Critical systems and web servers were moved into separate VLANs, and the firewall filters the traffic between the VLANs.
Municipality of Gödöllő
FortiGate, FortiAnalyzerWe built a redundant firewall system. The firewalls of external institutions, kindergartens, and nurseries were brought under central management, so rules and logging can be handled centrally.

Frequently asked questions

What people ask about firewalls and VPNs

Is a firewall at the perimeter enough?

Not on its own. A typical incident today starts with phishing or a stolen password, which gets around perimeter defenses: the attacker is already working from the inside. That is why you also need internal network segmentation. At a minimum, critical systems (domain controllers, backup infrastructure, financial systems) belong in their own segment. We cover this in more detail in our Zero Trust architecture guide.

What happens if a rule is wrong and a service goes down?

To prevent that, we cut over in stages, and the rule set runs in monitor mode first: it logs but does not block, so faulty rules come to light without affecting live traffic. Every step has its own rollback plan and time window.

Does ZTNA replace the VPN?

Partly. Switching pays off most when many external parties need access or the organization mostly uses cloud applications. For legacy applications that do not run over HTTP, the VPN usually stays. We go into detail in our comparison of VPN and ZTNA.

Does the same firewall work in an industrial environment?

No. A general-purpose firewall sees Modbus or S7comm traffic as a single TCP port, so it cannot tell a read from a write or from a program download. An OT environment needs a device that understands the function codes of these protocols, which lets you write a rule such as “from this segment, the PLCs are read-only.” Virtual patching matters too, because it can protect devices that cannot be updated. We wrote about this in detail in our article on OT endpoint protection, and our industrial services are collected on the OT security page.

Contact

Ready to secure your critical systems?

Our experts will assess where your security stands and build a roadmap that fits your organization.

ARLITECH's office in Gödöllő

Visit us

You are welcome to visit our Gödöllő office in person.

Address
Centrum Office Building, 2100 Gödöllő, Dózsa György út 13, 3rd floor, office 309
Office hours
Mon–Fri, 9 a.m. to 5 p.m.
Get directions (opens in a new tab)