The Official (ISC)2 CCSP CBK Reference

by Leslie Fife, Aaron Kraus, and Bryan Lewis
The Official (ISC)2 CCSP CBK Reference cover

On this page

Highlights

DOMAIN 1 Cloud Concepts, Architecture, and Design

My note: .h1

UNDERSTAND CLOUD COMPUTING CONCEPTS

My note: .h2

Cloud Computing Definitions

My note: .h3

Cloud Computing

My note: .h4

In NIST SP 800-145, cloud computing is defined as “a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources… . that can be rapidly provisioned and released with minimal management effort or service provider interaction.”
Service Models

My note: .h4

Deployment Models

My note: .h4

There are four deployment models: public, private, community, and hybrid clouds.
A public cloud deployment makes resources available for anyone who chooses to create an account and purchase access to the service. A service like Dropbox is available to the public SaaS deployment. Accounts on various cloud service providers such as Amazon Web Services (AWS), Google, and IBM Cloud are also public deployments of services.
A private cloud deployment consists of a set of cloud resources for a single organization (business, non-profit, etc.). The cloud may be located on-premise in the organization’s data center or may be in a single tenant cloud environment provided by a CSP.
A community cloud is most similar to a public cloud. It is a cloud deployment for a related group of companies or individuals such as a consortium of universities or a group of local or state governments. The cloud may be implemented in one of the organizations, with services provided to all members. Or, it can be implemented in an infrastructure like AWS or Google. However, access to the cloud resources is available only to the members of the group.
A hybrid cloud is any combination of these. A company may have a private cloud that accesses public cloud resources for some of its functions. The hybrid cloud allows the organization of cloud resources in whatever way makes the most sense to the organization.
Cloud Computing Roles

My note: .h3

Cloud Service Customer

My note: .h3

The cloud service customer (CSC) is the company or person purchasing the cloud service, or in the case of an internal customer, the employee using the cloud service.
Cloud Service Provider

My note: .h3

The cloud service provider (CSP) is the company or other entity offering cloud services. A CSP may offer SaaS, PaaS, or IaaS services in any combination. For example, major CSPs such as AWS, Microsoft Azure, and Google Cloud offer both PaaS and IaaS services.
This shared responsibility is a continuum, with the customer taking a larger security role in an IaaS service model and the CSP taking a larger role in the security in a SaaS service model.
Cloud Service Partner

My note: .h3

A cloud service partner is a third party offering a variety of cloud-based services (infrastructure, storage and application services, and platform services) using the associated CSP.
Cloud Service Broker

My note: .h3

The broker will package services in a manner that benefits the customer. This may involve the services of multiple CSPs. A broker is a value-add service and can be an easy way for a company to begin a move into the cloud. A broker adds value through aggregation of services from multiple parties, integration of services with a company's existing infrastructure, and customization of services that a CSP cannot or will not make.
Key Cloud Computing Characteristics

My note: .h2

On-Demand Self-Service

My note: .h3

The NIST definition of cloud computing identifies an on-demand service as one “that can be rapidly provisioned and released with minimal management effort or service provider interaction.” This means the user must be able to provision these services simply and easily when they are needed.
This can facilitate the poor practice often labeled as shadow IT. The ease with which a service can be provisioned makes it easy for an individual, team, or department to bypass company policies and procedures that handle the provisioning and control of IT services.
The pricing of these services may fall below corporate spending limits that would otherwise trigger involvement of the vendor management office (VMO) and information security and may simply be placed on a purchase card rather than through an invoice and vendor contract. Without VMO involvement, the corporate master services agreement will not be in effect.
If this behavior is allowed to proliferate, the organization can lose control of its sensitive data and processes.
Broad Network Access

My note: .h3

Cloud services assume the presence of a network.
They are solutions that exist on a network—in the cloud. Without broad and ubiquitous network access, the cloud becomes inaccessible and is no longer useful.
If you are able to access the cloud service and obtain access to your data anywhere in the world, so can others.
The requirement for identification and authentication becomes more important in this public-facing environment. The security of accessing your cloud services over the Internet can be improved in a number of ways including improved passwords, multifactor authentication (MFA), virtual private networks (VPNs), etc.
Multitenancy

My note: .h3

One way to get the improved efficiencies of cloud computing is through the sharing of infrastructure. A server may have more than one company purchasing access to its resources. These resources are shared by the tenants. Like
A multitenancy environment increases the importance of disaster recovery (DR) and business continuity (BC) planning.
Rapid Elasticity and Scalability

