+Alignment With Enterprise Architecture

Alignment With Enterprise Architecture

Description

Mechanisms exist to develop an enterprise architecture, aligned with industry-recognized leading practices, with consideration for security, compliance and resilience principles that addresses risk to organizational operations, assets, individuals and other organizations.

Possible Solutions & Considerations

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

∙ Follow secure coding basics
∙ Document security decisions

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

∙ Secure design checklist
∙ Basic threat modeling

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

∙ Enterprise architecture committee

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

∙ Enterprise architecture committee

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

∙ Enterprise architecture committee

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

Secure Engineering & Architecture (SEA) 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 SEA domain capabilities are formally documented and centrally-managed by the entity.
▪ Standardized Operating Procedures (SOP) associated with SEA 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 SEA domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD).
▪ Secure engineering and architecture-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines).
▪ Secure engineering and architecture 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 and/or cybersecurity personnel define entity-specific secure engineering practices to protect the Confidentiality, Integrity, Availability and Safety (CIAS) of the entity's TAASD.
▪ IT and/or cybersecurity personnel align secure engineering practices with the entity's broader IT architecture practices.
▪ IT and/or cybersecurity personnel use secure engineering practices to influence Secure Baseline Configurations (SBC).

Level 3 Well Defined

Secure Engineering & Architecture (SEA) 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 SEA 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 SEA domain capabilities are well-documented and kept current by process owners.
▪ A cybersecurity engineering / architecture team, or similar function, is appropriately staffed and supported to implement and maintain RSK domain capabilities.
▪ Technology is leveraged to enhance the efficiency and accuracy of secure engineering management operations (e.g., project management solution).
▪ 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 SEA 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 secure engineering principles on all applicable Technology Assets, Applications and/or Services (TAAS).
▪ An implemented and operational capability exists to develop an enterprise architecture, aligned with industry-recognized leading practices, with consideration for security, compliance and resilience principles that addresses risk to organizational operations, assets, individuals and other organizations.

Level 4 Quantitatively Controlled

Secure Engineering & Architecture (SEA) 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. Vue d’ensemble

1.1 Références

1.2 Exigences identifiées

1.3 Réglementations associées

2. Exigences identifiées

Exigences

3. Réglementations associées

Réglementations
EULAW Article 13 Gestion de la sécurité des réseaux

Article 13

Gestion de la sécurité des réseaux

Dans le cadre des garanties de sécurité des réseaux contre les intrusions et l’utilisation abusive de données, les entités financières élaborent, documentent et mettent en œuvre des politiques, des procédures, des protocoles et des outils de gestion de la sécurité des réseaux comprenant l’ensemble des éléments suivants:

a) 

la séparation et la segmentation des systèmes et réseaux de TIC, compte tenu:

i) 

de la criticité ou de l’importance de la fonction que soutiennent ces systèmes et réseaux de TIC;

ii) 

de la classification établie conformément à l’article 8, paragraphe 1, du règlement (UE) 2022/2554;

iii) 

du profil de risque global des actifs de TIC qui utilisent ces systèmes et réseaux de TIC;

b) 

la documentation de l’ensemble des connexions réseau et des flux de données de l’entité financière;

c) 

l’utilisation d’un réseau distinct et spécifique pour l’administration des actifs de TIC;

d) 

la définition et la mise en œuvre de contrôles d’accès au réseau afin de prévenir et de détecter les connexions au réseau de l’entité financière à partir de tout appareil ou système non autorisé, ou de tout point de terminaison ne répondant pas aux exigences de l’entité financière en matière de sécurité;

e) 

le chiffrement des connexions au réseau transitant par des réseaux d’entreprise, des réseaux publics, des réseaux nationaux, des réseaux tiers et des réseaux sans fil, pour les protocoles de communication utilisés, en tenant compte des résultats de la classification de données approuvée, des résultats de l’évaluation du risque lié aux TIC et du chiffrement des connexions au réseau prévu par l’article 6, paragraphe 2;

f) 

une conception du réseau conforme aux exigences en matière de sécurité des TIC définies par l’entité financière, tenant compte des pratiques de pointe afin de garantir la confidentialité, l’intégrité et la disponibilité du réseau;

g) 

la sécurisation du trafic entre les réseaux internes et l’internet et d’autres connexions externes;

h) 

la définition des rôles et responsabilités et des étapes de la spécification, de la mise en œuvre, de l’approbation, de la modification et du réexamen des règles de pare-feu et des filtres de connexion;

i) 

la réalisation d’examens de l’architecture du réseau et de la conception de la sécurité du réseau une fois par an, et périodiquement pour les microentreprises, afin de détecter les vulnérabilités potentielles;

j) 

des mesures visant à isoler temporairement, si nécessaire, les sous-réseaux et les composants et dispositifs de réseau;

k) 

