[Feb-2025] CCAK Dumps Full Questions – Cloud Security Alliance Exam Study Guide [Q118-Q135]

Implementing service level agreements (SLAs) around changes to baseline configurations is the most important way to manage risk from cloud vendors who might accidentally introduce unnecessary risk to an organization by adding new features to their solutions. A service level agreement (SLA) is a contract or a part of a contract that defines the expected level of service, performance, and quality that a cloud vendor will provide to an organization. An SLA can also specify the roles and responsibilities, the communication channels, the escalation procedures, and the penalties or remedies for non-compliance12.
Implementing SLAs around changes to baseline configurations can help an organization to manage the risk from cloud vendors who might add new features to their solutions without proper testing, validation, or notification. Baseline configurations are the standard or reference settings for a system or a network that are used to measure and maintain its security and performance. Changes to baseline configurations can introduce new vulnerabilities, errors, or incompatibilities that can affect the functionality, availability, or security of the system or network34. Therefore, an SLA can help an organization to ensure that the cloud vendor follows a change management process that includes steps such as risk assessment, impact analysis, approval, documentation, notification, testing, and rollback. An SLA can also help an organization to monitor and verify the changes made by the cloud vendor and to report and resolve any issues or incidents that may arise from them.
The other options are not the most effective ways to manage the risk from cloud vendors who might add new features to their solutions. Option A, deploying new features using cloud orchestration tools, is not a good way to manage the risk because cloud orchestration tools are used to automate and coordinate the deployment and management of complex cloud services and resources. Cloud orchestration tools do not address the issue of whether the new features added by the cloud vendor are necessary, secure, or compatible with the organization’s system or network. Option B, performing prior due diligence of the vendor, is not a good way to manage the risk because prior due diligence is a process that involves evaluating and verifying the background, reputation, capabilities, and compliance of a potential cloud vendor before entering into a contract with them. Prior due diligence does not address the issue of how the cloud vendor will handle changes to their solutions after the contract is signed. Option C, establishing responsibility in the vendor contract, is not a good way to manage the risk because establishing responsibility in the vendor contract is a process that involves defining and assigning the roles and obligations of both parties in relation to the cloud service delivery and performance. Establishing responsibility in the vendor contract does not address the issue of how the cloud vendor will communicate and coordinate with the organization about changes to their solutions. References :=
* What is an SLA? Best practices for service-level agreements | CIO1
* Service Level Agreements – Cloud Security Alliance2
* What is Baseline Configuration? – Definition from Techopedia3
* Baseline Configuration – Cloud Security Alliance4
* Change Management – Cloud Security Alliance
* Incident Response – Cloud Security Alliance
* What is Cloud Orchestration? – Definition from Techopedia
* Due Diligence – Cloud Security Alliance
* Contractual Security Requirements – Cloud Security Alliance

The Cloud Controls Matrix (CCM) is a cybersecurity control framework for cloud computing that can be used by cloud customers to build an operational cloud risk management program. The CCM provides guidance on which security controls should be implemented by which actor within the cloud supply chain, and maps the controls to industry-accepted security standards, regulations, and frameworks. The CCM can help cloud customers to assess the security posture of their cloud service providers, document their own responsibilities and requirements, and establish a baseline for cloud security assurance and compliance. Reference := Cloud Controls Matrix (CCM) – CSA1 What is the Cloud Controls Matrix (CCM)? – Cloud Security Alliance2 Certificate of Cloud Auditing Knowledge (CCAK) Study Guide, Chapter 5: Cloud Assurance Frameworks

