+Network Security Controls (NSC)

Network Security Controls (NSC)

Description

Mechanisms exist to develop, govern & update procedures to facilitate the implementation of Network Security Controls (NSC).

Possible Solutions & Considerations

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

∙ Basic firewall (home router or free pfSense)
∙ Network security policy

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

∙ Small business firewall (e.g., Cisco Meraki, Fortinet FortiGate)
∙ Network security policy

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

∙ Next-gen firewall (NGFW)
∙ Network segmentation
∙ IDS/IPS
∙ Network security standards

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

∙ Enterprise NGFW (e.g., Palo Alto Networks, Fortinet)
∙ Network security program
∙ IDS/IPS
∙ NAC

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

∙ Enterprise NGFW with threat intelligence feeds
∙ Zero-trust network architecture
∙ SIEM integration
∙ NAC
∙ SD-WAN

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.
▪ Administrative processes are used to configure boundary devices (e.g., firewalls and routers) to deny network traffic by default and allow network traffic by exception (e.g., deny all and permit by exception).
▪ Administrative processes enforce the use of human reviews for Access Control Lists (ACLs) and similar rulesets on a routine basis.
▪ Internet-facing technologies are governed no differently from internal network assets.
▪ 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 capability exists to develop, govern & update procedures to facilitate the implementation of Network Security Controls (NSC).

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. Ülevaade

1.1 Viited

1.2 Tuvastatud nõuded

1.3 Seotud regulatsioonid

2. Tuvastatud nõuded

Nõuded

3. Seotud regulatsioonid

Regulatsioonid
EULAW Artikkel 13 Võrgu turvalisuse haldamine

Artikkel 13

Võrgu turvalisuse haldamine

Finantssektori ettevõtjad töötavad võrgu turvalisuse tagamiseks kehtestatavate sissetungi ja andmete väärkasutamise vastaste kaitsemeetmete osana välja ja dokumenteerivad võrgu turvalisuse haldamise põhimõtted, menetlused, protokollid ja vahendid, mis peavad hõlmama kõike järgmist:

a) 

IKT-süsteemide ja võrkude eraldamine ja segmentimine, võttes arvesse

i) 

asjaomaste IKT-süsteemide ja võrkude toetatavate funktsioonide kriitilist tähtsust või olulisust,

ii) 

määruse (EL) 2022/2554 artikli 8 lõike 1 kohast liigitust,

iii) 

neid IKT-süsteeme ja võrke kasutavate IKT-varade üldist riskiprofiili;

b) 

finantssektori ettevõtja kõigi võrguühenduste ja andmevoogude dokumenteerimine;

c) 

eraldi ja spetsiaalse võrgu kasutamine IKT-varade haldamiseks;

d) 

võrkupääsu reguleerimise kindlaksmääramine ja rakendamine, et ära hoida ja avastada ühendused finantssektori ettevõtja võrguga pääsuloata seadme või süsteemi kaudu või mis tahes lõpp-punkti kaudu, mis ei vasta finantssektori ettevõtja turvanõuetele;

e) 

kasutatavate sideprotokollide jaoks sisevõrke, üldkasutatavaid võrke, riigisiseseid võrke, kolmandate isikute võrke ja traadita võrke läbivate võrguühenduste krüptimine, võttes arvesse heakskiidetud andmeliigituse ja IKT-riski hindamise tulemusi ning artikli 6 lõikes 2 osutatud võrguühenduste krüptimist;

f) 

võrgu projekteerimine kooskõlas finantssektori ettevõtja kehtestatud IKT turvanõuetega, võttes arvesse juhtivaid tavasid, et tagada võrgu konfidentsiaalsus, terviklus ja kättesaadavus;

g) 

sisevõrgu ning interneti ja muude välisühenduste vahelise võrguliikluse turvalisuse tagamine;

h) 

tulemüüri reeglite ja ühendusfiltrite kindlaksmääramiseks, rakendamiseks, heakskiitmiseks, muutmiseks ja läbivaatamiseks rollide ja vastutusvaldkondade ning etappide kindlaksmääramine;

i) 

võrguarhitektuuri ja võrgu sisseprojekteeritud turbe meetmete läbivaatamine kord aastas ning mikroettevõtjate puhul perioodiliselt, et teha kindlaks võimalikud nõrkused;

j) 

meetmed, et vajaduse korral ajutiselt isoleerida alamvõrgud ning võrgukomponendid ja -seadmed;

k) 

kõigi võrgukomponentide turvalise konfigureerimise lähtealuse rakendamine ning võrgu ja võrguseadmete tugevdamine kooskõlas teenuseosutaja juhistega, määruse (EL) nr 1025/2012 artikli 2 punktis 1 määratletud standarditega (kui see on asjakohane) ja juhtivate tavadega;

l) 

menetlused süsteemi- ja kaugseansside piiramiseks, lukustamiseks ja lõpetamiseks pärast kindlaksmääratud jõudeolekuperioodi möödumist;

m) 

võrguteenuste lepingute puhul

i) 

IKT-turvameetmete ja infoturbe meetmete, teenustasemete ja juhtimisnõuete kindlaksmääramine ja täpsustamine kõigi võrguteenuste puhul,

ii) 

teave selle kohta, kas neid teenuseid osutab kontsernisisene IKT-teenuste osutaja või osutavad neid kolmandast isikust IKT-teenuste osutajad.

