+Security, Compliance & Resilience Governance Policy
|
Security, Compliance & Resilience Governance Policy
Description
Mechanisms exist to establish a formal, documented security, compliance and resilience governance policy that:
(1) Conveys executive management's intent;
(2) Provides organizational direction and expected behaviors;
(3) Is reviewed at least annually; and
(4) Is updated, as necessary, to adapt to evolving risks, threats and other changes that affect the organization.
Possible Solutions & Considerations
Micro-Small Business (<10 staff) / BLS Firm Size Classes 1-2
∙ ComplianceForge - Security, Compliance & Resilience Program (SCRP) (https://complianceforge.com)
∙ Executive-approved written policy with documented annual review
Small Business (10-49 staff) / BLS Firm Size Classes 3-4
∙ ComplianceForge - Security, Compliance & Resilience Program (SCRP) (https://complianceforge.com)
∙ Executive-approved written policy with documented annual review
∙ Policy acknowledgement tracking (e.g., HR onboarding records)
Medium Business (50-249 staff) / BLS Firm Size Classes 5-6
∙ ComplianceForge - Security, Compliance & Resilience Program (SCRP) (https://complianceforge.com)
∙ GRC solution (e.g., SCFConnect, Cyturus, SureCloud, SimpleRisk, Ignyte, ZenGRC, Galvanize, MetricStream, Archer, etc.) for policy lifecycle management
∙ Documented annual policy review with version control
Large Business (250-999 staff) / BLS Firm Size Classes 7-8
∙ ComplianceForge - Security, Compliance & Resilience Program (SCRP) (https://complianceforge.com)
∙ GRC solution (e.g., SCFConnect, Cyturus, SureCloud, SimpleRisk, Ignyte, ZenGRC, Galvanize, MetricStream, Archer, etc.) for policy lifecycle management
∙ Policy governance committee with formal annual review and approval workflow
∙ Automated policy attestation and acknowledgement tracking
Enterprise (> 1,000 staff) / BLS Firm Size Class 9
∙ Steering committee
∙ ComplianceForge - Security, Compliance & Resilience Program (SCRP) (https://complianceforge.com)
∙ Enterprise GRC platform (e.g., Cyturus, Archer, MetricStream, ServiceNow IRM) for policy lifecycle management
∙ Automated policy attestation, exception tracking and change history
∙ Annual executive approval and board-level reporting
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
Cybersecurity & Data Protection Governance (GOV) 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 GOV domain capabilities are formally documented and centrally-managed by the entity.
▪ Standardized Operating Procedures (SOP) associated with GOV 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 GOV domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD).
▪ Governance-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines).
▪ No formal Governance, Risk & Compliance (GRC) team exists. GRC roles are assigned to existing IT and/or cybersecurity personnel.
Level 3 Well Defined
Cybersecurity & Data Protection Governance (GOV) 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 GOV 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 GOV domain capabilities are well-documented and kept current by process owners.
▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, is appropriately staffed and supported to implement and maintain GOV 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).
▪ Technology is leveraged to enhance the efficiency and accuracy of governance, risk management and compliance operations (e.g., GRC platform).
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ú
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 5 1
1. Beidh creat rialachais agus rialaithe inmheánaigh i bhfeidhm ag eintitis airgeadais lena n-áirithítear bainistíocht éifeachtach stuama i gcás gach riosca TFC, i gcomhréir le hAirteagal 6(4), chun ardchaighdeán athléimneachta digití oibríochtúla a bhaint amach.
|
|
EULAW
|
Airteagal 9 4
4. Mar chuid de chreat bainistíochta riosca TFC dá dtagraítear in Airteagal 6(1), déanfaidh eintitis airgeadais na nithe seo a leanas:
|
(a)
|
beartas slándála faisnéise a fhorbairt agus a dhoiciméadú lena sainítear rialacha chun infhaighteacht, barántúlacht, sláine agus rúndacht sonraí, sócmhainní faisnéise agus sócmhainní TFC, lena n-áirítear cinn a gcustaiméirí, a chosaint, i gcás inarb infheidhme;
|
|
(b)
|
i gcomhréir le cur chuige bunaithe ar riosca, struchtúr bainistíochta fónta gréasáin agus bonneagair a bhunú trí úsáid a bhaint as teicnící, modhanna agus prótacail iomchuí ar a bhféadfar a áireamh sásraí uathoibrithe a chur chun feidhme chun sócmhainní faisnéise, a ndearnadh difear dóibh, a scaradh amach i gcás cibirionsaithe;
|
|
(c)
|
beartais a chur i bhfeidhm lena ndéantar an rochtain fhisiciúil nó loighciúil ar shócmhainní faisnéise agus sócmhainní TFC a theorannú dá bhfuil riachtanach le haghaidh feidhmeanna agus gníomhaíochtaí dlisteanacha formheasta amháin, agus sraith beartas, nósanna imeachta agus rialuithe a bhunú chuige sin lena dtugtar aghaidh ar chearta rochtana agus lena n-áirithítear riarachán fónta orthu sin;
|
|
(d)
|
beartais agus prótacail le haghaidh sásraí láidre fíordheimhnithe a chur chun feidhme, bunaithe ar chaighdeáin ábhartha agus ar chórais thiomnaithe rialuithe, agus bearta cosanta i ndáil le heochracha cripteagrafacha trína ndéantar sonraí a chriptiú bunaithe ar thorthaí próiseas formheasta aicmithe sonraí agus measúnaithe riosca TFC;
|
|
(e)
|
beartais, nósanna imeachta agus rialuithe doiciméadaithe a chur chun feidhme le haghaidh bainistíocht athruithe TFC, lena n-áirítear athruithe ar bhogearraí, crua-earraí, comhpháirteanna dochtearraí, paraiméadair ar chórais nó paraiméadair slándála, atá bunaithe ar chur chuige measúnaithe riosca agus mar chuid dhílis de phróiseas foriomlán bainistíochta athruithe an eintitis airgeadais, chun a áirithiú go ndéanfar gach athrú ar chórais TFC a thaifeadadh, a thástáil, a mheasúnú, a fhormheas, a chur chun feidhme agus a fhíorú ar bhealach rialaithe;
|
|
(f)
|
beartais iomchuí chuimsitheacha dhoiciméadaithe a bheith acu maidir le paistí agus nuashonruithe.
|
Chun críocha na chéad fhomhíre, pointe (b), ceapfaidh eintitis airgeadais an bonneagar nasctha gréasáin ar bhealach lenar féidir é a ghearradh ar an toirt nó a dheighilt chun tógálacht a íoslaghdú agus a chosc, go háirithe i gcás próisis airgeadais idirnasctha.
Chun críocha na chéad fhomhíre, pointe (e), déanfar próiseas bainistíochta athruithe TFC a fhormheas ag línte bainistíochta iomchuí agus beidh prótacail shonracha i bhfeidhm aige.
|
|
EULAW
|
Airteagal 16 1
1. Ní bheidh feidhm ag Airteagail 5 go 15 den Rialachán seo maidir le gnólachtaí infheistíochta beaga agus neamh-idirnasctha, institiúidí íocaíochta atá díolmhaithe de bhun Threoir (AE) 2015/2366; institiúidí atá díolmhaithe de bhun Threoir 2013/36/AE a chinn na Ballstáit gan an rogha dá dtagraítear in Airteagal 2(4) den Rialachán seo a fheidhmiú ina leith; institiúidí ríomh-airgid atá díolmhaithe de bhun Threoir 2009/110/CE; agus institiúidí beaga um sholáthar pinsean ceirde.
Gan dochar don chéad fhomhír, déanfaidh na heintitis a liostaítear sa chéad fhomhír an méid seo a leanas:
|
(a)
|
creat bainistíochta riosca TFC fónta agus doiciméadaithe a chur ar bun agus a choinneáil, ar creat é lena dtabharfar mionsonraí maidir leis na sásraí agus na bearta a bhfuil sé d’aidhm acu riosca TFC a bhainistiú go tapa, go héifeachtúil agus go cuimsitheach, lena n-áirítear chun na comhpháirteanna agus bonneagair fhisiciúla ábhartha a chosaint;
|
|
(b)
|
faireachán leanúnach a dhéanamh ar shlándáil agus feidhmiú córais TFC uile;
|
|
(c)
|
tionchar riosca TFC a íoslaghdú trí úsáid a bhaint as córais, prótacail agus uirlisí TFC atá fónta, athléimneach agus nuashonraithe agus atá iomchuí chun tacú le feidhmíocht a ngníomhaíochtaí agus soláthar seirbhísí agus chun infhaighteacht, barántúlacht, sláine agus rúndacht na sonraí sna córais gréasáin agus faisnéise a chosaint ar bhealach leordhóthanach;
|
|
(d)
|
a fhágáil go bhféadfar foinsí riosca TFC agus aimhrialtachtaí sna córais gréasáin agus faisnéise a shainaithint agus a bhrath go mear agus teagmhais a bhaineann le TFC a láimhseáil go pras;
|
|
(e)
|
príomhspleáchais ar sholáthraithe seirbhísí tríú páirtí TFC a shainaithint;
|
|
(f)
|
leanúnachas feidhmeanna criticiúla nó tábhachtacha a áirithiú, trí phleananna leanúnachais gnó agus bearta freagartha agus athshlánaithe, lena n-áirítear, ar a laghad, bearta cúltaca agus athbhunaithe;
|
|
(g)
|
na pleananna agus na beartais dá dtagraítear i bpointe (f) a thástáil, mar aon le héifeachtacht na rialuithe arna gcur chun feidhme i gcomhréir le pointí (a) agus (c);
|
|
(h)
|
na conclúidí oibríochtúla ábhartha a eascraíonn as na tástálacha dá dtagraítear i bpointe (g) agus as an anailís iartheagmhais a rinneadh ar an bpróiseas measúnaithe riosca TFC a chur chun feidhme, de réir mar is iomchuí, cláir feasachta slándála TFC agus oiliúint athléimneachta digití oibríochtúla don fhoireann agus don bhainistíocht.
|
|
|
EULAW
|
Airteagal 16 2
2. Déanfar creat bainistíochta riosca TFC dá dtagraítear i mír 1, an dara fomhír, pointe (a), a dhoiciméadú agus a athbhreithniú go tréimhsiúil agus nuair a tharlaíonn mórtheagmhais a bhaineann le TFC i gcomhréir le treoracha maoirseachta. Cuirfear feabhas leanúnach ar an gcreat ar bhonn na gceachtanna a eascraíonn as cur chun feidhme agus faireachán. Cuirfear tuarascáil ar an athbhreithniú ar chreat bainistíochta riosca TFC faoi bhráid an údaráis inniúil arna iarraidh sin dó.
|
|
EULAW
|
Airteagal 21 Bearta bainistíochta riosca cibearshlándála
-
|
|
DELAW
|
BDSG § 9 Zuständigkeit
(1) Die oder der Bundesbeauftragte ist zuständig für die Aufsicht über die öffentlichen Stellen des Bundes, auch soweit sie als öffentlich-rechtliche Unternehmen am Wettbewerb teilnehmen, sowie über Unternehmen, soweit diese für die geschäftsmäßige Erbringung von Telekommunikationsdienstleistungen Daten von natürlichen oder juristischen Personen verarbeiten und sich die Zuständigkeit nicht bereits aus § 29 des Telekommunikation-Digitale-Dienste-Datenschutz-Gesetzes ergibt. Die Vorschriften dieses Kapitels gelten auch für Auftragsverarbeiter, soweit sie nichtöffentliche Stellen sind, bei denen dem Bund die Mehrheit der Anteile gehört oder die Mehrheit der Stimmen zusteht und der Auftraggeber eine öffentliche Stelle des Bundes ist. (2) Die oder der Bundesbeauftragte ist nicht zuständig für die Aufsicht über die von den Bundesgerichten im Rahmen ihrer justiziellen Tätigkeit vorgenommenen Verarbeitungen.
|
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.
|