CCSP

Certified Cloud Security

Professional
Kelly Handerhan, Instructor
 WELCOME TO CCSP

CCSP (Certified Cloud Security Professional)

Kelly Handerhan, Instructor

2
Domain 0
COURSE INTRODUCTION AND EXAM SPECIFICS
THE 6 DOMAINS OF CCSP
CISSP Course Syllabus:
Domain 0: Introduction and Exam Specifics
Domain 1: Architectural Concepts and Design Requirements
Domain 2: Cloud Data Security
Domain 3: Cloud Platform and Infrastructure
Domain 4: Cloud Application Security
Domain5: Operations
Domain 6: Legal and Compliance

4
EXAM REQUIREMENTS
EXAM SPECIFICS
Domain 1
ARCHITECTURAL CONCEPTS AND DESIGN
REQUIREMENTS
DOMAIN 1: ARCHITECTURAL CONCEPTS AND
DESIGN REQUIREMENTS INTRODUCTION

Why the Cloud? Definitions and Roles

Cloud Service Categories (SaaS, Paas, Iaas)
Deployment Models (Public, Private, Hybrid)
Key Principles of Enterprise Architecture
Network Security and Perimeter
Identity and Access Management
Media Sanitization
Virtualization Security
Threats
Business Continuity
CLOUD COMPUTING NIST SP 800-145
Cloud computing is a model for enabling ubiquitous,
convenient on-demand network access to a shared pool of
configurable computing resources (e.g., networks, server,
storage, applications, and services) that can be rapidly
provisioned and released with minimal management effort
or service provider interaction.
MANAGED SERVICE PROVIDERS
A managed service provider (MSP) is a company that remotely
manages a customer's IT infrastructure and/or end-user
systems, typically on a proactive basis and under a subscription
model.
Client maintains control over the technology and operating
procedures
Smaller companies may not have budget to support Full-time IT
Larger companies may supplement their existing staff
Offers a predictable monthly cost for IT services
CLOUD COMPUTING DEFINITIONS
Anything as a Service: Services provided over the internet as opposed to being
provided locally
Business Continuity: The capability of the organization to continue delivery of
products or services at acceptable predefined levels following a disruptive incident
Cloud Applications: a software application never installed on a local application,
but is accessed over the internet
CAMP (Cloud Application Management for Platforms) Providing service of
management applications including packaging and deployment across public and
private cloud computing
Cloud Backup: Allows backup to a remote cloud-based server
Cloud Migration: The process of transitioning all or part of a companys data or
infrastructure to the cloud
Cloud Portability: The ability to move applications and their data between one
cloud provider and another or from public/private cloud
 CLOUD COMPUTING DEFINITIONS CONTINUED
Cloud Provisioning: The deployment of a companys cloud computing strategy.
Provisioning entails developing the processes for interfacing with the clouds
applications and services as well as auditing and monitoring who accesses and
utilizes the resources.
Desktop as a Service: An implementation of virtual desktop infrastructure (VDI).
Often delivered with the applications needed for use on the virtual desktop
Infrastructure as a Service: Computer infrastructure such as servers, virtualization
and storage
Platform as a Service: Deploying onto the cloud infrastructure customer created
or acquired applications that are created programming libraries, languages,
services and tools supported by the provider.
Software as a Service: A software delivery method that provides access to
software and its functions remotely as a web-based service
Vertical Cloud Computing: Describes the use of cloud computing and services for
a particular vertical (Specific industry or specific-use) application
CLOUD COMPUTING DEFINITIONS CONTINUED

Public Cloud: Cloud storage where the enterprise is

separated from the service provider and the data is stored
and accessed across the internet
Private Cloud: Cloud storage where the data/storage
resources reside within the enterprises datacenter
CLOUD COMPUTING ROLES
Cloud Customer: Individual or entity that utilizes or subscribes to
cloud-based services or resources
Cloud Provider: The company that provides the cloud-based platform
or services
Cloud Backup Service provider: Third-party entity that manages and
provides operational services for cloud-based backups
Cloud Services Broker: A third-party entity that looks to extend or
enhance value to multiple customers of cloud-based services through
relationships with multiple cloud service providers. It acts as a liaison
between customers and providers ideally selecting the best provider for
each customer. The CSB acts as a middleman to broker the best deal
and customize services
Cloud Service Auditor: Third-party organization that verifies attainment
of SLAs
CLOUD COMPUTING ROLES CONTINUED
Cloud Administrator: Responsible for implementation, monitoring and
maintenance of the cloud within the organization or on behalf of an
organization.
Cloud Application Architect: Responsible for adapting, porting or
deploying applications to a target cloud environment
Cloud Data Architect: makes sure that storage and mechanisms within
the clouds meet and conform to the relevant SLAs.
Cloud Architect: will determine when and how a private cloud meets
the policies and needs of the organization
Cloud Service Manager: Typically responsible for policy design,
business agreements, pricing models and some elements of the SLA.
The role works with cloud management and customers to reach
agreement.
 WHY THE CLOUD?
