CCAK Isaca Certificate of Cloud Auditing Knowledge Free Practice Exam Questions (2025 Updated)

Understanding the organization’s past is crucial for individuals in charge of cloud compliance, particularly to address any open findings from previous external audits. This historical perspective is essential because it allows the compliance team to identify recurring issues, understand the context of past non-compliances, and ensure that corrective actions have been taken and are effective. It also helps in anticipating potential future compliance challenges based on past trends and patterns.

References = The importance of understanding an organization’s past for cloud compliance is supported by best practices in cloud security and compliance, which emphasize the need for continuous improvement and learning from past experiences to enhance security measures123.

 The management review of the information security framework is an activity that typically occurs outside the regular scope of information security monitoring. This review is a strategic exercise that involves evaluating the overall direction, effectiveness, and alignment of the information security program with the organization’s objectives and risk appetite. It is more about governance and ensuring that the security framework is up-to-date and capable of protecting the organization against current and emerging threats. This contrasts with the operational nature of security monitoring, which focuses on the day-to-day oversight of security controls and the detection of security events.

References = The answer provided is based on general knowledge of information security practices and the typical separation between strategic management activities and operational monitoring tasks. Direct references from the Cloud Auditing Knowledge (CCAK) documents and related resources by ISACA and the Cloud Security Alliance (CSA) are not included here, as my current capabilities do not allow me to access or verify content from external documents or websites. However, the concept of separating strategic management reviews from operational monitoring is a well-established practice in information security management.

Visibility to the source code within build scripts would give an auditor the best view of design and implementation decisions when an organization uses programmatic automation for Infrastructure as a Service (IaaS) deployments. IaaS is a cloud service model that provides virtualized computing resources, such as servers, storage, network, and operating systems, over the internet. Programmatic automation is the process of using code or scripts to automate the provisioning, configuration, management, and monitoring of the cloud infrastructure. Build scripts are files that contain commands or instructions to create or modify the cloud infrastructure according to the desired specifications.12

An auditor can use the source code within build scripts to gain insight into how the organization designs and implements its cloud infrastructure. The source code can reveal the following information3:

The type, size, and number of cloud resources that are provisioned and deployed

The configuration settings and parameters that are applied to the cloud resources

The security controls and policies that are enforced on the cloud resources

The dependencies and relationships between the cloud resources

The testing and validation methods that are used to verify the functionality and performance of the cloud resources

The logging and auditing mechanisms that are used to track and record the changes and activities on the cloud resources

By reviewing the source code within build scripts, an auditor can evaluate whether the organization follows the best practices and standards for cloud infrastructure design and implementation, such as scalability, reliability, security, compliance, and efficiency. An auditor can also identify any gaps or risks in the organization’s cloud infrastructure and provide recommendations for improvement.

References := What is Infrastructure as Code? | Cloud Computing - AWS1; What is Programmatic Automation? - Definition from Techopedia2; How to audit your IaC for better DevSecOps - TechBeacon3

DevSecOps is an approach that integrates security practices into every phase of the software development lifecycle. It emphasizes the incorporation of security from the beginning, rather than as an afterthought, and utilizes automation to ensure security measures are consistently applied throughout the development process. This method allows for early detection and resolution of security issues, making it an essential practice for organizations with mature security programs and cloud adoption.

References = The definition and best practices of DevSecOps are well-documented in resources provided by leading industry authorities such as Microsoft1 and IBM2, which describe DevSecOps as a framework that automates the integration of security into the software development lifecycle.

Requirements define control activities, which are the actions, processes, or mechanisms that are implemented to achieve the control objectives1. Control objectives are the targets or desired conditions to be met that are designed to ensure that policy intent is met2. Guidelines are the recommended practices or advice that provide flexibility in how to implement a policy, standard, or control3. Policies are the statements of management’s intent that establish the direction, purpose, and scope of an organization’s internal control system4.

References:

COSO – Control Activities - Deloitte1, section on Control Activities

Words Matter - Understanding Policies, Control Objectives, Standards …2, section on Control Objectives

Understanding Policies, Control Objectives, Standards, Guidelines …3, section on Guidelines

Internal Control Handbook4, section on Policies

 In the context of Infrastructure as a Service (IaaS), a vulnerability assessment will scan virtual machines to identify vulnerabilities in both operating system and application infrastructure contained within the customer’s instances. IaaS is a cloud service model that provides customers with access to virtualized computing resources, such as servers, storage, and networks, hosted by a cloud service provider (CSP). The customer is responsible for installing, configuring, and maintaining the operating system and application software on the virtual machines, while the CSP is responsible for managing the underlying physical infrastructure. Therefore, a vulnerability assessment will scan the customer’s instances to detect any weaknesses or misconfigurations in the operating system and application layers that may expose them to potential threats. A vulnerability assessment can help the customer to prioritize and remediate the identified vulnerabilities, and to comply with relevant security standards and regulations12.

