+52 straipsnis Procedūra
---+52 straipsnis 1.
---+52 straipsnis 2.
---+52 straipsnis 3.
---+52 straipsnis 4.
---+52 straipsnis 5.
---+52 straipsnis 6.

52 straipsnis Procedūra

-

1. Apžvalga

,
52 straipsnis 1.
Jei bendrosios paskirties DI modelis atitinka 51 straipsnio 1 dalies a punkte nurodytą sąlygą, atitinkamas tiekėjas nedelsdamas ir bet kuriuo atveju per dvi savaites po to, kai reikalavimas įvykdomas arba sužinoma, kad jis bus įvykdytas, praneša apie tai Komisijai. Tame pranešime pateikiama informacija, būtina įrodyti, kad atitinkamas reikalavimas įvykdytas. Jei Komisija sužino apie bendrosios paskirties DI modelį, kuris kelia sisteminę riziką, ir apie kurį jai nebuvo pranešta, ji gali nuspręsti jį priskirti sisteminės rizikos modeliams.
52 straipsnis 2.
Bendrosios paskirties DI modelio, atitinkančio 51 straipsnio 1 dalies a punkte nurodytą sąlygų, tiekėjas kartu su pranešimu gali pateikti pakankamai pagrįstų argumentų, kad įrodytų, jog bendrosios paskirties DI modelis, nors ir atitinka tą reikalavimą, dėl savo specifinių savybių nekelia sisteminės rizikos, todėl išimties tvarka neturėtų būti priskiriamas sisteminės rizikos bendrosios paskirties DI modeliams.
52 straipsnis 3.
Jei Komisija padaro išvadą, kad pagal 2 dalį pateikti argumentai nėra pakankamai pagrįsti ir atitinkamas tiekėjas nepajėgė įrodyti, kad bendrosios paskirties DI modelis dėl savo specifinių savybių nekelia sisteminės rizikos, ji tuos argumentus atmeta, o bendrosios paskirties DI modelis laikomas sisteminės rizikos bendrosios paskirties DI modeliu.
52 straipsnis 4.
Komisija gali priskirti bendrosios paskirties DI modelį sisteminės rizikos modeliams ex officio arba gavusi kvalifikuotą mokslinės komisijos perspėjimą pagal 90 straipsnio 1 dalies a punktą, remdamasi XIII priede nustatytais kriterijais.

Komisijai suteikiami įgaliojimai pagal 97 straipsnį priimti deleguotuosius aktus, siekiant iš dalies pakeisti XIII priedą, patikslindama ir atnaujindama tame priede išdėstytus kriterijus.
52 straipsnis 5.
Gavusi pagrįstą tiekėjo, kurio bendrosios paskirties DI modelis pagal 4 dalį priskirtas sisteminės rizikos modeliams, prašymą, Komisija atsižvelgia į prašymą ir gali nuspręsti iš naujo įvertinti, ar remiantis XIII priede nustatytais kriterijais šis bendrosios paskirties DI modelis vis dar gali būti laikomas sisteminės rizikos modeliu. Tokiame prašyme nurodomos objektyvios, išsamios ir naujos priežastys, atsiradusios po sprendimo dėl priskyrimo priėmimo. Tiekėjai gali prašyti atlikti pakartotinį vertinimą ne anksčiau kaip praėjus šešiems mėnesiams po sprendimo dėl priskyrimo priėmimo. Jei Komisija, atlikusi pakartotinį vertinimą, nusprendžia, kad atitinkamas modelis turi likti priskirtas sisteminės rizikos bendrosios paskirties DI modeliams, tiekėjai gali prašyti atlikti pakartotinį vertinimą ne anksčiau kaip praėjus šešiems mėnesiams po to sprendimo priėmimo.
52 straipsnis 6.
Komisija užtikrina, kad būtų paskelbtas sisteminės rizikos bendrosios paskirties DI modelių sąrašas, ir nuolat jį atnaujina, nedarant poveikio poreikiui paisyti intelektinės nuosavybės teisių ir verslo informacijos konfidencialumo ar komercinių paslapčių ir juos saugoti pagal Sąjungos ir nacionalinę teisę.

