Back

Include losses due to the incident in the incident response report.


CONTROL ID
12724
CONTROL TYPE
Establish/Maintain Documentation
CLASSIFICATION
Preventive

SUPPORTING AND SUPPORTED CONTROLS



This Control directly supports the implied Control(s):
  • Create an incident response report following an incident response., CC ID: 12700

There are no implementation support Controls.


SELECTED AUTHORITY DOCUMENTS COMPLIED WITH



  • Magnitude of the incident including foregone revenue, losses, costs, investments, number of customers affected, implications, consequences to reputation and confidence; and (§ 7.3.12.b.ii., Monetary Authority of Singapore: Technology Risk Management Guidelines)
  • the data losses that the ICT-related incident entails, in relation to availability, authenticity, integrity or confidentiality of data; (Art. 18.1.(d), Regulation (EU) 2022/2554 of the European Parliament and of the Council of 14 December 2022 on digital operational resilience for the financial sector and amending Regulations (EC) No 1060/2009, (EU) No 648/2012, (EU) No 600/2014, (EU) No 909/2014 and (EU) 2016/1011 (Text with EEA relevance))
  • the economic impact, in particular direct and indirect costs and losses, of the ICT-related incident in both absolute and relative terms. (Art. 18.1.(f), Regulation (EU) 2022/2554 of the European Parliament and of the Council of 14 December 2022 on digital operational resilience for the financial sector and amending Regulations (EC) No 1060/2009, (EU) No 648/2012, (EU) No 600/2014, (EU) No 909/2014 and (EU) 2016/1011 (Text with EEA relevance))
  • its effects, and (§ 67(6)(b), UK Data Protection Act 2018 Chapter 12)
  • its effects, and (§ 67(6)(b), UK Data Protection Act 2018 Chapter 12, Revised 06/06/2022)
  • For each significant service disruption, the entity shall disclose the duration of the disruption, the extent of impact, and the root cause, as well as any corrective actions taken to prevent future disruptions. Where material, the entity shall indicate the associated cost incurred, such as remediat… (Note to TC-SI-550a.1 1, Software & IT Services Sustainability Accounting Standard, Version 2018-10)
  • Where relevant, the entity shall indicate costs incurred, such as those due to organizational change, training, or technology expenditures required for remediation, lost revenues, payment of warranties, or cost associated with breach of contract. (Note to TC-TL-550a.1 1.1, Telecommunication Services Sustainability Accounting Standard, Version 2018-10)
  • The entity may discuss estimated amount of potential loss, probability of that loss, and the associated timeframe. These estimates may be based on insurance figures or other third-party or internal assessments of potential loss. (TC-TL-550a.2. 3, Telecommunication Services Sustainability Accounting Standard, Version 2018-10)
  • An analysis of parties that may have experienced a loss, whether monetary or otherwise, due to the SCI event, the number of such parties, and an estimate of the aggregate amount of such loss. (§242.1002(b)(4)(ii)(C), 17 CFR PART 242, Regulations M, SHO, ATS, AC, NMS, and SBSR and Customer Margin Requirements for Security Futures)