References:

Azure Security Control - Vulnerability Management | Microsoft Learn

How to Implement Enterprise Vulnerability Assessment - Gartner

An external audit is an appropriate tool and technique to support a customer’s verification of the cloud service provider’s claims regarding its responsibilities according to the shared responsibility model. An external audit is an independent and objective examination of the cloud service provider’s policies, procedures, controls, and performance by a qualified third-party auditor. An external audit can provide assurance that the cloud service provider is fulfilling its obligations and meeting the customer’s expectations in terms of security, compliance, availability, reliability, and quality. An external audit can also identify any gaps or weaknesses in the cloud service provider’s security posture and suggest recommendations for improvement.

An external audit can be based on various standards, frameworks, and regulations that are relevant to the cloud service provider’s industry and domain. For example, some common external audits for cloud service providers are:

ISO/IEC 27001: This is an international standard that specifies the requirements for establishing, implementing, maintaining, and continually improving an information security management system (ISMS). An ISMS is a systematic approach to managing sensitive information so that it remains secure. An ISO/IEC 27001 certification demonstrates that the cloud service provider has implemented a comprehensive and effective ISMS that covers all aspects of information security, including risk assessment, policy development, asset management, access control, incident management, business continuity, and compliance.1

SOC 2: This is an attestation report that evaluates the cloud service provider’s security controls based on the American Institute of Certified Public Accountants (AICPA) Trust Services Criteria. The Trust Services Criteria are a set of principles and criteria for evaluating the design and operating effectiveness of controls that affect the security, availability, processing integrity, confidentiality, and privacy of a system. A SOC 2 report provides assurance that the cloud service provider has implemented adequate controls to protect the customer’s data and systems.2

CSA STAR: This is a program for flexible, incremental, and multi-layered cloud provider certification and/or attestation according to the Cloud Security Alliance’s industry leading security guidance and control framework. The CSA STAR program consists of three levels of assurance: Level 1: Self-Assessment, Level 2: Third-Party Audit, and Level 3: Continuous Auditing. The CSA STAR program aims to provide transparency, assurance, and trust in the cloud ecosystem by enabling customers to assess and compare the security and compliance posture of cloud service providers.3

The other options listed are not suitable for supporting a customer’s verification of the cloud service provider’s claims regarding its responsibilities according to the shared responsibility model. An internal audit is an audit conducted by the cloud service provider itself or by an internal auditor hired by the cloud service provider. An internal audit may not be as independent or objective as an external audit, and it may not provide sufficient evidence or credibility to the customer. A contractual agreement is a legal document that defines the roles, responsibilities, expectations, and obligations of both the cloud service provider and the customer. A contractual agreement may specify the terms and conditions for service delivery, performance, availability, security, compliance, data protection, incident response, dispute resolution, liability, and termination. However, a contractual agreement alone does not verify or validate whether the cloud service provider is actually fulfilling its claims or meeting its contractual obligations. A security assessment is a process of identifying, analyzing, and evaluating the security risks and vulnerabilities of a system or an organization. A security assessment may involve various methods such as vulnerability scanning, penetration testing, threat modeling, or risk analysis. A security assessment may provide useful information about the current state of security of a system or an organization, but it may not cover all aspects of the shared responsibility model or provide assurance that the cloud service provider is complying with its responsibilities on an ongoing basis.

 The three layers of the Open Certification Framework (OCF) primarily help cloud service providers and cloud clients improve the level of transparency and assurance. The OCF is designed to provide a trusted and independent evaluation of cloud providers through a flexible, incremental, and multi-layered certification process. This framework enhances transparency by making it easier for consumers to understand and compare providers’ security and compliance capabilities. Additionally, it offers assurance by integrating with third-party assessment and attestation statements, thereby increasing the security baseline for all participants.

References = The benefits of the OCF in improving transparency and assurance are detailed in the Cloud Security Alliance’s documentation on the Open Certification Framework1.

SLAs in cloud computing define performance metrics and uptime commitments, making them crucial for monitoring and measuring service delivery against predefined benchmarks. Metrics from SLAs help in tracking service performance, compliance with contractual obligations, and cloud service provider accountability. ISACA’s CCAK outlines the importance of SLAs for cloud governance and risk management, as they provide a measurable baseline that informs cloud audit activities (referenced in CCM under Governance, Risk, and Compliance - GOV-05).

