+Airteagal 28 An próiseálaí
---+Airteagal 28 1.
---+Airteagal 28 2.
---+Airteagal 28 3.
---+Airteagal 28 4.
---+Airteagal 28 5.
---+Airteagal 28 6.
---+Airteagal 28 7.
---+Airteagal 28 8.
---+Airteagal 28 9.
---+Airteagal 28 10.

Airteagal 28 An próiseálaí

-

1. Forbhreathnú

,
Teideal Rialáil
Airteagal 28 1.
I gcás ina mbeidh próiseáil le déanamh thar ceann rialaitheora, ní bhainfidh an rialaitheoir úsáid ach as próiseálaithe a thugann ráthaíochtaí leordhóthanacha go gcuirfear bearta iomchuí teicniúla agus eagraíochtúla chun feidhme sa dóigh is go gcomhlíonfaidh an phróiseáil ceanglais an Rialacháin seo agus a áirithiú go gcosnófar cearta an ábhair sonraí.
Airteagal 28 2.
Ní fhostóidh próiseálaí cúnamh próiseálaí eile, gan údarú sonrach nó ginearálta a fháil ón rialaitheoir i scríbhinn. sin, i gcás údaraithe sonraigh nó ghinearálta, déanfaidh an próiseálaí an rialaitheoir a chur ar an eolas i gcónaí maidir le haon athrú a bheadh beartaithe a bhaineann le próiseálaithe a chur leis nó in ionad próiseálaithe eile, sa chaoi go mbeadh deis ag an rialaitheoir agóid a dhéanamh i gcoinne athruithe den chineál sin.
Airteagal 28 3.

Rialófar an phróiseáil a dhéanfaidh próiseálaí le conradh nó le gníomh dlí eile faoi dhlí an Aontais nó faoi dhlí Ballstáit atá ina cheangal ar an bpróiseálaí i dtaca leis an rialaitheoir ó thaobh dlí agus ina leagtar amach ábhar agus fad na próiseála, cineál agus críoch na próiseála, cineál na sonraí pearsanta agus catagóirí na n-ábhar sonraí do na sonraí agus oibleagáidí agus cearta an rialaitheora. Foráilfear sa chonradh nó sa ghníomh dlíthiúil eile go ndéanfaidh an próiseálaí an méid seo a leanas, go háirithe:

(a) 

ní phróiseálfaidh sé na sonraí pearsanta ach amháin ar threoracha doiciméadaithe a fháil ón rialaitheoir chuige sin, lena n-áirítear maidir le haistrithe sonraí pearsanta chuig tríú tír nó chuig eagraíocht idirnáisiúnta, mura n-éilítear an phróiseáil sin a dhéanamh faoi dhlí an Aontais nó faoi dhlí Ballstáit ar faoina réir atá an próiseálaí; agus sa chás sin, cuirfidh an próiseálaí an rialaitheoir in iúl faoin gceanglas dlíthiúil sin sula ndéanfar an phróiseáil, ach amháin mura gcoisctear an fhaisnéis sin faoin dlí sin ar fhorais thábhachtacha leasa phoiblí;

(b) 

áiritheoidh sé go bhfuil gealltanas rúndachta tugtha ag na daoine atá údaraithe chun na sonraí pearsanta a phróiseáil nó go bhfuil siad faoi cheangal oibleagáide rúndachta reachtúla iomchuí;

(c) 

déanfaidh sé gach beart is gá de bhun Airteagal 32;

(d) 

urramóidh sé na coinníollacha dá dtagraítear i mír 2 agus 4 faoina bhfostófar próiseálaí eile;

▼C2

(e) 

agus cineál na próiseála á chur san áireamh, cuideoidh sé leis an rialaitheoir, a mhéid is féidir, trí bhearta iomchuí teicniúla agus eagraíochtúla a bhaineann le comhlíonadh oibleagáid an rialaitheora iarrataí a fhreagairt maidir le feidhmiú chearta an ábhair sonraí a leagtar amach i gCaibidil III;

▼B

(f) 

cúnamh a thabhairt don rialaitheoir chun a áirithiú go gcomhlíontar na hoibleagáidí de bhun Airteagal 32 go hAirteagal 36, á chur san áireamh dó cineál na próiseála agus an fhaisnéis atá ar fáil don phróiseálaí;

(g) 

