+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. Visão geral
1.1 Referências
1.2 Requisitos identificados
1.3 Regulamentos relacionados
2. Requisitos identificados
Requisitos
| Fonte |
Requisito |
3. Regulamentos relacionados
Regulamentos
| Fonte |
Regulamentação |
|
EULAW
|
Artigo 2.o Elementos gerais das políticas, procedimentos, protocolos e ferramentas de segurança no domínio das TIC
-
|
|
EULAW
|
Artigo 3.o Gestão do risco associado às TIC
Artigo 3.o
Gestão do risco associado às TIC
As entidades financeiras devem desenvolver, documentar e aplicar políticas e procedimentos de gestão do risco associado às TIC que incluam todos os elementos seguintes:
a)
Uma indicação da aprovação do nível de tolerância ao risco associado às TIC estabelecido em conformidade com o artigo 6.o, n.o 8, alínea b), do Regulamento (UE) 2022/2554;
b)
Um procedimento e uma metodologia para realizar a avaliação do risco associado às TIC, que identifiquem:
i)
as vulnerabilidades e ameaças que afetem ou possam afetar as funções operacionais apoiadas, os sistemas de TIC e os ativos de TIC que apoiam essas funções,
ii)
os indicadores quantitativos ou qualitativos para medir o impacto e a probabilidade das vulnerabilidades e ameaças referidas na subalínea i);
c)
O procedimento para identificar, aplicar e documentar medidas de tratamento do risco associado às TIC para os riscos associados às TIC identificados e avaliados, designadamente a determinação das medidas de tratamento do risco associado às TIC necessárias para manter esse risco dentro do nível de tolerância referido na alínea a);
d)
Para os riscos residuais associados às TIC que ainda estejam presentes na sequência da aplicação das medidas de tratamento do risco associado às TIC referido na alínea c):
i)
disposições relativas à identificação desses riscos residuais associados às TIC,
ii)
a atribuição de funções e responsabilidades no que respeita:
(1)
à aceitação dos riscos residuais associados às TIC que excedem o nível de tolerância ao risco da entidade financeira referido na alínea a);
(2)
ao processo de revisão referido na subalínea iv) da presente alínea d);
iii)
a elaboração de um inventário dos riscos residuais associados às TIC aceites, incluindo uma justificação para a sua aceitação,
iv)
disposições relativas à revisão dos riscos residuais associados às TIC aceites, pelo menos uma vez por ano, nomeadamente:
(1)
a identificação de quaisquer alterações dos riscos residuais associados às TIC;
(2)
a avaliação das medidas de mitigação disponíveis;
(3)
uma avaliação para determinar se as razões que justificam a aceitação dos riscos residuais associados às TIC continuam a ser válidas e aplicáveis à data da revisão;
e)
Disposições relativas à monitorização:
i)
de quaisquer alterações do panorama dos riscos associados às TIC e das ciberameaças,
ii)
das vulnerabilidades e ameaças internas e externas,
iii)
do risco associado às TIC da entidade financeira, de um modo que permita a deteção rápida de alterações que possam afetar o seu perfil de risco associado às TIC;
f)
Disposições relativas a um processo para assegurar que quaisquer alterações da estratégia empresarial e da estratégia de resiliência operacional digital da entidade financeira são tidas em conta.
Para efeitos da alínea c), primeiro parágrafo, o procedimento referido nessa alínea deve assegurar:
a)
A monitorização da eficácia das medidas de tratamento do risco associado às TIC aplicadas;
b)
Uma avaliação para determinar se os níveis de tolerância ao risco estabelecidos pela entidade financeira foram atingidos;
c)
Uma avaliação para determinar se a entidade financeira tomou medidas para corrigir ou melhorar essas medidas, quando necessário.
|
|
EULAW
|
Artigo 23.o Deteção de atividades anómalas e critérios para a deteção e resposta a incidentes relacionados com as TIC
-
|
|
EULAW
|
Artigo 31.o Gestão do risco associado às TIC
-
|
|
EULAW
|
Artigo 34.o Segurança das operações de TIC
Artigo 34.o
Segurança das operações de TIC
As entidades financeiras a que se refere o artigo 16.o, n.o 1, do Regulamento (UE) 2022/2554 devem, no âmbito dos seus sistemas, protocolos e ferramentas, e em relação a todos os ativos de TIC:
a)
Acompanhar e gerir o ciclo de vida de todos os ativos de TIC;
b)
Verificar se os ativos de TIC são apoiados por terceiros prestadores de serviços de TIC de entidades financeiras, se for caso disso;
c)
Identificar as necessidades de capacidade dos seus ativos de TIC e as medidas para manter e melhorar a disponibilidade e a eficiência dos sistemas de TIC e evitar défices de capacidade das TIC antes da sua ocorrência;
d)
Realizar análises automatizadas das vulnerabilidades e avaliações de ativos de TIC proporcionadas à sua classificação, tal como referido no artigo 30.o, n.o 1, e ao perfil de risco global do ativo de TIC, bem como aplicar correções para resolver as vulnerabilidades identificadas;
e)
Gerir os riscos relacionados com ativos de TIC obsoletos, não apoiados ou legados;
f)
Registar eventos relacionados com o controlo lógico e físico do acesso e com as operações de TIC, incluindo atividades de tráfego nos sistemas e redes e a gestão de alterações das TIC;
g)
Identificar e aplicar medidas para monitorizar e analisar informações sobre atividades e comportamentos anómalos em operações críticas ou importantes no domínio das TIC;
h)
Aplicar medidas para monitorizar informações pertinentes e atualizadas sobre as ciberameaças;
i)
Aplicar medidas para identificar possíveis fugas de informação, códigos maliciosos e outras ameaças à segurança, bem como vulnerabilidades do conhecimento público em software e hardware, e verificar se existem novas atualizações de segurança correspondentes.
Para efeitos da alínea f), as entidades financeiras devem alinhar o nível de pormenor dos registos com a sua finalidade e a utilização do ativo de TIC que dá origem a esses registos.
|
|
EULAW
|
Artigo 13.o Aprendizagem e evolução
-
|
|
EULAW
|
Artigo 45.o Acordos de partilha de informações específicas e sensíveis relativas a ciberataques
-
|
|
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.
|
Pedidos ligados
- 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.
|