CCPA data breach prevention


I. Introduction And Background

     A. Disclosure of Cybersecurity Incidents On Current Reports


     B. Disclosures about Cybersecurity Incidents in Periodic Reports


     C. Disclosure of a Registrant’s Risk Management, Strategy and     Governance Regarding Cybersecurity Risks

1.   Risk Management Strategy

2. Governance

3. Definitions


     D. Disclosure Regarding the Board of Directors’ Cybersecurity   Expertise


     E. Disclosure by Foreign Private Issuers


     F. Structured Data Requirements


     G. Applicability to Certain Issuers


     H. Need for New Rules and Commission Authority

     I. Compliance Dates


II. Other Matters

III. Economic Analysis

A. Introduction

B. Economic Baseline

C. Benefits and Costs of Final Rules

1. Benefits

 2. Costs

 3. Indirect Economic Effects

D. Effects on Efficiency, Competition, and Capital Formation

E. Reasonable Alternatives

IV. Paperwork Reduction Act


V. Final Regulatory Flexibility Analysis

    1. Estimate of Affected Small Entities and Impact to Those Entities
    2. Consideration of Alternatives

STATUTORY AUTHORITY

II. OTHER MATTERS

If any of the provisions of these rules, or the application thereof to any person or circumstance, is held to be invalid, such invalidity shall not affect other provisions or application of such provisions to other persons or circumstances that can be given effect without the invalid provision or application.

Pursuant to the Congressional Review Act, the Office of Information and Regulatory Affairs has designated these rules as not a “major rule,” as defined by 5 U.S.C. 804(2).

III. ECONOMIC ANALYSIS


         A. Introduction

We are mindful of the costs imposed by, and the benefits to be obtained from, our rules. Section 2(b) of the Securities Act408 and Section 3(f) of the Exchange Act direct the Commission, when engaging in rulemaking where it is required to consider or determine whether an action is necessary or appropriate in the public interest, to consider, in addition to the protection of investors, whether the action will promote efficiency, competition, and capital formation. Further, Section 23(a)(2) of the Exchange Act requires the Commission, when making rules under the Exchange Act, to consider the impact that the rules would have on competition, and prohibits the Commission from adopting any rule that would impose a burden on competition not necessary or appropriate in furtherance of the Exchange Act. The discussion below addresses the economic effects of the final rules, including the likely benefits and costs, as well as the likely effects on efficiency, competition, and capital formation.

Where possible, we have attempted to quantify the benefits, costs, and effects on efficiency, competition, and capital formation expected to result from the final rules. In some cases, however, we are unable to quantify the potential economic effects because we lack information necessary to provide a reasonable estimate. For example, we lack the data to estimate any potential decrease in mispricing that might result from the rule, because we do not know how registrants’ disclosures of cybersecurity risk and governance will change or which cybersecurity incidents that would go undisclosed under the current guidance will be disclosed under the final rules. Where we are unable to quantify the economic effects of the final rules, we provide a qualitative assessment of the effects, and of the impacts of the final rule on efficiency, competition, and capital formation. To the extent applicable, the views of commenters relevant to our analysis of the economic effects, costs, and benefits of these rules are included in the discussion below.

While cybersecurity incident disclosure has become more frequent since the issuance of the 2011 Staff Guidance and 2018 Interpretive Release, there is concern that variation persists in the timing, content, and format of registrants’ existing cybersecurity disclosure, and that such variation may harm investors (as further discussed below).  When disclosures about cybersecurity breaches are made, they may not be timely or consistent. Because of the lack of consistency in when and how companies currently disclose incidents, it is difficult to assess quantitatively the timeliness of disclosures under current practices. According to Audit, Analytics data, in 2021, it took on average of 42 days for companies to discover breaches, and then it took an average of 80 days and a median of 56 days for companies to disclose a breach after its discovery. These data do not tell us when disclosure occurs relative to companies’ materiality determinations. That said, the report notes that some breaches were disclosed for the first time to investors in periodic reports, the timing of which are unrelated to the timing of the incident or the company’s assessment of the materiality of the incident. This implies at least some cybersecurity incident disclosures were not timely with respect to determination of materiality. Because cybersecurity incidents can significantly affect registrants’ stock prices, delayed disclosure results in mispricing of securities, harming investors. Incident disclosure practices, with respect to both location and content, currently vary across registrants. For example, some registrants disclose incidents through Form 10-K, others Form 8-K, and still others on a company website, or in a press release. Some disclosures do not discuss whether the cybersecurity incident had material impact on the company. Additionally, evidence suggests registrants may be underreporting cybersecurity incidents. More timely, informative, and standardized disclosure of material cybersecurity incidents may help investors to assess an incident’s impact better.

While disclosures about cybersecurity risk management, strategy, and governance have been increasing at least since the issuance of the 2018 Interpretive Release, they are not currently provided by all registrants. Despite the increasing prevalence of references to cybersecurity risks in disclosures, however, registrants do not consistently or uniformly disclose information related to cybersecurity risk management, strategy, and governance. Registrants currently make such disclosures in varying sections of a company’s periodic and current reports, such as in risk factors, in management’s discussion and analysis, in a description of business and legal proceedings, or in financial statement disclosures, and sometimes include them with other unrelated disclosures. One commenter noted that current disclosure is “piecemeal” in nature and that the varying content and placement make it difficult for investors and other market participants to locate and understand the cybersecurity risks that registrants face and their preparedness for an attack, and to make comparisons across registrants.

As we discuss in more detail below, some commenters supported the proposed rule. Specifically, one commenter noted that markets responded negatively to delayed cybersecurity disclosures, suggesting that timeliness in disclosing incidents is valuable to investors. Further, some academic commenters submitted papers that they authored finding that evidence suggests that companies experiencing data breaches subsequently experience higher borrowing costs. On the other hand, other commenters contended that the proposed rules would hinder capital formation, particularly for small registrants, or that a more cost-effective alternative to the proposed rules would be to look to existing rules to elicit relevant disclosures, as articulated by the 2011 Staff Guidance and the 2018 Interpretive Release. Several commenters pointed out that the proposed disclosures on cybersecurity risk management, strategy, and governance might be overly prescriptive and would potentially provide a roadmap for threat actors, and that these rules could increase, not decrease costs. In response to those comments, these provisions have been modified in the final rule, which should reduce the perceived risk of providing a roadmap for threat actors compared with the proposal.

B. Economic Baseline

1.Current Regulatory Framework

To assess the economic impact of the final rules, the Commission is using as its baseline the existing regulatory framework and market practice for cybersecurity disclosure. Although a number of Federal and State rules and regulations obligate registrants to disclose cybersecurity risks and incidents in certain circumstances, the Commission’s regulations currently do not explicitly address cybersecurity.

As noted in the Proposing Release, cybersecurity threats and incidents continue to increase in prevalence and seriousness, posing an ongoing and escalating risk to public registrants, investors, and other market participants. The number of reported breaches disclosed by public companies has increased almost 600 percent over the last decade, from 28 in 2011 to 131 in 2020 and 188 in 2021. Although estimating the total cost of cybersecurity incidents is difficult, as many events may be unreported, some estimates put the economy-wide total costs as high as trillions of dollars per year in the U.S. alone. The U.S. Council of Economic Advisers estimated that in 2016 the total cost of cybersecurity incidents was between $57 billion and $109 billion, or between 0.31 and 0.58 percent of U.S. GDP in that year. A more recent estimate suggests the average cost of a data breach in the U.S. is $9.44 million. Executives, boards of directors, and investors remain focused on the emerging risk of cybersecurity. A 2022 survey of bank Chief Risk Officers found that they identified managing cybersecurity risk as the top strategic risk. In 2022, a survey of audit committee members again identified cybersecurity as a top area of focus in the coming year.

In 2011, the Division of Corporation Finance issued interpretive guidance providing the Division’s views concerning operating registrants’ disclosure obligations relating to cybersecurity risks and incidents. This 2011 Staff Guidance provided an overview of existing disclosure obligations that may require a discussion of cybersecurity risks and cybersecurity incidents, along with examples of potential disclosures. Building on the 2011 Staff Guidance, the Commission issued the 2018 Interpretive Release to assist operating companies in preparing disclosure about cybersecurity risks and incidents under existing disclosure rules. In the 2018 Interpretive Release, the Commission reiterated that registrants must provide timely and ongoing information in periodic reports (Form 10-Q, Form 10-K, and Form 20-F) about material cybersecurity risks and incidents that trigger disclosure obligations. Additionally, the 2018 Interpretive Release encouraged registrants to continue to use current reports (Form 8-K or Form 6-K) to disclose material information promptly, including disclosure pertaining to cybersecurity matters. Further, the 2018 Interpretive Release noted that to the extent cybersecurity risks are material to a registrant’s business, the Commission believes that the required disclosure of the registrant’s risk oversight should include the nature of the board’s role in overseeing the management of that cybersecurity risk. The 2018 Interpretive Release also stated that a registrant’s controls and procedures should enable it to, among other things, identify cybersecurity risks and incidents and make timely disclosures regarding such risks and incidents. Finally, the 2018 Interpretive Release highlighted the importance of insider trading prohibitions and the need to refrain from making selective disclosures of cybersecurity risks or incidents.

In keeping with existing obligations, companies are increasingly acknowledging cybersecurity risks in their disclosures. One analysis of disclosures made by Fortune 100 companies that filed 10-Ks and proxy statements found 95 percent of those companies disclosed a focus on cybersecurity risk in the risk oversight section of their proxy statements filed in the period ending in May 2022, up from 89 percent of filings in 2020 and 76 percent in 2018.Disclosures of efforts to mitigate cybersecurity risk were found in 99 percent of proxy statements or Forms 10-K, up from 93 percent in 2020 and 85 percent in 2018. The Fortune 100 list is composed of the highest-revenue companies in the United States. As discussed later in this economic analysis, we observed the overall rate of disclosure across not just the largest, but all filers, approximately 8,400, to be approximately 73 percent. Further, one commenter noted that current disclosures are “scattered and unpredictable” rather than “uniform,” which “diminishes their effectiveness,” and so the final rule should improve investors’ ability to find and compare disclosures.

Registrants currently are and may continue to be subject to other cybersecurity incident disclosure requirements developed by various industry regulators and contractual counterparties. As discussed in Section II, CIRCIA was passed in March 2022 and requires CISA to develop and issue regulations on cybersecurity reporting. As set forth in CIRCIA, once those regulations are adopted, covered entities will have 72 hours to report covered cybersecurity incidents to CISA and will also be required to report a ransom payment as the result of a ransomware attack within 24 hours of the payment being made. In addition, Federal contractors may be required to monitor and report cybersecurity incidents and breaches or face liability under the False Claims Act. An FCC rule directs covered telecommunications providers on how and when to disclose breaches of certain customer data. HIPAA requires covered entities and their business associates to provide notification following a breach of unsecured protected health information. Similar rules require vendors of personal health records and related entities to report data breaches to affected individuals and the FTC. All 50 states have data breach laws that require businesses to notify individuals of security breaches involving their personally identifiable information. There are other rules that registrants must follow in international jurisdictions. For example, in the European Union, the General Data Protection Regulation mandates disclosure of cybersecurity breaches.

These other cybersecurity incident disclosure requirements may cover some of the material incidents that registrants will need to disclose under the final rules. However, not all registrants are subject to each of these other incident disclosure requirements and the timeliness and public reporting elements of these requirements vary, making it difficult for investors and other market participants to be alerted to the breaches and to gain an adequate understanding of the impact of such incidents on a registrant.

Some registrants are also subject to other mandates regarding cybersecurity risk management, strategy, and governance. For instance, government contractors may be subject to the Federal Information Security Modernization Act, and use the NIST framework to manage information and privacy risks. Certain financial institutions may be subject to the FTC’s Standards for Safeguarding Customer Information Rule, requiring an information security program, including a qualified individual to oversee the security program, and the provision of periodic reports on the cybersecurity program to a company’s board of directors or equivalent governing body. Under HIPAA regulations, covered entities are subject to rules that require protection against reasonably anticipated threats to electronic protected health information. International jurisdictions also have cybersecurity risk mitigation measures and governance requirements (see, for example, the GDPR). These rules and regulations provide varying standards and requirements for disclosing cybersecurity risk management, strategy, and governance, and may not provide investors with public or clear and comparable disclosure regarding how a particular registrant manages its cybersecurity risk profile.