My note: .h3

However, there is a cost to maintaining this excess capacity. The cost must be built into the cost model. In this way, all customers share in the cost of the CSP, maintaining some level of excess capacity. In the banking world, a bank must keep cash reserves of a certain percentage so that they can meet the withdrawal needs of their customers. But if every customer wanted all of their money at the same time, the bank would run out of cash on hand. In the same way, if every customer's potential peak usage occurred at the same time, the CSP would run out of resources, and the customers would be constrained (and unhappy).
Resource Pooling

My note: .h3

This resource pooling presents some challenges for the cybersecurity professional. When resources are pooled, it can lead to multitenancy. A competitor or a rival can be sharing the same physical hardware. If the system, especially the hypervisor, is compromised, sensitive data could be exposed. Resource pooling also implies that resources are allocated and deallocated as needed. The inability to ensure data erasure can mean that remnants of sensitive files could exist on storage allocated to another user. This increases the importance of data encryption and key management.
Measured Service

My note: .h3

For a public cloud, it allows each customer to pay for the resources used or consumed. With a measured service, everyone pays their share of the costs.
Building Block Technologies

My note: .h2

Without virtualization, there would be no resource pooling. Advances in networking allow for ubiquitous access. Improvements in storage and databases allow remote virtual storage in a shared resource pool. Orchestration puts all the pieces together. The combination of these technologies allows better resource utilization and improves the cost structure of technology.
Virtualization

My note: .h4

Virtualization allows the sharing of servers. Virtualization is not unique to cloud computing and can be used to share corporate resources among multiple process and services.
Storage

My note: .h4

A variety of storage solutions allow cloud computing to work. Two of these are storage area networks (SANs) and network-attached storage (NAS). These and other advances in storage allow a CSP to offer flexible and scalable storage capabilities.
Shared storage can create security challenges if file fragments remain on a disk after it has been deallocated from one customer and allocated to another. A customer has no way to securely wipe the drives in use, as the customer does not control the physical hardware. However, the use of crypto-shredding can make these fragments unusable if recovered.
Networking

My note: .h4

As all resources in a cloud environment are accessed through the network, a robust, available network is an essential element. The Internet is the network used by public and community clouds, as well as many private clouds.
The use of public networks also creates some security concerns. If access to cloud resources is via a public network, like the Internet, the traffic can be intercepted. If transmitted in the clear, the data can be read. The use of encryption and secure transport keeps the data in motion secure and cloud computing safer.
Databases

My note: .h4

data. By using a database in a cloud environment, the administration of the underlying database becomes the responsibility of the CSP. They become responsible for patching, tuning, and other database administrator services. The exception is IaaS, where the user is responsible for whatever database they install. The other advantage of databases offered through a cloud service is the number of different database types and options that can be used together.
Orchestration

My note: .h4

The major CSPs provide orchestration tools. These include IBM Cloud Orchestrator, Microsoft's OMS Management Suite, Oracle Cloud Management Solutions, and AWS Cloud Formation. Like all such offerings, they vary considerably in the tools provided and the integration with other vendors' cloud offerings.
DESCRIBE CLOUD REFERENCE ARCHITECTURE

My note: .h2

The purpose of a reference architecture (RA) is to allow a wide variety of cloud vendors and services to be interoperable. An RA creates a framework or mapping of cloud computing activities and cloud capabilities to allow the services of different vendors to be mapped and potentially work together more seamlessly.
The NIST RA is intended to be vendor neutral and defines five roles: cloud consumer, cloud provider, cloud auditor, cloud broker, and cloud carrier.
Cloud Computing Activities

My note: .h3

The NIST model includes five roles, with the following types of activities:
Cloud consumer:
Cloud provider:
Cloud auditor:
Cloud broker:
Cloud carrier:
Cloud Service Capabilities

My note: .h3

Application Capability Types

My note: .h4

Application capabilities include the ability to access an application over the network from multiple devices and from multiple locations.
Platform Capability Types

My note: .h4

A platform has the capability of developing and deploying solutions through the cloud. These solutions may be developed with available tools, they may be acquired solutions that are delivered through the cloud, or they may be solutions that are acquired and customized prior to delivery. The user of a platform service may modify the solutions they deploy, particularly the ones they develop and customize. However, the user has no capability to modify the underlying infrastructure.
Infrastructure Capability Types

My note: .h4

An infrastructure customer cannot control the underlying hardware but has control over the operating system, installed tools, solutions installed, and provisioning of infrastructure compute, storage, and network and other computing resources.
Cloud Service Categories

