Tutorial activities

Week 7 activity

Tue, 24 Mar 2026 16:02:12 GMT

by Ayman El Hajjar.

Week 7 activity

Re: Week 6 activity

Tue, 17 Mar 2026 17:08:41 GMT

by Hetvi Nikulbhai Patel.

Data Security, Governance and Compliance – Week 6
EduFlex School – Learning Management System

2529465-HETVI PATEL, 2507162-HIRAL JASOLIYA,2532368-SWASTI SAKARIYA,2523935-DIYA PATEL

Scenario Analysis
EduFlex school uses its Learning Management System for delivering lessons, managing assessments, tracking attendance, and communicating with students and parents. Potential threats include power outages, flooding, ransomware attacks, accidental data deletion, failed software updates, and cloud provider outages. The critical functions that must continue are student access to course materials, assignment submission and marking, progress tracking, secure login, and staff-to-parent communication.

Business Continuity Plan
Team Roles
The BC team consists of an IT Lead who coordinates the response and updates leadership, an LMS Administrator who manages the platform, a Network Engineer who handles connectivity and servers, a Teaching Lead who arranges alternative lessons, a Communications Lead who updates staff, students and parents, and a Support Lead who logs user issues throughout the incident.

Strategies
EduFlex will maintain a warm site in a secondary cloud region as the primary fallback, allowing the LMS to be restored within a few hours. A cold site provides a secondary option when more recovery time is available. A mutual agreement with a partner school offers additional support during prolonged incidents. A separate secure repository of teaching materials ensures teachers can still share resources when the LMS is fully unavailable.

BC Policy
The purpose of this plan is to keep essential educational services running during any LMS disruption. It covers the LMS application, database, identity services, network, and backup environment. All BC team members receive induction training upon joining and annual refresher training. The plan is reviewed yearly and updated after any system change or incident.

Maintenance and Testing
A full simulation exercise is conducted annually to test the team's response. After every test or real incident, the team debriefs and updates the plan based on lessons learned.

Disaster Recovery Plan
Disaster Classifications
Disasters are classified as either natural, such as flooding or power failure, or man-made, such as cyberattacks or accidental data loss. They are further classified as rapid onset, meaning sudden and without warning, or slow onset, meaning they develop gradually and may go unnoticed for some time.

Recovery Priorities and Steps
Systems are restored in a fixed order. Identity and network access come first, followed by the LMS database, then the LMS application, and finally any additional tools. Recovery steps include isolating affected systems, selecting a clean verified backup, restoring to the recovery environment, testing core functions such as logging in and submitting work, and monitoring the system before opening it to users.
DR Team Roles
The Recovery Lead coordinates the technical work and reports to leadership. System and Database Specialists carry out the restoration. The Security Specialist investigates the cause of the incident and confirms the environment is safe before the system goes live.

DR Policy
The policy covers the LMS, database, identity services, and network infrastructure. It identifies which staff require training in recovery procedures and requires that those procedures are tested regularly through desk checks, tabletop exercises, and structured walkthroughs involving both technical and teaching staff.

Testing and Improvement
After each exercise or real incident, findings are reviewed and the plan is updated to address any gaps. Regular testing ensures the team can respond quickly and confidently when a real disruption occurs.

Re: Week 6 activity

Tue, 17 Mar 2026 17:08:31 GMT

by Harsh Bipinbhai Valand.

objective: Design a Disaster recovery plan and a Business Continuity plan

week 6
harsh valand:2437861
sadab kureshi:2530072
tassavar kureshi:2530068
vinay patel:2519364
muhammad akteruzzman:2216724

A mid-sized organisation relies on IT systems, cloud services, and office operations to deliver services. Disruptions could halt operations, cause financial loss, and damage reputation.

1. Analyse the Scenario

Potential Disasters / Events

Natural:
Flooding
Fire
Severe weather (storms, power outages)

Man-made:

Cyberattacks (ransomware, phishing)
Data breaches
Hardware/software failure
Human error
Supply chain disruption

2. Business Continuity Plan (BCP)

1. Form the BC Team

Roles & Responsibilities:
BC Manager: Oversees entire continuity plan
IT Lead: Handles systems and data continuity
Operations Lead: Maintains business processes
HR Lead: Staff communication and welfare
Communications Officer: External/internal updates

Assigned Responsibilities:

Plan development: BC Manager + IT Lead
Testing: All department leads
Maintenance: BC Manager

2 Business Continuity Strategies
Exclusive-Use Options

Hot site: Fully operational backup site with real-time data (for critical systems)
Warm site: Partial infrastructure with periodic backups
Cold site: Basic facility with no active systems

Shared-Use Options
Cloud service providers
Third-party recovery vendors
Mutual aid agreements with partner organisations

Specialised Options
Mobile recovery units (temporary offices)
Remote work (work-from-home infrastructure)

3 Business Continuity Policy

Purpose: Ensure uninterrupted delivery of critical services during disruptions
Scope: Covers all departments, IT systems, and personnel
Resources: Backup sites, cloud systems, trained personnel
Roles: Clearly assigned BC team responsibilities
Training: Regular staff awareness and simulation exercises

4 Maintenance

Quarterly testing (simulations and drills)
Annual full review of the plan
Continuous updates after incidents or changes
Staff training and awareness programs

3. Disaster Recovery Plan (DRP)

1 Disaster Classification

Natural vs Man-made
Rapid onset: Fire, cyberattack, power outage
Slow onset: System degradation, supply chain failure

2 Recovery Steps

Step 1: Incident Response
Detect and report incident
Activate DR team

Step 2: Assessment

Evaluate damage and impact

Identify affected systems

Step 3: Prioritisation

Restore critical systems first:
Network & servers
Customer database
Communication systems

Step 4: Recovery Execution

Restore data from backups
Switch to backup site (hot/warm)
Validate system functionality

Step 5: Communication

Inform employees, customers, stakeholders

3 DR Policy

Scope: Covers IT systems, data, and infrastructure recovery
Training: Regular technical recovery drills
Testing: Backup restoration and failover testing
Compliance: Align with data protection laws (e.g., GDPR)

4. Testing and Improvement

Methods:

Simulation exercises: Realistic disaster scenarios
Desk checks: Review procedures step-by-step
Structured walkthroughs: Team-based reviews
Full-scale drills: End-to-end recovery testing

Continuous Improvement:
Record lessons learned
Update plans regularly
Improve response time and coordination