2. Affected Parties

The parties that are likely to be affected by the final rules include investors, registrants, other market participants that use the information provided in company filings (such as financial analysts, investment advisers, and portfolio managers), and external stakeholders such as consumers and other companies in the same industry as affected companies.

We expect the final rules to affect all registrants with relevant disclosure obligations on Forms 10-K, 20-F, 8-K, or 6-K. This includes (1) approximately 7,300 operating companies filing on domestic forms (of which, approximately 120 are business development companies) and (2) 1,174 FPIs filing on foreign forms, based on all companies that filed such forms or an amendment thereto during calendar year 2022. Our textual analysis of all calendar year 2022 Form 10-K filings and amendments reveals that approximately 73 percent of domestic filers made some kind of cybersecurity-related disclosures, whether of incidents, risk, or governance.

We also analyzed calendar year 2022 Form 8-K and Form 6-K filings. There were 71,505 Form 8-K filings in 2022, involving 7,416 filers, out of which 35 filings reported material cybersecurity incidents. Similarly, there were 27,296 Form 6-K filings in 2022, involving 1,161 filers, out of which 22 filings reported material cybersecurity incidents.

C. Benefits and Costs of the Final Rules

The final rules will benefit investors, registrants, and other market participants, such as financial analysts, investment advisers, and portfolio managers, by providing more timely and informative disclosures relating to cybersecurity incidents and cybersecurity risk management, strategy, and governance, facilitating investor decision-making and reducing information asymmetry in the market. The final rules also will entail costs. A discussion of the anticipated economic costs and benefits of the final rules is set forth in more detail below. We first discuss benefits, including benefits to investors and other market participants. We subsequently discuss costs, including the cost of compliance with the final rules. We conclude with a discussion of indirect economic effects on investors, external stakeholders such as consumers, and companies in the same industry with registrants subject to this rule, or those facing similar cybersecurity threats.

1. Benefits

Existing shareholders, and those seeking to purchase shares in registrants subject to the final rules, will be the main beneficiaries of the enhanced disclosure of both cybersecurity incidents and cybersecurity risk management, strategy, and governance as a result of the final rules. Specifically, investors will benefit because: (1) more informative and timely disclosure will improve investor decision-making by allowing investors to better understand a registrant’s material cybersecurity incidents, material cybersecurity risks, and ability to manage such risks, reducing information asymmetry and the mispricing of securities in the market; and (2) more uniform and comparable disclosures will lower search costs and information processing costs. Other market participants that rely on financial statement information to provide services to investors, such as financial analysts, investment advisers, and portfolio managers, will also benefit.

a. More Timely and Informative Disclosure

The final rules provide more timely and informative disclosures, relative to the current disclosure environment, which will allow investors to better understand registrants’ cybersecurity incidents, risks, and ability to manage such risks as well as reduce mispricing of securities in the market. Timeliness benefits to investors will result from the requirement to disclose cybersecurity incidents within four business days of determining an incident was
material, as well as the requirement to amend the disclosure to reflect material changes. Information benefits to investors will result from the disclosure of both (1) cybersecurity incidents and (2) cybersecurity risk management, strategy, and governance. Together, the timeliness and information benefits created by the final rules will reduce market mispricing and information asymmetry and potentially lower firms’ cost of capital.

We anticipate Item 1.05, governing cybersecurity incident disclosure on Form 8-K, will lead to more timely disclosure to investors. Currently, there is not a specific requirement for a registrant to disclose a cybersecurity incident to investors in a timely manner after its discovery and determination of material impact. Item 1.05’s requirement to disclose a material cybersecurity incident on Form 8-K within four business days after determining the incident is material will improve the overall timeliness of the disclosure offered to investors—disclosure that is relevant to the valuation of registrants’ securities. It is well-documented in the academic literature that the market reacts negatively to announcements of cybersecurity incidents. For example, one study finds a statistically significant mean cumulative abnormal return of -0.84 percent in the three days following cyberattack announcements, which, according to the study, translates into an average value loss of $495 million per attack. One commenter argued that the magnitude of stock market reaction to cybersecurity incidents from this study would not be considered significant by market participants, stating that “if a stock had a historical standard deviation of 1 percent and moved 0.8 percent on news, most market participants would suggest that the news was either not significant or the market had priced in that news so the reaction was muted.” We note, however, that a cumulative abnormal return (CAR) of -0.84 percent refers not to the total return but to the return relative to how stocks in similar industries and with similar risk profiles moved; thus, indeed, a statistically significantly negative CAR represents a meaningful reaction and change to how the stock price would have moved that day absent the announcement of the cybersecurity incident. By allowing investors to make decisions based on more current, material, information, Item 1.05 will reduce mispricing of securities and information asymmetry in the market.

Information asymmetries due to timing could also be exploited by the malicious actors who caused a cybersecurity incident, those who could access and trade on material information stolen during a cybersecurity incident, or those who learn about the incident before public disclosure, causing further harm to investors who trade unknowingly against those with inside information. Malicious actors may trade ahead of an announcement of a data breach that they caused or pilfer material information to trade on ahead of company announcements. Trading on undisclosed cybersecurity information is particularly pernicious, because profits generated from this type of trading provide incentives for malicious actors to “create” more incidents and proprietary information to trade on, further harming the shareholders of impacted companies. Employees or related third-party vendors of a company experiencing a cybersecurity incident may also learn of the incident and trade against investors in the absence of disclosure. More timely disclosure as a result of Item 1.05 will reduce mispricing by reducing windows of information asymmetry in connection with a material cybersecurity incident, thereby reducing opportunities to exploit the mispricing, enhancing investor protection.

A commenter noted that there is risk the rule could, under certain conditions, aid stock manipulation efforts by malicious actors, offsetting these benefits. One commenter suggested that mandated disclosure timing could make public cybersecurity incident disclosure dates more predictable, and thus trading strategies based on the accompanying negative stock price reaction more consistent, to the extent malicious actors can monitor or control discovery of breaches they cause and correctly anticipate materiality determination timing. Their ability to do this is unclear, but we note that if the final rules increase the precision of strategies by attackers that involve shorting the stock of their targets, that would reduce the benefit of the final rules.

Item 1.05 allows registrants to delay filing for up to 30 days if the Attorney General determines that the incident disclosure would pose a substantial risk to national security or public safety and notifies the Commission of such determination in writing. The delay may be extended up to an additional 30 days if the Attorney General determines disclosure continues to pose a substantial risk to national security or public safety and notifies the Commission of such determination in writing. In extraordinary circumstances, disclosure may be delayed for a final additional period of up to 60 days if the Attorney General determines that disclosure continues to pose a substantial risk to national security and notifies the Commission of such determination in writing. Beyond the final 60-day delay, if the Attorney General indicates that further delay is necessary, the Commission will consider additional requests for delay and may grant such relief through Commission exemptive order. These delay periods and possible exemptive relief would curb the timeliness benefits discussed above but would reduce the costs of premature disclosure such as alerting malicious actors targeting critical infrastructure that their activities have been discovered.

By requiring all material cybersecurity incidents to be disclosed, Item 1.05 will also provide investors more informative disclosure by increasing material cybersecurity incident disclosure. There are currently reasons that registrants do not disclose cybersecurity incidents. For example, a registrant’s managers may be reluctant to release information that they expect or anticipate will cause their stock price to suffer. Thus an agency problem prevents investors from receiving this useful information. In addition, registrants may consider only the benefits and costs that accrue to them when deciding whether to disclose an incident. As discussed in Section IV.C.3, incident disclosure can create indirect economic effects that accrue to parties other than the company itself. Companies focused on direct economic benefits, however, may not factor in this full range of effects resulting from disclosing cybersecurity incidents, resulting in less reporting and less information released to the market. The mandatory disclosure in Item 1.05 should thus lead to more incidents being disclosed, reducing mispricing of securities and information asymmetry in the market as stock prices will more accurately reflect registrants having experienced a cybersecurity incident.

Item 1.05 will also improve the informativeness of the content of cybersecurity incident disclosures. In 2022, when registrants filed a Form 8-K to report an incident, the Form 8-K did not necessarily state whether the incident was material, and in some cases, the Form 8-K stated that the incident was immaterial. Item 1.05 will require registrants to describe in an 8-K filing the material aspects of the nature, scope, and timing of a material cybersecurity incident and the material impact or reasonably likely material impact on the registrant, including on its financial condition and results of operations. The disclosure must also identify any information called for in Item 1.05(a) that is not determined or is unavailable at the time of the required filing. Registrants will then need to disclose this information in a Form 8-K amendment containing such information within four business days after the information is determined or becomes available. Item 1.05 is thus expected to elicit more pertinent information to aid investor decision-making. Additionally, the materiality requirement should minimize immaterial incident disclosure that might divert investor attention, which should reduce mispricing of securities. Numerous commenters on the Proposing Release agreed that more informative incident disclosure would be useful for investors.

Regulation S-K Items 106(b) and (c) of the final rules provide further benefits by requiring registrants to disclose, in their annual reports on Form 10-K, information about their cybersecurity risk management, strategy, and governance. The final rules require disclosure regarding a registrant’s processes, if any, for assessing, identifying, and managing material risks from cybersecurity threats, as well as disclosure of the registrant’s board of directors’ oversight of risks from cybersecurity threats and management’s role in assessing and managing material risks from cybersecurity threats. There are currently no disclosure requirements on Forms 10-K or 10-Q that explicitly refer to cybersecurity risks or governance, and thus Item 106 will benefit investors by eliciting relevant information about how registrants are managing their material cybersecurity risks.

One commenter took issue with the usefulness of the proposed disclosures, arguing, for example, that the particular requirement to disclose whether a registrant engages assessors, consultants, auditors, or other third parties in connection with any cybersecurity risk assessment program was unnecessary because there was no evidence that such third parties improved a registrant’s cyber risk management, and some companies have internal cybersecurity risk management capabilities. Some, however, have noted that the use of independent third-party advisors may be “vital to enhancing cyber resiliency” by validating that the risk management program is meeting its objectives. As discussed in Section II.C.1.c., it may be important for investors to know a registrant’s level of in-house versus outsourced cybersecurity capacity. Another commenter suggested that the requirement to disclose governance and risk management practices would be of limited value to investors, while being administratively burdensome. Other commenters said that the required disclosures about cybersecurity governance and risk management were too granular to be useful and suggested that the specific disclosures be replaced with a more high-level explanation of management’s and the board’s roles in cybersecurity risk management and governance. One such commenter stated that the proposed disclosures would create pressures to provide boilerplate responses to the specific items that would need to be disclosed instead of providing a robust discussion of the way a registrant would manage cybersecurity risk management and governance. Another commenter stated that granular disclosures “may result in overly detailed filings that have little utility to investors.” These commenters suggested that the specific disclosures should be replaced with a more high-level explanation of management’s and the board’s roles in cybersecurity risk management and governance.

