+Airteagal 49 Maoluithe i gcásanna sonracha
---+Airteagal 49 1.
---+Airteagal 49 2.
---+Airteagal 49 3.
---+Airteagal 49 4.
---+Airteagal 49 5.
---+Airteagal 49 6.

Airteagal 49 Maoluithe i gcásanna sonracha

-

1. Forbhreathnú

,
Teideal Rialáil
Airteagal 49 1.

In éagmais cinneadh leordhóthanachta de bhun Airteagal 45(3), nó in éagmais coimircí iomchuí de bhun Airteagal 46, lena n-áirítear rialacha ceangailteacha corparáideacha, ní dhéanfar aistriú sonraí pearsanta ná sraith d'aistrithe sonraí pearsanta chuig tríú tír ná chuig eagraíocht idirnáisiúnta ach amháin ar cheann amháin de na coinníollacha seo a leanas:

(a) 

gur thoiligh an t-ábhar sonraí go follasach leis an aistriú atá beartaithe, tar éis é a bheith curtha ar an eolas go bhféadfaidh rioscaí bheith ag baint le haistrithe den sórt sin don ábhar sonraí in éagmais cinneadh leordhóthanachta agus in éagmais coimircí iomchuí;

(b) 

gur gá an t-aistriú a dhéanamh chun conradh idir an t-ábhar sonraí agus an rialaitheoir a chomhlíonadh nó chun bearta réamhchonarthacha a chur chun feidhme arna iarraidh sin don ábhar sonraí;

(c) 

gur gá an t-aistriú a dhéanamh chun conradh, arna dhéanamh chun leasa an ábhair sonraí, idir an rialaitheoir agus duine nádúrtha nó dlítheanach eile a thabhairt i gcrích nó a chomhlíonadh;

(d) 

gur gá an t-aistriú a dhéanamh ar fhorais thábhachtacha leasa phoiblí;

(e) 

gur gá an t-aistriú a dhéanamh chun éilimh dhlíthiúla a bhunú, a fheidhmiú nó a chosaint;

(f) 

gur gá an t-aistriú a dhéanamh chun leasanna ríthábhachtacha an ábhair sonraí nó daoine eile a chosaint, i gcás nach féidir leis an ábhar sonraí toiliú a thabhairt go fisiciúil nó go dlíthiúil; nó

(g) 

go ndéantar an t-aistriú ó chlár arna cheapadh, de réir dhlí an Aontais nó dlí Ballstáit, chun faisnéis a chur ar fáil don phobal, ar clár é a fhéadfaidh an pobal i gcoitinne a cheadú nó a fhéadfaidh aon duine a thaispeánann leas dlisteanach a cheadú, ar choinníoll go bhfuil na coinníollacha maidir le comhairliúchán atá leagtha síos le dlí an Aontais nó le dlí Ballstáit comhlíonta sa chás áirithe.

I gcás nach bhféadfaí aistriú a bhunú ar fhoráil in Airteagal 45 nó 46, lena n-áirítear na forálacha maidir le rialacha ceangailteacha corparáideacha, agus nach bhfuil aon cheann de na maoluithe do chás sonrach dá dtagraítear sa chéad fhomhír den mhír seo infheidhme, ní fhéadfar aistriú chuig tríú tír nó eagraíocht idirnáisiúnta a dhéanamh ach amháin sa chás nach aistriú atarlaitheach é, nach mbaineann sé ach le líon teoranta ábhar sonraí, gur gá é chun críocha leasanna dlisteanacha tathantacha atá á saothrú ag an rialaitheoir agus nach bhfuil sáraíocht ag leasanna, cearta nó saoirsí an ábhair sonraí orthu, agus go bhfuil measúnú déanta ag an rialaitheoir ar na himthosca ar fad a bhaineann leis an aistriú sonraí agus, ar bhonn an mheasúnaithe sin, go bhfuil coimircí oiriúnacha soláthraithe aige i ndáil le cosaint sonraí pearsanta Maidir le pointe (h) den chéad fhomhír, cuirfidh an rialaitheoir an t-údarás maoirseachta ar an eolas faoin aistriú. Chomh maith leis an fhaisnéis dá dtagraítear in Airteagal 13 agus Airteagal 14, cuirfidh an rialaitheoir an t-ábhar sonraí ar an eolas maidir leis an aistriú agus maidir leis na leasanna dlisteanacha tathantacha atá á saothrú