1.1 Nuorodos

1.2 Nustatyti reikalavimai

1.3 Susiję standartai

2. Nustatyti reikalavimai

Reikalavimai

3. Susiję standartai

Standartai
SCF AI & Autonomous Technologies Registration

Description

Mechanisms exist to maintain a current registration for Artificial Intelligence (AI) and Autonomous Technologies (AAT) with the appropriate governing body, as required by statutory or regulatory requirements.

Possible Solutions & Considerations

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

∙ Determine whether any AI use requires registration (e.g., EU AI Act high-risk systems)

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

∙ Track AI registration obligations by jurisdiction in compliance checklist

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

∙ Register high-risk AI systems with relevant authorities as required

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

∙ AI registration compliance program
∙ Track registration requirements by jurisdiction

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

∙ Enterprise AI regulatory compliance platform
∙ Automated registration tracking
∙ EU AI Act database registration compliance

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

Artificial Intelligence and Autonomous Technology (AAT) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include:
▪ Policies, standards & procedures associated with AAT domain capabilities provide limited coverage due to the depth and breadth of the existing documentation.
▪ AAT-related processes are expected to follow the organization's existing processes (e.g., incident response, asset management, change control and risk assessments).
▪ No formal Governance, Risk & Compliance (GRC) team exists to provide AAT oversight, where the Chief Information Officer (CIO), or similar function, governs technology decisions what is acceptable for AAT within the organization.

Level 2 Planned Tracked

Artificial Intelligence and Autonomous Technology (AAT) 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 AAT domain capabilities are formally documented and centrally-managed by the entity.
▪ Standardized Operating Procedures (SOP) associated with AAT 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 AAT domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD).
▪ Artificial Intelligence (AI)-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines).
▪ Asset management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel.
▪ AAT is regarded as a technology and governed by the entity's existing IT governance practices.
▪ No formal Governance, Risk & Compliance (GRC) team exists to provide oversight of AAT-related activities. GRC functions are assigned to existing IT and/or cybersecurity personnel.

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 maintain a current registration for AAT with the appropriate governing body, as required by statutory or regulatory requirements.

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 AI & Autonomous Technologies Registration

Description

Mechanisms exist to maintain a current registration for Artificial Intelligence (AI) and Autonomous Technologies (AAT) with the appropriate governing body, as required by statutory or regulatory requirements.

Possible Solutions & Considerations

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

∙ Determine whether any AI use requires registration (e.g., EU AI Act high-risk systems)

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

∙ Track AI registration obligations by jurisdiction in compliance checklist

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

∙ Register high-risk AI systems with relevant authorities as required

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

∙ AI registration compliance program
∙ Track registration requirements by jurisdiction

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

∙ Enterprise AI regulatory compliance platform
∙ Automated registration tracking
∙ EU AI Act database registration compliance

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

Artificial Intelligence and Autonomous Technology (AAT) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include:
▪ Policies, standards & procedures associated with AAT domain capabilities provide limited coverage due to the depth and breadth of the existing documentation.
▪ AAT-related processes are expected to follow the organization's existing processes (e.g., incident response, asset management, change control and risk assessments).
▪ No formal Governance, Risk & Compliance (GRC) team exists to provide AAT oversight, where the Chief Information Officer (CIO), or similar function, governs technology decisions what is acceptable for AAT within the organization.

Level 2 Planned Tracked

Artificial Intelligence and Autonomous Technology (AAT) 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 AAT domain capabilities are formally documented and centrally-managed by the entity.
▪ Standardized Operating Procedures (SOP) associated with AAT 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 AAT domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD).
▪ Artificial Intelligence (AI)-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines).
▪ Asset management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel.
▪ AAT is regarded as a technology and governed by the entity's existing IT governance practices.
▪ No formal Governance, Risk & Compliance (GRC) team exists to provide oversight of AAT-related activities. GRC functions are assigned to existing IT and/or cybersecurity personnel.

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 maintain a current registration for AAT with the appropriate governing body, as required by statutory or regulatory requirements.

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.