CER Directive: what critical entities need to prove about site access

This guide covers what CER means for visitor and contractor access, with practical checks to help teams find gaps and strengthen site resilience.
Nov 17, 2026
Quentin Bosman
Quentin Bosman
Head of Customer Success - EMEA
CER Directive: what critical entities need to prove about site access

If your organisation was notified as a critical entity by an EU member state in July, your risk assessment is due by April 2027 and your resilience duties apply from May. That leaves a short runway to check how your sites control access and prepare for disruption.

When a competent authority looks at your sites, the questions are simple. Who was on site? Who approved them? When did their access end? Most organisations have the controls to answer them, but far fewer can prove it quickly, across every site, without rebuilding the story from emails and spreadsheets.

This guide covers what CER means for visitor and contractor access, with practical checks to help teams find gaps and strengthen site resilience.

What is the CER Directive?

The Critical Entities Resilience (CER) Directive is the EU’s framework for keeping essential services running. Formally, it’s Directive (EU) 2022/2557 on the resilience of critical entities. It replaced the 2008 European Critical Infrastructure Directive, which covered energy and transport and prioritised protection against terrorism.

The new directive takes an all-hazards approach. Critical entities must prepare for natural disasters, accidents, terrorism, sabotage, insider threats and public health emergencies, and be able to prevent, protect against, respond to and recover from incidents that disrupt their essential services.

Like NIS2, CER is a directive, not a regulation. Each member state writes it into national law, so organisations should check their national requirements as well as the EU framework.

Who the CER Directive applies to

CER covers eleven sectors: 

  • Energy
  • Transport
  • Banking
  • Financial market infrastructure
  • Health
  • Drinking water
  • Waste water
  • Digital infrastructure
  • Public administration
  • Space
  • Production, processing and distribution of food

Working in one of these sectors doesn’t automatically make your organisation a critical entity. National authorities decide based on the services you provide, where your infrastructure is located, and what would happen if those services stopped. They consider how many people depend on your services, who would be affected by a disruption, and what alternatives would be available.

How to confirm your organisation’s status

Authorities must notify entities when they’re identified as critical. If you operate in a CER sector across several countries, each of your EU entities may have a different answer. Check with your legal team and the relevant competent authority rather than relying on a public list. 

Which sectors have exemptions?

Different rules apply to banking, financial market infrastructure and digital infrastructure. Under Article 8, critical entities in these sectors are exempt from CER’s core resilience duties, although national laws may add requirements. For data centres, start with NIS2. Financial entities also need to consider DORA.

How CER affects UK-based organisations

CER is an EU directive and doesn’t directly apply to UK sites. But UK-headquartered groups with EU operations in energy, food, transport or health may find those EU entities designated. Having a consistent visitor and contractor process can help security teams manage the estate, while allowing for local requirements.

Key deadlines

Your notification date starts the clock, so be sure to check it alongside your national authority’s guidance to confirm which deadlines apply to your organisation.

Scroll horizontally to view all columns on smaller screens.

When What happens
December 2022 CER Directive adopted alongside NIS2.
17 October 2024 Deadline for member states to transpose CER into national law.
17 January 2026 Deadline for national resilience strategies and member state risk assessments.
13 July 2026 Article 13 guidelines published in the Official Journal as C/2026/3712, following adoption on 10 July.
17 July 2026 Deadline for member states to identify critical entities.
Within nine months of notification Entity risk assessment under Article 12.
10 months after notification Chapter III resilience duties apply under Article 6(3), subject to Article 8.

For example, an entity notified on 17 July 2026 reaches the nine-month milestone on 17 April 2027 and the ten-month milestone on 17 May 2027. Identification and notification are separate events, so July designation does not automatically mean a May deadline.

What Article 13 means for your sites

Article 13 is where CER becomes operational. Critical entities subject to these duties must take appropriate and proportionate technical, security and organisational measures, based on their risks, to:

  • Prevent incidents and physically protect premises and critical infrastructure.
  • Respond to incidents and restore essential services.
  • Manage personnel security, including access rights, relevant background-check procedures and qualifications.
  • Prepare staff through training, information and exercises.

Organisations must set out these measures in a resilience plan or equivalent documents, put them into practice, and name someone to act as the main contact for the authorities.

What the guidelines say about visitor access

The July 2026 guidelines describe practical measures for visitor access. They recommend:

  • Control entry. Register visitors at a controlled entry point and issue visible identification
  • Coordinate escorts. Escort visitors beyond reception unless otherwise authorised
  • Limit access. Give each person access only to the areas they need
  • Deactivate identification on exit. End visitor credentials when they leave
  • Keep access records. Log access events and maintain a register of keys and credentials, including issue, revocation and return dates

