+Network Intrusion Detection / Prevention Systems (NIDS / NIPS)

Network Intrusion Detection / Prevention Systems (NIDS / NIPS)

Description

Mechanisms exist to employ Network Intrusion Detection / Prevention Systems (NIDS/NIPS) to detect and/or prevent intrusions into the network.

Possible Solutions & Considerations

Micro-Small Business (<10 staff) / BLS Firm Size Classes 1-2

∙ Network Intrusion Detection System (NIDS)
∙ Network Intrusion Prevention Systems (NIPS)

Small Business (10-49 staff) / BLS Firm Size Classes 3-4

∙ Network Intrusion Detection System (NIDS)
∙ Network Intrusion Prevention Systems (NIPS)

Medium Business (50-249 staff) / BLS Firm Size Classes 5-6

∙ Network Intrusion Detection System (NIDS)
∙ Network Intrusion Prevention Systems (NIPS)

Large Business (250-999 staff) / BLS Firm Size Classes 7-8

∙ Network Intrusion Detection System (NIDS)
∙ Network Intrusion Prevention Systems (NIPS)

Enterprise (> 1,000 staff) / BLS Firm Size Class 9

∙ Network Intrusion Detection System (NIDS)
∙ Network Intrusion Prevention Systems (NIPS)

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

Network Security (NET) 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 NET domain capabilities are formally documented and centrally-managed by the entity.
▪ Standardized Operating Procedures (SOP) associated with NET 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 NET domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD).
▪ Network security-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines).
▪ Network security management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel.
▪ IT personnel define secure networking practices to protect the Confidentiality, Integrity, Availability and Safety (CIAS) of the organization's TAASD.
▪ Secure Baseline Configurations (SBC) enforce the principles of least privileges and least functionality for boundary protection technologies.

Level 3 Well Defined

Network Security (NET) 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 NET 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 NET domain capabilities are well-documented and kept current by process owners.
▪ A network security management team, or similar function, is appropriately staffed and supported to implement and maintain NET domain capabilities.
▪ Technology is leveraged to enhance the efficiency and accuracy of network security operations (e.g., network management solution and log aggregator).
▪ 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 NET 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 the principles of least privileges and least functionality for boundary protection technologies.
▪ An implemented and operational capability exists to employ Network Intrusion Detection / Prevention Systems (NIDS/NIPS) to detect and/or prevent intrusions into the network.

Level 4 Quantitatively Controlled

Network Security (NET) 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. Oversigt

1.1 Referencer

1.2 Identificerede krav

1.3 Relaterede reguleringer

2. Identificerede krav

Krav

3. Relaterede reguleringer

Reguleringer
EULAW Artikel 35 Data-, system- og netsikkerhed

Artikel 35

Data-, system- og netsikkerhed

De finansielle enheder, der er omhandlet i artikel 16, stk. 1, i forordning (EU) 2022/2554, udvikler og gennemfører som en del af deres systemer, protokoller og værktøjer sikkerhedsforanstaltninger, der garanterer netsikkerheden mod indtrængen og datamisbrug, og som bevarer tilgængeligheden, autenticiteten, integriteten og fortroligheden af data. Navnlig indfører finansielle enheder under hensyntagen til den klassificering, der er omhandlet i denne forordnings artikel 30, stk. 1, alt følgende:

a) 

identifikation og gennemførelse af foranstaltninger til beskyttelse af data, som i brug, under overførsel og inaktive

b) 

identifikation og gennemførelse af sikkerhedsforanstaltninger med henblik på brugen af software, datalagringsmedier, -systemer og endpoint-enheder til at overføre og lagre den finansielle enheds data

c) 

identifikation og gennemførelse af foranstaltninger til forebyggelse og detektion af uautoriserede forbindelser til den finansielle enheds netværk og til sikring af nettrafikken mellem den finansielle enheds interne netværk og internettet og andre eksterne forbindelser

d) 

identifikation og gennemførelse af foranstaltninger, der sikrer tilgængeligheden, autenticiteten, integriteten og fortroligheden af data i forbindelse med under overførsel på nettet

e) 

proces for sikker sletning af data, der findes i den finansielle enheds lokaler eller lagres eksternt, som den finansielle enhed ikke længere behøver at indsamle eller lagre

f) 

en proces til sikker bortskaffelse eller demontering af datalagringsenheder i lokaler eller datalagringsenheder, der er lagret eksternt, og som indeholder fortrolige oplysninger

