Free Managing-Cloud-Security Practice Test Questions and Answers (2026)

A Hardware Security Module (HSM) is a dedicated physical cryptographic processor specifically designed for the protection of the complete key lifecycle. It is engineered to securely generate, store, and manage cryptographic keys. In cloud environments, HSMs provide a high level of security by isolating key management operations within a tamper-resistant hardware boundary, ensuring that keys are never exposed in an unencrypted form outside the device. Major cloud providers offer HSM services to customers who require stringent security and compliance for their key management practices, which are fundamental to securing data both at rest and in transit.

B. Memory controller: This is a hardware component that manages the flow of data to and from the main system memory (RAM); it has no role in cryptographic key management.

C. RAID controller: This device manages physical disk drives in a storage array to provide data redundancy and performance improvements. It is not a general-purpose key management device.

D. Trusted platform module (TPM): A TPM is a secure cryptoprocessor chip on an individual computer's motherboard used for platform integrity and endpoint security, not for centralized key management in a cloud service.

1. Cloud Security Alliance (CSA). (2017). Security Guidance for Critical Areas of Focus in Cloud Computing v4.0. Domain 5: Cryptography

Encryption

and Key Management

Page 68. The document states

"Hardware Security Modules (HSMs) are dedicated hardware-based crypto-processors that are used to securely generate and store encryption keys."

2. National Institute of Standards and Technology (NIST). (2020). Special Publication 800-57 Part 1 Revision 5: Recommendation for Key Management: Part 1 – General. Section 5.3.1

"Cryptographic Modules." This publication discusses the use of validated cryptographic modules (often implemented as HSMs) as a fundamental component for protecting keys and performing cryptographic operations securely.

3. Amazon Web Services (AWS). (n.d.). What is AWS CloudHSM? AWS Documentation. Retrieved from https://docs.aws.amazon.com/cloudhsm/latest/userguide/introduction.html. The documentation specifies

"AWS CloudHSM provides hardware security modules (HSMs) in the AWS Cloud. An HSM is a computing device that processes cryptographic operations and provides secure storage for cryptographic keys."

4. Subashri

S.

& Shanthi

V. (2014). A survey on security issues and key management in cloud computing. International Journal of Engineering and Technology

5(6)

4775-4781. Page 4778 discusses key management solutions

noting that HSMs are used to "provide a higher level of security for the keys."

A Security Operations Center (SOC) is a centralized command center where security professionals monitor, analyze, and respond to cybersecurity incidents. The primary function of a SOC is to provide a dedicated space and team for continuous monitoring of an organization's security posture, including network traffic and events, to detect and respond to threats. This aligns directly with the organization's need for a central location for security administrators to perform these specific tasks.

A. Emergency response team (ERT): An ERT is a group of people designated to respond to various emergencies (e.g., medical, fire), not a centralized facility for continuous cybersecurity monitoring.

C. Disaster response team (DRT): A DRT is a team focused on recovery operations after a major disaster has occurred, which is distinct from the day-to-day security monitoring and threat response function.

D. Network operations center (NOC): A NOC's primary focus is on network performance, availability, and uptime, not on security. While a NOC monitors traffic, its goal is to prevent outages, whereas a SOC's goal is to prevent security breaches.

1. National Institute of Standards and Technology (NIST). Glossary of Key Information Security Terms

NISTIR 7298 Rev. 3. (May 2018). Page 168. The document defines a Security Operations Center as: "A centralized function within an organization employing people

processes

and technology to continuously monitor and improve an organization's security posture while preventing

detecting

analyzing

and responding to cybersecurity incidents."

2. Carnegie Mellon University

Software Engineering Institute (SEI). Al-Shaer

E.

et al. Ten Strategies of a World-Class Cybersecurity Operations Center. (December 2014). Section 1.1

Page 2. This publication states

"A cybersecurity operations center (CSOC) is the organizational unit...responsible for coordinating the defense of an enterprise’s information assets."

