incorporating: user awareness and training; counter-measures against malicious code, known attack methods and types; intrusion detection strategies; data egress monitoring & control; access control anomalies; audit analysis; system integrity checking; and vulnerability assessments. 7.1.7.C.02. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:1154] Agencies SHOULD develop, implement and maintain tools and procedures covering the detection of potential information security incidents, incorporating: user awareness and training; counter-measures against malicious code, known attack methods and types; intrusion detection strategies; data egress monitoring & control; access control anomalies; audit analysis; system integrity checking; and vulnerability assessments. 7.1.7.C.03. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:1155] Agencies SHOULD use the results of the security risk assessment to determine the appropriate balance of resources allocated to prevention versus resources allocated to detection of information security incidents. 7.2. Reporting Information Security Incidents Objective 7.2.1. To ensure reporting information security incidents is incorporated as an essential part of incident management, whether the reporting is within an agency or reports are provided to another government agency. 7.2.2. This assists in maintaining an accurate threat environment picture for government systems, particularly when All-of-Government (AoG) or multiagency systems are involved. Context Scope 7.2.3. This section covers information relating specifically to the reporting ofinformation security incidents. It does not cover the reporting of physical or personnel security incidents unless there is an impact on information systems. 7.2.4. It is important to note that, in most cases, information systems are likely to be affected. Requirement for information security incident reporting 7.2.5. The requirement to report an information security incident report applies irrespective of whether incident management is internally managed or if an agency has outsourced some or all of its information technology functions and services. 7.2.6. The information security threat and intelligence landscape continues to evolve, partly driven by more advanced, capable, well-resourced and motivated adversaries, as well as the need to improve management and governance of information systems. To assist in managing these requirements, a standardised form of information exchange is essential. 7.2.7. The requirement for incident reporting has existed for many years, and guidance can be found in various standards and good practice guidance (see References at 7.2.16). Historical Notes 7.2.8. While the requirement for incident reporting has been in place for many years, the reporting mechanism has changed over time: Incident categories, incident types and resolution types were previously defined in the Incident Object Description Exchange Format (IODEF) standard. IODEF was an e-GIF standard. IODEF was superseded by a group of protocols designed to automate and structure operational cybersecurity information sharing techniques on a global basis. International in scope and free for public use, TAXII, STIX and CybOX are community-driven technical specifications designed to enable automated information sharing. These protocols continued to evolve with CybOX absorbed into the protocol suite and no longer separately identified. An alternative to TAXII and STIX is VERIS ( The vocabulary for Event Recording and Incident Sharing), a set of metrics designed to provide a common language for describing security incidents in a structured and repeatable manner. Previously New Zealand’s National Cyber Security Centre (NCSC) had adopted this suite of protocols as the basis for incident reports to the NCSC and for reports issued by the NCSC. It was found, however, that agencies were not always able to utilise these protocols andthe requirement for reporting using these protocols has been withdrawn by the NCSC. Background 7.2.9. 71 Security Incidents are frequently also termed “a hack”, “a breach”, “a compromise” and “a cyber attack”. The more colloquial terms may not correctly Version_3.5__January-2022

Select target paragraph3

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