In response to these comments, the Commission is not adopting certain proposed disclosure requirements, such as disclosure of whether the registrant has a designated chief information security officer. However, Items 106(b) and (c) still require risk, strategy and governance disclosures as we continue to believe disclosures of cybersecurity risk oversight and processes, as well as management’s role and relevant expertise, are important to investors. Improved timeliness and informativeness of cybersecurity disclosures may provide further benefit by lowering companies’ cost of capital. As detailed above, the final rules should reduce information asymmetry and mispricing of securities. In an asymmetric
information environment, investors are less willing to hold shares, reducing liquidity. Registrants may respond by issuing shares at a discount, increasing their cost of capital. By providing more and more credible disclosure, however, companies can reduce the risk of adverse selection faced by investors and the discount they demand, ultimately increasing liquidity and decreasing the company’s cost of capital. Investors benefit when the companies they are invested in enjoy higher liquidity. Item 1.05 enables companies to provide more credible disclosure because currently, investors do not know whether an absence of incident disclosure means no incidents have occurred, or one has but the company has not yet chosen to reveal it. By requiring all material incidents to be reported, Item 1.05 supplies investors greater assurance that, indeed, barring extraordinary circumstances, no disclosure means the company has not been aware for more than four business days of a material incident having occurred. Similarly, Item 106 should also generate more credible disclosure. Currently, voluntary cybersecurity risk management, strategy, and governance disclosures lack standardization and consistency, reducing their comparability and usefulness for investors. Without set topics that must be addressed, companies may disclose only the strongest aspects of their cybersecurity processes, if they disclose at all. By clarifying what registrants must disclose with respect to their cybersecurity risk management, strategy, and governance, Item 106 will reduce information asymmetry and provide investors and other market participants more certainty and easier comparability of registrants’ vulnerability to and ability to manage cybersecurity breaches, reducing adverse selection and increasing liquidity. Thus, the final rules could decrease cost of capital across registrants and increase company value, benefiting investors.

One commenter argued that smaller registrants are less likely than larger registrants to experience cybersecurity incidents and that cyberattacks are not material for smaller registrants. This could imply that the degree of cybersecurity-driven adverse selection faced by investors in small registrants might be less severe. If so, the potential benefit from improvement in liquidity and cost of capital due to the timeliness and information benefits from the final rules might be smaller for small registrants and their investors. The research this commenter cited to support this assertion found larger companies were more susceptible than smaller companies to a particular category of cybersecurity incidents—those involving personal information lost through hacking by an outside party—which composed less than one-quarter of all cyber incidents in the sample (1,580 out of 6,382). It is possible that malicious strategies that target personal information are particularly suited to larger, well-known companies, and thus the research may overstate the degree to which large companies are more susceptible to cybersecurity incidents generally. These strategies explicitly harm companies’ customers, and customer ill will is potentially more newsworthy and consequential for a larger, well-known company as compared to a smaller one. In contrast, ransomware attacks that target non-personal, internal company operations such as an information technology network, for example, are less concerned with causing reputational loss and thus may have an optimal target profile that favors smaller firms as much as larger firms. Additionally, smaller companies may have fewer resources and weaker processes in place to prevent cybersecurity attacks. Hence, it is not clear that smaller companies experience fewer material cybersecurity incidents generally. Others have noted that small companies are frequently targeted victims of cyberattacks, potentially leading to dissolution of the business. Thus, overall, we maintain that cybersecurity attacks are material for smaller reporting companies and that the final rules will serve to benefit them and their investors.

Overall, Form 8-K Item 1.05 and Regulation S-K Item 106 provide for timely, informative, and up-to-date disclosure of cybersecurity incidents, as well as disclosure that may provide insight into whether a registrant is prepared for risks from cybersecurity threats and has adequate cybersecurity risk management, strategy, and governance measures in place to reduce the likelihood of future incidents, reducing the likelihood of delayed or incomplete disclosure and benefiting investors and the market.

We believe enhanced information, timing, and completeness of disclosures as a result of Form 8-K Item 1.05 and Regulation S-K Item 106 will benefit not only investors but also other market participants that rely on registrant disclosures to provide services to investors. They, too, will be able to better evaluate registrants’ cybersecurity preparations and risks and thus provide better recommendations. We note that the potential benefit of these amendments could be reduced because some registrants already provide relevant disclosures. That said, we expect this same information will become more useful due to added context from, and easier comparisons with, the increased number of other registrants now providing these disclosures.

We are unable to quantify the potential benefit to investors and other market participants as a result of the increase in disclosure and improvement in pricing under the final rules. Such estimation requires information about the fundamental value of securities and the extent of the mispricing. We do not have access to such information and therefore cannot provide a reasonable estimate. One commenter suggested we use existing cyber disclosure models to “empirically determine” the current degree of market mispricing, but did not suggest what data the Commission could use to do so. The Commission cannot estimate the effects of undisclosed cybersecurity incidents that are creating market mispricing, as the relevant information was never released and the market was unable to react.

b. Greater Uniformity and Comparability

The final rules requiring disclosure about cybersecurity incidents and cybersecurity risk management, strategy, and governance should also lead to more uniform and comparable disclosures, in terms of both content and location, benefiting investors by lowering their search and information processing costs. Currently, registrants do not always use Form 8-K to report cybersecurity incidents. Even among registrants that do, reporting practices vary widely. Some provide a discussion of materiality, the estimated costs of an incident, or the remedial steps taken as a result of an incident, while others do not provide such disclosure or provide much less detail. Disclosures related to risk management, strategy, and governance also vary significantly across registrants—such information could be disclosed in places such as the risk factors section, the management’s discussion and analysis section, or not at all. For both types of disclosures, the final rules specify the topics that registrants should disclose. As a result, both incident disclosure and risk management, strategy, and governance disclosure should become more uniform across registrants, making them easier for investors and other market participants to compare. The final rules also specify the disclosure locations (e.g., Item 1C of Form 10-K), benefiting investors and other market participants further by reducing the time, cost, and effort it takes them to search for and retrieve information (as pointed out by commenters).

We note that to the extent that the disclosures related to cybersecurity risk management, strategy, and governance become too uniform or “boilerplate,” the benefit of comparability may be diminished. However, we believe that Item 106 requires sufficient specificity, tailored to the registrant’s facts and circumstances, to help mitigate any tendency towards boilerplate disclosures. Item 106 also provides a non-exclusive list of information that registrants should disclose, as applicable, which should help in this regard.

The requirement to tag the cybersecurity disclosure in Inline XBRL will likely augment the informational and comparability benefits by making the disclosures more easily retrievable and usable for aggregation, comparison, filtering, and other analysis. XBRL requirements for public operating company financial statement disclosures have been observed to mitigate information asymmetry by reducing information processing costs, thereby making the disclosures easier to access and analyze. While these observations are specific to operating company financial statement disclosures and not to disclosures outside the financial statements, such as the cybersecurity disclosures, they suggest that the Inline XBRL requirements should directly or indirectly (i.e., through information intermediaries such as financial media, data aggregators, and academic researchers) provide investors with increased insight into cybersecurity-related information at specific companies and across companies, industries, and time periods. Also, unlike XBRL financial statements (including footnotes), which consist of tagged quantitative and narrative disclosures, the cybersecurity disclosures consist largely of tagged narrative disclosures. Tagging narrative disclosures can facilitate analytical benefits such as automatic comparison or redlining of these disclosures against prior periods and the performance of targeted artificial intelligence or machine learning assessments (tonality, sentiment, risk words, etc.) of specific cybersecurity disclosures rather than the entire unstructured document.

In addition, by formalizing the disclosure requirements related to cybersecurity incidents and cybersecurity risk management, strategy, and governance, the final rules could reduce compliance costs for those registrants that are currently providing disclosure about these topics. The compliance costs would be reduced to the extent that those registrants may be currently over-disclosing information out of caution, to increase the perceived credibility of their disclosures, or to signal to investors that they are diligent with regard to cybersecurity. For instance, the staff has observed that some registrants provide Form 8-K filings even when they do not anticipate the incident will have a material impact on their business operations or financial results. By specifying that only material incidents require disclosure, the final rules should ease some of these concerns and reduce costs to the extent those costs currently exist. Investors will benefit to the extent the registrants they invest in enjoy lower compliance costs.

2. Costs

We also recognize that enhanced cybersecurity disclosure would result in costs to registrants, borne by investors. These costs include potential increases in registrants’ vulnerability to cybersecurity incidents and compliance costs. We discuss these costs below.

First, the disclosure about cybersecurity incidents and cybersecurity risk management, strategy, and governance could potentially increase the vulnerability of registrants. Since the issuance of the 2011 Staff Guidance, concerns have been raised that providing detailed
disclosures of cybersecurity incidents could, potentially, provide a road map for future attacks, and, if the underlying security issues are not completely resolved, could exacerbate the ongoing attack. The concern is that malicious actors could use the disclosures to potentially gain insights into a registrant’s practices on cybersecurity. As a result, the final incident disclosure rules could potentially impose costs on registrants and their investors, if, for example, additional threat actors steal more data or hamper breach resolution.

The final rules have been modified from the Proposing Release to mitigate disclosure of details that could aid threat actors, while remaining informative for investors. Form 8-K Item 1.05 will require registrants to timely disclose material cybersecurity incidents, describe the material aspects of the nature, scope, and timing of the incident, and, importantly, describe the material impact or reasonably likely material impact of the incident on the registrant. Focusing on the material impact or reasonably likely material impact of the incident rather than the specific or technical details of the incident should reduce the likelihood of providing a road map that threat actors can exploit for future attacks, and should reduce the risks and costs stemming from threat actors acting in this manner.

Similar concerns were raised by commenters about the required risk management, strategy, and governance disclosure. Items 106(b) and (c) require registrants to provide specified disclosure regarding their cybersecurity risk management processes and cybersecurity governance by the management and board. The required disclosure could provide malicious actors information about which registrants have weak processes related to cybersecurity risk management and allow such malicious actors to determine their targets accordingly.

However, academic research so far has not provided evidence that more detailed cybersecurity risk disclosures necessarily lead to more attacks. For example, one study finds that measures for specificity (e.g., the uniqueness of the disclosure) do not have a statistically significant relation with subsequent cybersecurity incidents. Another study finds that cybersecurity risk factor disclosures that involve terms about processes are less likely to be related to future breach announcements than disclosures that employ more general language. On the other hand, we note that the final rules will require more details of cybersecurity processes than what is explicitly required under the current rules, and the uniformity of the final rules might also make it easier for malicious actors to identify registrants with relatively weaker processes. Therefore, these academic findings might not be generalizable to the effects of the final rules. However, we also note that we have streamlined the disclosure obligations for Items 106 (b) and (c), in response to commenters’ concerns, to require a more principles-based discussion of a registrant’s processes instead of detailed disclosures on a specific set of items. This change should help ease concerns that the required cybersecurity risk management, strategy, and governance disclosures will help malicious actors choose targets. In addition, the potential costs resulting from the disclosure requirements might be partially mitigated to the extent that registrants decide to enhance their cybersecurity risk management in anticipation of the increased disclosure. This possibility is discussed below under Indirect Economic Effects. The final rules will also impose compliance costs. Registrants, and thus their investors, will incur one-time and ongoing costs to fulfill the new disclosure requirements under Item 106 of Regulation S-K. These costs will include costs to gather the information and prepare the disclosures. Registrants will also incur compliance costs to fulfill the disclosure requirements related to Form 8-K (Form 6-K for FPIs) incident disclosure. These costs include one-time costs to implement or revise their incident disclosure practices, so that any registrant that determines it has experienced a material cybersecurity incident will disclose such incident with the required information within four business days. Registrants may also incur ongoing costs to disclose in a Form 8-K report any material changes or updates relating to previously disclosed incidents, and we expect these costs to be higher for registrants with more incidents to disclose. The costs will be mitigated for registrants whose current disclosure practices match or are similar to those that are in the final rules. One commenter suggested that companies could incur costs to reconcile their existing cybersecurity activities and NIST-based best practices with the requirements of the final rules but, as discussed in Section II.C.3.c, the final rules are not in conflict with NIST and we do not anticipate that significant reconciliation will be needed.

The compliance costs will also include costs attributable to the Inline XBRL tagging requirements. Many commenters supported the XBRL tagging requirement, while one commenter suggested that it would be burdensome to add tagging given the time-sensitive nature of the disclosure requirements. Various preparation solutions have been developed and used by operating companies to fulfill XBRL requirements, and some evidence suggests that, for smaller companies, XBRL compliance costs have decreased over time. The incremental compliance costs associated with Inline XBRL tagging of cybersecurity disclosures will also be mitigated by the fact that most companies that will be subject to the requirements are already subject to other Inline XBRL requirements for other disclosures in Commission filings, including financial statement and cover page disclosures in certain periodic reports and registration statements. Such companies may be able to leverage existing Inline XBRL preparation processes and expertise in complying with the cybersecurity disclosure tagging requirements. Moreover, the one-year XBRL compliance period extension could further assuage concerns about the transition for registrants to comply with the new requirements.