Role-based access control (RBAC) is a method of restricting access to resources based on the roles of individual users within an organization1 RBAC can help ensure adequate restriction on the number of people who can access the pipeline production environment, as it can limit the permissions and actions that each user can perform on the pipeline resources, such as code, secrets, environments, etc. RBAC can also help enforce the principle of least privilege, which states that users should only have the minimum level of access required to perform their tasks2 The other options are not correct because:
* Option A is not correct because ensuring segregation of duties in the production and development pipelines is not sufficient to ensure adequate restriction on the number of people who can access the pipeline production environment. Segregation of duties is a practice that aims to prevent fraud, errors, or conflicts of interest by dividing responsibilities among different people or teams3 However, segregation of duties does not necessarily limit the number of people who can access the pipeline resources, as it depends on how the roles and permissions are defined and assigned. Segregation of duties is also more relevant for preventing unauthorized changes or deployments to the production environment, rather than restricting access to it4
* Option B is not correct because periodic review of the continuous integration and continuous delivery (CI/CD) pipeline audit logs to identify any access violations is not a proactive measure to ensure adequate restriction on the number of people who can access the pipeline production environment. Audit logs are records of events or activities that occur within a system or process5 Audit logs can help monitor and detect any unauthorized or suspicious access to the pipeline resources, but they cannot prevent or restrict such access in the first place. Audit logs are also dependent on the frequency and quality of the review process, which may not be timely or effective enough to mitigate the risks of access violations6
* Option D is not correct because separation of production and development pipelines is not a direct way
* to ensure adequate restriction on the number of people who can access the pipeline production environment. Separation of production and development pipelines is a practice that aims to isolate and protect the production environment from any potential errors, bugs, or vulnerabilities that may arise from the development process. However, separation of pipelines does not automatically imply restriction of access, as it depends on how the roles and permissions are configured for each pipeline.
Separation of pipelines may also introduce challenges such as synchronization, coordination, and communication among the pipeline teams and stakeholders.
References: 1: Wikipedia. Role-based access control – Wikipedia. [Online]. Available: 1. [Accessed:
14-Apr-2023]. 2: Microsoft Learn. Set pipeline permissions – Azure Pipelines | Microsoft Learn.
[Online]. Available: 1. [Accessed: 14-Apr-2023]. 3: Investopedia. Segregation Of Duties Definition – Investopedia.com Blog. [Online]. Available: . [Accessed: 14-Apr-2023]. 4: Cider Security. Insufficient PBAC (Pipeline-Based Access Controls) – Cider Security Blog. [Online]. Available: . [Accessed: 14-Apr-2023]. 5:
Wikipedia. Audit trail – Wikipedia. [Online]. Available: . [Accessed: 14-Apr-2023]. 6: Microsoft Learn.
Securing Azure Pipelines – Azure Pipelines | Microsoft Learn. [Online]. Available: . [Accessed: 14-Apr-2023].
1: AWS DevOps Blog. How to implement CI/CD with AWS CodePipeline – AWS DevOps Blog | Amazon Web Services Blog. [Online]. Available: . [Accessed: 14-Apr-2023]. : LambdaTest. What Is Parallel Testing?
with Example – LambdaTest Blog. [Online]. Available: . [Accessed: 14-Apr-2023].

The most critical finding of an application security and DevOps audit would be that the application architecture and configurations did not consider security measures. This finding would indicate that the application is vulnerable to various threats and attacks, such as data breaches, unauthorized access, injection, cross-site scripting, denial-of-service, etc. This finding would also imply that the application does not comply with the security standards and best practices for cloud services, such as ISO/IEC 27017:20151, CSA Cloud Controls Matrix2, or NIST SP 800-1463. This finding would require immediate remediation and improvement of the application security posture, as well as the implementation of security controls and tests throughout the DevOps process.
Certifications with global security standards specific to cloud are not reviewed, and the impact of noted findings are not assessed (A) would be a significant finding of an application security and DevOps audit, but not the most critical one. This finding would indicate that the organization is not aware or informed of the security requirements and expectations for cloud services, as well as the gaps or issues that may affect their compliance or performance. This finding would require regular review and analysis of the certifications with global security standards specific to cloud, such as ISO/IEC 270014, CSA STAR Certification, or FedRAMP Authorization, as well as the assessment of the impact of noted findings on the organization’s risk profile and business objectives.
Outsourced cloud service interruption, breach, or loss of stored data occurred at the cloud service provider (B) would be a serious finding of an application security and DevOps audit, but not the most critical one. This finding would indicate that the cloud service provider failed to ensure the availability, confidentiality, and integrity of the cloud services and data that they provide to the organization. This finding would require investigation and resolution of the root cause and impact of the incident, as well as the implementation of preventive and corrective measures to avoid recurrence. This finding would also require review and verification of the contractual terms and conditions between the organization and the cloud service provider, as well as the service level agreements (SLAs) and recovery time objectives (RTOs) for the cloud services.
The organization is not using a unified framework to integrate cloud compliance with regulatory requirements
would be an important finding of an application security and DevOps audit, but not the most critical one.
This finding would indicate that the organization is not following a consistent and systematic approach to manage and monitor its cloud compliance with regulatory requirements, such as GDPR, HIPAA, PCI DSS, etc. This finding would require adoption and implementation of a unified framework to integrate cloud compliance with regulatory requirements, such as COBIT, NIST Cybersecurity Framework, or CIS Controls, as well as the alignment and integration of these frameworks with the DevOps process.