Scalability
Elasticity
Cost-Savings
Reduced Infrastructure
Less Overhead
Pay as you go
CLOUD SERVICE CATEGORIES
Iaas
Paas
Saas
IaaS
Infrastructure as a Service
Per NIST SP 800-145 the capability provided is to
provision processing, storage, networks and other
fundamental computing resources where the consumer is
able to deploy and run software including applications and
operating systems. The consumer doesnt control the
infrastructure, but does control the OS, storage, deployed
apps and configuration settings.
IaaS OFFERS:
Usage metered and priced on the basis of units consumed
Upwards or Downwards scalability as needed
Reduced TCO: No need to buy any assets, as day-to-day
efforts are provided within the cloud. Reduced cost of
maintenance and support, and no loss of asset value
Reduced energy and cooling costs along with green IT
environment
Reduced in-house IT staff
PaaS
Platform as a Service: provides the customer the capability
to deploy onto the cloud infrastructure consumer-created or
acquired application created using programming
languages, libraries, services and tools supported by the
provider.
PaaS OFFERS:
Support for multiple languages and frameworks allowing
developers to code in whichever programming language they
prefer
Multiple hosting environments: the ability to offer a wide variety
and choice for the underlying hosting environments
Flexibility: Focus on open standards and allowing relevant
plugins to be quickly introduced to the platform. The goal is to
reduce lock-in that comes with proprietary source code
Automatic scalability: The application to seamlessly scale up
and down as required by the platform.
SaaS
Software as a Services provides the consumer the ability to use
the providers applications running on a cloud infrastructure.
The applications are accessible from various client devices
through an interface like a web browser or a program interface
Can be delivered either as
Hosted Application Management (AM): The provider hosts
commercially available software for customers and
delivers it over the web
Software on Demand: The cloud provider gives customers
network-based access to a single copy of an application
created specifically for SaaS distribution
SaaS OFFERS
Users can access their applications and data from anywhere
anytime
Reduced TCOreduced the need for advanced hardware.
Redundancy and storage are provided
Rather than purchasing licenses, software is leased
Pay-per-use
Elasticity
Updates and Patch management is the responsibility of the
provider
Standardizationall users have the same version of software
CLOUD DEPLOYMENT MODELS
Public
Private
Hybrid
Community
MULTI-TENANCY
Mode of operation of software where multiple independent instances share
the same environment
Physical environment is generally shared
Segmentation: Separating tenant resources/data/applications, etc.
Isolation: Logical isolation is often provided through virtualization
Governance: Propose a data governance framework to ensure the
privacy, availability, integrity and overall security of data in different
cloud models
Service Levels: Document minimum expected performance
Chargeback and metering refers to the ability of an IT organization
to track and measure the IT expenses per business unit and charge
them back accordingly.
SERVICE LEVEL AGREEMENTS
Availability (e.g. 99.99% during work days, 99.9% for nights/weekends)
Performance (e.g. maximum response times)
Security / privacy of the data (e.g. encrypting all stored and transmitted data)
Disaster Recovery expectations (e.g. worse case recovery commitment)
Location of the data (e.g. consistent with local legislation)
Access to the data (e.g. data retrievable from provider in readable format)
Portability of the data (e.g. ability to move data to a different provider)
Process to identify problems and resolution expectations (e.g. call center)
Change Management process (e.g. changes updates or new services)
Dispute mediation process (e.g. escalation process, consequences)
Exit Strategy with expectations on the provider to ensure smooth transition
PUBLIC CLOUD BENEFITS
Easy and inexpensivehardware, application and
bandwidth are the responsibility of the provider
Easy to provision resources
Scalability
Pay as you go
PRIVATE CLOUD MODEL
Provisioned for exclusive use by a single organization
comprising multiple business units
It may be owned managed and operated by the organization, a
third party, or a combination
May be on or off premises
Provides much greater control over date, underlying systems and
applications
Greater control over security
Assurance over data location, removal of multiple jurisdiction
legal and compliance requirements
HYBRID CLOUD MODEL
The hybrid is a composition of two or more distinct cloud
infrastructures (private, community, or public)
Provides organizations with the ability to retain control of their IT
environments, but gives them the convenience of using public
cloud service for non-mission-critical efforts
Utilized if there is a need to retain ownership and oversight of
critical tasks and processes related to technology
Re-use previous investments in technology within the
organization
Control the most critical business components/systems
Cloud bursting allows for public cloud resources to be utilitzed
when private cloud workload has reached capacity
COMMUNITY CLOUD MODEL
Provisioned for exclusive use by a specific community of
consumers from organizations that have shared objectives
and requirements
May be operated by one of more of the organizations in the
community or a third party
Community clouds should give the benefits of a public
cloud while providing heightened privacy security and
regulatory compliance.
 KEY PRINCIPLES OF AN ENTERPRISE
