GSEC Virtualization, Cloud, and AI Essentials Practice Question
A healthcare organization uses a public cloud IaaS provider to host electronic health records (EHRs). The security team must ensure that data at rest is encrypted and that the cloud provider cannot access the plaintext. Which approach best meets this requirement?
⚠ Common exam trap
The trap here is assuming that server-side encryption with provider-managed keys prevents the provider from accessing data, but the provider holds the keys and can decrypt.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Implement client-side encryption with customer-managed keys stored on-premises.
Client-side encryption with customer-managed keys stored on-premises ensures that the cloud provider never has access to the encryption keys or plaintext data. Provider-managed keys leave the provider with decryption capability, failing the requirement. Other options like CASB or server-side encryption do not fully prevent provider access to plaintext.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Enable server-side encryption with provider-managed keys and enforce TLS for data in transit.
Why it's wrong here
Server-side encryption with provider-managed keys encrypts data at rest, but the provider holds the keys. TLS protects data in transit, not at rest. The requirement is specifically that the provider cannot access plaintext at rest; with provider-managed keys, the provider can decrypt the data, so this approach fails to meet the security objective.
- ✗
Use provider-managed encryption keys with automatic rotation.
Why it's wrong here
Provider-managed keys are controlled by the cloud provider. While they encrypt data at rest, the provider has access to the keys and can potentially decrypt the data. This does not meet the requirement that the provider cannot access plaintext, as the provider could be compelled or compromised. It also violates the principle of customer-controlled encryption for sensitive data.
- ✓
Implement client-side encryption with customer-managed keys stored on-premises.
Why this is correct
Client-side encryption with customer-managed keys stored on-premises ensures that data is encrypted before it leaves the organization's control, and the cloud provider never has access to the keys. This satisfies the requirement that the provider cannot access plaintext, as the provider only stores encrypted blobs. It also aligns with compliance requirements for protecting sensitive health information.
- ✗
Use a cloud access security broker (CASB) to encrypt data before it reaches the cloud.
Why it's wrong here
A CASB can encrypt data in transit or apply policies, but it typically does not provide persistent encryption at rest with customer-controlled keys. If the CASB encrypts data before it reaches the cloud, the cloud provider still might have access if keys are managed by the CASB vendor. This does not guarantee that the provider cannot access plaintext, as the CASB may be cloud-based.
About these practice questions
Courseiva writes every GSEC question from scratch — 351 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official GIAC exam blueprint
This GSEC practice question is part of Courseiva's free GIAC certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the GSEC exam.