+Airteagal 4 Sainmhínithe
|
Airteagal 4 Sainmhínithe
Airteagal 4
Chun críocha an Rialacháin seo, tá feidhm ag na sainmhínithe seo a leanas:
(1)
►C2
ciallaíonn “sonraí pearsanta” aon fhaisnéis a bhaineann le duine nádúrtha sainaitheanta nó in-sainaitheanta (“ábhar sonraí”); ◄ is é is duine nádúrtha in-sainaitheanta ann duine is féidir a shainaithint, go díreach nó go hindíreach, go háirithe trí thagairt a dhéanamh d'aitheantóir amhail ainm, uimhir aitheantais, sonraí suímh, aitheantóir ar líne nó ceann amháin nó níos mó de thosca a bhaineann go sonrach le céannacht fhisiceach, fhiseolaíoch, ghéiniteach, mheabhrach, eacnamaíoch, chultúrtha nó shóisialta an duine nádúrtha sin;
(2)
ciallaíonn “próiseáil” aon oibríocht nó aon sraith d'oibríochtaí a dhéantar ar shonraí pearsanta nó ar shraitheanna de shonraí pearsanta, trí mhodhanna uathoibrithe nó trí mhodhanna eile, amhail bailiú, taifeadadh, eagrú, struchtúrú, stóráil, oiriúnú nó athrú, aisghabháil, ceadú, úsáid, nochtadh trí tharchur, trí scaipeadh nó trí chur ar fáil ar bhealach eile, ailíniú nó comhcheangal, srianadh, léirscriosadh nó díothú;
(3)
ciallaíonn “srianadh ar phróiseáil” sonraí pearsanta stóráilte a mharcáil agus é d'aidhm leis sin teorainn a chur leis an bpróiseáil a dhéanfar orthu sa todhchaí;
(4)
ciallaíonn “próifíliú” aon chineál próiseála uathoibrithe a dhéantar ar shonraí pearsanta arb éard í úsáid na sonraí sin chun measúnú a dhéanamh ar ghnéithe pearsanta áirithe a bhaineann le duine nádúrtha, go háirithe chun anailís a dhéanamh ar ghnéithe a bhaineann le feidhmíocht an duine nádúrtha sin ag an obair, le staid eacnamaíoch, le sláinte, le roghanna pearsanta, le hábhair spéise, le hiontaofacht, le hiompar, le suíomh nó le gluaiseachtaí an duine nádúrtha sin nó chun na gnéithe sin a thuar;
(5)
ciallaíonn “ainm bréige a chur i bhfeidhm” próiseáil a dhéantar ar chaoi nach féidir na sonraí a chur i leith ábhair sonraí ar leith a thuilleadh gan faisnéis bhreise a úsáid, ar choinníoll go gcoimeádtar faisnéis bhreise den sórt sin ar leithligh agus go bhfuil sí faoi réir bearta teicniúla agus eagraíochtúla chun a áirithiú nach gcuirtear na sonraí pearsanta i leith duine nádúrtha sainaitheanta nó in-sainaitheanta;
(6)
ciallaíonn “córas comhdúcháin” aon sraith struchtúraithe de shonraí pearsanta a bhfuil rochtain orthu de réir critéir shonracha, is cuma má tá an sraith sin lárnaithe, díláraithe nó scaipthe ar bhonn feidhmeach nó geografach;
(7)
ciallaíonn “rialaitheoir” an duine nádúrtha nó dlítheanach, an t-údarás poiblí, an ghníomhaireacht nó an comhlacht eile a chinneann, ina aonar nó i gcomhpháirt, críocha agus modhanna na próiseála; i gcás ina gcinntear críocha agus modhanna na próiseála sin le dlí an Aontais nó le dlí Ballstáit, féadfar foráil a dhéanamh don rialaitheoir le dlí an Aontais nó le dlí Ballstáit nó féadfar foráil a dhéanamh do na critéir shonracha dá ainmniú le dlí an Aontais nó le dlí Ballstáit;
(8)
ciallaíonn “próiseálaí” duine nádúrtha nó dlítheanach, údarás poiblí, gníomhaireacht nó comhlacht eile a phróiseálann sonraí pearsanta thar ceann an rialaitheora;
(9)
ciallaíonn “faighteoir” duine nádúrtha nó dlítheanach, údarás poiblí, gníomhaireacht, nó comhlacht eile, dá nochtar na sonraí pearsanta, bíodh siad ina dtríú páirtí nó ná bíodh. Maidir le húdaráis phoiblí a fhéadfaidh sonraí pearsanta a fháil faoi chuimsiú fiosrúchán ar leith i gcomhréir le dlí an Aontais nó le dlí Ballstáit, ní mheasfar gur faighteoirí iad; comhlíonfaidh an phróiseáil a dhéanfaidh na húdaráis phoiblí sin ar na sonraí sin na rialacha is infheidhme maidir le cosaint sonraí de réir na gcríoch atá leis an bpróiseáil;
(10)
ciallaíonn “tríú páirtí” duine nádúrtha nó dlítheanach, údarás poiblí, gníomhaireacht, nó comhlacht eile seachas an t-ábhar sonraí, an rialaitheoir, an próiseálaí agus daoine a údaraítear, faoi údarás díreach an rialaitheora nó an phróiseálaí, chun na sonraí a phróiseáil;
▼C2
(11)
ciallaíonn “toiliú” an ábhair sonraí aon léiriú sonrach, feasach agus gan athbhrí a thugtar faoi shaoirse ar mhianta an ábhair sonraí trína gcuireann sé nó sí in iúl, trí ráiteas nó trí ghníomhaíocht shoiléir dhearfach, go n-aontaíonn sé nó sí le próiseáil sonraí pearsanta a bhaineann leis nó léi;
▼B
(12)
ciallaíonn “sárú i ndáil le sonraí pearsanta” sárú ar shlándáil as a dtiocfaidh scrios, cailleadh, athrú, nó nochtadh neamhúdaraithe sonraí pearsanta a rinneadh a tharchur, a stóráil nó a phróiseáil ar bhealach eile, nó rochtain neamhúdaraithe ar na sonraí sin, bíodh sé sin de thaisme nó neamhdhleathach;
(13)
ciallaíonn “sonraí géiniteacha” sonraí pearsanta a bhaineann le tréithe géiniteacha duine nádúrtha a fuarthas le hoidhreacht nó a fuarthas, a thugann faisnéis uathúil faoi fhiseolaíocht nó sláinte an duine nádúrtha sin agus arb é atá iontu an toradh, go háirithe, ar anailís arna déanamh ar shampla bitheolaíoch ón duine nádúrtha atá i gceist;
(14)
ciallaíonn “sonraí bithmhéadracha” sonraí pearsanta a eascraíonn as próiseáil theicniúil ar leith agus a bhaineann le saintréithe fisiciúla, fiseolaíocha nó iompraíochta duine nádúrtha, ar sonraí iad lena gceadaítear nó lena ndeimhnítear sainaithint uathúil an duine nádúrtha sin, amhail íomhánna den aghaidh nó sonraí dachtalascópacha;
(15)
ciallaíonn “sonraí a bhaineann leis an tsláinte” sonraí pearsanta a bhaineann le sláinte fhisiciúil nó mheabhrach duine nádúrtha, lena n-áirítear soláthar seirbhísí cúraim sláinte, lena nochtar faisnéis faoina stádas sláinte;
(16)
ciallaíonn “príomhbhunaíocht”:
(a)
maidir le rialaitheoir a bhfuil bunaíochtaí i níos mó ná Ballstát amháin aige, an áit a bhfuil a riarachán lárnach san Aontas, mura rud é go nglactar na cinntí maidir le críocha agus modhanna próiseála na sonraí pearsanta i mbunaíocht eile de chuid an rialaitheora san Aontas agus go bhfuil an chumhacht ag an mbunaíocht sin chun a chur faoi deara cinntí den sórt sin a chur chun feidhme, agus sa chás sin meastar gurb í an bhunaíocht a ghlac cinntí den sórt sin an phríomh-bhunaíocht;
(b)
i ndáil le próiseálaí a bhfuil bunaíochtaí i níos mó ná Ballstát amháin aige, an áit a bhfuil a riarachán lárnach san Aontas, nó mura bhfuil aon riarachán lárnach ag an bpróiseálaí san Aontas, bunaíocht an phróiseálaí san Aontas ina ndéantar na príomhghníomhaíochtaí próiseála i gcomhthéacs gníomhaíochtaí bunaíochta de chuid an phróiseálaí a mhéid atá an próiseálaí faoi réir oibleagáidí sonracha faoin Rialachán seo;
(17)
ciallaíonn “ionadaí” duine nádúrtha nó dlítheanach atá bunaithe san Aontas a dhéanann ionadaíocht thar ceann an rialaitheora nó an phróiseálaí maidir lena n-oibleagáidí faoi seach faoin Rialachán seo, agus atá ceaptha i scríbhinn ag an rialaitheoir nó ag an bpróiseálaí de bhun Airteagal 27;
(18)
ciallaíonn “fiontar” duine nádúrtha nó dlítheanach atá ag gabháil do ghníomhaíocht eacnamaíoch, is cuma faoi fhoirm dhlíthiúil na gníomhaíochta sin, lena n-áirítear comhpháirtíochtaí nó comhlachais a bhíonn ag gabháil go rialta do ghníomhaíocht eacnamaíoch;
(19)
ciallaíonn “grúpa gnóthas” gnóthas rialaitheach agus a ghnóthais atá faoi rialú;
(20)
ciallaíonn “rialacha ceangailteacha corparáideacha” beartais um chosaint sonraí pearsanta a gcloíonn rialaitheoir nó próiseálaí atá bunaithe ar chríoch Ballstáit leo, ar beartais iad le haghaidh aistrithe sonraí pearsanta nó sraith d'aistrithe sonraí pearsanta chuig rialaitheoir nó chuig próiseálaí i dtríú tír amháin nó níos mó laistigh de ghrúpa gnóthas, nó grúpa fiontar a bhfuil gníomhaíocht chomhpháirteach eacnamaíoch ar bun acu;
(21)
ciallaíonn “údarás maoirseachta” údarás poiblí neamhspleách a bhunaíonn Ballstát de bhun Airteagal 51;
▼C2
(22)
ciallaíonn “údarás maoirseachta lena mbaineann” údarás maoirseachta a mbaineann próiseáil sonraí pearsanta leis mar gurb amhlaidh:
(a)
go bhfuil an rialaitheoir nó an próiseálaí bunaithe ar chríoch Bhallstát an údaráis maoirseachta sin;
(b)
go bhfuil éifeacht shubstainteach nó gur dóchúil go mbeidh éifeacht shubstainteach ag an bpróiseáil ar ábhair sonraí atá ina gcónaí i mBallstát an údaráis maoirseachta sin; nó
(c)
go ndearnadh gearán a thaisceadh leis an údarás maoirseachta sin;
▼B
(23)
ciallaíonn “próiseáil trasteorann” ceann acu seo:
(a)
próiseáil sonraí pearsanta a dhéantar i gcomhthéacs gníomhaíochtaí bunaíochtaí i níos mó ná Ballstát amháin de chuid rialaitheora nó próiseálaí san Aontas, i gcás ina bhfuil an rialaitheoir nó an próiseálaí bunaithe i níos mó ná Ballstát amháin; nó
(b)
próiseáil sonraí pearsanta a dhéantar san Aontas a dhéantar i gcomhthéacs gníomhaíochtaí bunaíochta aonair de chuid rialaitheora nó próiseálaí san Aontas ach a bhfuil éifeacht shubstainteach ag an bpróiseáil sin ar ábhair sonraí i níos mó ná Ballstát amháin nó gur dóchúil go mbeidh éifeacht shubstainteach aici orthu.
(24)
ciallaíonn “agóid ábhartha réasúnaithe” agóid i gcoinne dréachtchinneadh i dtaca le cibé an ann do shárú ar an Rialachán seo nó nach ann dó, nó an gcomhlíonann an gníomhaíocht a bheartaítear i dtaca leis an rialaitheoir nó leis an bpróiseálaí an Rialachán seo, agóid a thaispeánann go soiléir suntasacht na rioscaí a d'fhéadfadh a bheith mar thoradh ar an dréachtchinneadh maidir le cearta bunúsacha agus saoirsí bunúsacha ábhar sonraí agus, i gcás inarb infheidhme, saorghluaiseacht sonraí pearsanta laistigh den Aontas;
(25)
ciallaíonn “seirbhís de chuid na sochaí faisnéise” seirbhís mar a shainmhínítear í i bpointe (b) d'Airteagal 1(1) de Threoir (AE) 2015/1535 ó Pharlaimint na hEorpa agus ón gComhairle (
1
);
(26)
ciallaíonn “eagraíocht idirnáisiúnta” eagraíocht agus a gcuid fochomhlachtaí a rialaítear leis an dlí idirnáisiúnta poiblí, nó aon chomhlacht eile a bhunaítear le comhaontú idir dhá thír nó níos mó nó ar bhonn chomhaontaithe idir dhá thír nó níos mó.
1. Forbhreathnú
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
|
Achieving Security, Compliance & Resilience Requirements
Description
Mechanisms exist to design Technology Assets, Applications and/or Services (TAAS) so that required capabilities continue to operate in a controlled and acceptable manner, when conditions are both routine and degraded.
Possible Solutions & Considerations
Micro-Small Business (<10 staff) / BLS Firm Size Classes 1-2
∙ Defined "secure engineering principles" (e.g., alignment with NIST 800-160)
Small Business (10-49 staff) / BLS Firm Size Classes 3-4
∙ Defined "secure engineering principles" (e.g., alignment with NIST 800-160)
Medium Business (50-249 staff) / BLS Firm Size Classes 5-6
∙ Defined "secure engineering principles" (e.g., alignment with NIST 800-160)
Large Business (250-999 staff) / BLS Firm Size Classes 7-8
∙ Defined "secure engineering principles" (e.g., alignment with NIST 800-160)
Enterprise (> 1,000 staff) / BLS Firm Size Class 9
∙ Defined "secure engineering principles" (e.g., alignment with NIST 800-160)
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
Secure Engineering & Architecture (SEA) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include: ▪ Policies, standards & procedures associated with SEA domain capabilities provide limited coverage due to the depth and breadth of the existing documentation. ▪ Security engineering-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 design, build and maintain secure, compliant and resilient solutions.
Level 2 Planned Tracked
Secure Engineering & Architecture (SEA) 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 SEA domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with SEA 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 SEA domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Secure engineering and architecture-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Secure engineering and architecture 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 define entity-specific secure engineering practices to protect the Confidentiality, Integrity, Availability and Safety (CIAS) of the entity's TAASD. ▪ IT and/or cybersecurity personnel align secure engineering practices with the entity's broader IT architecture practices. ▪ IT and/or cybersecurity personnel use secure engineering practices to influence Secure Baseline Configurations (SBC).
Level 3 Well Defined
Secure Engineering & Architecture (SEA) 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 SEA 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 SEA domain capabilities are well-documented and kept current by process owners. ▪ A cybersecurity engineering / architecture team, or similar function, is appropriately staffed and supported to implement and maintain RSK domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of secure engineering management operations (e.g., project 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 SEA 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). ▪ Secure Baseline Configurations (SBC) enforce the secure engineering principles on all applicable Technology Assets, Applications and/or Services (TAAS). ▪ An implemented and operational capability exists to achieve resilience requirements in normal and adverse situations.
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
|
Standardized Terminology
Description
Mechanisms exist to standardize technology and process terminology to reduce confusion amongst groups and departments.
Possible Solutions & Considerations
Micro-Small Business (<10 staff) / BLS Firm Size Classes 1-2
∙ Follow secure coding basics when developing software
Small Business (10-49 staff) / BLS Firm Size Classes 3-4
∙ Secure coding guidelines for developers ∙ Basic security review before release
Medium Business (50-249 staff) / BLS Firm Size Classes 5-6
∙ Formal security engineering principles ∙ Secure design patterns ∙ Threat modeling
Large Business (250-999 staff) / BLS Firm Size Classes 7-8
∙ Enterprise security engineering program ∙ Formal threat modeling ∙ Security architecture standards
Enterprise (> 1,000 staff) / BLS Firm Size Class 9
∙ Enterprise security architecture framework (SABSA) ∙ Formal threat modeling program ∙ Security design patterns library
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
Secure Engineering & Architecture (SEA) 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 SEA domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with SEA 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 SEA domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Secure engineering and architecture-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Secure engineering and architecture 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 define entity-specific secure engineering practices to protect the Confidentiality, Integrity, Availability and Safety (CIAS) of the entity's TAASD. ▪ IT and/or cybersecurity personnel align secure engineering practices with the entity's broader IT architecture practices. ▪ IT and/or cybersecurity personnel use secure engineering practices to influence Secure Baseline Configurations (SBC).
Level 3 Well Defined
Cybersecurity & Data Protection Governance (GOV) 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 GOV 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 GOV domain capabilities are well-documented and kept current by process owners. ▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, is appropriately staffed and supported to implement and maintain GOV 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). ▪ Technology is leveraged to enhance the efficiency and accuracy of governance, risk management and compliance operations (e.g., GRC platform). ▪ An implemented and operational capability exists to standardize technology and process terminology to reduce confusion amongst groups and departments.
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.
|
|