Some commenters contended that the Proposing Release failed to consider the costs of the proposed rules adequately. We are generally unable to quantify costs related to the final rules due to a lack of data. For example, we are unable to quantify the impact of any increased vulnerability to existing or new threat actors arising from the required incident or risk management, strategy, or governance disclosures. Moreover, costs related to preparing cyberrelated disclosures are generally private information known only to the issuing firm, hence such data are not readily available to the Commission. There is also likely considerable variation in these costs depending on a given firm’s size, industry, complexity of operations, and other characteristics, which makes comprehensive estimates difficult to obtain. We note that the Commission has provided certain estimates for purposes of compliance with the Paperwork Reduction Act of 1995, as further discussed in Section V below. Those estimates, while useful to understanding the collection of information burden associated with the final rules, do not purport to reflect the full costs associated with making the required disclosures.

One commenter provided a numerical cost estimate, stating the initial costs of complying with the proposed rules would be $317.5 million to $523.4 million ($38,690 to $69,151 per regulated company), and future annual costs would be $184.8 million to $308.1 million ($22,300 to $37,500 per regulated company). We cannot directly evaluate the accuracy of these estimates because the commenter did not provide any explanation for how they were derived. We believe, however, these estimates likely significantly overstate the costs of the final rules.

First, the commenter overestimates the number of registrants who are likely to bear the full costs of new disclosures. Converting the total and per company cost estimates to registrant counts implies the commenter assumed these costs would be borne by approximately 8,000 companies, which would be nearly every registrant. As stated in Section IV.B.2 above, however, 73 percent of domestic filers in 2022 already made cybersecurity-related disclosures in Form 10-K filings and amendments, and 35 Form 8-K filings disclosed material cybersecurity incidents. While the degree to which registrants’ existing disclosures already may be in line with the requirements of the final rules varies—some registrants may need to make significant changes while others may not, especially given the guidance from the 2018 Interpretive Release—most registrants should not bear the full costs of compliance. In addition, while cybersecurity incident disclosure is expected to increase as a result of Item 1.05, we do not expect that most companies will need to report in any given year. Extrapolating from the current numbers of incidents reported—for example, public companies disclosed 188 reported breaches in 2021—we expect that the overwhelming majority of registrants will not experience a material breach and will not need to disclose cybersecurity incidents and incur the ongoing associated costs. They may, however, revisit their disclosure controls initially, to ensure they are capturing what the rule requires.

Second, we have made changes from the proposed rules that would also reduce costs as compared with the proposal. Some of these changes concerned aspects of the proposed rules that the commenter noted would be burdensome. For example, the commenter states that “potential material incidents in the aggregate would be difficult to identify and operationally challenging to track.” The commenter also states “the SEC underestimates the burdens related to tracking ‘several small but continuous cyberattacks against a company,’ which may or may not prove to be material.” These comments refer to proposed Item 106(d)(2), which would have required disclosure when a series of previously undisclosed individually immaterial cybersecurity incidents become material in the aggregate. In response to comments, we are not adopting this aspect of the proposal and instead have added “a series of related unauthorized occurrences” to the definition of “cybersecurity incident,” which may help address this concern about the burden of the proposal. The comment letter also stated that “cybersecurity talent is scarce globally. From a personnel standpoint, it’s unclear where companies would get the so-called cybersecurity experts that the proposed regulation would mandate. There is a well-documented lack of cybersecurity talent for the public and private sectors that would unquestionably affect companies’ recruitment of board cybersecurity experts.” We are not adopting proposed 407(j) about the cybersecurity expertise, if any, of a registrant’s board members, which may have factored into the commenter’s cost estimates. Additionally, the proposal would not have mandated recruitment of cybersecurity experts, only disclosure of their presence. Additional streamlining of requirements in the final rules (e.g., reduced granularity of cybersecurity incident disclosure requirements) should further reduce costs from what might have been estimated using the Proposing Release.

Another commenter stated that the Commission’s calculation of costs and benefits does not adequately address the impact of different but overlapping disclosure and reporting requirements that may escalate burdens and costs. We acknowledge the possibility that to the extent different information has to be reported pursuant to different regulations, laws, or other requirements, there could be a greater cost because of the demands to keep track of and manage the multiple different disclosure regimes. However, to the extent that certain other existing requirements may involve monitoring cybersecurity incidents or assessing an incident’s impact on the registrant, the registrant may be able to leverage existing disclosures to reduce the burden of complying with the final rules. Additionally, as noted in Section II.A.3 those other regulations generally serve different purposes than the final rules, and we believe that the benefits of the final rules justify the costs.

One commenter raised a concern that the costs of the rules reached the threshold of an “economically significant rulemaking” under the Unfunded Mandate Reform Act of 1995 (“UMRA”) and the Small Business Regulatory Enforcement Fairness Act, thus requiring an “enhanced economic analysis.” The requirement to issue an analysis under the UMRA does not apply to rules issued by independent regulatory agencies.

The compliance costs of the final rules could be disproportionately burdensome to smaller registrants, as some of these costs may have a fixed component that does not scale with the size of the registrant. Also, smaller registrants may have fewer resources with which to implement these changes. One commenter suggested this could lead some small companies seeking to conduct an initial public offering to reconsider. Commenters also noted that smaller companies may not yet have a mature reporting regime and organizational structure and would benefit from an onramp to compliance. We are not adopting some proposed requirements (e.g., disclosing whether the board includes a cybersecurity expert), and thus the cost burden of the final rules should not be as high as initially proposed. We also are delaying compliance for incident disclosure for smaller reporting companies by providing an additional phase-in period of 180 days after the non-smaller reporting company compliance date for smaller reporting companies, which will delay compliance with these requirements for 270 days from effectiveness of the rules. To the extent smaller reporting companies are less likely than larger companies to have incident disclosure processes in place, they could benefit from additional time to comply. An extended compliance date may also permit smaller reporting companies to benefit from seeing how larger companies implement these disclosures. Investors in these smaller registrants could benefit from higher disclosure quality afforded by the delay, although some benefits, such as the reduction in asymmetric information and mispricing, would also be delayed.

3. Indirect Economic Effects

While the final rules only require disclosures—not changes to risk management practices—the requirement to disclose and the disclosures themselves could result in certain indirect benefits and costs. In anticipating investor reactions to the required disclosures, for example, registrants might devote more resources to cybersecurity governance and risk management in order to be able to disclose those efforts. Although not the purpose of this rule, registrants devoting resources to cybersecurity governance and risk management could reduce both their susceptibility to a cybersecurity attack, reducing the likelihood of future incidents, as well as the degree of harm suffered from an incident, benefiting registrants and investors. The choice to dedicate these resources would also represent an indirect cost of the final rules, to the extent registrants do not already have governance and risk management measures in place. As with compliance costs, the cost of improving cybersecurity governance and risk management could be proportionally higher for smaller companies if these registrants have fewer resources to implement these changes, and to the extent these costs do not scale with registrant size.

In addition, the requirement to tag the cybersecurity disclosure in Inline XBRL could have indirect effects on registrants. As discussed in Section III.C.1.a.(ii), XBRL requirements for public operating company financial statement disclosures have been observed to reduce information processing cost. This reduction in information processing cost has been observed to facilitate the monitoring of registrants by other market participants, and, as a result, to influence registrants’ behavior, including their disclosure choices.

The requirement in Item 1.05 that registrants timely disclose material cybersecurity incidents could also indirectly affect consumers, and external stakeholders such as other registrants in the same industry and those facing similar cybersecurity threats. Cybersecurity incidents can harm not only the company that suffers the incident but also other businesses and consumers. For example, a cybersecurity breach at one company, such as a gas pipeline, or a power company, may cause a major disruption or shutdown of a critical infrastructure industry, resulting in broad losses throughout the economy. Timely disclosure of cybersecurity incidents required by Item 1.05 could increase awareness by those external stakeholders and companies in the same industry that the malicious activities are occurring, giving them more time to mitigate any potential damage.

To the extent that Item 1.05 increases incident disclosure, consumers may learn about a particular cybersecurity breach and therefore take appropriate actions to limit potential economic harm that they may incur from the breach. For example, there is evidence that increased disclosure of cybersecurity incidents by companies can reduce the risk of identity theft for individuals. Also, consumers may be able to make better informed decisions about which companies to entrust with their personal information.

As discussed above, to the extent that registrants may decide to enhance their cybersecurity risk management in anticipation of the increased disclosure, that could reduce registrants’ susceptibility to and damage incurred from a cybersecurity attack. This reduced likelihood of and vulnerability to future incidents could reduce the negative externalities of those incidents, leading to positive spillover effects and a reduction in overall costs to society from
these attacks.

However, the magnitude of this and the other indirect effects discussed above would depend upon factors outside of the specific disclosures provided in response to the final rule, and therefore it is difficult to assess with certainty the likelihood or extent of these effects.

D. Effects on Efficiency, Competition, and Capital Formation We believe the final rules should have positive effects on market efficiency. As discussed above, the final rules should improve the timeliness and informativeness of cybersecurity incident and risk disclosure. As a result of the disclosure required by the final rules, investors and other market participants should better understand the cybersecurity threats registrants are facing, their potential impact, and registrants’ ability to respond to and manage risks. Investors and other market participants should thereby better evaluate registrants’ securities and make more informed decisions. As a result, the required disclosures should reduce information asymmetry and mispricing in the market, improving market efficiency. More efficient prices should improve capital formation by increasing overall public trust in markets, leading to greater investor participation and market liquidity. The final rules also could promote competition among registrants with respect to improvement in both their cybersecurity risk management and transparency in communicating their cybersecurity processes. To the extent investors view strong cybersecurity risk management, strategy, and governance favorably, registrants disclosing more robust processes, more clearly, could benefit from greater interest from investors, leading to higher market liquidity relative to companies that do not. Customers may also be more likely to entrust their business to companies that protect their data. Registrants that to date have invested less in cybersecurity preparation could thus be incentivized to invest more, to the benefit of investors and customers, in order to become more competitive. To the extent that increased compliance costs resulting from the final rules prevent smaller companies from entering the market, as a commenter suggested, the final rules could reduce the ability of smaller companies to compete and thereby reduce competition overall.

E. Reasonable Alternatives

1. Website Disclosure

As an alternative to Form 8-K disclosure of material cybersecurity incidents, we considered providing registrants with the option of disclosing this information instead through company websites, if the company disclosed its intention to do so in its most recent annual report, and subject to information availability and retention requirements. While this approach may be less costly for the company because it may involve fewer compliance costs, disclosures made on company websites would not be located in a central depository, such as the EDGAR system, and would not be in the same place as other registrants’ disclosures of material cybersecurity incidents, nor would they be organized into the standardized sections found in Form 8-K and could thus be less uniform. Even if we required registrants to announce the disclosure, or to alert the Commission to it, the information would still be more difficult for investors and market participants to locate and less uniform than Form 8-K.

The lack of a central repository, and a lack of uniformity of website disclosures, could increase the costs for investors and other market participants to search for and process the information to compare cybersecurity risks across registrants. Additionally, such disclosure might not be preserved on the company’s website for as long as it would be on the EDGAR system when the disclosure is filed with the Commission, because registrants may not keep historical information available on their websites indefinitely and it could be difficult to determine whether the website information had moved or changed. Therefore, this approach would be less beneficial to investors, other market participants, and the overall efficiency of the market.

2. Disclosure through Periodic Reports

