An enterprise cloud engineering team is establishing baseline security controls for a newly migrated production environment. Match each technical implementation on the left with the primary security pillar or objective it satisfies on the right.
- Applying asymmetric digital signatures to automated infrastructure deployment manifests before executionNon-Repudiation
- Configuring SHA-256 cryptographic checksums coupled with write-once-read-many (WORM) audit loggingIntegrity
- Deploying active-active multi-region database replicas with automated health-check failoverAvailability
- Enforcing client-side AES-256-GCM encryption on cloud object storage bucketsConfidentiality
Answer
Asymmetric digital signatures map to Non-Repudiation; SHA-256 hashing with WORM storage maps to Integrity; Active-active multi-region redundancy maps to Availability; Client-side AES-256 encryption maps to Confidentiality.
Each control satisfies its corresponding pillar: asymmetric digital signatures cryptographically bind identity to deployment actions for non-repudiation; SHA-256 hashing with WORM prevents undetected log alteration for integrity; multi-region active-active clustering maintains service uptime for availability; client-side AES-256 encryption prevents unauthorized data viewing for confidentiality.
Step-by-Step Solution
Key Concept
CIA Triad and Non-Repudiation