Airteagal 49 2.
Ní áireofar na sonraí pearsanta ar fad ná na catagóirí sonraí pearsanta ar fad atá sa chlár i gcás aistrithe de bhun phointe (g) den chéad fhomhír de mhír 1. I gcás ina bhfuil sé beartaithe go bhféadfaidh daoine a bhfuil leas dlisteanach acu an clár a cheadú, ní dhéanfar an t-aistriú ach ar iarraidh ó na daoine sin nó má tá siad le bheith ina bhfaighteoirí.
Airteagal 49 3.
Ní bheidh feidhm ag pointí (a), (b), (c) den chéad fhomhír de mhír 1 ná ag an dara fomhír de mhír 1 maidir le gníomhaíochtaí a dhéanann údaráis phoiblí i bhfeidhmiú a gcumhachtaí poiblí.
Airteagal 49 4.
Déanfar an leas poiblí dá dtagraítear i bpointe (d) den chéad fhomhír de mhír 1 a bheith aitheanta i ndlí an Aontais nó i ndlí an Bhallstáit a bhfuil an rialaitheoir faoina réir.
Airteagal 49 5.
In éagmais cinneadh leordhóthanachta, féadfaidh dlí an Aontais nó dlí Ballstáit, ar chúiseanna tábhachtacha leasa phoiblí, teorannacha a leagan síos go sainráite ar aistriú catagóirí sonracha sonraí pearsanta chuig tríú tír nó chuig eagraíocht idirnáisiúnta. Cuirfidh na Ballstáit forálacha den sórt sin in iúl don Choimisiún.
Airteagal 49 6.
Déanfaidh an rialaitheoir nó an próiseálaí an measúnú agus na coimircí oiriúnacha dá dtagraítear sa dara fomhír de mhír 1 den Airteagal seo a dhoiciméadú sna taifid dá dtagraítear in Airteagal 30.

1.1 Tagairtí

1.2 Ceanglais aitheanta

1.3 Caighdeáin ghaolmhara

2. Ceanglais aitheanta

Ceanglais
Foinse Ceanglas

3. Caighdeáin ghaolmhara

Caighdeáin
Foinse Ceanglas
SCF Ad-Hoc Transfers

Description

Mechanisms exist to secure ad-hoc exchanges of large digital files with internal or external parties.

Possible Solutions & Considerations

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

∙ Data classification program
∙ Secure Baseline Configurations (SBC)
∙ Content / DNS filtering

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

∙ Data classification program
∙ Secure Baseline Configurations (SBC)
∙ Content / DNS filtering

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

∙ Data classification program
∙ Secure Baseline Configurations (SBC)
∙ Content / DNS filtering

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

∙ Data classification program
∙ Secure Baseline Configurations (SBC)
∙ Content / DNS filtering∙ Data governance program

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

∙ Data classification program
∙ Secure Baseline Configurations (SBC)
∙ Content / DNS filtering∙ Data governance program

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

Data Classification & Handling (DCH) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include:
▪ Policies, standards & procedures associated with DCH domain capabilities provide limited coverage due to the depth and breadth of the existing documentation.
▪ Data management-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
▪ Restrictions for ad-hoc data transfers are primarily administrative in nature (e.g., policies & standards).

Level 2 Planned Tracked

Data Classification & Handling (DCH) 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 DCH 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 DCH domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD).
▪ Data classification and handling-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines).
▪ Data classification and handling management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel.
▪ A formalized data classification scheme exists to identify categories of data, based on protection requirements from applicable laws, regulations and/or contractual obligations.
▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to document where sensitive/regulated data is stored, transmitted and/or processed.

Level 3 Well Defined

Data Classification & Handling (DCH) 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 DCH domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function.
▪ Standardized Operating Procedures (SOP) associated with DCH domain capabilities are well-documented and kept current by process owners.
▪ A Governance, Risk & Compliance (GRC) team, or similar function, is appropriately staffed and supported to implement and maintain DCH domain capabilities.
▪ Technology is leveraged to enhance the efficiency and accuracy of data classification and handling operations (e.g., GRC platform).
▪ 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 DCH 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 secure ad-hoc exchanges of large digital files with internal or external parties.

Level 4 Quantitatively Controlled

Data Classification & Handling (DCH) 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

Data Classification & Handling (DCH) 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.
SCF External Transfer of Sensitive / Regulated Data

Description

Mechanisms exist to restrict and govern the transfer of sensitive and/or regulated data:
(1) Cross-border; and/or
(2) Interorganizational.

Possible Solutions & Considerations

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

∙ Model contracts
∙ Binding Corporate Rules (BCR)

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

∙ Model contracts
∙ Binding Corporate Rules (BCR)

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

∙ Model contracts
∙ Binding Corporate Rules (BCR)

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

∙ Model contracts
∙ Binding Corporate Rules (BCR)

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

∙ Model contracts
∙ Binding Corporate Rules (BCR)

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

Data Classification & Handling (DCH) 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 DCH 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 DCH domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD).
▪ Data classification and handling-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines).
▪ Data classification and handling management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel.
▪ A formalized data classification scheme exists to identify categories of data, based on protection requirements from applicable laws, regulations and/or contractual obligations.

Level 3 Well Defined

Data Classification & Handling (DCH) 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 DCH domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function.
▪ Standardized Operating Procedures (SOP) associated with DCH domain capabilities are well-documented and kept current by process owners.
▪ A Governance, Risk & Compliance (GRC) team, or similar function, is appropriately staffed and supported to implement and maintain DCH domain capabilities.
▪ Technology is leveraged to enhance the efficiency and accuracy of data classification and handling operations (e.g., GRC platform).
▪ 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 DCH 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 restrict and govern the transfer of sensitive and/or regulated data to third-countries or international organizations.

Level 4 Quantitatively Controlled

Data Classification & Handling (DCH) 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

Data Classification & Handling (DCH) 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.