Oracle Database 19c: Data Encryption — Lesson 1: Encryption Architecture, Threat Model, Keystores, and Key Ownership

Technical Scope

• data-at-rest and data-in-transit threats
• TDE architecture and key hierarchy
• password, auto-login, and external keystore concepts
• ownership, separation, backup, and recovery requirements

Instructor Demonstration

Demonstrate data-at-rest and data-in-transit threats inside a regulated database secured at tablespace, column, backup, and client-connection layers, then capture the exact configuration, command, transaction, report, or code evidence that proves the result.

Applied Workshop

Implement a controlled workshop covering TDE architecture and key hierarchy and password, auto-login, and external keystore concepts, then test a failure or exception involving ownership, separation, backup, and recovery requirements.

1. Confirm environment, identity, data, dependencies, and expected result.
2. Complete the product-specific implementation or analysis.
3. Capture commands, configuration, output, logs, transactions, or reports.
4. Explain the operational, security, performance, or business trade-off.

Validation Standard

The Encryption Architecture, Threat Model, Keystores, and Key Ownership result must be reproducible, traceable to approved inputs, and consistent with the expected Oracle product behavior.

• The intended target and ownership are verified.
• The result is supported by reproducible evidence.
• Security, performance, reliability, and support impact are reviewed.
• Unexpected behavior is investigated before acceptance.

Failure Analysis

Diagnose issues in data-at-rest and data-in-transit threats, TDE architecture and key hierarchy, password, auto-login, and external keystore concepts, or ownership, separation, backup, and recovery requirements without making an unverified production change.

Learners isolate the smallest proven cause, apply a reversible correction, rerun validation, and record the preventive action.