☐ Standard Operating Procedures (SOPs) have been developed, and roles and responsibilities assigned for use of facilities and communications technologies in response to cyber incidents, and these resources are confirmed as available. This includes for alternative/back-up ICT-based channels. ☐ Incident logging/records and tracking technologies used to manage a response are confirmed as available and have been tested. ☐ Role cards have been developed for each person involved in the CIRT and the SEMT. Individual actions will depend on the type and severity of the incident. Example role card is available at Appendix J. Your organisation has internal or third party arrangements and capabilities to monitor threats. Situational awareness information is collected from internal and external data sources, including: ☐ o Local system and network traffic and activity logs o News feeds concerning ongoing political, social, or economic activities that might impact incident activity o External feeds on incident trends, new attack vectors, current attack indicators and new mitigation strategies and technologies. Detection, Investigation, Analysis and Activation Standard Operating Procedures (SOPs) have been developed, and roles and responsibilities assigned for: Detection mechanisms which can be used to identify potential information security incidents, such as scanning, senses and logging mechanisms. These mechanisms require monitoring processes to identify unusual or suspicious activity, for example behaviour and logging, commensurate with the impact of an incident. Common monitoring techniques include: a) network and user profiling that establishes a baseline of normal activity which, when combined with logging and alerting mechanisms, can enable detection of anomalous activity; ☐ b) scanning for unauthorised hardware, software and changes to configurations; c) sensors that provide an alert when a measure breaches a defined threshold(s) (e.g. device, server and network activity); d) logging and alerting of access to sensitive data or unsuccessful logon attempts to identify potential unauthorised access; and e) 4 users with privileged access accounts subject to a greater level of monitoring in light of the heightened risks involved.4 ☐ Incident detection, including self-detected incidents, notifications received from service providers or vendors, and notifications received from trusted third parties (e.g. ACSC). ☐ Incident analysis, including how incidents are to be categorised, classified and prioritised, and controls related to how data is stored and transmitted (i.e. if out-of-band transmission is required). ☐ Activating a Cyber Incident Response Team (CIRT) to manage critical incidents, with roles and responsibilities assigned. APRA Prudential Practice Guide CPG 234 Information Security. 25

Select target paragraph3

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