ValarContact

Solutions

Different sectors, different obligations.

Which network security requirements apply depends on sector and size. Here you can see how Valar is typically used.

01 / Practices

Medical and dental practices.

In Germany, practices must follow the IT security guideline under Section 75b of the Social Code Book V. Among other things, it requires a firewall at the internet boundary. Most practices, however, are not covered by NIS2.

Valar 1 suits a practice with up to about 25 users. With several sites, all units are managed centrally with the same rules, and access to specialist systems runs over VPN.

Valar 1

02 / Mid-sized companies

Industry and services.

In mid-sized companies, office, production and often guests share the same network. Valar separates these areas. Machines only reach what they actually need.

SSL inspection can be switched on for office traffic and deliberately left off for production. Two Valar 2 units as a pair make sure a hardware failure does not stop operations.

Valar 2

03 / NIS2

NIS2 and network security.

NIS2 generally applies to companies in certain sectors with 50 or more employees or more than 10 million euros in turnover. It calls for measures on network security and supply chain security, among others.

A firewall alone does not make you NIS2 compliant, but it is a central building block. For your evidence, we provide documentation on the origin of the software, updates and data residency.

04 / Critical infrastructure and public sector

Critical infrastructure, public authorities.

Energy suppliers, hospitals and public administrations need high availability and must be able to show where software and updates come from when they procure.

Valar 3 and Valar 4 are designed for data centre operation, and Valar 4 can also run as a cluster across two sites. Tender documentation with technical data sheets and supply chain evidence is available on request.

Valar 3Valar 4

Application examples

What this looks like in practice.

Three typical setups as we plan them with customers and partners. The examples are simplified and show which model fits which purpose.

Example · Valar 1

Group practice with three sites

Starting point

A group practice with 18 staff at three sites. So far, each site has a simple internet router and the practice network is not segmented.

Setup with Valar

  • One Valar 1 per site
  • Separate areas for practice management, medical devices, telephony and guest Wi-Fi
  • Sites are connected via IPsec VPN
  • All appliances are managed centrally with the same rules
  • Basis for the evidence required by the applicable IT security rules

Valar 1

Example · Valar 2

Machine builder with connected production

Starting point

A mid-sized machine builder with around 90 office workstations and connected machines in production. Office and production networks are not yet separated.

Setup with Valar

  • Two Valar 2 as a high-availability pair
  • Separate zones for office, production, servers and guests
  • Machines only reach the systems they need to operate
  • SSL inspection for office traffic, deliberately not for production
  • Field staff and home offices via WireGuard VPN

Valar 2

Example · Valar 4

Regional energy supplier

Starting point

An energy supplier with two data centres. Control systems and office network must be strictly separated, and the origin of software and updates must be traceable.

Setup with Valar

  • Valar 4 as a cluster across both data centres
  • Strict separation of control and office networks
  • Findings from NeoI feed into the existing SOC
  • Documentation on software, updates and supply chain for internal audits and procurement

Valar 4