3. Microsoft Azure Documentation. Security Operations Center (SOC). (Accessed 2023). The documentation clarifies the distinction between a SOC and a NOC: "A NOC team is focused on maintaining network uptime... A SOC team is focused on protecting the organization from cyberattacks."

4. AWS Well-Architected Framework. Security Pillar. (July 2023). Page 53. The framework describes a SOC as a "team of security professionals that monitors an organization’s IT infrastructure to detect cybersecurity events and to prevent and resolve security incidents."

Escrow is a legal arrangement where a third party holds an asset, in this case, a copy of the organization's data, on behalf of the other two parties (the organization and the cloud provider). The asset is released to the organization upon the occurrence of a contractually defined condition, such as the provider's bankruptcy or business failure. This mechanism directly addresses the organization's requirement to ensure access to its critical data if the cloud provider cannot fulfill its obligations, providing a crucial layer of business continuity.

A. Indemnification: This is a contractual obligation for one party to compensate another for specific losses or damages; it provides financial protection, not a mechanism for data recovery.

C. Offboarding: This refers to the standard procedures for terminating a service and returning or deleting customer data at the end of a contract, not a contingency for provider failure.

D. Encryption: This is a technical control to ensure data confidentiality. It does not guarantee the availability or return of data if the provider goes out of business.

1. Cloud Security Alliance (CSA). Security Guidance for Critical Areas of Focus in Cloud Computing v4.0. (2017). In Domain 4: Cloud Computing Governance and Risk Management

the guidance discusses the importance of contractual provisions for business continuity and exit strategies. It notes the need for "provisions for retrieving data from a provider that has gone out of business

" which is the function of a data escrow agreement. (See Section: "Domain 4: Cloud Computing Governance and Risk Management

" subsection on Contractual Security Requirements).

2. Jansen

W.

& Grance

T. Guidelines on Security and Privacy in Public Cloud Computing (NIST Special Publication 800-144). (2011). National Institute of Standards and Technology. Section 6.3

"Service Agreements

" discusses the need for clear terms regarding data ownership and procedures if a provider ceases operations

stating that an organization should "understand what will happen to its data and services in the case of an acquisition or business failure of the cloud provider." An escrow provision is a primary method to address this risk. (p. 31).

3. Subashini

S.

& Kavitha

V. (2011). A survey on security issues in service delivery models of cloud computing. Journal of Network and Computer Applications

34(1)

1-11. In the discussion of data security and availability

the paper identifies provider failure as a significant risk and mentions "data escrow services" as a potential solution to ensure customers can retrieve their data. (Section 4.1. Data Issues

p. 5). https://doi.org/10.1016/j.jnca.2010.07.006

Crypto-shredding, also known as cryptographic erasure, is a method used to sanitize or destroy data. The process involves encrypting the target data with a strong encryption key and then deliberately and securely deleting or overwriting that key. Without the key, the encrypted data (ciphertext) is rendered unrecoverable, which is functionally equivalent to its destruction. This technique is a core component of the "Destroy" phase of the cloud data life cycle, ensuring data is permanently and securely eliminated when it is no longer needed.

B. Create: This phase involves the generation of new data. While data may be encrypted upon creation, the destruction of its key does not occur here.

C. Archive: This phase is for long-term, inactive data retention. Data is preserved and protected, which is the opposite of the destruction accomplished by crypto-shredding.

D. Store: This phase involves committing data to a repository for active use. The goal is to maintain data availability and integrity, not to destroy it.

1. Cloud Security Alliance (CSA). Security Guidance for Critical Areas of Focus in Cloud Computing v4.0. (2017). In Domain 2: Governance and Enterprise Risk Management

the Data Security Lifecycle section describes the "Destroy" phase. It explicitly states

"For data in the cloud

the most viable option for data destruction is cryptographic erasure (crypto-shredding)." (p. 39).

2. National Institute of Standards and Technology (NIST). NIST Special Publication 800-88 Revision 1: Guidelines for Media Sanitization. (December 2014). Section 2.5