Punkti h kohaldamisel vaatavad finantssektori ettevõtjad tulemüüri reeglid ja ühendusfiltrid korrapäraselt läbi, võttes arvesse määruse (EL) 2022/2554 artikli 8 lõike 1 kohast liigitust ja asjaomaste IKT-süsteemide üldist riskiprofiili. Kriitilise tähtsusega või olulisi funktsioone toetavate IKT-süsteemide puhul kontrollivad finantssektori ettevõtjad kehtivate tulemüüri reeglite ja ühendusfiltrite asjakohasust vähemalt iga kuue kuu tagant.
EULAW Artikkel 35 Andmete, süsteemide ja võrgu turvalisus

Artikkel 35

Andmete, süsteemide ja võrgu turvalisus

Määruse (EL) 2022/2554 artikli 16 lõikes 1 osutatud finantssektori ettevõtjad töötavad oma süsteemide, protokollide ja vahendite osana välja sissetungi ja andmete väärkasutamise vastased kaitsemeetmed, millega tagatakse võrkude turvalisus ning säilitatakse andmete kättesaadavus, autentsus, terviklus ja konfidentsiaalsus, ning rakendavad neid meetmeid. Eelkõige näevad finantssektori ettevõtjad käesoleva määruse artikli 30 lõikes 1 osutatud liigitust arvesse võttes ette kõik järgmise:

a) 

kasutatavate, edastatavate ja jõudeolekus andmete kaitsmise meetmete kindlaksmääramine ja rakendamine;

b) 

finantssektori ettevõtja andmete edastamiseks ja säilitamiseks kasutatava tarkvara, andmekandjate, süsteemide ja lõppseadmete kasutamisega seotud turvameetmete kindlaksmääramine ja rakendamine;

c) 

selliste meetmete kindlaksmääramine ja rakendamine, millega hoitakse ära ja avastatakse loata ühendused finantssektori ettevõtja võrguga ning tagatakse finantssektori ettevõtja sisevõrgu ning interneti ja muude välisühenduste vahelise võrguliikluse turvalisus;

d) 

selliste meetmete kindlaksmääramine ja rakendamine, mis tagavad andmete kättesaadavuse, autentsuse, tervikluse ja konfidentsiaalsuse võrguedastuse ajal;

e) 

selliste finantssektori ettevõtja ruumides või väljaspool säilitatavate andmete turvalise kustutamise protsess, mida finantssektori ettevõtjal ei ole enam vaja koguda või säilitada;

f) 

finantssektori ettevõtja ruumides või mujal asuvate konfidentsiaalset teavet sisaldavate andmesalvestusseadmete turvalise likvideerimise või kasutusest kõrvaldamise protsess;

g) 

selliste meetmete kindlaksmääramine ja rakendamine, millega tagatakse, et kaugtöö ja isiklike lõppseadmete kasutamine ei kahjusta finantssektori ettevõtja suutlikkust teha asjakohaselt, õigeaegselt ja turvaliselt oma kriitilise tähtsusega toiminguid.
EULAW Artikkel 21 Küberturvalisuse riskijuhtimismeetmed
-

Lingitud teemad

Lingid
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 3 TACTICAL
blocks Unauthorized Privilege Elevation
blocks Unauthorized Access
blocks Loss, Theft or Damage of Assets
blocks Unauthorized Retention / Inability to Dispose of Data
blocks Business / Service Interruption
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 Failure to Support Business / Mission Objectives
blocks Unaddressed Security / Compliance Exposure
blocks Uncontrolled Internal Security / Privacy Exposure
blocks Uncontrolled Third-Party Security / Privacy Exposure
blocks Lack of oversight of internal controls
blocks Lack of oversight of third-party controls
blocks Incident Response / Recovery Cost
blocks Third-Party Cybersecurity Compromise / Exposure
blocks Third-Party Physical Security Disruption / Exposure
blocks Sub-Tier / Fourth-Party Supply Chain Exposure
blocks Third-Party Legal / Compliance Exposure
blocks Harm from Unauthorized / Unintended Product or Service Use
blocks Third-Party Dependency Failure
is related to relative Control Weighting = 10
is related to Govern
is related to SCRM Focus Tier 1 STRATEGIC
is related to SCRM Focus Tier 2 OPERATIONAL
blocks Exposure from Unaddressed Vulnerabilities
blocks System / Service Compromise
blocks Loss of Authorization / Certification / License
blocks Unperformed / Unowned Control Responsibilities
blocks Inability to Demonstrate Due Diligence / Due Care
blocks Unreliable Assurance / Decision Information
blocks Undetected / Delayed Detection of Adverse Activity
blocks Lack of a security-minded workforce
blocks Loss of Confidentiality
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 Malicious Cyber Activity
blocks Dysfunctional Management Practices
blocks Human Error
blocks Statutory / Regulatory / Contractual Change
blocks Conflict of Interest (COI) / Undue Influence / Insider Misconduct
blocks Workforce Shortage / Loss of Critical Skills / Labor Disruption
blocks COS-02.01B
blocks COS-03.03B
is blocked by NET-02 Network Security Controls (NSC) – Assessment Procedure
blocks SC-01 Policy and Procedures
blocks SC-01 [L] Policy and Procedures
blocks SC-01 [M] Policy and Procedures
blocks SC-01 [H] Policy and Procedures
blocks 03.01.12 Remote Access
blocks 03.01.16 Wireless Access
blocks 03.01.18 Access Control for Mobile Devices
blocks 03.13.01 Boundary Protection
blocks PR.IR-01 Networks and environments are protected from unauthorized logical access and usage
  • 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.