+Event Log & Security-Relevant Telemetry Retention
|
Event Log & Security-Relevant Telemetry Retention
Description
Mechanisms exist to retain event logs and security-relevant telemetry for a time period consistent with records retention requirements to provide support for after-the-fact investigations of security incidents and to meet statutory, regulatory and contractual retention requirements.
Possible Solutions & Considerations
Micro-Small Business (<10 staff) / BLS Firm Size Classes 1-2
∙ Managed Security Services Provider (MSSP)
∙ Log retention policy (minimum 90 days online, 1 year archived)
∙ Cloud log storage (e.g., AWS S3, Azure Storage)
Small Business (10-49 staff) / BLS Firm Size Classes 3-4
∙ Managed Security Services Provider (MSSP)
∙ Log retention policy (minimum 90 days online, 1 year archived)
∙ Cloud SIEM with configurable retention
Medium Business (50-249 staff) / BLS Firm Size Classes 5-6
∙ Security Incident Event Manager (SIEM) with defined retention schedules
∙ Managed Security Services Provider (MSSP)
∙ Log archiving to cold storage (e.g., AWS S3 Glacier, Azure Archive)
Large Business (250-999 staff) / BLS Firm Size Classes 7-8
∙ SIEM with tiered log retention (hot/warm/cold storage)
∙ Log retention policy aligned to regulatory requirements (e.g., HIPAA 6 yrs, PCI DSS 1 yr)
∙ Managed Security Services Provider (MSSP)
Enterprise (> 1,000 staff) / BLS Firm Size Class 9
∙ Enterprise log retention program aligned to all applicable regulations
∙ SIEM with tiered retention (hot/warm/cold storage)
∙ Immutable log archives (e.g., AWS S3 Object Lock, Azure Blob WORM)
∙ Legal hold capability for investigation support
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
Continuous Monitoring (MON) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include:
▪ Policies, standards & procedures associated with MON domain capabilities provide limited coverage due to the depth and breadth of the existing documentation.
▪ Event monitoring-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
▪ Monitoring is primarily reactive in nature, focused on identifying incidents that occurred.
▪ Event log reviews primarily rely on manual processes to identify anomalous behaviors.
Level 2 Planned Tracked
Continuous Monitoring (MON) 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 MON domain capabilities are formally documented and centrally-managed by the entity.
▪ Standardized Operating Procedures (SOP) associated with MON 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 MON domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD).
▪ Continuous monitoring-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines).
▪ Continuous monitoring may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel.
Level 3 Well Defined
Continuous Monitoring (MON) 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 MON domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function.
▪ Cybersecurity personnel use a structured process via Standardized Operating Procedures (SOP) to review and analyze logs.
▪ A Security Operations Center (SOC) team, or similar function, is appropriately staffed and supported to implement and maintain MON domain capabilities.
▪ Technology is leveraged to enhance the efficiency and accuracy of continuous monitoring operations (e.g., Security Incident Event Manager (SIEM)).
▪ 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 MON 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 security event logging to contain sufficient information to establish necessary details of activity and allow for forensics analysis.
▪ An implemented and operational capability exists to retain event logs for a time period consistent with records retention requirements to provide support for after-the-fact investigations of security incidents and to meet statutory, regulatory and contractual retention requirements.
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 19 Logaí a ghintear go huathoibríoch
-
|
|
EULAW
|
Airteagal 19 Logaí a ghintear go huathoibríoch
-
|
|
EULAW
|
Airteagal 8 Beartais agus nósanna imeachta um oibríochtaí TFC
|
|
EULAW
|
Airteagal 12 Logáil
|
|
EULAW
|
Airteagal 21 Rialú rochtana
Airteagal 21
Mar chuid dá rialú ar chearta bainistithe rochtana, déanfaidh eintitis airgeadais beartas a fhorbairt, a dhoiciméadú agus a chur chun feidhme ina mbeidh na nithe uile seo a leanas:
(a)
cearta rochtana ar shócmhainní TFC a shannadh bunaithe ar an bprionsabal ‘ar bhonn riachtanais eolais’, an prionsabal ‘ar bhonn riachtanais úsáide’ agus prionsabal an údaráis is lú, lena n-áirítear i gcás cianrochtana agus rochtain éigeandála;
(b)
dualgais a dheighilt sa chaoi go gcoiscfear rochtain neamhúdaraithe ar shonraí criticiúla nó leithdháileadh teaglamaí ceart rochtana a d’fhéadfaí a úsáid chun teacht timpeall ar rialuithe;
(c)
foráil maidir le cuntasacht úsáideora, trí úsáid cuntas cineálach agus comhroinnte a theorannú a mhéid is féidir agus trína áirithiú go mbíonn úsáideoirí in-sainaitheanta i gcónaí i leith na ngníomhaíochtaí a dhéantar sna córais TFC;
(d)
foráil maidir le srianta rochtana ar shócmhainní TFC lena leagtar amach rialuithe agus uirlisí chun rochtain neamhúdaraithe a chosc;
(e)
nósanna imeachta bainistíochta cuntais um chearta rochtana a dheonú, a athrú nó a chúlghairm do chuntais úsáideoirí agus cuntais chineálacha, lena n-áirítear forálacha maidir leis na nithe uile seo a leanas:
(i)
róil agus freagrachtaí a shannadh maidir le cearta rochtana a dheonú, a athbhreithniú agus a chúlghairm;
(ii)
rochtain phribhléidithe, éigeandála agus riarthóra a shannadh ar bhonn riachtanais úsáide nó ar bhonn ad hoc maidir leis na córais TFC uile;
(iii)
cearta rochtana a aistarraingt gan moill mhíchuí ar fhoirceannadh fostaíochta nó i gcás nach mbeidh gá leis an rochtain a thuilleadh;
(iv)
cearta rochtana a thabhairt cothrom le dáta i gcás ina mbeidh gá le hathruithe agus uair amháin sa bhliain ar a laghad maidir leis na córais TFC uile, seachas córais TFC lena dtacaítear le feidhmeanna criticiúla nó tábhachtacha agus gach 6 mhí ar a laghad i gcás córais TFC lena dtacaítear le feidhmeanna criticiúla nó tábhachtacha;
(f)
modhanna fíordheimhniúcháin, lena n-áirítear na nithe uile seo a leanas:
(i)
úsáid a bhaint as modhanna fíordheimhniúcháin atá 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 sócmhainní TFC agus breithniú á dhéanamh ar chleachtais atá chun tosaigh;
(ii)
úsáid a bhaint as modhanna fíordheimhniúcháin láidre i gcomhréir le cleachtais atá chun tosaigh agus teicnící maidir le cianrochtain ar ghréasán an eintitis airgeadais, rochtain phribhléidithe, rochtain ar shócmhainní TFC lena dtacaítear le feidhmeanna criticiúla nó tábhachtacha nó ar shócmhainní TFC atá inrochtana don phobal;
(g)
bearta maidir le rialuithe rochtana fisiciúla, lena n-áirítear:
(i)
sainaithint agus logáil ar dhaoine nádúrtha atá údaraithe chun rochtain a fháil ar áitreabh, lárionaid sonraí agus limistéir ainmnithe íogaire arna sainaithint ag an eintiteas airgeadais ina bhfuil sócmhainní TFC agus sócmhainní faisnéise lonnaithe;
(ii)
cearta rochtana fisiciúla ar shócmhainní TFC criticiúla a dheonú do dhaoine údaraithe amháin, i gcomhréir leis an bprionsabal ‘ar bhonn riachtanais eolais’ agus le prionsabal an údaráis is lú, agus ar bhonn ad hoc;
(iii)
faireachán ar rochtain fhisiciúil ar áitreabh, lárionaid sonraí agus limistéir ainmnithe íogaire arna sainaithint ag an eintiteas airgeadais ina bhfuil sócmhainní TFC nó sócmhainní faisnéise, nó an dá chineál, lonnaithe;
(iv)
athbhreithniú ar chearta rochtana fisiciúla chun a áirithiú go ndéanfar cearta rochtana neamhriachtanacha a chúlghairm go pras.
Chun críocha phointe (e)(i), bunóidh eintitis airgeadais an tréimhse choinneála, á gcur san áireamh na cuspóirí gnó agus slándála faisnéise, na cúiseanna le taifeadadh an teagmhais sna logaí agus torthaí an mheasúnaithe riosca TFC.
Chun críocha phointe (e)(ii), úsáidfidh eintitis airgeadais, i gcás inar féidir, cuntais thiomnaithe chun cúraimí riaracháin a dhéanamh ar chórais TFC. I gcás inarb indéanta agus iomchuí, cuirfidh eintitis airgeadais réitigh uathoibrithe in úsáid le haghaidh an bhainistithe rochtana pribhléidithe.
Chun críocha phointe (g)(i), beidh an tsainaithint agus an logáil i gcomhréir le tábhacht an áitribh, na lárionad sonraí agus na limistéar ainmnithe íogair agus le criticiúlacht na n-oibríochtaí nó na gcóras TFC atá lonnaithe iontu.
Chun críocha phointe (g)(iii), beidh an faireachán i gcomhréir leis an aicmiú a bhunaítear i gcomhréir le hAirteagal 8(1) de Rialachán (AE) 2022/2554 agus le criticiúlacht an limistéir ar a bhfaightear rochtain.
|
|
EULAW
|
Airteagal 22 Polasaí bainistíochta teagmhas a bhaineann le TFC
Airteagal 22
Polasaí bainistíochta teagmhas a bhaineann le TFC
Mar chuid de na sásraí chun gníomhaíochtaí aimhrialta a bhrath, lena n-áirítear fadhbanna feidhmíochta gréasáin TFC agus teagmhais a bhaineann le TFC, déanfaidh eintitis airgeadais beartas teagmhas a bhaineann le TFC a fhorbairt, a dhoiciméadú agus a chur chun feidhme, trína ndéanfaidh siad na nithe seo a leanas:
(a)
an próiseas bainistithe teagmhas a bhaineann le TFC dá dtagraítear in Airteagal 17 de Rialachán (AE) 2022/2554 a dhoiciméadú;
(b)
liosta a bhunú de theagmhálaithe ábhartha a bhfuil feidhmeanna inmheánacha acu agus de gheallsealbhóirí seachtracha a bhfuil baint dhíreach acu le slándáil oibríochtaí TFC, lena n-áirítear:
(i)
cibearbhagairtí a bhrath agus faireachán a dhéanamh orthu;
(ii)
gníomhaíochtaí aimhrialta a bhrath;
(iii)
bainistíocht leochaileachta;
(c)
sásraí teicniúla, eagraíochtúla agus oibríochtúla a bhunú, a chur chun feidhme agus a oibriú chun tacú leis an bpróiseas bainistithe teagmhas a bhaineann le TFC, lena n-áirítear sásraí lena mbeifear in ann gníomhaíochtaí agus iompraíochtaí aimhrialta a bhrath go pras i gcomhréir le hAirteagal 23 den Rialachán seo;
▼C1
(d)
an fhianaise uile atá gaolmhar le teagmhais a bhaineann le TFC a choimeád ar feadh tréimhse nach faide ná mar is gá chun na gcríoch dá mbailítear na sonraí, i gcomhréir le criticiúlacht na bhfeidhmeanna gnó, na bpróiseas tacaíochta agus na sócmhainní TFC agus faisnéise dá ndéantar difear, i gcomhréir le hAirteagal 8(2) de Rialachán Tarmligthe (AE) 2024/1772 ón gCoimisiún (
2
) agus le haon cheanglas coinneála is infheidhme de bhun dhlí an Aontais;
▼B
(e)
sásraí a bhunú agus a chur chun feidhme chun anailís a dhéanamh ar theagmhais mhóra nó athfhillteacha a bhaineann le TFC agus ar phatrúin sa líon teagmhas a bhaineann le TFC agus sa chaoi a dtarlaíonn siad.
Chun críocha phointe (d), déanfaidh eintitis airgeadais an fhianaise dá dtagraítear sa phointe sin a choinneáil ar bhealach slán.
|
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.
|