"Cryptographic Erase (CE)

" defines the process as using "the encryption of target data as a method of sanitization" where "the media is sanitized by erasing the cryptographic key." This publication categorizes CE as a method for data purging and destruction.

3. Mell

P.

& Grance

T. NIST Special Publication 800-144: Guidelines on Security and Privacy in Public Cloud Computing. (December 2011). Section 6.3

"Data Disposal

" discusses the challenges of verifying data deletion in the cloud and notes that "a possible solution is to encrypt the data and to discard the keys when the data is no longer needed

" which is the definition of crypto-shredding as a destruction method. (p. 22).

4. Fernandes

D. A. B.

Soares

L. F. B.

Gomes

J. V.

Freire

M. M.

& Inácio

P. R. M. (2014). "Security issues in cloud environments: a survey." International Journal of Information Security

13(2)

113–170. Section 5.3

"Data Deletion

" discusses crypto-shredding as a primary technique for secure data deletion in multi-tenant cloud environments

aligning it with the data destruction phase. (DOI: https://doi.org/10.1007/s10207-013-0208-7).

Cryptographic erasure, also known as crypto-shredding, is a data sanitization technique where data is first encrypted, and then the cryptographic keys required to decrypt that data are securely and deliberately destroyed. By eliminating the keys, the encrypted data (ciphertext) is rendered unrecoverable, effectively destroying the information. The process described in the question—encrypting data and then destroying the keys used for that encryption—is the precise definition of cryptographic erasure. This method is particularly prevalent and recommended in cloud environments where the customer does not have physical control over the storage media.

A. One-way hashing: This process creates a non-reversible, fixed-length digest of data for integrity verification, not for data destruction or sanitization.

B. Degaussing: This is a physical sanitization method that uses a strong magnetic field to destroy data on magnetic media; it does not involve encryption.

C. Overwriting: This technique involves writing new patterns of data over the original data to make it unrecoverable; it is a different method from key destruction.

1. National Institute of Standards and Technology (NIST) Special Publication 800-88 Revision 1

Guidelines for Media Sanitization.

Section 2.5

"Cryptographic Erase (CE)": "Cryptographic Erase (CE) is a method of sanitization where the media is sanitized by erasing the cryptographic key that was used to encrypt the data

leaving only the ciphertext." (Page 8).

Appendix A

"Sanitization and Disposition Decision Flow": Describes CE as a valid sanitization method for devices that support it

such as Self-Encrypting Drives (SEDs).

2. Cloud Security Alliance (CSA)

Security Guidance for Critical Areas of Focus in Cloud Computing v4.0.

Domain 11: Data Security & Encryption

"Data Destruction" section: "Cryptographic erasure (or crypto-shredding) is a viable option for rendering data unrecoverable. With this method

data is encrypted by a key

and the key is destroyed to make the data unrecoverable." (Page 128).

3. ISO/IEC 27040:2015

Information technology — Security techniques — Storage security.

Section 7.5.6

"Cryptographic erase": This standard defines cryptographic erase as a method that can be used to sanitize data on storage media by sanitizing the media encryption keys

which renders the encrypted data unreadable. It notes this is often the only feasible option for sanitizing certain technologies.

In the context of release management and DevOps, a pipeline is the specific term for the automated workflow that moves a software change from its initial implementation to production. This process typically includes stages for building the code, automated code review and analysis, various testing phases (unit, integration, security), and finally, deployment. The pipeline automates this entire sequence, ensuring consistency, speed, and reliability in software delivery, which directly matches the process described in the question.

A. Iteration: An iteration is a time-boxed development cycle within an agile framework (e.g., a sprint), not the automated deployment process itself.

B. Baseline: A baseline is a fixed, formally reviewed version of a product or configuration item that serves as a point of reference for future development.

D. Framework: A framework is a set of guiding principles, best practices, and tools, not the specific, automated workflow for releasing code.

1. Google Cloud Documentation. (n.d.). DevOps tech: Continuous integration. Google Cloud. Retrieved from https://cloud.google.com/devops/tech/continuous-integration.

Reference Point: In the "What is continuous integration?" section

it states

"CI is the first step in the path to production

which is often visualized as a pipeline. A pipeline is a series of automated steps that your code changes must pass through on their way to production."

2. Amazon Web Services (AWS) Documentation. (n.d.). What is a CI/CD Pipeline? AWS. Retrieved from https://aws.amazon.com/devops/ci-cd-pipeline/.

Reference Point: The document defines

"A CI/CD pipeline is a series of steps that must be performed in order to deliver a new version of software. CI/CD pipelines are a practice focused on improving software delivery throughout the software development life cycle via automation."

3. Jabbari

R.

bin Ali

N.

Petersen

K.

& Tanveer

B. (2016). What is DevOps? A Systematic Mapping Study on Definitions and Practices. 2016 23rd Asia-Pacific Software Engineering Conference (APSEC)

395-402. https://doi.org/10.1109/APSEC.2016.068

Reference Point: In Section IV

Part A

"Practices

" the paper defines the Deployment Pipeline as "an automated process for managing all changes

from check-in to release." This confirms the academic definition of a pipeline as the end-to-end automated process.

Infrastructure as a Service (IaaS) is the cloud service model that provides fundamental computing resources on demand. This model offers virtualized components such as servers (compute), storage (e.g., block storage), and networking. It allows organizations to rent IT infrastructure from a cloud provider on a pay-as-you-go basis, giving them the highest level of control to build and manage their own custom IT solutions. The consumer does not manage the underlying physical hardware but has control over operating systems, storage, and deployed applications. This directly matches the description of accessing "basic building blocks."

A. Networking as a service (NaaS) is a more specific model that focuses exclusively on providing network resources and is considered a component within the broader IaaS category.

B. Platform as a service (PaaS) abstracts the underlying infrastructure, providing a platform (e.g., operating systems, databases) for developers to build and run applications without managing servers.

C. Software as a service (SaaS) delivers ready-to-use software applications over the internet, where the provider manages the entire stack, from infrastructure to the application itself.

1. Mell

P.

& Grance

T. (2011). The NIST Definition of Cloud Computing (NIST Special Publication 800-145). National Institute of Standards and Technology. Retrieved from https://doi.org/10.6028/NIST.SP.800-145.

Section 2

"Definitions

" page 3: "Cloud Infrastructure as a Service (IaaS). The capability provided to the consumer is to provision processing

storage

networks

and other fundamental computing resources where the consumer is able to deploy and run arbitrary software

which can include operating systems and applications."

2. Amazon Web Services (AWS). (n.d.). What is IaaS? AWS Documentation.

Paragraph 1: "Infrastructure as a Service (IaaS) contains the basic building blocks for cloud IT. It typically provides access to networking features

computers (virtual or on dedicated hardware)

and data storage space."

3. Microsoft Azure. (n.d.). What is IaaS? Infrastructure as a service. Azure Documentation.

Overview Section: "Infrastructure as a service (IaaS) is a type of cloud computing service that offers essential compute

storage

and networking resources on demand

on a pay-as-you-go basis."

4. Armbrust

M.

Fox

A.

Griffith

R.

Joseph

A. D.

Katz

R.

Konwinski

A.

... & Zaharia

M. (2010). A view of cloud computing. Communications of the ACM

53(4)

50-58. https://doi.org/10.1145/1721654.1721672

Section 3

"Classes of Utility Computing

" page 51: "IaaS is the lowest-level

offering basic server and storage... The service provider owns the equipment and is responsible for housing

running

and maintaining it. The user

in turn

pays for what they use."

A rollback is the process of reverting a system's state to a previously known, stable version. In the context of network-as-code, where infrastructure is defined and versioned like software, a bug introduced in a new release can be quickly remediated by deploying the last known good version of the code. This action directly and immediately restores functionality to the production site, which is the primary goal after a failed deployment. The other options are preventative measures that occur before a release, not restorative actions taken after a failure has occurred in production.

A. Staging: This is a pre-production environment used for testing before a release. It is a preventative safeguard, not a method to restore a live production site.

B. Code review: This is a quality assurance process to detect flaws before code is deployed. It is a preventative measure, not a recovery mechanism for a live system.

C. Code testing: This is the process of executing code to find bugs before a release. It is a preventative control, not a method for restoring a failed production environment.

1. Official Vendor Documentation: AWS CloudFormation User Guide

"Stack updates

" section on "Monitoring the progress of a stack update." The documentation states

"By default

if the stack update fails

CloudFormation rolls back all changes to the stack's previous working state." This exemplifies rollback as a standard recovery mechanism in an Infrastructure as Code (IaC) service.

2. Peer-reviewed Academic Publication: Rahman

A.

& Williams

L. (2016). "On the relationships between build failures

continuous integration

and fault-proneness: An empirical study of open source projects." 2016 IEEE International Conference on Software Quality

Reliability and Security (QRS). While focused on CI

the paper's context on build management highlights that a key tenet of CI/CD is the ability to quickly revert changes

i.e.

rollback

if a build introduces faults (p. 160

Section III-B). DOI: 10.1109/QRS.2016.29

3. University Courseware: Ousterhout

J. (2018). Lecture notes for CS 140: Operating Systems. Stanford University. Lecture 18

"Crash Recovery

" discusses the fundamental principle of using a stable

previous state (like a checkpoint or log) to recover from failures

which is the core concept of a rollback in deployment scenarios (pp. 5-7).

An incident, in the context of IT Service Management (ITSM) and security, is defined as an unplanned interruption to a service or a reduction in its quality. The scenario describes an "unplanned event" leading to a "loss of service," which is a classic service disruption. The primary objective of the incident management process is to restore normal service operation as quickly as possible and minimize the adverse impact on business operations. Therefore, the incident generated seeks to resolve the service disruption.

A. Change: A change is a planned and authorized activity to add, modify, or remove something that could have an effect on IT services. The event described was unplanned.

B. Error: An error is a known underlying cause of one or more incidents. Resolving the root-cause error is the goal of problem management, not the immediate incident response.

D. Bug: A bug is a specific type of error in software code. While a bug may have caused the incident, the immediate goal is to restore service, not necessarily to fix the bug itself.

1. NIST Special Publication 800-61 Rev. 2

Computer Security Incident Handling Guide (December 2012). Section 2.1 defines an incident

and the overall goal of the incident handling process described in Section 3 is to recover from the event

which involves resolving the service disruption (loss of availability).

2. Iden

J.

& Eikebrokk

T. R. (2013). Implementing IT Service Management: A systematic literature review. International Journal of Information Management

33(3)

512-523. This paper references the standard ITIL definition of an incident as an "unplanned interruption to an IT Service or a reduction in the quality of an IT Service" (p. 515)

which directly corresponds to a disruption. https://doi.org/10.1016/j.ijinfomgt.2013.01.004

3. AWS Security Incident Response Guide (August 2022). In the "Preparation" section

it states

"Your goal is to respond to an incident to limit the disruption and begin recovery" (p. 4). This aligns the goal of incident response with resolving the disruption.

To ensure organization-wide trust for internally generated certificates, a central, trusted entity must issue and sign them. This entity is the Certificate Authority (CA). An organization establishes its own internal CA server, and its root certificate is installed on all devices and systems within the organization's control. This action establishes a "chain of trust." Consequently, any certificate that is subsequently generated and signed by this internal CA server will be automatically trusted by all entities within the organization, fulfilling the stated requirement.

A. Individual users’ private keys are used for personal authentication, signing, and decryption; they cannot issue certificates that are trusted by the entire organization.

B. A certificate repository server is a storage and distribution point for certificates and revocation lists, but it does not have the function to generate or sign them.

D. Individual systems' private keys are used for that specific system's cryptographic functions, not for issuing certificates to other entities in a trusted manner.

1. National Institute of Standards and Technology (NIST). (2020). Special Publication (SP) 800-57 Part 1 Rev. 5: Recommendation for Key Management

Part 1: General. Section 2.1.3

"Public Key Infrastructure

" states

"A CA is an authority trusted by one or more users to create and assign public key certificates... The CA is the component that users trust to bind public keys to identities."

2. Microsoft Corporation. (2021). Public Key Infrastructure Design Guidance. Microsoft Learn. In the "Role of the Certification Authority" section

it is detailed that "A certification authority (CA) is responsible for establishing and vouching for the identity of users

computers

and organizations... By issuing a digitally signed certificate

the CA attests to the identity of the certificate subject."

3. Pfleeger

C. P.

Pfleeger

S. L.

& Margulies

J. (2015). Security in Computing (5th ed.). Pearson Education. Chapter 5

"Cryptography in Practice

" Section 5.4

"Public Key Infrastructure

" explains that the CA is the trusted third party that signs certificates

and its public key serves as the root of trust for validating other certificates within its domain.

Electronic discovery, often abbreviated as e-discovery, is the formal legal process of identifying, preserving, collecting, processing, reviewing, and producing electronically stored information (ESI) in response to a request for production in a lawsuit or investigation. It encompasses the entire procedure of locating and securing digital data for use as evidence in legal proceedings. This process is governed by rules of civil procedure and is a critical component of modern litigation.

A. Chain of custody: This is a chronological record documenting the handling and control of evidence to ensure its integrity, not the discovery process itself.

B. Forensic imaging: This is a specific technical method for creating an exact, bit-for-bit copy of a storage device, which is a step within the e-discovery process.

D. Gap analysis: This is a business management technique used to compare the actual performance of an organization with its potential or desired performance.

1. Cloud Security Alliance (CSA). (2017). Security Guidance for Critical Areas of Focus in Cloud Computing v4.0. Domain 6: Legal Issues: Contracts and Electronic Discovery

p. 75. The document defines e-discovery as "the process of identifying and producing ESI in litigation."

2. Kent

K.

Chevalier

S.

Grance

T.

& Dang

H. (2006). Guide to Integrating Forensic Techniques into Incident Response (NIST SP 800-86). National Institute of Standards and Technology. Section 2.4.2

p. 13

discusses e-discovery as a major consideration for organizations when handling data that may be involved in litigation.

3. Legal Information Institute (LII)

Cornell Law School. "Electronic Discovery." This resource defines electronic discovery as "any process in which electronic data is sought

located

secured

and searched with the intent of using it as evidence in a civil or criminal legal case."

4. The Sedona Conference. (2007). The Sedona Principles

Second Edition: Best Practices Recommendations & Principles for Addressing Electronic Document Production. The Sedona Conference Journal

8

1-58. Principle 1

p. 10

establishes that electronically stored information is discoverable and subject to the same legal rules as tangible evidence.

For long-term storage of backup data in the cloud, encryption is a fundamental security control. Access to this encrypted data is entirely dependent on the availability of the corresponding decryption keys. A robust key management plan, which governs the entire lifecycle of cryptographic keys (generation, storage, use, archival, and destruction), is essential. If the keys are lost, corrupted, or the systems managing them become obsolete, the organization will permanently lose access to its own encrypted backup data. Therefore, addressing key management is the most critical factor to prevent this specific risk.

A. Quantum computing: This is a future threat to the confidentiality of current encryption algorithms, not a direct cause of losing access due to current operational mismanagement.

B. Change tracking: This is a process for monitoring modifications to data or configurations, which is important for integrity and auditing but does not control access to the data itself.

D. Regulatory compliance: This involves adhering to laws and standards. While compliance may mandate encryption and key management, it is the failure of the technical control (key management) itself that causes the loss of access.

1. National Institute of Standards and Technology (NIST) Special Publication 800-57 Part 1

Rev. 5

Recommendation for Key Management. Section 8.1.6

"Key Archival

" states

"If an archive of cryptographic keys is not maintained

access to the encrypted data will be lost when the keys are destroyed. Therefore

the loss of an archive of keys used to encrypt stored data may be catastrophic."

2. Cloud Security Alliance (CSA)

Security Guidance for Critical Areas of Focus in Cloud Computing v4.0. In Domain 11: Data Security and Encryption

the document emphasizes

"Proper key management is the most important aspect to get right when using cryptography... If keys are not properly secured

the entire security of the encryption is negated. If keys are lost

so is the data." (p. 121).

3. Armknecht

F.

& Westhoff

D. (2012). Security and Trust in Cloud Systems. In Secure Cloud Computing (pp. 3-19). Springer. This academic text discusses the challenges of cloud security

noting that for long-term data storage

"the long-term secure management of the corresponding keys is a major challenge. The loss of a key usually implies the loss of all data encrypted with it." (Section 2.2

Challenges).

The Agile methodology is an iterative approach to software development that prioritizes customer satisfaction and flexibility. Its core principles, as defined in the Agile Manifesto, emphasize early and continuous delivery of functional software, close collaboration with customers, and the ability to welcome and adapt to changing requirements, even late in the development cycle. This contrasts with more rigid, sequential models. The focus is on delivering value and responding to change over strictly following a predefined plan, which directly aligns with the scenario described.

B. Spiral: The Spiral model is iterative, but its primary focus is on risk analysis and mitigation at each stage, not specifically on welcoming late-stage requirement changes.

C. Waterfall: This is a linear, sequential model where each phase must be completed before the next begins. It is known for its rigidity and difficulty in accommodating changes.

D. Lean: While sharing principles with Agile, Lean's primary focus is on eliminating waste and optimizing the development process to deliver value, rather than specifically on customer collaboration and changing requirements.

1. Beck

K.

Beedle

M.

van Bennekum

A.

Cockburn

A.

Cunningham

W.

Fowler

M.

Grenning

J.

Highsmith

J.

Hunt

A.

Jeffries

R.

Kern

J.

Marick

B.

Martin

R. C.

Mellor

S.

Schwaber

K.

Sutherland

J.

& Thomas

D. (2001). Manifesto for Agile Software Development. Agile Alliance. Retrieved from https://agilemanifesto.org/principles.html. The principles state

"Our highest priority is to satisfy the customer through early and continuous delivery of valuable software

" and "Welcome changing requirements

even late in development."

2. Boehm

B. (1988). A spiral model of software development and enhancement. Computer

21(5)

61-72. https://doi.org/10.1109/2.59. This foundational paper describes the Spiral model's emphasis on risk-driven iterations (see Figure 4

p. 65)

