NIS2 Classifies Accounting Firms as Essential Services. Here's What That Means for Your AI.
Network and Information Security Directive Impact on Professional Accounting IT
---
On October 17, 2024, your accounting firm was reclassified as essential infrastructure under EU law — whether or not anyone sent you a notification about it. NIS2 (EU Directive 2022/2555, the Network and Information Security Directive, which took full effect on that date) expanded its coverage to the financial sector including accounting services, placing firms above 50 employees under the same security obligations as electricity grid operators and healthcare systems. The AI tool your team uses to process client invoices and generate financial reports is now a supply chain security risk that your partners are personally liable to manage.
Being classified as essential infrastructure does not require being critical in the way a power plant is critical. It requires handling enough client financial data that a security breach would cause measurable economic disruption across multiple organizations. Accounting firms above 50 employees managing dozens of SME payrolls, 200+ audit engagements, and consolidated financial reporting almost universally meet that threshold — which means most mid-market accounting firms in the EU are now essential infrastructure, whether their partners have been briefed about it or not.
---
What NIS2 Actually Requires from an Accounting Firm
Article 21 of NIS2 — the provision that defines what essential entities must implement — requires security measures across seven categories. Risk analysis and information system security policies. Incident handling and recovery. Business continuity planning covering system failures. Supply chain security including documented vendor assessment. Security in network and information system procurement. Policies to assess the effectiveness of security measures in place. Basic cybersecurity hygiene practices and training.
For a tax firm or accounting practice, supply chain security is the category most directly relevant to AI tool selection. Every IT vendor the firm uses — including accounting AI software — is a supply chain element that must be assessed, documented, and available for regulatory inspection. The documentation requirement is ongoing, not a one-time exercise. And the penalties for non-compliance reach €10 million or 2% of global annual turnover, whichever is higher, with personal liability for management body members who fail to oversee compliance.
Personal accountability runs deeper still. Under Article 20, management bodies — in an accounting firm, that means the partners — must approve and oversee NIS2 security measures and receive training on cybersecurity risk management. Partners cannot delegate this accountability to an IT manager or to the AI vendor's security team. The liability runs to the individuals who manage the firm.
---
The Certification Gap
Most accounting firms that have started their NIS2 review have reached for vendor certifications as the solution to supply chain security requirements. SOC 2 Type II and ISO 27001 are two common ones — independent security audits where a third-party examiner verifies that the vendor's security controls meet a defined standard. These certifications represent substantial independent audit work.
They do not automatically satisfy NIS2's supply chain security requirement.
Supply chain security under Article 21 requires the firm to document its own assessment of the vendor's security posture — not simply to hold a certificate the vendor obtained. The assessment must address how the vendor's security practices affect the firm's ability to meet its NIS2 obligations, what the residual risk is after the vendor's controls are applied, what the firm's incident response plan is if the AI vendor experiences a breach, and how the firm would exit the vendor relationship within a defined timeline.
A vendor's certifications are inputs to that assessment. They are not the assessment itself.
BDO and Mazars — two of the larger international accounting networks — published NIS2 readiness guidance for their accounting clients in 2025, recognizing that they themselves were subject to the same requirements. Mid-market accounting firms in Germany and the Netherlands received NIS2 essential entity classification confirmation from national competent authorities in early 2025. French accounting associations are developing implementation guidance. Firms that waited for definitive guidance before starting are now compressed against an enforcement timeline that did not pause for them.
---
What a NIS2 Supply Chain Assessment for AI Looks Like
An accounting firm satisfying NIS2 Article 21's supply chain security requirement for its AI accounting tool needs documentation covering four areas.
Security architecture documentation: where does the AI process data, under which jurisdiction, and what technical controls are applied at each stage? This requires more than a privacy policy — it requires the vendor to answer specific questions about their infrastructure that a security officer can validate.
Response timeline documentation: how does the AI vendor notify the firm of a security incident, within what timeline, and what is the firm's 24-hour notification procedure to its NIS2 competent authority? NIS2 requires initial incident notification within 24 hours. A firm using an AI tool whose contract specifies a 72-hour breach notification service level agreement (SLA) cannot meet the 24-hour NIS2 requirement with that tool alone.
Migration planning: what is the documented plan for switching away from the AI vendor within 12 months, and what data portability provisions ensure client data can be retrieved? A firm critically dependent on an AI tool that cannot be replaced within a defined timeline fails the business continuity requirement.
Ongoing assessment records: evidence that the firm reviews its vendor assessments periodically — not just at onboarding — and captures any changes to the vendor's security posture. Regulator enforcement increasingly focuses on whether assessments are maintained rather than merely completed.
---
Sovereign AI and the NIS2 Compliance Story
Accounting firms selecting Stralevo have a specific compliance advantage for NIS2 supply chain assessments: the documentation required for those assessments exists by architectural design rather than being assembled in response to a questionnaire.
EU data residency as the default means the jurisdiction question in a supply chain assessment has a clean, documentable answer. No routing to whichever cloud region has available capacity. No CLOUD Act exposure — the US law that allows American law enforcement to compel US-headquartered companies to produce data stored anywhere in the world, including EU data centers. The architecture produces the answer the supply chain assessment requires.
Contractual audit rights are part of the service agreement, not a custom negotiation. The firm can exercise the right to audit that NIS2 Article 21 requires firms to establish with critical vendors. The contract already contains it.
Incident notification timelines are defined and compatible with NIS2's 24-hour requirement. The firm can document what it will receive, when, and through which channel — the three questions a NIS2-compliant incident response plan needs to answer.
Exit strategy documentation is available because the architecture was designed to be exitable: data is stored in formats that support portability, and migration support is part of the contractual relationship.
One supply chain assessment that closes on all four required areas, rather than a certification document that needs to be translated into an assessment by the firm's own compliance team.
---
The Enforcement Trajectory
National regulators applying NIS2 across the EU are building enforcement capacity with the same pattern observed in GDPR rollout: early years focused on who is covered, subsequent years focused on whether what they're doing is adequate. The accounting sector in 2025 is where GDPR was in 2019 — newly covered, still orienting to requirements, and watching the first enforcement actions emerge in adjacent sectors.
Enforcement cases in other NIS2-covered sectors — telecoms, energy, digital infrastructure — are establishing the baseline. Management body personal liability provisions are being applied, not just threatened. Executives who failed to document supply chain security assessments have faced personal administrative sanctions alongside corporate fines. Accounting firm partners reviewing those cases will recognize that their liability structure is the same category.
Firms that complete genuine supply chain assessments now — with documentation of ongoing review processes, not one-time checkboxes — are building compliance assets that remain valid as enforcement standards tighten. Waiting compounds exposure, because every month without an assessment is a month of records that will not exist if a regulator requests evidence of continuous compliance management rather than a single-point assessment.
Partners who have never thought of themselves as infrastructure operators are now classified as managing essential infrastructure. The question is not whether that classification applies. It is whether the firm is prepared to demonstrate compliance when the question is asked.