Skip to main content
Back to overview

NIS2 Background Checks: What Human Resources Security Actually Requires

By NIS2Certify
nis2background-checkshuman-resources-securityarticle-21gdprmsp
NIS2 Background Checks: What Human Resources Security Actually Requires

An MSP hires a senior engineer who will hold admin rights on forty client tenants. HR sends him a form asking for a criminal record extract, "because NIS2 requires it". He refuses and points to data protection law.

Both sides are half right. NIS2 background checks are a real obligation for a defined group of entities, but the directive never says "criminal record", and in most member states an employer cannot simply demand one.

Human resources security is the part of Article 21 that security teams hand to HR and HR hands back. Here is what the texts say, and what you can defend in front of a supervisor.

NIS2 background checks start with four words in Article 21(2)(i)

Article 21(2)(i) of Directive (EU) 2022/2555 lists "human resources security, access control policies and asset management" as one of the ten minimum measures. That is the whole provision.

Recital 79 adds only that entities should "address human resources security" as part of their risk management. Nowhere does the directive mention vetting, screening or criminal records.

So for most essential and important entities, the obligation is open-ended: show that people risk is part of your risk management, in proportion to your size and exposure. We covered the other two thirds of the same point in our guide to access control and asset management.

Article 21 — 10 NIS2 Cybersecurity Measures

Article 21

10 Cybersecurity Measures

Governance & Strategy

1Risk analysis & information security policies
6Effectiveness assessment of security measures

Incident & Continuity

2Incident handling & notification
3Business continuity & disaster recovery

Supply Chain & Systems

4Supply chain security
5Security in network & information systems development

Technical Controls

8Cryptography & encryption
10Multi-factor authentication & secure communications

People & Assets

7Cyber hygiene & training
9HR security & access control

For MSPs and cloud providers, the Implementing Regulation spells it out

Commission Implementing Regulation (EU) 2024/2690 is where the detail sits. It applies directly to DNS service providers, TLD name registries, cloud computing, data centre and CDN providers, managed service providers, managed security service providers, online marketplaces, search engines, social networking platforms and trust service providers.

If you run an MSP, that is you, not just your clients.

Section 10 of the Annex contains four blocks:

  • 10.1 Human resources security. Employees, and where applicable direct suppliers, must understand and commit to their security responsibilities. Hiring must include mechanisms such as "reference checks, vetting procedures, validation of certifications, or written tests". Role assignments are reviewed at least annually.
  • 10.2 Verification of background. Covered below.
  • 10.3 Termination or change of employment. Duties that survive the contract, such as confidentiality, must be contractually defined and enforced.
  • 10.4 Disciplinary process. A documented, communicated process for violations of security policy.

Point 10.1.2 also singles out two groups: users with administrative or privileged access, and members of management bodies. Both must demonstrably know their role and authority.

Background verification is risk-based, not a blanket rule

Point 10.2.1 requires verification of background "to the extent feasible" and only "if necessary for their role, responsibilities and authorisations". This is not a duty to screen every employee.

Point 10.2.2 sets two concrete tasks. First, define criteria for which roles may only be exercised by people whose background has been verified. Second, complete that verification before the person starts in the role.

The regulation names no roles. ENISA's technical implementation guidance (version 1.0, June 2025) suggests executives, roles with access to sensitive information, financial roles, procurement and physical security. For an MSP, the obvious list is shorter: anyone with privileged access to client environments, the RMM platform, backup systems or the identity provider.

Criminal records appear only in recital 22, as an example: verification "may include measures such as checks of the person's criminal record or past professional duties". May, not shall. Reference checks, diploma validation and identity verification are verification too.

The regulation also does not require periodic re-screening. ENISA recommends repeating checks for critical roles, but that is guidance.

GDPR Article 10 limits what a background check can contain

Point 10.2.2 says verification must "take into consideration the applicable laws, regulations, and ethics". That sentence carries more weight than it looks.

Article 10 GDPR allows processing of criminal conviction data "only under the control of official authority or when the processing is authorised by Union or Member State law". A recital in an implementing regulation saying a check "may include" criminal records is a thin basis on its own. National law decides.

ENISA's guidance lists "signed consent forms" as possible evidence. Be careful: several data protection authorities take the view that consent is rarely valid between employer and candidate. A signature does not repair a missing legal basis.