which is a different primary focus than that described in the question.

3. Royce

W. W. (1970). Managing the development of large software systems. Proceedings of IEEE WESCON

26(August)

1-9. This paper

often cited as the origin of the Waterfall model

describes a sequential

non-iterative process where feedback loops are treated as rework

highlighting its inflexibility to change.

4. Poppendieck

M.

& Poppendieck

T. (2003). Lean Software Development: An Agile Toolkit. Addison-Wesley Professional. The core principles of Lean software development are detailed as: Eliminate Waste

Amplify Learning

Decide as Late as Possible

Deliver as Fast as Possible

Empower the Team

Build Integrity In

and See the Whole. While related to Agile

the emphasis is on process optimization.

The relationship and all service obligations between a cloud provider and a customer are governed by the contract or Service Level Agreement (SLA). In a standard multi-tenant cloud environment, a single physical drive often stores data for multiple customers (resource pooling). Therefore, physically destroying a drive upon a single customer's request is operationally infeasible as it would destroy other customers' data. Such a specific and costly service as dedicated hardware disposal must be explicitly negotiated and stipulated in the contract, which is typically available only for private or dedicated hosting models. Without this contractual provision, the provider is not obligated to fulfill the request and will instead follow their standard, secure data sanitization procedures.

A. "Hardware disposal insurance" is not a standard industry term; service obligations are defined by the contract, not a specific type of insurance.

