Back to blog
Compliance9 min read|

November 18, 2026

NIS2 and File Transfer: A Practical Checklist for SFTP

What NIS2 means for file transfer: map Article 21 measures to SFTP keys, encryption, audit logs, supplier risk and 24-hour incident reporting.

NIS2 and File Transfer: A Practical Checklist for SFTP

Your company has just been told it falls under NIS2, and the security lead is working through the Article 21 measures one by one. Somewhere on that list sits the SFTP server that receives payroll files from your HR provider, sends invoices to forty customers, and pulls nightly stock updates from a logistics partner. Nobody has written down who owns it. The question on the table is simple: what does NIS2 actually require of file transfer?

NIS2 file transfer obligations are not spelled out as a separate rule. The directive describes outcomes, and your file exchange setup has to support them like any other system. This post maps the relevant NIS2 measures to concrete controls for SFTP and managed file transfer, so you can turn a legal text into a checklist an engineer can work through.

This is a practical engineering guide, not legal advice. Your national transposition law and your competent authority have the final word.

What NIS2 is and who it covers

NIS2 is Directive (EU) 2022/2555, the successor to the original NIS Directive. Member states had to transpose it into national law by 17 October 2024. Some did so on time, Belgium among them, while others are still finishing their laws.

The directive applies to medium and large organizations in a long list of sectors, including energy, transport, banking, health, drinking water, digital infrastructure, ICT service management, public administration, postal services, waste management, manufacturing of certain products, food, and digital providers. Entities are split into two groups:

  • Essential entities - Generally larger organizations in the most critical sectors. They face proactive supervision and higher maximum fines.
  • Important entities - The rest of the in-scope organizations. Supervision is mostly reactive, after an incident or a complaint.

Two features make NIS2 different from earlier rules. First, management bodies must approve the cybersecurity measures and can be held liable for failures (Article 20). Second, the directive explicitly reaches into your supply chain, which is where file transfer becomes hard to ignore.

Why file transfer is squarely in scope

File transfer is how many regulated organizations exchange data with the outside world. Payment files go to banks, patient data moves between labs and hospitals, orders and invoices flow between manufacturers and distributors. That makes your SFTP endpoints:

  • An external attack surface - They are internet-facing services that accept credentials from third parties.
  • A supply chain link - A compromised partner account is a direct path into your environment, and a compromised file can poison downstream systems.
  • An operational dependency - If the nightly file does not arrive, production planning, billing or payroll may stop.

NIS2 asks you to manage risks to the "network and information systems" that support your services. A file exchange that carries business-critical data clearly qualifies, whether you run it yourself or buy it as a service.

Mapping Article 21 measures to file transfer controls

Article 21(2) lists ten minimum areas of cybersecurity risk management. Not all of them touch file transfer equally. Here are the ones that do, with the controls that usually satisfy them.

Risk analysis and security policies

Start with an inventory. List every file exchange: the partner, the protocol, the direction, the data classification, the business process that depends on it, and the internal owner. Most organizations discover forgotten accounts during this step. An account that nobody can explain is a finding in itself.

Supply chain security

Article 21(2)(d) covers security in your relationships with direct suppliers and service providers. For file transfer, that means two things:

  • Your MFT or SFTP provider - Treat it as an ICT supplier. Ask where data is hosted, how tenants are isolated, how support staff access your environment, and how incidents are communicated to you.
  • Your trading partners - Each partner account is a trust relationship. Give each one its own credentials, limit it to its own folders, and remove it when the relationship ends. The partner onboarding guide covers how to set this up cleanly.

Cryptography and encryption

Article 21(2)(h) asks for policies on the use of cryptography and, where appropriate, encryption. In practice:

  • Disable plain FTP for anything outside a closed test network.
  • Require SFTP or FTPS with TLS 1.2 or later for partner traffic.
  • Use modern SSH key types such as Ed25519, and retire old RSA keys under 2048 bits.
  • Know where your data is encrypted at rest and who holds the keys.

Access control and authentication

Articles 21(2)(i) and 21(2)(j) cover access control policies and the use of multi-factor authentication. For SFTP this translates to public-key authentication instead of passwords, MFA on the admin console, account lockout after repeated failures, and a defined key lifecycle. Keys that never expire are a classic audit finding, so plan rotations in advance using an overlap process like the one in rotating SSH keys for SFTP partners.

Incident handling and business continuity

Articles 21(2)(b) and 21(2)(c) cover incident handling, backups and recovery. For file exchange, ask: if a corrupted or malicious file arrives, can you stop it before it reaches the ERP? If a delivery fails, can you replay it once the cause is fixed? If a file is overwritten, can you get the previous version back?

