NIS2 is a European directive. It does not apply to a South African organisation solely because it is based in South Africa. It becomes relevant where the organisation has entities in the Union that fall within the sectors in Annexes I and II, or where its European operations meet the size or entity-type tests. Each in-scope entity is classified as essential or important. It must take cybersecurity risk-management measures under Article 21, have its management body approve and oversee them under Article 20, report significant incidents to tight deadlines under Article 23, and accept supervision under Articles 32 and 33. That is a system. It is not a questionnaire. King V and POPIA remain the primary duties for the South African organisation. NIS2 is an additional layer for the European entities that are in scope.

What the duty asks for

Three questions come first for any European entity. Am I in scope: sector, entity type, headcount, turnover and balance sheet, and the types that are always in. Which class: essential or important, which decides the supervision regime and the fine exposure under Article 34. Which clock: a 24-hour early warning, a 72-hour notification, and a final report one month later, each with its own trigger.

For digital-infrastructure and digital-provider entities, Implementing Regulation (EU) 2024/2690 adds technical requirements and criteria for a significant incident. National law in the Member State adds its own duties. The EU-level system stays the same. The national layer sits on top of it. The South African parent still needs a clear view of which of its European entities are in scope and which class they fall into.

What a list leaves unbuilt

A list of Article 21 measures, marked in place, does not calculate the class from size, sector and designation. It does not record a management-body approval. It does not run the significance test, including the loss threshold. It does not start the 24-hour clock from a recorded awareness time. It does not stop an author approving their own record. When the authority asks, the organisation has a completed questionnaire and no system of record. The same gap appears if the South African group treats NIS2 as a remote European issue and has no process that feeds incidents or measures back to the governing body under King V.

How a management system meets it

A management system covers NIS2 from the scope decision to the answer to a supervisory authority. Every obligation has its own record type, tied to its article, to the annex point of the implementing regulation, or to the national provision. Every record follows the same approval lifecycle. A scope engine applies the size test and the always-in-scope types. The class is calculated and stored. An override needs a reason. Article 21 measures are controlled records: policy, incident handling, continuity, supply chain, development and vulnerability handling, effectiveness, hygiene, cryptography, access and assets. A gap register is seeded for each entity. Only assessors set a gap's status.

Incident reporting is a process. The register holds the 24-hour, 72-hour, intermediate, final and progress reports, with timers and overdue flags. A "not significant" decision needs a written justification. An author cannot approve their own record. If an approved record is edited, it returns to draft and the approval is cleared. Approved records are locked. An approved record, with its evidence, closes a gap item.

AICOB is the process model. NIS2 is mapped onto it for the European entities that are in scope. POPIA and King V remain mapped for the South African organisation. The platform is the environment. The management body approves and oversees. It does not operate the measures. That separation is the duty, not a design preference. The same living processes that support King V oversight of technology risk can carry the NIS2 mapping for the European entities without duplicating the work.

None of this certifies the organisation or declares it compliant. Those decisions sit with the relevant European supervisory authority for the in-scope entities, or with the governing body itself under King V. The system makes the work visible so the decision can be made on evidence.