We also considered requiring disclosure of material cybersecurity incidents through quarterly or annual reports, as proposed, instead of Form 8-K. Reporting material cybersecurity incidents at the end of the quarter or year would allow registrants more time to assess the financial impact of such incidents. The resulting disclosure might be more specific or informative for investors and other market participants to value the securities and make more informed decisions. The compliance costs would be less under this alternative, because registrants would not have to file as frequently. And, it might further reduce the risk that disclosure could provide timely information to attackers.

However, this alternative also would lead to less timely reporting on material cybersecurity incidents. As a result, the market would not be able to incorporate the information related to cybersecurity risk into securities prices in as timely a manner, and investors and other market participants would not be able to make as informed decisions as they could under the requirements of Item 1.05. Additionally, as previously discussed, less timely reporting could adversely impact external stakeholders, such as other registrants in the same industry and those facing similar cybersecurity threats, and consumers whose data were compromised.

Relatedly, we proposed requiring registrants to disclose material changes and additions to previously reported cybersecurity incidents on Forms 10-K and 10-Q instead of on an amended Form 8-K. However, as discussed above, we believe using Form 8-K would be more timely and consistent; all disclosures concerning material cybersecurity incidents, whether new or containing information not determined or unavailable initially, will be disclosed on the same form.

3. Exempt Smaller Reporting Companies

We also considered exempting smaller reporting companies from the final rules. Exempting smaller reporting companies from the disclosure requirements of the final rules would avoid compliance costs for smaller companies, including those compliance costs that could disproportionately affect smaller companies. As noted earlier, however, we are not adopting some proposed requirements (e.g., disclosing whether the board includes a cybersecurity expert) and modifying others (e.g., requiring a description of cybersecurity “processes” instead of more formal “policies and procedures”), and thus the cost burden of the final rules should not be as high as initially proposed. This should mitigate some of the concerns raised by commenters and would also reduce the potential value of an exemption. Moreover, an exemption would remove the benefit to investors of informative, timely, uniform, and comparable disclosure with regard to smaller companies. And although one commenter argued for an exemption based on a perception that smaller companies are less likely to experience cybersecurity incidents, for the reasons explained in Section IV.C.1.b, we believe that smaller companies are still at risk for material cybersecurity incidents. This aligns with comments we received opposing an exemption for smaller reporting companies.

Lastly, one commenter that argued for an exemption cited the Proposing Release, which noted a potential for increased cost of capital for registrants that do not have cybersecurity programs once disclosures are mandated; the commenter stated that these would disproportionately be smaller registrants. We have reconsidered the argument that registrants without robust cybersecurity processes in place might face a higher cost of capital and as a result would be priced unfavorably, and no longer believe it to be accurate. It is indeed possible that companies that reveal what investors consider to be less robust cybersecurity risk management, strategy, and governance processes may experience a decline in stock price. However, because the risk of cybersecurity attacks should be idiosyncratic, this decline would likely be due to investors updating their expectations of future cash flows for this firm to incorporate higher likelihood of a future incident—moderating the decline should future incidents occur—not an increase in fundamental market risk and thus cost of capital. In addition, to the extent investors already rationally anticipate that smaller registrants or registrants that have not previously disclosed such information have less robust policies, there may be less or no stock price decline as a result of Item 106, as these disclosures would merely confirm expectations. Thus, increases in cost of capital should not be prevalent in this regard and should not be a reason to exempt small firms from the final rules.

IV. PAPERWORK REDUCTION ACT

A. Summary of the Collections of Information

Certain provisions of our rules and forms that will be affected by the final rules contain “collection of information” requirements within the meaning of the Paperwork Reduction Act (“PRA”). The Commission published a notice requesting comment on changes to these collections of information in the Proposing Release and submitted these requirements to the Office of Management and Budget (“OMB”) for review in accordance with the PRA.

The hours and costs associated with preparing, filing, and sending the forms constitute reporting and cost burdens imposed by each collection of information. An agency may not conduct or sponsor, and a person is not required to comply with, a collection of information unless it displays a currently valid OMB control number. Compliance with the information collections is mandatory. Responses to the information collections are not kept confidential and there is no mandatory retention period for the information disclosed. The titles for the affected collections of information are:

    • “Form 8-K” (OMB Control No. 3235-0060);
    • “Form 6-K” (OMB Control No. 3235-0116);
    • “Form 10-K” (OMB Control No. 3235-0063); and
    • “Form 20-F” (OMB Control No. 3235-0288).

The Commission adopted all of the existing regulations and forms pursuant to the Securities Act and the Exchange Act. The regulations and forms set forth disclosure requirements for current reports and periodic reports filed by registrants to help shareholders make informed voting and investment decisions.

A description of the final amendments, including the need for the information and its use, as well as a description of the likely respondents, can be found in Section II above, and a discussion of the economic effects of the final amendments can be found in Section IV above.

B. Summary of Comment Letters and Revisions to PRA Estimates

In the Proposing Release, the Commission requested comment on the PRA burden hour and cost estimates and the analysis used to derive the estimates. While a number of parties commented on the potential costs of the proposed rules, only one commenter spoke specifically to the PRA analysis, arguing that the proposal “cannot be justified under the Paperwork Reduction Act” because of an “unreasonable” number of separate disclosures and because “the amount of information the Proposal would require to be produced is unwarranted in light of other, existing regulations.” The commenter further alleged that the Proposing Release’s “calculation of costs and benefits is skewed” because “different but overlapping disclosure and reporting requirements do not correlate with lower burdens on information providers, but rather, escalated burdens and costs.

While we acknowledge the commenter’s concerns about costs of the proposal, for the reasons discussed in Section II.H and elsewhere throughout this release, we believe the information required by the final rules is necessary and appropriate in the public interest and for the protection of investors. Further, a discussion of the economic effects of the final
amendments, including consideration of comments that expressed concern about the expected costs associated with the proposed rules, can be found in Section IV above. With regard to the calculation of paperwork burdens, we note that both the Proposing Release’s PRA analysis and our PRA analysis of the final amendments here estimate the incremental burden of each new or revised disclosure requirement individually and fully comport with the requirements of the PRA. Our estimates reflect the modifications to the proposed rules that we are adopting in response to commenter concerns, including streamlining some of the proposed rule’s elements to address concerns regarding the level of detail required and the anticipated costs of compliance.

C. Effects of the Amendments on the Collections of Information

The following PRA Table 1 summarizes the estimated effects of the final amendments on the paperwork burdens associated with the affected collections of information listed in Section V.A.

PRA Table 1 – Estimated Paperwork Burden of Final Amendments

Final Amendments and EffectsAffected FormsEstimated Burden IncreaseNumber of Estimated
Affected Responses*
Form 8-K
• Add Item 1.05 equiring disclosure of material cybersecurity incidents within four business days following
determination of materiality.
Form 8-K9 hour increase in compliance burden per form200 Filings
Form 6-K
• Add “cybersecurity incident” to the list in General Instruction B of information required to be furnished on Form 6-K.Form 6-K9 hour increase in compliance burden per form20 Filings
Regulation S-K Item 106
• Add Item 106(b) requiring disclosure
regarding cybersecurity risk management and strategy.
Form 10-K
Form 10-K: 10 hour increase in compliance burden per form
8,292 Filings
• Add Item 106(c) requiring disclosure
regarding cybersecurity governance.
Form 20-FForm 20-F: 10 hour increase in compliance burden per form729 Filings

* The OMB PRA filing inventories represent a three-year average. Averages may not align with the actual number of filings in any given year.

The estimated burden increases for Forms 8-K, 10-K, and 20-F reflect changes from the estimates provided in the Proposing Release. There, the Commission estimated that the average incremental burden for an issuer to prepare the Form 8-K Item 1.05 disclosure would be 10 hours. The proposed estimate included the time and cost of preparing the disclosure, as well as tagging the data in XBRL. The changes we are making to Item 1.05 in the final rules should generally reduce the associated burden by an incremental amount in most cases. We therefore estimate that Form 8-K Item 1.05 will have a burden of 9 hours, on par with the average burdens of existing Form 8-K items, which is 9.21 hours.

In the Proposing Release, the Commission estimated that the average incremental burden for preparing Form 10-K stemming from proposed Item 106 would be 15 hours. Similarly, the Commission estimated that proposed Item 106 would result in an average incremental burden for preparing Form 20-F of 16.5 hours. The proposed estimates included the time and cost of preparing the disclosure, as well as tagging the data in XBRL. We estimate the changes we are making to Item 106 in the final rules should generally reduce the associated burden by one-third due to the elimination of many of the proposed disclosure items; accordingly, we have reduced the estimated burden to 10 hours from 15 hours for Form 10-K, and to 10 hours from 16.5 hours for Form 20-F.

We have not modified the estimated number of estimated affected responses for Form 8-K and Form 6-K from what was proposed. As noted in the Proposing Release, not every filing of these forms would include responsive disclosures. Rather, these disclosures would be required only when a registrant has made the determination that it has experienced a material cybersecurity incident. Further, in the case of Form 6-K, the registrant would only have to provide the disclosure if it is required to disclose such information elsewhere.

D. Incremental and Aggregate Burden and Cost Estimates for the Final Amendments

Below we estimate the incremental and aggregate increase in paperwork burden as a result of the final amendments. These estimates represent the average burden for all respondents, both large and small. In deriving our estimates, we recognize that the burdens will likely vary among individual respondents and from year to year based on a number of factors, including the nature of their business.

The burden estimates were calculated by multiplying the estimated number of responses by the estimated average amount of time it would take a registrant to prepare and review disclosure required under the final amendments. For purposes of the PRA, the burden is to be allocated between internal burden hours and outside professional costs. PRA Table 2 below sets forth the percentage estimates we typically use for the burden allocation for each collection of information. We also estimate that the average cost of retaining outside professionals is $600 per hour.

PRA Table 2: Standard Estimated Burden Allocation for Specified Collections of Information

Collection of InformationInternalOutside Professionals
Form 10-K, Form 6-K, and Form 8-K75%25%
Form 20-F25%75%

PRA Table 3 below illustrates the incremental change to the total annual compliance burden of affected collections of information, in hours and in costs, as a result of the final amendments.

PRA Table 3. Calculation of the Incremental Change in Burden Estimates of Current Responses Resulting from the Final Amendments

Collection of
Information
Number of
Estimated
Affected
Responses
Burden Hour
Increase per
Response
Change in
Burden Hours
Change in
Company
Hours
Change in
Professional
Hours
Change in
Professional
Costs
(A)*(B)(C)
= (A) x (B)**
(D)
= (C) x 0.75
or .25
(E)
= (C) x 0.25 or
.75
(F)
= (E) x $600
8-K20091,8001,350450$270,000
6-K20918013545$27,000
10-K8,2921082,92062,19020,730$12,438,000
20-F729107,2901,822.505,467.50$3,280,500

* The number of estimated affected responses is based on the number of responses in the Commission’s current OMB PRA filing inventory. The OMB PRA filing inventory represents a three-year average.

** The estimated changes in Columns (C), (D), and (E) are rounded to the nearest whole number.



The following PRA Table 4 summarizes the requested paperwork burden, including the estimated total reporting burdens and costs, under the final amendments.

PRA Table 4. Requested Paperwork Burden Under the Final Amendments

Current Burden

FormCurrent Annual Responses (A)Current Burden Hours (B)Current Cost Burden (C)
Form 8-K118,387818,158$108,674,430
Form 6-K34,794227,031$30,270,780
Form 10-K8,29213,988,770$1,835,588,919
Form 20-F729478,983$576,490,625

Program Change

FormChange in Number of Affected Responses (D)Change in Company Hours (E)†Change in Professional Costs (F)‡
Form 8-K2001,350$270,000
Form 6-K20135$27,000
Form 10-K62,190$12,438,000
Form 20-F1,822.50$3,280,500

Revised Burden

FormAnnual Responses (G) = (A)+(D)Burden Hours (H) = (B) + (E)Cost Burden (I) = (C) +(F)
Form 8-K118,587819,508$108,944,430
Form 6-K34,814227,166$30,297,780
Form 10-K8,29214,050,960$1,848,026,919
Form 20-F729480,805.50$579,771,125

V. FINAL REGULATORY FLEXIBILITY ANALYSIS