g) 

identifikation og gennemførelse af foranstaltninger til at sikre, at telearbejde og brugen af private endpoint-enheder ikke har en negativ indvirkning på den finansielle enheds evne til at udøve sine kritiske aktiviteter på en passende, rettidig og sikker måde.
EULAW Artikel 10 Detektion
-
EULAW Artikel 10 Detektion
-
EULAW Artikel 10 2

2.   Ved de i stk. 1 omhandlede detektionsmekanismer skal det gøres muligt at anvende flere kontrollag, fastlægge varslingstærskler og -kriterier, som skal udløse og igangsætte indsatsforanstaltninger mod IKT-relaterede hændelser, herunder automatiske varslingsmekanismer for det relevante personale, som har ansvar for indsatsen mod IKT-relaterede hændelser.

Linkede sager

Sagslinks
is related to Annual
is related to relative Control Weighting = 09
is related to Technology
is related to Protect
is related to SCRM Focus Tier 2 OPERATIONAL
is related to SCRM Focus Tier 3 TACTICAL
blocks Unauthorized Access
blocks Identity Compromise / Impersonation
blocks Unauthorized Modification / Loss of System Integrity
blocks System / Data Compromise (Technical Vector)
blocks Regulatory / Legal / Contractual Financial Liability
blocks Exposure from Unaddressed Vulnerabilities
blocks System / Service Compromise
blocks Loss of Investigative / Evidentiary Capability
blocks Delayed Containment / Increased Incident Impact
blocks Incident Persistence / Recurrence
blocks Undetected / Delayed Detection of Adverse Activity
blocks Loss of Confidentiality
blocks Loss of Data Integrity
blocks Loss of Data / Service Availability
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 Civil or Political Unrest
blocks Malicious Cyber Activity
blocks Hazardous Materials Emergencies
blocks Nuclear, Biological and Chemical (NBC) Weapons
blocks Physical Crime
blocks Terrorism & Armed Attacks
blocks Utility Service Disruption
blocks Dysfunctional Management Practices
blocks Human Error
blocks Technical / Mechanical Failure
blocks Data Quality Degradation / Data Poisoning
blocks Artificial Intelligence & Autonomous Technologies (AAT) System Failure or Unintended Behavior
blocks Fraud, Corruption and/or Intentional Criminal Conduct
blocks Hazardous / Degraded Operational Environment
blocks Product Defect / Design Failure
blocks Workforce Shortage / Loss of Critical Skills / Labor Disruption
blocks Infrastructure Failure / Degradation
blocks Adversarial Artificial Intelligence (AI) Attack
blocks COS-01.01B
blocks COS-01.02B
blocks Unauthorized Access
blocks Identity Compromise / Impersonation
blocks Unauthorized Modification / Loss of System Integrity
blocks System / Data Compromise (Technical Vector)
blocks Regulatory / Legal / Contractual Financial Liability
blocks Exposure from Unaddressed Vulnerabilities
blocks System / Service Compromise
blocks Loss of Investigative / Evidentiary Capability
blocks Delayed Containment / Increased Incident Impact
blocks Incident Persistence / Recurrence
blocks Undetected / Delayed Detection of Adverse Activity
blocks Loss of Confidentiality
blocks Loss of Data Integrity
blocks Loss of Data / Service Availability
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 Civil or Political Unrest
blocks Malicious Cyber Activity
blocks Hazardous Materials Emergencies
blocks Nuclear, Biological and Chemical (NBC) Weapons
blocks Physical Crime
blocks Terrorism & Armed Attacks
blocks Utility Service Disruption
blocks Dysfunctional Management Practices
blocks Human Error
blocks Technical / Mechanical Failure
blocks Data Quality Degradation / Data Poisoning
blocks Artificial Intelligence & Autonomous Technologies (AAT) System Failure or Unintended Behavior
blocks Fraud, Corruption and/or Intentional Criminal Conduct
blocks Hazardous / Degraded Operational Environment
blocks Product Defect / Design Failure
blocks Workforce Shortage / Loss of Critical Skills / Labor Disruption
blocks Infrastructure Failure / Degradation
blocks Adversarial Artificial Intelligence (AI) Attack
blocks COS-01.01B
blocks COS-01.02B
is blocked by NET-31 Network Intrusion Detection / Prevention Systems (NIDS / NIPS) – Assessment Procedure
blocks 03.13.01 Boundary Protection
blocks 03.14.06 System Monitoring
  • 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.