My note: .h2

There are three primary cloud service categories: SaaS, PaaS, and IaaS. In addition, other service categories are sometimes suggested, such as storage as a service (STaaS), database as a service (DBaaS), and even everything as a service (XaaS). However, these can be described in terms of the three basic types and have not caught on in common usage.
If you are an end user, you are likely using a SaaS solution. If you are a developer, you may be offering a SaaS solution you developed in-house or through the use of a PaaS development environment. It is possible that the cloud service you provide is a development environment, so you offer a PaaS service you built on an IaaS service. Some customers work at all three levels. They use an IaaS service to build a development environment to create a SaaS solution.
Software as a Service

My note: .h4

SaaS is the most common cloud service that most people have experience with.
Platform as a Service

My note: .h4

PaaS is the domain of developers. With a PaaS solution, the service provider is responsible for infrastructure, networking, virtualization, compute, storage, and operating systems. Everything built on top of that is the responsibility of the developer and their organization.
Infrastructure as a Service

My note: .h4

IaaS is where we find the system administrators (SysAdmins). In a typical IaaS offering, the IaaS service provider is responsible for the provisioning of the hardware, networking, and storage, as well as any virtualization necessary to create the IaaS environment. The SysAdmin is responsible for everything built on top of that, including the operating system, developer tools, and end-user applications as needed.
Cloud Deployment Models

My note: .h2

There are three cloud deployment models and one hybrid model. The hybrid model is a combination of any two or more other deployment models. Each deployment model has advantages and disadvantages.
Public Cloud

My note: .h4

In a public cloud, anyone with access to the Internet may access the resources provided, usually through a subscription-based service. The resources and application services are provided by third-party service providers, and the systems and data reside on third-party servers.
There are concerns with privacy and security in a public cloud. And, while that may have been the case in the past, public clouds have made great strides in both privacy and security. The responsibility for both—data privacy and security—remains with the data owner (customer). Concerns about reliability can sometimes be handled contractually through the use of an service-level agreement (SLA). However, for many public cloud services, the contractual terms are fixed for both individual or corporate accounts.
Private Cloud

My note: .h4

A private cloud is built in the same manner as a public cloud, architecturally. The difference is in ownership. A private cloud belongs to a single company and contains data and services for use by that company. There is not a subscription service for the general public.
A private cloud is usually more customizable, and the company controls access, security, and privacy. A private cloud is also generally more expensive. There are no other customers to share the infrastructure costs. With no other customers, the cost of providing excess capacity is not shared.
Community Cloud

My note: .h4

A community cloud falls somewhere between public and private clouds. The cloud is built for the needs of multiple organizations, all in the same industry. These common industries might be banks; governments such as a group of states; or resources shared between local, county (or parish), and state governments. Universities often set up consortiums for research, and this can be facilitated through a community cloud. Structured like public and private clouds, the infrastructure may be hosted by one of the community partners or by a third-party. Access is restricted to members of the community and may be subscription based.
Hybrid Cloud

My note: .h4

A hybrid cloud can be a combination of any of the other cloud deployment models but is usually a combination of the private and public cloud deployment models and can be used in ways that enhance security when necessary and allows scalability and flexibility.
In a hybrid model, the disadvantages and benefits of each type of cloud deployment remains for the portion of the cloud using that deployment model. Cloud orchestration can be used to keep this hybrid cloud manageable for the workforce to use.
Cloud Shared Considerations

My note: .h2

Interoperability

My note: .h4

Interoperability creates the ability to communicate with and share data across multiple platforms and between traditional and cloud services provided by different vendors.
Portability

My note: .h4

Portability may refer to data portability or architecture portability. Data portability is focused on the ability to move data between traditional and cloud services or between different cloud services without having to port the data under challenging and lossy methods or significant changes to either service or the loss of metadata.
Reversibility is a measure of the extent your cloud services can be moved from one cloud environment to another.
Reversibility

My note: .h4

Availability

My note: .h4

Availability has two components. The first is one leg of the CIA triad. Within the constraints of the agreed-upon SLA, the purchased services and company or individual data must be made available to the customer by the CSP. If the SLA is not met, the contract will spell out the penalties or recourses available.
The second component of availability is concerned with the elasticity and scalability of the cloud service.
Security

My note: .h4