The Regulatory Flexibility Act (“RFA”) requires the Commission, in promulgating rules under Section 553 of the Administrative Procedure Act, to consider the impact of those rules on small entities. We have prepared this Final Regulatory Flexibility Analysis (“FRFA”) in accordance with Section 604 of the RFA. An Initial Regulatory Flexibility Analysis (“IRFA”) was prepared in accordance with the RFA and was included in the Proposing Release.

A. Need for, and Objectives of, the Final Amendments

The purpose of the final amendments is to ensure investors and other market participants receive timely, decision-useful information about registrants’ material cybersecurity incidents, and periodic information on registrants’ approaches to cybersecurity risk management, strategy, and governance that is standardized and comparable across registrants. The need for, and objectives of, the final rules are described in Sections I and II above. We discuss the economic impact and potential alternatives to the amendments in Section IV, and the estimated compliance costs and burdens of the amendments under the PRA in Section V.

B. Significant Issues Raised by Public Comments

In the Proposing Release, the Commission requested comment on any aspect of the IRFA, and particularly on the number of small entities that would be affected by the proposed amendments, the existence or nature of the potential impact of the proposed amendments on small entities discussed in the analysis, how the proposed amendments could further lower the burden on small entities, and how to quantify the impact of the proposed amendments.

We received one comment letter on the IRFA, from the U.S. Small Business Administration’s Office of Advocacy (“Advocacy”). Advocacy’s letter expressed concern that “the IRFA does not adequately describe the regulated small entities and potential impacts on those entities.” In the Proposing Release, the Commission estimated that the proposed amendments would apply to 660 issuers and 9 business development companies that may be considered small entities. Advocacy’s comment letter stated that this estimate did “not provide additional information, such as the North American Industry Classification System (“NAICS”) classifications of the affected entities” and did not “break down the affected entities into smaller size groups (e.g., based on total assets).” It also stated that the IRFA did not “adequately analyze the relative impact of costs to small entities.” In this vein, it suggested that emerging growth companies (“EGCs”) may face particular challenges complying with the proposed rules. In particular, Advocacy’s comment letter stated that “[e]merging growth companies may have little or no revenue to afford the additional cost burden of the proposed rules and may not have access to the cybersecurity expertise necessary to comply with the new disclosure requirements.”

The comment letter from Advocacy also addressed the discussion of alternatives within the IRFA and the Commission’s explanation of why it did not ultimately propose such alternatives. Advocacy stated that “[t]he RFA requires that an IRFA provide significant, feasible alternatives that accomplish an agency’s objectives,” and stated that the IRFA did not satisfy this requirement because it listed “broad categories of potential alternatives to the proposed rules but did not analyze any specific alternative that was considered by the SEC,” and because it did not “contain a description of significant alternatives which accomplish the stated SEC objectives and which minimize the significant economic impact of the proposal on small entities.”

1. Estimate of Affected Small Entities and Impact to Those Entities

With respect to the adequacy of the Proposing Release’s estimate of affected small entities, the RFA requires “a description of and, where feasible, an estimate of the number of small entities to which the proposed rule will apply.” Advocacy’s published guidance recommends agencies use NAICS classifications to help in “identifying the industry, governmental and nonprofit sectors they intend to regulate.” Here, given that the rulemaking applies to and impacts all public company registrants, regardless of industry or sector, we do not believe that further breakout of such registrants by industry classification is necessary or would otherwise be helpful to such entities understanding the impact of the proposed or final rules. This is not a case in which small entities in certain industries and sectors would be affected more than others, as cybersecurity risks exist across industries. For the same reasons we are not breaking down the affected entities into smaller size groups (e.g., based on total assets) as recommended by Advocacy. Given the nature of the final rules, we believe that our estimate of the number of small entities to which the final rules will apply adequately describes and estimates the small entities that will be affected.

With respect to Advocacy’s suggestion that the proposed rule may be “particularly problematic” for EGCs, we have discussed in Section IV.C.2 above the anticipated costs of the final rules, including their impact on EGCs. We also note that the category of EGC is not the same as the category of “small entity” for purposes of the RFA, and indeed EGC status is not a reliable indicator of whether a registrant is a small entity. While EGC status does include a revenue component, it importantly considers whether the issuer is seasoned, meaning, whether it is a new registrant (rather than a registrant with a longer public reporting history). Accordingly, while many EGCs are small entities, there are many that are not. Likewise, many small entities are not EGCs. For purposes of the FRFA, our focus is on the impact on small entities, regardless of whether or not they are EGCs.

We disagree with the statement in the Advocacy comment letter that “SEC expects that the costs associated with the proposed amendments to be similar for large and small entities.” The Commission explained in the IRFA that the proposed amendments would apply to small entities to the same extent as other entities, irrespective of size, and that therefore, the Commission expected that “the nature of any benefits and costs associated with the proposed amendments to be similar for large and small entities” (emphasis added). The analysis with respect to the nature of the costs (and benefits) of the proposed rules detailed in the Economic Analysis of the Proposing Release was referenced in the IRFA to help small entities understand such impacts, not to imply that small entities face the same degree of costs as large entities. Indeed, the Commission went on to state in both the IRFA and the Economic Analysis of the Proposing Release that, while it was unable to project the economic impacts on small entities with precision, it recognized that “the costs of the proposed amendments borne by the affected entities could have a proportionally greater effect on small entities, as they may be less able to bear such costs relative to larger entities.” Additionally, in Section IV, above, we discuss the economic effects, including costs, of the final amendments across all entities. We recognize that to the extent the costs are generally uniform across all entities, they would have a relatively greater burden on smaller entities. That said, as discussed both above and below, to help mitigate that relatively greater burden and to respond to comment letters including the letter from Advocacy, we have extended the compliance date for smaller reporting companies so as to provide additional transition time and allow them to benefit from the experience of larger companies. Accordingly, we believe that both this FRFA and our prior IRFA adequately describe and analyze the relative impact of costs to small entities.

2. Consideration of Alternatives

The IRFA’s discussion of significant alternatives, and our discussion of alternatives below, satisfy the RFA. The relevant RFA requirement provides that an IRFA “shall also contain a description of any significant alternatives to the proposed rule which accomplish the stated objectives of applicable statutes and which minimize any significant economic impact of the proposed rule on small entities.” In the Proposing Release, the Commission discussed each of the types of significant alternatives noted in Section 603 of the RFA and concluded that none of these alternatives would accomplish the stated objectives of the rulemaking while minimizing any significant impact on small entities. In addition, Section III.E of the Proposing Release discussed reasonable alternatives to the proposed rules and their economic impacts. Similarly, in addition to the discussion in Section VI.E below, in Section IV.E of this release we also discuss reasonable alternatives of the final rules and their economic impacts.

While not commenting on the alternatives raised in the IRFA specifically, two commenters stated that the final rules should exempt smaller businesses. One of these commenters stated that small companies in the biotechnology industry “do not have the capacity, nor the business need, to have institutional structures related to the management, planning, oversight, and maintenance of cybersecurity related systems and suppliers. These companies should not have to hire extra employees specifically for the purposes of implementing cybersecurity related programs.” The other commenter noted that, with respect to the proposed requirement to require disclosure about the cybersecurity expertise of board members, small companies “have limited resources to begin with, and may find it more difficult than large companies to identify board members with requisite cyber expertise given that there already is a lack of talent in this area.”

With respect to the first of these commenters, we note that neither the proposed nor the final rules require any company to “implement new management structures” or otherwise adopt or change “institutional structures related to the management, planning, oversight, and maintenance of cybersecurity related systems and suppliers.” The final rules instead call for disclosure of a registrant’s processes, if any, for assessing, identifying, and managing material cybersecurity risks. To the extent that a registrant does not have such processes, the final rules do not impose any additional costs. With respect to the second of these commenters, we note that, consistent with commenter feedback and for the reasons discussed above, we have not adopted the proposed requirement related to disclosure of board cybersecurity expertise.

Finally, we note that many commenters explicitly opposed exempting smaller businesses from the proposed rules, in part because they may face equal or greater cybersecurity risk than larger companies, or because investors’ relative share in a smaller company may be higher, such that small companies’ cybersecurity risk “may actually embody the most pressing cybersecurity risk to an investor.” We agree with these analyses, and accordingly are not exempting small entities from the final rules. However, as discussed above, in response to concerns about the impact of the rules on smaller companies and in order to provide smaller reporting companies with additional time to prepare to comply with the incident disclosure requirements, we are providing such registrants with an additional 180 days from the non-smaller reporting company compliance date before they must comply with the new Form 8-K requirement.

C. Small Entities Subject to the Final Amendments

The final amendments would apply to registrants that are small entities. The RFA defines “small entity” to mean “small business,” “small organization,” or “small governmental jurisdiction.” For purposes of the RFA, under our rules, a registrant, other than an investment company, is a “small business” or “small organization” if it had total assets of $5 million or less on the last day of its most recent fiscal year and is engaged or proposing to engage in an offering of securities that does not exceed $5 million. An investment company, including a business development company, is considered to be a “small business” if it, together with other investment companies in the same group of related investment companies, has net assets of $50 million or less as of the end of its most recent fiscal year. We estimate that, as of December 31, 2022, there were approximately 800 issuers and 10 business development companies that may be considered small entities that would be subject to the proposed amendments.

D. Projected Reporting, Recordkeeping, and other Compliance Requirements

Per the final rules, registrants will be required to report material cybersecurity incidents on Form 8-K and Form 6-K for FPIs, and will be required to describe in their annual reports on Forms 10-K and 20-F certain aspects of their cybersecurity risk management, strategy, and governance, if any. The final amendments are described in more detail in Section II above. These requirements generally will apply to small entities to the same extent as other entities, irrespective of size or industry classification, although we are adopting a later compliance date for smaller reporting companies in response to concerns raised by commenters. We continue to expect that the nature of any benefits and costs associated with the amendments to be similar for large and small entities, and so we refer to the discussion of the amendments’ economic effects on all affected parties, including small entities, in Section IV above. Also consistent with the discussion in Sections II and IV above, we acknowledge that, in particular to the extent that a smaller entity would be required to provide disclosure under the final rules, it may face costs that are proportionally greater as they may be less able to bear such costs relative to larger entities. However, as discussed in in Section IV, we anticipate that the economic benefits and costs likely could vary widely among small entities based on a number of factors, such as the nature and conduct of their businesses, including whether the company actively manages material cybersecurity risks, which makes it difficult to project the economic impact on small entities with precision. To the extent that the disclosure requirements have a greater effect on small registrants relative to large registrants, they could result in adverse effects on competition. The fixed component of the legal costs of preparing the disclosure would be a primary contributing factor. Compliance with certain provisions of the final amendments may require the use of professional skills, including legal, accounting, and technical skills.

E. Agency Action to Minimize Effect on Small Entities

The RFA directs us to consider alternatives that would accomplish our stated objectives, while minimizing any significant adverse impact on small entities. Accordingly, we considered the following alternatives:

    • Exempting small entities from all or part of the requirements;
    • Establishing different compliance or reporting requirements that take into account the resources available to small entities;
    • Using performance rather than design standards; and
    • Clarifying, consolidating, or simplifying compliance and reporting requirements under the rules for small entities.

The rules are intended to better inform investors about cybersecurity incidents and, if any, the cybersecurity risk management, strategy, and governance of registrants of all types and sizes that are subject to the Exchange Act reporting requirements. We explain above in Sections II and IV that current requirements and guidance are not yielding uniform, comparable disclosure sufficient to meet investors’ needs. The disclosure that does exist is scattered in various parts of registrants’ filings, making it difficult for investors to locate, analyze, and compare across registrants. Staff has also observed that smaller reporting companies generally provide less cybersecurity disclosure as compared to larger registrants, and commenters agreed that there is a need for cybersecurity disclosure from small companies.

