Why regulators now care
Regulators act for three broad reasons: to protect individuals, whose data companies hold as custodians rather than owners; to protect markets, because investors trade on what companies tell them; and to protect society, because some services such as power, water, transport, banking and healthcare are essential to daily life. Many regulators have also concluded that the root cause of large incidents is rarely purely technical. More often it is a governance failure, with nobody senior paying attention or warnings ignored, so regulation increasingly targets leaders.
Across most countries and sectors, the expectations are broadly similar: know what data you hold, protect it sensibly, notice when something goes wrong, tell the right people promptly and honestly, and make sure leaders are paying attention. Because these obligations are predictable, they can be prepared for. The companies that struggle are usually meeting their regulators for the first time on their worst day. The chapter is explicit that it offers orientation, not legal advice.
Data protection and breach disclosure
The EU's General Data Protection Regulation is the best-known data-protection law and a reference point for many others. In broad terms it expects a lawful basis for using personal data, collecting and keeping no more than necessary, security suited to the risk, respect for individual rights, accountability backed by records, and reporting of breaches likely to pose a risk to individuals, generally within 72 hours of becoming aware where feasible. That window means reporting what you know and updating later, not waiting for certainty. Japan's Act on the Protection of Personal Information has made reporting certain categories of breach to the Personal Information Protection Commission, and notifying affected people, mandatory. The United States relies on a patchwork of sector, state and breach-notification laws.
A second category asks companies to tell the market when an incident matters to the business. Rules adopted by the US SEC in 2023 require companies listed in the US to disclose a material cybersecurity incident, generally within four business days of determining that it is material, and to describe their cyber risk management and board oversight each year. Materiality is a judgement that weighs financial, reputational, customer, regulatory and operational effects, and it should not be improvised at two in the morning. At Meridian Foods, an investor's due-diligence questionnaire prompts a two-page materiality guide naming the factors, the decision-makers and the need for a written record, with the board chair always informed.
Sector rules, and rules that arrive through customers
Financial services face detailed expectations, including the EU's Digital Operational Resilience Act. Card payments bring PCI DSS, a contractual standard that behaves much like regulation because failing it can end the ability to take cards. Health data is specially protected, and critical-infrastructure regimes such as the EU's NIS2 Directive place explicit duties on management bodies. A food company may fall within such regimes depending on its size and country, and even if it does not, its large retail customers may pass requirements down the supply chain through contracts and questionnaires. Rules often reach a business through commercial relationships rather than a regulator's letter.
For specialists, the chapter recommends a notification matrix prepared in advance, listing each obligation's trigger, clock, recipient and owner and rehearsed in exercises; one common control framework mapped to every regime; a register of contractual security and notification commitments; careful handling of cross-border data transfers; and public security claims that match reality.
Compliance is not the same as security
Compliance means meeting a defined set of requirements and being able to prove it; security means actually being protected against the threats you face. Like a driving test, an audit shows that a standard was met on a sample at a point in time. The chapter warns against compliance theatre, in which documents are polished for auditors while the controls they describe are neglected, and recommends treating compliance as a floor and a by-product of good security rather than a substitute for it.
Practical habits keep the distinction alive: ask what the audit did not test, ask for evidence that controls operate rather than merely exist (for example, a recent restore of the order system and how long it took), receive compliance status and security risk as separate reports, and treat audit findings as useful information rather than failures.
Director and officer liability in general terms
In many legal systems directors owe duties of care and good faith, and courts in several countries recognise a duty of oversight. Directors are generally not expected to prevent every incident, but they are expected to ensure a reasonable system for overseeing cyber risk and to act on warnings. The most exposed position is a breach after the board was warned and did nothing, or one where the board never asked. Newer regimes increasingly name management responsibilities, and public statements about security can create exposure if they prove misleading.
The protections are mostly governance habits: make sure there is an owner, a programme and a reporting line; keep minutes that show cyber risk was discussed, questioned and decided on; record the response to warnings; keep public statements honest; and understand what directors and officers insurance and cyber insurance cover. The chapter repeats that specific obligations vary widely and must be confirmed with qualified counsel.
KEY POINTS
Key points
- Keep a current list of the data-protection, disclosure and sector rules that apply in each country where you operate, with a named owner.
- Build a notification matrix covering regulators, customers and partners, with deadlines and owners, before an incident happens.
- Write down who decides materiality, which factors they weigh and how the reasoning is recorded.
- Ask what your last security audit did not test, and request evidence that key controls actually operate.
- Make sure board minutes record cyber discussions, questions, decisions and responses to warnings.
- Check that public statements about your security match reality.
QUESTIONS
Common questions
- What do data protection regulators expect from companies?
- Across most regimes, regulators expect a lawful reason for using personal data, collecting no more than needed, security appropriate to the risk, respect for individuals' rights, records that demonstrate accountability, and prompt reporting of certain breaches. They generally do not expect perfection, but evidence that the company acted reasonably. Laws differ by country and change often, so companies should confirm with qualified counsel which apply to them.
- What is the GDPR 72-hour breach notification rule?
- Under GDPR, a personal data breach likely to pose a risk to individuals must generally be reported to the supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of it. Where the risk to individuals is high, they must generally be told as well. The rule does not require knowing everything within three days; companies report what they know and update as they learn more.
- What do the SEC cybersecurity disclosure rules require?
- Rules adopted by the US Securities and Exchange Commission in 2023 apply to companies whose shares are publicly traded in the US. In general terms, they require disclosure of a material cybersecurity incident, usually within four business days of determining that it is material, and an annual description of how the company assesses and manages cyber risk, how the board oversees it and management's role. The materiality determination itself is expected without unreasonable delay.
- How should a company decide whether a cyber incident is material?
- Agree the process before an incident rather than during one. A short materiality guide can list the factors to weigh, such as estimated financial impact, number of customers affected, operational disruption, likely regulatory involvement and press interest, name who makes the call and require a written record of the reasoning. Materiality is a judgement, not a calculation.
- What is the difference between compliance and security?
- Compliance means meeting a defined set of requirements, such as a regulation, standard or contract, and being able to prove it. Security means actually being protected against the threats a company faces. Because an audit tests samples at a point in time, passing it does not show that the most important systems would withstand a determined attacker this month, so compliance should be treated as a floor, not a ceiling.
- Can company directors be personally liable for a cyber breach?
- It depends heavily on the country, the type of company, the director's role and the facts, so specific advice must come from qualified counsel. In general terms, directors are not expected to prevent every incident, but they are expected to ensure a reasonable system of oversight and to act on warnings. Board minutes showing that cyber risk was discussed, questioned and decided upon are an important record that the board did its job.