One issue that is part of various national laws such as the European Union's General Data Protection Regulation is the restriction on cross-border transfers of data. In an environment where the actual hardware could be anywhere, it is an important consideration to know where your data resides. When there are law enforcement issues, location of the data may also be a jurisdictional challenge.
The owner of data remains ultimately responsible for the security of the data, regardless of what cloud or noncloud services are used.
Privacy

My note: .h4

Privacy concerns include access to data both during a contract and at the end of a contract as well as the erasure or destruction of data when requested or as required within the contract. Regulatory and contractual requirements such as HIPAA and PCI are also key concerns. Monitoring and logging of data access and modification, and the location of data storage, are additional privacy concerns.
Resilience is the ability to continue operating under adverse or unexpected conditions.
Resiliency

My note: .h4

Performance

My note: .h4

Performance is measured through an SLA. Performance of a cloud service is generally quite high as major CSPs build redundancy into their systems. The major performance concerns are network availability and bandwidth.
Governance

My note: .h4

Cloud governance uses the same mechanisms as governance of your on-premises IT solutions. This includes policies, procedures, and controls. Controls include encryption, access control lists (ACLs), and identity and access management. As many organizations have cloud services from multiple vendors, a cloud governance framework and application can make the maintenance and automation of cloud governance manageable. This may be another cloud solution.
Maintenance and Versioning

My note: .h4

Maintenance and versioning in a cloud environment have some advantages and disadvantages. Each party is responsible for the maintenance and versioning of their portion of the cloud stack.
What this means in practical terms is that updates and patches in a SaaS or PaaS environment may occur without the knowledge of the customer. If properly tested before being deployed, it will also be unnoticed by the customer.
On the positive side, there will not be the endpoints that exist in every organization that never get updated and have older, insecure versions of potentially unlicensed software. When connecting to the cloud service, the customer will always be using the newest, most secure version of the solution in a SaaS solution.
Service Levels and Service Level Agreements

My note: .h4

Contractually, an SLA specifies the required performance parameters of a solution. This negotiation will impact the price, as more stringent requirements can be more expensive. For example, if you need 24-hour support, this will be less expensive than 4-hour support.
Some CSPs will provide a predefined set of SLAs, and customers choose the level of service they need. The customer can be an individual or an organization. For the customer contracting with a CSP, this is a straightforward approach. The CSP publishes their performance options and the price of each, and the customer selects the one that best suits their needs and resources.
Auditability

My note: .h4

A cloud solution needs to be auditable. This is an independent examination of the cloud services controls, with the expression of an opinion on their function with respect to their purpose. Are the controls properly implemented? Are the controls functioning and achieving their goal? These are the questions of an auditor.
Regulatory

My note: .h4

Proper oversight and auditing of a CSP makes regulatory compliance more manageable. A regulatory environment is one where a principle or rule controls or manages an organization.
One form of regulations are those governmental requirements that have the force of law. The Health Insurance Portability and Accountability Act (HIPAA), Gramm-Leach-Bliley Act (GLBA), Sarbanes-Oxley Act (SOX) in the United States, and GDPR in the European Union are examples of laws that are implemented through regulations and have the force of law.
Another form of regulations is those put in place through contractual requirements. An SLA takes the form of a contractual obligation as do the rules associated with credit and debit cards through the Payment Card Industry Data Security Standard (PCI DSS).
A third form of regulations is found through standards bodies like International Organization for Standardization (ISO) and NIST as well as nongovernmental groups such as the Cloud Security Alliance and the Center for Internet Security. These
Impact of Related Technologies

My note: .h2

Machine Learning

My note: .h4

Machine learning (ML) is a key component of artificial intelligence (AI) and is becoming more widely used in the cloud. Machine learning creates the ability for a solution to learn and improve without the use of additional programming. Many
Artificial Intelligence

My note: .h4

Machine learning is not the only AI technology. The goal of AI is to create a machine that has the capabilities of a human and cannot be distinguished from a human. It is possible that AI could create intelligent agents online that are indistinguishable to human agents. This
Blockchain

My note: .h4

A blockchain is an open distributed ledger of transactions, often financial, between two parties. This transaction is recorded in a permanent and verifiable manner. The records, or blocks, are linked cryptographically and are distributed across a set of computers, owned by a variety of entities.
Blockchain provides a secure way to perform anonymous transactions that also maintain nonrepudiation. The ability to securely store a set of records across multiple servers, perhaps in different CSPs or on-premise, could lead to new and powerful storage approaches. Any data transaction would be committed to the chain and could be verifiable and secure. Blockchain technology pushes the boundaries of cryptographic research in ways that support secure distributed computing.
Internet of Things

