023.4 Lesson 1
Certificate: |
Security Essentials |
---|---|
Version: |
1.0 |
Topic: |
023 Device and Storage Security |
Objective: |
023.4 Data Availability |
Lesson: |
1 of 1 |
Introduction
In today’s digital world, data is the lifeblood of many activities, whether for personal, academic, or business purposes. Ensuring the availability of your data is crucial, as data loss can be catastrophic. This lesson guides you through the essential concepts of data availability, including backups and cloud storage.
The Importance of Backups
Data loss can occur due to various reasons, such as hardware failures, software glitches, human errors, or even cyberattacks. Backups are copies of your data that can be used to restore it in case of loss or damage. Here are some key reasons why backups are essential.
Backups allow you to recover your data quickly and efficiently in case of unexpected events such as hardware failures, accidents, or cyberattacks. Backups serve as a safety net for your data.
Backups help maintain the integrity of your data, ensuring that it remains intact and uncorrupted.
For business continuity, backups are critical for maintaining operations and preventing downtime. Losing customer or inventory information could be fatal to a business, so backups are essential.
It is a necessity for an organization to have a good backup plan. A backup plan should be developed to determine what data is important to keep as well as how often that important data is to be copied.
Common Backup Types and Strategies
To effectively implement a backup plan, it’s crucial to consider several backup types and strategies alongside establishing a consistent schedule based on your data’s criticality and frequency of change.
A full backup copies all data at a specific point in time. It provides complete data recovery Typically, the first backup in a system will be a full backup. While this method provides the most comprehensive recovery option, it is time-consuming and requires significant storage space. Full backups are typically performed less frequently due to the time and resource demands they require, but are often used as a baseline for other types of backups.
Incremental backups copy only data that has changed since the last backup, whether it was a full or incremental backup. This method is efficient in terms of storage and time, as it requires less space and quicker processing. However, during restoration, you need the last full backup and every subsequent incremental backup, which can make recovery more complex.
A differential backup saves all changes made since the last full backup, regardless of whether previous differential backups have been made. This method requires more space than incremental backups but simplifies the restoration process, as only the last full backup and the most recent differential backup are needed.
Snapshot backups capture the state of a system at a specific point in time. Unlike traditional file-based backups, snapshots can be taken quickly and offer near-instantaneous recovery by rolling the system back to a prior state. However, snapshots require more advanced storage systems and may not offer the same granular recovery options as other methods.
Example Scenarios
Understanding when to use either a differential or incremental backup after a full backup is an important aspect of a backup plan. To help illustrate the differences between differential and incremental backups, compare the two following scenarios.
Restoring Data from Full and Incremental Backups
Imagine an IT administrator named Emma who works for a medium-sized e-commerce company. The company’s database contains critical customer order information, and they perform regular backups to ensure data availability.
On Sunday night, Emma initiates a full backup of the entire database, capturing all customer orders and product inventory data.
From Monday to Saturday, incremental backups are scheduled daily. These backups capture only the data that has changed since the last backup. Each day, the database experiences minor updates due to new customer orders and product additions.
On Wednesday, a hardware failure occurs, and some data in the database becomes corrupted. Customer orders made on Wednesday morning are lost.
To restore the lost data, Emma starts by using the most recent full backup, which was taken on Sunday. This backup contains the baseline data. Next, Emma applies the incremental backups from Monday, Tuesday, and Wednesday. This process ensures that she brings the database up to date while minimizing the amount of data transferred and the time required for the restoration.
By restoring from the full backup and applying the incremental backups, Emma successfully recovers the lost data, ensuring that all customer orders and product information are intact up to the moment of the hardware failure on Wednesday.
Restoring Data from Full and Differential Backups
Now, consider a different scenario involving the same e-commerce company and IT administrator Emma, but this time they use a differential backup strategy.
On Sunday night, Emma initiates a full backup of the entire database, capturing all customer orders and product inventory data.
Throughout the week, Emma schedules differential backups daily. These backups capture all data changes since the last full backup.
On Wednesday, a database corruption occurs due to a software glitch, leading to data loss.
To restore the lost data, Emma starts by using the most recent full backup taken on Sunday night. This full backup contains the baseline data. Emma then applies only the latest differential backup from Wednesday. Since differential backups capture all changes since the last full backup, only the most recent differential backup is needed.
By restoring from the full backup and applying the most recent differential backup, Emma successfully recovers the lost data, ensuring that all customer orders and product information are restored up to the point of the software glitch on Wednesday. This method simplifies the restoration process because it requires restoring only the full backup and the latest differential backup, unlike incremental backups that would require applying multiple backups in sequence.
Backup Retention
A good backup retention policy is essential for effective data management and disaster recovery planning. It defines how long backups are retained and under what conditions they are deleted. The goal of a well-designed retention policy is to balance data availability, compliance requirements, storage costs, and operational efficiency. Here are some key components of a good backup retention policy.
First, the data is classified based on its importance, and usage and retention periods for different data categories are established (e.g., daily backups may be retained for 7-30 days for operational recovery, weekly backups may be retained for 4-12 weeks for short-term recovery, and monthly or yearly backups may be retained for long-term archival purposes).
To ensure compliance with industry-specific regulations (e.g., GDPR, HIPAA) that mandate data retention periods, legal and compliance teams should be consulted to align retention policies with legal requirements.
Another consideration is the granularity of backups to be retained. For example, you might retain hourly backups for the last 24 hours, daily backups for the previous week, and weekly backups for the previous year.
An organization can also keep multiple versions of backups, especially for critical data, to allow for point-in-time recovery.
Given the limited life of most backups, automated processes can make it easier to delete backups once they reach their specified retention periods. This helps avoid manual errors and ensures compliance.
Offsite storage for long-term backups protects against disasters such as fires, floods, and hardware failures.
It’s important to periodically test the restoration process for backups with different retention periods to ensure that data can be recovered successfully.
The backup retention policy should be clearly communicated to all relevant stakeholders, including IT personnel, data owners, and management.
Stakeholders should also regularly review and adjust the retention policy to align with changing business needs, compliance requirements, and technological advancements.
Thorough documentation of the backup retention policy should be created and maintained, including details about retention periods, data classification, and compliance considerations.
Backup policies also need processes for handling exceptions, such as extending retention periods for specific data due to legal investigations or litigation.
Monitoring and reporting mechanisms can ensure compliance with the policy and alert administrators of potential issues or violations.
A good backup retention policy should strike a balance between data availability and storage costs, while adhering to legal and compliance requirements. Regularly reviewes and updates to the policy ensures that it remains effective in meeting the organization’s evolving needs.
Security Implications of Backups
Backups should be treated with the same level of security as primary data.
Thus, they should be encrypted to protect them from unauthorized access.
Access control ensures that only authorized personnel have access to the backups. Depending on the organization, it could be helpful to maintain a log of who accesses the backups and when. This log file could be audited regularly to ensure backup policy compliance.
Additional resilience is created by storing backups in a separate location to protect against physical disasters like fire or theft. Third-party companies are available to take the physical backups (usually written to tape) and store them in an offsite location that has restricted access and is climate-controlled. Such a service can be expensive and is typically employed by large enterprises. Any data stored offsite should be encrypted as a precaution against data theft.
Cloud-based or offsite backups should follow strict security protocols, including encryption, access control, and adherence to data protection regulations.
Backup strategies that are resistant to ransomware attacks include using immutable storage or air-gapped backups to ensure data remains safe in case of an infection.
Creating and Securely Storing Backups
The following practices help create and securely store backups.
Factors to consider in choosing a backup software or service include the number of systems that a solution can back up and the ease of restoring backups. Some backup solutions provide _ersioning, which allows you to access and restore previous versions of files or data. Synchronization helps to maintain a history of changes, enabling you to roll back to a specific point in time when needed. This is valuable for recovering from accidental deletions or data corruption.
Regularly scheduled backups ensure that your data is up to date. Monitor the backup solution to make sure that the schedule is being followed and that resources are available for the backup.
Reliable and secure storage devices or services use external hard drives, network-attached storage (NAS), or cloud storage for redundancy. Magnetic tape is often used for offsite archival storage.
Backup integrity should be verified to ensure restorability. Set up a schedule where you could test your backups by using them to restore data and systems in a staging environment.
Data Storage, Access, and Sharing in Cloud Services
Cloud services offer convenient ways to store, access, and share data. Key concepts include the following.
In this backup model, data is stored on remote servers maintained by cloud service providers. The price of these services often depends on a variety of factors, such as the amount of storage needed for backups, the retention time of the backups, and the speed at which data will be transferred should a backup be utilized to restore a system. Keep in mind that some internet service providers may charge a fee for large amounts of data that traverse their network.
Cloud services offer granular control over who can access your data. An administrator can manage these controls using tools available from the cloud provider, typically via a web interface or a command line utility.
Storage services such as Dropbox, Google Drive, and OneDrive allow you to easily share files with others. Bear in mind that these services are not necessarily backup solutions, but instead are a means of providing access to files within an organization. When a user deletes a file, either intentionally or accidentally, depending on how the other users' client systems are configured they will likely have the same file deleted from their system. To restore a file that has been removed in this way, it may be necessary to contact the cloud service provider and ask them to restore the file. This might also incur an additional cost.
Security Implications of Cloud Storage and Shared Access
It is important to understand that cloud solutions are basically “somebody else’s computers.” With that in mind, the cloud storage provider should demonstrate a level of trust to the customer, considering that their systems will be storing copies of the client’s most important data. At the forefront of this trust are the following considerations.
Administrators should evaluate the security measures provided by the cloud service provider and use additional encryption if necessary.
Caution is also required when sharing data, to ensure that only authorized individuals have access. Keep a log of who accesses the backups as well as when the backups were accessed.
Dependence on Internet Connection and Data Synchronization
When dealing with offsite or cloud solutions for backups, keep the following in mind:
Cloud storage depends on an internet connection. Lack of connectivity may affect access to your data. As stated earlier, some internet service providers may charge a higher fee for extensive use of bandwidth. Also, bear in mind the security concerns that an internet connection entails.
Synchronization ensures that the data stored in your cloud backup matches the data on your local systems. It helps maintain data consistency by keeping the backup copy up-to-date with changes made to the source data. Without proper synchronization, you might have outdated or incomplete backups, which can be problematic during data recovery.
Guided Exercises
-
What is the primary purpose of a backup?
-
Which backup type is described as the most efficient in terms of storage space, but can be slower when restoring data?
-
What is the purpose of a backup retention policy?
Explorational Exercises
-
Create a backup plan for your personal or work-related data, considering the type of data, frequency of backups, and storage options.
-
Research a popular cloud storage service and its security features.
Summary
In this lesson, we’ve explored the importance of data backups, common backup types and strategies, security implications related to backups, and the basics of data storage in cloud services. By following best practices in data management and backup strategies, you can ensure the availability and security of your valuable data. If utilizing offsite storage for backups (including the cloud), be sure to encrypt them for data safety and integrity.
Answers to Guided Exercises
-
What is the primary purpose of a backup?
To recover data in case of loss or damage.
-
Which backup type is described as the most efficient in terms of storage space, but can be slower when restoring data?
Incremental backups.
-
What is the purpose of a backup retention policy?
To define how long backups are retained and when they are deleted.
Answers to Explorational Exercises
-
Create a backup plan for your personal or work-related data, considering the type of data, frequency of backups, and storage options.
Solutions to this task vary depending on the system getting backed up. Linux users can use Déjà Dup and duplicity for easy backup management, Apple users can use Time Machine and iCloud backups, and Windows users can use the Windows Backup utility. Many of these utilities offer ways to schedule backup jobs to keep up with data changes.
-
Research a popular cloud storage service and its security features.
Factors to take into consideration include the amount of storage available for each service plan, encryption methodologies used, data access restrictions, and data transfer fees.