+Encrypting Data In Transit

Encrypting Data In Transit

Description

Cryptographic mechanisms exist to prevent the unauthorized disclosure of data in transit.

Possible Solutions & Considerations

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

∙ NIST Cryptographic Module Validation Program (CMVP) (https://csrc.nist.gov)
∙ Transport Layer Security (TLS)
∙ IPSec encryption
∙ Encrypted Multiprotocol Label Switching (MPLS)

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

∙ NIST Cryptographic Module Validation Program (CMVP) (https://csrc.nist.gov)
∙ Transport Layer Security (TLS)
∙ IPSec encryption
∙ Encrypted Multiprotocol Label Switching (MPLS)

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

∙ NIST Cryptographic Module Validation Program (CMVP) (https://csrc.nist.gov)
∙ Transport Layer Security (TLS)
∙ IPSec encryption
∙ Encrypted Multiprotocol Label Switching (MPLS)

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

∙ NIST Cryptographic Module Validation Program (CMVP) (https://csrc.nist.gov)
∙ Transport Layer Security (TLS)
∙ IPSec encryption
∙ Encrypted Multiprotocol Label Switching (MPLS)

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

∙ NIST Cryptographic Module Validation Program (CMVP) (https://csrc.nist.gov)
∙ Transport Layer Security (TLS)
∙ IPSec encryption
∙ Encrypted Multiprotocol Label Switching (MPLS)

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

Cryptographic Protections (CRY) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include:
▪ Policies, standards & procedures associated with CRY domain capabilities provide limited coverage due to the depth and breadth of the existing documentation.
▪ Cryptography 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 provide an encryption solution (software or hardware) for the storage of sensitive/regulated data.
▪ Sensitive/regulated data is encrypted in transit according to standardized processes.

Level 2 Planned Tracked

Cryptographic Protections (CRY) 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 CRY domain capabilities are formally documented and centrally-managed by the entity.
▪ Standardized Operating Procedures (SOP) associated with CRY 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 CRY domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD).
▪ Cryptographic management controls-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines).
▪ Cryptographic management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel.
▪ Technology Assets, Applications and/or Services (TAAS) that store, process or transmit sensitive/regulated data use cryptographic mechanisms to prevent unauthorized disclosure of information as an alternate to physical safeguards.
▪ External compliance requirements for cryptography are identified and documented, based on applicable laws, regulations and contractual obligations.
▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to implement cryptographic mechanisms that are applicability for statutory, regulatory and/or contractual compliance obligations.
▪ Sensitive/regulated data is encrypted at rest using cryptographic protections that are commensurate with the sensitivity of the data.
▪ Sensitive/regulated data is encrypted during transmission using cryptographic protections that are commensurate with the sensitivity of the data.

Level 3 Well Defined

Cryptographic Protections (CRY) 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 CRY 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 CRY domain capabilities are well-documented and kept current by process owners.
▪ A security engineering team, or similar function, is appropriately staffed and supported to implement and maintain CRY domain capabilities.
▪ Technology is leveraged to enhance the efficiency and accuracy of cryptographic protections operations (e.g., PKI management tool).
▪ 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 CRY 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 cryptographic capability exists to protect the confidentiality of data being transmitted.

Level 4 Quantitatively Controlled

Cryptographic Protections (CRY) 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. Ħarsa ġenerali

1.1 Referenzi

1.2 Rekwiżiti identifikati

1.3 Regolamenti relatati

2. Rekwiżiti identifikati

Rekwiżiti

3. Regolamenti relatati

Regolamenti
EULAW Artikolu 6 Kriptaġġ u kontrolli kriptografiċi
-
EULAW Artikolu 6 Kriptaġġ u kontrolli kriptografiċi
-
EULAW Artikolu 13 Ġestjoni tas-sigurtà tan-network

Artikolu 13

Ġestjoni tas-sigurtà tan-network

L-entitajiet finanzjarji għandhom, bħala parti mis-salvagwardji li jiżguraw is-sigurtà tan-networks kontra l-intrużjonijiet u l-użu ħażin tad-data, jiżviluppaw, jiddokumentaw u jimplimentaw politiki, proċeduri, protokolli u għodod dwar il-ġestjoni tas-sigurtà tan-network, inklużi dawn kollha li ġejjin:

(a) 

is-segregazzjoni u s-segmentazzjoni tas-sistemi u tan-networks tal-ICT filwaqt li jitqiesu:

(i) 

il-kritikalità jew l-importanza tal-funzjoni li jappoġġaw dawk is-sistemi u n-networks tal-ICT;

(ii) 

il-klassifikazzjoni stabbilita f’konformità mal-Artikolu 8(1) tar-Regolament (UE) 2022/2554;

(iii) 

il-profil tar-riskju kumplessiv tal-assi tal-ICT bl-użu ta’ dawk is-sistemi u networks;

(b) 

id-dokumentazzjoni tal-konnessjonijiet tan-network u l-flussi tad-data kollha tal-entità finanzjarja;

(c) 

l-użu ta’ network separat u ddedikat għall-amministrazzjoni tal-assi tal-ICT;

(d) 

l-identifikazzjoni u l-implimentazzjoni ta’ kontrolli tal-aċċess għan-network biex jiġu evitati u identifikati konnessjonijiet man-network tal-entità finanzjarja minn kwalunkwe apparat jew sistema mhux awtorizzati, jew kwalunkwe punt tat-tmiem li ma jissodisfax ir-rekwiżiti ta’ sigurtà tal-entità finanzjarja;

(e) 

il-kriptaġġ tal-konnessjonijiet tan-network li jgħaddu minn fuq in-networks korporattivi, in-networks pubbliċi, in-networks domestiċi, in-networks ta’ partijiet terzi, u n-networks mingħajr fili, għall-protokolli ta’ komunikazzjoni użati, filwaqt li jitqiesu r-riżultati tal-klassifikazzjoni tad-data approvata, ir-riżultati tal-valutazzjoni tar-riskju tal-ICT u l-kriptaġġ tal-konnessjonijiet tan-network imsemmija fl-Artikolu 6(2);

(f) 

id-disinn ta’ networks f’konformità mar-rekwiżiti tas-sigurtà tal-ICT stabbiliti mill-entità finanzjarja, filwaqt li jitqiesu l-prattiki ewlenin biex jiġu żgurati l-kunfidenzjalità, l-integrità u d-disponibbiltà tan-network;

(g) 

l-iżgurar tat-traffiku tan-network bejn in-networks interni u l-Internet u konnessjonijiet esterni oħrajn;

(h) 

l-identifikazzjoni tar-rwoli u tar-responsabbiltajiet u tal-passi għall-ispeċifikazzjoni, għall-implimentazzjoni, għall-approvazzjoni, għat-tibdil u għar-rieżami tar-regoli dwar il-firewalls u tal-filtri tal-konnessjonijiet;

(i) 

il-prestazzjoni tar-rieżamijiet tal-arkitettura tan-network u tad-disinn tas-sigurtà tan-network darba fis-sena, u perjodikament għall-mikrointrapriżi, biex jiġu identifikati l-vulnerabbiltajiet potenzjali;

(j) 

il-miżuri biex jiġu iżolati temporanjament, meta meħtieġ, is-subnetworks, u l-komponenti u l-apparati tan-network;

(k) 

l-implimentazzjoni ta’ linja bażi ta’ konfigurazzjoni sigura tal-komponenti kollha tan-network, u t-twebbis tan-network u tal-apparati tan-network f’konformità ma’ kwalunkwe struzzjoni tal-bejjiegħ, u, meta applikabbli, standards, kif iddefiniti fl-Artikolu 2, il-punt (1) tar-Regolament (UE) Nru 1025/2012, u prattiki ewlenin;

(l) 

il-proċeduri biex jiġu llimitati, imblokkati u tterminati s-sistema u s-sessjonijiet mill-bogħod wara perjodu speċifikat ta’ inattività;

(m) 

għall-ftehimiet dwar is-servizzi tan-network:

(i) 

l-identifikazzjoni u l-ispeċifikazzjoni tal-miżuri tas-sigurtà tal-ICT u tal-informazzjoni, tal-livelli ta’ servizz u tar-rekwiżiti ta’ ġestjoni tas-servizzi kollha tan-network;

(ii) 

jekk dawk is-servizzi humiex ipprovduti minn fornitur ta’ servizzi intragrupp tal-ICT jew minn fornituri terz ta’ servizzi tal-ICT.

Għall-finijiet tal-punt (h), l-entitajiet finanzjarji għandhom iwettqu r-rieżami tar-regoli dwar il-firewall u tal-filtri tal-konnessjonijiet fuq bażi regolari f’konformità mal-klassifikazzjoni stabbilita f’konformità mal-Artikolu 8(1) tar-Regolament (UE) 2022/2554 u mal-profil tar-riskju ġenerali tas-sistemi tal-ICT involuti. Għas-sistemi tal-ICT li jappoġġaw funzjonijiet kritiċi jew importanti, l-entitajiet finanzjarji għandhom jivverifikaw l-adegwatezza tar-regoli eżistenti dwar il-firewall u l-filtri ta’ konnessjoni mill-anqas kull 6 xhur.
EULAW Artikolu 14 Żgurar tal-informazzjoni fi tranżitu
-
EULAW Artikolu 14 Żgurar tal-informazzjoni fi tranżitu
-
EULAW Artikolu 35 Sigurtà tad-data, tas-sistema u tan-network

Artikolu 35

Sigurtà tad-data, tas-sistema u tan-network

L-entitajiet finanzjarji msemmija fl-Artikolu 16(1) tar-Regolament (UE) 2022/2554 għandhom, bħala parti mis-sistemi, il-protokolli u l-għodod tagħhom, jiżviluppaw u jimplimentaw salvagwardji li jiżguraw is-sigurtà tan-networks kontra l-intrużjonijiet u l-użu ħażin tad-data u li jippreżervaw id-disponibbiltà, l-awtentiċità, l-integrità u l-kunfidenzjalità tad-data. B’mod partikolari, l-entitajiet finanzjarji għandhom, filwaqt li jqisu l-klassifikazzjoni msemmija fl-Artikolu 30(1) ta’ dan ir-Regolament, jistabbilixxu dan kollu li ġej:

(a) 

l-identifikazzjoni u l-implimentazzjoni ta’ miżuri għall-protezzjoni tad-data waqt l-użu, fi tranżitu u waqt li tkun wieqfa;

(b) 

l-identifikazzjoni u l-implimentazzjoni ta’ miżuri ta’ sigurtà rigward l-użu ta’ software, mezzi għall-ħżin tad-data, sistemi u apparati ta’ punt tat-tmiem li jittrasferixxu u jaħżnu d-data tal-entità finanzjarja;

(c) 

l-identifikazzjoni u l-implimentazzjoni ta’ miżuri biex jiġu pprevenuti u individwati konnessjonijiet mhux awtorizzati man-network tal-entità finanzjarja, u biex jiġi żgurat it-traffiku tan-network bejn in-networks interni tal-entità finanzjarja u l-Internet u konnessjonijiet esterni oħrajn;

(d) 

l-identifikazzjoni u l-implimentazzjoni ta’ miżuri li jiżguraw id-disponibbiltà, l-awtentiċità, l-integrità u l-kunfidenzjalità tad-data matul it-trażmissjonijiet tan-network;

(e) 

proċess biex titħassar b’mod sigur id-data fil-bini, jew li tinħażen esternament, li l-entità finanzjarja ma għadhiex teħtieġ tiġbor jew taħżen;

(f) 

proċess biex l-apparati għall-ħżin tad-data fil-bini jew l-apparati għall-ħżin tad-data li jinħażnu esternament li jkun fihom informazzjoni kunfidenzjali jintremew b’mod sigur, jew jiġu ddekumissjonati;

(g) 

l-identifikazzjoni u l-implimentazzjoni ta’ miżuri biex jiġi żgurat li t-telexogħol u l-użu ta’ apparati ta’ punt tat-tmiem privat ma jkollhomx impatt negattiv fuq il-kapaċità tal-entità finanzjarja li twettaq l-attivitajiet kritiċi tagħha b’mod adegwat, f’waqtu u sigur.
EULAW Artikolu 35 Sigurtà tad-data, tas-sistema u tan-network

Artikolu 35

Sigurtà tad-data, tas-sistema u tan-network

L-entitajiet finanzjarji msemmija fl-Artikolu 16(1) tar-Regolament (UE) 2022/2554 għandhom, bħala parti mis-sistemi, il-protokolli u l-għodod tagħhom, jiżviluppaw u jimplimentaw salvagwardji li jiżguraw is-sigurtà tan-networks kontra l-intrużjonijiet u l-użu ħażin tad-data u li jippreżervaw id-disponibbiltà, l-awtentiċità, l-integrità u l-kunfidenzjalità tad-data. B’mod partikolari, l-entitajiet finanzjarji għandhom, filwaqt li jqisu l-klassifikazzjoni msemmija fl-Artikolu 30(1) ta’ dan ir-Regolament, jistabbilixxu dan kollu li ġej:

(a) 

l-identifikazzjoni u l-implimentazzjoni ta’ miżuri għall-protezzjoni tad-data waqt l-użu, fi tranżitu u waqt li tkun wieqfa;

(b) 

l-identifikazzjoni u l-implimentazzjoni ta’ miżuri ta’ sigurtà rigward l-użu ta’ software, mezzi għall-ħżin tad-data, sistemi u apparati ta’ punt tat-tmiem li jittrasferixxu u jaħżnu d-data tal-entità finanzjarja;

(c) 

l-identifikazzjoni u l-implimentazzjoni ta’ miżuri biex jiġu pprevenuti u individwati konnessjonijiet mhux awtorizzati man-network tal-entità finanzjarja, u biex jiġi żgurat it-traffiku tan-network bejn in-networks interni tal-entità finanzjarja u l-Internet u konnessjonijiet esterni oħrajn;

(d) 

l-identifikazzjoni u l-implimentazzjoni ta’ miżuri li jiżguraw id-disponibbiltà, l-awtentiċità, l-integrità u l-kunfidenzjalità tad-data matul it-trażmissjonijiet tan-network;

(e) 

proċess biex titħassar b’mod sigur id-data fil-bini, jew li tinħażen esternament, li l-entità finanzjarja ma għadhiex teħtieġ tiġbor jew taħżen;

(f) 

proċess biex l-apparati għall-ħżin tad-data fil-bini jew l-apparati għall-ħżin tad-data li jinħażnu esternament li jkun fihom informazzjoni kunfidenzjali jintremew b’mod sigur, jew jiġu ddekumissjonati;

(g) 

l-identifikazzjoni u l-implimentazzjoni ta’ miżuri biex jiġi żgurat li t-telexogħol u l-użu ta’ apparati ta’ punt tat-tmiem privat ma jkollhomx impatt negattiv fuq il-kapaċità tal-entità finanzjarja li twettaq l-attivitajiet kritiċi tagħha b’mod adegwat, f’waqtu u sigur.

Kwistjonijiet marbuta

Links
is related to Annual
is related to relative Control Weighting = 10
is related to Data
is related to Protect
is related to SCRM Focus Tier 2 OPERATIONAL
is related to SCRM Focus Tier 3 TACTICAL
blocks Unauthorized Access
blocks Unauthorized Modification / Loss of System Integrity
blocks Unauthorized Retention / Inability to Dispose of Data
blocks Data Loss / Integrity Compromise
blocks System / Data Compromise (Technical Vector)
blocks System / Data Compromise (Non-Technical Vector)
blocks Revenue Loss
blocks Contractual Default / Termination
blocks Loss of Competitive Advantage
blocks Reputational Harm / Loss of Stakeholder Trust
blocks Regulatory / Legal / Contractual Financial Liability
blocks Exposure from Unaddressed Vulnerabilities
blocks System / Service Compromise
blocks Failure to Support Business / Mission Objectives
blocks Unaddressed Security / Compliance Exposure
blocks Unperformed / Unowned Control Responsibilities
blocks Uncontrolled Internal Security / Privacy Exposure
blocks Uncontrolled Third-Party Security / Privacy Exposure
blocks Loss of Investigative / Evidentiary Capability
blocks Incident Persistence / Recurrence
blocks Incident Response / Recovery Cost
blocks OS Credential Dumping
blocks LSASS Memory
blocks Security Account Manager
blocks NTDS
blocks LSA Secrets
blocks Cached Domain Credentials
blocks DCSync
blocks Proc Filesystem
blocks /etc/passwd and /etc/shadow
blocks Data from Local System
blocks Data from Removable Media
blocks Exfiltration Over C2 Channel
blocks Exfiltration Over Alternative Protocol
blocks Exfiltration Over Asymmetric Encrypted Non-C2 Protocol
blocks Exfiltration Over Unencrypted Non-C2 Protocol
blocks Exfiltration Over Physical Medium
blocks Exfiltration over USB
blocks Valid Accounts
blocks Default Accounts
blocks Local Accounts
blocks Cloud Accounts
blocks Data from Information Repositories
blocks Confluence
blocks Sharepoint
blocks Customer Relationship Management Software
blocks Messaging Applications
blocks Data from Cloud Storage
blocks Application Access Token
blocks Unsecured Credentials
blocks Credentials In Files
blocks Credentials in Registry
blocks Shell History
blocks Private Keys
blocks Data Manipulation
blocks Stored Data Manipulation
blocks Runtime Data Manipulation
blocks Exfiltration Over Web Service
blocks Network Boundary Bridging
blocks Network Address Translation Traversal
blocks Data from Configuration Repository
blocks SNMP (MIB Dump)
blocks Network Device Configuration Dump
blocks Traffic Duplication
blocks Network Sniffing
blocks Proxy
blocks Domain Fronting
blocks Web Session Cookie
blocks Container API
blocks Adversary-in-the-Middle
blocks Name Resolution Poisoning and SMB Relay
blocks ARP Cache Poisoning
blocks DHCP Spoofing
blocks Evil Twin
blocks Identity Compromise / Impersonation
blocks Intellectual Property / Trade Secret Loss
blocks AI Data Confidentiality / Integrity / Provenance Loss
blocks Long-Term Confidentiality Loss from Cryptographic Obsolescence
blocks Loss of Confidentiality
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 Human Error
blocks Technical / Mechanical Failure
blocks Statutory / Regulatory / Contractual Change
blocks Product Defect / Design Failure
blocks Harvest Now / Decrypt Later (HNDL)
blocks Cryptographic Compromise / Cryptanalytic Capability Advancement
blocks OPS-09.03B
blocks OPS-19.01B
blocks OPS-34.02B
blocks CRY-04.01B
blocks CRY-04.01AS
blocks COS-06.01AC
blocks PI-01.01B
is blocked by CRY-05 Encrypting Data In Transit – Assessment Procedure
blocks SC-08 Transmission Confidentiality and Integrity
blocks SC-08(01) Cryptographic Protection
blocks SC-08 [M] Transmission Confidentiality and Integrity
blocks SC-08(01) [M] Cryptographic Protection
blocks SC-08 [H] Transmission Confidentiality and Integrity
blocks SC-08(01) [H] Cryptographic Protection
blocks 03.13.08 Transmission and Storage Confidentiality
blocks 03.13.11 Cryptographic Protection
blocks PR.DS-02 The confidentiality, integrity, and availability of data-in-transit are protected