+Safeguarding Data Over Open Networks

Safeguarding Data Over Open Networks

Description

Cryptographic mechanisms exist to implement strong cryptography and security protocols to safeguard sensitive and/or regulated data during transmission over open, public networks.

Possible Solutions & Considerations

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

∙ Use HTTPS/TLS for all internet-facing communications

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

∙ TLS for all internet traffic
∙ No unencrypted protocols over public networks

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

∙ Encryption-in-transit standards
∙ TLS 1.2+ enforcement
∙ Certificate management

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

∙ Enterprise encryption-in-transit program
∙ TLS 1.3 enforcement
∙ Certificate lifecycle management

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

∙ Enterprise encryption governance program
∙ TLS 1.3+
∙ Certificate management platform (e.g., Venafi)
∙ Automated certificate monitoring

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

Network Security (NET) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include:
▪ Policies, standards & procedures associated with NET domain capabilities provide limited coverage due to the depth and breadth of the existing documentation.
▪ Network security-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
▪ Network communications containing sensitive/regulated data are protected using a cryptographic mechanism to prevent unauthorized disclosure of information while in transit (e.g., SSH, TLS and VPN).
▪ Wireless access is protected via secure authentication and encryption.

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.
▪ Network communications containing sensitive/regulated data use a cryptographic mechanism to prevent the unauthorized disclosure of information while in transit (e.g., SSH, TLS and VPN).

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 cryptographic capability exists to implement strong cryptography and security protocols to safeguard sensitive/regulated data during transmission over open, public networks.

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

1.1 Referenties

1.2 Geïdentificeerde eisen

1.3 Gerelateerde regelingen

2. Geïdentificeerde eisen

Eisen

3. Gerelateerde regelingen

Regelingen
EULAW Artikel 13 Beheer van netwerkbeveiliging

Artikel 13

Beheer van netwerkbeveiliging

Als onderdeel van de beschermingsmaatregelen die netwerken tegen inbraken en misbruik van gegevens moeten beveiligen, ontwikkelen, documenteren en implementeren financiële entiteiten beleidslijnen, procedures, protocollen en tools voor het beheer van netwerkbeveiliging, die alle volgende elementen bevatten:

a) 

de scheiding en segmentatie van ICT-systemen en -netwerken, rekening houdende met:

i) 

het kritieke karakter of belang van de functie die door deze ICT-systemen en -netwerken wordt ondersteund;

ii) 

de overeenkomstig artikel 8, lid 1, van Verordening (EU) 2022/2554 vastgestelde classificatie;

iii) 

het algemene risicoprofiel van ICT-assets die van die ICT-systemen en -netwerken gebruikmaken;

b) 

de documentatie van alle netwerkverbindingen en gegevensstromen van de financiële entiteit;

c) 

het gebruik van een apart en specifiek netwerk voor het beheer van die ICT-assets;

d) 

de identificatie en implementatie van controles op netwerktoegang voor het voorkomen en detecteren van verbindingen met het netwerk door een ongeautoriseerd apparaat of systeem, of van endpoints die niet voldoen aan de beveiligingseisen van de financiële entiteit;

e) 

de encryptie van netwerkverbindingen die over bedrijfsnetwerken, publieke netwerken, thuisnetwerken, netwerken van derde partijen en draadloze netwerken lopen, voor gebruikte communicatieprotocollen, rekening houdende met de uitkomsten van de goedgekeurde dataclassificatie, de uitkomsten van de ICT-risicobeoordeling en de encryptie van netwerkverbindingen als bedoeld in artikel 6, lid 2;

f) 

de opzet van netwerken in lijn met de ICT-beveiligingseisen die door de financiële entiteit zijn vastgesteld, rekening houdende met maatgevende praktijken om de vertrouwelijkheid, integriteit en beschikbaarheid van het netwerk te borgen;

g) 

de beveiliging van netwerkverkeer tussen de interne netwerken en de internet- en andere externe verbindingen;

h) 

het in kaart brengen van de rollen, verantwoordelijkheden en stappen voor de specificatie, implementatie, goedkeuring, wijziging en evaluatie van firewallregels en verbindingsfilters;

i) 

het uitvoeren van evaluaties van de netwerkarchitectuur en van de inrichting van de netwerkbeveiliging eenmaal per jaar, en op periodieke basis voor micro-ondernemingen, om potentiële kwetsbaarheden in beeld te brengen;

j) 

de maatregelen om, waar nodig, subnetwerken en netwerkcomponenten en apparaten tijdelijk te isoleren;

k) 

de implementatie van een veilige configuratiebaseline van alle netwerkcomponenten en van de hardening van het netwerk en netwerkapparaten in lijn met eventuele instructies van de verkoper en, in voorkomend geval, toepasselijke normen zoals gedefinieerd in artikel 2, punt 1), van Verordening (EU) nr. 1025/2012, en maatgevende praktijken;

l) 

de procedures om systeemsessies en externe sessies na een gespecificeerde periode van inactiviteit te beperken, te vergrendelen en te beëindigen;

