+Incident Response Training
---+Simulated Incidents
---+Automated Incident Response Training Environments
|
Incident Response Training
Description
Mechanisms exist to train personnel in their incident response roles and responsibilities.
Possible Solutions & Considerations
Micro-Small Business (<10 staff) / BLS Firm Size Classes 1-2
∙ Basic incident response plan
∙ Designate incident response contact
Small Business (10-49 staff) / BLS Firm Size Classes 3-4
∙ Documented incident response plan
∙ Incident log
∙ Designated IR team
Medium Business (50-249 staff) / BLS Firm Size Classes 5-6
∙ ITIL 4 (https://axelos.com) ∙ Incident and problem management
Large Business (250-999 staff) / BLS Firm Size Classes 7-8
∙ ITIL 4 (https://axelos.com) ∙ Incident and problem management
Enterprise (> 1,000 staff) / BLS Firm Size Class 9
∙ ITIL 4 (https://axelos.com) ∙ Incident and problem management
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
Incident Response (IRO) 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 IRO domain capabilities are formally documented and centrally-managed by the entity.
▪ Standardized Operating Procedures (SOP) associated with DCH 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 IRO domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD).
▪ Incident response-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines).
▪ Incident response 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 operate an incident response capability using a documented and tested Incident Response Plan (IRP) to facilitate incident management operations that cover preparation, detection and analysis, containment, eradication and recovery.
▪ Incident responders are proficient on their specific IRP role(s) and responsibilities through recurring training events (e.g., annual rock drill).
Level 3 Well Defined
Incident Response (IRO) 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 IRO domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function.
▪ Cybersecurity personnel operate an incident response capability using a documented and tested Incident Response Plan (IRP) to facilitate incident management operations that cover preparation, detection and analysis, containment, eradication and recovery.
▪ An incident response team, or similar function, is appropriately staffed and supported to implement and maintain IRO domain capabilities.
▪ Technology is leveraged to enhance the efficiency and accuracy of incident response operations (e.g., incident management software).
▪ 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 IRO 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).
▪ An implemented and operational capability exists to train personnel in their incident response roles and responsibilities.
Level 4 Quantitatively Controlled
Incident Response (IRO) 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. Forbhreathnú
| Teideal |
Caighdeán |
|
Simulated Incidents
|
Description
Mechanisms exist to incorporate simulated events into incident response training to facilitate effective response by personnel in crisis situations.
Possible Solutions & Considerations
Micro-Small Business (<10 staff) / BLS Firm Size Classes 1-2
∙ Basic incident response plan
∙ Designate incident response contact
Small Business (10-49 staff) / BLS Firm Size Classes 3-4
∙ Documented incident response plan
∙ Incident log
∙ Designated IR team
Medium Business (50-249 staff) / BLS Firm Size Classes 5-6
∙ Formal incident response program
∙ IR playbooks
∙ Tabletop exercises
Large Business (250-999 staff) / BLS Firm Size Classes 7-8
∙ Enterprise incident response program
∙ 24/7 SOC monitoring
∙ SOAR platform
Enterprise (> 1,000 staff) / BLS Firm Size Class 9
∙ Enterprise SOC with SIEM/SOAR (e.g., Splunk SOAR, Palo Alto XSOAR)
∙ IR retainer
∙ Threat hunting
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
Incident Response (IRO) 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 IRO domain capabilities are formally documented and centrally-managed by the entity.
▪ Standardized Operating Procedures (SOP) associated with DCH 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 IRO domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD).
▪ Incident response-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines).
▪ Incident response 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 operate an incident response capability using a documented and tested Incident Response Plan (IRP) to facilitate incident management operations that cover preparation, detection and analysis, containment, eradication and recovery.
Level 3 Well Defined
Incident Response (IRO) 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 IRO domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function.
▪ Cybersecurity personnel operate an incident response capability using a documented and tested Incident Response Plan (IRP) to facilitate incident management operations that cover preparation, detection and analysis, containment, eradication and recovery.
▪ An incident response team, or similar function, is appropriately staffed and supported to implement and maintain IRO domain capabilities.
▪ Technology is leveraged to enhance the efficiency and accuracy of incident response operations (e.g., incident management software).
▪ 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 IRO 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).
▪ An implemented and operational capability exists to incorporate simulated events into incident response training to facilitate effective response by personnel in crisis situations.
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.
|
|
Automated Incident Response Training Environments
|
Description
Automated mechanisms exist to provide a more thorough and realistic incident response training environment.
Possible Solutions & Considerations
Micro-Small Business (<10 staff) / BLS Firm Size Classes 1-2
∙ Basic incident response plan
∙ Designate incident response contact
Small Business (10-49 staff) / BLS Firm Size Classes 3-4
∙ Documented incident response plan
∙ Incident log
∙ Designated IR team
Medium Business (50-249 staff) / BLS Firm Size Classes 5-6
∙ Formal incident response program
∙ IR playbooks
∙ Tabletop exercises
Large Business (250-999 staff) / BLS Firm Size Classes 7-8
∙ Enterprise incident response program
∙ 24/7 SOC monitoring
∙ SOAR platform
Enterprise (> 1,000 staff) / BLS Firm Size Class 9
∙ Enterprise SOC with SIEM/SOAR (e.g., Splunk SOAR, Palo Alto XSOAR)
∙ IR retainer
∙ Threat hunting
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
Incident Response (IRO) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include:
▪ Policies, standards & procedures associated with IRO domain capabilities provide limited coverage due to the depth and breadth of the existing documentation.
▪ Incident response-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
▪ IT and/or cybersecurity personnel use an informal process to facilitate incident management operations that cover preparation, detection and analysis, containment, eradication and recovery.
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
Incident Response (IRO) 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 IRO domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function.
▪ Cybersecurity personnel operate an incident response capability using a documented and tested Incident Response Plan (IRP) to facilitate incident management operations that cover preparation, detection and analysis, containment, eradication and recovery.
▪ An incident response team, or similar function, is appropriately staffed and supported to implement and maintain IRO domain capabilities.
▪ Technology is leveraged to enhance the efficiency and accuracy of incident response operations (e.g., incident management software).
▪ 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 IRO 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).
▪ An implemented and operational capability exists to automatically provide a more thorough and realistic incident response training environment.
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.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 14 1
1. Mar chuid de chreat bainistíochta riosca TFC dá dtagraítear in Airteagal 6(1), beidh pleananna cumarsáide géarchéime i bhfeidhm ag eintitis airgeadais lena gcumasófar, ar a laghad, mórtheagmhais a bhaineann le TFC nó leochaileachtaí a nochtadh ar bhealach freagrach do chliaint agus contrapháirtithe agus don phobal chomh maith, de réir mar is iomchuí.
|
|
EULAW
|
Airteagal 14 2
2. Mar chuid de chreat bainistíochta rioscaí TFC, cuirfidh eintitis airgeadais beartais chumarsáide chun feidhme don fhoireann inmheánach agus do gheallsealbhóirí seachtracha. Cuirfear san áireamh le beartais chumarsáide don fhoireann an gá le hidirdhealú a dhéanamh idir baill foirne a a ghlacann páirt i mbainistíocht rioscaí TFC, go háirithe an fhoireann atá freagrach as freagairt agus athshlánú, agus na baill foirne is gá a chur ar an eolas.
|
|
EULAW
|
Airteagal 14 3
3. Cuirfear de chúram ar dhuine amháin ar a laghad san eintiteas airgeadais an straitéis cumarsáide le haghaidh teagmhas a bhaineann le TFC a chur chun feidhme agus comhlíonfaidh an duine sin an fheidhm phoiblí agus an fheidhm a bhaineann leis na meáin chun na críche sin.
|
|
EULAW
|
Airteagal 19 1
1. Tuairisceoidh eintitis airgeadais mórtheagmhais a bhaineann le TFC don údarás inniúil ábhartha dá dtagraítear in Airteagal 46 i gcomhréir le mír 4 den Airteagal seo.
I gcás ina mbeidh eintiteas airgeadais faoi réir maoirseachta ag níos mó ná údarás inniúil náisiúnta amháin dá dtagraítear in Airteagal 46, ainmneoidh na Ballstáit údarás inniúil aonair mar an t-údarás inniúil ábhartha a bheidh freagrach as na feidhmeanna agus na dualgais dá bhforáiltear san Airteagal seo a chur i gcrích.
Déanfaidh institiúidí creidmheasa a aicmítear mar institiúidí suntasacha, i gcomhréir le hAirteagal 6(4) de Rialachán (AE) Uimh. 1024/2013, mórtheagmhais a bhaineann le TFC a thuairisciú don údarás inniúil náisiúnta ábhartha arna ainmniú i gcomhréir le hAirteagal 4 de Threoir 2013/36/AE, a tharchuirfidh an tuarascáil sin láithreach chuig BCE.
Chun críche na chéad fhomhíre, tabharfaidh eintitis airgeadais, tar éis dóibh an fhaisnéis ábhartha uile a bhailiú agus a anailísiú, an fógra tosaigh agus na tuarascálacha dá dtagraítear i mír 4 den Airteagal seo ar aird trí úsáid a bhaint as na teimpléid dá dtagraítear in Airteagal 20 agus cuirfidh siad iad faoi bhráid an údaráis inniúil. I gcás nach mbeidh sé indéanta go teicniúil an fógra tosaigh a chur isteach trí úsáid a bhaint as an teimpléad, tabharfaidh eintitis airgeadais fógra ina leith don údarás inniúil trí mhodhanna malartacha.
Beidh san fhógra tosaigh agus sna tuarascálacha dá dtagraítear i mír 4 an fhaisnéis uile is gá don údarás inniúil chun a shuntasaí agus atá an mórtheagmhas a bhaineann le TFC a chinneadh agus chun tionchair fhéideartha thrasteorann a mheasúnú.
Gan dochar don tuairisciú de bhun na chéad fhomhíre arna dhéanamh ag an eintiteas airgeadais don údarás inniúil ábhartha, féadfaidh na Ballstáit a chinneadh, ina theannta sin, go dtabharfaidh roinnt eintiteas airgeadais, nó iad ar fad, an fógra tosaigh agus gach tuarascáil dá dtagraítear i mír 4 den Airteagal seo trí úsáid a bhaint as na teimpléid dá dtagraítear in Airteagal 20 do na húdaráis inniúla nó do na foirne freagartha do theagmhais a bhaineann le slándáil ríomhairí (CSIRTanna) arna n-ainmniú nó arna mbunú i gcomhréir le Treoir (AE) 2022/2555 .
|
|
EULAW
|
Airteagal 19 2
2. Féadfaidh eintitis airgeadais, ar bhonn deonach, cibearbhagairtí suntasacha a chur in iúl don údarás inniúil ábhartha i gcás ina measann siad go bhfuil an bhagairt ábhartha don chóras airgeadais, d’úsáideoirí seirbhíse nó do chliaint. Féadfaidh an t-údarás inniúil ábhartha an fhaisnéis sin a sholáthar d’údaráis ábhartha eile i gcomhréir le mír 6.
Féadfaidh institiúidí creidmheasa a aicmítear mar institiúidí suntasacha, i gcomhréir le hAirteagal 6(4) de Rialachán (AE) Uimh. 1024/2013, ar bhonn deonach, fógra a thabhairt faoi chibearbhagairtí suntasacha don údarás inniúil náisiúnta ábhartha, arna ainmniú i gcomhréir le hAirteagal 4 de Threoir 2013/36/AE, a tharchuirfidh an fógra sin láithreach chuig BCE.
Féadfaidh na Ballstáit a chinneadh go bhféadfaidh na heintitis airgeadais sin a thugann fógra ar bhonn deonach i gcomhréir leis an gcéad fhomhír an fógra sin a tharchur freisin chuig CSIRTanna arna n-ainmniú nó arna mbunú i gcomhréir le Treoir (AE) 2022/2555.
|
|
EULAW
|
Airteagal 19 3
3. I gcás ina dtarlóidh mórtheagmhas a bhaineann le TFC agus ina mbeidh tionchar aige ar leasanna airgeadais cliant, cuirfidh eintitis airgeadais, gan moill mhíchuí, a luaithe a bheidh siad feasach air, a gcuid cliant ar an eolas faoin mórtheagmhas a bhaineann le TFC agus faoi na bearta a rinneadh chun na héifeachtaí díobhálacha a bhaineann leis an teagmhas sin a mhaolú.
I gcás cibearbhagairt shuntasach, cuirfidh eintitis airgeadais, i gcás inarb infheidhme, a gcliaint a bhféadfaí difear a dhéanamh dóibh ar an eolas faoi aon bhearta cosanta iomchuí a d’fhéadfadh na heintitis sin a bhreithniú agus a dhéanamh.
|
|
EULAW
|
Airteagal 19 4
4. Cuirfidh eintitis airgeadais, laistigh de na teorainneacha ama atá le leagan síos i gcomhréir le hAirteagal 20, an chéad mhír, pointe (a), pointe (ii), an méid seo a leanas faoi bhráid an údaráis inniúil ábhartha:
|
(b)
|
tuarascáil idirmheánach tar éis an fhógra tosaigh dá dtagraítear i bpointe (a), a luaithe a bheidh athrú suntasach tagtha ar stádas an teagmhais bhunaidh nó a luaithe a athrófar láimhseáil an mhórtheagmhais a bhaineann le TFC bunaithe ar fhaisnéis nua atá ar fáil, agus fógraí nuashonraithe ina dhiaidh sin, de réir mar is iomchuí, gach uair a bheidh nuashonrú ábhartha ar stádas ar fáil, agus ar iarraidh shonrach ón údarás inniúil;
|
|
(c)
|
tuarascáil deiridh, nuair a bheidh an anailís ar an mbunchúis curtha i gcrích, gan beann ar cibé acu ar cuireadh bearta maolaithe chun feidhme cheana féin, agus nuair a bheidh na figiúir iarbhír faoin tionchar ar fáil chun dul in ionad meastachán.
|
|
|
EULAW
|
Airteagal 19 5
5. Féadfaidh eintitis airgeadais na hoibleagáidí tuairiscithe faoin Airteagal seo a sheachfhoinsiú, i gcomhréir le dlí earnálach an Aontais agus náisiúnta, chuig soláthraí seirbhíse tríú páirtí. I gcás seachfhoinsithe den sórt sin, leanfaidh an t-eintiteas airgeadais de bheith freagrach go hiomlán as na ceanglais maidir le tuairisciú teagmhas a chomhlíonadh.
|
|
EULAW
|
Airteagal 45 3
3. Tabharfaidh eintitis airgeadais fógra d’údaráis inniúla maidir lena rannpháirtíocht sna socruithe comhroinnte faisnéise dá dtagraítear i mír 1, tar éis bhailíochtú a mballraíochta, nó, mar is infheidhme, maidir le scor a mballraíochta, a thúisce a bheidh éifeacht leis.
|
|
EULAW
|
Airteagal 34 Sárú i ndáil le sonraí pearsanta a chur in iúl don ábhar sonraí
-
|
|
EULAW
|
Airteagal 23 Oibleagáidí maidir le tuairisciú
-
|
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.
|