+Anomalous Behavior
---+Unusual Transactions
|
Anomalous Behavior
Description
Mechanisms exist to utilize User & Entity Behavior Analytics (UEBA) and/or User Activity Monitoring (UAM) solutions to detect and respond to anomalous behavior that could indicate account compromise or other malicious activities.
Possible Solutions & Considerations
Micro-Small Business (<10 staff) / BLS Firm Size Classes 1-2
∙ Indicators of Compromise (IoC)
∙ Indicators of Exposure (IoE)
∙ Managed Security Services Provider (MSSP)
Small Business (10-49 staff) / BLS Firm Size Classes 3-4
∙ Indicators of Compromise (IoC)
∙ Indicators of Exposure (IoE)
∙ Security Incident Event Manager (SIEM)
∙ Managed Security Services Provider (MSSP)
Medium Business (50-249 staff) / BLS Firm Size Classes 5-6
∙ Indicators of Compromise (IoC)
∙ Indicators of Exposure (IoE)
∙ Security Incident Event Manager (SIEM)
∙ Extended Detection and Response (XDR)
∙ Managed Security Services Provider (MSSP)
Large Business (250-999 staff) / BLS Firm Size Classes 7-8
∙ Indicators of Compromise (IoC)
∙ Indicators of Exposure (IoE)
∙ Security Incident Event Manager (SIEM)
∙ Extended Detection and Response (XDR)
∙ Managed Security Services Provider (MSSP)
Enterprise (> 1,000 staff) / BLS Firm Size Class 9
∙ Indicators of Compromise (IoC)
∙ Indicators of Exposure (IoE)
∙ Security Incident Event Manager (SIEM)
∙ Extended Detection and Response (XDR)
∙ Managed Security Services Provider (MSSP)
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
Continuous Monitoring (MON) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include:
▪ Policies, standards & procedures associated with MON domain capabilities provide limited coverage due to the depth and breadth of the existing documentation.
▪ Event monitoring-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
▪ Monitoring is primarily reactive in nature, focused on identifying incidents that occurred.
▪ Event log reviews primarily rely on manual processes to identify anomalous behaviors.
Level 2 Planned Tracked
Continuous Monitoring (MON) 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 MON domain capabilities are formally documented and centrally-managed by the entity.
▪ Standardized Operating Procedures (SOP) associated with MON 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 MON domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD).
▪ Continuous monitoring-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines).
▪ Continuous monitoring 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
Continuous Monitoring (MON) 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 MON domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function.
▪ Cybersecurity personnel use a structured process via Standardized Operating Procedures (SOP) to review and analyze logs.
▪ A Security Operations Center (SOC) team, or similar function, is appropriately staffed and supported to implement and maintain MON domain capabilities.
▪ Technology is leveraged to enhance the efficiency and accuracy of continuous monitoring operations (e.g., Security Incident Event Manager (SIEM)).
▪ 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 MON 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).
▪ Secure Baseline Configurations (SBC) enforce security event logging to contain sufficient information to establish necessary details of activity and allow for forensics analysis.
▪ An implemented and operational capability exists to utilize User & Entity Behavior Analytics (UEBA) and/or User Activity Monitoring (UAM) solutions to detect and respond to anomalous behavior that could indicate account compromise or other malicious activities.
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. Ülevaade
| Pealkiri |
Standard |
|
Unusual Transactions
|
Description
Mechanisms exist to define "normal business activities" to identify anomalous transaction activities that can reduce the opportunity for sending (outbound) and/or receiving (inbound) hostile and/or fraudulent actions.
Possible Solutions & Considerations
Micro-Small Business (<10 staff) / BLS Firm Size Classes 1-2
∙ Indicators of Fraud (IoF) (e.g., fraud "red flags")
Small Business (10-49 staff) / BLS Firm Size Classes 3-4
∙ Indicators of Fraud (IoF) (e.g., fraud "red flags")
Medium Business (50-249 staff) / BLS Firm Size Classes 5-6
∙ Indicators of Fraud (IoF) (e.g., fraud "red flags")
Large Business (250-999 staff) / BLS Firm Size Classes 7-8
∙ Indicators of Fraud (IoF) (e.g., fraud "red flags")
Enterprise (> 1,000 staff) / BLS Firm Size Class 9
∙ Indicators of Fraud (IoF) (e.g., fraud "red flags")
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
Data Classification & Handling (DCH) 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 DCH domain capabilities are formally documented and centrally-managed by the entity.
▪ Standardized Operating Procedures (SOP) associated with DCH 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 DCH domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD).
▪ Data classification and handling-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines).
▪ Data classification and handling management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel.
▪ A formalized data classification scheme exists to identify categories of data, based on protection requirements from applicable laws, regulations and/or contractual obligations.
Level 3 Well Defined
Continuous Monitoring (MON) 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 MON domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function.
▪ Cybersecurity personnel use a structured process via Standardized Operating Procedures (SOP) to review and analyze logs.
▪ A Security Operations Center (SOC) team, or similar function, is appropriately staffed and supported to implement and maintain MON domain capabilities.
▪ Technology is leveraged to enhance the efficiency and accuracy of continuous monitoring operations (e.g., Security Incident Event Manager (SIEM)).
▪ 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 MON 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).
▪ Secure Baseline Configurations (SBC) enforce security event logging to contain sufficient information to establish necessary details of activity and allow for forensics analysis.
▪ An implemented and operational capability exists to establish organization-defined "normal business activities" to identify anomalous transaction activities that can reduce the opportunity for sending (outbound) and/or receiving (inbound) fraudulent actions.
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.1 Viited
1.2 Tuvastatud nõuded
1.3 Seotud regulatsioonid
2. Tuvastatud nõuded
3. Seotud regulatsioonid
Regulatsioonid
| Allikas |
Regulatsioon |
|
EULAW
|
Article 10 1
1. Financial entities shall have in place mechanisms to promptly detect anomalous activities, in accordance with Article 17, including ICT network performance issues and ICT-related incidents, and to identify potential material single points of failure.
All detection mechanisms referred to in the first subparagraph shall be regularly tested in accordance with Article 25.
|
|
EULAW
|
Artikkel 22 IKT intsidentide haldamise põhimõtted
Artikkel 22
IKT intsidentide haldamise põhimõtted
Finantssektori ettevõtjad töötavad anomaalse tegevuse, sealhulgas IKT-võrgu jõudluse probleemide ja IKT intsidentide avastamise mehhanismide osana välja ja dokumenteerivad IKT intsidentide haldamise põhimõtted ning rakendavad neid ning teevad nende kohaselt järgmist:
a)
dokumenteerivad määruse (EL) 2022/2554 artiklis 17 osutatud IKT intsidentide haldamise protsessi;
b)
koostavad loetelu asjakohaste sisefunktsioonide täitjatest ja väliste sidusrühmade esindajatest, kes on otseselt seotud IKT-toimingute turvalisusega, sealhulgas järgmisega:
i)
küberohtude avastamine ja seire,
ii)
anomaalse tegevuse avastamine,
c)
loovad, võtavad kasutusele ja käitavad IKT intsidentide haldamise protsessi toetavaid tehnilisi, korralduslikke ja tegevusmehhanisme, sealhulgas mehhanisme, mis võimaldavad kiiresti avastada anomaalse tegevuse ja käitumise kooskõlas käesoleva määruse artikliga 23;
▼C1
d)
kooskõlas komisjoni delegeeritud määruse (EL) 2024/1772 (
2
) artikli 8 lõikega 2 ja liidu õiguses sätestatud kohaldatavate säilitamisnõuetega säilitavad kõik IKT intsidentidega seotud tõendid, mis on vastavuses mõjutatud ärifunktsioonide, toetavate protsesside ning IKT- ja teabevarade kriitilise tähtsusega, ajavahemiku jooksul, mis ei ole pikem kui on vajalik andmete kogumise eesmärgi saavutamiseks;
▼B
e)
loovad mehhanismid, et analüüsida olulisi või korduvaid IKT intsidente ning nende intsidentide arvu ja esinemisega seotud suundumusi, ning rakendavad neid mehhanisme.
Punkti d kohaldamisel säilitavad finantssektori ettevõtjad nimetatud punktis osutatud tõendeid turvalisel viisil.
|
|
EULAW
|
Artikkel 23 Anomaalse tegevuse avastamine ning IKT intsidentide avastamise ja neile reageerimise kriteeriumid
-
|
|
EULAW
|
Artikkel 23 Anomaalse tegevuse avastamine ning IKT intsidentide avastamise ja neile reageerimise kriteeriumid
-
|
|
EULAW
|
Artikkel 34 IKT-toimingute turvalisus
Artikkel 34
IKT-toimingute turvalisus
Määruse (EL) 2022/2554 artikli 16 lõikes 1 osutatud finantssektori ettevõtjad teevad oma süsteemide, protokollide ja vahendite rakendamise raames kõigi IKT-varade puhul järgmist:
a)
seiravad ja haldavad kõigi IKT-varade olelusringi;
b)
vajaduse korral kontrollivad, kas nende IKT-varasid toetavad kolmandast isikust IKT-teenuste osutajad;
c)
teevad kindlaks oma IKT-varade ja -meetmete vajamineva võimsuse, mis võimaldab säilitada ja muuta paremaks IKT-süsteemide kättesaadavuse ja tõhususe ning ennetada IKT võimsuse puudujääki;
d)
teevad IKT-varade nõrkuse automaatse skaneerimise ja hindamise, mis on vastavuses artikli 30 lõikes 1 osutatud liigitusega ja IKT-vara üldise riskiprofiiliga, ning võtavad kasutusele paigad tuvastatud nõrkuste kõrvaldamiseks;
e)
juhivad aegunud, toetamata või IKT pärandvaraga seotud riske;
f)
logivad sündmusi, mis on seotud loogilise ja füüsilise pääsu reguleerimisega, IKT-toimingutega, sealhulgas süsteemi- ja võrguliiklusega, ning IKT-muudatuste juhtimisega;
g)
määravad kindlaks meetmed, millega seirata ja analüüsida kriitilise tähtsusega või oluliste IKT-toimingutega seotud anomaalset tegevust ja käitumist käsitlevat teavet;
h)
rakendavad meetmeid, millega seirata küberohte käsitlevat asja- ja ajakohast teavet;
i)
rakendavad meetmeid, millega teha kindlaks võimalikud teabelekked, ründekoodid ja muud turvaohud, samuti tarkvara ja riistvara üldteada nõrkused ning kontrollida vastavaid turvauuendeid.
Punkti f kohaldamisel viivad finantssektori ettevõtjad logide üksikasjalikkuse vastavusse logide otstarbega ja neid logisid tootva IKT-vara kasutamisega.
|
|
EULAW
|
Artikkel 10 Avastamine
-
|
Lingitud teemad
- 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.
|