+Incident Response Operations
|
Incident Response Operations
Description
Mechanisms exist to implement and govern processes and documentation to facilitate an organization-wide response capability for cybersecurity and data protection-related incidents.
Possible Solutions & Considerations
Micro-Small Business (<10 staff) / BLS Firm Size Classes 1-2
∙ Incident Response Plan (IRP)
Small Business (10-49 staff) / BLS Firm Size Classes 3-4
∙ Incident Response Plan (IRP)
Medium Business (50-249 staff) / BLS Firm Size Classes 5-6
∙ Integrated Incident Response Program (IIRP)
Large Business (250-999 staff) / BLS Firm Size Classes 7-8
∙ Integrated Incident Response Program (IIRP)
Enterprise (> 1,000 staff) / BLS Firm Size Class 9
∙ Integrated Incident Response Program (IIRP)
SCR-CMM
Level 0 Not Performed
Practices are non-existent, based on the inability to demonstrate an implemented and operational capability. A reasonable person would conclude the control is not being performed.
Level 1 Performed Informally
Incident Response (IRO) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include: ▪ Policies, standards & procedures associated with IRO domain capabilities provide limited coverage due to the depth and breadth of the existing documentation. ▪ Incident response-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices. ▪ IT and/or cybersecurity personnel use an informal process to facilitate incident management operations that cover preparation, detection and analysis, containment, eradication and recovery.
Level 2 Planned Tracked
Incident Response (IRO) capabilities are requirements-driven, but are not standardized across the entity (e.g., local/regional level consistency). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with IRO domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with DCH domain capabilities are documented and maintained by process owners. ▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with IRO domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Incident response-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Incident response management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel. ▪ IT and/or cybersecurity personnel operate an incident response capability using a documented and tested Incident Response Plan (IRP) to facilitate incident management operations that cover preparation, detection and analysis, containment, eradication and recovery. ▪ IT and/or cybersecurity personnel facilitate prompt response to suspected or confirmed security incidents, including timely notification to affected stakeholders.
Level 3 Well Defined
Incident Response (IRO) capabilities are standardized across the entity for applicability to People, Processes, Technologies, Data and/or Facilities (PPTDF) to ensure consistency for Technology Assets, Applications, Services and/or Data (TAASD). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with IRO domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function. ▪ Cybersecurity personnel operate an incident response capability using a documented and tested Incident Response Plan (IRP) to facilitate incident management operations that cover preparation, detection and analysis, containment, eradication and recovery. ▪ An incident response team, or similar function, is appropriately staffed and supported to implement and maintain IRO domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of incident response operations (e.g., incident management software). ▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, works with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with IRO domain capabilities to address Minimum Compliance Requirements (MCR) (e.g., applicable statutory, regulatory and/or contractual requirements) and Discretionary Security Requirements (DSR) (e.g., entity-required controls). ▪ An implemented and operational capability exists to implement and govern processes and documentation to facilitate an organization-wide response capability for cybersecurity and data protection-related incidents.
Level 4 Quantitatively Controlled
Utilize SCR-CMM Level 3 criteria definitions: ▪ There are no defined Level 4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to operationalize this control. ▪ While it may be possible to develop “metrics-driven” capabilities for this control, the criteria would be organization-specific to define.
Level 5 Continuously Improving
Utilize SCR-CMM Level 3 or Level 4 (if available) criteria definitions: ▪ There are no defined Level 5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to operationalize this control. ▪ Level 5 capabilities should be considered “world-class” where the control builds on Level 4 capabilities, but are continuously improving through Artificial Intelligence (AI) and/or Machine Learning (ML) technologies. ▪ While it may be possible to develop responsive capabilities for this control through the use of AI and/or ML technologies, the criteria would be organization-specific to define.
1. Ülevaade
1.1 Viited
1.2 Tuvastatud nõuded
1.3 Seotud regulatsioonid
2. Tuvastatud nõuded
3. Seotud regulatsioonid
Regulatsioonid
| Allikas |
Regulatsioon |
|
EULAW
|
Article 9 4
4. As part of the ICT risk management framework referred to in Article 6(1), financial entities shall:
|
(a)
|
develop and document an information security policy defining rules to protect the availability, authenticity, integrity and confidentiality of data, information assets and ICT assets, including those of their customers, where applicable;
|
|
(b)
|
following a risk-based approach, establish a sound network and infrastructure management structure using appropriate techniques, methods and protocols that may include implementing automated mechanisms to isolate affected information assets in the event of cyber-attacks;
|
|
(c)
|
implement policies that limit the physical or logical access to information assets and ICT assets to what is required for legitimate and approved functions and activities only, and establish to that end a set of policies, procedures and controls that address access rights and ensure a sound administration thereof;
|
|
(d)
|
implement policies and protocols for strong authentication mechanisms, based on relevant standards and dedicated control systems, and protection measures of cryptographic keys whereby data is encrypted based on results of approved data classification and ICT risk assessment processes;
|
|
(e)
|
implement documented policies, procedures and controls for ICT change management, including changes to software, hardware, firmware components, systems or security parameters, that are based on a risk assessment approach and are an integral part of the financial entity’s overall change management process, in order to ensure that all changes to ICT systems are recorded, tested, assessed, approved, implemented and verified in a controlled manner;
|
|
(f)
|
have appropriate and comprehensive documented policies for patches and updates.
|
For the purposes of the first subparagraph, point (b), financial entities shall design the network connection infrastructure in a way that allows it to be instantaneously severed or segmented in order to minimise and prevent contagion, especially for interconnected financial processes.
For the purposes of the first subparagraph, point (e), the ICT change management process shall be approved by appropriate lines of management and shall have specific protocols in place.
|
|
EULAW
|
Article 14 1
1. As part of the ICT risk management framework referred to in Article 6(1), financial entities shall have in place crisis communication plans enabling a responsible disclosure of, at least, major ICT-related incidents or vulnerabilities to clients and counterparts as well as to the public, as appropriate.
|
|
EULAW
|
Article 14 2
2. As part of the ICT risk management framework, financial entities shall implement communication policies for internal staff and for external stakeholders. Communication policies for staff shall take into account the need to differentiate between staff involved in ICT risk management, in particular the staff responsible for response and recovery, and staff that needs to be informed.
|
|
EULAW
|
Article 14 3
3. At least one person in the financial entity shall be tasked with implementing the communication strategy for ICT-related incidents and fulfil the public and media function for that purpose.
|
|
EULAW
|
Article 18 1
1. Financial entities shall classify ICT-related incidents and shall determine their impact based on the following criteria:
|
(a)
|
the number and/or relevance of clients or financial counterparts affected and, where applicable, the amount or number of transactions affected by the ICT-related incident, and whether the ICT-related incident has caused reputational impact;
|
|
(b)
|
the duration of the ICT-related incident, including the service downtime;
|
|
(c)
|
the geographical spread with regard to the areas affected by the ICT-related incident, particularly if it affects more than two Member States;
|
|
(d)
|
the data losses that the ICT-related incident entails, in relation to availability, authenticity, integrity or confidentiality of data;
|
|
(e)
|
the criticality of the services affected, including the financial entity’s transactions and operations;
|
|
(f)
|
the economic impact, in particular direct and indirect costs and losses, of the ICT-related incident in both absolute and relative terms.
|
|
|
EULAW
|
Article 18 2
2. Financial entities shall classify cyber threats as significant based on the criticality of the services at risk, including the financial entity’s transactions and operations, number and/or relevance of clients or financial counterparts targeted and the geographical spread of the areas at risk.
|
|
EULAW
|
Artikkel 21 Küberturvalisuse riskijuhtimismeetmed
-
|
|
EULAW
|
Artikkel 23 Teatamiskohustus
-
|
|
EULAW
|
Artikkel 22 IKT intsidentide haldamise põhimõtted
Artikkel 22
IKT intsidentide haldamise põhimõtted
Finantssektori ettevõtjad töötavad anomaalse tegevuse, sealhulgas IKT-võrgu jõudluse probleemide ja IKT intsidentide avastamise mehhanismide osana välja ja dokumenteerivad IKT intsidentide haldamise põhimõtted ning rakendavad neid ning teevad nende kohaselt järgmist:
a)
dokumenteerivad määruse (EL) 2022/2554 artiklis 17 osutatud IKT intsidentide haldamise protsessi;
b)
koostavad loetelu asjakohaste sisefunktsioonide täitjatest ja väliste sidusrühmade esindajatest, kes on otseselt seotud IKT-toimingute turvalisusega, sealhulgas järgmisega:
i)
küberohtude avastamine ja seire,
ii)
anomaalse tegevuse avastamine,
c)
loovad, võtavad kasutusele ja käitavad IKT intsidentide haldamise protsessi toetavaid tehnilisi, korralduslikke ja tegevusmehhanisme, sealhulgas mehhanisme, mis võimaldavad kiiresti avastada anomaalse tegevuse ja käitumise kooskõlas käesoleva määruse artikliga 23;
▼C1
d)
kooskõlas komisjoni delegeeritud määruse (EL) 2024/1772 (
2
) artikli 8 lõikega 2 ja liidu õiguses sätestatud kohaldatavate säilitamisnõuetega säilitavad kõik IKT intsidentidega seotud tõendid, mis on vastavuses mõjutatud ärifunktsioonide, toetavate protsesside ning IKT- ja teabevarade kriitilise tähtsusega, ajavahemiku jooksul, mis ei ole pikem kui on vajalik andmete kogumise eesmärgi saavutamiseks;
▼B
e)
loovad mehhanismid, et analüüsida olulisi või korduvaid IKT intsidente ning nende intsidentide arvu ja esinemisega seotud suundumusi, ning rakendavad neid mehhanisme.
Punkti d kohaldamisel säilitavad finantssektori ettevõtjad nimetatud punktis osutatud tõendeid turvalisel viisil.
|
|
EULAW
|
Artikkel 22 IKT intsidentide haldamise põhimõtted
Artikkel 22
IKT intsidentide haldamise põhimõtted
Finantssektori ettevõtjad töötavad anomaalse tegevuse, sealhulgas IKT-võrgu jõudluse probleemide ja IKT intsidentide avastamise mehhanismide osana välja ja dokumenteerivad IKT intsidentide haldamise põhimõtted ning rakendavad neid ning teevad nende kohaselt järgmist:
a)
dokumenteerivad määruse (EL) 2022/2554 artiklis 17 osutatud IKT intsidentide haldamise protsessi;
b)
koostavad loetelu asjakohaste sisefunktsioonide täitjatest ja väliste sidusrühmade esindajatest, kes on otseselt seotud IKT-toimingute turvalisusega, sealhulgas järgmisega:
i)
küberohtude avastamine ja seire,
ii)
anomaalse tegevuse avastamine,
c)
loovad, võtavad kasutusele ja käitavad IKT intsidentide haldamise protsessi toetavaid tehnilisi, korralduslikke ja tegevusmehhanisme, sealhulgas mehhanisme, mis võimaldavad kiiresti avastada anomaalse tegevuse ja käitumise kooskõlas käesoleva määruse artikliga 23;
▼C1
d)
kooskõlas komisjoni delegeeritud määruse (EL) 2024/1772 (
2
) artikli 8 lõikega 2 ja liidu õiguses sätestatud kohaldatavate säilitamisnõuetega säilitavad kõik IKT intsidentidega seotud tõendid, mis on vastavuses mõjutatud ärifunktsioonide, toetavate protsesside ning IKT- ja teabevarade kriitilise tähtsusega, ajavahemiku jooksul, mis ei ole pikem kui on vajalik andmete kogumise eesmärgi saavutamiseks;
▼B
e)
loovad mehhanismid, et analüüsida olulisi või korduvaid IKT intsidente ning nende intsidentide arvu ja esinemisega seotud suundumusi, ning rakendavad neid mehhanisme.
Punkti d kohaldamisel säilitavad finantssektori ettevõtjad nimetatud punktis osutatud tõendeid turvalisel viisil.
|
|
EULAW
|
Artikkel 9 Kaitse ja ennetus
-
|
|
EULAW
|
Artikkel 14 Kommunikatsioon
-
|
|
EULAW
|
Artikkel 17 IKT intsidentide haldamise protsess
-
|
|
EULAW
|
Artikkel 9 Kaitse ja ennetus
-
|
|
EULAW
|
Artikkel 14 Kommunikatsioon
-
|
|
EULAW
|
Artikkel 17 IKT intsidentide haldamise protsess
-
|
|
EULAW
|
Article 17 1
1. Financial entities shall define, establish and implement an ICT-related incident management process to detect, manage and notify ICT-related incidents.
|
|
EULAW
|
Article 17 2
2. Financial entities shall record all ICT-related incidents and significant cyber threats. Financial entities shall establish appropriate procedures and processes to ensure a consistent and integrated monitoring, handling and follow-up of ICT-related incidents, to ensure that root causes are identified, documented and addressed in order to prevent the occurrence of such incidents.
|
|
EULAW
|
Article 17 3
3. The ICT-related incident management process referred to in paragraph 1 shall:
|
(a)
|
put in place early warning indicators;
|
|
(b)
|
establish procedures to identify, track, log, categorise and classify ICT-related incidents according to their priority and severity and according to the criticality of the services impacted, in accordance with the criteria set out in Article 18(1);
|
|
(c)
|
assign roles and responsibilities that need to be activated for different ICT-related incident types and scenarios;
|
|
(d)
|
set out plans for communication to staff, external stakeholders and media in accordance with Article 14 and for notification to clients, for internal escalation procedures, including ICT-related customer complaints, as well as for the provision of information to financial entities that act as counterparts, as appropriate;
|
|
(e)
|
ensure that at least major ICT-related incidents are reported to relevant senior management and inform the management body of at least major ICT-related incidents, explaining the impact, response and additional controls to be established as a result of such ICT-related incidents;
|
|
(f)
|
establish ICT-related incident response procedures to mitigate impacts and ensure that services become operational and secure in a timely manner.
|
|
|
EULAW
|
Artikkel 95 Operatsiooni- ja turvariskide juhtimine
-
|
Lingitud teemad
- Secure Controls Framework -
"The SCF is the Common Controls Framework™ (CCF), the world's most comprehensive cybersecurity and data privacy metaframework - it is also free to use. The entire concept is building secure, compliant and resilient capabilities in the most efficient and cost-effective manner possible.
The SCF is more than just a unified control catalog, since its included content creates a playbook for Governance, Risk & Compliance (GRC) capabilities. Used globally by organizations of every size, the SCF is a robust and scalable solution for security, compliance and resilience controls. As a comprehensive security framework, the SCF maps 1,400+ controls across 200+ laws, regulations, and industry frameworks so you can implement once and comply everywhere.
Like it or not, cybersecurity is a protracted war on an asymmetric battlefield, where the threats are everywhere and as defenders we have to make the effort to work together to help improve cybersecurity and data privacy practices, since we all suffer when massive data breaches occur or when cyber attacks have physical impacts. Hackers share information on attack methods with other hackers, so why shouldn’t the good guys share information on how to best protect an organization? We decided to take action and make a difference, since we feel it is too important to wait for someone else to fix the problems that exist.
The SCF is made up of volunteers, mainly specialists within the cybersecurity profession, who focus on GRC and the cybersecurity side of data privacy. These are auditors, engineers, architects, incident responders, consultants and other specialists who live and breathe these topics on a daily basis. The end product is "expert-derived content" that makes up the SCF." https://securecontrolsframework.com/
Terms & Conditions
The SCF End User License Agreement (EULA) governs the use of the Secure Controls Framework® (SCF) under the Creative Commons Attribution-No Derivatives 4.0 International Public License.
|