B. Cryptographic erasure is a valid data sanitization method, but it does not fulfill the customer's specific request for physical destruction.

D. Degaussing is a data sanitization method for magnetic media, but it is not the physical destruction that the customer specifically requested.

1. Cloud Security Alliance. (2017). Security Guidance for Critical Areas of Focus in Cloud Computing v4.0. Domain 2: Governance and Enterprise Risk Management

p. 31. The document states

"The contract is the only guarantee of any level of service or commitment from the provider

" underscoring that specific actions like physical destruction must be contractually defined.

2. Mell

P.

& Grance

T. (2011). The NIST Definition of Cloud Computing (NIST SP 800-145). p. 2

"Essential Characteristics." The concept of "Resource Pooling" explains that provider resources are pooled to serve multiple consumers

making the destruction of a shared drive for a single customer impractical without a specific contractual arrangement for dedicated resources.

3. National Institute of Standards and Technology (NIST). (2014). Special Publication 800-88 Rev. 1

Guidelines for Media Sanitization. Section 2.3

"Destroy." This publication defines "Destroy" as a distinct category of sanitization

separate from "Purge" (e.g.

degaussing) and "Clear" (e.g.

cryptographic erase)

confirming that the customer's request is for a specific action that may differ from the provider's standard procedures.

4. ISO/IEC 27017:2015. Information technology — Security techniques — Code of practice for information security controls based on ISO/IEC 27002 for cloud services. Annex A