A dot release of the Cloud Controls Matrix (CCM) indicates a technical change (revision, addition, or deletion) of a number of controls that is smaller than 10% compared to the previous full release. A dot release is a minor update to the CCM that reflects the feedback from the cloud security community and the changes in the cloud technology landscape. A dot release does not change the domain structure or the overall scope of the CCM, but rather improves the clarity, accuracy, and relevance of the existing controls. A dot release is denoted by a decimal number after the major version number, such as CCM v4.1 or CCM v4.2. The current version of the CCM is v4.0, which was released in October 20211.
The other options are incorrect because:
* A. a revision of the CCM domain structure: A revision of the CCM domain structure is a major change that affects the organization and categorization of the controls into different domains. A revision of the CCM domain structure requires a full release, not a dot release, and is denoted by an integer number, such as CCM v3 or CCM v42.
* C. the introduction of new control frameworks mapped to previously published CCM controls: The introduction of new control frameworks mapped to previously published CCM controls is an additional feature that enhances the usability and applicability of the CCM. The introduction of new control frameworks mapped to previously published CCM controls does not require a dot release or a full release, but rather an update to the mapping table that shows the relationship between the CCM controls and other industry-accepted security standards, regulations, and frameworks3.
* D. technical change (revision, addition, or deletion) of a number of controls that is greater than 10% compared to the previous full release: A technical change (revision, addition, or deletion) of a number of controls that is greater than 10% compared to the previous full release is a significant change that affects the content and scope of the CCM. A technical change (revision, addition, or deletion) of a number of controls that is greater than 10% compared to the previous full release requires a full release, not a dot release, and is denoted by an integer number, such as CCM v3 or CCM v42.
References:
* Cloud Controls Matrix (CCM) – CSA
* The CSA Cloud Controls Matrix (CCM) V4: Raising the cloud security bar
* Cloud Security Alliance Releases New Cloud Controls Matrix Auditing Guidelines

The cloud auditor should check if there is explicit documented approval from all customers whose data is affected by the transfer of production data to the test environment. This is because production data may contain sensitive or personal information that is subject to privacy and security regulations, such as the General Data Protection Regulation (GDPR) or the Health Insurance Portability and Accountability Act (HIPAA). Therefore, using production data for testing purposes without the consent of the data owners may violate their rights and expose the organization to legal and reputational risks. This is also stated in the Cloud Controls Matrix (CCM) control DSI-04: Production / Non-Production Environments12, which is part of the Data Security & Information Lifecycle Management domain. The CCM is a cybersecurity control framework for cloud computing that can be used by cloud customers to build an operational cloud risk management program.
The other options are not directly related to the question. Option A, approval of the change by the change advisory board, refers to the process of reviewing and authorizing changes to the system or software before they are implemented in the production environment. This is a good practice for ensuring the quality and reliability of the system or software, but it does not address the issue of using production data for testing purposes. Option C, training for the librarian, refers to the process of providing adequate education and awareness to the staff who are responsible for managing and transferring data between different environments. This is a good practice for ensuring the competence and accountability of the staff, but it does not address the issue of obtaining consent from the data owners. Option D, verification that the hardware of the test and production environments are compatible, refers to the process of ensuring that the system or software can run smoothly and consistently on both environments. This is a good practice for ensuring the performance and functionality of the system or software, but it does not address the issue of protecting the privacy and security of the production data. References :=
* Certificate of Cloud Auditing Knowledge (CCAK) Study Guide, Chapter 6: Cloud Security Controls
* Cloud Controls Matrix (CCM) – CSA3
* DSI-04: Production / Non-Production Environments – CSF Tools – Identity Digital1
* DSI: Data Security & Information Lifecycle Management – CSF Tools – Identity Digital

