Module 2 CyberOps
Module 2 CyberOps
Module 2:
Introduction to Cloud Computing and Security
Cloud Computing
&
Cloud Service Models
Cloud Service Models
Source: https://www.hostingadvice.com/how-to/cloud-hosting-statistics/
• Distributed storage.
• Scalability (vertically & horizontally).
• Resource pooling.
• Accessibility.
• Measured service.
• Automated management.
NIST on Cloud
• https://nvlpubs.nist.gov/nistpubs/legacy/sp/nistspecialpublication800-145.p
df
Cloud Essentials
• NIST state that cloud computing should have the following essential
characteristics:
Source: https://cic.gsa.gov/basics/cloud-basics
Cloud Deployment Models
Source: https://cic.gsa.gov/basics/cloud-basics
SaaS
• Cloud Service Providers (CSPs) must take security and compliance very
seriously.
• In the IaaS the CSP only must patch hypervisors and other supporting
hardware.
• Your cloud provider should agree in writing to provide the level of security
required for your customers.
DevOps, CI, CD, DevSecOps
DevOps & Others
• Prior to DevOps other models were used, the most popular being:
• Waterfall:
• a software and hardware development and project management
methodology that has at least five to seven phases that follow in strict
linear order.
• Each phase cannot start until the previous phase has been
completed.
DevOps & Others
• Agile:
• is a software development and project management process where a
project is managed by breaking it up into several stages and involving
constant collaboration with stakeholders and continuous improvement
and iteration at every stage.
Back to DevOps
• Product management.
• Software (or hardware) development.
• Quality assurance (QA).
• IT operations.
• Infosec and cybersecurity practices.
DevOps Methods
1. The first way includes systems and flow. In this way (or method), you make work
visible by reducing the work “batch” sizes, reducing intervals of work, and
preventing defects from being introduced by building in quality and control.
2. The second way includes a feedback loop to prevent problems from happening
again (enabling faster detection and recovery by seeing problems as they occur and
maximizing opportunities to learn and improve).
• For example, although your data is in the cloud, it must reside in a physical
location somewhere.
• Your cloud provider should agree in writing to provide the level of security
required for your customers.
Questions to ask your CSP
The following are questions to ask a cloud provider before signing a contract
for its services:
Who has access?
• Access control is a key concern because insider attacks are a huge risk.
Anyone who has been approved to access the cloud has the potential of
mishandling or exposing data to unauthorized users, so you want to know
who has access and how they were screened.
• Another example where you want to monitor who has access to what cloud
service is when an employee leaves your organization, and he or she was
the only “administrator,” and then you find out that you don’t have the
password to the cloud service, or the cloud service gets canceled because
maybe the bill didn’t get paid.
• This example seems like an immature way of handling a production
service, but this still happens in today’s environment.
Questions to ask your CSP
• This particular item is no small matter in that the cloud provider should
agree in writing to the terms of the audit.
• With cloud computing, maintaining compliance could become more difficult
to achieve and even harder to demonstrate to auditors and assessors.
• Of the many regulations touching on information technology, few were
written with cloud computing in mind.
• Auditors and assessors might not be familiar with cloud computing
generally or with a given cloud service in particular.
Questions to ask your CSP
• Because cloud-based services are accessible via the Internet, they are
open to any number of attacks.
• Some of the potential attack vectors that criminals might attempt include
the following:
• DoS/DDoS, Session Hijacking, DNS Attacks, XSS, Hypervisor attacks,
Virtual Machine attacks, CSRF, SQL Injection, MiTM, Side-channel
attacks, Authentication attacks, API attacks, Other known vulnerabilities.