Secure Coding & OWASP Top 10 for Backend · Lesson

Protecting Sensitive Data at Rest

Implement encryption strategies for data stored in databases, file systems, and other storage mediums to prevent data breaches.

Protecting Sensitive Data at Rest is a free Secure Coding & OWASP Top 10 for Backend lesson on CoddyKit — lesson 1 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Secure Coding & OWASP Top 10 for Backend learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.

Data At Rest: What & Why?

Welcome to protecting sensitive data! In this lesson, we'll focus on data at rest. This refers to data that is stored physically, like on a hard drive, in a database, or on a backup tape.

Think of it as data that's 'sitting still' rather than moving across a network. It's a prime target for attackers if not properly secured.

Encryption: Our Digital Shield

The primary method for protecting data at rest is encryption. Encryption transforms data into an unreadable format, called ciphertext, using a secret key.

Only someone with the correct key can decrypt the data back into its original, readable form (plaintext). It's like locking your valuable information in a safe!

Database Encryption: TDE

Many databases offer features like Transparent Data Encryption (TDE). TDE encrypts an entire database or specific tablespaces at the storage level.

It's 'transparent' because applications can still access the data without needing to be rewritten.
The encryption happens automatically when data is written and decryption when it's read.
TDE protects against unauthorized access to the database files themselves.

Application-Level Encryption

For highly sensitive data, you might use application-level encryption. This means your application encrypts specific data fields (e.g., credit card numbers, personal IDs) before storing them in the database.

This adds an extra layer of security, as even if the database is compromised, the sensitive fields remain encrypted. The application holds the keys and manages the encryption/decryption.

Encrypting Data in Java

Here's a simplified Java example demonstrating application-level encryption using AES. We'll encrypt and then decrypt a simple message. Note: Key management is a complex topic covered in a later lesson!

import javax.crypto.Cipher;
import javax.crypto.KeyGenerator;
import javax.crypto.SecretKey;
import javax.crypto.spec.SecretKeySpec;
import java.util.Base64;

public class DataProtection {

    private static SecretKey generateKey() throws Exception {
        KeyGenerator keyGen = KeyGenerator.getInstance("AES");
        keyGen.init(128); // 128-bit AES key
        return keyGen.generateKey();
    }

    private static String encrypt(String plaintext, SecretKey key) throws Exception {
        Cipher cipher = Cipher.getInstance("AES");
        cipher.init(Cipher.ENCRYPT_MODE, key);
        byte[] encryptedBytes = cipher.doFinal(plaintext.getBytes());
        return Base64.getEncoder().encodeToString(encryptedBytes);
    }

    private static String decrypt(String ciphertext, SecretKey key) throws Exception {
        Cipher cipher = Cipher.getInstance("AES");
        cipher.init(Cipher.DECRYPT_MODE, key);
        byte[] decryptedBytes = cipher.doFinal(Base64.getDecoder().decode(ciphertext));
        return new String(decryptedBytes);
    }

    public static void main(String[] args) throws Exception {
        String originalData = "My secret message!";
        SecretKey secretKey = generateKey();

        // Encrypt the data
        String encryptedData = encrypt(originalData, secretKey);
        System.out.println("Original: " + originalData);
        System.out.println("Encrypted: " + encryptedData);

        // Decrypt the data
        String decryptedData = decrypt(encryptedData, secretKey);
        System.out.println("Decrypted: " + decryptedData);
    }
}

Protecting Files & Disks

Beyond databases, sensitive data often resides in files or on entire storage devices. Here are common protection methods:

Full Disk Encryption (FDE): Encrypts an entire hard drive (e.g., BitLocker on Windows, dm-crypt on Linux). This protects all data on the disk if the device is lost or stolen.
Encrypted File Systems (EFS): Allows encryption of specific files or folders. Only authorized users can access the content.

The Key to Security: Key Management

Encryption is only as strong as its keys! If an attacker gets your encryption keys, all your encrypted data is at risk. This is why secure key management is critical.

Keys should be: generated securely, stored separately from the data they protect (e.g., in a Key Management System or Hardware Security Module), rotated regularly, and properly revoked when no longer needed.

Alternatives: Tokenization & Masking

Sometimes, full encryption isn't the only solution. Consider these methods:

Tokenization: Replaces sensitive data with a non-sensitive 'token.' The actual data is stored securely elsewhere. Useful for credit card numbers.
Data Masking: Obfuscates or scrambles sensitive data, often for non-production environments (like development or testing). The masked data looks real but contains no actual sensitive information.

Data at Rest Best Practices

To effectively protect data at rest, remember these best practices:

Encrypt by Default: Assume all sensitive data needs encryption.
Strong Algorithms: Use industry-standard, strong encryption algorithms (e.g., AES-256).
Secure Key Management: Implement robust systems for generating, storing, and managing encryption keys.
Regular Audits: Periodically review your encryption strategies and key management processes.

Quick Check: Data Protection

Which of the following are crucial aspects of protecting sensitive data at rest?

Recap: Protecting Data at Rest

You've learned about protecting data at rest, which is crucial for preventing breaches of stored information. We covered:

The role of encryption using methods like TDE for databases and application-level encryption for specific fields.
Protecting files and disks with Full Disk Encryption.
The critical importance of secure key management.
Alternative strategies like tokenization and data masking.

Keep these principles in mind to build robust data protection into your backend systems!

Frequently asked questions

Is the “Protecting Sensitive Data at Rest” lesson free?

Yes — the full text of “Protecting Sensitive Data at Rest” is free to read here on the web, and the Secure Coding & OWASP Top 10 for Backend course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Secure Coding & OWASP Top 10 for Backend course, upgrade to CoddyKit PRO.

What will I learn in “Protecting Sensitive Data at Rest”?

Implement encryption strategies for data stored in databases, file systems, and other storage mediums to prevent data breaches. You practise Secure Coding & OWASP Top 10 for Backend with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.

Do I need any experience to start Secure Coding & OWASP Top 10 for Backend?

No prior experience is required. Secure Coding & OWASP Top 10 for Backend on CoddyKit is structured for beginners through advanced learners; this is — lesson 1 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “Protecting Sensitive Data at Rest” lesson take?

Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.

Can I write and run code in this Secure Coding & OWASP Top 10 for Backend lesson?

Yes. Every Secure Coding & OWASP Top 10 for Backend lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.

All lessons in this course

← Back to Secure Coding & OWASP Top 10 for Backend