describe the nature and effect of the incident and should be used with care, if used at all. It is important to note that security incidents include physical incidents (such as lost documents) as well as “cyber” incidents. 7.2.10. The detection, recording, management and response to an incident depends primarily on effective prevention and detection mechanisms and a robust response plan. Effective detection and response mechanisms also provide an important record of events and assist in preventing repeat events, improving defences and streamlining response measures. 7.2.11. A key part of the detection and response is incident reporting, including internal security system reports as well as any essential external reporting. It is essential that response is timely and methodical in order to minimise the effects of the incident. In all cases it is vital that steps are taken to quickly contain the incident, minimise damage and implement measures to prevent or contain any reoccurrence. 7.2.12. Not every cybersecurity event is serious enough to warrant detailed investigation and reporting, for example a single login failure from an employee on premises. A persistent login failure is, however, more serious and may indicate a malicious access attempt. Thresholds should be established which will trigger an incident response. In all cases incidents should be recorded to support analysis and reporting. Definition of a Cyber Security Incident 7.2.13. A cyber security incident is any event that jeopardises or may jeopardise the confidentiality, integrity, or availability of an information system or the information a system processes, stores, or communicates. This includes a violation or potential violation of security policies, security procedures, acceptable use policies or any relevant regulation or legislation. 7.2.14. It is also important to categorise incidents in order to better manage allocation of resources to the containment and remediation of the incident. A three-tier categorisation is suggested: 1. Critical: Incident affecting critical systems or information with potential to impact operations, revenue or customers. 2. Serious: Incident affecting noncritical systems or information, impact on operations, revenue or customers. Employee investigations that are time sensitive should typically be classified at this level. 3. Low: Possible incident affecting noncritical systems. Incidents or employee investigations that are not time sensitive. Long term investigations requiring extensive research and/or detailed forensic work. 7.2.15. Factors that assist in determining the severity of an incident include: Whether the incident affects a single agency or multiple agencies; Functional impact of the incident (availability); Information impact of the incident (confidentiality, integrity); Recoverability from the incident; Whether a breach of personally identifiable information (PII) held by the agency has occurred; Reputational risk to the agency; Impact on any MOUs, MOAs and similar formal agreements. References 7.2.16. Additional information relating to information security incidents can be found at: Reference RFC 5070 Title The Incident Object Description Exchange Format, December Publisher Source The Internet Engineering Taskforce (IETF) https://datatracker.ietf.org/doc/html/ rfc5070 IETF https://datatracker.ietf.org/doc/html/ 2007 RFC 6685 Expert Review for Incident Object Description Exchange rfc6685 Format (IODEF) Extensions in IANA XML Registry, July 2012, ISSN: 2070-1721 Detect, SHARE, Protect ENISA http://www.enisa.europa.eu/activitie Solutions for Improving Threat s/cert/support/data-sharing/detect- Data Exchange among CERTs, October 2013 share-protect-solutions-forimproving-threat-data-exchangeamong-certs SP 800-61 rev2 Computer Security Incident Handling Guide, rev2, August NIST https://csrc.nist.gov/publications/det ail/sp/800-61/rev-2/final NIST https://csrc.nist.gov/publications/det 2012 SP 800-60 Volume l Revision 1 Guide for Mapping Types of Information and Information ail/sp/800-60/vol-1-rev-1/final Systems to Security Categories SP 800-60 Volume ll Revision 1 Guide for Mapping Types of Information and Information Systems to Security Categories, NIST https://csrc.nist.gov/publications/det ail/sp/800-60/vol-2-rev-1/final Volume ll: Appendices 72 Version_3.5__January-2022

Select target paragraph3

Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents