CCSK Flashcards
Core of Big Data, the 3 V’s
Volume
Velocity
Variety
5 Essentials of Cloud Computing per NIST
Broad Network Access, Rapid elasticity, Measured Service, On Demand Self Service, Resource Pooling
3 A’s of Vulnerability
Authentication
Authorization
Accounting
Service Models
Software as a Service (SaaS)
Platform as a Service (PaaS)
Infrastructure as a Service (IaaS)
Deployment Models
Public
Private
Hybrid
Community
IaaS
provider is responsible for foundational security, while the cloud user is responsible for everything they build on the infrastructure. Unlike PaaS, this places far more responsibility on the client
PaaS
Cloud provider is responsible for the security of the platform, while the consumer is responsible for everything they implement on the platform, including how they configure any offered security features
SaaS
cloud provider is responsible for nearly all security
Logical Model
Infrastructure
Metastructure
Infostructure
Applistructure
Cloud Security Process Model
Identify Requirements Select Provider Define Architecture Assess Security Controls Identify Gaps Design and Implement Controls Manage Changes
Cloud Security Models
Conceptual Model/Framework
Control Model/Framework
Reference Architecture
Design Patterns
Design patterns
are reusable solutions to problems
Reference architectures
templates for implementing cloud security, typically generalized They can be very abstract, bordering on conceptual, or quite detailed
Controls models or frameworks
specific cloud security controls or
categories of controls, such as the CSA CCM
Conceptual models or frameworks
visualizations and descriptions used to explain cloud security concepts and principles
Infrastructure
Core components of a computing system: compute, network, and storage foundation that everything else is built on
Metastructure
protocols and mechanisms that provide the interface between the infrastructure layer and the other layers. The Glue that holds it all together. Main difference between cloud and traditional computing
Infostructure
data and information. Content in a database, file storage, etc.
Applistructure
applications deployed in the cloud and the underlying application services used to build them
Three main aspects of BC/DR
- Ensuring continuity and recovery. tools and techniques to best architect cloud deployment, keep things running.
- Preparing for and managing provider outages.
- Considering options for portability in case you need to migrate providers or platforms
BC/DR
is a shared responsibility takes a risk-based approach must account for the entire logical stack
Enterprise risk management (ERM)
includes managing overall risk for the organization, aligned to the organization’s governance and risk tolerance. Enterprise risk management includes all areas of risk, not merely those concerned with technology
Based on Shared Responsibility Model
Governance
(Cannot be Outsourced)
includes the policy, process, and internal controls that comprise how an organization is run. Everything from the structures and policies to the leadership and other mechanisms for management
Information risk management
covers managing the risk to information, including information technology
Information security
is the tools and practices to manage risk to information
Contracts:
primary tool of governance is the contract between a cloud provider and a cloud customer (this is true for public and private cloud). The contract is your only guarantee of any level of service or commitment—assuming there is no breach of contract
Supplier Assessments:
assessments are performed by the potential cloud customer using available information and allowed processes techniques. They combine contractual and manual research with third-party attestations and technical research
Attestation
legal statements often used to communicate the results of an assessment or audit
Compliance reporting
The documentation on a provider’s internal (i.e. self) and external compliance assessments Can be performed by provider, customer or 3rd party (preferred)
Cloud Security Alliance STAR Registry
an assurance program and documentation registry for cloud provider assessments based on the CSA Cloud Controls Matrix and Consensus Assessments Initiative Questionnaire
Risk tolerance
amount of risk that the leadership and stakeholders of an organization are willing to accept. It varies based on asset and you shouldn’t make a blanket risk decision about a particular provider; rather, assessments should align with the value and requirements of the assets involved
Cloud Risk Management Tools
- Request or acquire documentation.
- Review their security program and documentation.
- Review any legal, regulatory, contractual, and jurisdictional requirements for both the provider and yourself.
- Evaluate the contracted service in the context of your information assets.
- Separately evaluate the overall provider, such as finances/stability, reputation, and outsourcers.
Residual risk
after all your assessments and the controls that you implement yourself there is still residual risk your only options are to transfer it,
accept the risk, or avoid it
Data Protection
Laws and regulations vary greatly depending on location of provider, user, servers, data subject, treaties
Cross-border Data Transfers
countries prohibit or restrict the transfer of information out of their borders. In most cases, the transfer is permitted only if the country to which the data is transferred offers an “adequate level of protection”
General Data Protection Regulation (GDPR)
directly binding on any corporation that processes the data of EU citizens, and will be adjudicated by the data supervisory authorities or the courts of the member states that have the closest relationship with the individuals or the entities on both sides of the dispute
Applicability
processing of personal data in the context of the activities of an establishment of a controller or processor
Processing of personal data is allowed if?
(a) the data subject has freely given specific, informed, and unambiguous indication of his/her consent to the processing of his/her personal data or
(b) the processing is authorized by a statutory provision
Accountability Obligations
requirements placed companies to keep records of their data processing activities
Data Subjects’ Rights
subjects have rights to information regarding the processing of their data: the right to object to certain uses of their personal data; to have their data corrected or erased; to be compensated for damages suffered because of unlawful processing; the right to be forgotten; and the right to data portability
Network Information Security Directive
framework to enable networks and information systems to resist, at a given level of confidence
Scope of Preservation
Data that a requesting part is entitled to. It is hosted in the cloud and contains, or is reasonably calculated to lead to, relevant, probative information for the legal issue at hand
Dynamic and Shared Storage
cloud environment that programmatically modifies or purges data, or one where the data is shared with people unaware of the need to preserve, preservation can be more difficult.
Access and Bandwidth
Clients ability to access it own data.
Determined by Service Level Agreements.
Ability to collect large volumes of data quickly and in a forensically sound manner may be limited
Forensics
by-bit imaging of a cloud data source is generally difficult or impossible. For obvious security reasons, providers are reluctant to allow access to their hardware, particularly in a multitenant environment where a client could gain access to other clients’ data
Reasonable Integrity
reasonable steps to validate that its collection from its cloud provider is complete and accurate, especially were ordinary business procedures for the request are unavailable and litigation-specific measures are being used to obtain the information
Limits to Accessibility:
When Cloud customer cannot access their data due to access rights, privileges and how data is stored
Compliance
validates awareness of and adherence to corporate obligations (e.g., corporate social responsibility, ethics, applicable laws, regulations, contracts, strategies, and policies)
Audits
key tool for proving (or disproving) compliance
pass-through audits
providers certified for various regulations and industry requirements, such as PCI DSS, SOC1, SOC2, HIPAA, best practices/frameworks like CSA CCM, and global/regional regulations like the EU GDPR
Artifacts
The logs, documentation, and other materials needed for audits and compliance; they are the evidence to support
compliance activities
Multitenancy data governance
data is stored in the public cloud, it’s stored on shared infrastructure with other, untrusted tenants
Shared security responsibility
Data is now more likely to be owned and managed by different teams or even organizations
Ownership
Owner of the data, may not always be clear and depends on laws, contracts, and policies
Custodianship
Refers to who is managing the data
Jurisdictional boundaries and data sovereignty
Locations where the data is stored
3 things that are impacted by cloud due to the combination of a third-party provider and jurisdictional changes
Compliance, regulations, and privacy policies
Destruction and removal of data
ties into the technical capabilities of the cloud platform. Can you ensure the destruction and removal of data in accordance with policy
Information Classification
Tied to compliance, determines how and where data can and cannot be stored. (Personnel files, Medical files etc.)
Information Management Policies
tie to classification and the cloud needs to be added if you have them. They should also cover the different SPI tiers, since sending data to a SaaS vendor versus building your own IaaS app is very different
Data Security Lifecycle
Create, Store, Use, Share, Archive, Destroy ↻
Create
Creation is the generation of new digital content, or the alteration/updating/modifying of existing content
Store
Storing is the act committing the digital data to some sort of storage repository and typically occurs nearly simultaneously with creation
Use
Data is viewed, processed, or otherwise used in some sort of activity, not including modification
Share
Information is made accessible to others, such as between users, to customers, and to partners
Archive
Data leaves active use and enters long-term storage
Destroy
Data is permanently destroyed using physical or digital means (e.g., cryptoshredding)
3 Function with Data
Read: ad the data, including creating, copying, file transfers, dissemination, and other exchanges
Process: transaction on the data; update it, use it
Store. Hold the data (in a file, database, etc.)
management plane
is the single most significant security difference between traditional infrastructure and cloud computing
• The cloud provider is responsible for ensuring the management plane is secure and necessary security features are exposed to the cloud user, such as granular entitlements to control what someone can do even if they have management plane access.
• The cloud user is responsible for properly configuring their use of the management plane, as well as for securing and managing their credentials
Architect for Failure
Do not rely on traditional strategies (lift and shift) when migrating to the cloud. They will be less resilient. Leverage new cross platform and isolation technologies to improve failover
Ways to access the Management Plane
APIs and web consoles are the way the management plane is delivered
Software Development Kits (SDKs) and Command Line Interfaces (CLIs)
Tools provided by the cloud provider to make integration easier
Identity and Access Management (IAM)
identification, authentication, and authorizations. How you determine who can do what within your cloud
authentication mechanisms in REST
HTTP request signing and OAuth are the most common; both leverage cryptographic techniques to validate