Given the current disclosure landscape, exempting small entities or otherwise clarifying, consolidating, or simplifying compliance and reporting requirements under the rules for small entities would frustrate the rulemaking’s goal of providing investors with more uniform and timely disclosure about material cybersecurity incidents and about cybersecurity risk management, strategy, and governance practices across all registrants. That said, as discussed in Section II above, we have consolidated and simplified the disclosure requirements for all entities, which should ease small entities’ compliance as well. Further, as noted above, smaller companies may face equal or greater cybersecurity risk than larger companies, making the disclosures important for investors in these companies.

On the other hand, we believe the rulemaking’s goals can be achieved by providing smaller reporting companies with additional time to come into compliance. Therefore, we are delaying smaller reporting companies’ required compliance date with the Form 8-K incident disclosure requirement by an additional 180 days from the non-smaller reporting company compliance date. This delay will benefit smaller reporting companies both by giving them extra time to establish disclosure controls and procedures and by allowing them to observe and learn from best practices as they develop among larger registrants.

Similarly, the final rules incorporate a combination of performance and design standards
with respect to all subject entities, including small entities, in order to balance the objectives and compliance burdens of the rules. While the final rules do use design standards to promote uniform compliance requirements for all registrants and to address the concerns underlying the amendments, which apply to entities of all size, they also incorporate elements of performance standards to give registrants sufficient flexibility to craft meaningful disclosure that is tailored to their particular facts and circumstances. For example, the final rules require a registrant to describe its “processes, if any, for assessing, identifying, and managing material risks from cybersecurity threats in sufficient detail for a reasonable investor to understand those processes.” The rule also provides a non-exclusive list of disclosure items that a registrant should include in providing responsive disclosure to this performance standard; this design element provides registrants with additional guidance with respect to the type of disclosure topics that could be covered and promotes consistency.

STATUTORY AUTHORITY

The amendments contained in this release are being adopted under the authority set forth
in Sections 7 and 19(a) of the Securities Act and Sections 3(b), 12, 13, 15, and 23(a) of the
Exchange Act.

List of Subjects in 17 CFR Parts 229, 232, 239, 240, and 249

Reporting and record keeping requirements, Securities.

TEXT OF AMENDMENTS

For the reasons set forth in the preamble, the Commission amends title 17, chapter II of the
Code of Federal Regulations as follows:

PART 229—STANDARD INSTRUCTIONS FOR FILING FORMS UNDER
SECURITIES ACT OF 1933, SECURITIES EXCHANGE ACT OF 1934 AND ENERGY
POLICY AND CONSERVATION ACT OF 1975—REGULATION S-K

1. The authority citation for part 229 continues to read as follows:

Authority: 15 U.S.C. 77e, 77f, 77g, 77h, 77j, 77k, 77s, 77z-2, 77z-3, 77aa(25), 77aa(26),
77ddd, 77eee, 77ggg, 77hhh, 77iii, 77jjj, 77nnn, 77sss, 78c, 78i, 78j, 78j-3, 78l, 78m, 78n,78n-1, 78o, 78u-5, 78w, 78ll, 78mm, 80a-8, 80a-9, 80a-20, 80a-29, 80a-30, 80a-31(c), 80a-37, 80a38(a), 80a-39, 80b-11 and 7201 et seq.; 18 U.S.C. 1350; sec. 953(b), Pub. L. 111-203, 124 Stat. 1904 (2010); and sec. 102(c), Pub. L. 112-106, 126 Stat. 310 (2012).

2. Add §229.106 to read as follows:

§229.106 (Item 106) Cybersecurity.

(a) Definitions. For purposes of this section:

Cybersecurity incident means an unauthorized occurrence, or a series of related unauthorized occurrences, on or conducted through a registrant’s information systems that jeopardizes the confidentiality, integrity, or availability of a registrant’s information systems or any information residing therein.

Cybersecurity threat means any potential unauthorized occurrence on or conducted through a registrant’s information systems that may result in adverse effects on the confidentiality, integrity, or availability of a registrant’s information systems or any information residing therein.

Information systems means electronic information resources, owned or used by the registrant, including physical or virtual infrastructure controlled by such information resources, or components thereof, organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of the registrant’s information to maintain or support the registrant’s operations.

(b) Risk management and strategy.

(1) Describe the registrant’s processes, if any, for assessing, identifying, and managing material risks from cybersecurity threats in sufficient detail for a reasonable investor to understand those processes. In providing such disclosure, a registrant should address, as applicable, the following non-exclusive list of disclosure items:

(i) Whether and how any such processes have been integrated into the registrant’s overall risk management system or processes;

(ii) Whether the registrant engages assessors, consultants, auditors, or other third parties in connection with any such processes; and

(iii) Whether the registrant has processes to oversee and identify such risks from cybersecurity threats associated with its use of any third-party service provider.

(2) Describe whether any risks from cybersecurity threats, including as a result of any previous cybersecurity incidents, have materially affected or are reasonably likely to materially affect the registrant, including its business strategy, results of operations, or financial condition and if so, how.

(c) Governance.

(1) Describe the board of directors’ oversight of risks from cybersecurity threats. If applicable, identify any board committee or subcommittee responsible for the oversight of risks from cybersecurity threats and describe the processes by which the board or such committee is informed about such risks.

(2) Describe management’s role in assessing and managing the registrant’s material risks from cybersecurity threats. In providing such disclosure, a registrant should address, as applicable, the following non-exclusive list of disclosure items:

(i) Whether and which management positions or committees are responsible for assessing and managing such risks, and the relevant expertise of such persons or members in such detail as necessary to fully describe the nature of the expertise;

(ii) The processes by which such persons or committees are informed about and monitor the prevention, detection, mitigation, and remediation of cybersecurity incidents; and

(iii) Whether such persons or committees report information about such risks to the board of directors or a committee or subcommittee of the board of directors.

Instruction 1 to Item 106(c): In the case of a foreign private issuer with a two-tier board of directors, for purposes of paragraph (c) of this section, the term “board of directors” means the supervisory or non-management board. In the case of a foreign private issuer meeting the requirements of §240.10A-3(c)(3) of this chapter, for purposes of paragraph (c) of this Item, the term “board of directors” means the issuer’s board of auditors (or similar body) or statutory auditors, as applicable.

Instruction 2 to Item 106(c): Relevant expertise of management in Item 106(c)(2)(i) may include, for example: Prior work experience in cybersecurity; any relevant degrees or certifications; any knowledge, skills, or other background in cybersecurity.

(d) Structured Data Requirement.

Provide the information required by this Item in an Interactive Data File in accordance with Rule 405 of Regulation S-T and the EDGAR Filer Manual.

3. Amend §229.601 by revising paragraph (b)(101)(i)(C)(1) as follows:
§ 229.601 (Item 601) Exhibits

* * * * *
(b) * * *
(101) * * *
(i) * * *
(C) * * *
(1) Only when:

(i) The Form 8-K contains audited annual financial statements that are a revised version of financial statements that previously were filed with the Commission and that have been revised pursuant to applicable accounting standards to reflect the effects of certain subsequent events, including a discontinued operation, a change in reportable segments or a change in accounting principle. In such case, the Interactive Data File will be required only as to such revised financial statements regardless of whether the Form 8-K contains other financial statements; or

(ii) The Form 8-K includes disclosure required to be provided in an Interactive Data File
pursuant to Item 1.05(b) of Form 8-K; and

* * * * *

PART 232—REGULATION S-T—GENERAL RULES AND REGULATIONS FOR
ELECTRONIC FILINGS

4. The general authority citation for part 232 continues to read as follows:

Authority: 15 U.S.C. 77c, 77f, 77g, 77h, 77j, 77s(a), 77z-3, 77sss(a), 78c(b), 78l, 78m,
78n, 78o(d), 78w(a), 78ll, 80a-6(c), 80a-8, 80a-29, 80a-30, 80a-37, 80b-4, 80b-6a, 80b-10, 80b11, 7201 et seq.; and 18 U.S.C. 1350, unless otherwise noted.

* * * * *

5. Amend §232.405 by adding paragraph (b)(4)(v) to read as follows:

§232.405 Interactive Data File submissions.

* * * * *
(b) * * *
(4) * * *

(v) Any disclosure provided in response to: §229.106 of this chapter (Item 106 of Regulation S-K); Item 1.05 of §249.308 of this chapter (Item 1.05 of Form 8-K); and Item 16K of § 249.220f of this chapter (Item 16K of Form 20-F).

PART 239—FORMS PRESCRIBED UNDER THE SECURITIES ACT OF 1933

6. The general authority citation for part 239 continues to read as follows:

Authority: 15 U.S.C. 77c, 77f, 77g, 77h, 77j, 77s, 77z-2, 77z-3, 77sss, 78c, 78l, 78m,78n,
78o(d), 78o-7 note, 78u-5, 78w(a), 78ll, 78mm, 80a-2(a), 80a-3, 80a-8, 80a-9, 80a-10, 80a-13, 80a24, 80a-26, 80a-29, 80a-30, 80a-37, and sec. 1003 and sec. 84001, Pub. L. 114.94, 129 Stat. 1321,
unless otherwise noted.

7. Amend § 239.13 by revising paragraph (a)(3)(ii) to read as follows:

§239.13 Form S-3, for registration under the Securities Act of 1933 of securities of certain
issuers offered pursuant to certain types of transactions.

(a) * * *
(3) * * *

(ii) Has filed in a timely manner all reports required to be filed during the twelve calendar months and any portion of a month immediately preceding the filing of the registration statement, other than a report that is required solely pursuant to Item 1.01, 1.02, 1.05, 2.03, 2.04, 2.05, 2.06, 4.02(a), 6.01, 6.03, or 6.05 of Form 8-K (§ 249.308 of this chapter). If the registrant has used (during the twelve calendar months and any portion of a month immediately preceding the filing of the registration statement) § 240.12b-25(b) of this chapter with respect to a report or a portion of a report, that report or portion thereof has actually been filed within the time period prescribed by that section; and

8. Amend Form S-3 (referenced in § 239.13) by adding General Instruction I.A.3(b).

Note: Form S-3 is attached as Appendix A to this document. Form S-3 will not appear in the Code of Federal Regulations.

PART 240—GENERAL RULES AND REGULATIONS, SECURITIES EXCHANGE
ACT OF 1934

9. The authority citation for part 240 continues to read, in part, as follows:

Authority: 15 U.S.C. 77c, 77d, 77g, 77j, 77s, 77z-2, 77z-3, 77eee, 77ggg, 77nnn, 77sss, 77ttt, 78c, 78c-3, 78c-5, 78d, 78e, 78f, 78g, 78i, 78j, 78j-1, 78k, 78k-1, 78l, 78m, 78n, 78n-1, 78o, 78o-4, 78o-10, 78p, 78q, 78q-1, 78s, 78u-5, 78w, 78x, 78dd, 78ll, 78mm, 80a-20, 80a-23, 80a-29, 80a-37, 80b-3, 80b-4, 80b-11, 7201 et seq., and 8302; 7 U.S.C. 2(c)(2)(E); 12 U.S.C.
5221(e)(3); 18 U.S.C. 1350; Pub. L. 111-203, 939A, 124 Stat. 1376 (2010); and Pub. L. 112-106, sec. 503 and 602, 126 Stat. 326 (2012), unless otherwise noted.

Section 240.15d-11 is also issued under secs. 3(a) and 306(a), Pub. L. 107-204, 116 Stat.
745.

10. Amend § 240.13a-11 by revising paragraph (c) to read as follows:

§240.13a-11 Current reports on Form 8-K (§249.308 of this chapter).

(c) No failure to file a report on Form 8-K that is required solely pursuant to Item 1.01, 1.02, 1.05, 2.03, 2.04, 2.05, 2.06, 4.02(a), 5.02(e), or 6.03 of Form 8-K shall be deemed to be a violation of 15 U.S.C. 78j(b) and §240.10b-5.

11. Amend § 240.15d-11 by revising paragraph (c) to read as follows

§240.15d-11 Current reports on Form 8-K (§249.308 of this chapter).