m) 

voor overeenkomsten inzake netwerkdiensten:

i) 

de identificatie en specificatie van ICT- en informatiebeveiligingsmaatregelen, service levels en beheersvereisten voor alle netwerkdiensten;

ii) 

de vraag of die diensten worden verricht door een intragroepsaanbieder van ICT-diensten of door derde aanbieders van ICT-diensten.

Voor de toepassing van punt h) voeren financiële entiteiten de evaluatie van firewallregels en verbindingsfilters op regelmatige basis uit in overeenstemming met de overeenkomstig artikel 8, lid 1, van Verordening (EU) 2022/2554 vastgestelde classificatie en het algemene risicoprofiel van de betrokken ICT-systemen. Voor ICT-systemen die kritieke of belangrijke functies ondersteunen, gaan financiële entiteiten ten minste om de zes maanden na of de bestaande firewallregels en verbindingsfilters afdoende zijn.
EULAW Artikel 14 Informatie in transit beveiligen
-

Gekoppelde issues

Koppelingen
is related to Annual
is related to relative Control Weighting = 08
is related to Technology
is related to Protect
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 Unauthorized Access
blocks Identity Compromise / Impersonation
blocks Data Loss / Integrity Compromise
blocks System / Data Compromise (Technical Vector)
blocks Regulatory / Legal / Contractual Financial Liability
blocks System / Service Compromise
blocks Intellectual Property / Trade Secret Loss
blocks Incident Response / Recovery Cost
blocks Long-Term Confidentiality Loss from Cryptographic Obsolescence
blocks Loss of Confidentiality
blocks Loss of Data Integrity
blocks Loss of Authenticity / Provenance
blocks Privacy Harm / Unauthorized Processing
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 Malicious Cyber Activity
blocks Dysfunctional Management Practices
blocks Human Error
blocks Technical / Mechanical Failure
blocks Statutory / Regulatory / Contractual Change
blocks Fraud, Corruption and/or Intentional Criminal Conduct
blocks Product Defect / Design Failure
blocks Harvest Now / Decrypt Later (HNDL)
blocks Cryptographic Compromise / Cryptanalytic Capability Advancement
blocks CRY-01.01B
blocks COS-08.01B
blocks COS-08.02B
blocks SSO-07.01B
blocks SSO-07.01AS
blocks Unauthorized Access
blocks Identity Compromise / Impersonation
blocks Data Loss / Integrity Compromise
blocks System / Data Compromise (Technical Vector)
blocks Regulatory / Legal / Contractual Financial Liability
blocks System / Service Compromise
blocks Intellectual Property / Trade Secret Loss
blocks Incident Response / Recovery Cost
blocks Long-Term Confidentiality Loss from Cryptographic Obsolescence
blocks Loss of Confidentiality
blocks Loss of Data Integrity
blocks Loss of Authenticity / Provenance
blocks Privacy Harm / Unauthorized Processing
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 Malicious Cyber Activity
blocks Dysfunctional Management Practices
blocks Human Error
blocks Technical / Mechanical Failure
blocks Statutory / Regulatory / Contractual Change
blocks Fraud, Corruption and/or Intentional Criminal Conduct
blocks Product Defect / Design Failure
blocks Harvest Now / Decrypt Later (HNDL)
blocks Cryptographic Compromise / Cryptanalytic Capability Advancement
blocks CRY-01.01B
blocks COS-08.01B
blocks COS-08.02B
blocks SSO-07.01B
blocks SSO-07.01AS
is blocked by NET-37 Safeguarding Data Over Open Networks – Assessment Procedure
blocks AC-02 Account Management
blocks AC-03 Access Enforcement
blocks AC-05 Separation of Duties
blocks SI-03 Malicious Code Protection
blocks SI-04 System Monitoring
blocks SI-05 Security Alerts, Advisories, and Directives
blocks SI-07 Software, Firmware, and Information Integrity
blocks SI-10 Information Input Validation
blocks AC-02 [L] Account Management
blocks AC-03 [L] Access Enforcement
blocks SI-03 [L] Malicious Code Protection
blocks SI-04 [L] System Monitoring
blocks SI-05 [L] Security Alerts, Advisories, and Directives
blocks AC-02 [M] Account Management
blocks AC-03 [M] Access Enforcement
blocks AC-05 [M] Separation of Duties
blocks SI-03 [M] Malicious Code Protection
blocks SI-04 [M] System Monitoring
blocks SI-05 [M] Security Alerts, Advisories, and Directives
blocks SI-07 [M] Software, Firmware, and Information Integrity
blocks SI-10 [M] Information Input Validation
blocks AC-02 [H] Account Management
blocks AC-03 [H] Access Enforcement
blocks AC-05 [H] Separation of Duties
blocks SI-03 [H] Malicious Code Protection
blocks SI-04 [H] System Monitoring
blocks SI-05 [H] Security Alerts, Advisories, and Directives
blocks SI-07 [H] Software, Firmware, and Information Integrity
blocks SI-10 [H] Information Input Validation