+Strategic Plan & Objectives
|
Strategic Plan & Objectives
Description
Mechanisms exist to establish a:
(1) Strategic security, compliance and resilience-specific business plan; and
(2) Set of objectives to achieve that plan.
Possible Solutions & Considerations
Micro-Small Business (<10 staff) / BLS Firm Size Classes 1-2
∙ Include security tasks in project plans
Small Business (10-49 staff) / BLS Firm Size Classes 3-4
∙ Security requirements in project planning
∙ Project security checklist
Medium Business (50-249 staff) / BLS Firm Size Classes 5-6
∙ Documented cybersecurity and data protection-specific business plan
Large Business (250-999 staff) / BLS Firm Size Classes 7-8
∙ Documented cybersecurity and data protection-specific business plan
Enterprise (> 1,000 staff) / BLS Firm Size Class 9
∙ Documented cybersecurity and data protection-specific business plan
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
Project & Resource Management (PRM) 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 PRM domain capabilities are formally documented and centrally-managed by the entity.
▪ Standardized Operating Procedures (SOP) associated with PRM 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 PRM domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD).
▪ Project & Resource Management -related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines).
▪ Project & Resource Management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel.
▪ The Chief Information Officer (CIO), or similar function, analyzes the organization's business strategy and prioritizes the objectives and resourcing of the security function, based on broader business requirements.
▪ A Project Management Office (PMO), or project management function, enables the implementation of cybersecurity and data protection-related resource planning controls across the System Development Lifecycle (SDLC) for all high-value projects.
▪ Quarterly Business Review (QBR), or similar status reporting, exists to provide recurring reports on the state of the cybersecurity and data protection program.
Level 3 Well Defined
Project & Resource Management (PRM) 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 PRM 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 PRM domain capabilities are well-documented and kept current by process owners.
▪ A Project Management Office (PMO), or similar function, is appropriately staffed and supported to implement and maintain PRM domain capabilities.
▪ Technology is leveraged to enhance the efficiency and accuracy of project and resource management operations (e.g., project 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 PRM 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).
▪ The Chief Information Officer (CIO), or similar function, analyzes the organization's business strategy and prioritizes the objectives and resourcing of the security function, based on broader business requirements.
▪ An implemented and operational capability exists to establish a:
(1) Strategic security, compliance and resilience-specific business plan; and
(2) Set of objectives to achieve that plan.
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.
1. Apžvalga
1.1 Nuorodos
1.2 Nustatyti reikalavimai
1.3 Susiję teisės aktai
2. Nustatyti reikalavimai
Reikalavimai
| Šaltinis |
Reikalavimas |
3. Susiję teisės aktai
Teisės aktai
| Šaltinis |
Reguliavimas |
|
EULAW
|
7 straipsnis IRT sistemos, protokolai ir priemonės
Siekdami mažinti ir valdyti IRT riziką, finansų sektoriaus subjektai naudoja ir nuolat atnaujina IRT sistemas, protokolus ir priemones, kurie:
|
|
EULAW
|
2 straipsnis Bendrieji IRT saugumo politikos, procedūrų, protokolų ir priemonių elementai
-
|
|
EULAW
|
3 straipsnis IRT rizikos valdymas
3 straipsnis
Finansų sektoriaus subjektai parengia, dokumentuoja ir įgyvendina IRT rizikos valdymo politiką ir procedūras, apimančias visus šiuos elementus:
a)
nuorodą į patvirtintą priimtiną IRT rizikos lygį, nustatytą pagal Reglamento (ES) 2022/2554 6 straipsnio 8 dalies b punktą;
b)
IRT rizikos vertinimo procedūrą ir metodiką, kuriose nustatomi:
i)
pažeidžiamumai ir grėsmės, darantys ar galintys daryti poveikį palaikomoms veiklos funkcijoms, šias funkcijas palaikančioms IRT sistemoms ir IRT turtui;
ii)
kiekybiniai ar kokybiniai rodikliai, pagal kuriuos vertinamas poveikis ir i punkte nurodytų pažeidžiamumų ir grėsmių tikimybė;
c)
procedūrą, pagal kurią identifikuojamos, įgyvendinamos ir dokumentuojamos veiksmų su IRT rizika priemonės, taikomos identifikuotai ir įvertintai IRT rizikai, įskaitant veiksmų su IRT rizika priemones, kurios yra būtinos, kad IRT rizika neviršytų a punkte nurodytos priimtinos rizikos lygio;
d)
dėl liekamosios IRT rizikos, kuri vis dar kyla įgyvendinus c punkte nurodytas veiksmų su IRT rizika priemones:
i)
tos liekamosios IRT rizikos identifikavimo nuostatas;
ii)
priskirtus vaidmenis ir pareigas, susijusius su:
(1)
liekamosios IRT rizikos, viršijančios finansų sektoriaus subjekto priimtinos rizikos lygį, nurodytą a punkte, pripažinimu;
(2)
peržiūros procesu, nurodytu šio d punkto iv papunktyje;
iii)
pripažintos liekamosios IRT rizikos aprašo, be kita ko, nurodant tos rizikos priėmimo pagrindimą, parengimą;
iv)
pripažintos liekamosios IRT rizikos peržiūros bent kartą per metus nuostatas, įskaitant:
1.
bet kokių liekamosios IRT rizikos pokyčių nustatymą;
2.
turimų poveikio mažinimo priemonių vertinimą;
3.
vertinimą, ar liekamosios IRT rizikos pripažinimą pagrindžiančios priežastys vis dar aktualios ir egzistuoja peržiūros metu;
e)
nuostatas dėl stebėsenos, susijusios su:
i)
visais IRT rizikos ir kibernetinių grėsmių aplinkos pokyčiais;
ii)
vidaus ir išorės pažeidžiamumais ir grėsmėmis;
iii)
finansų sektoriaus subjekto IRT rizika, kai ta stebėsena sudaro sąlygas greitai aptikti pokyčius, galinčius daryti poveikį subjekto IRT rizikos profiliui;
f)
nuostatas dėl proceso, kuriuo užtikrinama, kad būtų atsižvelgta į visus finansų sektoriaus subjekto veiklos strategijos ir skaitmeninės veiklos atsparumo strategijos pokyčius.
Taikant pirmos pastraipos c punktą, tame punkte nurodyta procedūra užtikrinama:
a)
įgyvendinamų veiksmų su IRT rizika priemonių veiksmingumo stebėsena;
b)
įvertinimas, ar neviršijamas nustatytas finansų sektoriaus subjekto priimtinos rizikos lygis;
c)
įvertinimas, ar finansų sektoriaus subjektas ėmėsi veiksmų, kad prireikus tas priemones pakoreguotų ar patobulintų.
|
|
EULAW
|
6 straipsnis IRT rizikos valdymo sistema
-
|
|
EULAW
|
6 straipsnis 8
8. Į IRT rizikos valdymo sistemą įtraukiama skaitmeninės veiklos atsparumo strategija, kurioje nustatoma, kaip sistema turi būti įgyvendinama. Tuo tikslu skaitmeninės veiklos atsparumo strategija apima IRT rizikos mažinimo ir konkrečių IRT tikslų įgyvendinimo metodus:
|
a)
|
paaiškinama, kaip IRT rizikos valdymo sistema prisidedama prie finansų sektoriaus subjekto veiklos strategijos ir tikslų;
|
|
b)
|
nustatomas priimtinos IRT rizikos lygmuo, atsižvelgiant į finansų sektoriaus subjekto norimą prisiimti riziką, ir analizuojamas priimtinas IRT sutrikdymo poveikis;
|
|
c)
|
nustatomi aiškūs informacijos saugumo tikslai, įskaitant pagrindinius veiklos rezultatų rodiklius ir pagrindinius rizikos parametrus;
|
|
d)
|
paaiškinama IRT bazinė architektūra ir visi pakeitimai, reikalingi konkretiems veiklos tikslams pasiekti;
|
|
e)
|
nurodomi įvairūs mechanizmai, įdiegti siekiant aptikti su IRT susijusius incidentus, užkirsti kelią jų poveikiui ir nuo jo apsisaugoti;
|
|
f)
|
nurodoma esama skaitmeninės veiklos atsparumo padėtis remiantis didelių su IRT susijusių incidentų, apie kuriuos pranešta, skaičiumi ir prevencinių priemonių veiksmingumas;
|
|
g)
|
įgyvendinamas skaitmeninės veiklos atsparumo testavimas pagal šio reglamento IV skyrių;
|
|
h)
|
nurodoma komunikacijos strategija su IRT susijusių incidentų, kuriuos atskleisti reikalaujama pagal 14 straipsnį, atveju.
|
|
Susietos užduotys
- 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.
|