3.6 - Given a scenario, apply cybersecurity solutions to the cloud. Flashcards
Cloud security controls
Cloud-native security controls
– Integrated and supported by the cloud provider
– Many configuration options
– Security is part of the infrastructure
– No additional costs
High availability across zones
*
Availability zones (AZ)
– Isolated locations within a cloud region (geographical location)
– AZ commonly spans across multiple regions
– Each AZ has independent power, HVAC, and networking
*
Build applications to be highly available (HA)
– Run as active/standby or active/active
– Application recognizes an outage and moves to the other AZ
*
Use load balancers to provide seamless HA
– Users don’t experience any application issues
Resource policies
*
Identity and access management (IAM)
– Who gets access, what they get access to
*
Map job functions to roles
– Combine users into groups
*
Provide access to cloud resources
– Set granular policies - Group, IP address, date and time
*
Centralize user accounts, synchronize across all platforms
Secrets management
*
Cloud computing includes many secrets
– API keys, passwords, certificates
*
This can quickly become overwhelming
– Difficult to manage and protect
*
Authorize access to the secrets
– Limit access to the secret service
*
Manage an access control policy
– Limit users to only necessary secrets
*
Provide an audit trail
– Know exactly who accesses secrets and when
Integration and auditing
*
Integrate security across multiple platforms
– Different operating systems and applications
*
Consolidate log storage and reporting
– Cloud-based Security Information and Event
Management (SIEM)
*
Auditing - Validate the security controls
– Verify compliance with financial and user data
Storage
*
Data is on a public cloud
– But may not be public data
*
Access can be limited
– And protected
*
Data may be required in different geographical locations
– A backup is always required
*
Availability is always important
– Data is available as the cloud changes?
Permissions
*
A significant cloud storage concern
– One permission mistake can cause a data breach
– Accenture, Uber, US Department of Defense
*
Public access
– Should not usually be the default
*
Many different options
– Identity and Access Management (IAM)
– Bucket policies
– Globally blocking public access
– Don’t put data in the cloud unless it really
needs to be there
Encryption
*
Cloud data is more accessible than non-cloud data
– More access by more people
*
Server-side encryption
– Encrypt the data in the cloud
– Data is encrypted when stored on disk
*
Client-side encryption
– Data is already encrypted when it’s sent to the cloud
– Performed by the application
*
Key management is critical
Replication
*
Copy data from one place to another
– Real-time data duplication in multiple locations
*
Disaster recovery, high availability
– Plan for problems
– Maintain uptime if an outage occurs
– Hot site for disaster recovery
*
Data analysis
– Analytics, big data analysis
*
Backups
– Constant duplication of data
High availability
Availability zones (AZ)
– Isolated locations within a cloud region (geographical location)
– AZ commonly spans across multiple regions
– Each AZ has independent power, HVAC, and networking
Build applications to be highly available (HA)
– Run as active/standby or active/active
– Application recognizes an outage and moves to the other AZ
Use load balancers to provide seamless HA
– Users don’t experience any application issues
Virtual networks
*
A cloud contains virtual devices
– Servers, databases, storage devices
*
Virtual switches, virtual routers
– Build the network from the cloud console
– The same configurations as a physical device
*
The network changes with the rest of the infrastructure
– On-demand
– Rapid elasticity
Public and private subnets
Private cloud
– All internal IP addresses
– Connect to the private cloud over a VPN
– No access from the Internet
Public cloud
– External IP addresses
– Connect to the cloud from anywhere
Hybrid cloud
– Combine internal cloud resources with external
– May combine both public and private subnets
Segmentation
The cloud contains separate VPCs, containers,
and microservices
– Application segmentation is almost guaranteed
*
Separation is a security opportunity
– Data is separate from the application
– Add security systems between application
components
*
Virtualized security technologies
– Web Application Firewall (WAF)
– Next-Generation Firewall (NGFW)
*
Intrusion Prevention System (IPS)
API inspection and integration
Microservice architecture is the
underlying application engine
– A significant security concern
API calls can include risk
– Attempts to access critical data
– Geographic origin
– Unusual API calls
API monitoring
– View specific API queries
– Monitor incoming and outgoing data
Compute