ar rogha an rialaitheora, tabharfaidh sé na sonraí pearsanta uile ar ais don rialaitheoir nó scriosfaidh sé iad, tar éis dheireadh sholáthar na seirbhísí a bhaineann leis an bpróiseáil sonraí agus na cóipeanna atá ar marthain a scriosadh, mura rud é go n-éilíonn dlí an Aontais nó dlí Ballstáit go ndéanfar na sonraí údarú sonrach nó ginearálta sin a stóráil; agus

▼C2

(h) 

cuirfidh sé ar fáil don rialaitheoir an fhaisnéis uile is gá chun comhlíonadh na n-oibleagáidí atá leagtha síos san Airteagal seo a thaispeáint agus ceadóidh sé go ndéanfaidh an rialaitheoir nó iniúchóir eile dá dtabharfaidh an rialaitheoir sainordú, iniúchtaí, lena n-áirítear cigireachtaí, agus beidh baint aige leis na hiniúchtaí agus leis na cigireachtaí sin.

▼B

I dtaca le pointe (h) den chéad fhomhír, cuirfidh an próiseálaí an rialaitheoir ar an eolas láithreach, más rud é, ina thuairim, go sáraíonn treoir an Rialachán seo nó forálacha maidir le cosaint sonraí de chuid an Aontais nó Ballstáit.

Airteagal 28 4.
I gcás ina bhfostóidh próiseálaí cúnamh próiseálaí eile d'fhonn gníomhaíochtaí sonracha próiseála a chur i gcrích thar ceann an rialaitheora, déanfar na hoibleagáidí cosanta sonraí céanna atá leagtha amach sa chonradh nó i ngníomh dlíthiúil eile idir an rialaitheoir agus an próiseálaí dá dtagraítear i mír 2 a fhorchur ar an bpróiseálaí eile, trí chonradh nó trí ghníomh dlíthiúil eile faoi dhlí an Aontais nó faoi dhlí Ballstáit, lena dtabharfar go háirithe ráthaíochtaí leordhóthanacha go gcuirfear na bearta iomchuí teicniúla agus eagraíochtúla chun feidhme sa dóigh is go gcomhlíonfaidh an phróiseáil ceanglais an Rialacháin seo. I gcás ina mainníonn an próiseálaí eile a oibleagáidí cosanta sonraí a chomhlíonadh, beidh an chéad phróiseálaí go hiomlán dlite don rialaitheoir as feidhmiú oibleagáidí an phróiseálaí eile.
Airteagal 28 5.
Má chloíonn próiseálaí le cód formheasta iompair amhail dá dtagraítear in Airteagal 40 nó le sásra deimhniúcháin amhail dá dtagraítear in Airteagal 42, féadfar sin a úsáid mar eilimint le ráthaíochtaí leordhóthanacha iomchuí amhail dá dtagraítear i mír 1 agus i mír 4 den Airteagal seo a thaispeáint.
Airteagal 28 6.
Gan dochar do chonradh aonair idir an rialaitheoir agus an próiseálaí, féadfaidh an conradh nó an gníomh dlíthiúil eile dá dtagraítear i mír 3 agus i mír 4 den Airteagal seo a bheith bunaithe, go hiomlán nó go páirteach, ar chlásail chaighdeánacha chonarthacha dá dtagraítear i mír 7 agus i mír 8 den Airteagal seo, lena n-áirítear nuair atá siad mar chuid de dheimhniúchán a dheonaítear don rialaitheoir nó don phróiseálaí de bhun Airteagal 42 agus Airteagal 43.
Airteagal 28 7.
Féadfaidh an Coimisiún clásail chaighdeánacha chonarthacha a leagan síos le haghaidh na n-ábhar dá dtagraítear i mír 3 agus i mír 4 den Airteagal seo agus i gcomhréir leis an nós imeachta scrúdúcháin dá dtagraítear in Airteagal 93(2).
Airteagal 28 8.
Féadfaidh údarás maoirseachta clásail chaighdeánacha chonarthacha a ghlacadh le haghaidh na n-ábhar dá dtagraítear i mír 3 agus i mír 4 i gcomhréir leis an sásra comhsheasmhachta dá dtagraítear in Airteagal 63.
Airteagal 28 9.
Is i scríbhinn, lena n-áirítear i bhfoirm leictreonach, a bheidh an conradh nó an gníomh dlíthiúil eile dá dtagraítear i mír 3 agus i mír 4.
Airteagal 28 10.
Gan dochar d'Airteagal 82, d'Airteagal 83 agus d'Airteagal 84, má sháraíonn próiseálaí an Rialachán seo trí chríocha agus modhanna na próiseála a chinneadh, measfar gur rialaitheoir é an próiseálaí i ndáil leis an bpróiseáil sin.

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 Personal Data (PD) Inventory Automation Support

