+Член 80 Процедура за работа със системи с ИИ, класифицирани от доставчика като непредставляващи високорискови при прилагане на приложение III
---+Член 80 1.
---+Член 80 2.
---+Член 80 3.
---+Член 80 4.
---+Член 80 5.
---+Член 80 6.
---+Член 80 7.
---+Член 80 8.

Член 80 Процедура за работа със системи с ИИ, класифицирани от доставчика като непредставляващи високорискови при прилагане на приложение III

-

1. Преглед

,
Член 80 1.
Когато орган за надзор на пазара има достатъчно основания да счита, че дадена система с ИИ, класифицирана от доставчика като непредставляваща високорискова съгласно член 6, параграф 3, в действителност е високорискова, органът за надзор на пазара извършва оценка на съответната система с ИИ по отношение на класифицирането ѝ като високорискова система с ИИ въз основа на условията, посочени в член 6, параграф 3 и насоките на Комисията.
Член 80 2.
Когато в хода на тази оценка органът за надзор на пазара установи, че съответната система с ИИ е високорискова, той без ненужно забавяне изисква от съответния доставчик да предприеме всички необходими действия, за да приведе системата с ИИ в съответствие с изискванията и задълженията, установени в настоящия регламент, както и да предприеме подходящи коригиращи действия в срока, определен от органа за надзор на пазара.
Член 80 3.
Когато органът за надзор на пазара счита, че използването на съответната система с ИИ не е ограничено само до националната му територия, той информира без ненужно забавяне Комисията и другите държави членки за резултатите от оценяването и за действията, които е изискал да бъдат предприети от доставчика.
Член 80 4.
Доставчикът гарантира, че са предприети всички необходими действия за привеждане на системата с ИИ в съответствие с изискванията и задълженията, установени в настоящия регламент. Когато доставчикът на система с ИИ не приведе системата с ИИ в съответствие с тези изисквания и задължения в рамките на срока, посочен в параграф 2 от настоящия член, на доставчика се налагат глоби и имуществени санкции в съответствие с член 99.
Член 80 5.
Доставчикът осигурява предприемането на подходящи коригиращи действия по отношение на всички съответни системи с ИИ, които е предоставил на пазара на Съюза.
Член 80 6.
Когато доставчикът на съответната система с ИИ не предприеме подходящи коригиращи действия в срока, посочен в параграф 2 от настоящия член, се прилага член 79, параграфи 5 – 9.
Член 80 7.
Когато в хода на оценката съгласно параграф 1 от настоящия член органът за надзор на пазара установи, че системата с ИИ е била неправилно класифицирана от доставчика като непредставляваща високорискова, за да се заобиколи прилагането на изискванията в глава III, раздел 2, на доставчика се налагат глоби и имуществени санкции в съответствие с член 99.
Член 80 8.
При упражняване на правомощието си за мониторинг на прилагането на настоящия член и в съответствие с член 11 от Регламент (ЕС) 2019/1020 органите за надзор на пазара могат да извършват подходящи проверки, като вземат предвид по-специално информацията, съхранявана в базата данни на ЕС, посочена в член 71 от настоящия регламент.

1.1 Препратки

1.2 Идентифицирани изисквания

1.3 Свързани стандарти

2. Идентифицирани изисквания

Изисквания

3. Свързани стандарти

Стандарти
SCF Non-Conformity Corrective Action

Description

Mechanisms exist to implement corrective action to remediate instances of non-conformity with applicable statutory, regulatory, and/or contractual compliance obligations.

Possible Solutions & Considerations

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

∙ Corrective action log (spreadsheet)
∙ Documented remediation plans for audit findings

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

∙ Corrective action register with remediation tracking
∙ Management review of open findings

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

∙ Formal corrective action plan process
∙ GRC platform for finding tracking and remediation
∙ Management review of open findings

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

∙ Enterprise corrective action management program
∙ GRC platform with workflow-driven remediation tracking
∙ Executive reporting on open findings

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

∙ Enterprise GRC platform for corrective action management
∙ Automated finding tracking and escalation workflows
∙ Board-level reporting on material findings

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

Compliance (CPL) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include:
▪ Policies, standards & procedures associated with CPL domain capabilities provide limited coverage due to the depth and breadth of the existing documentation.
▪ Compliance management-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
▪ Compliance efforts are narrowly-limited to certain compliance requirements.
▪ IT and/or cybersecurity personnel use an informal process to govern statutory, regulatory and contractual compliance obligations.

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.

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 take corrective action to remediate instances of non-conformity with applicable statutory, regulatory, and/or contractual compliance obligations.

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 Non-Conformity Corrective Action

Description

Mechanisms exist to implement corrective action to remediate instances of non-conformity with applicable statutory, regulatory, and/or contractual compliance obligations.

Possible Solutions & Considerations

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

∙ Corrective action log (spreadsheet)
∙ Documented remediation plans for audit findings

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

∙ Corrective action register with remediation tracking
∙ Management review of open findings

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

∙ Formal corrective action plan process
∙ GRC platform for finding tracking and remediation
∙ Management review of open findings

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

∙ Enterprise corrective action management program
∙ GRC platform with workflow-driven remediation tracking
∙ Executive reporting on open findings

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

∙ Enterprise GRC platform for corrective action management
∙ Automated finding tracking and escalation workflows
∙ Board-level reporting on material findings

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

Compliance (CPL) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include:
▪ Policies, standards & procedures associated with CPL domain capabilities provide limited coverage due to the depth and breadth of the existing documentation.
▪ Compliance management-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
▪ Compliance efforts are narrowly-limited to certain compliance requirements.
▪ IT and/or cybersecurity personnel use an informal process to govern statutory, regulatory and contractual compliance obligations.

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.

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 take corrective action to remediate instances of non-conformity with applicable statutory, regulatory, and/or contractual compliance obligations.

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.