ARCHITECTURE
Define protections that enable trust in the cloud
Develop cross-platform capabilities and patterns for proprietary and open source
providers
Facilitate trusted and efficient access, administration and resiliency to the customer
Provide direction to secure information that is protected by regulations.
Facilitate proper and efficient identification, authentication, authorization,
administration and auditability.
Centralize security policy maintenance operation, and oversight functions.
Access to information must be secure yet still easy to obtain
Delegate or federate access control where appropriate
Must be easy to adopt and consume, supporting the design of security patterns
The architecture must be elastic, flexible and resilient, supporting multi-tenant, multi-
landlord platforms
Architecture must address and support multiple levels of protection, including
network, operating system, and application security needs
CRYPTOGRAPHY IN THE CLOUD
Data in Motion
Cloud architect is usually responsible for reviewing how data in transit will
be protected
SSL/TLS create and encrypted tunnel
IP Sec tunnel mode is also a good solution
Data at rest
Though data is stored in the cloud best practices dictate key management
be handled by the client
RKMS (Remote Key Management Service): Customer owns KMS on
premise but it is managed remotely by the service provider allowing
customer to control the confidentiality while the provider provides
support remotely
Client Side Key Management: Similar to RKMS the client side
approach puts the customer in control of encryption/decryption keys.
KMS resides on customers premises.
IDENTITY AND ACCESS MANAGEMENT AND
ACCESS CONTROL
Includes the people, processes and systems that are used
to manage access to enterprise resources. This ensures:
Identity of an entity is verified
Correct level of access is granted based on asset,
services and protected resources being accessed
Multifactor Authentication is preferred
PHASES OF IAM
Provisioning and de-provisioning
Centralized directory services
Privileged user management
Authentication and access management
PROVISIONING AND DE-PROVISIONING
The goal of provisioning is to standardize, streamline, and
create an efficient account creation process, while creating
a consistent, measurable, traceable and auditable
framework for providing access to end users.
De-Provisioning is the process whereby a user account is
disabled when the user no longer requires access to the
cloud-based services and resources. Includes users
leaving the organization, as well as changing roles or
functions or departments
CENTRALIZED DIRECTORY SERVICES
Most common protocol is LDAP, which stores, processes
and facilitates a structured repository of information stored,
coupled with unique identifiers and locations
LDAP Is the communications protocol used to interact with
Active Director
PRIVILEGED USER MANAGEMENT
Focuses on process and ongoing requirements to manage
the lifecycle of user accounts with the highest privileges
These accounts carry the highest risk and impact
Should include the ability to: track usage, authentication
successes and failures, authorization times/dates, log
successful and failed events, enforce password
management and contain sufficient levels of auditing and
reporting
AUTHORIZATION AND ACCESS MANAGEMENT
Regulates what a subject can do to an object
Users require authorization and access management to
access required/appropriate resources
Should be functional, operational and trusted
Should be based on sound security principles such as
separation of duties, privilege management,
password management, etc.
DATA AND MEDIA SANITIZATION
When leaving or migrating from a cloud provider,
considerations must be made for export/import of data in
standards-based formats
Vendor lock-in describes situation where proprietary
formats, technology, etc. make it more difficult to move data
out of the cloud or from on provider or another
How is media sanitized after removal?
Degaussing/physical destruction is rarely an option.
Overwriting is frequently used.
VIRTUALIZATION SECURITY
Virtualization allows logical isolation on multi-tenant
servers
May also allow attackers to target relevant components and
functions to gain unauthorized access to
data/systems/resources]f
Relies upon the security of the Hypervisor
HYPERVISOR
Allows multiple OS to share a single hardware host, with
the appearance of each host having exclusive use of
resources
Type I Hypervisor running directly on the hardware with VM
resources provided by the hypervisor. Also referred to as
bare metal. VMware ESXI, Citrix XenServer. Hardware
based
Type II Hypervisor runs on a host OS to provide
virtualization services. VMware workstation, and MS
VirtualPC. Software-based.
HYPERVISOR SECURITY
Type I hypervisors significantly reduce the attack surface.
Hypervisor vendors has control over relevant software that
comprises and forms the hypervisor package, reducing the
likelihood of malicious code being introduced at the
hypervisor foundation
Type II hypervisors have greater vulnerability since they are
OS based. Numerous vulnerabilities exist within various
OS opening up additional opportunities.
COMMON THREATS
Notorious 9
Data Breaches: Disclosure
Data Loss: Loss of integrity or destruction
Account of Service Hijacking: Attacker sniffing or MITM
Insecure Interfaces/APIs: provided by vendors to access their networks
DoS or DDos
Malicious insiders
Abuse of cloud services: Inherent weakness of any internet service
Insufficient Due Diligence/Due Care
Due diligence investigating and understanding risks
Due care: Developing policies and procedures to address risks
Shared Technology Vulnerabilities: multiple tenants brings in risks
SECURITY FOR DIFFERENT CLOUD CATEGORIES
IaaS requires focus and understanding of the layers of the architecture
from architecture to virtualization components. Concerns include VM
Attacks, Virtual Switches/Network, VM Based Rootkits/malicious
hypervisor, single point of access
PaaS requires addressing 4 main issues
System/Resource isolation
User-level permissions
User Access Management
Protection against malware
SaaS Involves 3 main areas
Data Segregation
Data Access and Policies
Web Application Security
BUSINESS CONTINUITY AND DISASTER
RECOVER PLANNING
Continuity Management is the process in which risks and
threats to the ongoing availability of services, business
functions and the organization are actively reviewed and
managed at set intervals.
Disaster recovery focuses on restoration of most critical
business functions in the event of large impact events
Must address C-I-A triad
RESTORATION PLAN
Due Diligence requires review of plans of the Cloud Service
Provider and SLAs in relation to:
RPO
RTO
Compensation for loss
Definitions of Criticality of specific services
Points of contact and escalation
COST-BENEFIT ANALYSIS
The key driver for the adoption of cloud computing
Resource pooling
Time and efficiencies
No depreciation of resources
Savings of utilities costs
Software Licensing and maintenance costs
Thin Clients
Pay per usage
STANDARDS-BASED APPROACHES
Few standards exist exclusively for cloud computing
ISO 27001 looks to certify that the ISMS can address relevant risks and
elements that is appropriate based on risks
ISO 27002 is the framework for best practice
SOC I, II, III Service Organization Control defines a comprehensive approach
to auditing and assesses the providers controls and their effectiveness
NIST 800-53: Goal is ensure that appropriate security requirements and
security controls are applied to all US Federal government information and
information systems
Common Criteria
FIPS 140 addresses uses of encryption and cryptography
PCI-DSS, HIPPA and other regulations
DOMAIN 1: ARCHITECTURAL CONCEPTS AND
DESIGN REQUIREMENTS
Introduction
Why the Cloud? Definitions and Roles
Cloud Service Categories (SaaS, Paas, Iaas)
Deployment Models (Public, Private, Hybrid)
Key Principles of Enterprise Architecture
Network Security and Perimeter
Identity and Access Management
Media Sanitization
Virtualization Security
Threats
Business Continuity
Domain 2
CLOUD DATA SECURITY
DOMAIN 2 CLOUD DATA SECURITY
Storage Architectures
Data Lifecycle Security
Database Security
Data Loss Prevention (DLP)
Data Encryption
Key Management
STORAGE ARCHITECTURES: IaaS
Volume storage (block storage) Includes volumes/data
stores attached to IaaS instances, usually a virtual hard
drive. Should provide redundancy
Object storage: Example: Dropbox. Used for write-once,
read many; not suitable for applications like databases
Independent of virtual machine
Because of varying laws and regulations, customers should
always know where their physical data is stored and is stored in
compliance with their needs
DATA STORAGE: PaaS
PaaSutilizes the following data storage types:
Structured: Highly organized, such that inclusion in a
relational database is seamless and readily searchable
Unstructured: Information that doesnt reside in a
traditional row-column databasetext, multimedia
content, email, etc.
DATA STORAGE: SaaS
Information Storage and Management: Data is entered into
the system via the web interface and stored with the SaaS
application (often a backend database)
Content/file storage is stored within the application
DATA SECURITY LIFECYCLE
The Cloud Security Alliance has incorporated the data security
lifecycle which enables the organization to map the different
phases in the data lifecycle against the required controls that
are relevant to each phase.
The lifecycle contains three steps:
Map the different lifecycle phases
Integrate the different data locations and access types
Map into functions, actors and controls
MAPPING THE LIFECYCLE PHASES
FUNCTIONS, ACTORS, AND CONTROLS
DATABASE SECURITY
Mainly supported by two key elements
DAM Database Activity Monitoring that captures and
records all SQL activity in real time or near real time.
Can prevent malicious commands from executing on a
server
FAM File Activity Monitoring that monitors and
records all activity for a specific file repository and can
generate alerts on policy violations
DLP Data Loss Prevention systems
DATA LOSS PREVENTION DLP
Can also be know as Data Leakage Prevention describes
the controls put in place by an organization to ensure that
certain types of data (SSNs, Account Numbers, etc) remain
under organization controls in line with policies, standards,
and procedures
Detects exfiltration of certain types of key data (SSNs,
Account number, etc.)
Help ensure compliance with regulations like HIPAA, PCI-
DSS and others
DATA SECURITY IN THE CLOUD
Protecting Data moving to and within the cloud
SSL/TLS/IP Sec
Protecting Data in the Cloud
Encryption
Detection of Data Migration to the Cloud
DAM, FAM, DLP
Data Dispersion: Data is replicated in multiple physical locations
across your cloud.
Data Fragmentation involves splitting a data set into smaller fragments
(or shards), and distributing them across a large number of machines.
CASES FOR ENCRYPTION
When data moves in and out of the cloud
Protecting data at rest
Compliance with regulations like HIPAA and PCI-DSS
Protection from 3 rd party access
Creating enhanced mechanisms for logical separation
between different customers data
Logical destruction of data when physical destruction is not
feasible
ENCRYPTION BEST PRACTICES
Use Open and validated formats
All encryption keys should be stored within the enterprise
Identity-based key assignment and protection of private
keys
Use strong encryption
Follow Key management best practices for location of keys
DATA ENCRYPTION IN ACROSS IMPLEMENTATIONS

