A security engineering team is establishing baseline controls for a cloud-native software delivery pipeline. Match each security implementation on the left with the primary security objective (CIA Triad pillar or Non-Repudiation) it provides on the right.
- Digitally signing container images using an asymmetric private key prior to registry deployment.Non-Repudiation
- Encrypting database backups at rest using AES-256 encryption.Confidentiality
- Deploying auto-scaling groups across multi-region redundant load balancers.Availability
- Generating SHA-256 cryptographic hashes for software release packages.Integrity
Cevap
Digitally signing container images maps to Non-Repudiation; encrypting database backups at rest maps to Confidentiality; deploying multi-region auto-scaling load balancers maps to Availability; and generating SHA-256 hashes maps to Integrity.
Each security control aligns directly with a core security objective: Asymmetric digital signatures ensure Non-Repudiation because the signature uniquely proves origin identity. Encryption protects Confidentiality by preventing unauthorized disclosure. Redundant auto-scaling architectures maintain Availability by ensuring system resilience and uptime. Cryptographic hashing enforces Integrity by verifying that files have not suffered unauthorized tampering.
Adım Adım Çözüm
Anahtar Kavram
Mapping technical controls to the CIA Triad (Confidentiality, Integrity, Availability) and Non-Repudiation principles.