When the Systems Go Down: Will Your Business Go Down with It?

When the Systems Go Down: Will Your Business Go Down with It?

When the Systems Go Down: Will Your Business Go Down with It?

Cyber resilience through the lens of King V and South African law
By Yolandi Erasmus | Managing Director | Y. Erasmus & Associates Inc.

Imagine arriving at work to find that your business cannot access its email, customer orders or accounting records. Deliveries are waiting. Payroll is approaching. The IT provider is investigating, but cannot yet say when access will return.

Alongside the recovery work, management must decide who can authorise emergency spending, what to tell customers, whether personal information has been compromised and which contractual deadlines are approaching. These decisions become harder if the people, documents and approval channels needed to make them are also unavailable.

For growing businesses, cyber resilience therefore includes the ability to exercise authority, meet legal obligations and protect commercial relationships during a disruption.

What King V asks of business leaders

King V superseded King IV and is effective for financial years beginning on or after 1 January 2026. It is a voluntary governance code, although requirements to apply it may arise under particular regulatory or contractual arrangements. Statutory duties must be assessed separately. 1, 2

Principle 10 places the governance of data, information and technology with the governing body. Its recommended practices address disaster recovery planning and testing, cybersecurity, assurance from outsourced technology providers and accountable AI use with appropriate human oversight. Principle 8 also addresses business continuity.

These practices can be scaled to the organisation. A medium-sized company can start with clear responsibilities, a tested recovery process and reliable information about its significant risks. Delegating work to management or an IT provider leaves the governing body accountable for its oversight. 1

The practical question is whether the board knows how a technology failure would affect the business and has acted on the weaknesses identified.

Directors need informed decisions and evidence

Section 76 of the Companies Act requires directors to exercise appropriate care, skill and diligence, assessed against their functions and their knowledge and experience. It also allows reliance on suitable employees and professional advisers, subject to the statutory conditions. 3

A successful cyberattack does not, by itself, establish that a director breached these duties. Any liability requires the applicable legal requirements to be met. However, ignored warnings, unresolved recovery failures or unsupported assurances may become relevant when the director’s conduct is examined. 3

Directors should ask for evidence of recovery tests, critical supplier dependencies and outstanding corrective actions. Minutes should capture significant decisions, the information considered and follow-up responsibilities. This gives the company a usable record of how it addressed the risk.

Check the gap between your contracts

Consider a business that promises customers delivery within 24 hours, while its technology provider promises only to begin responding to a critical incident within 48 hours. That mismatch can leave the business exposed even while the provider meets its own contractual commitment.

Review the service agreement against what the business actually needs: recovery commitments, access to usable data, incident cooperation, subcontractor dependencies and liability limits. A promise to maintain backups deserves scrutiny of whether the business can restore and use them within an acceptable period.

Where a provider processes personal information as an operator, POPIA section 21 requires a written contract securing the relevant safeguards. It also requires the operator to notify the responsible party immediately when there are reasonable grounds to believe personal information has been accessed or acquired without authority. 4

On the customer side, relief from missed performance cannot simply be assumed. Force majeure wording, notice requirements, the facts and applicable impossibility principles need assessment. Ask the insurance broker to confirm how the policy responds to the same scenario, including notification, expert appointment and expenditure conditions. 7

Assess the incident and the reporting duties

POPIA section 19 requires reasonable technical and organisational protection of personal information, supported by risk identification and ongoing verification and updating of safeguards. 4

Section 22 requires notification to the Information Regulator and affected data subjects when there are reasonable grounds to believe personal information has been accessed or acquired without authority, subject to the statutory qualifications. Notification must occur as soon as reasonably possible, with the factors permitted by the Act taken into account. POPIA does not impose a general 72-hour deadline. 4

Management needs an early assessment of the statutory trigger alongside containment and investigation. A completed forensic report is not a prerequisite for notification. Reports to the Regulator are submitted through its eServices portal. 5, 6

Different obligations may arise under customer contracts, insurance policies or sector rules. Allocate responsibility for assessing each one and record what was known, when it became known and why decisions were taken.

Make emergency authority usable

A response plan should identify who may engage forensic specialists, approve urgent costs, communicate externally and authorise alternative operating arrangements. Check those powers against the company’s actual delegations and banking mandates, including arrangements when key people are on leave.

Keep essential contact details and response documents securely accessible if ordinary systems fail. Agree an alternative communication channel in advance and retain payment verification controls. An urgent instruction, even one apparently delivered in a familiar voice, should be independently verified through an established contact route.

Coordinate restoration with preservation of relevant logs and records. A contemporaneous incident chronology can support notifications, insurance claims and later disputes.

Run the exercise before year end

Before key staff go on leave, test a simple scenario: email and accounting systems are unavailable for three days and a usual payment approver cannot be reached. Bring management, the IT provider, finance and legal advisers into the same discussion.

Identify which activities must continue, who can authorise them and what information each decision requires. Test access to the documents and contacts involved. Assign an owner and deadline to every material gap.

At EAI Law, we help businesses align their governance, contracts and legal obligations with the way they operate. Preparing for disruption means making those arrangements work under pressure. When the systems go down, your business should still be able to make informed, authorised decisions and protect its position.

This article reflects the position as at 29 October 2026 and provides general information. Advice on a specific incident will depend on its facts and the applicable agreements.

References

  1. Institute of Directors in South Africa, King V Code on Corporate Governance for South Africa 2025, Principles 8 and 10, particularly practices 93(d) and 100–110; proportional application at page 2. Source
  2. IoDSA, King V release announcement, including its commencement and voluntary framework. Source
  3. Companies Act 71 of 2008, sections 76 and 77. Source
  4. Protection of Personal Information Act 4 of 2013, sections 19, 21 and 22. Source
  5. Information Regulator, security compromise reporting platform announcement, 7 April 2025, and fact sheet on handling security compromises. Source
  6. Information Regulator, fact sheet on handling security compromises. Source
  7. Transnet Ltd t/a National Ports Authority v Owner of MV Snow Crystal (250/07) [2008] ZASCA 27, paragraph 28, on supervening impossibility. This is authority on the general doctrine, not a cyberattack case. Source

Leave a Reply

Your email address will not be published. Required fields are marked *

Chat to EAI Law