Description

Automated mechanisms exist to determine if Personal Data (PD) is maintained in electronic form.

Possible Solutions & Considerations

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

∙ Data classification program
∙ Data privacy program
∙ Data Protection Impact Assessment (DPIA)
∙ Product / project management

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

∙ Data classification program
∙ Data privacy program
∙ Data Protection Impact Assessment (DPIA)
∙ Product / project management

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

∙ Data classification program
∙ Data privacy program
∙ Data Protection Impact Assessment (DPIA)
∙ Product / project management

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

∙ Data classification program
∙ Data privacy program
∙ Data Protection Impact Assessment (DPIA)
∙ Product / project management

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

∙ Data classification program
∙ Data privacy program
∙ Data Protection Impact Assessment (DPIA)
∙ Product / project management

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

Privacy (PRI) 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 PRI 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 PRI domain capabilities are well-documented and kept current by process owners.
▪ A data privacy team, or similar function, is appropriately staffed and supported to implement and maintain PRI domain capabilities.
▪ Technology is leveraged to enhance the efficiency and accuracy of data privacy operations (e.g., privacy notice management software and customer management solution).
▪ 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 PRI 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 determine if Personal Data (PD) is maintained in electronic form.

Level 4 Quantitatively Controlled

Privacy (PRI) 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

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.
SCF Data Privacy Requirements for Contractors & Service Providers

Description

Mechanisms exist to include data privacy requirements in contracts and other acquisition-related documents that establish data privacy roles and responsibilities for contractors and service providers.

Possible Solutions & Considerations

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

∙ Data classification program
∙ Data privacy program
∙ Data Protection Impact Assessment (DPIA)
∙ Product / project management

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

∙ Data classification program
∙ Data privacy program
∙ Data Protection Impact Assessment (DPIA)
∙ Product / project management

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

∙ Data classification program
∙ Data privacy program
∙ Data Protection Impact Assessment (DPIA)
∙ Product / project management

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

∙ Data classification program
∙ Data privacy program
∙ Data Protection Impact Assessment (DPIA)
∙ Product / project management

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

∙ Data classification program
∙ Data privacy program
∙ Data Protection Impact Assessment (DPIA)
∙ Product / project management

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

Privacy (PRI) 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 PRI 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 PRI domain capabilities are well-documented and kept current by process owners.
▪ A data privacy team, or similar function, is appropriately staffed and supported to implement and maintain PRI domain capabilities.
▪ Technology is leveraged to enhance the efficiency and accuracy of data privacy operations (e.g., privacy notice management software and customer management solution).
▪ 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 PRI 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 include data privacy requirements in contracts and other acquisition-related documents that establish data privacy roles and responsibilities for contractors and service providers.

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.
SCF Data Privacy Requirements for Contractors & Service Providers

Description

Mechanisms exist to include data privacy requirements in contracts and other acquisition-related documents that establish data privacy roles and responsibilities for contractors and service providers.

Possible Solutions & Considerations

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

∙ Data classification program
∙ Data privacy program
∙ Data Protection Impact Assessment (DPIA)
∙ Product / project management

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

∙ Data classification program
∙ Data privacy program
∙ Data Protection Impact Assessment (DPIA)
∙ Product / project management

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

∙ Data classification program
∙ Data privacy program
∙ Data Protection Impact Assessment (DPIA)
∙ Product / project management

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

∙ Data classification program
∙ Data privacy program
∙ Data Protection Impact Assessment (DPIA)
∙ Product / project management

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

∙ Data classification program
∙ Data privacy program
∙ Data Protection Impact Assessment (DPIA)
∙ Product / project management

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

Privacy (PRI) 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 PRI 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 PRI domain capabilities are well-documented and kept current by process owners.
▪ A data privacy team, or similar function, is appropriately staffed and supported to implement and maintain PRI domain capabilities.
▪ Technology is leveraged to enhance the efficiency and accuracy of data privacy operations (e.g., privacy notice management software and customer management solution).
▪ 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 PRI 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 include data privacy requirements in contracts and other acquisition-related documents that establish data privacy roles and responsibilities for contractors and service providers.

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.