+Artikolu 6 Legalità tal-ipproċessar
---+Artikolu 6 1.
---+Artikolu 6 2.
---+Artikolu 6 3.
---+Artikolu 6 4.
|
Artikolu 6 Legalità tal-ipproċessar
-
1. Ħarsa ġenerali
| Titlu |
Regolamentazzjoni |
|
Artikolu 6 1.
|
L-ipproċessar għandu jkun legali biss jekk u safejn mill-inqas ikun japplika wieħed mill-punti li ġejjin:
(a)
is-suġġett tad-data jkun ta l-kunsens għall-ipproċessar ta' data personali tiegħu għal fini speċifiku wieħed jew aktar;
(b)
l-ipproċessar ikun meħtieġ għat-twettiq ta' kuntratt li għalih is-suġġett tad-data huwa parti jew sabiex jittieħdu passi fuq talba tas-suġġett tad-data qabel ma jidħol f'kuntratt;
(c)
l-ipproċessar ikun meħtieġ għall-konformità ma' obbligu legali li għalih huwa soġġett il-kontrollur;
(d)
l-ipproċessar ikun meħtieġ sabiex ikunu protetti l-interessi vitali tas-suġġett tad-data jew ta' persuna fiżika oħra;
(e)
l-ipproċessar ikun meħtieġ għat-twettiq ta' kompitu li jsir fl-interess pubbliku jew fl-eżerċizzju ta' awtorità uffiċjali mogħtija lill-kontrollur;
(f)
l-ipproċessar ikun meħtieġ għall-finijiet tal-interessi leġittimi segwiti mill-kontrollur jew minn parti terza, għajr meta dawn l-interessi jingħelbu mill-interessi jew id-drittijiet u l-libertajiet fundamentali tas-suġġett tad-data li jeħtieġu l-protezzjoni tad-data personali, b'mod partikolari meta s-suġġett tad-data jkun minorenni.
Il-punt (f) tal-ewwel subparagrafu m'għandux japplika għall-ipproċessar li jitwettaq minn awtoritajiet pubbliċi fit-twettiq tal-kompiti tagħhom.
|
|
Artikolu 6 2.
|
L-Istati Membri jistgħu jżommu jew jintroduċu dispożizzjonijiet aktar speċifiċi biex jadattaw l-applikazzjoni tar-regoli ta' dan ir-Regolament fir-rigward ta' pproċessar għal konformità mal-punti (c) u (e) tal-paragrafu 1 billi jiddeterminaw b'mod aktar preċiż rekwiżiti speċifiċi għall-ipproċessar u miżuri oħrajn biex jiġi żgurat ipproċessar legali u ġust inkluż għal sitwazzjonijiet speċifiċi oħrajn ta' pproċessar kif previst fil-Kapitolu IX.
|
|
Artikolu 6 3.
|
Il-bażi għall-ipproċessar imsemmi fil-punti (c) u (e) tal-paragrafu 1 għandha tkun stipulata minn:
(b)
il-liġi tal-Istat Membru li għaliha huwa soġġett il-kontrollur.
Il-fini tal-ipproċessar għandu jkun iddeterminat fdik il-bażi legali jew, fir-rigward tal-ipproċessar imsemmi fil-punt (e) tal-paragrafu 1, għandu jkun meħtieġ għat-twettiq ta' kompitu li jsir fl-interess pubbliku jew fl-eżerċizzju tal-atorità uffiċjali mogħtija lill-kontrollur. Dik il-bażi legali jista' jkun fiha dispożizzjonijiet speċifiċi biex tiġi adattata l-applikazzjoni ta' regoli ta' dan ir-Regolament, inklużi l-kondizzjonijiet ġenerali li jirregolaw il-legalità tal-ipproċessar mill-kontrollur; it-tipi ta' data li huma soġġetti għall-ipproċessar; is-suġġetti tad-data kkonċernati; l-entitajiet li lilhom, jew li għalihom, tista' tiġi żvelata d-data personali; il-limitazzjoni tal-fini; il-perijodi tal-ħażna u attivitajiet ta' pproċessar u proċeduri ta' pproċessar, inklużi miżuri li jiżguraw ipproċessar legali u ġust bħal dawk għal sitwazzjonijiet speċifiċi oħrajn ta' pproċessar kif previst fil-Kapitolu IX. Il-liġi tal-Unjoni jew il-liġi tal-Istat Membru għandha tissodisfa l-objettiv ta' interess pubbliku u tkun proporzjonata mal-għan leġittimu mfittex.
|
|
Artikolu 6 4.
|
Fejn l-ipproċessar għal finijiet differenti minn dak li għalih id-data personali tkun inġabret ma jkunx ibbażat fuq il-kunsens tas-suġġett tad-data jew fuq liġi tal-Unjoni jew ta' Stat Membru li tikkostitwixxi miżura meħtieġa u proporzjonata f'soċjetà demokratika biex tissalvagwardja l-objettivi msemmija fl-Artikolu 23(1), il-kontrollur għandu, sabiex jaċċerta jekk l-ipproċessar għal fini ieħor huwiex kompatibbli mal-fini li għalih tkun inġabret id-data personali inizjalment, jieħu kont, fost l-oħrajn, ta':
(a)
kwalunkwe rabta bejn il-fini li għalih tkun inġabret id-data personali u l-fini tal-ipproċessar ulterjuri li jkun maħsub;
(b)
il-kuntest li fih inġabret id-data personali, b'mod partikolari fir-rigward tar-relazzjoni bejn is-suġġetti tad-data u l-kontrollur;
(c)
in-natura tad-data personali, b'mod partikolari jekk jiġux ipproċessati kategoriji speċjali ta' data personali, skont l-Artikolu 9, jew jekk tiġix ipproċessata data personali relatata ma' kundanni kriminali u reati, skont l-Artikolu 10;
(d)
il-konsegwenzi possibbli għas-suġġetti tad-data tal-ipproċessar ulterjuri maħsub;
(e)
l-eżistenza ta' salvagwardji xierqa, li jistgħu jinkludu kriptaġġ jew psewdonimizzazzjoni.
|
,
1.1 Referenzi
1.2 Rekwiżiti identifikati
1.3 Standards relatati
2. Rekwiżiti identifikati
3. Standards relatati
Standards
| Sors |
Rekwiżit |
|
SCF
|
Data Subject Opt-In Consent
Description
Mechanisms exist to obtain consent from data subjects to opt-in for the following Personal Data (PD) actions:
(1) Collecting;
(2) Receiving;
(3) Processing;
(4) Storing;
(5) Transmitting;
(6) Sharing; and/or
(7) Updating.
Possible Solutions & Considerations
Micro-Small Business (<10 staff) / BLS Firm Size Classes 1-2
∙ Obtain opt-in consent before processing personal data
Small Business (10-49 staff) / BLS Firm Size Classes 3-4
∙ Opt-in consent policy and procedures
Medium Business (50-249 staff) / BLS Firm Size Classes 5-6
∙ Formal opt-in consent program
∙ Consent records management
Large Business (250-999 staff) / BLS Firm Size Classes 7-8
∙ Enterprise consent management platform (e.g., OneTrust, Cookiebot)
∙ Consent audit trail
Enterprise (> 1,000 staff) / BLS Firm Size Class 9
∙ Enterprise consent management platform (e.g., OneTrust, TrustArc)
∙ Granular consent management
∙ Automated consent renewal
∙ Consent audit logs
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
Privacy (PRI) 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 PRI domain capabilities are formally documented and centrally-managed by the entity.
▪ Standardized Operating Procedures (SOP) associated with PRI 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 PRI domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD).
▪ Data privacy management-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines).
▪ Data privacy management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel.
▪ The data privacy program is developed to work with IT and cybersecurity staff to ensure that applicable statutory, regulatory and/or contractual data privacy obligations for Personal Data (PD) are properly identified and implemented.
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 obtain consent from data subjects to opt-in for the following Personal Data (PD) actions:
(1) Collecting;
(2) Receiving;
(3) Processing;
(4) Storing;
(5) Transmitting:
(6) Sharing; and/or
(7) Updating.
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.
|
|