Here we are, six months after the SEC's rule on cyber incident reporting last September. Let's start with why this new set of rules was issued. The SEC was prompted to create new rules regarding cybersecurity incident reporting to enhance and standardize disclosures related to cybersecurity risk management strategy, governance, and incidents by public companies. The main reasons included investor protection, to ensure that investors have timely and consistent information about material cybersecurity incidents that can significantly impact their investment decisions. Previously, there was a lack of consistency on how companies disclose cybersecurity information, and the requirements were very vague.
What the cyber incident reporting rules do
The new rules aim to standardize this process, but the scope of changes will take time to surface in practice. For risk management and strategy, the goal is to provide investors with a better understanding of a company's risk management and cybersecurity practices, which are increasingly important in today's digital economy. The SEC also wants transparency with respect to a company's governance and cybersecurity risk, including Board oversight and the role of management and other company leaders in managing these risks.
Protecting investors and standardizing risk reporting
The why boils down to protecting investors, customers, partners, and. Before the SEC regulations, investors and other stakeholders felt that answers to questions about security protocols were very subjective and based on what one individual within a company thought and was willing to disclose. Companies might demonstrate how they were compliant with PCI, HIPAA, etc., but that didn’t cover overall reporting for governance, risk, and compliance. Being compliant does not automatically mean that you are risk-free. The SEC is doing what it can to impose consistency for GRC reporting across every public company. All of that said, the regulations still have leeway for interpretation– much will be left up to the cybersecurity managers who are reporting the information.
Compliance does not automatically mean secure
Being compliant is not synonymous with being secure. Those are two different things. Compliance—whether it be HIPAA, PCI, SOC, any of those—are checkboxes, basically. I could show adherence to every requirement, meet those checkboxes, and still be at a high risk of data loss or operational shutdown. Companies really need to have an overall encompassing governance, risk and compliance framework in addition to any required compliance certifications.
The problem with checkboxes
How you create a GRC framework and report on it should be specific to your company and what it does for your customers. Does your organization really use those checkboxes as part of your overall plan? A lot of people have checkboxes. They put them away until next year, when they’ll break them back out as evidence of what they are doing for validation. Unfortunately, this is not really a security plan. It is just making sure you achieve compliance. An important detail to remember is that compliance alone doesn't mean you're actually safe. That, in essence, is why these SEC regulations are now in place.
When I have a discussion like this, I always like to clarify in a disclaimer that I'm not providing any legal advice. These are my insights based on my experience and my knowledge. I recommend that if someone has questions on how the new regulations will impact their specific organizational needs and business model, that they should reach out to their legal function.
Learn more about Altiam Digital Cybersecurity solutions.