Explanation
When developing a cloud compliance program, the primary reason for a cloud customer to determine how those services will fit within its policies and procedures is to ensure that the cloud services are aligned with the customer’s business objectives, risk appetite, and compliance obligations. Cloud services may have different characteristics, features, and capabilities than traditional on-premises services, and may require different or additional controls to meet the customer’s security and compliance requirements. Therefore, the customer needs to assess how the cloud services will fit within its existing policies and procedures, such as data classification, data protection, access management, incident response, audit, and reporting. The customer also needs to identify any gaps or conflicts between the cloud services and its policies and procedures, and implement appropriate measures to address them. By doing so, the customer can ensure that the cloud services are used in a secure, compliant, and effective manner12.
References:
ISACA, Certificate of Cloud Auditing Knowledge (CCAK) Study Guide, 2021, p. 19-20.
Cloud Compliance Frameworks: What You Need to Know

Explanation
To assist an organization with planning a cloud migration strategy to execution, an auditor should recommend the use of enterprise architecture (EA). EA is a holistic approach to aligning the business and IT objectives, processes, and resources of an organization. EA helps to define the current and future state of the organization, identify the gaps and opportunities, and design the roadmap and governance for the cloud migration. EA also helps to ensure that the cloud migration is consistent with the organization’s vision, mission, values, and strategy, and that it meets the requirements of the stakeholders, customers, and regulators. EA is part of the Cloud Control Matrix (CCM) domain GRC-01: Enterprise Risk Management, which states that “The organization should have a policy and procedures to identify, assess, manage, and monitor risks related to cloud services.”1 References := CCAK Study Guide, Chapter 2: Cloud Governance, page 25

Explanation
The Cloud Octagon Model was developed to support organizations’ risk assessment methodology. Risk assessment is the process of identifying, analyzing, and evaluating the risks associated with a cloud computing environment. The Cloud Octagon Model provides a logical approach to holistically deal with security aspects involved in moving to the cloud by introducing eight dimensions that need to be considered: procurement, IT governance, architecture, development and engineering, service providers, risk processes, data classification, and country. The model aims to reduce risks, improve effectiveness, manageability, and security of cloud solutions12.
References:
Cloud Octagon Model | CSA
Cloud Security Alliance Releases Cloud Octagon Model

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.

During the implementation phase of a cloud assurance program, the focus is on establishing the operational aspects that will ensure the ongoing security and compliance of the cloud environment. This includes developing the monitoring goals and requirements which are essential for setting up the assurance framework. It involves determining what needs to be monitored, how it should be monitored, and the metrics that will be used to measure compliance and performance.
Reference = The information aligns with best practices for cloud migration and assurance programs as outlined in various resources, including the Cloud Assurance Program Guide by Microsoft Cybersecurity1, which discusses the importance of developing and implementing policies for cloud data and system migration, and the Enterprise Guide to Successful Cloud Adoption by New Relic2, which emphasizes the role of observability in cloud migration, including the establishment of monitoring goals.

According to the ISACA CCAK Study Guide, the auditor should report the findings to the management of the organization being audited, as they are the primary stakeholders and decision makers for the cloud service.
The management is responsible for ensuring that the cloud service meets the requirements and expectations of the community, as well as complying with any relevant laws and regulations. The auditor should also communicate the findings to the cloud service provider, as they are the secondary stakeholders and service providers for the cloud service. The cloud service provider should be aware of any issues or gaps identified by the auditor and work with the management to resolve them. The auditor should not report the findings to the public, shareholders, or interested parties, as they are not directly involved in the cloud service or its governance. The auditor should respect the confidentiality and privacy of the community and its data, and only disclose the findings to those who have a legitimate need to know. References :=
* ISACA, Certificate of Cloud Auditing Knowledge (CCAK) Study Guide, 2021, p. 971
* ISACA, Cloud Auditing Knowledge: Preparing for the CCAK Certificate Exam, 2021, p. 36