IaaS Encryption uses Volume Storage Encryption and

Object Storage Encryption
PaaS Encryption with Client/Application Encryption,
Databased encryption and proxy-based encryption
SaaS Encryption is managed by the Cloud Service Provider
by the applications and through Proxy encryption
MASKING/OBFUSCATION, ANONYMIZATION,
AND TOKENIZATION
Masking/Obfuscation is the process of hiding, replacing or
omitting sensitive information from a specific dataset. For
instance, masking all but last 4 digits of SSN
Data Anonymization is the process of either encrypting or
removing personally identifiable information from data sets, so
that the people whom the data describe remain anonymous
Tokenization: Public cloud service can be integrated and paired
with a private cloud that stores sensitive data. The data sent to
the public cloud is altered and contains a reference to the data
residing the in the private cloud.
DATA DISCOVERY
Emphasizes visual, interactive analytics rather than static
reporting
Provides a way to make sense of big datathe sheer
volume and diversity of data makes this challenging for the
old means of static reporting
Can provide agile, near real-time analytics
DATA DISCOVERY TECHNIQUES
Data Discovery is a user-driven process of searching for patterns or
specific items in a data set. Data Discovery applications use visual
tools such as geographical maps, pivot-tables, and heat-maps to
make the process of finding patterns or specific items rapid and
intuitive. Data Discovery may leverage statistical and data
mining techniques to accomplish these goals. There are several
different ways Data Discovery tools make their analysis
Metadata provides data its meaning and describes its
attributes
Labels provide a logical grouping of data elements and
gives them a tag describing the data
Content analysis examines the data itself
DATA CLASSIFICATION
Categorizes data based on its value and drives the controls that are put
in place to secure it.
Within the cloud, the CSP should
Ensure proper security controls are in place so that whenever
data is created or modified by anyone, they are forced to classify
or update the data as part of the creation/modification process
Implement Controls (could be administrative, preventive or
compensating)
Make metadata available, as it could be used as a means of
determining classification
Protect data according to its classification at rest and in transit
Should support the reclassification process.
DATA PRIVACY TERMS
Data subject: an identifiable subject who can be identified by reference to
an id number, or one or more factors specific to the his physical,
physiological, mental, economic, cultural, or social identity (Telephone
number, SSN, IP address, etc.)
Personal data: information relating to an identified or identifiable natural
personbiometrics, health data, etc.
Processing: Operations performed on personal datacollection, recording,
organization, storage, etc.
Controller: Person, public authority, agency that determines the purposes
and means of processing to be in compliance with laws and regulations
Processor: One who processes data on behalf of the controller
**The customer is the controller of the data and is responsible to all the legal
duties addressed in the Privacy and Data Protection (P&DP) applicable laws.
The service provider supplies the means and the platform, and is considered
to be the processor.
CSA CLOUD CONTROLS MATRIX (CCMS)
Designed to provide fundamental security principles to guide
cloud vendors and to assist prospective cloud customers in
assessing the overall security risk of a provider
Provides a controls framework in 16 domains that are cross-
walked to other industry-accepted security standards,
regulations, and controls frameworks to reduce audit complexity
It provides mapping to the industry-accepted security standards
such as ISO 27001/27002, COBIT, PCI-DSS
DOMAINS OF THE CCM
MANAGEMENT CONTROLS FOR PRIVACY AND
DATA PROTECTION MEASURES

