+Interconnection Security Agreements (ISAs)
---+External System Connections
---+Internal System Connections
|
Interconnection Security Agreements (ISAs)
Description
Mechanisms exist to authorize connections from systems to other systems using Interconnection Security Agreements (ISAs), or similar methods, that document, for each interconnection:
(1) Interface characteristics;
(2) Security, compliance and resilience requirements; and;
(3) The nature of the information communicated.
Possible Solutions & Considerations
Micro-Small Business (<10 staff) / BLS Firm Size Classes 1-2
∙ Interconnection Security Agreement (ISA)
∙ Information Exchange Security Agreements (IESA)
∙ Memoranda of Understanding (MOU) / Agreement (MOA)
Small Business (10-49 staff) / BLS Firm Size Classes 3-4
∙ Interconnection Security Agreement (ISA)
∙ Information Exchange Security Agreements (IESA)
∙ Memoranda of Understanding (MOU) / Agreement (MOA)
Medium Business (50-249 staff) / BLS Firm Size Classes 5-6
∙ Interconnection Security Agreement (ISA)
∙ Information Exchange Security Agreements (IESA)
∙ Memoranda of Understanding (MOU) / Agreement (MOA)
Large Business (250-999 staff) / BLS Firm Size Classes 7-8
∙ Interconnection Security Agreement (ISA)
∙ Information Exchange Security Agreements (IESA)
∙ Memoranda of Understanding (MOU) / Agreement (MOA)
Enterprise (> 1,000 staff) / BLS Firm Size Class 9
∙ Interconnection Security Agreement (ISA)
∙ Information Exchange Security Agreements (IESA)
∙ Memoranda of Understanding (MOU) / Agreement (MOA)
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.
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.
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 authorize connections from systems to other systems using Interconnection Security Agreements (ISAs), or similar methods, that document, for each interconnection:
(1) Interface characteristics;
(2) Security, compliance and resilience requirements; and;
(3) The nature of the information communicated.
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. Forbhreathnú
| Teideal |
Caighdeán |
|
External System Connections
|
Description
Mechanisms exist to prohibit the direct connection of a sensitive system to an external network without the use of an organization-defined boundary protection device.
Possible Solutions & Considerations
Micro-Small Business (<10 staff) / BLS Firm Size Classes 1-2
∙ Document authorized external system connections
Small Business (10-49 staff) / BLS Firm Size Classes 3-4
∙ External connection inventory
∙ Connection approval policy
Medium Business (50-249 staff) / BLS Firm Size Classes 5-6
∙ Formal external system connection management process
∙ Connection authorization records
Large Business (250-999 staff) / BLS Firm Size Classes 7-8
∙ External connection governance program
∙ Automated connection inventory
Enterprise (> 1,000 staff) / BLS Firm Size Class 9
∙ Enterprise external connection governance platform
∙ Automated discovery and authorization of external connections
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.
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.
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 prohibit the direct connection of a sensitive system to an external network without the use of an organization-defined boundary protection device.
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.
|
|
Internal System Connections
|
Description
Mechanisms exist to control internal system connections through authorizing internal connections of systems and documenting, for each internal connection, the interface characteristics, security requirements and the nature of the information communicated.
Possible Solutions & Considerations
Micro-Small Business (<10 staff) / BLS Firm Size Classes 1-2
∙ Document authorized internal system connections
Small Business (10-49 staff) / BLS Firm Size Classes 3-4
∙ Internal network connection documentation
∙ Connection authorization process
Medium Business (50-249 staff) / BLS Firm Size Classes 5-6
∙ Formal internal connection management policy
∙ Network topology documentation
Large Business (250-999 staff) / BLS Firm Size Classes 7-8
∙ Enterprise CMDB with internal connection mapping
∙ Automated network topology discovery
Enterprise (> 1,000 staff) / BLS Firm Size Class 9
∙ Enterprise CMDB (e.g., ServiceNow)
∙ Automated network discovery (e.g., Nmap, SolarWinds)
∙ Connection governance program
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.
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.
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 control internal system connections through authorizing internal connections of systems and documenting, for each internal connection, the interface characteristics, security requirements and the nature of the information communicated.
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.1 Tagairtí
1.2 Ceanglais aitheanta
1.3 Rialacháin ghaolmhara
2. Ceanglais aitheanta
Ceanglais
| Foinse |
Ceanglas |
3. Rialacháin ghaolmhara
Rialacháin
| Foinse |
Rialáil |
|
EULAW
|
Airteagal 13 Bainistiú slándála gréasáin
Airteagal 13
Bainistiú slándála gréasáin
Mar chuid de na coimircí lena n-áirithítear slándáil gréasán in aghaidh ionraí agus mí-úsáid sonraí, déanfaidh eintitis airgeadais beartais, nósanna imeachta, prótacail agus uirlisí bainistithe slándála gréasáin a fhorbairt, a dhoiciméadú agus a chur chun feidhme, lena n-áirítear na nithe uile seo a leanas:
(a)
córais agus gréasáin TFC a leithscaradh agus a dheighilt, agus na nithe seo a leanas á gcur san áireamh:
(i)
criticiúlacht nó tábhacht na feidhme a dtacaíonn na córais agus na gréasáin TFC sin léi;
(ii)
an t-aicmiú a bhunaítear i gcomhréir le hAirteagal 8(1) de Rialachán (AE) 2022/2554;
(iii)
próifíl riosca fhoriomlán sócmhainní TFC a úsáideann na córais agus na gréasáin TFC sin;
(b)
naisc ghréasáin agus sreabha sonraí uile an eintitis airgeadais a dhoiciméadú;
(c)
gréasán scartha tiomnaithe a úsáid chun sócmhainní TFC a riar;
(d)
rialuithe rochtana gréasáin a shainaithint agus a chur chun feidhme chun naisc a dhéanfaidh aon ghaireas nó córas neamhúdaraithe le gréasán an eintitis airgeadais, nó a dhéanfaidh aon chríochphointe nach gcomhlíonann ceanglais slándála an eintitis airgeadais, a chosc agus a bhrath;
(e)
criptiú a dhéanamh ar naisc ghréasáin a théann trí ghréasáin chorparáide, gréasáin phoiblí, gréasáin tí, gréasáin tríú páirtí agus gréasáin gan sreang, le haghaidh na bprótacal cumarsáide a úsáidtear, agus torthaí an aicmithe sonraí fhormheasta, torthaí an mheasúnaithe riosca TFC agus an criptiú ar naisc ghréasáin dá dtagraítear in Airteagal 6(2) á gcur san áireamh;
(f)
gréasáin a dhearadh i gcomhréir leis na ceanglais slándála TFC arna leagan síos ag an eintiteas airgeadais, agus cleachtais atá chun tosaigh á gcur san áireamh chun rúndacht, sláine agus infhaighteacht an ghréasáin a áirithiú;
(g)
trácht gréasáin idir na gréasáin inmheánacha agus an t-idirlíon agus naisc sheachtracha eile a dhaingniú;
(h)
na róil, na freagrachtaí agus na céimeanna a shainaithint chun rialacha maidir le balla dóiteáin agus scagairí nasc a shonrú, a chur chun feidhme, a fhormheas, a athrú agus a athbhreithniú;
(i)
athbhreithnithe a dhéanamh uair amháin sa bhliain, agus go tréimhsiúil i gcás micrifhiontar, ar ailtireacht líonraí agus ar an dearadh slándála gréasáin chun leochaileachtaí féideartha a bhrath;
(j)
na bearta chun fo-ghréasáin, agus comhpháirteanna agus gairis ghréasáin, a leithlisiú go sealadach i gcás inar gá;
(k)
bunlíne cumraíochta sláine gach comhpháirte gréasáin a chur chun feidhme, agus an gréasán agus gairis ghréasáin a chruachan i gcomhréir le haon treoir ón díoltóir agus, i gcás inarb infheidhme, le caighdeáin a shainítear in Airteagal 2, pointe (1), de Rialachán (AE) Uimh. 1025/2012, agus le cleachtais atá chun tosaigh;
(l)
na nósanna imeachta chun seisiúin chórais agus chianda a theorannú, a ghlasáil agus a chríochnú tar éis tréimhse shonraithe neamhghníomhaíochta;
(m)
i gcás comhaontuithe seirbhísí gréasáin:
(i)
bearta slándála faisnéise agus TFC, leibhéil seirbhíse agus ceanglais bhainistíochta na seirbhísí gréasáin uile a shainaithint agus a shonrú;
(ii)
cé acu soláthraí seirbhísí TFC inghrúpa nó soláthraithe seirbhísí TFC tríú páirtí a sholáthraíonn na seirbhísí sin.
Chun críocha phointe (h), déanfaidh eintitis airgeadais an t-athbhreithniú ar rialacha maidir le balla dóiteáin agus scagairí nasc ar bhonn tráthrialta i gcomhréir leis an aicmiú a bhunaítear i gcomhréir le hAirteagal 8(1) de Rialachán (AE) 2022/2554 agus le próifíl riosca fhoriomlán na gcóras TFC lena mbaineann. I gcás córais TFC lena dtacaítear le feidhmeanna criticiúla nó tábhachtacha, fíoróidh eintitis airgeadais gach 6 mhí ar a laghad go bhfuil na rialacha atá ann cheana maidir le balla dóiteáin agus scagairí nasc leordhóthanach.
|
Saincheisteanna nasctha
- Secure Controls Framework -
"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.
|