A cloud service provider (CSP) providing cloud services currently being used by the United States federal government should obtain FedRAMP Authorization to assure compliance to stringent government standards. FedRAMP is a government-wide program that provides a standardized approach to security assessment, authorization, and continuous monitoring for cloud products and services. FedRAMP enables agencies to leverage the security assessments of CSPs that have been approved by FedRAMP, and establishes a baseline set of security controls for cloud computing, based on NIST SP 800-53. FedRAMP also helps CSPs to demonstrate their compliance with relevant laws and regulations, such as FISMA, FIPS, and NIST standards. FedRAMP Authorization can be obtained through two paths: a provisional authorization from the Joint Authorization Board (JAB) or an authorization from an individual agency12.
The other options are incorrect because:
A . CSA STAR Level Certificate: CSA STAR is a program for security assurance in the cloud that encompasses key principles of transparency, rigorous auditing, and harmonization of standards. CSA STAR Level Certificate is one of the certification options offered by CSA STAR, which is based on the ISO/IEC 27001 standard and the CSA Cloud Controls Matrix (CCM). CSA STAR Level Certificate is not specific to the US federal government standards, and does not guarantee compliance with FedRAMP requirements3.
B . Multi-Tier Cloud Security (MTCS) Attestation: MTCS is a cloud security standard developed by the Singapore government to provide greater clarity and transparency on the level of security offered by different CSPs. MTCS defines three levels of security controls for CSPs: Level 1, Level 2, and Level 3, with Level 3 being the most stringent. MTCS Attestation is a voluntary self-disclosure scheme for CSPs to declare their conformance to the MTCS standard. MTCS Attestation is not applicable to the US federal government standards, and does not ensure compliance with FedRAMP requirements4.
C . ISO/IEC 27001:2013 Certification: ISO/IEC 27001 is a standard for information security management systems that specifies the requirements for establishing, implementing, maintaining, and continually improving an information security management system within the context of the organization. ISO/IEC 27001 Certification is an independent verification that an organization conforms to the ISO/IEC 27001 standard. ISO/IEC 27001 Certification is not exclusive to cloud computing or the US federal government standards, and does not cover all aspects of FedRAMP requirements5.
Reference:
Learn What FedRAMP is All About | FedRAMP | FedRAMP.gov
How to Become FedRAMP Authorized | FedRAMP.gov
STAR | CSA
Multi-Tiered Cloud Security Standard (MTCS SS)
ISO – ISO/IEC 27001 – Information security management

Explanation
According to the definition of regression testing, it is a type of software testing that confirms that a recent program or code change has not adversely affected existing features1 It involves re-running functional and non-functional tests to ensure that previously developed and tested software still performs as expected after a change2 If the software does not perform as expected, it is called a regression. Therefore, the most important goal of regression testing is to ensure new releases do not impact previous stable features.
The other options are not correct because:
Option A is not correct because the expected outputs are provided by the new features is not the goal of regression testing, but rather the goal of functional testing or acceptance testing. These types of testing aim to verify that the software meets the specified requirements and satisfies the user needs. Regression testing, on the other hand, focuses on checking that the existing features are not broken by the new features3 Option B is not correct because the system can handle a high number of users is not the goal of regression testing, but rather the goal of performance testing or load testing. These types of testing aim to evaluate the behavior and responsiveness of the software under various workloads and conditions. Regression testing, on the other hand, focuses on checking that the software functionality and quality are not degraded by code changes4 Option C is not correct because the system can be restored after a technical issue is not the goal of regression testing, but rather the goal of recovery testing or disaster recovery testing. These types of testing aim to assess the ability of the software to recover from failures or disasters and resume normal operations. Regression testing, on the other hand, focuses on checking that the software does not introduce new failures or defects due to code changes5 References: 1: Wikipedia. Regression testing – Wikipedia. [Online]. Available: 3. [Accessed: 14-Apr-2023]. 2:
Katalon. What is Regression Testing? Definition, Tools, Examples – Katalon.
[Online]. Available: 4. [Accessed: 14-Apr-2023]. 3: Guru99. What is Functional Testing? Types & Examples – Guru99. [Online]. Available: . [Accessed: 14-Apr-2023]. 4: Guru99. What is Performance Testing? Types & Examples – Guru99. [Online]. Available: . [Accessed: 14-Apr-2023]. 5: Guru99. What is Recovery Testing?
with Example – Guru99. [Online]. Available: . [Accessed: 14-Apr-2023].