My note: .h4

With the growth of the Internet of Things (IoT), a great deal of data is being generated and stored. The cloud is a natural way to store this data. Particularly for large organizations, with IoT devices such as thermostats, cameras, irrigation controllers, and similar devices, the ability to store, aggregate, and mine this data in the cloud from any location with a network connection is beneficial.
Containers

My note: .h4

Virtualization is a core technology in cloud computing. It allows resource pooling, multitenancy, and other important characteristics. Containers are one approach to the virtualization. In a traditional virtualization environment, the hypervisor sits atop the host OS. The VM sits atop the hypervisor. The VM contains the guest OS and all files and applications needed in that VM. A machine can have multiple VMs, each running a different machine.
In containerization, there is no hypervisor and no guest OS. A container runtime sits above the host OS, and then each container uses the container runtime to access needed system resources. The container contains the files and data necessary to run, but no guest OS. The virtualization occurs higher in the stack and is generally smaller and can start up more quickly. It also uses fewer resources by not needing an additional OS in the virtual space. The smaller size of the container image and the low overhead are the primary advantages of containers over traditional virtualization.
Quantum Computing

My note: .h4

Quantum computers use quantum physics to build extremely powerful computers. When these are linked to the cloud, it becomes quantum cloud computing. IBM, AWS, and Azure all provide a quantum computing service to select customers.
A concern for quantum computing is that traditional methods for encryption/decryption could become obsolete as the vast power of the cloud coupled with quantum computing makes the search space more manageable. This would effectively break current cryptographic methods. New quantum methods of encryption would be necessary or methods not susceptible to quantum computing.
UNDERSTAND SECURITY CONCEPTS RELEVANT TO CLOUD COMPUTING

My note: .h2

Cryptography and Key Management

My note: .h3

Access Control

My note: .h3

Administrative access control refers to the policies and procedures a company uses to regulate and monitor access.
Data and Media Sanitization

My note: .h3

Network Security

My note: .h3

Virtualization Security

My note: .h3

Common Threats

My note: .h3

UNDERSTAND DESIGN PRINCIPLES OF SECURE CLOUD COMPUTING

My note: .h2

Cloud Secure Data Lifecycle

My note: .h3

Cloud-Based Disaster Recovery and Business Continuity Planning

My note: .h3

Cost-Benefit Analysis

My note: .h3

Functional Security Requirements

My note: .h3

Security Considerations for Different Cloud Categories

My note: .h3

EVALUATE CLOUD SERVICE PROVIDERS

My note: .h2

Verification against Criteria

My note: .h3

System/Subsystem Product Certifications

My note: .h3

Summary

My note: .h3

In order to discuss the cloud, each individual must be familiar with the terminology surrounding this technology. This understanding includes characteristics of cloud computing, as well as the service models and deployment models of cloud computing. It also includes the role of the CSP in cloud computing and the shared security model that exists between the CSP and the customer. Finally, the technologies that make cloud computing possible are discussed in this chapter alongside the emerging technologies that will support and transform cloud computing in the future. Understanding this chapter will make it easier to access the discussion in each of the following domains.
DOMAIN 2 Cloud Data Security

My note: .h1

DESCRIBE CLOUD DATA CONCEPTS

My note: .h2

Cloud Data Lifecycle Phases
Data Dispersion

My note: .h3

DESIGN AND IMPLEMENT CLOUD DATA STORAGE ARCHITECTURES

My note: .h2

Storage Types

My note: .h3

Threats to Storage Types

My note: .h3

DESIGN AND APPLY DATA SECURITY TECHNOLOGIES AND STRATEGIES

My note: .h2

Encryption and Key Management

My note: .h3

Hashing

My note: .h3

Masking

My note: .h3

Tokenization

My note: .h3

Data Loss Prevention

My note: .h3

Data Obfuscation

My note: .h3

Deletion or nullification simply replaces the original data with null values.
Data De-identification

My note: .h3

IMPLEMENT DATA DISCOVERY

My note: .h2

A lake is an unstructured data storage mechanism with data often stored in files or blobs, while a warehouse is structured storage in which data has been normalized to fit a defined data model.
Structured Data

My note: .h3

Unstructured Data

My note: .h3

IMPLEMENT DATA CLASSIFICATION

My note: .h2

Mapping

My note: .h3

Labeling

My note: .h3

Sensitive Data

My note: .h3

DESIGN AND IMPLEMENT INFORMATION RIGHTS MANAGEMENT

My note: .h2

Objectives

