Go to all blog posts

Cybersecurity Is Now Part of the Job: What the New CoESS-Euralarm Guidelines Mean for Installers and ARCs

Key takeaways

  • The updated CoESS-Euralarm guidelines make cybersecurity a core quality and legal requirement for everyone in the security and fire safety chain, driven by NIS2 and the Cyber Resilience Act.

  • They set out five stages (product, project design, installation and maintenance, monitoring and alarm response), each with its own risks, from misconfiguration and unpatched devices to attackers moving laterally across networks.

  • Most of these risks can be reduced with practical steps such as changing defaults, enabling multi-factor authentication, separating networks and keeping systems updated, and Netcelero’s secure connectivity helps installers and ARCs put them in place.

Why these guidelines matter

Cybersecurity is no longer an optional extra in the security and fire safety industry. It is now a quality requirement, and for many businesses it is also a legal one.

That is the central message of the updated cybersecurity guidelines from CoESS and Euralarm, the European bodies representing private security services and the fire safety and security industry. The guidelines are written for everyone in the value chain: manufacturers, system designers, installers, maintainers, Alarm Receiving Centres (ARCs) and alarm response teams.

Their starting point is simple. Anything connected can be attacked, whether it is a camera, a fire panel or a software platform. One weak link can be enough to compromise a protected site and the businesses that rely on it.

The encouraging news is that good cybersecurity does not always need complex technology or a large budget. Many risks can be reduced with basic, well-applied measures. Below, we walk through the guidelines’ five-stage approach and what each stage means in practice for installers and ARCs.

The five stages, and what they mean in practice

The guidelines follow a five-pillar approach that covers the full lifecycle of a security system, from the product itself through to the response when an alarm is raised. Each stage carries its own risks and its own responsibilities.

1. Product

Devices should be secure by design and secure by default. That means strong access control and authentication, secure storage and communication, logging, a way to apply updates safely, and a reduced attack surface. Under the EU Cyber Resilience Act, this approach becomes a legal requirement for manufacturers from December 2027.

Where Netcelero fits: the i-ctrl does not expose its management interfaces, such as SSH or its web interface, on its public connection. It is managed over a private VPN that the device itself opens to our core network, and firmware updates are delivered centrally over that same secure path.

2. Project design

Good design starts with a security risk assessment and a clear understanding of what the customer needs to protect. Where a system connects to a remote server or cloud platform, for remote access, servicing or alarm transmission, the risks to that IT infrastructure need to be considered too.

Where Netcelero fits: our Cookbook of reference designs includes cyber notes for every configuration, so you can see the potential weak points before you install. Features such as VLAN support and Dual Static IP make it straightforward to keep systems like CCTV and SCADA separated from day one.

3. Installation and maintenance

The guidelines point out that installation brings no new external threats, but it does introduce the risk of misconfiguration. Default passwords should be changed, user accounts set up properly, encryption switched on and unnecessary settings disabled. Updates should be installed as soon as they are available, and users should be told clearly how to operate the system securely.

Where Netcelero fits: centrally managed firmware updates take one task off the installer’s list. On site, we recommend using managed switches with VLANs and port isolation, disabling UPnP on third-party routers, and enabling multi-factor authentication on every Netcelero portal account.

4. Monitoring

For ARCs, the major concern is lateral movement: an attacker gains a foothold on one device and moves quietly through the rest of the IT and OT estate. The guidelines recommend placing internet-facing devices on an isolated network, allowing them to communicate only with approved systems, denying all unauthorised traffic and keeping event logs.

Where Netcelero fits: Netcelero provides a static IP and secure VPN access without exposing the customer’s wider network. The i-ctrl firewall supports geo-locking and traffic rules, Secure Link encrypts traffic from the site itself, and the Netcelero portal logs logins, configuration changes and connection attempts.

5. Alarm response

When an alarm is verified, the ARC may alert the customer, a mobile patrol or the police. Alarm data, CCTV footage, communications and access control can all be targeted, so the integrity and availability of the communication path matter just as much here.

Where Netcelero fits: automatic failover and failback across 4G, 5G, Starlink and fixed lines keeps the path to site available, backed by our dual data centres in Dublin and Amsterdam.

The regulation behind it

NIS2 takes a supply chain approach. Even if your business is not directly in scope, your customers may be, and they will increasingly expect their security and connectivity suppliers to demonstrate good practice.

RegulationWho it affectsKey dates
NIS2 Directive (EU) 2022/2555Essential and important entities, including many critical infrastructure operators, and the suppliers in their supply chainMember States were required to transpose it into national law by 17 October 2024
Cyber Resilience Act (EU) 2024/2847Manufacturers and suppliers of connected products, including alarm systems, cameras, access control and remote monitoring softwareReporting of actively exploited vulnerabilities and severe incidents from 11 September 2026; full application from December 2027

The CRA reporting deadlines are tight. Manufacturers must send an early warning within 24 hours of becoming aware of an actively exploited vulnerability or severe incident, followed by a full notification within 72 hours, and a final report once the issue has been addressed. Reports are submitted through ENISA’s Single Reporting Platform. The European Commission sets out the full detail on its CRA reporting obligations page.

NIS2 takes a supply chain approach. Even if your business is not directly in scope, your customers may be, and they will increasingly expect their security and connectivity suppliers to demonstrate good practice.

The guidelines also note that the EU is considering further simplification of its cybersecurity framework, particularly around incident reporting. If your organisation is unsure how these rules apply to it, independent legal or compliance advice is the best next step. In Ireland, the National Cyber Security Centre is a useful starting point, and UK readers can turn to the National Cyber Security Centre.

A practical checklist for installers and ARCs

None of these steps needs a large budget, and each one reduces risk straight away.

  • Know what is connected. Keep an up-to-date inventory of the devices on each site, including firmware versions and vendor contacts.
  • Assess the risk before you design. Understand what the customer needs to protect and where the system connects to the outside world.
  • Change every default. Replace default passwords and set up individual user accounts on every device.
  • Switch on multi-factor authentication. Enable it wherever it is offered, including on your connectivity and monitoring portals.
  • Separate your networks. Use VLANs and port isolation so that a compromised camera cannot become a route into the rest of the network.
  • Close what you don’t need. Avoid open port forwards where a VPN will do, and disable UPnP and unused services on routers.
  • Keep everything up to date. Apply security updates promptly and check that devices are still supported by their manufacturer.
  • Plan for the bad day. Agree responsibilities with your customer and test your backup and incident procedures before you need them.

Cybersecurity is part of the job

The CoESS-Euralarm guidelines make one thing clear: every actor in the security chain now shares responsibility for cybersecurity. The good news is that the right foundations make that responsibility far easier to carry.

At Netcelero, secure connectivity is what we do. Our solutions give installers and ARCs a fixed, secure path to site over any connection, including 4G, 5G and Starlink, without exposing the customer’s network.

If you would like to talk through how these guidelines apply to your sites, or which Netcelero configuration fits best, our team will be glad to help. Get in touch with us today.