By now, CFOs understand that the SEC’s final rule on cybersecurity disclosure requires public companies to give investors prompt, “decision-useful” information about material cybersecurity incidents, as well as periodic information on their approaches to cyber risk management, strategy and governance.
What they may not fully appreciate is the holistic, collaborative approach required to meet the new disclosure requirements.
CFOs may encounter challenges in applying “materiality” to cyber risks and cyber incidents. They may also face similar uncertainties in assessing their company’s cyber risk management, strategy and governance. In both cases, the path forward calls for careful coordination with the CISO and general counsel (GC) — and potentially the CIO/CTO and CEO.
The final rule requires public companies to describe in their annual 10-K filings the processes, if any, for assessing, identifying and managing material risks from cybersecurity threats, management’s role in assessing and managing those risks, and the board of directors’ oversight of risks from cybersecurity threats. It also requires timely disclosure of material cybersecurity incidents on Form 8-K — within four business days of determining that an incident is material.
Evaluating materiality is about much more than direct financial impacts when deciding whether and how to disclose a cyber incident under the rule. It’s a deliberative process that requires objective analysis of both quantitative and qualitative factors.
CFOs have a critical role helping their company produce accurate, well-reasoned and defensible cybersecurity disclosures on Forms 8-K and 10-K. To carry out this role with confidence, here are some questions to consider.
Have we reached a clear understanding with the finance, IT/security and legal teams about the quantitative and qualitative factors that go into evaluations of a cyber incident’s materiality and its reasonably likely impact on your company’s financial condition?
The SEC’s standard for materiality, as outlined in the rule’s adopting release, is anchored to what the Supreme Court has deemed material information. A fact is material if there is a “substantial likelihood that a reasonable investor would consider it important” or if it would have “significantly altered the ‘total mix’ of information made available.”
To apply this standard in the context of a cyber incident, your team should be prepared to conduct an objective analysis of both quantitative and qualitative factors, including evaluation of the incident’s impact and reasonably likely impacts.
As CFO, you may think in terms of a quantitative, financial materiality threshold: Was this attack costly enough to be considered material? But as the definition states, materiality judgments require going beyond purely quantitative measures. Even less-costly breaches, or those that cause no financial harm, can lead to a determination that the incident is material. If sensitive customer data was hacked, for instance, your company’s reputation might suffer.
Your CISO and GC may have ideas regarding materiality that extend beyond financial loss. The GC, in particular, may need to consider legal questions that are more open-ended and qualitative. In this case, it’s important for you and them to agree on a collective, objective and defensible assessment.