(c) No failure to file a report on Form 8-K that is required solely pursuant to Item 1.01, 1.02, 1.05, 2.03, 2.04, 2.05, 2.06, 4.02(a), 5.02(e), or 6.03 of Form 8-K shall be deemed to be a violation of 15 U.S.C. 78j(b) and §240.10b-5.

PART 249—FORMS, SECURITIES EXCHANGE ACT OF 1934

12. The authority citation for part 249 continues to read, in part, as follows:

Authority: 15 U.S.C. 78a et seq. and 7201 et seq.; 12 U.S.C. 5461 et seq.; 18 U.S.C. 1350; Sec. 953(b), Pub. L. 111-203, 124 Stat. 1904; Sec. 102(a)(3), Pub. L. 112-106, 126 Stat. 309 (2012); Sec. 107, Pub. L. 112-106, 126 Stat. 313 (2012), Sec. 72001 Pub. L. 114-94, 129 Stat. 1312 (2015), and secs. 2 and 3 Pub. L. 116-222, 134 Stat. 1063 (2020), unless otherwise noted.

Section 249.220f is also issued under secs. 3(a), 202, 208, 302, 306(a), 401(a), 401(b), 406 and 407, Pub. L. 107-204, 116 Stat. 745, and secs. 2 and 3, Pub. L. 116-222, 134 Stat. 1063.

Section 249.308 is also issued under 15 U.S.C. 80a-29 and 80a-37.

Section 249.310 is also issued under secs. 3(a), 202, 208, 302, 406 and 407, Pub. L. 107- 204, 116 Stat. 745.

13. Revise Form 20-F (referenced in § 249.220f) by adding Item 16K.

Note: Form 20-F is attached as Appendix B to this document. Form 20-F will not appear in the Code of Federal Regulations.

14. Amend Form 6-K (referenced in § 249.306) by adding, in the second paragraph of General Instruction B, the phrase “material cybersecurity incident;” before the phrase “and any other information which the registrant deems of material importance to security holders.”

15. Revise Form 8-K (referenced in §249.308) by:

a. Revising General Instruction B.1.;

b. Revising General Instruction G.1.; and

c. Adding Item 1.05.

Note: Form 8-K is attached as Appendix C to this document. Form 8-K will not appear in the Code of Federal Regulations.

16. Revise Form 10-K (referenced in § 249.310) by:

a. Revising General Instruction J(1)(b); and

b. Adding Item 1C to Part I.

Note: Form 10-K is attached as Appendix D to this document. Form 10-K will not appear in the Code of Federal Regulations.

By the Commission.

Dated: July 26, 2023

Vanessa A. Countryman,

Secretary.

Note: The following appendices will not appear in the Code of Federal Regulations.

Appendix A—Form S-3

FORM S-3

INFORMATION TO BE INCLUDED IN THE REPORT

General Instructions

I. Eligibility Requirements for Use of Form S-3

A. Registrant Requirements.

3. * * *

(b) has filed in a timely manner all reports required to be filed during the twelve calendar months and any portion of a month immediately preceding the filing of the registration statement, other than a report that is required solely pursuant to Item 1.01, 1.02, 1.04, 1.05, 2.03, 2.04, 2.05, 2.06, 4.02(a) or 5.02(e) of Form 8-K (§249.308 of this chapter). If the registrant has used (during the twelve calendar months and any portion of a month immediately preceding the filing of the registration statement) Rule 12b-25(b) (§240.12b-25(b) of this chapter) under the Exchange Act with respect to a report or a portion of a report, that report or portion thereof has actually been filed within the time period prescribed by that rule.

Appendix B—Form 20-F


FORM 20-F


PART II

Item 16K. Cybersecurity.


(a) Definitions. For purposes of this section:


(1) Cybersecurity incident means an unauthorized occurrence, or a series of related unauthorized occurrences, on or conducted through a registrant’s information systems that jeopardizes the confidentiality, integrity, or availability of a registrant’s information systems or any information residing therein.

(2) Cybersecurity threat means any potential unauthorized occurrence on or conducted through a registrant’s information systems that may result in adverse effects on the confidentiality, integrity, or availability of a registrant’s information systems or any information residing therein.

(3) Information systems means electronic information resources, owned or used by the registrant, including physical or virtual infrastructure controlled by such information resources, or components thereof, organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of the registrant’s information to maintain or support the registrant’s operations.


(b) Risk management and strategy.


(1) Describe the registrant’s processes, if any, for assessing, identifying, and managing material risks from cybersecurity threats in sufficient detail for a reasonable investor to understand those processes. In providing such disclosure, a registrant should address, as applicable, the following non-exclusive list of disclosure items:

(i) Whether and how any such processes have been integrated into the registrant’s overall risk management system or processes;

(ii) Whether the registrant engages assessors, consultants, auditors, or other third parties in connection with any such processes; and

(iii) Whether the registrant has processes to oversee and identify such risks from cybersecurity threats associated with its use of any third-party service provider.

(2) Describe whether any risks from cybersecurity threats, including as a result of any previous cybersecurity incidents, have materially affected or are reasonably likely to materially affect the registrant, including its business strategy, results of operations, or financial condition and if so, how.


(c) Governance.


(1) Describe the board of directors’ oversight of risks from cybersecurity threats. If applicable, identify any board committee or subcommittee responsible for the oversight of risks from cybersecurity threats and describe the processes by which the board or such committee is informed about such risks.

(2) Describe management’s role in assessing and managing the registrant’s material risks from cybersecurity threats. In providing such disclosure, a registrant should address, as applicable, the following non-exclusive list of disclosure items:

(i) Whether and which management positions or committees are responsible for assessing and managing such risks, and the relevant expertise of such persons or members in such detail as necessary to fully describe the nature of the expertise;

(ii) The processes by which such persons or committees are informed about and monitor the prevention, detection, mitigation, and remediation of cybersecurity incidents; and

(iii) Whether such persons or committees report information about such risks to the board of directors or a committee or subcommittee of the board of directors.


Instructions to Item 16K(c).


1. In the case of a foreign private issuer with a two-tier board of directors, for purposes of paragraph (c) of this Item, the term “board of directors” means the supervisory or non-management board. In the case of a foreign private issuer meeting the requirements of §240.10A-3(c)(3) of this chapter, for purposes of paragraph (c) of this Item, the term “board of directors” means the issuer’s board of auditors (or similar body) or statutory auditors, as
applicable.

2. Relevant expertise of management in paragraph (c)(2)(i) of this Item may include, for
example: Prior work experience in cybersecurity; any relevant degrees or certifications; any
knowledge, skills, or other background in cybersecurity.


(d) Structured Data Requirement.

Provide the information required by this Item in an Interactive Data File in accordance with Rule 405 of Regulation S-T and the EDGAR Filer Manual.


Instruction to Item 16K. Item 16K applies only to annual reports, and does not apply to registration statements on Form 20-F.

Appendix C—Form 8-K

FORM 8-K


GENERAL INSTRUCTIONS

* * * * *


B. Events to be Reported and Time for Filing of Reports.

1. A report on this form is required to be filed or furnished, as applicable, upon the occurrence of any one or more of the events specified in the items in Sections 1 through 6 and 9 of this form. Unless otherwise specified, a report is to be filed or furnished within four business days after occurrence of the event. If the event occurs on a Saturday, Sunday or holiday on which the Commission is not open for business, then the four business day period shall begin to run on, and include, the first business day thereafter. A registrant either furnishing a report on this form under Item 7.01 (Regulation FD Disclosure) or electing to file a report on this form under Item 8.01 (Other Events) solely to satisfy its obligations under Regulation FD (17 CFR 243.100 and 243.101) must furnish such report or make such filing, as applicable, in accordance with the requirements of Rule 100(a) of Regulation FD (17 CFR 243.100(a)), including the deadline for furnishing or filing such report. A report pursuant to Item 5.08 is to be filed within four business days after the registrant determines the anticipated meeting date. A report pursuant to Item 1.05 is to be filed within four business days after the registrant determines that it has experienced a material cybersecurity incident.

G. Use of this Form by Asset-Backed Issuers.

1. * * *

(a) Item 1.05, Cybersecurity Incidents;
(b) Item 2.01, Completion of Acquisition or Disposition of Assets;
(c) Item 2.02, Results of Operations and Financial Condition;
(d) Item 2.03, Creation of a Direct Financial Obligation or an Obligation under an Off-Balance

Sheet Arrangement of a Registrant;

(e) Item 2.05, Costs Associated with Exit or Disposal Activities;
(f) Item 2.06, Material Impairments;
(g) Item 3.01, Notice of Delisting or Failure to Satisfy a Continued Listing Rule or Standard;
Transfer of Listing;
(h) Item 3.02, Unregistered Sales of Equity Securities;
(i) Item 4.01, Changes in Registrant’s Certifying Accountant;
(j) Item 4.02, Non-Reliance on Previously Issued Financial Statements or a Related Audit Report or Completed Interim Review;
(k) Item 5.01, Changes in Control of Registrant;
(l) Item 5.02, Departure of Directors or Principal Officers; Election of Directors; Appointment of Principal Officers;
(m) Item 5.04, Temporary Suspension of Trading Under Registrant’s Employee Benefit Plans; and
(n) Item 5.05, Amendments to the Registrant’s Code of Ethics, or Waiver of a Provision of the Code of Ethics.

INFORMATION TO BE INCLUDED IN THE REPORT

Section 1 – Registrant’s Business and Operations

Item 1.05 Material Cybersecurity Incidents.

(a) If the registrant experiences a cybersecurity incident that is determined by the registrant to be material, describe the material aspects of the nature, scope, and timing of the incident, and the material impact or reasonably likely material impact on the registrant, including its financial condition and results of operations.

(b) A registrant shall provide the information required by this Item in an Interactive Data File in accordance with Rule 405 of Regulation S-T and the EDGAR Filer Manual.

(c) Notwithstanding General Instruction B.1. to Form 8-K, if the United States Attorney General determines that disclosure required by paragraph (a) of this Item 1.05 poses a substantial risk to national security or public safety, and notifies the Commission of such determination in writing, the registrant may delay providing the disclosure required by this Item 1.05 for a time period specified by the Attorney General, up to 30 days following the date when the disclosure required by this Item 1.05 was otherwise required to be provided. Disclosure may be delayed for an additional period of up to 30 days if the Attorney General determines that disclosure continues to pose a substantial risk to national security or public safety and notifies the Commission of such determination in writing. In extraordinary circumstances, disclosure may be delayed for a final additional period of up to 60 days if the Attorney General determines that disclosure continues to pose a substantial risk to national security and notifies the Commission of such determination in writing. Beyond the final 60-day delay under this paragraph, if the Attorney General indicates that further delay is necessary, the Commission will consider additional requests for delay and may grant such relief through Commission exemptive order.

(d) Notwithstanding General Instruction B.1. to Form 8-K, if a registrant that is subject to 47 CFR 64.2011 is required to delay disclosing a data breach pursuant to such rule, it may delay providing the disclosure required by this Item 1.05 for such period that is applicable under 47 CFR 64.2011(b)(1) and in no event for more than seven business days after notification required under such provision has been made, so long as the registrant notifies the Commission in correspondence submitted to the EDGAR system no later than the date when the disclosure required by this Item 1.05 was otherwise required to be provided.

Instructions to Item 1.05.

1. A registrant’s materiality determination regarding a cybersecurity incident must be made without unreasonable delay after discovery of the incident.

2. To the extent that the information called for in Item 1.05(a) is not determined or is unavailable at the time of the required filing, the registrant shall include a statement to this effect in the filing and then must file an amendment to its Form 8-K filing under this Item 1.05 containing such information within four business days after the registrant, without unreasonable delay, determines such information or within four business days after such information becomes available.

3. The definition of the term “cybersecurity incident” in §229.106(a) [Item 106(a) of Regulation S-K] applies to this Item.

4. A registrant need not disclose specific or technical information about its planned response to the incident or its cybersecurity systems, related networks and devices, or potential system vulnerabilities in such detail as would impede the registrant’s response or remediation of the incident.