easy-accordion-free
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/mother99/jacksonholdingcompany.com/wp-includes/functions.php on line 6114zoho-flow
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/mother99/jacksonholdingcompany.com/wp-includes/functions.php on line 6114wordpress-seo
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/mother99/jacksonholdingcompany.com/wp-includes/functions.php on line 6114Post Content\u00a0\u00a0<\/p>\n
\u200b<\/p>\n
The Securities and Exchange Commission (SEC) has recently introduced new cyber rules that require organizations to disclose material cybersecurity incidents and provide information on their cybersecurity risk management strategies. These rules aim to ensure consistent and decision-useful disclosures regarding an organization’s exposure to cybersecurity risks and incidents.\u00a0\u00a0\u00a0<\/p>\n
We have reviewed the rules in a prior post<\/a>, but for review, the SEC requires the following:<\/a><\/p>\n Current reporting about material cybersecurity incidents on Form 8-K;\u00a0 \tCybersecurity disclosures must be presented in Inline eXtensible Business Reporting Language (Inline XBRL).<\/p>\n We must all be aware of the timing deadlines. By December 15<\/strong>, companies are required to begin disclosures of any cybersecurity incidents determined to be material within four business days on Form 8-K. Additionally, annual reports from December 15 onward should include descriptions of processes for assessing, identifying, and managing material risks from cybersecurity threats, as well as the board of directors’ oversight of such risks.<\/p>\n We suggest you gather your team, as noted below, to ensure you have discussed or refined your process for these new compliance requirements.\u00a0 As food for thought, we have gathered the below steps to initiate further discussions internally:<\/p>\n Rally your team for cyber filings: Gather your existing cross-functional team, consisting of CISO\/security teams, finance, legal, and audit professionals. This team (hopefully already assembled for current compliance) will play a crucial role in assessing, identifying, and managing cybersecurity risks, ensuring compliance with the new rules.\u00a0 Importantly, this team will have the critical role of determining what a material cybersecurity incident is that would require disclosure. Compliance with the SEC’s new cyber rules is crucial for organizations to protect themselves and their stakeholders from cybersecurity- and compliance-related risks. By considering these five steps, organizations can begin to navigate the regulatory landscape effectively and ensure they meet the requirements for disclosure and risk management. Naturally, this blog is not meant to be legal advice, however, we hope you find it useful in considering your compliance moving forward.<\/p>\n As organizations digest the new SEC cyber rules and consider how to best move forward with cyber risk management, we have introduced Risk360\u2122<\/a>, our<\/strong>data-driven product for managing cybersecurity risk. Risk36<\/a>0<\/a> is a comprehensive risk framework for powerful cyber risk quantification that ingests real data from an organization\u2019s Zscaler environment. Risk360 offers intuitive risk visualizations, risk mapped to stages of an attack, financial exposure detail, and board-ready reporting, along with detailed, actionable security risk insights to immediately use for mitigation.\u00a0<\/p>\n
\n\tPeriodic disclosures regarding, among other things:\u00a0
\n\tA registrant\u2019s policies and procedures to identify and manage cybersecurity risks;\u00a0
\n\t\tManagement\u2019s role in implementing cybersecurity policies and procedures;\u00a0
\n\t\tBoard of directors\u2019 cybersecurity expertise, if any, and its oversight of cybersecurity risk; and\u00a0
\n\t\tUpdates about previously reported material cybersecurity incidents;\u00a0<\/p>\nTiming<\/h3>\n
Initial thoughts on compliance<\/h3>\n
\n\tGain resolution on what is “material”: Work closely with your team to clearly define what constitutes a “material” cybersecurity incident for your organization. This can be challenging, as the idea of materiality is not always clear cut, so consider a process to rely on after any considerable cyber incident in order to make a determination. This will ensure the appropriate level of disclosure required under the new rules.
\n\tMove toward a cyber risk score and description: We are now asked in S-K Item(s) 106 (b) to describe \u201cpolicies and procedures to identify and manage cybersecurity risks.\u201d Implement a cyber risk quantification process to assess and manage cybersecurity risks effectively. This process should provide a clear risk scoring mechanism and a comprehensive description of the organization’s cyber risk management strategies.
\n\tStart board reporting on cyber risk now: Initiate regular reporting on cyber risk to the board by making it a permanent agenda item. This will ensure that the board is actively involved in overseeing cybersecurity risks and can provide valuable insights for annual filings.
\n\tCapture board expertise for next filing: Have a security leader engage the board to capture their expertise in the preparation of the next annual filing. The SEC tells us we must share \u201cmanagement\u2019s role and expertise in assessing and managing cybersecurity risk.\u201d<\/p>\n