(1) The purpose of this policy is to set out the elements of organisational processes that are required to be in place to ensure the preparedness of Charles Sturt University (the University) to be able to effectively plan for, respond to, and recover from, disruptions. (2) This policy is derived from the University’s resilience framework set out in this policy. (3) This policy applies to all academic and professional/general staff of the University, controlled entities, educational partnerships, contractors and adjunct staff. (4) For the purpose of this policy, the University has adopted the following definitions: (5) The University’s resilience framework is based on the following standards: AS/NZS 5050 (Int):2020 - Managing disruption-related risk; AS ISO 22301:2020 - Security and resilience - Business continuity management systems - Requirements; and AS 3745:2010 - Planning for emergencies in facilities. (6) Critical to the success of the resilience framework is robust stakeholder engagement and collaboration to ensure the University is prepared to respond and recover from disruptions. (7) Planning and preparing to respond to a disruption requires areas to evaluate the potential disruption, design a response and implement the following planning strategies, processes, oversighting and implementation responsibilities. (8) Awareness and anticipation strategies: to enable the University to understand potential sources and types of disruptions, as well as establish mechanisms to identify disruptive events and respond flexibly in a timely fashion. Such strategies may involve developing monitoring mechanisms to detect early warnings of change, scenario analysis, and awareness training. (9) Prevention and protection strategies: to remove or reduce potential sources of disruption and minimise interaction with sources of disruption. For example, these strategies include establishing effective controls to prevent unwanted behaviour, ceasing activities with undue exposure to risk, developing safety procedures, relocating people away from sources of harm. (10) Preparedness strategies: to improve the University’s capability to respond to and withstand disruptive events. This entails improving the capability of people (e.g. leadership and team skills), infrastructure (e.g. reducing logical security vulnerabilities), contingency arrangements (e.g. manual workarounds), and management systems (e.g. reporting). Preparedness strategies include actively anticipating and mitigating the impacts of incidents on staff and student wellbeing. (11) Risk assessment: to identify, analyse, and evaluate potential threats and sources of disruption. (12) Business impact analysis (BIA): to assess the impact of a potential disruption and determine business continuity priorities and requirements. The BIA defines the types of impacts, criteria for assessing the impacts over time, maximum tolerable period of disruption, activities and resources to be prioritised, as well as dependencies (e.g. partners and suppliers). (13) Response procedures and plans: to be activated by relevant areas and response teams when addressing a disruption. Procedures and plans must specify practical steps to respond to a disruption, be flexible in responding to any changes in internal and external conditions of a disruption, be effective in minimising the effects of a disruption, and assign roles and responsibilities for tasks. These procedures and plans should consider wellbeing and support protocols, succession plans, and staff emergency contact and next of kin notification. (14) Training and testing: to ensure individuals and teams are enabled to respond to disruptions and enact relevant response procedures and plans, as well as to validate the effectiveness of resilience strategies (e.g. through drills and simulations). (15) Oversighting the development of plans to respond to a disruption will involve the following areas across the University: (16) The following areas will implement the strategies and processes associated with the planning phase: (17) Responding to a disruption requires areas to design and implement the following response strategies, processes, oversighting and implementation responsibilities. (18) Communication strategies: to inform stakeholders about disruptive events, as well as the University’s responses and expected adjustments to processes and behaviours. Communications strategies include the provision of timely and accurate advice about the disruption, alternative arrangements to respond to the disruption, and approaches to recovery. (19) Containment strategies: to prevent the spread of disruption effects, including the potential use of quarantine, isolation, evacuation, relocation, and hibernation responses. (20) Stabilisation strategies: to prevent further incident and volatility. These strategies may include, for example, senior management involvement, reprioritising workloads, ceasing non-essential activities, and enhancing information provision. (21) Suppression strategies: to reduce the sources and effects of an incident. Countermeasures aimed at reducing the source of an incident include, for example, removing an insider threat. Countermeasures focused on addressing effects involve, for instance, responding to cybersecurity incidents. (22) Contingency strategies: to safeguard the continuity of critical business functions, including the reprioritisation of objectives, redeployment of resources, activating emergency response, business continuity or disaster recovery plans and adjusting supplier arrangements. (23) These response strategies should include considerations to support the wellbeing of persons directly or indirectly affected by an incident. (24) Emergency management: to ensure that resources and services are efficiently mobilised and deployed in response to an emergency. (25) Critical incident management: to ensure that predetermined or bespoke leadership arrangements and functional teams are mobilised and deployed to manage the disruption on behalf of the University. (26) Crisis management: to ensure that crises are adequately managed by a Crisis Management Team made up of representatives of the Vice-Chancellor's Leadership Team and specialist expert advisers. (27) Business continuity management: to safeguard the University’s capability to maintain its critical functions and areas, as well as deliver essential products and services during a disruption, while supporting the recovery towards pre-existing or modified business as usual operations. (28) IT disaster recovery: to ensure the timely response and restoration of the University’s IT infrastructure, electronic data and access to applications, in the event of a disruption. IT disaster recovery also entails the re-establishment of cybersecurity protocols for affected information systems. (29) Response processes should be carried out in accordance with relevant procedures and/or plans. (30) Oversighting the response to a disruption will involve the portfolio leader of the portfolio of origin of the incident. In general, portfolio leaders will oversight incidents as set out below: (31) If necessary, portfolio leaders responsible for oversighting a particular incident may convene a cross-portfolio Critical Incident Management Team (CIMT), to be chaired by the responsible portfolio leader or another member of the CIMT. The aim of a CIMT is to draw on multidisciplinary expertise to respond to an incident. A CIMT may also be appointed by the Crisis Management Team (see below). (32) A Crisis Management Team (CMT) chaired by the Vice-Chancellor and composed of representatives of the Vice-Chancellor's Leadership Team, and other representatives as required, will oversight the University's response to a crisis. The CMT have the authority to approve and provide clarity in relation to working arrangements and circumstances otherwise unanticipated by standing policy and procedure. The purpose of the CMT is to ultimately guide response teams while also having regard to the implications of the disruptive event for the University, including internal and external stakeholders. (33) Incident response strategies and processes will be carried out by the following areas across the University: (34) Recovering from a disruption requires areas to design and implement the following recovery strategies, processes, oversighting and implementation responsibilities. (35) Strategic recovery: to reconfirm, modify or reprioritise the University’s strategic plan in light of the disruption. While strategic recovery at the University-level is managed by the Vice-Chancellor's Leadership Team, at the portfolio-level it is managed by portfolio leaders. (36) Functional recovery: to re-establish or introduce changes to the organisational structures and functions with a view to deliver existing or modified products or services (e.g. re-structuring areas to reflect new strategic objectives). (37) People recovery: to assist individuals and teams to return to previous or modified work arrangements, organisational structures, and processes, as well as support their wellbeing (e.g. through mentoring, counselling, coaching). (38) Infrastructure recovery: to restore affected facilities, equipment, IT and telecommunications, and other physical assets (e.g. equipment repair). Infrastructure recovery arrangements should include assets owned or operated by third-parties to provide services to the University (e.g. partnership facilities). (39) Process, systems and information recovery, including the restoration of IT systems, data, and information, as well as the re-design of processes (e.g. learning and teaching processes). (40) Recovery from the effects of a disruption and restoring capability will be driven by business continuity management and IT disaster recovery processes. Both processes should be designed to deliver on the recovery strategies outlined above, including where interdependencies exist with University suppliers, partners or other third parties. (41) Oversighting the recovery to a disruption will involve the following: (42) Disruption recovery strategies and processes will be carried out by the following areas across the University: (43) In implementing a return to business as usual operations, consideration should be given to learnings and opportunities that have been realised throughout the incident management phase, recognising that post-incident operations may include considered varied business processes arising from the incident itself. (44) Student and staff wellbeing should be considered throughout the implementation of the recovery phase. (45) The resilience framework will be supported by the hierarchy of policy, procedures and plans. (46) This section summarises the responsibilities across the University for implementing the Resilience Policy. (47) The Vice-Chancellor is responsible for the following: (48) The Chief Operating Officer is responsible for the following: (49) The Deputy Vice-Chancellor (Research) is responsible for the following within their portfolio: (50) The Deputy Vice-Chancellor (Academic) is responsible for the following within their portfolio: (51) All portfolio leaders are responsible for the following within their portfolio: (52) The Risk and Compliance Unit is responsible for the following: (53) Where convened in accordance with the critical incident management procedure, Critical Incident Management Teams are responsible for the following: (54) Where convened in accordance with the crisis management procedure, the Crisis Management Team is responsible for the following: (55) Nil. Resilience Policy
Section 1 - Purpose
Scope
Section 2 - Glossary
Top of PageSection 3 - Policy
Part A - Resilience framework
Phase 1: Planning
Planning strategies
Planning processes
Oversighting the planning phase
Implementing the planning phase
Phase 2: Response
Response strategies
Response processes
Oversighting the response phase
Implementing the response phase
Phase 3: Recovery
Recovery strategies
Recovery processes
Oversighting the recovery phase
Implementing the recovery phase
Hierarchy of supporting documentation
Part B - Responsibilities
Top of PageSection 4 - Guidelines
View Current
This is not a current document. To view the current version, click the link in the document's navigation bar.