la mise en œuvre d’une configuration sécurisée de référence incluant tous les composants du réseau, et le renforcement du réseau et des dispositifs de réseau conformément aux éventuelles instructions du vendeur, aux normes telles que définies à l’article 2, point 1), du règlement (UE) no 1025/2012, le cas échéant, et aux pratiques de pointe;

l) 

les procédures de limitation, de verrouillage et d’arrêt du système et des sessions à distance après une période déterminée d’inactivité;

m) 

pour les accords de services de réseau:

i) 

l’indication et la spécification des mesures de sécurité des TIC et de l’information, des niveaux de service et des exigences en matière de gestion de tous les services de réseau;

ii) 

une indication précisant si ces services sont fournis par un prestataire intra-groupe de services TIC ou par des prestataires tiers de services TIC.

Aux fins du point h), les entités financières procèdent à un réexamen régulier des règles de pare-feu et des filtres de connexion, conformément à la classification établie en application de l’article 8, paragraphe 1, du règlement (UE) 2022/2554 et au profil de risque global des systèmes de TIC concernés. Pour les systèmes de TIC qui soutiennent des fonctions critiques ou importantes, les entités financières vérifient l’adéquation des règles de pare-feu et des filtres de connexion existants au moins tous les six mois.
EULAW Article 9 Protection et prévention
-
EULAW Article 9 Protection et prévention
-
EULAW Article 9 3

3.   In order to achieve the objectives referred to in paragraph 2, financial entities shall use ICT solutions and processes that are appropriate in accordance with Article 4. Those ICT solutions and processes shall:

(a)

ensure the security of the means of transfer of data;

(b)

minimise the risk of corruption or loss of data, unauthorised access and technical flaws that may hinder business activity;

(c)

prevent the lack of availability, the impairment of the authenticity and integrity, the breaches of confidentiality and the loss of data;

(d)

ensure that data is protected from risks arising from data management, including poor administration, processing-related risks and human error.

Tickets liés

Liens
is related to Annual
is related to relative Control Weighting = 07
is related to Technology
is related to Protect
is related to SCRM Focus Tier 3 TACTICAL
blocks Loss of Accountability / Attribution
blocks Excessive or Unauthorized Privilege
blocks Unauthorized Privilege Elevation
blocks Unauthorized Access
blocks Loss, Theft or Damage of Assets
blocks Unauthorized Modification / Loss of System Integrity
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 System / Service Compromise
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 Loss of Investigative / Evidentiary Capability
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 Exploitation for Privilege Escalation
blocks Drive-by Compromise
blocks Exploit Public-Facing Application
blocks Exploitation for Client Execution
blocks Exploitation of Remote Services
blocks Exploitation for Stealth
blocks Exploitation for Credential Access
blocks Authentication Package
blocks Security Support Provider
blocks LSASS Driver
blocks Modify Authentication Process
blocks Domain Controller Authentication
blocks Escape to Host
is related to relative Control Weighting = 09
is related to Process
is related to SCRM Focus Tier 1 STRATEGIC
is related to SCRM Focus Tier 2 OPERATIONAL
blocks Regulatory / Legal / Contractual Financial Liability
blocks Failure to Achieve Strategic / Mission Objectives
blocks Inability to Demonstrate Due Diligence / Due Care
blocks Concentration / Single-Point Dependency Failure
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 Dysfunctional Management Practices
blocks Human Error
blocks Statutory / Regulatory / Contractual Change
blocks Fraud, Corruption and/or Intentional Criminal Conduct
blocks Conflict of Interest (COI) / Undue Influence / Insider Misconduct
blocks Economic Shock / Market Disruption
blocks Workforce Shortage / Loss of Critical Skills / Labor Disruption
blocks OPS-22.01AC
blocks Regulatory / Legal / Contractual Financial Liability
blocks Failure to Achieve Strategic / Mission Objectives
blocks Inability to Demonstrate Due Diligence / Due Care
blocks Concentration / Single-Point Dependency Failure
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 Dysfunctional Management Practices
blocks Human Error
blocks Statutory / Regulatory / Contractual Change
blocks Fraud, Corruption and/or Intentional Criminal Conduct
blocks Conflict of Interest (COI) / Undue Influence / Insider Misconduct
blocks Economic Shock / Market Disruption
blocks Workforce Shortage / Loss of Critical Skills / Labor Disruption
blocks OPS-22.01AC
is blocked by SEA-04 Alignment With Enterprise Architecture – Assessment Procedure
blocks PL-08 Security and Privacy Architectures
blocks PM-07 Enterprise Architecture
blocks PL-08 [M] Security and Privacy Architectures
blocks PL-08 [H] Security and Privacy Architectures
blocks PL-08 [P] Security and Privacy Architectures
blocks PM-07 [P] Enterprise Architecture
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 03.16.01 Security Engineering Principles
blocks PR.IR Technology Infrastructure Resilience
blocks PR.IR-01 Networks and environments are protected from unauthorized logical access and usage
blocks PR.IR-03 Mechanisms are implemented to achieve resilience requirements in normal and adverse situations
  • 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.