Separation of Duties
Training
Authentication and Authorization procedures
Vulnerability Assessments
Backup and Recovery processes
Logging
Data-retention control
Secure disposal
DATA RIGHTS MANAGEMENT
DRM or IRM (Information Rights Management) adds an extra
layer of access controls on top of the data object or
document and provides granularity flowing down to
printing, saving, copying and other options
ACLs are embedded into the file, it is agnostic to the
location of data. IRM will travel with the file
Useful for protecting sensitive organization content and
intellectual property
IRM CLOUD CHALLENGES
IRM requires that al users with access should have matching
encryption keys. This requires a strong and comprehensive
identity structure
Each user will need to be provisioned with an access policy and
keys
Access can be identity based or role based (RBAC)
Identity can be implemented with a single director location or
across federated trust
End users will likely have to install a local IRM agent for key
storage or authenticating and retrieval of protected information
Can be challenging with disparate systems and document
readers
DATA PROTECTION POLICIES: RETENTION
Data retention: Established protocol for keeping information for
operational or regulatory compliance needs.
Cloud considerations:
Legal, regulatory and standards requirements must be
well-documented and agreed upon
Data mapping should map all relevant data in order to
understand formats, data types and data locations
Data Classification based on locations, compliance
requirements, ownership and business usage
Each categorys procedures should be followed based on
appropriate policy that governs the data type
DATA PROTECTION POLICIES: DATA DELETION

Safe disposal of data once it is no longer needed.

Physical destruction
Degaussing
Overwriting
Encryption (Crypto-shredding)
DATA PROTECTION POLICIES: DATA ARCHIVING
Data archiving is the process of identifying and moving inactive data out of
current productions systems and into specialized long-term archival
storage systems. Considerations include:
Encryption
Monitoring
Granular retrieval
Electronic discovery (also called e-discovery) any process in which
electronic data is sought, located, secured, and searched with the
intent of using it as evidence in a civil or criminal legal case
Backup and recovery
Media Type
Restoration procedures
AUDITABILITY
In order to be able to perform effective audits and
investigations The CSP should provide an audit log with as
much information as is relevant
When: Time and date of logs and events
Where: Application identifier, application address
(cluster/host or IP Address)
Who: Human or machine
What: Type of event, severity of event and description
SECURITY AND EVENT MANAGEMENT
Software and products combining security information management and event
management. It provides real-time analysis of security alerts generated by network
hardware and applications. SEIM Systems often provide:
Aggregation from many sources
Correlation across common attributes
Alerting to a pre-defined entity responsible for monitoring
Dashboard tools to take event data and organize into charts or other
formats
Compliance tools automate the gathering of compliance data
Retention employs long term storage of historical data to facilitate
correlation of data over time to provide the retention necessary for
compliance
Forensic analysis provides the ability to search across logs on different
nodes and time periods based on specific criteria
CHAIN OF CUSTODY

Chain of Custody is the preservation and protection of

evidence from the time it is collected until the time it is
presented in court.
Documentation should exist for the collection, possession,
condition, location, transfer, access to and any analysis
performed on an item from acquisition through eventual
final disposition
Chain of Custody provision should be included in the
service contract and ensure that the cloud provider will
comply with requests
DOMAIN 2 CLOUD DATA SECURITY REVIEW
Storage Architectures
Data Lifecycle Security
Database Security
Data Loss Prevention (DLP)
Data Encryption
Key Management
Domain 3
CLOUD PLATFORM AND INFRASTRUCTURE SECURITY
DOMAIN 3 CLOUD PLATFORM AND
INFRASTRUCTURE SECURITY DOMAIN
Hypervisor security
VM Concerns, vulnerabilities and weaknesses
Performance and operational complexity
Data Center Operations
Perimeter security
Physical Security
HYPERVISOR SECURITY
NIST SP 800-125 Guide to Security for Full Virtualization
Technologies
Guest OS
Isolation
OS Monitoring
Image and Snapshot Monitoring
 SECURING THE HYPERVISOR
Install all updates to the hypervisor as they are released by the vendor.
Centralized patch management solutions can also be used to administer
updates.
Restrict administrative access to the management interfaces of the hypervisor.
Protect all management communication channels using a dedicated
management network
Synchronize the virtualized infrastructure to a trusted authoritative time server.
Disconnect unused physical hardware from the host system (external drives,
NICs.)
Disable all hypervisor services such as clipboard- or file-sharing between the
guest OS and the host OS unless they are needed
Consider using introspection capabilities to monitor the security of each guest
OS and their interactions
Carefully monitor the hypervisor itself for signs of compromise. This includes
using self-integrity monitoring capabilities that hypervisors may provide, as
well as monitoring and analyzing hypervisor logs on an ongoing basis.
SECURING THE GUEST OS
Follow the recommended practices for managing the physical OS, e.g., time
synchronization, log management, authentication, remote access, etc.
Install all updates to the guest OS promptly. All modern OSs have features
that will automatically check for updates and install them.
Back up the virtual drives used by the guest OS on a regular basis, using
the same policy for backups as is used for non-virtualized computers in the
organization.
In each guest OS, disconnect unused virtual hardware. This is particularly
important for virtual drives (usually virtual CDs and floppy drives), but is
also important for virtual network adapters other than the primary network
interface and serial and/or parallel ports.
Use separate authentication solutions for each guest OS unless there is a
particular reason for two guest OSs to share credentials.
Ensure that virtual devices for the guest OS are associated only with the
appropriate physical devices on the host system, such as the mappings
between virtual and physical NICs.
VIRTUALIZATION CONCERNS
Inter-VM attacks
traffic between the VMs traverses a virtual network and are invisible to the
physical security elements and is sometimes referred to as the Blind Spot
Monitoring of the virtual network is as essential as that of the physical
Performance:
Many security tools affect performance, perhaps more so on VMs
Understanding the virtual environment and the use of proper sizing,
planning and balancing the needs of the environment
VM Sprawl:
The increasing number of VMs in use leaves the potential for oversights and
misconfigurations
Automation and proper governance and long term framework to mitigate
the risks associated with operational complexity.
 VIRTUALIZATION CONCERNS CONTINUED
