Skip to content
Cyber security roles
ASD ISMISM-0733

ASD ISM 0733 Ensure CISO awareness of cyber incidents

What it says

The CISO is fully aware of all cyber security incidents within their organisation.

Quoted as published. Everything else on this page is written by Control Stack.

What it means

In plain English

The CISO should be informed about all cyber security incidents in the organisation.

This control means that the Chief Information Security Officer (CISO) must be kept in the loop about every cyber security issue that happens within the organisation. It matters because if incidents are kept hidden or not communicated promptly, the organisation could face bigger security risks, leading to data breaches, financial loss, or damage to its reputation.

Why it matters

Unchecked cyber incidents can escalate threats, causing severe reputational damage and financial loss if the CISO is not promptly informed.

How to implement

  1. CIO (Chief Information Officer) should establish a process: Develop a clear communication plan to inform the CISO of any cyber incidents.

    Set up automatic alerts through email or a secure messaging platform each time an incident is reported.

  2. IT security team should document incidents: Keep a detailed record of what happens during each incident, complete with timelines and response actions.

    Use a shared system where the CISO can access and review these records anytime.

  3. Office Manager should coordinate regular updates: Schedule a weekly briefing with the CISO to review all incidents reported during the period.

    Use this time to discuss any changes in response strategies or upcoming risks.

  4. HR should train staff: Educate employees about the importance of reporting cyber security incidents.

    Provide simple guidelines on how to escalate issues to ensure the CISO is informed quickly.

  5. Procurement should ensure tools are in place: Acquire the right tools for tracking and managing incidents.

    Ensure these tools have user-friendly reporting features so that incidents can be logged and accessed by the CISO efficiently.

Keep it running

Ensure incident reports are relayed to the CISO within 24 hours, enabling timely decision-making and effective response coordination.

Evidence and audit

  1. Check 1 of 5What an auditor asks for

    Ask for

    The incident communication plan: Request a written document that outlines how cyber incidents are communicated to the CISO.

    Look at

    Details on incident types, notification procedures, and responsible parties.

    Good evidence

    Includes clear procedures and contact channels for alerting the CISO.

  2. Check 2 of 5What an auditor asks for

    Ask for

    To see incident logs: Request access to recent cyber security incident records.

    Look at

    The details and ensure they are thorough and timely.

    Good evidence

    Shows complete logs with time stamps and actions taken.

  3. Check 3 of 5What an auditor asks for

    Ask for

    Meeting records: Request minutes or notes from the CISO's regular briefing meetings.

    Look at

    Consistency and the discussion of relevant incidents.

    Good evidence

    Includes dates, attendees, and summarised discussions of incidents.

  4. Check 4 of 5What an auditor asks for

    Ask for

    About staff training records: Obtain proof of staff training on reporting incidents.

    Look at

    Attendance and training materials.

    Good evidence

    Shows high participation rates and relevant, up-to-date content.

  5. Check 5 of 5What an auditor asks for

    Ask for

    Tool usage reports: Request data on the usage of tools designed for incident tracking and reporting.

    Look at

    User logs and access by the CISO.

    Good evidence

    Shows regular, documented usage and CISO engagement.

Mappings

Closest match in ASD Essential Eight: E8-AC-ML2.9, Cyber security incidents are reported promptly to CISO, which asks for the same thing.

ISO 27001

ISO/IEC 27001: 1 mapping

Essential Eight

ASD Essential Eight: 4 mappings

Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.