=========================

 The organization (client) is accountable for the use of a cloud service. Accountability in cloud computing is the responsibility of cloud service providers and other parties in the cloud ecosystem to protect and properly process the data of their clients and users. However, accountability ultimately rests with the organization (client) that uses the cloud service, as it is the data owner and controller. The organization (client) has to ensure that the cloud service provider and its suppliers meet the agreed-upon service levels, security standards, and regulatory requirements. The organization (client) also has to perform due diligence and oversight on the cloud service provider and its suppliers, as well as to comply with the shared responsibility model, which defines how the security and compliance tasks and obligations are divided between the cloud service provider and the organization (client)123.

The other options are not correct. Option A, the cloud access security broker (CASB), is incorrect because a CASB is a software tool or service that acts as an intermediary between cloud users and cloud service providers, providing visibility, data security, threat protection, and compliance. A CASB does not use the cloud service, but facilitates its secure and compliant use4. Option B, the supplier, is incorrect because a supplier is a third-party entity that provides services or products to the cloud service provider, such as infrastructure, software, hardware, or support. A supplier does not use the cloud service, but supports its delivery5. Option C, the cloud service provider, is incorrect because a cloud service provider is a company that provides cloud computing services to the organization (client). A cloud service provider does not use the cloud service, but offers it to the organization (client)6. References :=