Instant-On Gaps
Vulnerabilities exist from when a VM is powered on and when its security rules
can be updated
Best practices include network based security and virtual patching that
inspects traffic for known attacks before it can get to a newly provisioned or
newly started VM. It is also possible to enforce NAC (Network Access Control)-
like capabilities to isolate stale VMs until their rules and pattern files are
updated and a scan has been run.
VM Theft or Modification
VM Encryption is necessary as VMs are susceptible to modification or theft,
but it can affect performance
Data Comingling:
Data of different classifications could potentially be stored on the same
physical device
combination of VLANs, firewalls, and IDS/IPS to ensure VM isolation as a
mechanism for supporting mixed mode deployments. We also recommend
using data categorization and policy based management to prevent this. In
Cloud Computing environments, the lowest common denominator of security
could potentially be shared by all tenants in the multi-tenant virtual
environment.
 RECOMMENDATIONS FOR THE CLOUD CUSTOMER
Identify which types of virtualization your cloud provider uses, if any.
Consider a zoned approach, with production separate from test/dev, and highly sensitive
data/workloads in different environments than low-need content.
Consider performance when testing and installing virtual machine security tools, as performance
varies widely. Virtualization-aware server security tools are important to consider.
.Evaluate, negotiate and refine the licensing agreements with major vendors for virtualized
environment.
Secure each virtualized OS by using software in each guest or using an inline virtual machine
combined with hypervisor-based APIs such as VMware vShield.
Virtualized operating systems should be augmented by built-in security measures, leveraging third
party security technology to provide layered security controls and reduce dependency on the platform
provider alone.
Secure by default configuration must be assured by following or exceeding available industry
baselines.
Encrypt virtual machine images when not in use.
Explore the efficacy and feasibility of segregating VMs and creating security zones by type of usage
(e.g., desktop vs. server), production stage (e.g., development, production, and testing) and
sensitivity of data on separate physical hardware components such as servers, storage, etc.
Make sure that the security vulnerability assessment tools or services cover the virtualization
technologies used.
DATA CENTER OPERATIONS
Cloud providers running data center operations should
demonstrate to customers their compliance to current
regulations and standards.
CSPs can/should share results of independent audits
Cloud Trust Protocol is intended to establish digital trust
between a cloud computing customer and provider and
create transparency about the provider's configurations,
vulnerabilities, access, authorization, policy,
accountability, anchoring and operating status conditions.
CloudAudit: Provides automated audit, assertion,
assessment, and assurance
PERIMETER SECURITY
Should add distance, time and scale to the physical access
of systems
Focuses on the 4 Ds
Deter
Detect
Delay
Deny
BACKUP AND RECOVERY CONSIDERATIONS
CSPs should provide assurance in securing customer data backed up
to the cloud for the purpose of fault tolerance and disaster recover.
Solutions might include
SSL/TLS secure transfers
Encrypted storage
Password protections
Geo-redundant storage
Continuous backup
Express restore
Deduplication (finding and removing duplication within data
without compromising its fidelity or integrity allowing a more
intelligent form of data compression)
PHYSICAL LOCATION OF CLOUD INFRASTRUCTURE

Physical location of CSP should be evaluated for location in

relation to
Regions with a high rate of natural disasters (flood,
landslides, seismic activity, etc.)
Regions of high crime, social/political unrest
Frequency of inaccessibility
DOMAIN 3 CLOUD PLATFORM AND
INFRASTRUCTURE SECURITY DOMAIN
Hypervisor security
VM Concerns, vulnerabilities and weaknesses
Performance and operational complexity
Data Center Operations
Perimeter security
Physical Security
Domain 4
CLOUD APPLICATION SECURITY
DOMAIN 4 CLOUD APPLICATION SECURITY
Determining Data Sensitivity
Security Responsibilities Across Models
The Software Development Lifecycle
OWASP Top Ten Vulnerabilities
IAM and Federated identity management
Application Security Testing
DETERMINING DATA SENSITIVITY
Six key questions in relation to determining data sensitivity.
What would the impact be if:
Information was widely distributed
An employee of cloud provider accessed the application
The process was manipulated by an outsider
The process failed to provide the expected result
The information was unexpectedly changed
The application or information was unavailable for a period
of time
SECURITY RESPONSIBILITIES ACROSS MODELS
THE SDLC (SOFTWARE DEVELOPMENT
LIFECYCLE) FOR THE CLOUD
Planning and Requirements analysis: All business requirements
should be defined and risks should be identified
Defining: Clearly defines the requirements through a
requirement specification document
Designing: Specifies hardware and system requirements and
helps define overall architecture
Developing: Work is divided into modules and the actual coding
starts
Testing: Code is tested against requirements: Unit testing,
integration testing, system testing and user acceptance testing
Maintenance: Continuous monitoring and updates as needed
VULNERABILITY DATABASES AND RESOURCES

OWASP (Open Web Application Security Project) Top Ten

CVE (Common Vulnerabilities and Exposures)
CWE (Common Weakness Enumeration)
NVD (National Vulnerability Database)
US CERT (Computer Emergency Response Team)
Vulnerability Database
OWASP (OPEN WEB APPLICATION
SECURITY PROJECT) TOP TEN

OWASP is an international non-profit organization

OWASP (Open Web Application Security Project) Top Ten
Offers a broad consensus on the most common security
flaws/exploits
Designed to raise awareness and the stress the need for
security in web-based applications

https://www.owasp.org/index.php/About_OWASP
OWASP TOP TEN 2013