These are non-binding recommendations, not a universal checklist of legal duties for every site. The measures you need depend on your risk assessment and applicable national requirements. Still, they give security teams a useful way to test their visitor and contractor process.

Background checks need separate attention. Article 14 sets out a nationally governed process for specified categories of people. Commercial watchlist screening or a visitor ID check should not replace that process.

Why CER is also a site access and evidence problem

Many critical sites already have controls in place: a reception desk, an access control system, a contractor induction and a permit process. The gap can be between them.

Your visitor log says the contractor left at 16:00. Does your access control system agree? If the two don’t connect, credentials can stay active long after people leave. Maintenance crews, cleaners and specialist engineers often have the widest site access and the least scrutiny. If contractor approvals live in email and their qualifications live with a third party, that is the gap an authority will find first.

CER asks for measures you can describe and demonstrate. Connecting visitor records with approvals and access control evidence helps make that record part of normal operations.

How connected visitor workflows can help

The examples below support parts of site resilience. They don’t represent a complete CER compliance assessment.

Scroll horizontally to view all columns on smaller screens.

Site access task With disconnected tools How Envoy can support the workflow
Controlled entry and registration Paper logs or separate kiosks leave records spread across entrances. Visitor and contractor sign-ins bring visit information into a shared system.
Approval before access Decisions are difficult to retrieve. Approval Workflows route visits to designated reviewers and record approval decisions and timestamps.
Contractor checks Qualification and document records are managed separately. Supported screening integrations and assessments help teams check contractor qualifications against site requirements.
Visible identification and escorts Badges and escort handoffs are inconsistent. Visitor badges and host notifications support identification and handoffs while staff enforce escort rules.
Ending access Deactivation depends on a separate manual task. Supported access control integrations connect the visit to credential management, according to the integration and configuration.
Evidence for review Teams reconstruct the visit after the fact. Visitor records and reporting work alongside access control logs to show who visited, who approved the visit, and when access ended.

Six ways to test your site access process this month

Once your team has confirmed designation status, notification dates and national deadlines, use these checks to put the site access process through its paces. Agree who owns each one and use your risk assessment to prioritise the gaps you find.

  1. Check who owns each step. Your head of security or CER liaison officer should confirm who reviews contractor qualifications, approves access, coordinates escorts, and closes out visits. Make sure staff know who takes over when that person is unavailable.
  2. Map every entry point and how visitors and contractors pass through it. Site security and facilities should include secondary entrances and after-hours arrivals, and check how access to sensitive areas is controlled.
  3. Pick one recent contractor visit. Ask security and compliance to show who approved it, what checks were done, and when access ended. Check that authorised staff can retrieve the supporting records without chasing several teams.
  4. Test that temporary credentials end when visits do. Your access control administrator should confirm the result in the access control system, working with IT, and check how physical badges or keys are returned.
  5. Time how long it takes to produce an accurate onsite list, including contractors. Your health and safety or emergency response lead should set a response target that fits your emergency plan, and test with security how the team would contact and account for those people.
  6. Test the fallback process. Your business continuity lead should walk through, with security, facilities, and IT, how the site handles arrivals, departures, and emergency accountability if the kiosk, network, or access control system goes offline. Agree who takes over and how records are reconciled afterwards.

Record the gaps, assign someone to resolve each one, and test again once changes are in place. Use the findings to update relevant procedures, staff training, and the resilience plan.

Explore Visitors Critical to see how Envoy connects identity verification, screening and approvals, or schedule a demo to discuss your site’s requirements.

Man with tattoos wearing a burgundy cap and gray sleeveless sweater over a white shirt sitting indoors.
AUTHOR BIO
Head of Customer Success - EMEA

Quentin leads Envoy across EMEA, and has been working with organisations to strengthen their security operations and meet compliance requirements over the last 8 years. Outside of work you’ll find him at a coffee shop, on a long bike ride, or in a boxing ring (for fun).

Read more

Explore what a physical security assessment is and learn the steps your team should take to conduct one.

We’ll show you how to put together a visitor process around SQF requirements, with practical steps and records your team can use.

This guide covers CTPAT’s visitor management criteria and the workflows and records that help your team prepare for validation.

This guide covers how visitor management supports FISMA, which NIST controls apply, and what your team needs to document along the way.

In this guide, we’ll break down how cloud digital signage works, how it compares with on-premise signage, cost factors, and what to look for in a solution.

Learn how to support ITAR compliance with visitor screening, access approvals, onsite controls, and records that document each visit.