My note: .h3

Appropriate Tools

My note: .h3

PLAN AND IMPLEMENT DATA RETENTION, DELETION, AND ARCHIVING POLICIES

My note: .h2

Data Retention Policies
Data Deletion Procedures and Mechanisms

My note: .h3

Data Archiving Procedures and Mechanisms

My note: .h3

Legal Hold

My note: .h3

DESIGN AND IMPLEMENT AUDITABILITY, TRACEABILITY, AND ACCOUNTABILITY OF DATA EVENTS

My note: .h2

Definition of Event Sources and Requirement of Identity Attribution

My note: .h3

Logging, Storage, and Analysis of Data Events

My note: .h3

Chain of Custody and Nonrepudiation

My note: .h3

SUMMARY

My note: .h2

Cloud services offer many benefits for accessing, managing, and handling the data that are crucial to modern business operations, but they are not free from risk. The cloud data lifecycle provides a convenient framework for identifying the types of activities, risks, and appropriate security controls required to ensure data remains secure. This, coupled with an understanding of the storage architectures available in different cloud service models, allows a CCSP to design and apply appropriate safeguards such as data discovery, encryption, and tokenization, as well as countermeasures like DLP. Proper cloud data security requires organizations to know what kind of data they handle and where it is stored, and deploy adequate policies, procedures, and technical controls to ensure the business benefits of cloud environments are not offset by increased information-security risks.
DOMAIN 3 Cloud Platform and Infrastructure Security

My note: .h1

COMPREHEND CLOUD INFRASTRUCTURE COMPONENTS

My note: .h2

Physical Environment

My note: .h3

Network and Communications

My note: .h3

Compute

My note: .h3

Virtualization

My note: .h3

Storage

My note: .h3

Management Plane

My note: .h3

DESIGN A SECURE DATA CENTER

My note: .h2

Logical Design

My note: .h3

Physical Design

My note: .h3

Environmental Design

My note: .h3

ANALYZE RISKS ASSOCIATED WITH CLOUD INFRASTRUCTURE

My note: .h2

Risk Assessment and Analysis

My note: .h3

Cloud Vulnerabilities, Threats, and Attacks

My note: .h3

Virtualization Risks

My note: .h3

Countermeasure Strategies

My note: .h3

DESIGN AND PLAN SECURITY CONTROLS

My note: .h2

Physical and Environmental Protection

My note: .h3

System and Communication Protection

My note: .h3

Virtualization Systems Protection

My note: .h3

Identification, Authentication, and Authorization in Cloud Infrastructure

My note: .h3

Audit Mechanisms

My note: .h3

PLAN DISASTER RECOVERY AND BUSINESS CONTINUITY

My note: .h2

Risks Related to the Cloud Environment

My note: .h3

Business Requirements

My note: .h3

Business Continuity/Disaster Recovery Strategy

My note: .h3

Creation, Implementation, and Testing of Plan

My note: .h3

SUMMARY

My note: .h2

Moving to the cloud is a business decision. Moving to the cloud changes capital expense to operational expense and can add high availability and resiliency at a price that is attractive to businesses of all types. It also provides capabilities not available to all businesses. To achieve these benefits, a customer must have an understanding of the key infrastructure pieces of a cloud environment. The customer must also understand the shared security responsibility between the CSP and the customer. Finally, a customer must understand how to properly configure and use the cloud resources they purchase to ensure appropriate controls are in place to secure the process and data.
DOMAIN 4 Cloud Application Security

My note: .h1

ADVOCATE TRAINING AND AWARENESS FOR APPLICATION SECURITY

My note: .h2

Cloud Development Basics

My note: .h3

Common Pitfalls

My note: .h3

Common Cloud Vulnerabilities

My note: .h3

DESCRIBE THE SECURE SOFTWARE DEVELOPMENT LIFECYCLE PROCESS

My note: .h2

NIST Secure Software Development Framework

My note: .h3

OWASP Software Assurance Security Model

My note: .h3

Business Requirements

My note: .h3

Phases and Methodologies

My note: .h3

APPLY THE SECURE SOFTWARE DEVELOPMENT LIFECYCLE

My note: .h2

Avoid Common Vulnerabilities During Development
Cloud-Specific Risks

My note: .h3

Quality Assurance

My note: .h3

Threat Modeling

My note: .h3

Software Configuration Management and Versioning

My note: .h3

APPLY CLOUD SOFTWARE ASSURANCE AND VALIDATION

My note: .h2

Functional Testing

My note: .h3