https://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project#tab=OWASP_Top_10_for_2013
1. CODE INJECTION
Injection flaws, such as SQL, OS, and LDAP injection occur
when untrusted data is sent to an interpreter as part of a
command or query. The attackers hostile data can trick the
interpreter into executing unintended commands or
accessing data without proper authorization
2. BROKEN AUTHENTICATION &
SESSION MANAGEMENT
Application functions related to authentication and
session management are often not implemented
correctly, allowing attackers to compromise passwords,
keys, or session tokens, or to exploit other
implementation flaws to assume other users identities
3. XSS (CROSS SITE SCRIPTING)
XSS flaws occur whenever an application takes
untrusted data and sends it to a web browser without
proper validation or escaping. XSS allows attackers to
execute scripts in the victims browser which can hijack
user sessions, deface web sites, or redirect the user to
malicious sites
4. INSECURE DIRECT OBJECT REFERENCES
Defined as an unauthorized user or process which can invoke
the internal functionality of the software by manipulating
parameters and other object values that directly reference this
functionality. Issues resulting include:
Data disclosure
Privilege escalation
Authentication and authorization checks bypass
Restricted resource access
5. SECURITY MISCONFIGURATIONS

Good security requires having a secure configuration

defined and deployed for the application, frameworks,
application server, web server, database server, and
platform. Secure settings should be defined,
implemented, and maintained, as defaults are often
insecure. Additionally, software should be kept up to
date
6. SENSITIVE DATA EXPOSURE
Many web applications do not properly protect sensitive data, such as
credit cards, tax IDs, and authentication credentials. Attackers may
steal or modify such weakly protected data to conduct credit card
fraud, identity theft, or other crimes. Sensitive data deserves extra
protection such as encryption at rest or in transit, as well as special
precautions when exchanged with the browser
Primary reasons for sensitive data exposure:
Insufficient dataintransit protection
Insufficient dataatrest protection and
Electronic social engineering
7. MISSING FUNCTION LEVEL ACCESS CONTROL

Most web applications verify function level access rights

before making that functionality visible in the UI. However,
applications need to perform the same access control
checks on the server when each function is accessed. If
requests are not verified, attackers will be able to forge
requests in order to access functionality without proper
authorization
Failure to restrict access to privileged functionalities or
URLs. Web pages that provide administrative functionality
are the primary targets for such brute force attacks
Mitigation: Role Based Access Control (RBAC) of functions
and URLs that denies access by default
8. CROSS SITE REQUEST FORGERY (CSRF)

A CSRF attack forces a loggedon victims browser to

send a forged HTTP request, including the victims
session cookie and any other automatically included
authentication information, to a vulnerable web
application. This allows the attacker to force the victims
browser to generate requests the vulnerable application
thinks are legitimate requests from the victim
CSRF MITIGATION STRATEGIES
Do not save username/password in the browser.
Do not check the remember me option in websites.
Do not use the same browser to surf the Internet and
access sensitive websites at the same time, if you are
accessing both from the same machine.
Read standard emails in plain text.
Explicitly log off after using a web application.
Use clientside browser extensions that mitigate
CSRF attacks.
DEVELOPER STRATEGIES TO MITIGATE CSRF
Implement the software to use a unique session specific token
(called a nonce) that is generated in a random, nonpredictable,
nonguessable and/or sequential manner.
CAPTCHAs can be used to establish specific token identifiers
per session.
The uniqueness of session tokens is to be validated on the
server side and not be solely dependent on client based
validation.
Use POST methods instead of GET requests for sensitive data
transactions and privileged and state change transactions, along
with randomized session identifier generation and usage
9. KNOWN VULNERABLE COMPONENT USAGE

Components, such as libraries, frameworks, and other

software modules, almost always run with full
privileges. If a vulnerable component is exploited, such
an attack can facilitate serious data loss or server
takeover. Applications using components with known
vulnerabilities may undermine application defenses
and enable a range of possible attacks and impacts
Deprecated, insecure and banned APIs
10. NON VALIDATED REDIRECTS AND FORWARDS

Web applications frequently redirect and forward users

to other pages and websites, and use untrusted data to
determine the destination pages. Without proper
validation, attackers can redirect victims to phishing or
malware sites, or use forwards to access unauthorized
pages
THREAT MODELING
Identify Security Objectives
Legislative Drivers
Contractual Requirements
Alignment with Business Objectives
CIA Triad
Tools for Threat Modeling
Data Flow Diagrams
Use/Misuse Cases
THREAT MODELING: DATA FLOW DIAGRAMS

Blue circles are

data
transformations
(processing).
Arrows are data
flows. The
"Student
database" is a
data store
USE/MISUSE CASES

https://www.owasp.org/index.php/Application_Threat_Modeling
THREAT MODELING: STRIDE

Threat Mitigation
Spoofing Authentication
Tampering Integrity Verification (Message Digests/CRCs)
Repudiation Non-Repudiation (Digital Signatures, Keys)
Information Disclosure Confidentiality Through Encryption
Denial of Service High Availability/Redundancy/Fault Tolerance
Escalation of Privilege Authorization
RISKS IN DESIGN
Code Reuse
Flaws vs. Bugs
Flaw: Inherent fault with the design of code
Bug: Implementation fault
Open vs. Closed Design
CONTROLS EVALUATION
Efficacy of Controls
Economy of Mechanism
Cost/Benefit Analysis
Psychological Acceptability
SUPPLEMENTAL SECURITY DEVICES
WAF Web Application Firewall is Layer 7 firewall that can
understand HTTP traffic and help prevent DoS attacks
DAM Database Activity Monitoring is a layer 7 monitoring device
that understands SQL commands and can limit code injection
XML Gateways transform how services and sensitive data are
exposed as APIs to developers and users and can implement
DLPs, antivirus and anti-malware
Firewalls can be configured across the SaaS, PaaS and IaaS
API Gateways filter APIs and can implement access control, rate
limiting, logging, metrics and filtering
APPLICATION SECURITY TESTING
SAST Static Application Security Testing: Whitebox test used to
determine structure and logic and to detect coding errors without
executing the code. Should be done early in the lifecycle
DAST Dynamic Application Security Testing is used with
applications in their running state and is considered a black-box
test
RASP Runtime Application Self Protection: enables applications to
protect themselves by identifying and blocking attacks in real time.
Unlike firewalls, which rely solely on network data to work, RASP
leverages the applications intrinsic knowledge of itself to accurately
differentiate attacks from legitimate traffic, stopping only malicious
traffic
DOMAIN 5 OPERATIONS
Physical and Environmental Controls for the Datacenter
Logical Cloud Infrastructure
Risk Assessments of Physical and Logical Infrastructure
PHYSICAL AND ENVIRONMENTAL DESIGN

