+User Provisioning & De-Provisioning
---+Change of Roles & Duties
---+Termination of Employment
|
User Provisioning & De-Provisioning
Description
Mechanisms exist to utilize a formal user registration and de-registration process that governs the assignment of access rights.
Possible Solutions & Considerations
Micro-Small Business (<10 staff) / BLS Firm Size Classes 1-2
∙ Documented process for adding/removing user access
Small Business (10-49 staff) / BLS Firm Size Classes 3-4
∙ User provisioning and de-provisioning procedure
∙ Timely removal of access on departure
Medium Business (50-249 staff) / BLS Firm Size Classes 5-6
∙ Formal user lifecycle management process
∙ Provisioning workflows
∙ Timely de-provisioning
Large Business (250-999 staff) / BLS Firm Size Classes 7-8
∙ Enterprise IAM with automated provisioning/de-provisioning (e.g., SailPoint, Saviynt)
Enterprise (> 1,000 staff) / BLS Firm Size Class 9
∙ Enterprise IGA platform (e.g., SailPoint, Saviynt, Microsoft Entra ID Governance)
∙ Automated lifecycle management
∙ Role-based access provisioning
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
Identification & Authentication (IAC) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include:
▪ Policies, standards & procedures associated with IAC domain capabilities provide limited coverage due to the depth and breadth of the existing documentation.
▪ Identity & Access Management (IAM)-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
▪ IAM controls are primarily administrative in nature (e.g., policies & standards) to manage accounts and permissions.
▪ IT and/or cybersecurity personnel identify and implement IAM cybersecurity and data protection controls that are appropriate to address applicable statutory, regulatory and contractual requirements.
Level 2 Planned Tracked
Identification & Authentication (IAC) 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 IAC domain capabilities are formally documented and centrally-managed by the entity.
▪ Standardized Operating Procedures (SOP) associated with IAC 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 IAC domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD).
▪ Identity & Access Management (IAM)-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines) to enforce Logical Access Control (LAC).
▪ IAM may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel to implement Role Based Access Control (RBAC) practices for the management of user, group and system accounts, including privileged accounts.
▪ A directory services technology is used to centrally manage identities and permissions with RBAC. Due to technical or business limitations, asset/process owners are empowered to operate a decentralized access control program for their specific Technology Assets, Applications and/or Services (TAAS) that cannot be integrated into directory services.
▪ Configuration management and IAM functions collaborate to ensure Secure Baseline Configurations (SBC) enforce “least privileges” on TAAS.
▪ IAM restricts the assignment of privileged accounts to entity-defined personnel and/or roles (privilege assignment requires management approval).
Level 3 Well Defined
Identification & Authentication (IAC) 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 IAC 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 IAC domain capabilities are well-documented and kept current by process owners.
▪ An Identity & Access Management (IAM) team, or similar function, is appropriately staffed and supported to implement and maintain IAC domain capabilities.
▪ Technology is leveraged to enhance the efficiency and accuracy of IAM operations (e.g., directory services, Authenticate, Authorize and Audit (AAA) 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 IAC 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 utilize a formal user registration and de-registration process that governs the assignment of access rights.
Level 4 Quantitatively Controlled
Identification & Authentication (IAC) 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.
1. Prezentare generală
| Titlu |
Standard |
|
Change of Roles & Duties
|
Description
Mechanisms exist to revoke user access rights following changes in personnel roles and duties, if no longer necessary or permitted.
Possible Solutions & Considerations
Micro-Small Business (<10 staff) / BLS Firm Size Classes 1-2
∙ Update access rights promptly when roles change
Small Business (10-49 staff) / BLS Firm Size Classes 3-4
∙ Access change procedure for role changes
∙ Notify IT/security of role changes
Medium Business (50-249 staff) / BLS Firm Size Classes 5-6
∙ Formal access modification process for role changes
∙ Timely access updates
Large Business (250-999 staff) / BLS Firm Size Classes 7-8
∙ Enterprise IAM with role-change workflow integration with HR
∙ Automated access adjustment
Enterprise (> 1,000 staff) / BLS Firm Size Class 9
∙ Enterprise IGA platform with HR integration
∙ Automated role-change access adjustments
∙ Access certification
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
Identification & Authentication (IAC) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include:
▪ Policies, standards & procedures associated with IAC domain capabilities provide limited coverage due to the depth and breadth of the existing documentation.
▪ Identity & Access Management (IAM)-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
▪ IAM controls are primarily administrative in nature (e.g., policies & standards) to manage accounts and permissions.
▪ IT and/or cybersecurity personnel identify and implement IAM cybersecurity and data protection controls that are appropriate to address applicable statutory, regulatory and contractual requirements.
▪ Active Directory (AD), or a similar technologies, are used to centrally manage identities and permissions, but asset/process owners are authorized to operate a decentralized access control program for their specific Technology Assets, Applications, Services and/or Data (TAASD).
Level 2 Planned Tracked
Identification & Authentication (IAC) 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 IAC domain capabilities are formally documented and centrally-managed by the entity.
▪ Standardized Operating Procedures (SOP) associated with IAC 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 IAC domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD).
▪ Identity & Access Management (IAM)-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines) to enforce Logical Access Control (LAC).
▪ IAM may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel to implement Role Based Access Control (RBAC) practices for the management of user, group and system accounts, including privileged accounts.
▪ A directory services technology is used to centrally manage identities and permissions with RBAC. Due to technical or business limitations, asset/process owners are empowered to operate a decentralized access control program for their specific Technology Assets, Applications and/or Services (TAAS) that cannot be integrated into directory services.
▪ Configuration management and IAM functions collaborate to ensure Secure Baseline Configurations (SBC) enforce “least privileges” on TAAS.
Level 3 Well Defined
Identification & Authentication (IAC) 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 IAC 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 IAC domain capabilities are well-documented and kept current by process owners.
▪ An Identity & Access Management (IAM) team, or similar function, is appropriately staffed and supported to implement and maintain IAC domain capabilities.
▪ Technology is leveraged to enhance the efficiency and accuracy of IAM operations (e.g., directory services, Authenticate, Authorize and Audit (AAA) 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 IAC 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 revoke user access rights following changes in personnel roles and duties, if no longer necessary or permitted.
Level 4 Quantitatively Controlled
Identification & Authentication (IAC) 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.
|
|
Termination of Employment
|
Description
Mechanisms exist to revoke user access rights in a timely manner, upon termination of employment or contract.
Possible Solutions & Considerations
Micro-Small Business (<10 staff) / BLS Firm Size Classes 1-2
∙ Revoke all access immediately upon employee termination
Small Business (10-49 staff) / BLS Firm Size Classes 3-4
∙ Documented termination procedure with immediate access revocation
Medium Business (50-249 staff) / BLS Firm Size Classes 5-6
∙ Formal termination checklist
∙ Same-day access revocation process
Large Business (250-999 staff) / BLS Firm Size Classes 7-8
∙ Enterprise automated offboarding workflow
∙ HR-to-IAM integration for immediate access revocation
Enterprise (> 1,000 staff) / BLS Firm Size Class 9
∙ Enterprise IGA with automated offboarding
∙ HR system integration
∙ Immediate access revocation across all systems
∙ Exit interview and access audit
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
Identification & Authentication (IAC) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include:
▪ Policies, standards & procedures associated with IAC domain capabilities provide limited coverage due to the depth and breadth of the existing documentation.
▪ Identity & Access Management (IAM)-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
▪ IAM controls are primarily administrative in nature (e.g., policies & standards) to manage accounts and permissions.
▪ IT and/or cybersecurity personnel identify and implement IAM cybersecurity and data protection controls that are appropriate to address applicable statutory, regulatory and contractual requirements.
▪ Active Directory (AD), or a similar technologies, are used to centrally manage identities and permissions, but asset/process owners are authorized to operate a decentralized access control program for their specific Technology Assets, Applications, Services and/or Data (TAASD).
Level 2 Planned Tracked
Identification & Authentication (IAC) 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 IAC domain capabilities are formally documented and centrally-managed by the entity.
▪ Standardized Operating Procedures (SOP) associated with IAC 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 IAC domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD).
▪ Identity & Access Management (IAM)-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines) to enforce Logical Access Control (LAC).
▪ IAM may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel to implement Role Based Access Control (RBAC) practices for the management of user, group and system accounts, including privileged accounts.
▪ A directory services technology is used to centrally manage identities and permissions with RBAC. Due to technical or business limitations, asset/process owners are empowered to operate a decentralized access control program for their specific Technology Assets, Applications and/or Services (TAAS) that cannot be integrated into directory services.
▪ Configuration management and IAM functions collaborate to ensure Secure Baseline Configurations (SBC) enforce “least privileges” on TAAS.
Level 3 Well Defined
Identification & Authentication (IAC) 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 IAC 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 IAC domain capabilities are well-documented and kept current by process owners.
▪ An Identity & Access Management (IAM) team, or similar function, is appropriately staffed and supported to implement and maintain IAC domain capabilities.
▪ Technology is leveraged to enhance the efficiency and accuracy of IAM operations (e.g., directory services, Authenticate, Authorize and Audit (AAA) 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 IAC 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 revoke user access rights in a timely manner, upon termination of employment or contract.
Level 4 Quantitatively Controlled
Identification & Authentication (IAC) 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.
|
1.1 Referințe
1.2 Cerințe identificate
1.3 Reglementări asociate
2. Cerințe identificate
3. Reglementări asociate
Reglementări
| Sursă |
Reglementare |
|
EULAW
|
Articolul 20 Gestionarea identității
|
|
EULAW
|
Articolul 21 Controlul accesului
Articolul 21
Ca parte a controlului pe care îl exercită asupra drepturilor de gestionare a accesului, entitățile financiare elaborează, documentează și pun în aplicare o politică ce conține toate elementele următoare:
(a)
atribuirea drepturilor de acces la activele TIC pe baza principiului necesității de a cunoaște, al necesității de a utiliza și al celor mai mici privilegii, inclusiv pentru accesul la distanță și de urgență;
(b)
separarea sarcinilor pentru a preveni accesul nejustificat la datele critice sau a preveni alocarea combinațiilor de drepturi de acces care ar putea fi utilizate pentru eludarea controalelor;
(c)
o dispoziție privind răspunderea utilizatorului, prin limitarea, în măsura posibilului, a utilizării conturilor de utilizator generice și partajate și prin asigurarea faptului că utilizatorii sunt identificabili pentru acțiunile pe care le efectuează în sistemele TIC în orice moment;
(d)
o dispoziție privind restricțiile de acces la activele TIC, care să stabilească controalele și instrumentele de prevenire a accesului neautorizat;
(e)
proceduri de gestionare a conturilor pentru acordarea, modificarea sau revocarea drepturilor de acces pentru conturile de utilizator și conturile generice, inclusiv pentru conturile de administrator generice, care conțin dispoziții privind toate elementele următoare:
(i)
atribuirea rolurilor și a responsabilităților pentru acordarea, revizuirea și revocarea drepturilor de acces;
(ii)
atribuirea accesului privilegiat, a accesului în situații de urgență și a accesului cu drepturi de administrator pe baza principiului necesității de a utiliza sau ad-hoc pentru toate sistemele TIC;
(iii)
retragerea drepturilor de acces fără întârzieri nejustificate la încetarea contractului de muncă sau atunci când accesul nu mai este necesar;
(iv)
actualizarea drepturilor de acces în cazul în care sunt necesare modificări și cel puțin o dată pe an pentru toate sistemele TIC, altele decât sistemele TIC care sprijină funcții critice sau importante și cel puțin o dată la 6 luni pentru sistemele TIC care sprijină funcții critice sau importante;
(f)
metode de autentificare care includ toate elementele următoare:
(i)
utilizarea unor metode de autentificare proporționale cu clasificarea stabilită în conformitate cu articolul 8 alineatul (1) din Regulamentul (UE) 2022/2554 și cu profilul general de risc al activelor TIC și luând în considerare cele mai avansate practici;
(ii)
utilizarea unor metode de autentificare puternice în conformitate cu cele mai avansate practici și tehnici pentru accesul de la distanță la rețeaua entității financiare, pentru accesul privilegiat și pentru accesul la active TIC care sprijină funcții critice sau importante sau la active TIC accesibile publicului;
(g)
măsuri de control al accesului fizic care includ:
(i)
identificarea și înregistrarea persoanelor fizice autorizate să aibă acces la sedii, centre de date și zone sensibile desemnate identificate de entitatea financiară în care sunt situate activele TIC și informaționale;
(ii)
acordarea drepturilor de acces fizic la activele TIC esențiale numai persoanelor autorizate, în conformitate cu principiul necesității de a cunoaște și al celor mai mici privilegii și ad-hoc;
(iii)
monitorizarea accesului fizic la sedii, centre de date și zone sensibile desemnate identificate de entitatea financiară în care sunt se află activele TIC și/sau informaționale;
(iv)
revizuirea drepturilor fizice de acces pentru a se asigura că se revocă prompt drepturile de acces inutile.
În sensul literei (e) punctul (i), entitățile financiare stabilesc perioada de păstrare, ținând seama de obiectivele în materie de securitate a activității și a informațiilor, de motivele înregistrării evenimentului în jurnal și de rezultatele evaluării riscurilor TIC.
În sensul literei (e) punctul (ii), entitățile financiare utilizează, în măsura posibilului, conturi specifice pentru îndeplinirea sarcinilor administrative legate de sistemele TIC. Atunci când este fezabil și adecvat, entitățile financiare implementează soluții automatizate pentru gestionarea accesului privilegiat.
În sensul literei (g) punctul (i), identificarea și jurnalizarea sunt proporționale cu importanța sediilor, a centrelor de date și a zonelor sensibile desemnate și cu caracterul critic al operațiunilor sau al sistemelor TIC situate în acestea.
În sensul literei (g) punctul (iii), monitorizarea este proporțională cu clasificarea stabilită în conformitate cu articolul 8 alineatul (1) din Regulamentul (UE) 2022/2554 și cu caracterul critic al zonei accesate.
|
|
EULAW
|
Articolul 21 Controlul accesului
Articolul 21
Ca parte a controlului pe care îl exercită asupra drepturilor de gestionare a accesului, entitățile financiare elaborează, documentează și pun în aplicare o politică ce conține toate elementele următoare:
(a)
atribuirea drepturilor de acces la activele TIC pe baza principiului necesității de a cunoaște, al necesității de a utiliza și al celor mai mici privilegii, inclusiv pentru accesul la distanță și de urgență;
(b)
separarea sarcinilor pentru a preveni accesul nejustificat la datele critice sau a preveni alocarea combinațiilor de drepturi de acces care ar putea fi utilizate pentru eludarea controalelor;
(c)
o dispoziție privind răspunderea utilizatorului, prin limitarea, în măsura posibilului, a utilizării conturilor de utilizator generice și partajate și prin asigurarea faptului că utilizatorii sunt identificabili pentru acțiunile pe care le efectuează în sistemele TIC în orice moment;
(d)
o dispoziție privind restricțiile de acces la activele TIC, care să stabilească controalele și instrumentele de prevenire a accesului neautorizat;
(e)
proceduri de gestionare a conturilor pentru acordarea, modificarea sau revocarea drepturilor de acces pentru conturile de utilizator și conturile generice, inclusiv pentru conturile de administrator generice, care conțin dispoziții privind toate elementele următoare:
(i)
atribuirea rolurilor și a responsabilităților pentru acordarea, revizuirea și revocarea drepturilor de acces;
(ii)
atribuirea accesului privilegiat, a accesului în situații de urgență și a accesului cu drepturi de administrator pe baza principiului necesității de a utiliza sau ad-hoc pentru toate sistemele TIC;
(iii)
retragerea drepturilor de acces fără întârzieri nejustificate la încetarea contractului de muncă sau atunci când accesul nu mai este necesar;
(iv)
actualizarea drepturilor de acces în cazul în care sunt necesare modificări și cel puțin o dată pe an pentru toate sistemele TIC, altele decât sistemele TIC care sprijină funcții critice sau importante și cel puțin o dată la 6 luni pentru sistemele TIC care sprijină funcții critice sau importante;
(f)
metode de autentificare care includ toate elementele următoare:
(i)
utilizarea unor metode de autentificare proporționale cu clasificarea stabilită în conformitate cu articolul 8 alineatul (1) din Regulamentul (UE) 2022/2554 și cu profilul general de risc al activelor TIC și luând în considerare cele mai avansate practici;
(ii)
utilizarea unor metode de autentificare puternice în conformitate cu cele mai avansate practici și tehnici pentru accesul de la distanță la rețeaua entității financiare, pentru accesul privilegiat și pentru accesul la active TIC care sprijină funcții critice sau importante sau la active TIC accesibile publicului;
(g)
măsuri de control al accesului fizic care includ:
(i)
identificarea și înregistrarea persoanelor fizice autorizate să aibă acces la sedii, centre de date și zone sensibile desemnate identificate de entitatea financiară în care sunt situate activele TIC și informaționale;
(ii)
acordarea drepturilor de acces fizic la activele TIC esențiale numai persoanelor autorizate, în conformitate cu principiul necesității de a cunoaște și al celor mai mici privilegii și ad-hoc;
(iii)
monitorizarea accesului fizic la sedii, centre de date și zone sensibile desemnate identificate de entitatea financiară în care sunt se află activele TIC și/sau informaționale;
(iv)
revizuirea drepturilor fizice de acces pentru a se asigura că se revocă prompt drepturile de acces inutile.
În sensul literei (e) punctul (i), entitățile financiare stabilesc perioada de păstrare, ținând seama de obiectivele în materie de securitate a activității și a informațiilor, de motivele înregistrării evenimentului în jurnal și de rezultatele evaluării riscurilor TIC.
În sensul literei (e) punctul (ii), entitățile financiare utilizează, în măsura posibilului, conturi specifice pentru îndeplinirea sarcinilor administrative legate de sistemele TIC. Atunci când este fezabil și adecvat, entitățile financiare implementează soluții automatizate pentru gestionarea accesului privilegiat.
În sensul literei (g) punctul (i), identificarea și jurnalizarea sunt proporționale cu importanța sediilor, a centrelor de date și a zonelor sensibile desemnate și cu caracterul critic al operațiunilor sau al sistemelor TIC situate în acestea.
În sensul literei (g) punctul (iii), monitorizarea este proporțională cu clasificarea stabilită în conformitate cu articolul 8 alineatul (1) din Regulamentul (UE) 2022/2554 și cu caracterul critic al zonei accesate.
|
Tichete legate
- Secure Controls Framework -
"The SCF is the Common Controls Framework™ (CCF), the world's most comprehensive cybersecurity and data privacy metaframework - it is also free to use. The entire concept is building secure, compliant and resilient capabilities in the most efficient and cost-effective manner possible.
The SCF is more than just a unified control catalog, since its included content creates a playbook for Governance, Risk & Compliance (GRC) capabilities. Used globally by organizations of every size, the SCF is a robust and scalable solution for security, compliance and resilience controls. As a comprehensive security framework, the SCF maps 1,400+ controls across 200+ laws, regulations, and industry frameworks so you can implement once and comply everywhere.
Like it or not, cybersecurity is a protracted war on an asymmetric battlefield, where the threats are everywhere and as defenders we have to make the effort to work together to help improve cybersecurity and data privacy practices, since we all suffer when massive data breaches occur or when cyber attacks have physical impacts. Hackers share information on attack methods with other hackers, so why shouldn’t the good guys share information on how to best protect an organization? We decided to take action and make a difference, since we feel it is too important to wait for someone else to fix the problems that exist.
The SCF is made up of volunteers, mainly specialists within the cybersecurity profession, who focus on GRC and the cybersecurity side of data privacy. These are auditors, engineers, architects, incident responders, consultants and other specialists who live and breathe these topics on a daily basis. The end product is "expert-derived content" that makes up the SCF." https://securecontrolsframework.com/
Terms & Conditions
The SCF End User License Agreement (EULA) governs the use of the Secure Controls Framework® (SCF) under the Creative Commons Attribution-No Derivatives 4.0 International Public License.
|