Security Testing Methodologies

My note: .h3

USE VERIFIED SECURE SOFTWARE

My note: .h2

Approved Application Programming Interfaces

My note: .h3

Supply-Chain Management

My note: .h3

Third-Party Software Management

My note: .h3

Validated Open-Source Software

My note: .h3

COMPREHEND THE SPECIFICS OF CLOUD APPLICATION ARCHITECTURE

My note: .h2

Supplemental Security Components

My note: .h3

Cryptography

My note: .h3

Sandboxing

My note: .h3

Application Virtualization and Orchestration

My note: .h3

DESIGN APPROPRIATE IDENTITY AND ACCESS MANAGEMENT SOLUTIONS

My note: .h2

Federated Identity

My note: .h3

Identity Providers

My note: .h3

Single Sign-On

My note: .h3

Multifactor Authentication

My note: .h3

Cloud Access Security Broker

My note: .h3

SUMMARY

My note: .h3

Cloud application security requires many things working together. The first step is to choose to develop secure applications by policy. All other decisions flow from this one decision. Once this decision is made, an SSDLC must be adopted with training on secure software development and the tools and processes used in this approach to application development. An SSDLC must be implemented, with development leading to assurance and validation activities to ensure that developed solutions are secure. The next step is to develop mechanisms to ensure verified software is distributed securely and that modified software can be detected to prevent the insertion of malicious code in your securely developed software solutions. Finally, the software solutions must be deployed using the architected secure solution. This approach implements secure API gateways, XML firewalls, web application firewalls, DAM, IAM, CASB, and other tools as necessary. These tools monitor the applications in use, with the ability to respond to potentially malicious behavior and potentially prevent malicious use.
DOMAIN 5 Cloud Security Operations

My note: .h1

IMPLEMENT AND BUILD PHYSICAL AND LOGICAL INFRASTRUCTURE FOR CLOUD ENVIRONMENT

My note: .h2

Hardware-Specific Security Configuration Requirements

My note: .h3

Installation and Configuration of Virtualization Management Tools

My note: .h3

Virtual Hardware–Specific Security Configuration Requirements

My note: .h3

Installation of Guest Operating System Virtualization Toolsets

My note: .h3

OPERATE PHYSICAL AND LOGICAL INFRASTRUCTURE FOR CLOUD ENVIRONMENT

My note: .h2

Configure Access Control for Local and Remote Access

My note: .h3

Secure Network Configuration

My note: .h3

Operating System Hardening through the Application of Baselines

My note: .h3

Availability of Stand-Alone Hosts

My note: .h3

Availability of Clustered Hosts

My note: .h3

Availability of Guest Operating Systems

My note: .h3

MANAGE PHYSICAL AND LOGICAL INFRASTRUCTURE FOR CLOUD ENVIRONMENT

My note: .h2

Access Controls for Remote Access

My note: .h3

Operating System Baseline Compliance Monitoring and Remediation

My note: .h3

Patch Management

My note: .h3

Performance and Capacity Monitoring

My note: .h3

Hardware Monitoring

My note: .h3

Configuration of Host and Guest Operating System Backup and Restore Functions

My note: .h3

Network Security Controls

My note: .h3

Management Plane

My note: .h3

IMPLEMENT OPERATIONAL CONTROLS AND STANDARDS

My note: .h2

Change Management

My note: .h3

Continuity Management

My note: .h3

Information Security Management

My note: .h3

Continual Service Improvement Management

My note: .h3

Incident Management

My note: .h3

Problem Management

My note: .h3

Release Management

My note: .h3

Deployment Management

My note: .h3

Configuration Management

My note: .h3

Service Level Management

My note: .h3

Availability Management

My note: .h3

Capacity Management

My note: .h3

SUPPORT DIGITAL FORENSICS

My note: .h2

Forensic Data Collection Methodologies

My note: .h3

Evidence Management

My note: .h3

Collect, Acquire, and Preserve Digital Evidence

My note: .h3

MANAGE COMMUNICATION WITH RELEVANT PARTIES

My note: .h2

Vendors

My note: .h3

Customers

My note: .h3

Shared Responsibility Model

My note: .h3

Partners

My note: .h3

Regulators

My note: .h3

Other Stakeholders

My note: .h3

MANAGE SECURITY OPERATIONS

My note: .h2

Security Operations Center

My note: .h3

Monitoring of Security Controls

My note: .h3

Log Capture and Analysis

My note: .h3

Incident Management

My note: .h3

