+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. Forbhreathnú

Teideal Caighdeán

1.1 Tagairtí

1.2 Ceanglais aitheanta

1.3 Rialacháin ghaolmhara

2. Ceanglais aitheanta

Ceanglais
Foinse Ceanglas

3. Rialacháin ghaolmhara

Rialacháin
Foinse Rialáil
EULAW Airteagal 7 Córais, prótacail agus uirlisí TFC

Chun aghaidh a thabhairt ar riosca TFC agus chun an riosca sin a bhainistiú, bainfidh na heintitis airgeadais úsáid as córais, prótacail agus uirlisí TFC nuashonraithe a bheidh:

EULAW Airteagal 2 Eilimintí ginearálta de bheartais, nósanna imeachta, prótacail agus uirlisí slándála TFC
EULAW Airteagal 3 Bainistíocht riosca TFC

Airteagal 3

Bainistíocht riosca TFC

Déanfaidh eintitis airgeadais beartais agus nósanna imeachta bainistíochta riosca TFC a fhorbairt, a dhoiciméadú agus a chur chun feidhme ina mbeidh na nithe uile seo a leanas:

(a) 

léiriú ar fhormheas an leibhéil lamháltais riosca i leith riosca TFC a leagtar síos i gcomhréir le hAirteagal 6(8), pointe (b), de Rialachán (AE) 2022/2554;

(b) 

nós imeachta agus modheolaíocht chun an measúnú riosca TFC a dhéanamh, lena sainaithnítear:

(i) 

leochaileachtaí agus bagairtí a dhéanann difear, nó a d’fhéadfadh difear a dhéanamh, d’fheidhmeanna gnó a dtacaítear leo, do na córais TFC agus do shócmhainní TFC lena dtacaítear leis na feidhmeanna sin;

(ii) 

na táscairí cainníochtúla nó cáilíochtúla chun tionchar agus dóchúlacht na leochaileachtaí agus na mbagairtí dá dtagraítear i bpointe (i) a thomhas;

(c) 

an nós imeachta chun bearta láimhseála riosca TFC a shainaithint, a chur chun feidhme agus a dhoiciméadú i ndáil leis na rioscaí TFC a shainaithnítear agus a ndéantar measúnú orthu, lena n-áirítear cinneadh na mbeart láimhseála riosca TFC a bhfuil gá leo chun riosca TRC a chur i gcomhréir leis an leibhéal lamháltais riosca dá dtagraítear i bpointe (a);

(d) 

i gcás na rioscaí TFC iarmharacha atá fós ann tar éis chur chun feidhme na mbeart láimhseála riosca TFC dá dtagraítear i bpointe (c):

(i) 

forálacha maidir le sainaithint na rioscaí TFC iarmharacha sin;

(ii) 

róil agus freagrachtaí a shannadh maidir leis na nithe seo a leanas:

(1) 

glacadh le rioscaí TFC iarmharacha a sháraíonn leibhéal lamháltais riosca an eintitis airgeadais dá dtagraítear i bpointe (a);

(2) 

i gcás an phróisis athbhreithnithe dá dtagraítear i bpointe (iv) den phointe seo (d);

(iii) 

fardal de na rioscaí TFC iarmharacha a fhorbairt, lena n-áirítear an t-údar le glacadh leo;

(iv) 

forálacha maidir leis an athbhreithniú, uair amháin sa bhliain ar a laghad, ar na rioscaí TFC iarmharacha a nglactar leo, lena n-áirítear:

(1) 

sainaithint aon athraithe ar na rioscaí TFC iarmharacha;

(2) 

measúnú ar bhearta maolaithe atá ar fáil;

(3) 

measúnú ar cé acu atá nó nach bhfuil na cúiseanna a thugann údar le glacadh leis na rioscaí TFC iarmharacha fós bailí agus infheidhme ar dháta an athbhreithnithe;

(e) 

forálacha maidir le faireachán ar na nithe seo a leanas:

(i) 

aon athrú ar an riosca TFC agus ar an tírdhreach cibearbhagartha;

(ii) 

leochaileachtaí agus bagairtí inmheánacha agus seachtracha;

(iii) 

riosca TFC an eintitis airgeadais lena gcumasaítear brath athruithe go pras a d’fhéadfadh difear a dhéanamh dá phróifíl riosca TFC;

(f) 

forálacha maidir le próiseas lena n-áirithítear go gcuirfear aon athrú ar straitéis gnó agus straitéis athléimneachta digití oibríochtúla an eintitis airgeadais san áireamh.

Chun críocha na chéad fhomhíre, pointe (c), áiritheoidh an nós imeachta dá dtagraítear sa phointe sin:

(a) 

go ndéanfar faireachán ar éifeachtacht na mbeart láimhseála riosca TFC a chuirtear chun feidhme;

(b) 

go ndéanfar measúnú ar cé acu atá nó nach bhfuil leibhéil lamháltais riosca bhunaithe an eintitis airgeadais bainte amach;

(c) 

go ndéanfar measúnú ar cé acu a rinne nó nach ndearna an t-eintiteas airgeadais gníomhaíochtaí chun feabhas a chur ar na bearta sin i gcás inar gá.

