Document Feedback - Review and Comment
Step 1 of 4: Comment on Document
How to make a comment?
1. Use this to open a comment box for your chosen Section, Part, Heading or clause.
2. Type your feedback into the comments box and then click "save comment" button located in the lower-right of the comment box.
3. Do not open more than one comment box at the same time.
4. When you have finished making comments proceed to the next stage by clicking on the "Continue to Step 2" button at the very bottom of this page.
Important Information
During the comment process you are connected to a database. Like internet banking, the session that connects you to the database may time-out due to inactivity. If you do not have JavaScript running you will recieve a message to advise you of the length of time before the time-out. If you have JavaScript enabled, the time-out is lengthy and should not cause difficulty, however you should note the following tips to avoid losing your comments or corrupting your entries:
-
DO NOT jump between web pages/applications while logging comments.
-
DO NOT log comments for more than one document at a time. Complete and submit all comments for one document before commenting on another.
-
DO NOT leave your submission half way through. If you need to take a break, submit your current set of comments. The system will email you a copy of your comments so you can identify where you were up to and add to them later.
-
DO NOT exit from the interface until you have completed all three stages of the submission process.
(1) The Business Continuity Management Procedure forms part of Charles Sturt University's (the University) overall resilience framework. (2) In circumstances where there is a disruption event that interferes with the normal operations and functions of the University, this procedure outlines the University's approach in preparing, responding and recovering from disruptions and the prioritisation of resources required to minimise impacts to the University's critical business processes. (3) The purpose of this procedure is to: (4) This procedure applies to all staff, students, contractors, education partners and third-party service providers of the University and its controlled entities. (5) Where a disruption occurs, the following elements of the resilience framework should be enacted: (6) This procedure supports the Resilience Policy. (7) The first priority in any disruption event will be the ongoing safety of students, staff and visitors. Staff are to follow the directions of wardens during any emergency event. (8) This procedure incorporates principles from AS ISO 22301:2020 Security and resilience – business continuity management systems – requirements. (9) The following range of scenarios are considered in scope for the response and recovery processes outlined in this procedure: (10) Business continuity management encompasses the identification and risk management of critical business processes in line with the University's Risk Management Policy. The University’s approach to managing business continuity includes: (11) The University’s recovery priorities are determined in line with the University's strategic objectives and are used, in conjunction with business impact analysis results, to guide the criticality of the University's business processes and prioritise recovery. The University’s recovery priorities are outlined below: (12) A business impact analysis process will be undertaken annually, facilitated by Risk and Compliance Unit in conjunction with each portfolio and faculty to identify and validate critical business processes. Performing business impact analysis assesses the impact of disruptions to the University's business processes, including: (13) Maximum tolerable outage times for IT systems identified through the business impact analysis process should reconcile with recovery times defined in the University's IT Disaster Recovery Procedure. (14) Maximum tolerable outage (MTO) times across critical business processes will be based on: (15) If a business process supports a recovery priority and has an MTO of less than 48 hours (two calendar days), it must be classified as a critical business process. (16) For each identified critical business process, identify: (17) A business continuity plan (BCP) will apply for each portfolio and faculty, detailing how to prepare for, prevent, respond to and recover from a disruption event for all relevant critical business processes. (19) BCPs do not attempt to identify and plan for every contingency or outage that could occur and should focus on the relevant critical business processes. The BCP should provide a flexible framework for BCP owners to identify, plan and develop resilience in their critical business processes. (20) BCPs must be approved by the relevant Executive Leadership Team member (the BCP owner). (21) A copy of each BCP will be retained by the BCP owner and the Risk and Compliance Unit. (22) The Crisis Management Team and/or Critical Incident Management Team will determine whether a business continuity plan is to be activated in response to a disruption event. Once activated, the BCP owner is responsible for coordinating response and recovery activities in line with the BCP. (23) The manner in which the University conveys information during a disruption event is critical to students, staff and the public’s understanding and perception of the University's management of a situation. (24) Each BCP will include provision for internal and external communication requirements during a disruption event. Messaging to students, staff, regulators, government partners, third-party partners, stakeholders and the media must be coordinated through the Crisis Management Team to ensure the accuracy and continuity of messaging. BCP owners are to direct all communication requests, including communication requests to be issued by third-party education partners, for management through the Crisis Management Procedure. (25) Communication with staff on BCP response and recovery activities is the responsibility of the BCP owner and should include: (26) Where critical business processes are supported by a third party, the University must satisfy itself that the third party’s business continuity management arrangements are adequate to meet the University's recovery priorities. (27) The University must also satisfy itself that the third party adequately reviews and tests its business continuity plan. (28) The Risk and Compliance Unit will provide training to BCP owners to raise awareness of roles, responsibilities before, during and after a business disruption event, and the practical application of their BCPs. (29) BCP owners are responsible for ensuring their staff are trained and aware of the BCPs. (30) Test exercises conducted in line with clauses 31 and 32 will also be considered a form of ongoing training that supports awareness of business continuity management at the University. (31) The purpose of testing BCPs is to: (32) BCP owners are responsible for carrying out regular reviews to test the validity and practicality of their BCPs. (33) The Risk and Compliance Unit will coordinate annual testing of BCPs, noting that not all BCPs may be tested each year based on the scenario and method of testing used. (34) BCPs must be reviewed by the BCP owner following each test exercise to address learnings and implement opportunities for improvement identified. (35) Following a disruption event, a post incident review will be conducted in consultation with the Risk and Compliance Unit to identify and address lessons learnt and implement opportunities for improvement. (36) In all other instances, BCPs must be reviewed by the BCP owner at least annually, or earlier following a BCP event or a major change to the University. (37) Recovery priorities, business impact analysis and BCPs will be reviewed more frequently than annually in the event of major change. (38) The Risk and Compliance Unit will report the following to the Executive Leadership Team and Audit and Risk Committee at least annually: (40) This procedure uses the following terms: Business Continuity Management Procedure
Section 1 - Purpose
Scope
Top of PageSection 2 - Policy
Section 3 - Procedure
Disruption scenarios
Methodology
Business impact analysis
High or very high impact timeframe
MTO
Immediate
4 hours
Today
12 hours
Next day
24 hours
Two calendar days
48 hours
More than two calendar days
48+ hours
Business continuity strategies and planning
Communication
Third-party arrangements
Education and training
Testing
Monitoring, review and reporting
Top of PageSection 4 - Guidelines
Top of PageSection 5 - Glossary