Effectiveness and hygiene

Article 21(2)(f) asks you to assess whether your measures work. That requires evidence, which for file transfer mostly means logs you can trust. More on that below.

NIS2 incident reporting and your file transfer logs

Article 23 sets a tight reporting timeline for significant incidents:

  1. Early warning within 24 hours of becoming aware of the incident.
  2. Incident notification within 72 hours, with an initial assessment of severity and impact.
  3. Final report within one month of the notification.

The 24-hour clock is where file transfer logging gets tested. If a partner account is used from an unknown location to download a month of payroll files, you need to answer quickly: which account, which files, when, from where, and whether anything was modified. Logs that are scattered across a server's syslog, a rotated file on disk and a spreadsheet of partner contacts will not give you that answer in time.

Good file transfer audit logs for NIS2 purposes should be:

  • Complete - Every login, upload, download, delete, rename and permission change, with the actor and the source.
  • Tamper-evident - An attacker with access to the server should not be able to quietly edit the trail.
  • Retained - Kept long enough to investigate incidents discovered late. Set a retention period with your legal team.
  • Searchable - You should be able to filter by user, path and time window in minutes, not hours.

The audit logging guide for file transfers goes deeper on what to capture and how to structure it.

A practical NIS2 checklist for file exchange

Use this as a starting point and adapt it to your risk assessment.

Inventory and ownership

  • Every SFTP, FTPS and API integration is listed with an owner and a data classification.
  • Unused accounts are disabled, and each account has a review date.

Authentication

  • SFTP access uses public keys only. No shared or password-based partner accounts.
  • Admin access to the file transfer platform requires MFA.
  • Accounts lock after repeated failed logins.
  • Each partner system has its own key, and keys have a rotation schedule.

Encryption

  • Plain FTP is disabled or limited to documented exceptions.
  • FTPS endpoints require TLS 1.2 or later.
  • Encryption at rest is documented, including where keys are held.

Integrity and continuity

  • Incoming files are validated before downstream systems consume them.
  • Failed or suspect files go to a quarantine area, not straight into production.
  • Transfers can be replayed, and earlier file versions can be restored.
  • Copies and moves are checked with a cryptographic checksum.

Monitoring and evidence

  • Audit logs are tamper-evident and retained for a defined period.
  • Logs can be exported or forwarded to your SIEM.
  • Failed deliveries trigger alerts to a named team.

Supplier management

  • Your file transfer provider's hosting location, tenant isolation and support access model are documented.
  • Partner offboarding removes keys and accounts on the day the contract ends.

A quick sanity check you can run today on a self-managed OpenSSH server is to list which accounts still allow password logins:

sudo sshd -T | grep -Ei '^(passwordauthentication|kbdinteractiveauthentication|pubkeyauthentication)'

If passwordauthentication yes comes back, find out which partners rely on it before you switch it off.

Common pitfalls

  • Treating NIS2 as a certification - There is no NIS2 certificate to buy. You need measures that fit your risks and evidence that they work.
  • Forgetting the provider is a supplier - Moving to a managed service does not remove the risk assessment. It changes what you assess.
  • Logs on the same box as the data - If an attacker can edit them, they will not hold up when you need to reconstruct an incident.
  • One shared account for many partners - It makes incident scoping and offboarding nearly impossible.
  • No owner for the file exchange - The 24-hour early warning clock does not wait while you work out who runs the server.
  • Ignoring data location - NIS2 sits alongside GDPR. Check where files are stored, as covered in data sovereignty and file transfer.

How FilePulse fits

FilePulse is a fully managed file transfer service hosted in the EU, run by a company based in Belgium. SFTP uses public-key authentication only, FTPS requires TLS 1.2 or later, and plain FTP is off unless you enable it per user. Web app accounts support MFA through TOTP, WebAuthn and passkeys, with lockout after repeated failures, and support access is audited and time-limited. Workflows can validate incoming files, route failures to a quarantine inbox, replay transfers and keep versions, with copies and moves verified by SHA-256. Activity is recorded in a tamper-evident, SHA-256 hash-chained audit log with signed checkpoints, and SIEM forwarding and evidence packages are available on premium plans. FilePulse does not hold a NIS2 certification (no such thing exists), and it does not replace your own risk assessment, but it covers a large share of the file transfer controls above out of the box.

Next step: Start a 14-day free FilePulse trial, no credit card required, and run your first partner exchange through key-only SFTP with a full audit trail.