Control A.8.3.2

"Disposal of media." This standard advises cloud customers to seek assurance on the provider's disposal methods

implying these terms are part of the service agreement.

The Payment Card Industry Data Security Standard (PCI DSS) provides a specific mechanism for entities that cannot meet a requirement as stated due to legitimate technical or business constraints. This mechanism is the implementation of a "compensating control." A compensating control must meet the intent and rigor of the original PCI DSS requirement, provide a similar level of defense, and be "above and beyond" other PCI DSS requirements. In this scenario, since the legacy system prevents encryption, the cloud provider must implement alternative controls to sufficiently mitigate the risk of storing unencrypted cardholder data to maintain compliance.

A. Privacy control: This is a general term. While related, it is not the specific mechanism defined within the PCI DSS framework for addressing an inability to meet a technical requirement.

B. Protection levels: This is a vague concept and not a formal term or process within the PCI DSS standard for achieving compliance when a specific control is not met.

C. Risk acceptance: Formally accepting the risk of not encrypting cardholder data is not a valid option for compliance with a mandatory PCI DSS requirement and would result in a finding of non-compliance.

1. PCI Security Standards Council (PCI SSC). Payment Card Industry (PCI) Data Security Standard Requirements and Security Assessment Procedures

Version 4.0. (May 2024). In Appendix B: Compensating Controls

the document states

"For many PCI DSS requirements

there may be more than one way to meet the requirement’s stated objective... PCI DSS also allows for compensating controls to be considered when an entity cannot meet a requirement explicitly as stated

due to a legitimate and documented technical or business constraint." (p. 211).

2. PCI Security Standards Council (PCI SSC). Navigating PCI DSS v4.0: A Guide for Assessors and Other Professionals. (May 2024). Section "Compensating Controls" explains: "Compensating controls are alternate security measures that can be used to meet a PCI DSS requirement when an entity is unable to meet the requirement as stated." (p. 13).

3. Amazon Web Services (AWS). PCI DSS Standard on AWS. (Rev. March 2024). The whitepaper discusses compliance strategies

stating

"If a customer is unable to meet a specific PCI DSS requirement due to a legitimate technical or business constraint

they can implement a compensating control... The compensating control must provide a similar level of defense as the original requirement." (p. 10).