+Host Containment
|
Host Containment
Description
Automated mechanisms exist to enforce host containment protections that revoke or quarantine a host's access to the network.
Possible Solutions & Considerations
Micro-Small Business (<10 staff) / BLS Firm Size Classes 1-2
∙ Isolate suspected compromised systems from the network immediately
Small Business (10-49 staff) / BLS Firm Size Classes 3-4
∙ Host isolation procedure for incident response
∙ Documented steps to isolate compromised hosts
Medium Business (50-249 staff) / BLS Firm Size Classes 5-6
∙ Formal host containment policy and procedure
∙ EDR-based isolation capability
Large Business (250-999 staff) / BLS Firm Size Classes 7-8
∙ EDR with automated host isolation (e.g., CrowdStrike, SentinelOne)
∙ IR playbook for containment
Enterprise (> 1,000 staff) / BLS Firm Size Class 9
∙ Enterprise EDR/XDR with automated host containment
∙ SOAR-orchestrated isolation workflows
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
SCR-CMM Level 2 criteria definitions are not available for this control:
▪ A reasonable person would conclude a well-defined and standardized process is required.
▪ At this level of maturity, the “requirements-driven” nature of performing the control is focused on a localized and/or regionalized implementation, not uniform and consistent across the organization.
▪ Requirements are narrowly scoped for applicability and are primarily derived from compliance obligations (e.g., laws, regulations and contracts).
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 automatically enforce host containment protections that revoke or quarantine a host's access to the network.
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. Ħarsa ġenerali
1.1 Referenzi
1.2 Rekwiżiti identifikati
1.3 Regolamenti relatati
2. Rekwiżiti identifikati
3. Regolamenti relatati
Regolamenti
| Sors |
Regolamentazzjoni |
|
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.
|
Kwistjonijiet marbuta
- Secure Controls Framework -
EN: GRCA includes the Secure Controls Framework® (SCF) content, © Secure Controls Framework Council, LLC, used under the Creative Commons Attribution-NoDerivatives 4.0 International Public License. SCF control numbers, names, descriptions and mappings appear exactly as published by the SCF Council – https://securecontrolsframework.com. GRCA may group or reorder SCF content for display, which does not change SCF content; the mappings are shown as links to the frameworks they name. Learn more at https://securecontrolsframework.com.
DE: GRCA enthält Inhalte des Secure Controls Framework® (SCF), © Secure Controls Framework Council, LLC, genutzt unter der Creative Commons Attribution-NoDerivatives 4.0 International Public License. Nummern, Namen, Beschreibungen und Zuordnungen der SCF-Controls erscheinen genau so, wie der SCF Council sie veröffentlicht – https://securecontrolsframework.com. GRCA gruppiert oder sortiert SCF-Inhalte für die Anzeige, ohne sie zu verändern; die Zuordnungen erscheinen als Verknüpfungen zu den genannten Regelwerken. Mehr unter https://securecontrolsframework.com.
|