+92 straipsnis Įgaliojimai atlikti vertinimus
---+92 straipsnis 1.
---+92 straipsnis 2.
---+92 straipsnis 3.
---+92 straipsnis 4.
---+92 straipsnis 5.
---+92 straipsnis 6.
---+92 straipsnis 7.

92 straipsnis Įgaliojimai atlikti vertinimus

-

1. Apžvalga

,
92 straipsnis 1.

DI tarnyba, pasikonsultavusi su Valdyba, gali atlikti atitinkamo bendrosios paskirties DI modelio vertinimus:

a) 

kad įvertintų, kaip tiekėjas vykdo pareigas pagal šį reglamentą, kai pagal 91 straipsnį surinkta informacija yra nepakankama, arba

b) 

kad ištirtų sisteminę riziką Sąjungos lygmeniu, susijusią su sisteminės rizikos bendrosios paskirties DI modeliais, visų pirma remiantis mokslinės komisijos kvalifikuotu perspėjimu pagal 90 straipsnio 1 dalies a punktą.
92 straipsnis 2.
Komisija gali nuspręsti paskirti nepriklausomus ekspertus vertinimams atlikti jos vardu, įskaitant ekspertus iš mokslinės komisijos, sudarytos pagal 68 straipsnį. Šiai užduočiai atlikti paskirti nepriklausomi ekspertai turi atitikti 68 straipsnio 2 dalyje išdėstytus kriterijus.
92 straipsnis 3.
1 dalies tikslais Komisija gali prašyti prieigos prie atitinkamo bendrosios paskirties DI modelio per API arba kitas tinkamas technines priemones ir įrankius, įskaitant pirminį kodą.
92 straipsnis 4.
Prašyme suteikti prieigą prie informacijos nurodomas prašymo teisinis pagrindas, tikslas bei priežastys ir nustatomas laikotarpis, per kurį prieiga turi būti suteikta, taip pat nurodomos 101 straipsnyje numatytos baudos už prieigos nesuteikimą.
92 straipsnis 5.
Atitinkamo bendrosios paskirties DI modelio tiekėjai arba jo atstovas suteikia prašomą informaciją. Juridinių asmenų, bendrovių ar įmonių atveju arba tais atvejais, kai tiekėjas neturi juridinio asmens statuso, prašomą prieigą atitinkamo bendrosios paskirties DI modelio tiekėjo vardu suteikia asmenys, teisės aktais arba jų nuostatais įgalioti jiems atstovauti.
92 straipsnis 6.
Komisija priima įgyvendinimo aktus, kuriais nustatoma išsami vertinimų tvarka ir sąlygos, įskaitant išsamią nepriklausomų ekspertų įtraukimo tvarką ir jų atrankos procedūrą. Tie įgyvendinimo aktai priimami laikantis 98 straipsnio 2 dalyje nurodytos nagrinėjimo procedūros.
92 straipsnis 7.
Prieš prašydama prieigos prie atitinkamo bendrosios paskirties DI modelio, DI tarnyba gali pradėti struktūrinį dialogą su bendrosios paskirties DI modelio tiekėju, kad surinktų daugiau informacijos apie modelio vidaus bandymus, sisteminės rizikos prevencijai skirtas vidaus apsaugos priemones ir kitas vidaus procedūras bei priemones, kurių tiekėjas ėmėsi tokiai rizikai sumažinti.

1.1 Nuorodos

1.2 Nustatyti reikalavimai

1.3 Susiję standartai

2. Nustatyti reikalavimai

Reikalavimai

3. Susiję standartai

Standartai
SCF Legal Assessment of Investigative Inquires

Description

Mechanisms exist to determine whether a government agency has an applicable and valid legal basis to request data from the organization and what further steps need to be taken, if necessary.

Possible Solutions & Considerations

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

∙ Legal review

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

∙ Legal review

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

∙ Legal review

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

∙ Legal review

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

∙ Legal review

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

Compliance (CPL) 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 CPL domain capabilities are formally documented and centrally-managed by the entity.
▪ Standardized Operating Procedures (SOP) associated with CPL 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 CPL domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD).
▪ Compliance management controls-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines).
▪ Compliance management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel.
▪ External compliance requirements for cybersecurity and data privacy are identified and documented, based on applicable laws, regulations and contractual obligations.
▪ IT and/or cybersecurity personnel work with the organization's legal counsel for guidance on how to respond to legal orders (e.g., court orders and investigations).

Level 3 Well Defined

Compliance (CPL) 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 CPL 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 CPL 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 CPL domain capabilities.
▪ Technology is leveraged to enhance the efficiency and accuracy of governance, risk management and compliance 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 CPL 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 determine whether a government agency has an applicable and valid legal basis to request data from the organization and what further steps need to be taken, if necessary.

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 Legal Assessment of Investigative Inquires

Description

Mechanisms exist to determine whether a government agency has an applicable and valid legal basis to request data from the organization and what further steps need to be taken, if necessary.

Possible Solutions & Considerations

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

∙ Legal review

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

∙ Legal review

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

∙ Legal review

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

∙ Legal review

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

∙ Legal review

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

Compliance (CPL) 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 CPL domain capabilities are formally documented and centrally-managed by the entity.
▪ Standardized Operating Procedures (SOP) associated with CPL 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 CPL domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD).
▪ Compliance management controls-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines).
▪ Compliance management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel.
▪ External compliance requirements for cybersecurity and data privacy are identified and documented, based on applicable laws, regulations and contractual obligations.
▪ IT and/or cybersecurity personnel work with the organization's legal counsel for guidance on how to respond to legal orders (e.g., court orders and investigations).

Level 3 Well Defined

Compliance (CPL) 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 CPL 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 CPL 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 CPL domain capabilities.
▪ Technology is leveraged to enhance the efficiency and accuracy of governance, risk management and compliance 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 CPL 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 determine whether a government agency has an applicable and valid legal basis to request data from the organization and what further steps need to be taken, if necessary.

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.