The practical consequence: your client's screening policy has two authors. The security officer defines which roles need verification. Legal or HR defines which checks national law permits for those roles.

National law decides what a NIS2 background check looks like

The six markets we follow most closely show how far apart the answers are.

  • Netherlands. Article 14(3) of the Cyberbeveiligingsbesluit requires "betrouwbaarheidseisen" for staff with security tasks. The usual tool is a VOG, which the employee requests from Justis; the employer sees the declaration, not the record.
  • Germany. § 30(2) no. 9 BSIG requires concepts for personnel security. Under § 30 BZRG only the individual can apply for a Führungszeugnis. Formal security vetting under the SÜG covers a narrow list of sites.
  • France. The Assemblée nationale added human resources security to Article 14 of the Résilience bill on 10 November 2026; the bill is not yet law. The CNIL allows an employer to view a bulletin n° 3 only where the job justifies it, without keeping a copy.
  • Spain. No NIS2 law yet. The AEPD states that employers cannot require a criminal record certificate unless a law provides for it.
  • Italy. Legislative Decree 138/2024 speaks of "sicurezza e affidabilità del personale". In 2021 the Garante fined a company €40,000 for asking a candidate for criminal record certificates without a legal basis.
  • Poland. The exception. Article 8f of the amended KSC Act requires people performing risk management or incident handling tasks to present a criminal record certificate, limited to offences against the protection of information.

One directive, six different answers. A group-wide screening policy copied from headquarters will be unlawful in at least one of them.

