+Threat Intelligence Program
|
Threat Intelligence Program
Description
Mechanisms exist to implement a threat intelligence program that includes a cross-organization information-sharing capability that can influence the development of the system and security architectures, selection of security solutions, monitoring, threat hunting, response and recovery activities.
Possible Solutions & Considerations
Micro-Small Business (<10 staff) / BLS Firm Size Classes 1-2
∙ Subscribe to free threat intelligence feeds (e.g., CISA alerts)
Small Business (10-49 staff) / BLS Firm Size Classes 3-4
∙ CISA alerts subscription
∙ Basic threat awareness program
Medium Business (50-249 staff) / BLS Firm Size Classes 5-6
∙ Threat intelligence program
Large Business (250-999 staff) / BLS Firm Size Classes 7-8
∙ Threat intelligence program
Enterprise (> 1,000 staff) / BLS Firm Size Class 9
∙ Threat intelligence program
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
Threat Management (THR) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include:
▪ Policies, standards & procedures associated with THR domain capabilities provide limited coverage due to the depth and breadth of the existing documentation.
▪ Threat management-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
▪ IT and/or cybersecurity personnel subscribe to threat feeds to maintain situational awareness of emerging threats.
Level 2 Planned Tracked
Threat Management (THR) 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 THR domain capabilities are formally documented and centrally-managed by the entity.
▪ Standardized Operating Procedures (SOP) associated with THR 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 THR domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD).
▪ Threat management-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines).
▪ Threat management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel.
Level 3 Well Defined
Threat Management (THR) 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 THR 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 THR domain capabilities are well-documented and kept current by process owners.
▪ A threat management team, or similar function, is appropriately staffed and supported to implement and maintain THR domain capabilities.
▪ Technology is leveraged to enhance the efficiency and accuracy of threat management operations (e.g., threat intelligence solution and bug bounty 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 THR 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 implement a threat intelligence program that includes a cross-organization information-sharing capability that can influence the development of the system and security architectures, selection of security solutions, monitoring, threat hunting, response and recovery activities.
Level 4 Quantitatively Controlled
Threat Management (THR) 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. Pregled
1.1 Reference
1.2 Utvrđeni zahtjevi
1.3 Povezani propisi
2. Utvrđeni zahtjevi
3. Povezani propisi
Propisi
| Izvor |
Regulativa |
|
EULAW
|
Članak 2. Opći elementi politika, postupaka, protokola i alata za sigurnost IKT-a
-
|
|
EULAW
|
Članak 3. Upravljanje IKT rizicima
Članak 3.
Financijski subjekti izrađuju, dokumentiraju i provode politike i postupke za upravljanje IKT rizicima koji sadržavaju sve sljedeće:
(a)
navođenje odobrenja razine tolerancije na IKT rizik utvrđene u skladu s člankom 6. stavkom 8. točkom (b) Uredbe (EU) 2022/2554;
(b)
postupak i metodologiju za provedbu procjene IKT rizika kojom se utvrđuju:
i.
ranjivosti i prijetnje koje utječu ili mogu utjecati na poslovne funkcije koje se podupiru, IKT sustave i IKT imovinu kojom se te funkcije podupiru;
ii.
kvantitativni ili kvalitativni pokazatelji za mjerenje učinka i vjerojatnosti pojave ranjivosti i prijetnji iz podtočke i.;
(c)
postupak za utvrđivanje, provedbu i dokumentiranje mjera za postupanje s utvrđenim i procijenjenim IKT rizicima, što uključuje određivanje mjera za postupanje s IKT rizicima koje su nužne kako bi se IKT rizik smanjio na razinu tolerancije na rizik iz točke (a);
(d)
za preostale IKT rizike koji i dalje postoje nakon provedbe mjera za postupanje s IKT rizicima iz točke (c):
i.
odredbe o utvrđivanju tih preostalih IKT rizika;
ii.
dodjelu uloga i odgovornosti u vezi s:
1.
prihvaćanjem preostalih IKT rizika koji prelaze razinu tolerancije financijskog subjekta na rizik iz točke (a);
2.
procesom preispitivanja iz podtočke iv. ove točke (d);
iii.
izradu popisa prihvaćenih preostalih IKT rizika uz obrazloženje prihvaćanja;
iv.
odredbe o preispitivanju prihvaćenih preostalih IKT rizika najmanje jedanput godišnje, uključujući:
1.
utvrđivanje svih promjena preostalih IKT rizika;
2.
procjenu dostupnih mjera za ublažavanje;
3.
procjenu toga jesu li razlozi za prihvaćanje preostalih IKT rizika i dalje valjani i primjenjivi na datum preispitivanja;
(e)
odredbe o praćenju:
i.
svih promjena IKT rizika i prirode kiberprijetnji;
ii.
unutarnjih i vanjskih ranjivosti i prijetnji;
iii.
IKT rizika financijskog subjekta kojim se omogućuje brzo otkrivanje promjena koje bi mogle utjecati na njegov profil IKT rizičnosti;
(f)
odredbe o procesu kojim se osigurava da se uzimaju u obzir sve promjene poslovne strategije i strategije za digitalnu operativnu otpornost financijskog subjekta.
Za potrebe prvog stavka točke (c) postupkom iz te točke osigurava se:
(a)
praćenje djelotvornosti provedenih mjera za postupanje s IKT rizicima;
(b)
procjena toga jesu li postignute utvrđene razine tolerancije financijskog subjekta na rizik;
(c)
procjena toga je li financijski subjekt prema potrebi poduzeo mjere za ispravak ili poboljšanje tih mjera.
|
|
EULAW
|
Članak 23. Otkrivanje neobičnih aktivnosti te kriteriji za otkrivanje i odgovor na IKT incidente
-
|
|
EULAW
|
Članak 31. Upravljanje IKT rizicima
-
|
|
EULAW
|
Članak 34. Sigurnost operacija IKT-a
Članak 34.
Sigurnost operacija IKT-a
Financijski subjekti iz članka 16. stavka 1. Uredbe (EU) 2022/2554 u sklopu svojih sustava, protokola i alata te u pogledu sve IKT imovine:
(a)
prate i upravljaju životnim ciklusom sve IKT imovine;
(b)
prate podupiru li IKT imovinu treće strane pružatelji IKT usluga financijskih subjekata, prema potrebi;
(c)
utvrđuju zahtjeve za kapacitet svoje IKT imovine te mjere za održavanje i povećanje dostupnosti i učinkovitosti IKT sustavâ te sprečavaju manjak kapaciteta IKT-a prije nego što do njega dođe;
(d)
provode automatizirano skeniranje i procjenu ranjivosti IKT imovine razmjerne njihovoj klasifikaciji u skladu s člankom 30. stavkom 1. i ukupnom profilu rizičnosti IKT imovine te uvode zakrpe kako bi otklonili utvrđene ranjivosti;
(e)
upravljaju rizicima povezanima sa zastarjelom ili nepodržanom IKT imovinom;
(f)
evidentiraju događaje povezane s kontrolom logičkog i fizičkog pristupa, operacijama IKT-a, među ostalim aktivnostima sustava i mrežnog prometa, i upravljanjem promjenama IKT-a;
(g)
utvrđuju i provode mjere za praćenje i analiziranje informacija o neobičnim aktivnostima i ponašanju za ključne ili važne operacije IKT-a;
(h)
provode mjere za praćenje relevantnih i aktualnih informacija o kiberprijetnjama;
(i)
provode mjere za utvrđivanje mogućih curenja informacija, zlonamjernog koda i drugih sigurnosnih prijetnji, kao i javno poznatih ranjivosti softvera i hardvera te provjeravaju postoje li odgovarajuća nova sigurnosna ažuriranja.
Za potrebe točke (f) financijski subjekti usklađuju razinu detaljnosti evidencije s njihovom svrhom i upotrebom IKT imovine koja se koristi za izradu evidencije.
|
|
EULAW
|
Članak 13. Učenje i razvoj
|
|
EULAW
|
Članak 45. Aranžmani za razmjenu informacija i saznanja o kiberprijetnjama
|
|
EULAW
|
Article 13 1
1. Financial entities shall have in place capabilities and staff to gather information on vulnerabilities and cyber threats, ICT-related incidents, in particular cyber-attacks, and analyse the impact they are likely to have on their digital operational resilience.
|
|
EULAW
|
Article 45 1
1. Financial entities may exchange amongst themselves cyber threat information and intelligence, including indicators of compromise, tactics, techniques, and procedures, cyber security alerts and configuration tools, to the extent that such information and intelligence sharing:
|
(a)
|
aims to enhance the digital operational resilience of financial entities, in particular through raising awareness in relation to cyber threats, limiting or impeding the cyber threats’ ability to spread, supporting defence capabilities, threat detection techniques, mitigation strategies or response and recovery stages;
|
|
(b)
|
takes places within trusted communities of financial entities;
|
|
(c)
|
is implemented through information-sharing arrangements that protect the potentially sensitive nature of the information shared, and that are governed by rules of conduct in full respect of business confidentiality, protection of personal data in accordance with Regulation (EU) 2016/679 and guidelines on competition policy.
|
|
|
EULAW
|
Article 45 2
2. For the purpose of paragraph 1, point (c), the information-sharing arrangements shall define the conditions for participation and, where appropriate, shall set out the details on the involvement of public authorities and the capacity in which they may be associated to the information-sharing arrangements, on the involvement of ICT third-party service providers, and on operational elements, including the use of dedicated IT platforms.
|
|
EULAW
|
Article 45 3
3. Financial entities shall notify competent authorities of their participation in the information-sharing arrangements referred to in paragraph 1, upon validation of their membership, or, as applicable, of the cessation of their membership, once it takes effect.
|
Povezani zadaci
- 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.
|