The auditor’s next course of action should be to review the contract and DR capability of the cloud service provider. The contract should specify the roles and responsibilities of both parties regarding disaster recovery, as well as the service level agreements (SLAs) and recovery time objectives (RTOs) for the critical application. The DR capability should demonstrate that the cloud service provider has a plan that is aligned with the organization’s requirements and expectations, and that it is tested annually and validated by independent auditors. The auditor should also verify that the organization has a process to monitor and review the cloud service provider’s performance and compliance with the contract and SLAs.
Planning an audit of the provider (B) may not be feasible or necessary, as the auditor may not have access to the provider’s environment or data, and may not have the authority or expertise to conduct such an audit. The auditor should rely on the provider’s audit reports and certifications to assess their compliance with relevant standards and regulations.
Reviewing the security white paper of the provider © may not be sufficient or relevant, as the security white paper may not cover the specific aspects of disaster recovery for the critical application, or may not reflect the current state of the provider’s security controls and practices. The security white paper may also be biased or outdated, as it is produced by the provider themselves.
Reviewing the provider’s audit reports (D) may be helpful, but not enough, as the audit reports may not address the specific requirements and expectations of the organization for disaster recovery, or may not cover the latest changes or incidents that may affect the provider’s DR capability. The audit reports may also have limitations or qualifications that may affect their reliability or validity. Reference := Audit a Disaster Recovery Plan | AlertFind ISACA Introduces New Audit Programs for Business Continuity/Disaster …
How to Maintain and Test a Business Continuity and Disaster Recovery Plan

The cloud service provider is responsible for the patching of the hypervisor layer in all three cloud deployment models (IaaS, PaaS, and SaaS). The hypervisor layer is the software that allows the creation and management of virtual machines on a physical server. The hypervisor layer is part of the cloud infrastructure, which is owned and operated by the cloud service provider. The cloud service provider is responsible for ensuring that the hypervisor layer is secure, reliable, and up to date with the latest patches and updates. The cloud service provider should also monitor and report on the status and performance of the hypervisor layer, as well as any issues or incidents that may affect it.
The cloud service customer is not responsible for the patching of the hypervisor layer, as they do not have access or control over the cloud infrastructure. The cloud service customer only has access and control over the cloud resources and services that they consume from the cloud service provider, such as virtual machines, storage, databases, applications, etc. The cloud service customer is responsible for ensuring that their own cloud resources and services are secure, compliant, and updated with the latest patches and updates.
The patching of the hypervisor layer is not a shared responsibility between the cloud service provider and the cloud service customer, as it is solely under the domain of the cloud service provider. The shared responsibility model in cloud computing refers to the division of security and compliance responsibilities between the cloud service provider and the cloud service customer, depending on the type of cloud deployment model. For example, in IaaS, the cloud service provider is responsible for securing the physical infrastructure, network, and hypervisor layer, while the cloud service customer is responsible for securing their own operating systems, applications, data, etc. In PaaS, the cloud service provider is responsible for securing everything up to the platform layer, while the cloud service customer is responsible for securing their own applications and data. In SaaS, the cloud service provider is responsible for securing everything up to the application layer, while the cloud service customer is responsible for securing their own data and user access.
Patching on hypervisor layer is required, as it is essential for maintaining the security, reliability, and performance of the cloud infrastructure. Patching on hypervisor layer can help prevent vulnerabilities, bugs, errors, or exploits that may compromise or affect the functionality of the virtual machines or other cloud resources and services. Patching on hypervisor layer can also help improve or enhance the features or capabilities of the hypervisor software or hardware. References :=
* Patching process – AWS Prescriptive Guidance
* What is a Hypervisor in Cloud Computing and Its Types? – Simplilearn
* In all three cloud deployment models, (IaaS, PaaS, and … – Exam4Training
* Reference Architecture: App Layering | Citrix Tech Zone
* Hypervisor – GeeksforGeeks