In establishing a physical security function within a cloud

environment, the following must be considered:
The security needs for the equipment and services
being protected
The human resources that are in place for physical
security
How legacy physical security efforts have been
managed and staffed prior to transition to cloud
The financial resources available for these efforts
PHYSICAL AND ENVIRONMENTAL DESIGN
CONTINUED

Physical security normally takes one of four forms in

design and implementation
Environmental design
Mechanical, electronic and procedural controls
Detection and response procedures
Personnel identification, authentication, and access control
HUMAN RESOURCES CONTROLS
The purpose of the human resources physical control is to minimize the
risk of the personnel closest to the data disrupting operations and
compromising the cloud. Consider the following measures:
Roles and responsibilities
Background Agreements
Employment Agreement
Employment Termination
Separation of Duties
Job Rotation
Mandatory Vacations
PHYSICAL LOCATION OF THE CSP FACILITY
Check if the location of the facility falls under any active
seismic zone and the risks thereof.
Facility should not be located in a geographic region which
is prone to:
Flooding, landslides or other natural disasters
Political, ethnic, communal or social unrests
Easy and quick accessibility of the facilitys location
 DOCUMENT REVIEW
Physical & Environmental Security Policy
User Account Termination Procedures
Contingency Plan
Incident Reporting & Response Plan
Emergency Response Plan
Facility Layout emergency exits, positioning of CCTV cameras, secure
entry points
Fire Exit Route Map & Fire Order Instructions
Emergency Evacuation Plan & Procedures
Crisis Communication Procedures
Emergency Contact Numbers
User Facility Access Review/Audit Records
Security Awareness Training documentation, presentation, handouts, etc
 DOCUMENT REVIEW
CONTINUED
Security Awareness Attendance Records
Succession Planning for key executives
Technical Documents electrical wiring diagrams, BMS, UPS,
AHU details
Maintenance Schedule of Electrical, Generator & CCTV
List of Authorized Personnel allowed entry inside facility
Security Staff profiles bio & background information
Background Check Reports of Security Staff (must be
performed every year)
Annual Maintenance Contracts for key equipment & devices
(focus on SLAs for equipment/devices downtime &
restoration)
 CSP ASSESSMENT
Check whether all the documents are updated and current. The documents must
be reviewed by the CSP at least once in a year. Should include revision data and
signoff
Further, the policy and procedure documents (that are suitable for employee
viewing) should be made available through a common Intranet site where
authorized employees of the CSP can access them anytime for reference.
Check whether the CSP has security awareness program in place. At the
minimum, the CSP should ensure that employees are given adequate security
awareness training at least once a year and receive sign off from them. Also, new
employees joining the organization shall undergo a security orientation session
as part of the induction program where key policies and procedures are to be
covered. To make the program effective, a senior staff from the security team
must conduct the session
If the CSP is compliant with global security standards like ISO 27001 ISMS or any
other industry-specific standard :
Verify the compliance certificate and its validity.
Look for verifiable evidence of resources allocation budget and
manpower to sustain the compliance program.
Verify internal audit reports and evidence of remedial actions for the
findings.
PERIMETER SECURITY

Data Center Fire Exits

Administrative CCTV Command Center
areas AHU Room
Locker Room
Reception UPS Room
Parking Area Generator Room
Fuel Storage
Storage Area
SECURITY INFRASTRUCTURE
Secure Entry Points Access Fire Exits (must not be locked)
control systems (proximity Panic Bars in fire exits
cards/biometric access)
CCTV Cameras and DVR server
Access Control System linked (including backup timelines)
with fire control panel for
emergency release Door Closures and time-delay door
alarms
Emergency auto-release buttons
near all access card readers Gas-based fire suppressants inside
Data Centers
Motion-sensing alarms, thermal
tracking devices Paper Shredders near printers
Emergency Response Team Kit (ERT
Fire Safety Equipment Wet Kit)
Riser, Hydrants, Hoses,
Two-way Radio devices (Walkie-
Smoke Detectors & Water talkie handsets) for security staff
Sprinklers
Duress Alarms underneath security
Fire Extinguishers desk and vantage (concealed) points
SECURITY GUARDS
Curbing tail-gating by employees.
Handle visitors and movement within the facility.
Handling phone calls.
Monitoring intrusion and fire alarm systems and dispatch personnel to respond to
alarms.
Controlling movement of materials into and out of the building and enforcing
property pass regulations.
Enforcing rules and regulations established for the building.
Patrolling inside facility.
CCTV monitoring.
Key control and management.
Frisking and checking housekeeping and maintenance personnel during entry and
exit.
Emergency response procedures.
Escalating security-related issues to security manager.
Accepting and dispatching mail.
Escort unattended business visitors inside the office.
ENVIRONMENTAL CONTROLS
American Society of Heating, Refrigeration, and Air
Conditioning Engineers (ASHRAE) Technical Committee 9.9
has created a set of guidelines for temperature and
humidity ranges in the datacenter
Temperature between 64 and 80 degrees Fahrenheit
Humidity should be between 40 and 80 percent
Cable management strategy should be in place to minimize
airflow obstructions caused by cable and wiring
Hot/Cold aisles should be established