Accountability Issues in Cloud Computing (5 Step … - Medium1

Shared responsibility in the \uE000cloud\uE001 - Microsoft Azure2

Who Is Responsible for Cloud Security? - Security Intelligence3

What is CASB? - Cloud Security Alliance4

Cloud Computing: Auditing Challenges - ISACA5

What is Cloud Provider? - Definition from Techopedia

 The CSA STAR registry is a publicly accessible registry that documents the security and privacy controls provided by popular cloud computing offerings. The registry is based on the Cloud Controls Matrix (CCM), which is a framework of cloud-specific security best practices, and the GDPR Code of Conduct, which is a set of privacy principles for cloud service providers. The registry allows cloud customers to assess the security and compliance posture of cloud service providers, as well as to compare different providers based on their level of assurance. The registry also reduces the complexity and cost of filling out multiple customer questionnaires and requests for proposal (RFPs). Therefore, the best recommendation to reduce the provider’s burden is to direct all customer inquiries to the information in the CSA STAR registry, which can demonstrate the provider’s transparency, trustworthiness, and adherence to industry standards. The provider can also encourage customers to use the Consensus Assessments Initiative Questionnaire (CAIQ), which is a standardized set of questions based on the CCM, to evaluate the provider’s security controls. Alternatively, the provider can pursue higher levels of assurance, such as third-party audits or continuous monitoring, to further validate their security and privacy practices and increase customer confidence.

References:

STAR Registry | CSA

STAR | CSA

CSA Security Trust Assurance and Risk (STAR) Registry Reaches Notable …

Why CSA STAR Is Important for Cloud Service Providers - A-LIGN

When applying the Top Threats Analysis methodology following an incident, the scope of the technical impact identification step is to determine the impact on confidentiality, integrity, and availability of the information system. The Top Threats Analysis methodology is a framework developed by the Cloud Security Alliance (CSA) to help organizations identify, analyze, and mitigate the most critical threats to cloud computing. The methodology consists of six steps: threat identification, threat analysis, technical impact identification, business impact analysis, risk assessment, and risk treatment12.

The technical impact identification step is the third step of the methodology, and it aims to assess how the incident affected the security properties of the information system, namely confidentiality, integrity, and availability. Confidentiality refers to the protection of data from unauthorized access or disclosure. Integrity refers to the protection of data from unauthorized modification or deletion. Availability refers to the protection of data and services from disruption or denial. The technical impact identification step can help organizations to understand the severity and extent of the incident and its consequences on the information system12.

The other options are not within the scope of the technical impact identification step. Option A, determine the impact on the controls that were selected by the organization to respond to identified risks, is not within the scope because it is part of the risk treatment step, which is the sixth and final step of the methodology. Option C, determine the impact on the physical and environmental security of the organization, excluding informational assets, is not within the scope because it is not related to the information system or its security properties. Option D, determine the impact on the financial, operational, compliance, and reputation of the organization, is not within the scope because it is part of the business impact analysis step, which is the fourth step of the methodology. References :=

Top Threats Analysis Methodology - CSA1

Top Threats Analysis Methodology - Cloud Security Alliance

 According to the ISACA Cloud Auditing Knowledge Certificate Study Guide, the final decision to include a material finding in a cloud audit report should be made by the cloud auditor1. A material finding is a significant error or risk in the cloud service that could affect the achievement of the audit objectives or the cloud customer’s business outcomes. The cloud auditor is responsible for identifying, evaluating, and reporting the material findings based on the audit criteria, methodology, and evidence. The cloud auditor should also communicate the material findings to the auditee and other relevant stakeholders, and obtain their feedback and responses.

The other options are not correct. Option A is incorrect, as the auditee’s senior management is not in charge of the audit report, but rather the subject of the audit. The auditee’s senior management should provide their perspective and action plans for the material findings, but they cannot decide whether to include or exclude them from the report. Option B is incorrect, as the organization’s CEO is not involved in the audit process, but rather the ultimate recipient of the audit report. The organization’s CEO should review and act upon the audit report, but they cannot influence the content of the report. Option D is incorrect, as the organization’s CISO is not an independent party, but rather a stakeholder of the audit. The organization’s CISO should support and collaborate with the cloud auditor, but they cannot make the final decision on the material findings. References:

ISACA Cloud Auditing Knowledge Certificate Study Guide, page 19-20.

It is most important for an auditor to be aware that an inventory of assets within a cloud environment is fundamental for the security management program. An inventory of assets is a list of all the hardware, software, data, and services that are owned, used, or managed by an organization in the cloud. An inventory of assets helps the organization to identify, classify, and prioritize its cloud resources and to implement appropriate security controls and policies to protect them. An inventory of assets also helps the organization to comply with relevant regulations, standards, and contracts that may apply to its cloud environment.12

An auditor should be aware of the importance of an inventory of assets in the cloud because it provides a baseline for assessing the security posture and compliance status of the organization’s cloud environment. An auditor can use the inventory of assets to verify that the organization has a clear and accurate understanding of its cloud resources and their characteristics, such as location, ownership, configuration, dependencies, vulnerabilities, and risks. An auditor can also use the inventory of assets to evaluate whether the organization has implemented adequate security measures and processes to protect its cloud resources from threats and incidents. An auditor can also use the inventory of assets to identify any gaps or weaknesses in the organization’s security management program and to provide recommendations for improvement.34

References := Why is IT Asset Inventory Management Critical? - Fresh Security1; Use asset inventory to manage your resources’ security posture2; The importance of asset inventory in cybersecurity3; The Importance Of Asset Inventory In Cyber Security And CMDB - Visore4

 Supply chain agreements between a cloud service provider and cloud customers should, at a minimum, include audits, assessments, and independent verification of compliance certifications with agreement terms. This is because cloud services involve multiple parties in the supply chain, such as cloud providers, sub-providers, brokers, carriers, and auditors. Each party may have different roles and responsibilities in delivering the cloud services and ensuring their quality, security, and compliance. Therefore, it is important for the cloud customers to have visibility and assurance of the performance and compliance of the cloud providers and their sub-providers. Audits, assessments, and independent verification of compliance certifications are methods to evaluate the effectiveness of the controls and processes implemented by the cloud providers and their sub-providers to meet the agreement terms. These methods can help the cloud customers to identify any gaps or risks in the supply chain and to take corrective actions if needed. This is part of the Cloud Control Matrix (CCM) domain COM-04: Audit Assurance & Compliance, which states that "The organization should have a policy and procedures to conduct audits and assessments of cloud services and data to verify compliance with applicable regulatory frameworks, contractual obligations, and industry standards."12 References := CCAK Study Guide, Chapter 3: Cloud Compliance Program, page 551; Practical Guide to Cloud Service Agreements Version 2.02

A detective control is a type of internal control that seeks to uncover problems in a company’s processes once they have occurred1. Examples of detective controls include physical inventory checks, reviews of account reports and reconciliations, as well as assessments of current controls1. Detective controls use platform telemetry to detect misconfigurations, vulnerabilities, and potentially malicious activity in the cloud environment2.

In a Software as a Service (SaaS) service provider, privileged access monitoring is a detective control that can help identify unauthorized or suspicious activities by users who have elevated permissions to access or modify cloud resources, data, or configurations. Privileged access monitoring can involve logging, auditing, alerting, and reporting on the actions performed by privileged users3. This can help detect security incidents, compliance violations, or operational errors in a timely manner and enable appropriate responses.

Data encryption, incident management, and network segmentation are examples of preventive controls, which are designed to prevent problems from occurring in the first place. Data encryption protects the confidentiality and integrity of data by transforming it into an unreadable format that can only be decrypted with a valid key1. Incident management is a process that aims to restore normal service operations as quickly as possible after a disruption or an adverse event4. Network segmentation divides a network into smaller subnetworks that have different access levels and security policies, reducing the attack surface and limiting the impact of a breach1.

References:

Detective controls - SaaS Lens - docs.aws.amazon.com3, section on Privileged access monitoring

Detective controls | Cloud Architecture Center | Google Cloud2, section on Detective controls

Internal control: how do preventive and detective controls work?4, section on SaaS Solutions to Support Internal Control

Detective Control: Definition, Examples, Vs. Preventive Control1, section on What Is a Detective Control?