NIS2 transposition by country

  • AustriaIn force
    • In force since October 1, 2026
    • Act: NISG 2026 (BGBl. I Nr. 94/2025)
    • Registration due December 31, 2026

    Authority: Federal Office for Cybersecurity · Source

  • NetherlandsIn force
    • In force since August 15, 2026
    • Act: Cyberbeveiligingswet (Stb. 2026, 187)
    • Registration required, no transition period

    Authority: NCSC (MijnNCSC) · Source

  • LuxembourgIn force
    • In force since May 10, 2026
    • Act: Law of 5 May 2026
    • Registration due July 10, 2026

    Authority: ILR (CSSF for finance) · Source

  • PolandIn force
    • In force since April 3, 2026
    • Act: UKSC (Dz.U. 2026 poz. 252)
    • Registration due October 3, 2026
    • Measures due April 3, 2027

    Authority: Minister Cyfryzacji (Wykaz KSC) · Source

  • PortugalIn force
    • In force since April 3, 2026
    • Act: Decree-Law 125/2025 (RJC)

    Authority: CNCS · Source

  • BulgariaIn force
    • In force since February 13, 2026
    • Act: Cybersecurity Act amendment (State Gazette No 17/2026)

    Authority: Ministry of e-Government · Source

  • MaltaIn force
    • In force since January 23, 2026
    • Act: S.L. 460.41

    Authority: Critical Infrastructure Protection Department · Source

  • SwedenIn force
    • In force since January 15, 2026
    • Act: SFS 2025:1506

    Authority: NCSC-SE · Source

  • EstoniaIn force
    • In force since January 1, 2026
    • Act: Cybersecurity Act (KüTS) amendment
    • Registration within 3 months

    Authority: RIA · Source

  • GermanyIn force
    • In force since December 6, 2025
    • Act: NIS2UmsuCG
    • Registration due March 6, 2026
    • 17,729 registered by June 30, 2026

    Authority: BSI · Source

  • CzechiaIn force
    • In force since November 1, 2025
    • Act: Act No 264/2025 Coll.
    • Registration within 60 days

    Authority: NÚKIB · Source

  • DenmarkIn force
    • In force since July 1, 2025
    • Act: NIS 2 Act No 434 of 6 May 2025
    • Registration due October 1, 2025

    Authority: Danish Agency for Societal Security · Source

  • SloveniaIn force
    • In force since June 19, 2025
    • Act: ZInfV-1 (OG 40/25)
    • Registration within 30 days

    Authority: URSIV · Source

  • CyprusIn force
    • In force since April 25, 2025
    • Act: Law 60(I)/2025

    Authority: Digital Security Authority · Source

  • FinlandIn force
    • In force since April 8, 2025
    • Act: Cybersecurity Act 124/2025
    • Registration due May 8, 2025
    • Measures due July 8, 2025

    Authority: Traficom (NCSC-FI) · Source

  • HungaryIn force
    • In force since January 1, 2025
    • Act: Act LXIX of 2024

    Authority: SZTFH · Source

  • SlovakiaIn force
    • In force since January 1, 2025
    • Act: Act No 366/2024 Coll.
    • Registration within 60 days

    Authority: NBÚ · Source

  • RomaniaIn force
    • In force since December 31, 2024
    • Act: GEO 155/2024 (Law 124/2025)
    • Registration within 30 days

    Authority: DNSC · Source

  • GreeceIn force
    • In force since November 27, 2024
    • Act: Law 5160/2024 (Gazette A' 195)

    Authority: National Cybersecurity Authority · Source

  • BelgiumIn force
    • In force since October 18, 2024
    • Registration due March 18, 2025

    Authority: CCB · Source

  • LithuaniaIn force
    • In force since October 18, 2024
    • Act: Law No XIV-2902

    Authority: NCSC (MoND) · Source

  • ItalyIn force
    • In force since October 16, 2024
    • Act: D.Lgs. 138/2024
    • Baseline measures due by October 2026 (entities listed in 2025)

    Authority: ACN · Source

  • LatviaIn force
    • In force since September 1, 2024
    • Act: National Cybersecurity Law

    Authority: National Cybersecurity Centre · Source

  • CroatiaIn force
    • In force since February 15, 2024
    • Act: Cybersecurity Act (OG 14/2024)

    Authority: NCSC (SOA) · Source

  • FranceNot yet transposed
    • Senate adopted the law on March 12, 2025
    • Regulator published its framework on March 17, 2026
    • Referred to the Court of Justice on July 8, 2026
    • Pre-registration open

    Authority: ANSSI · Source

  • SpainNot yet transposed
    • Draft bill approved on January 14, 2025
    • Referred to the Court of Justice on July 8, 2026
    • The NIS1 regime still applies

    Authority: CCN / INCIBE · Source

  • IrelandNot yet transposed
    • Referred to the Court of Justice on July 8, 2026
    • Bill not yet enacted

    Authority: NCSC Ireland · Source

Status as of September 28, 2026. Other member states: see the country-by-country timeline.

Supplier staff are covered by contract, not by your HR department

Point 10.2.1 extends verification to direct suppliers and service providers "where applicable", by reference to point 5.1.4. That point requires contracts to specify, where appropriate, "requirements regarding the verification of the background of the suppliers' and service providers' employees".

The route is contractual. You do not screen your subcontractor's engineers; you require the subcontractor to do so, and to confirm it.

For MSPs this runs in both directions. Your clients in scope of NIS2 will add the same clause to your contract. Expect it in renewals, and have an answer ready. Our post on supplier risk assessment covers the rest of that contract.

Leavers and discipline are the cheapest part to fix

Most HR security findings have nothing to do with vetting. They concern people who left.

Point 10.3 requires that post-employment duties are written into the contract. Point 12.5 of the same Annex requires documented return or deletion of assets on termination. Add timely revocation of access and you have the classic offboarding checklist.

Point 10.4 requires a disciplinary process for security policy violations that is established, communicated and maintained. It can sit inside the existing HR procedure. It cannot be undocumented.

The evidence an auditor will ask for

ENISA's guidance gives a fair preview of the evidence list:

  1. A documented analysis of which roles require background verification, and why.
  2. A background verification procedure, with records that checks were completed before start dates.
  3. Signed acknowledgements of the security policy from employees and, where relevant, suppliers.
  4. Employment contracts with confidentiality duties that survive termination.
  5. Offboarding records: assets returned, access revoked, dated.
  6. A communicated disciplinary process.
  7. Supplier contracts with background verification clauses where the risk justifies them.

Notice what is not on the list: a folder of criminal record extracts. In several countries, keeping that folder is the violation.

If you want to see where a client stands on this and the other Article 21 measures before a supervisor asks, run the NIS2Certify quick scan. It gives you a gap analysis you can take to both the security officer and HR.

Start with the role list. Ten minutes with the client's identity provider tells you who holds privileged access. Whether those people were verified before they got it, and whether the check was lawful where they work, is the question that matters.

Still have a question?

Answers are generated from our articles and are not legal advice. Do not enter personal or confidential data.