EULAW Airteagal 6 Creat bainistíochta riosca TFC
-
EULAW Airteagal 6 8

8.   Beidh straitéis athléimneachta digití oibríochtúla ina leagfar síos an chaoi a gcuirfear an creat chun feidhme mar chuid den chreat bainistíochta riosca TFC. Chuige sin, áireofar sa straitéis athléimneachta digití oibríochtúla na modhanna chun aghaidh a thabhairt ar riosca TFC agus cuspóirí sonracha TFC a bhaint amach mar a leanas:

(a)

an chaoi lena dtacaítear creat bainistíochta riosca TFC le straitéis agus cuspóirí gnó an eintitis airgeadais a mhíniú;

(b)

an leibhéal lamháltais riosca maidir le riosca TFC a leagan síos, i gcomhréir le hinghlacthacht riosca an eintitis airgeadais, agus anailís ar lamháltas tionchair le haghaidh bristeacha TFC;

(c)

cuspóirí soiléire a leagan amach i gcomhair na slándála faisnéise, lena n-áirítear na príomhtháscairí feidhmíochta agus na príomh-mhéadrachtaí riosca;

(d)

míniú a thabhairt ar an ailtireacht tagartha TFC agus ar aon athruithe a bhfuil gá leo chun cuspóirí sonracha gnó a bhaint amach;

(e)

achoimre ar na sásraí éagsúla a cuireadh i bhfeidhm chun teagmhais a bhaineann le TFC a bhrath, a dtionchar a chosc agus cosaint ina choinne a chur ar fáil;

(f)

an staid reatha maidir le hathléimneacht dhigiteach oibríochtúil a léiriú ar bhonn líon na mórtheagmhas a bhaineann le TFC tuairiscithe maille le héifeachtacht na mbeart coiscthe;

(g)

tástáil athléimneachta digití oibríochtúla a chur chun feidhme, i gcomhréir le Caibidil IV den Rialachán seo;

(h)

achoimre a thabhairt ar straitéis cumarsáide i gcás teagmhais a bhaineann le TFC, nach mór a nochtadh i gcomhréir le hAirteagal 14.

Saincheisteanna nasctha

Naisc
Cineál naisc Saincheist
is related to Annual
is related to relative Control Weighting = 08
is related to Process
is related to Identify
is related to SCRM Focus Tier 1 STRATEGIC
is related to SCRM Focus Tier 2 OPERATIONAL
is related to SCRM Focus Tier 3 TACTICAL
blocks Business / Service Interruption
blocks Data Loss / Integrity Compromise
blocks Reduced Operational Productivity
blocks System / Data Compromise (Technical Vector)
blocks System / Data Compromise (Non-Technical Vector)
blocks Exposure from Unaddressed Vulnerabilities
blocks Failure to Support Business / Mission Objectives
blocks Unaddressed Security / Compliance Exposure
blocks Unperformed / Unowned Control Responsibilities
blocks Uncontrolled Internal Security / Privacy Exposure
blocks Uncontrolled Third-Party Security / Privacy Exposure
blocks Lack of oversight of internal controls
blocks Lack of oversight of third-party controls
blocks Loss of Investigative / Evidentiary Capability
blocks Incident Response / Recovery Cost
blocks Third-Party Cybersecurity Compromise / Exposure
blocks Third-Party Physical Security Disruption / Exposure
blocks Sub-Tier / Fourth-Party Supply Chain Exposure
blocks Third-Party Legal / Compliance Exposure
blocks Harm from Unauthorized / Unintended Product or Service Use
blocks Third-Party Dependency Failure
is related to relative Control Weighting = 05
blocks Failure to Achieve Strategic / Mission Objectives
blocks Inability to Demonstrate Due Diligence / Due Care
blocks Unreliable Assurance / Decision Information
blocks Drought & Water Shortage
blocks Earthquakes
blocks Fire & Wildfires
blocks Floods
blocks Hurricanes & Tropical Storms
blocks Landslides & Debris Flow
blocks Pandemic (Disease) Outbreaks
blocks Severe Weather
blocks Space Weather
blocks Thunderstorms & Lightning
blocks Tornadoes
blocks Tsunamis
blocks Volcanoes
blocks Winter Storms & Extreme Cold
blocks Dysfunctional Management Practices
blocks Human Error
blocks Statutory / Regulatory / Contractual Change
blocks Fraud, Corruption and/or Intentional Criminal Conduct
blocks Conflict of Interest (COI) / Undue Influence / Insider Misconduct
blocks Economic Shock / Market Disruption
blocks Workforce Shortage / Loss of Critical Skills / Labor Disruption
blocks OIS-02.03B
blocks SP-01.01B
is blocked by PRM-02 Strategic Plan & Objectives – Assessment Procedure
blocks GV GOVERN
blocks GV.OC-04 Critical objectives, capabilities, and services that external stakeholders depend on or expect from the organization are understood and communicated
blocks GV.RM Risk Management Strategy
blocks GV.OV-01 Cybersecurity risk management strategy outcomes are reviewed to inform and adjust strategy and direction
  • Secure Controls Framework -

    The Secure Controls Framework® (SCF)

    "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.