+Automated Incident Handling Processes
---+Automated Reporting
---+Automated Tracking, Data Collection & Analysis
---+Dynamic Reconfiguration
---+Automatic Disabling of Technology Assets, Applications and/or Services (TAAS)

Automated Incident Handling Processes

Description

Automated mechanisms exist to support the incident handling process.

Possible Solutions & Considerations

Micro-Small Business (<10 staff) / BLS Firm Size Classes 1-2

∙ Basic incident response plan
∙ Designate incident response contact

Small Business (10-49 staff) / BLS Firm Size Classes 3-4

∙ Documented incident response plan
∙ Incident log
∙ Designated IR team

Medium Business (50-249 staff) / BLS Firm Size Classes 5-6

∙ CimTrak Integrity Suite (https://cimcor.com/cimtrak)

Large Business (250-999 staff) / BLS Firm Size Classes 7-8

∙ CimTrak Integrity Suite (https://cimcor.com/cimtrak)

Enterprise (> 1,000 staff) / BLS Firm Size Class 9

∙ CimTrak Integrity Suite (https://cimcor.com/cimtrak)

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

SCR-CMM Level 1 criteria definitions are not available for this control:
▪ A reasonable person would conclude this control requires a structured process.
▪ At this level of maturity, the "ad hoc" nature of performing a capability informally would indicate the intent of the control is not met due to a lack of consistency and formality.

Level 2 Planned Tracked

SCR-CMM Level 2 criteria definitions are not available for this control:
▪ A reasonable person would conclude a well-defined and standardized process is required.
▪ At this level of maturity, the “requirements-driven” nature of performing the control is focused on a localized and/or regionalized implementation, not uniform and consistent across the organization.
▪ Requirements are narrowly scoped for applicability and are primarily derived from compliance obligations (e.g., laws, regulations and contracts).

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 automatically support the incident handling process.

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. Forbhreathnú

Teideal	Caighdeán
Automated Reporting	Description Automated mechanisms exist to assist in the reporting of cybersecurity and data protection incidents. Possible Solutions & Considerations Micro-Small Business (<10 staff) / BLS Firm Size Classes 1-2 ∙ Basic incident response plan ∙ Designate incident response contact Small Business (10-49 staff) / BLS Firm Size Classes 3-4 ∙ Documented incident response plan ∙ Incident log ∙ Designated IR team Medium Business (50-249 staff) / BLS Firm Size Classes 5-6 ∙ Formal incident response program ∙ IR playbooks ∙ Tabletop exercises Large Business (250-999 staff) / BLS Firm Size Classes 7-8 ∙ Enterprise incident response program ∙ 24/7 SOC monitoring ∙ SOAR platform Enterprise (> 1,000 staff) / BLS Firm Size Class 9 ∙ Enterprise SOC with SIEM/SOAR (e.g., Splunk SOAR, Palo Alto XSOAR) ∙ IR retainer ∙ Threat hunting 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 SCR-CMM Level 1 criteria definitions are not available for this control: ▪ A reasonable person would conclude this control requires a structured process. ▪ At this level of maturity, the "ad hoc" nature of performing a capability informally would indicate the intent of the control is not met due to a lack of consistency and formality. Level 2 Planned Tracked SCR-CMM Level 2 criteria definitions are not available for this control: ▪ A reasonable person would conclude a well-defined and standardized process is required. ▪ At this level of maturity, the “requirements-driven” nature of performing the control is focused on a localized and/or regionalized implementation, not uniform and consistent across the organization. ▪ Requirements are narrowly scoped for applicability and are primarily derived from compliance obligations (e.g., laws, regulations and contracts). 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 automatically assist in the reporting of cybersecurity and data protection 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.
Automated Tracking, Data Collection & Analysis	Description Automated mechanisms exist to assist in the tracking, collection and analysis of information from actual and potential cybersecurity and data protection incidents. Possible Solutions & Considerations Micro-Small Business (<10 staff) / BLS Firm Size Classes 1-2 ∙ Basic incident response plan ∙ Designate incident response contact Small Business (10-49 staff) / BLS Firm Size Classes 3-4 ∙ Documented incident response plan ∙ Incident log ∙ Designated IR team Medium Business (50-249 staff) / BLS Firm Size Classes 5-6 ∙ Formal incident response program ∙ IR playbooks ∙ Tabletop exercises Large Business (250-999 staff) / BLS Firm Size Classes 7-8 ∙ Enterprise incident response program ∙ 24/7 SOC monitoring ∙ SOAR platform Enterprise (> 1,000 staff) / BLS Firm Size Class 9 ∙ Enterprise SOC with SIEM/SOAR (e.g., Splunk SOAR, Palo Alto XSOAR) ∙ IR retainer ∙ Threat hunting 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 SCR-CMM Level 1 criteria definitions are not available for this control: ▪ A reasonable person would conclude this control requires a structured process. ▪ At this level of maturity, the "ad hoc" nature of performing a capability informally would indicate the intent of the control is not met due to a lack of consistency and formality. Level 2 Planned Tracked SCR-CMM Level 2 criteria definitions are not available for this control: ▪ A reasonable person would conclude a well-defined and standardized process is required. ▪ At this level of maturity, the “requirements-driven” nature of performing the control is focused on a localized and/or regionalized implementation, not uniform and consistent across the organization. ▪ Requirements are narrowly scoped for applicability and are primarily derived from compliance obligations (e.g., laws, regulations and contracts). 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 automatically assist in the tracking, collection and analysis of information from actual and potential cybersecurity and data protection incidents. Level 4 Quantitatively Controlled Incident Response (IRO) capabilities, in addition to being standardized across the entity and centrally managed to ensure consistency across Technology Assets, Applications, Services and/or Data (TAASD), efforts are metrics driven to provide sufficient insight for decision makers to predict optimal performance, ensure continued operations and/or identify areas for improvement. Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Applicable SCR-CMM Level 3 (Well Defined) capabilities are implemented and operational. ▪ Metrics reporting includes quantitative analysis of Key Performance Indicators (KPIs). ▪ Metrics reporting includes quantitative analysis of Key Risk Indicators (KRIs). ▪ Scope of metrics, KPIs and KRIs covers organization-wide cybersecurity and data protection controls, including functions performed by third-parties. ▪ Organizational leadership maintains a formal process to objectively review and respond to metrics, KPIs and KRIs (e.g., monthly or quarterly review). ▪ Based on metrics analysis, process improvement recommendations are submitted for review and are handled in accordance with change control processes. ▪ Business and technical stakeholders are involved in reviewing and approving proposed changes to evolve capabilities. Level 5 Continuously Improving Incident Response (IRO) capabilities, in addition to being standardized across the entity and centrally managed to ensure consistency across Technology Assets, Applications, Services and/or Data (TAASD), efforts are metrics driven to provide sufficient insight for decision makers to predict optimal performance, ensure continued operations and/or identify areas for improvement. Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Applicable SCR-CMM Level 3 (Well Defined) capabilities are implemented and operational. ▪ Based on predictive analysis, process improvements are implemented according to “continuous improvement” practices that affect process changes. ▪ Stakeholders make time-sensitive decisions to support operational efficiency, which may include automated remediation actions via Artificial Intelligence (AI) or Machine Learning (ML) technologies.
Dynamic Reconfiguration	Description Automated mechanisms exist to dynamically reconfigure system components as part of the incident response capability. Possible Solutions & Considerations Micro-Small Business (<10 staff) / BLS Firm Size Classes 1-2 ∙ Basic incident response plan ∙ Designate incident response contact Small Business (10-49 staff) / BLS Firm Size Classes 3-4 ∙ Documented incident response plan ∙ Incident log ∙ Designated IR team Medium Business (50-249 staff) / BLS Firm Size Classes 5-6 ∙ CimTrak Integrity Suite (https://cimcor.com/cimtrak) Large Business (250-999 staff) / BLS Firm Size Classes 7-8 ∙ CimTrak Integrity Suite (https://cimcor.com/cimtrak) Enterprise (> 1,000 staff) / BLS Firm Size Class 9 ∙ CimTrak Integrity Suite (https://cimcor.com/cimtrak) 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 SCR-CMM Level 2 criteria definitions are not available for this control: ▪ A reasonable person would conclude a well-defined and standardized process is required. ▪ At this level of maturity, the “requirements-driven” nature of performing the control is focused on a localized and/or regionalized implementation, not uniform and consistent across the organization. ▪ Requirements are narrowly scoped for applicability and are primarily derived from compliance obligations (e.g., laws, regulations and contracts). 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 automatically dynamically reconfigure system components as part of the incident response capability. 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.
Automatic Disabling of Technology Assets, Applications and/or Services (TAAS)	Description Mechanisms exist to automatically disable Technology Assets, Applications and/or Services (TAAS), upon detection of a possible incident that meets organizational criteria, which allows for forensic analysis to be performed. Possible Solutions & Considerations Micro-Small Business (<10 staff) / BLS Firm Size Classes 1-2 ∙ Basic incident response plan ∙ Designate incident response contact Small Business (10-49 staff) / BLS Firm Size Classes 3-4 ∙ Documented incident response plan ∙ Incident log ∙ Designated IR team Medium Business (50-249 staff) / BLS Firm Size Classes 5-6 ∙ Formal incident response program ∙ IR playbooks ∙ Tabletop exercises Large Business (250-999 staff) / BLS Firm Size Classes 7-8 ∙ Enterprise incident response program ∙ 24/7 SOC monitoring ∙ SOAR platform Enterprise (> 1,000 staff) / BLS Firm Size Class 9 ∙ Enterprise SOC with SIEM/SOAR (e.g., Splunk SOAR, Palo Alto XSOAR) ∙ IR retainer ∙ Threat hunting 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 SCR-CMM Level 2 criteria definitions are not available for this control: ▪ A reasonable person would conclude a well-defined and standardized process is required. ▪ At this level of maturity, the “requirements-driven” nature of performing the control is focused on a localized and/or regionalized implementation, not uniform and consistent across the organization. ▪ Requirements are narrowly scoped for applicability and are primarily derived from compliance obligations (e.g., laws, regulations and contracts). 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 automatically disable Technology Assets, Applications and/or Services (TAAS), upon detection of a possible incident that meets organizational criteria, which allows for forensic analysis to be performed. 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.1 Tagairtí

1.2 Ceanglais aitheanta

1.3 Rialacháin ghaolmhara

2. Ceanglais aitheanta

Ceanglais
Foinse	Ceanglas

3. Rialacháin ghaolmhara

Rialacháin

EULAW

Airteagal 14 1

1. Mar chuid de chreat bainistíochta riosca TFC dá dtagraítear in Airteagal 6(1), beidh pleananna cumarsáide géarchéime i bhfeidhm ag eintitis airgeadais lena gcumasófar, ar a laghad, mórtheagmhais a bhaineann le TFC nó leochaileachtaí a nochtadh ar bhealach freagrach do chliaint agus contrapháirtithe agus don phobal chomh maith, de réir mar is iomchuí.

EULAW

Airteagal 14 2

2. Mar chuid de chreat bainistíochta rioscaí TFC, cuirfidh eintitis airgeadais beartais chumarsáide chun feidhme don fhoireann inmheánach agus do gheallsealbhóirí seachtracha. Cuirfear san áireamh le beartais chumarsáide don fhoireann an gá le hidirdhealú a dhéanamh idir baill foirne a a ghlacann páirt i mbainistíocht rioscaí TFC, go háirithe an fhoireann atá freagrach as freagairt agus athshlánú, agus na baill foirne is gá a chur ar an eolas.

EULAW

Airteagal 14 3

3. Cuirfear de chúram ar dhuine amháin ar a laghad san eintiteas airgeadais an straitéis cumarsáide le haghaidh teagmhas a bhaineann le TFC a chur chun feidhme agus comhlíonfaidh an duine sin an fheidhm phoiblí agus an fheidhm a bhaineann leis na meáin chun na críche sin.

EULAW

Airteagal 9 Cosaint agus cosc
-

EULAW

Airteagal 9 Cosaint agus cosc
-

EULAW

Airteagal 9 4

4. Mar chuid de chreat bainistíochta riosca TFC dá dtagraítear in Airteagal 6(1), déanfaidh eintitis airgeadais na nithe seo a leanas:

(a)	beartas slándála faisnéise a fhorbairt agus a dhoiciméadú lena sainítear rialacha chun infhaighteacht, barántúlacht, sláine agus rúndacht sonraí, sócmhainní faisnéise agus sócmhainní TFC, lena n-áirítear cinn a gcustaiméirí, a chosaint, i gcás inarb infheidhme;

(b)

i gcomhréir le cur chuige bunaithe ar riosca, struchtúr bainistíochta fónta gréasáin agus bonneagair a bhunú trí úsáid a bhaint as teicnící, modhanna agus prótacail iomchuí ar a bhféadfar a áireamh sásraí uathoibrithe a chur chun feidhme chun sócmhainní faisnéise, a ndearnadh difear dóibh, a scaradh amach i gcás cibirionsaithe;

(c)

beartais a chur i bhfeidhm lena ndéantar an rochtain fhisiciúil nó loighciúil ar shócmhainní faisnéise agus sócmhainní TFC a theorannú dá bhfuil riachtanach le haghaidh feidhmeanna agus gníomhaíochtaí dlisteanacha formheasta amháin, agus sraith beartas, nósanna imeachta agus rialuithe a bhunú chuige sin lena dtugtar aghaidh ar chearta rochtana agus lena n-áirithítear riarachán fónta orthu sin;

(d)

beartais agus prótacail le haghaidh sásraí láidre fíordheimhnithe a chur chun feidhme, bunaithe ar chaighdeáin ábhartha agus ar chórais thiomnaithe rialuithe, agus bearta cosanta i ndáil le heochracha cripteagrafacha trína ndéantar sonraí a chriptiú bunaithe ar thorthaí próiseas formheasta aicmithe sonraí agus measúnaithe riosca TFC;

(e)

beartais, nósanna imeachta agus rialuithe doiciméadaithe a chur chun feidhme le haghaidh bainistíocht athruithe TFC, lena n-áirítear athruithe ar bhogearraí, crua-earraí, comhpháirteanna dochtearraí, paraiméadair ar chórais nó paraiméadair slándála, atá bunaithe ar chur chuige measúnaithe riosca agus mar chuid dhílis de phróiseas foriomlán bainistíochta athruithe an eintitis airgeadais, chun a áirithiú go ndéanfar gach athrú ar chórais TFC a thaifeadadh, a thástáil, a mheasúnú, a fhormheas, a chur chun feidhme agus a fhíorú ar bhealach rialaithe;

(f)	beartais iomchuí chuimsitheacha dhoiciméadaithe a bheith acu maidir le paistí agus nuashonruithe.

Chun críocha na chéad fhomhíre, pointe (b), ceapfaidh eintitis airgeadais an bonneagar nasctha gréasáin ar bhealach lenar féidir é a ghearradh ar an toirt nó a dheighilt chun tógálacht a íoslaghdú agus a chosc, go háirithe i gcás próisis airgeadais idirnasctha.

Chun críocha na chéad fhomhíre, pointe (e), déanfar próiseas bainistíochta athruithe TFC a fhormheas ag línte bainistíochta iomchuí agus beidh prótacail shonracha i bhfeidhm aige.

Saincheisteanna nasctha

Naisc
Cineál naisc	Saincheist
is related to	Annual
is related to	relative Control Weighting = 09
is related to	Process
is related to	Respond
is related to	SCRM Focus Tier 2 OPERATIONAL
is related to	SCRM Focus Tier 3 TACTICAL
blocks	Loss of Accountability / Attribution
blocks	Excessive or Unauthorized Privilege
blocks	Unauthorized Privilege Elevation
blocks	Unauthorized Access
blocks	Loss, Theft or Damage of Assets
blocks	Unauthorized Modification / Loss of System Integrity
blocks	Business / Service Interruption
blocks	Data Loss / Integrity Compromise
blocks	Reduced Operational Productivity
blocks	System / Data Compromise (Technical Vector)
blocks	System / Data Compromise (Non-Technical Vector)
blocks	Revenue Loss
blocks	Contractual Default / Termination
blocks	Loss of Competitive Advantage
blocks	Reputational Harm / Loss of Stakeholder Trust
blocks	Regulatory / Legal / Contractual Financial Liability
blocks	Exposure from Unaddressed Vulnerabilities
blocks	System / Service Compromise
blocks	Failure to Support Business / Mission Objectives
blocks	Unaddressed Security / Compliance Exposure
blocks	Unperformed / Unowned Control Responsibilities
blocks	Uncontrolled Internal Security / Privacy Exposure
blocks	Uncontrolled Third-Party Security / Privacy Exposure
blocks	Lack of oversight of internal controls
blocks	Lack of oversight of third-party controls
blocks	Loss of Investigative / Evidentiary Capability
blocks	Delayed Containment / Increased Incident Impact
blocks	Incident Persistence / Recurrence
blocks	Incident Response / Recovery Cost
blocks	Undetected / Delayed Detection of Adverse Activity
blocks	Lack of a security-minded workforce
blocks	Third-Party Cybersecurity Compromise / Exposure
blocks	Third-Party Physical Security Disruption / Exposure
blocks	Sub-Tier / Fourth-Party Supply Chain Exposure
blocks	Third-Party Legal / Compliance Exposure
blocks	Harm from Unauthorized / Unintended Product or Service Use
blocks	Third-Party Dependency Failure
is related to	Quarterly
is related to	relative Control Weighting = 01
is related to	Technology
blocks	Inability to Demonstrate Due Diligence / Due Care
blocks	Recovery Failure / Unacceptable Recovery Delay
blocks	Drought & Water Shortage
blocks	Earthquakes
blocks	Fire & Wildfires
blocks	Floods
blocks	Hurricanes & Tropical Storms
blocks	Landslides & Debris Flow
blocks	Pandemic (Disease) Outbreaks
blocks	Severe Weather
blocks	Space Weather
blocks	Thunderstorms & Lightning
blocks	Tornadoes
blocks	Tsunamis
blocks	Volcanoes
blocks	Winter Storms & Extreme Cold
blocks	Civil or Political Unrest
blocks	Malicious Cyber Activity
blocks	Hazardous Materials Emergencies
blocks	Nuclear, Biological and Chemical (NBC) Weapons
blocks	Physical Crime
blocks	Terrorism & Armed Attacks
blocks	Utility Service Disruption
blocks	Dysfunctional Management Practices
blocks	Human Error
blocks	Technical / Mechanical Failure
blocks	Data Quality Degradation / Data Poisoning
blocks	Fraud, Corruption and/or Intentional Criminal Conduct
blocks	Conflict of Interest (COI) / Undue Influence / Insider Misconduct
blocks	Product Defect / Design Failure
blocks	Supplier Financial Distress / Insolvency
blocks	Workforce Shortage / Loss of Critical Skills / Labor Disruption
blocks	Infrastructure Failure / Degradation
blocks	Inability to Demonstrate Due Diligence / Due Care
blocks	Recovery Failure / Unacceptable Recovery Delay
blocks	Drought & Water Shortage
blocks	Earthquakes
blocks	Fire & Wildfires
blocks	Floods
blocks	Hurricanes & Tropical Storms
blocks	Landslides & Debris Flow
blocks	Pandemic (Disease) Outbreaks
blocks	Severe Weather
blocks	Space Weather
blocks	Thunderstorms & Lightning
blocks	Tornadoes
blocks	Tsunamis
blocks	Volcanoes
blocks	Winter Storms & Extreme Cold
blocks	Civil or Political Unrest
blocks	Malicious Cyber Activity
blocks	Hazardous Materials Emergencies
blocks	Nuclear, Biological and Chemical (NBC) Weapons
blocks	Physical Crime
blocks	Terrorism & Armed Attacks
blocks	Utility Service Disruption
blocks	Dysfunctional Management Practices
blocks	Human Error
blocks	Technical / Mechanical Failure
blocks	Data Quality Degradation / Data Poisoning
blocks	Fraud, Corruption and/or Intentional Criminal Conduct
blocks	Conflict of Interest (COI) / Undue Influence / Insider Misconduct
blocks	Product Defect / Design Failure
blocks	Supplier Financial Distress / Insolvency
blocks	Workforce Shortage / Loss of Critical Skills / Labor Disruption
blocks	Infrastructure Failure / Degradation
is blocked by	IRO-07 Automated Incident Handling Processes – Assessment Procedure
blocks	IR-04(01) Automated Incident Handling Processes
blocks	SI-04(07) Automated Response to Suspicious Events
blocks	IR-04(01) [M] Automated Incident Handling Processes
blocks	IR-04(01) [H] Automated Incident Handling Processes

Secure Controls Framework -
EN: GRCA includes the Secure Controls Framework® (SCF) content, © Secure Controls Framework Council, LLC, used under the Creative Commons Attribution-NoDerivatives 4.0 International Public License. SCF control numbers, names, descriptions and mappings appear exactly as published by the SCF Council – https://securecontrolsframework.com. GRCA may group or reorder SCF content for display, which does not change SCF content; the mappings are shown as links to the frameworks they name. Learn more at https://securecontrolsframework.com.

DE: GRCA enthält Inhalte des Secure Controls Framework® (SCF), © Secure Controls Framework Council, LLC, genutzt unter der Creative Commons Attribution-NoDerivatives 4.0 International Public License. Nummern, Namen, Beschreibungen und Zuordnungen der SCF-Controls erscheinen genau so, wie der SCF Council sie veröffentlicht – https://securecontrolsframework.com. GRCA gruppiert oder sortiert SCF-Inhalte für die Anzeige, ohne sie zu verändern; die Zuordnungen erscheinen als Verknüpfungen zu den genannten Regelwerken. Mehr unter https://securecontrolsframework.com.