Cloud-Specific Incident Management

My note: .h3

SUMMARY

My note: .h3

Cloud security operations, like all other security practices, must be anchored by two key principles: operations must be driven by the organization's business objectives or mission and must preserve the confidentiality, integrity, and availability of data and systems in the cloud. Operations is a far-reaching topic covering the selection, implementation, and monitoring of physical and logical infrastructure, as well as security controls designed to address the risks posed in cloud computing.
There are a variety of standards that can assist the CCSP in implementing or managing security controls for cloud environments. These cover major objectives such as access control, securing network activity, designing operational control programs, and handling communications. Choosing the correct standard will be driven by each organization's location, industry, and possibly costs associated with the various standards. All programs implemented should have feedback mechanisms designed to continuously improve security as risks evolve.
Also key is an understanding of the shared responsibility model. CSPs will perform the majority of work related to physical infrastructure, though cloud consumers may need physical security for infrastructure that connects them to cloud computing. Logical infrastructure is a more equally shared responsibility: in non-SaaS models, the CSP runs the underlying infrastructure, but consumers have key responsibilities in securing the logical infrastructure in their virtual slice of the cloud.
DOMAIN 6 Legal, Risk, and Compliance

My note: .h1

ARTICULATING LEGAL REQUIREMENTS AND UNIQUE RISKS WITHIN THE CLOUD ENVIRONMENT

My note: .h2

Conflicting International Legislation

My note: .h3

Evaluation of Legal Risks Specific to Cloud Computing

My note: .h3

Legal Frameworks and Guidelines That Affect Cloud Computing

My note: .h3

Forensics and eDiscovery in the Cloud

My note: .h3

UNDERSTANDING PRIVACY ISSUES

My note: .h2

Difference between Contractual and Regulated Private Data

My note: .h3

Country-Specific Legislation Related to Private Data

My note: .h3

Jurisdictional Differences in Data Privacy

My note: .h3

Standard Privacy Requirements

My note: .h3

UNDERSTANDING AUDIT PROCESS, METHODOLOGIES, AND REQUIRED ADAPTATIONS FOR A CLOUD ENVIRONMENT

My note: .h2

Internal and External Audit Controls

My note: .h3

Impact of Audit Requirements

My note: .h3

Identity Assurance Challenges of Virtualization and Cloud

My note: .h3

Types of Audit Reports

My note: .h3

Restrictions of Audit Scope Statements

My note: .h3

Gap Analysis

My note: .h3

Audit Planning

My note: .h3

Internal Information Security Management Systems

My note: .h3

Internal Information Security Controls System
Organizational Policies

My note: .h3

Identification and Involvement of Relevant Stakeholders

My note: .h3

Specialized Compliance Requirements for Highly Regulated Industries

My note: .h3

Impact of Distributed Information Technology Models

My note: .h3

UNDERSTAND IMPLICATIONS OF CLOUD TO ENTERPRISE RISK MANAGEMENT

My note: .h2

Assess Providers Risk Management Programs

My note: .h3

Differences Between Data Owner/Controller vs. Data Custodian/Processor

My note: .h3

Regulatory Transparency Requirements

My note: .h3

Risk Treatment

My note: .h3

Risk Frameworks

My note: .h3

Metrics for Risk Management

My note: .h3

Assessment of Risk Environment

My note: .h3

UNDERSTANDING OUTSOURCING AND CLOUD CONTRACT DESIGN

My note: .h2

Business Requirements

My note: .h3

Vendor Management

My note: .h3

Contract Management

My note: .h3

Supply Chain Management

My note: .h3

SUMMARY

My note: .h3

A cloud security professional must be constantly aware of the legal and compliance issues in migrating and maintaining systems in the cloud. Understanding the legal requirements, privacy issues, audit challenges, and how these relate to risk and contracts with cloud providers is a must for any company taking advantage of cloud services. A cloud security professional must also be well versed in the frameworks provided by professional organizations such as ENISA, NIST, ISO, and the CSA. All information security is essentially a business risk, and understanding and mitigating the risks faced by a company is critical to any business strategy. Any cloud security professional should understand the role that IT plays in this larger picture and have the communication and people skills to involve the appropriate business, legal, and risk decision-makers within a company.

366 highlights, exported from my Kindle via Readwise.

Subscribe to Ishan Girdhar newsletter and stay updated.

Don't miss anything. Get all the latest posts delivered straight to your inbox. It's free!
Great! Check your inbox and click the link to confirm your subscription.
Error! Please enter a valid email address!