ch09
ch09
Cloud Forensics
1
Objectives
2
An Overview of Cloud Computing
3
An Overview of Cloud Computing
4
History of the Cloud
5
History of the Cloud
6
Types of Cloud Computing Services
7
Infrastructure as a Service (IaaS)
• Advantages
• Dynamic infrastructure scaling
• Guaranteed uptime
• Automation of administrative tasks
• Elastic load balancing (ELB)
• Policy-based services
• Global accessibility
• Disadvantages
• Software security is at high risk (third-party providers are more
prone to attacks)
• Performance issues and slow connection speeds
8
Platform as a Service (PaaS)
• Advantages
• Simplified deployment
• Prebuilt business functionality
• Lower risk
• Instant community
• Pay-per-use model
• Scalability
• Disadvantages
• Vendor lock-in
• Data privacy
• Integration with the rest of the system applications
9
Software-as-a-Service (SaaS)
• Advantages
• Low cost
• Easier administration
• Global accessibility
• Compatible (Requires no special hardware or software)
• Disadvantages
• Security and latency issue
• Total dependency on the Internet
• Switching between SaaS vendors is difficult
10
Separation of Responsibilities in Cloud
11
Deployment Methods for a Cloud
12
Cloud Computing Threats
13
Cloud Computing Threats
14
Cloud Computing Attacks
15
Cloud Vendors
• Salesforce
• IBM Cloud
• Cisco Cloud Computing
• Amazon EC2
• AT&T Synaptic
• Google Cloud Storage
• HP Helion
• Microsoft Azure
16
Cloud Forensics
17
Legal Challenges in Cloud Forensics
CSP components must state who is authorized to access data and what
limitations are in conducting acquisitions for an investigation
18
Service Level Agreements
19
Service Level Agreements
20
Service Level Agreements
21
Jurisdiction Issues
22
Accessing Evidence in the Cloud
• Search Warrants
• Can be used only in criminal cases and must be requested by a
law enforcement officer who has evidence of probably cause
that a crime was committed
• Law requires search warrants to contain specific descriptions of
what’s to be seized
• For cloud environments, the property to be seized usually
describes data rather than physical hardware, unless the CSP is
the suspect
• Must also describe the location of items to be seized
• Difficult when dealing with cloud data because servers are
often dispersed across state or national borders
• Must establish how it will be carried out
• Specifying the date and time of day to minimize disruptions
to people and business operations
23
Technical Challenges in Cloud Forensics
• Architecture
• Data collection
• Analysis of cloud forensic data
• Anti-forensics
• Incident first responders
• Role management
• Legal issues
• Standards and training
24
Architecture
Deletion in the cloud: CPS may not implement necessary methods to retrieve
information on deleted data in an IaaS or PaaS delivery models
Single points of failure and no single point of failure for criminals: Cloud
ecosystem has single points of failure, which may have adverse impact on the
evidence acquisition process. Collection and analysis of evidentiary data from
distributed and disparate sources is highly difficult as criminals may choose one
CSP to store their data, second CSP to obtain computing services, and third CSP
to route all their communications
25
Architecture
Cloud confiscation and resource seizure may of ten affect the business continuity
of other tenants
26
Architecture
27
Data Collection
Decreased access and data: CSPs hide data location purposefully to ease data
movement and replication
Chain of dependencies: , CSPs and most cloud apps rely on other CSP(s), and the
dependencies in a chain of CSP(s)/client(s) can be prominently dynamic
Data location
Root of trust: Determining the reliability and integrity of cloud forensics data is a
challenge
28
Data Collection
29
Log Collection
Decentralization of Logs
Evaporation of Logs: Once the VM instance is powered off the logs will vanish
Multiple Layers and Tiers: There are many layers and tiers in cloud architecture
and loss are generated in each tier which are valuable to the investigator but
collection from different places is a challenge
30
Anti-Forensics
31
Anti-Forensics
32
Incident First Responders
33
Role Management
34
Investing Cloud Storage Services
35
Investigating Google Drive
36
Artifacts Left by Google Drive Web Portal
37
Artifacts Left by Google Drive Web Portal
38
Artifacts Left by Google Drive on Windows
39
Artifacts Left by Google Drive on Windows
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\Folders
HKCU\SOFTWARE\Google\Drive
HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\GoogleDriveSync
HKCU\SOFTWARE\Classes
40
Artifacts Left by Google Drive on Windows
41
Artifacts Left by Google Drive on Windows
42
Artifacts Left by Google Drive on Windows
43
Artifacts Left by Google Drive on Windows
44
Artifacts Left by Google Drive on Windows
45
Disk Pulse
46
Directory Monitor
47
Artifacts Left by Google Drive on Windows
48
Artifacts Left by Google Drive on Windows
49
Investigating OneDrive
50
Investigating OneDrive
51
Investigating Dropbox
52
Artifacts Left by Dropbox Web Portal
53
Artifacts Left by Dropbox Web Portal
54
Artifacts Left by Dropbox Web Portal
55
Artifacts Left by Dropbox on Windows
56
Artifacts Left by Dropbox on Windows
57
Artifacts Left by Dropbox on Windows
58
Artifacts Left by Dropbox on Windows
config.db: Obtain some Information about local Dropbox Installation and account.
Lists the email IDs linked with the account, current version/build for the Ideal
application, the host_id, and local path information
sigstore.db: Record SHA-256 hash and each File's site information, but no names
etc.
59
Artifacts Left by Dropbox on Windows
60
Artifacts Left by Dropbox on Windows
61
Artifacts Left by Dropbox on Windows
62
Summary
63
Summary
64