+Artikolu 30 2
|
Artikolu 30 2
2. L-arranġamenti kuntrattwali dwar l-użu ta’ servizzi tal-ICT għandhom jinkludu mill-inqas l-elementi li ġejjin:
|
(a)
|
deskrizzjoni ċara u kompleta tal-funzjonijiet u s-servizzi kollha tal-ICT li għandhom jiġu pprovduti mill-fornitur terz ta’ servizz tal-ICT, li tindika jekk huwiex permess is-sottokuntrattar ta’ servizz tal-ICT li jappoġġja funzjoni kritika jew importanti, jew partijiet materjali tiegħu u, f’dak il-każ, il-kondizzjonijiet li japplikaw għal tali sottokuntrattar;
|
|
(b)
|
il-postijiet, jiġifieri r-reġjuni u l-pajjiżi, fejn iridu jiġu pprovduti l-funzjonijiet u s-servizzi tal-ICT kuntrattati jew sottokuntrattati u fejn id-data trid tiġi pproċessata, inkluż fejn ser jinħażnu, u r-rekwiżit li l-fornitur terz ta’ servizzi tal-ICT jinnotifika lill-entità finanzjarja minn qabel jekk ikun biħsiebu jibdel il-postijiet tal-ħażna;
|
|
(c)
|
dispożizzjonijiet dwar id-disponibbiltà, l-awtentiċità, l-integrità u l-kunfidenzjalità fir-rigward tal-protezzjoni tad-data, inkluż id-data personali;
|
|
(d)
|
dispożizzjonijiet dwar l-iżgurar tal-aċċess, l-irkupru u r-ritorn f’format faċilment aċċessibbli tad-data personali u mhux personali pproċessata mill-entità finanzjarja fil-każ tal-insolvenza, ir-riżoluzzjoni jew il-waqfien tal-operat tal-fornitur terz ta’ servizzi tal-ICT, jew fil-każ tat-terminazzjoni tal-arranġamenti kuntrattwali;
|
|
(e)
|
deskrizzjonijiet tal-livell ta’ servizz, inkluż aġġornamenti u reviżjonijiet tiegħu[…]
|
|
(f)
|
l-obbligu tal-fornitur terz ta’ servizzi tal-ICT li jipprovdi assistenza lill-entità finanzjarja mingħajr kost addizzjonali, jew b’kost li jiġi ddeterminat ex ante, meta jseħħ inċident tal-ICT li jkun relatat mas-servizz tal-ICT ipprovdut lill-entità finanzjarja;
|
|
(g)
|
l-obbligu tal-fornitur terz ta’ servizzi tal-ICT li jikkoopera bis-sħiħ mal-awtoritajiet kompetenti u l-awtoritajiet ta’ riżoluzzjoni tal-entità finanzjarja, inklużi persuni maħtura minnhom;
|
|
(h)
|
id-drittijiet ta’ terminazzjoni u l-perjodi minimi ta’ avviż għat-terminazzjoni tal-arranġamenti kuntrattwali, f’konformità mal-aspettattivi tal-awtoritajiet kompetenti u l-awtoritajiet ta’ riżoluzzjoni;
|
|
(i)
|
il-kondizzjonijiet għall-parteċipazzjoni ta’ fornituri terzi ta’ servizzi tal-ICT fil-programmi ta’ sensibilizzazzjoni dwar is-sigurtà tal-ICT tal-entitajiet finanzjarji u fis-sessjonijiet ta’-taħriġ dwar ir-reżiljenza operazzjonali diġitali f’konformità mal-Artikolu 13(6).
|
1. Ħarsa ġenerali
| Titlu |
Regolamentazzjoni |
,
1.1 Referenzi
1.2 Rekwiżiti identifikati
1.3 Standards relatati
2. Rekwiżiti identifikati
3. Standards relatati
Standards
| Sors |
Rekwiżit |
|
NOREA
|
Termination Rights and Conditions
Define explicit termination rights including significant breaches of laws, regulations, or contract terms, material changes in third-party risks, demonstrated ICT weaknesses, and regulator oversight constraints. Set provisions for ensuring access, recovery, and return of data in an easily accessible format in cases of termination, insolvency, resolution, or discontinuation of the service provider's business operations.
|
|
NOREA
|
Service Level Management
Define clear and measurable service level descriptions outlining expected performance and quality standards. Ensure that the service provider provides a comprehensive description of all functions and ICT services that are offered, including any sub-contracting arrangements. Establish arrangements ensuring appropriate levels of data protection in line with regulatory requirements.
|
|
NOREA
|
Service Locations and Data Processing
Specify service locations and data processing sites. Require timely notification of any intended changes to these locations.
|
|
NOREA
|
Cooperation in Incident Response
Oblige the ICT third-party service provider to fully cooperate with the regulator and provide necessary assistance in the event of an incident related to the provided service.
|
|
NOREA
|
Participation in Security Awareness Programs
Specify conditions for the participation of the service provider in security awareness and resilience programs/trainings.
|
|
SCF
|
Security, Compliance & Resilience Outsourcing Limitations
Description
Mechanisms exist to ensure organizations involved in developing, implementing and/or maintaining Technology Assets, Applications and/or Services (TAAS) provide assurance of internal oversight capabilities that demonstrate:
(1) Governance of internal controls;
(2) Risk management, including analysis and mitigation activities; and
(3) Compliance with applicable laws, regulations and contractual obligations.
Possible Solutions & Considerations
Micro-Small Business (<10 staff) / BLS Firm Size Classes 1-2
∙ Vendor due diligence checklist
∙ Third-party security questionnaire (e.g., CAIQ, SIG)
Small Business (10-49 staff) / BLS Firm Size Classes 3-4
∙ Vendor security questionnaire (CAIQ or SIG)
∙ Third-party risk assessment prior to outsourcing
Medium Business (50-249 staff) / BLS Firm Size Classes 5-6
∙ Third-party risk management program
∙ Vendor security assessments with contractual security obligations
∙ Contract security requirements for outsourced functions
Large Business (250-999 staff) / BLS Firm Size Classes 7-8
∙ Third-party risk management (TPRM) program
∙ Vendor SOC 2 and ISO 27001 certification requirements
∙ Contractual security and compliance obligations
Enterprise (> 1,000 staff) / BLS Firm Size Class 9
∙ Enterprise TPRM program with automated vendor risk assessment
∙ Third-party risk ratings (e.g., BitSight, SecurityScorecard)
∙ Contractual oversight and audit rights for outsourced functions
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
Cybersecurity & Data Protection Governance (GOV) 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 GOV domain capabilities are formally documented and centrally-managed by the entity.
▪ Standardized Operating Procedures (SOP) associated with GOV 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 GOV domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD).
▪ Governance-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines).
▪ No formal Governance, Risk & Compliance (GRC) team exists. GRC roles are assigned to existing IT and/or cybersecurity personnel.
Level 3 Well Defined
Third-Party Management (TPM) 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 TPM 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 TPM domain capabilities are well-documented and kept current by process owners.
▪ A procurement team, or similar function, is appropriately staffed and supported to implement and maintain TPM domain capabilities.
▪ Technology is leveraged to enhance the efficiency and accuracy of third-party management operations (e.g., TPRM risk management solution and vendor 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 TPM 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 ensure organizations involved in developing, implementing and/or maintaining Technology Assets, Applications and/or Services (TAAS) provide assurance of internal oversight capabilities that demonstrate:
(1) Governance of internal controls;
(2) Risk management, including analysis and mitigation activities; and
(3) Compliance with applicable laws, regulations and contractual 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
|
Third-Party Contract Requirements
Description
Mechanisms exist to require contractual requirements for applicable security, compliance and resilience requirements with third-parties, reflecting the organization's needs to protect its Technology Assets, Applications, Services and/or Data (TAASD).
Possible Solutions & Considerations
Micro-Small Business (<10 staff) / BLS Firm Size Classes 1-2
∙ Cybersecurity Supply Chain Risk Management (C-SCRM) program
∙ Data Protection Impact Assessment (DPIA)
∙ Third-party contract requirements for cybersecurity controls
∙ Non-Disclosure Agreements (NDAs)
Small Business (10-49 staff) / BLS Firm Size Classes 3-4
∙ Cybersecurity Supply Chain Risk Management (C-SCRM) program
∙ Data Protection Impact Assessment (DPIA)
∙ Third-party contract requirements for cybersecurity controls
∙ Non-Disclosure Agreements (NDAs)
Medium Business (50-249 staff) / BLS Firm Size Classes 5-6
∙ Cybersecurity Supply Chain Risk Management (C-SCRM) program
∙ Data Protection Impact Assessment (DPIA)
∙ Third-party contract requirements for cybersecurity controls
∙ Non-Disclosure Agreements (NDAs)
Large Business (250-999 staff) / BLS Firm Size Classes 7-8
∙ Cybersecurity Supply Chain Risk Management (C-SCRM) program
∙ Data Protection Impact Assessment (DPIA)
∙ Third-party contract requirements for cybersecurity controls
∙ Non-Disclosure Agreements (NDAs)
Enterprise (> 1,000 staff) / BLS Firm Size Class 9
∙ Cybersecurity Supply Chain Risk Management (C-SCRM) program
∙ Data Protection Impact Assessment (DPIA)
∙ Third-party contract requirements for cybersecurity controls
∙ Non-Disclosure Agreements (NDAs)
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
Third-Party Management (TPM) 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 TPM domain capabilities are formally documented and centrally-managed by the entity.
▪ Standardized Operating Procedures (SOP) associated with TPM 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 TPM domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD).
▪ Third-party management-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.
▪ Procurement practices contractually require ESP to follow secure engineering practices as part of a broader Cybersecurity Supply Chain Risk Management (C-SCRM) initiative.
▪ A formal agreement exists between the organization and applicable third-parties that includes a Non-Disclosure Agreement (NDA) addressing shared sensitive data.
Level 3 Well Defined
Third-Party Management (TPM) 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 TPM 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 TPM domain capabilities are well-documented and kept current by process owners.
▪ A procurement team, or similar function, is appropriately staffed and supported to implement and maintain TPM domain capabilities.
▪ Technology is leveraged to enhance the efficiency and accuracy of third-party management operations (e.g., TPRM risk management solution and vendor 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 TPM 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 require contractual requirements for applicable security, compliance and resilience requirements with third-parties, reflecting the organization's needs to protect its TAASD.
Level 4 Quantitatively Controlled
Third-Party Management (TPM) capabilities, in addition to being standardized across the entity and centrally managed to ensure consistency across Technology Assets, Applications, Services and/or Data (TAASD), efforts are metrics driven to provide sufficient insight for decision makers to predict optimal performance, ensure continued operations and/or identify areas for improvement. Capability criteria associated with this control reasonably expect the following criteria to exist:
▪ Applicable SCR-CMM Level 3 (Well Defined) capabilities are implemented and operational.
▪ Metrics reporting includes quantitative analysis of Key Performance Indicators (KPIs).
▪ Metrics reporting includes quantitative analysis of Key Risk Indicators (KRIs).
▪ Scope of metrics, KPIs and KRIs covers organization-wide cybersecurity and data protection controls, including functions performed by third-parties.
▪ Organizational leadership maintains a formal process to objectively review and respond to metrics, KPIs and KRIs (e.g., monthly or quarterly review).
▪ Based on metrics analysis, process improvement recommendations are submitted for review and are handled in accordance with change control processes.
▪ Business and technical stakeholders are involved in reviewing and approving proposed changes to evolve capabilities.
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.
|
|