Q No: 1) Discuss Security of Database Services

SECURITY OF DATABASE SERVICES

Database-as-a-Service (DBaaS) is a key component of cloud computing, offering users scalable, managed
database solutions. However, delegating database management to cloud providers raises serious security
concerns regarding data integrity, confidentiality, and availability.
Entities Involved in DBaaS Security
1. Data Owners
Individuals or organizations that generate and own the data.
2. Database Users
Clients accessing the DBaaS for queries and data retrieval.
3. Cloud Service Providers (CSPs)
The companies that host and manage cloud databases.
4. Third-Party Auditors (TPAs)
Independent entities that verify compliance and security.
Major Security Threats to DBaaS
1. Data Integrity and Confidentiality Risks
• Unauthorized Access
Weak authentication and access control mechanisms expose databases to unauthorized users.
• Insider Threats
Superusers with excessive privileges can manipulate, leak, or delete sensitive data.
• Encryption Issues
Inconsistent use of encryption or weak encryption keys can make stored data vulnerable.
2. External Attacks
• SQL Injection
Attackers manipulate database queries to gain unauthorized access or modify data.
• Man-in-the-Middle (MitM) Attacks
Interception of data transmitted between users and DBaaS.
• Side Channel Attacks
Exploiting patterns in database access to infer confidential information.
3. Multi-Tenancy Risks
• Data Leakage
Different users sharing the same physical infrastructure increases the risk of data leaks.
• Illegal Data Recovery
Improperly sanitized storage devices can allow retrieval of previously deleted data.
4. Availability Risks
 • Denial-of-Service (DoS) Attacks
Overloading the database service to make it inaccessible.
• Resource Exhaustion
Inefficient allocation of database resources can lead to system crashes.
Security Measures for DBaaS
1. Strong Authentication and Access Control
• Implement multi-factor authentication (MFA).
• Enforce role-based access control (RBAC) to limit user privileges.
2. Data Encryption and Secure Storage
• Encrypt data at rest and in transit using strong cryptographic standards.
• Use homomorphic encryption to allow computations on encrypted data without decryption.
3. Secure Backup and Disaster Recovery
• Maintain regular backups with version control.
• Implement geo-redundancy to ensure data availability in case of disasters.
4. Auditing and Monitoring
• Enable log tracking for access and modification records.
• Utilize anomaly detection systems to detect suspicious database activity.

Question No 2: Explain Security Risks Posed by Shared Images & Management OS

SECURITY RISKS POSED BY SHARED IMAGES

1. Introduction
• Image sharing in cloud computing, especially in IaaS cloud delivery models, poses significant security
risks.
• Example: In AWS EC2, users can choose Amazon Machine Images (AMIs) via:
o Quick Start (official, pre-configured images).
o Community AMIs (user-shared images).
• Problem: Many users, especially beginners, use public/shared AMIs without verifying their security.
• Even trusted cloud providers cannot prevent all risks from shared images.
2. Security Risks Found in Shared AMIs
A. Backdoors & Leftover Credentials
22% of scanned Linux AMIs contained credentials allowing remote login.
Identified:
• 100 passwords.
• 995 SSH keys.
 • 90 cases with both passwords and SSH keys exposed.
Attack Vectors
1. SSH Key Backdoors
o AWS stores user’s public SSH key in ~/.ssh/authorized_keys.
o Malicious AMI creators can leave their own SSH keys.
o They can log into any instance using that image.
2. Password-Based Authentication
o If SSH password authentication is enabled, AMI creators may leave their passwords.
o Attackers can extract password hashes and crack them using "John the Ripper".
B. Unsolicited Connections & Data Leaks
Outgoing connections from compromised AMIs may leak:
• Instance IP address.
• System logs (/var/log/syslog).
• Login events, web requests, and user activity.
Example:
Audit found Linux instances with modified syslog daemons forwarding logs to an external server.
C. Malware & Trojan Infections
Malware types found in AMIs:

• Trojan-Spy (variant 50112) → Keylogging, data theft, process monitoring.

• Trojan-Agent (variant 173287) → Stealing stored passwords from Firefox.

• Virus-infected Windows AMIs detected via ClamAV malware scanner.
D. Risks for AMI Creators (Privacy Concerns)
• Sensitive files (e.g., AWS API keys) may be exposed.
• Malicious users can extract private information like:
o API keys ([Link], [Link])
o SSH private keys (id_rsa, id_dsa)
o IP addresses & user data logs
o Browser history & shell history (.bash_history)

SECURITY RISKS POSED BY A MANAGEMENT OS

1. Introduction
• Virtualization is often considered more secure because a hypervisor is smaller and easier to analyze
than a traditional operating system.
• However, the hypervisor still depends on a Management OS (Dom0) for:
 o VM creation and administration.
o Storage and network operations.
o Device driver support and live migration.
• Key issue: Management OS is part of the Trusted Computing Base (TCB) and can introduce security
risks.
2. Security Risks of Dom0 (Management OS)
Dom0 has full control over the system and can:
• Create new VMs.
• Modify kernel settings of guest VMs.
• Manage storage and networking operations.
Attack Vectors
A malicious Dom0 can compromise guest VMs during:
1. VM creation.
2. VM execution.
A. Security Risks During VM Creation
Possible malicious actions by Dom0:
• Refuse to start the VM (Denial-of-Service attack).
• Modify guest OS kernel to allow remote access.

• Set incorrect page tables → compromise memory integrity.

• Retain foreign mapping access → spy on the VM while it runs.

B. Security Risks During VM Execution
Potential attacks:
• Eavesdropping on data transfers (network traffic, disk storage).
• Extracting cryptographic keys from guest VMs.
• Blocking or modifying access to XenStore (configuration storage).

Question No: 3) Discuss how virtual machines are secured

VIRTUAL MACHINE SECURITY

Virtual Machines (VMs) are widely used in cloud computing, allowing multiple operating systems to run on
a single physical server. However, they introduce unique security challenges due to shared resources,
hypervisor vulnerabilities, and potential misconfigurations. VM security refers to the protection of virtualized
environments from unauthorized access, data breaches, malware attacks, and system vulnerabilities. It involves
securing both the hypervisor and guest VMs to maintain data confidentiality, integrity, and availability.
Virtual machines are secured by protecting the following key components:
1. Virtual Machine Monitor (VMM) / Hypervisor
• The hypervisor is the software layer that manages VMs and hardware resources.
 • If compromised, an attacker can control all guest VMs on a server.
• Types of Hypervisors:
o Type 1 (Bare-metal): Runs directly on hardware (e.g., VMware ESXi, Microsoft Hyper-V, Xen).
o Type 2 (Hosted): Runs on a host OS (e.g., VirtualBox, VMware Workstation).
• Security Concern: Hypervisors have privileged access to the system and are prime targets for attackers.
2. Guest Virtual Machines
• Each VM operates independently and may run a different OS.
• Security Concern: A compromised VM can attack the host system or other VMs (VM escape attacks).
3. Virtual Networking
• Virtual switches and routers manage traffic between VMs.
• Security Concern: Misconfigured virtual networks can expose VMs to external attacks.
4. Virtual Storage
• Cloud-based storage (e.g., Amazon S3, Google Cloud Storage) is used to store VM data.
• Security Concern: Data exposure or loss due to misconfigured access controls.
Common Virtual Machine Security Threats
NIST security group distinguishes two groups of threats, hypervisor-based and VM-based.
Hypervisor-based threats:
1. Starvation of resources and denial of service for some VMs
Probable causes:
(a) badly configured resource limits for some VMs.
(b) a rogue VM with the capability to bypass resource limits set in hypervisor.
2. VM side-channel attacks
Probable causes:
(a) lack of proper isolation of inter-VM traffic due to misconfiguration of the virtual network residing
in the hypervisor.
(b) limitation of packet inspection devices to handle high-speed traffic.
(c) presence of VM instances built from insecure VM images.
3. Buffer overflow attacks
VM-based threats:
1. Deployment of rogue or insecure VM
Unauthorized users may create insecure instances from images or may perform unauthorized
administrative actions on existing VMs.
Probable cause: improper configuration of access controls on VM administrative tasks such as instance
creation, launching, suspension, re-activation and so on.
2. Presence of insecure and tampered VM images in the VM image repository
 Probable causes:
(a) lack of access control to the VM image repository.
(b) lack of mechanisms to verify the integrity of the images, e.g., digitally signed image.
Privilege Escalation Attacks
• Attackers exploit vulnerabilities to gain higher-level privileges on a VM or hypervisor.

Question No: 4) Explain reputation system design options

Source: Distributed and Cloud Computing – Chapter 4: Cloud Security and Trust Management → 4.6.4
Reputation Systems for Clouds
Question No: 4
Question:
Explain reputation system design options.
Answer:
Reputation System Design Options
Reputation-based trust management and techniques for securing P2P and social networks could be
merged to defend data centers and cloud platforms against attacks from the open network.
A centralized reputation system is easier to implement, but demands more powerful and reliable server
resources; a distributed reputation system is much more complex to build. Distributed systems are more
scalable and reliable in terms of handling failures. At the second tier, reputation systems are further classified
by the scope of reputation evaluation. User-oriented reputation systems focus on individual users or agents.
Most P2P reputation systems belong to this category. In data centers, reputation is modeled for the resource
site as a whole. This reputation applies to products or services offered by the cloud.
Commercial reputation systems have been built by eBay, Google, and Amazon in connection with the
services they provide. These are centralized reputation systems.
Distributed reputation systems are mostly developed by academic research communities.
Aberer and Despotovic have proposed a model to manage trust in P2P systems.
The Eigentrust reputation system was developed at Stanford University using a trust matrix approach.
The PeerTrust system was developed at Georgia Institute of Technology for supporting e-commerce
applications.
The PowerTrust system was developed at the University of Southern California based on Power law
characteristics of Internet traffic for P2P applications.
Vu, et al. proposed a QoS-based ranking system for P2P transactions.
Design options of reputation systems:
• Centralized User-oriented
• Centralized Data center-based
• Distributed User-oriented
• Distributed Data center-based

Question No: 5) Summarize cloud data encryption and challenges in data encryption
 CLOUD DATA ENCRYPTION
Introduction to Cloud Data Encryption
• Governments, corporations, and users are concerned about storing sensitive data on public clouds.
• Encryption is the primary solution for protecting outsourced data.
• Cloud service providers (CSPs) offer encryption services, e.g., AWS Key Management Service (KMS),
which integrates with services like EBS, S3, RDS, Redshift, etc.
• Encryption SDKs are available for developers to enhance security in cloud applications.
Foundations of Cryptography for Cloud Security
1. CSP Encryption Offerings
Amazon AWS Key Management Service (KMS):
1. Creates and manages encryption keys.
2. Integrated with AWS services: EBS, S3, RDS, Redshift, WorkMail, Elastic Transcoder.
Research & Cryptographic Foundations
• RSA Cryptosystem (1978): Basis of public-key cryptography.
• Paillier Cryptosystem (1999):
o Uses composite residuosity classes (factoring large numbers).
o Supports homomorphic properties for secure computation.
• Fully Homomorphic Encryption (FHE) (2009, Craig Gentry, Stanford University):
1. Allows computation on encrypted data without decryption.
2. Significant breakthrough in privacy-preserving cloud computing.
Homomorphic Encryption
• Ensures that computations on encrypted data yield the same results as operations on plaintext data.
• Allows arithmetic and logic operations without decrypting data.
• Key Benefit: Data remains encrypted during processing, eliminating the decryption vulnerability.
Searchable Encryption for Cloud Databases
Solutions:
• Order-Preserving Encryption (OPE): OPE preserves order among encrypted numeric values, enabling
range queries.
• Searchable Symmetric Encryption (SSE): SSE enables keyword-based search without decrypting the
entire database.
Threats to Private Cloud Data
Threats:
• External attacks: Hackers exploiting vulnerabilities in CSP infrastructure.
• Internal threats: Malicious insiders accessing sensitive data.
• Network attacks: Man-in-the-middle attacks during data transfer.
 Defensive Measures:
• Strong encryption before storage (AES, RSA, ECC, FHE).
• Controlled access via cryptographic key management.
• Secure multi-party computation for data processing.
CHALLENGES IN DATA ENCRYPTION
1. Performance Issues
• FHE remains computationally expensive.
2. Search Optimization
• Improved SSE methods are needed for efficiency.
3. Privacy-Preserving Computation
• Secure enclaves and zero-knowledge proofs can enhance cloud security.
4. Regulatory Compliance
• Encryption strategies must align with laws like GDPR, HIPAA, and PCI-DSS.
5. Cloud data encryption is essential for securing sensitive information.
6. Ongoing research aims to balance security, efficiency, and compliance.
7. Organizations must implement robust cryptographic techniques to mitigate security risks in cloud
environments.

Question No: 6
Write a note on cloud security defense strategies.

Answer:
Cloud Security Defense Strategies
Virtualization enhances cloud security. But VMs add an additional layer of software that could become a
single point of failure. With virtualization, a single physical machine can be divided or partitioned into
multiple VMs (e.g., server consolidation). This provides each VM with better security isolation and each
partition is protected from DoS attacks by other partitions. Security attacks in one VM are isolated and
contained from affecting the other VMs. VM failures do not propagate to other VMs. The hypervisor provides
visibility of the guest OS, with complete guest isolation. Fault containment and failure isolation of VMs
provide a more secure and robust environment.
Physical and Cyber Security Protection at Cloud/Data Centers:
1. Secure data centers and computer buildings
Choose hazard-free location, enforce building safety. Avoid windows, keep buffer zone around the
site, bomb detection, camera surveillance, earthquake-proof, etc.
2. Use redundant utilities at multiple sites
Multiple power and supplies, alternate network connections, multiple databases at separate sites,
data consistency, data watermarking, user authentication, etc.
3. Trust delegation and negotiation
 Cross certificates to delegate trust across PKI domains for various data centers, trust negotiation
among certificate authorities (CAs) to resolve policy conflicts.
4. Worm containment and DDoS defense
Internet worm containment and distributed defense against DDoS attacks to secure all data centers
and cloud platforms.
5. Reputation system for data centers
Reputation system could be built with P2P technology; one can build a hierarchy of reputation
systems from data centers to distributed file systems.
6. Fine-grained file access control
Fine-grained access control at the file or object level; this adds to security protection beyond firewalls
and IDSes.
7. Copyright protection and piracy prevention
Piracy prevention achieved with peer collusion prevention, filtering of poisoned content,
nondestructive read, alteration detection, etc.
8. Privacy protection
Uses double authentication, biometric identification, intrusion detection and disaster recovery,
privacy enforcement by data watermarking, data classification, etc.

Question No: 7
Explain anomaly detection techniques in cloud.

Answer:
Anomaly Detection Techniques in Cloud
Data security is the weakest link in all cloud models. We need new cloud security standards to apply
common API tools to cope with the data lock-in problem and network attacks or abuses. The IaaS model
represented by Amazon is most sensitive to external attacks.
Security threats may be aimed at VMs, guest OSes, and software running on top of the cloud. IDSes
attempt to stop these attacks before they take effect. Both signature matching and anomaly detection can be
implemented on VMs dedicated to building IDSes.
Signature-matching IDS technology is more mature, but require frequent updates of the signature
databases. Network anomaly detection reveals abnormal traffic patterns, such as unauthorized episodes of TCP
connection sequences, against normal traffic patterns. Distributed IDSes are needed to combat both types of
intrusions.
Distributed Defense against DDoS Flooding Attacks
A DDoS defense system must be designed to cover multiple network domains spanned by a given
cloud platform. These network domains cover the edge networks where cloud resources are connected. DDoS
attacks come with widespread worms. The flooding traffic is large enough to crash the victim server by buffer
overflow, disk exhaustion, or connection saturation.
The flooding traffic flows essentially with a tree pattern. Successive attack-transit routers along the
tree reveal the abnormal surge in traffic. This DDoS defense system is based on change-point detection by all
routers. Based on the anomaly pattern detected in covered network domains, the scheme detects a DDoS
attack before the victim is overwhelmed.
Question:
Explain access control and identity access management.

Answer:
Access Control
The authorization is a process to exercise access control of shared resources. Decisions can be made
either at the access point of service or at a centralized place. Typically, the resource is a host that provides
processors and storage for services deployed on it. Based on a set predefined policies or rules, the resource
may enforce access for local services. The central authority is a special entity which is capable of issuing and
revoking policies of access rights granted to remote accesses.
The authority can be classified into three categories:
• Attribute authorities issue attribute assertions.
• Policy authorities issue authorization policies.
• Identity authorities issue certificates.
The authorization server makes the final authorization decision.
Identity Access Management
Here are several security features desired in a secure cloud:
• Effective user identity management and data-access management
• Single sign-on and single sign-off to reduce security enforcement overhead
• Established trust between users and providers through SLAs and reputation systems
• Protection of sensitive and regulated information in a shared environment
Government risk management and compliance, identity and access management, virtual machines
(VMs), patch management are security measures deployed at various cloud operating levels.

Question: Explain the major security concerns and risks faced by cloud users.

Major Security Concerns and Risks Faced by Cloud Users

1. Unauthorized Access & Data Theft
• Data in storage is more vulnerable than data in transit or during processing.
• Insider threats: Rogue employees at CSPs can steal or misuse sensitive data.

2. Data Lifecycle & Control Issues

• Users have no control over actual data deletion.
• CSPs automatically back up data without user consent.
• Risks:
o Deleted records might still exist in backups.
o Attackers could recover residual data.

3. Lack of Standardization & Interoperability

• No global security standards for cloud computing.
 • Unanswered questions:
o How to recover data if the CSP shuts down?
o What happens if prices increase unexpectedly?
o How difficult is switching CSPs?

4. Auditing & Compliance Challenges

• Full security audits on cloud infrastructure are nearly impossible.
• Legal compliance issues:
o Data laws differ across countries.
o Users don’t know where data is stored.

5. Emerging Threats from Autonomic Computing

• Autonomic features (self-repair, self-optimization) introduce new vulnerabilities:
o Harder to track and investigate security breaches.
o Automated systems may fail unpredictably.

6. Multi-Tenancy Security Concerns

• Shared cloud environments → Data breaches affect multiple users.

• Example: A hacked database can expose millions of user records.

7. Legal & Jurisdiction Issues

• Cloud data centers exist in multiple countries.
• Unclear jurisdiction:
o Which country's laws apply?
o What about data that crosses multiple borders?
• Data outsourcing risks:
o CSPs may subcontract data handling, making security compliance difficult.
o Example: Microsoft subpoenaed to provide Hotmail user emails.

8. Traditional Security Threats

• Increased Impact: Due to the large user base and shared resources.
• Responsibility Gaps: Unclear boundaries of security responsibility between the cloud provider and the
user.
• Key Attack Vectors:
 o Distributed Denial of Service (DDoS) attacks → Overloading cloud services to block legitimate
access.

o Phishing → Tricking users into providing sensitive credentials.

o SQL Injection → Exploiting web applications to manipulate databases.

o Cross-Site Scripting (XSS) → Injecting malicious scripts into web pages.

• Authentication & Authorization Risks:
o Assigning different privilege levels to enterprise users is complex.
o Merging internal security policies with cloud security models is challenging.

9. System Availability Threats

• Disruptions can be caused by:
o System failures, power outages, or cyberattacks.

o Data lock-in → Customers may be unable to move data when needed.

o Phase transitions in complex cloud systems → Unexpected failures due to rapid demand shifts.

o Unverified application results → Users cannot always trust the accuracy of cloud computations.

10. Third-Party Data Control Risks

• Lack of Transparency:
o Users do not have full visibility into how data is handled.
o Cloud providers may subcontract services to untrusted third parties.
• Data Loss Risks:
o Poor storage quality or hardware failures can lead to irretrievable data loss.
o Legal challenges in proving whether cloud data has been deleted.
• Cloud Provider Espionage:
o Cloud providers may access or misuse user data.
o Example: AWS Terms of Service disclaims liability for data breaches, losses, and service outages.

Question: Describe the process and significance of a Privacy Impact Assessment in cloud computing.

Privacy Impact Assessment (PIA) in Cloud Computing

Definition
• PIA is a tool used to evaluate privacy risks in information systems.

Significance of Privacy Impact Assessment (PIA)

Purpose
 • Identify and address privacy concerns before system deployment.
• Ensure compliance with legal regulations.
• Conducted by governments, corporations, and CSPs.
• Required in some countries for public sector IT projects.

Process of Privacy Impact Assessment (PIA)

PIA Report Components
1. Project Information
• Description of data collection and processing.
2. Privacy Risks
• Identification of vulnerabilities.
3. Stakeholders
• Who handles and accesses data?
4. Security & Transparency
• How data is protected and disclosed.
5. Cross-Border Data Flows
• Evaluating the legality of international data transfers.

PIA Knowledge Base (KB)

• Maintained by domain experts.
• Uses questionnaires and rule-based systems to identify risks.

Automated PIA Tools

• Web-based tools can generate automated privacy risk reports.
• Some tools incorporate AI-based assessments.

Question No.: 3
Question: Discuss various encryption techniques used for securing data in the cloud.

Various Encryption Techniques Used for Securing Data in the Cloud

Introduction to Cloud Data Encryption
• Governments, corporations, and users are concerned about storing sensitive data on public clouds.
• Encryption is the primary solution for protecting outsourced data.
• Cloud service providers (CSPs) offer encryption services, e.g., AWS Key Management Service (KMS),
which integrates with services like EBS, S3, RDS, Redshift, etc.
• Encryption SDKs are available for developers to enhance security in cloud applications.
 1. RSA Cryptosystem (1978)
• Basis of public-key cryptography.

2. Paillier Cryptosystem (1999)

• Uses composite residuosity classes (factoring large numbers).
• Supports homomorphic properties for secure computation.

3. Homomorphic Encryption
• Ensures that computations on encrypted data yield the same results as operations on plaintext data.
• Concept: A homomorphic function f(a) on encrypted data maintains structure-preserving properties.
• Allows arithmetic and logic operations without decrypting data, closing the vulnerability window.
• Challenge: Data must be decrypted for processing, creating a vulnerability window.
• Solution: Homomorphic encryption allows computations on encrypted data without decryption.
• Concept:
o Homomorphism is a structure-preserving map between two algebraic structures.
o If f(·) is a homomorphic function, then:

▪ f(a ⊕ b) = f(a) ⊗ f(b)

▪ This means performing an operation on encrypted values is equivalent to performing the operation
on plain values and then encrypting the result.
• Key Benefit: Data remains encrypted during processing, eliminating the decryption vulnerability.
• Challenges: High computational overhead; FHE currently impractical for large-scale cloud applications.

4. Fully Homomorphic Encryption (FHE)

• Major Breakthrough (Craig Gentry, 2009)
o Enables general computations on encrypted data.
o Solves the privacy problem in cloud computing.
• Challenges:
o Extremely slow compared to plaintext processing.
o Processing overhead increases by orders of magnitude.
• Example:

▪ Early FHE implementations took ~6 minutes per operation.

▪ Optimized versions reduced this to ~1 second.

5. Order-Preserving Encryption (OPE)
• Goal: Encrypt numeric data while preserving ordering to allow efficient range queries.
• Method:
o Maps a range of plaintext values (1, ..., M) into a much larger ciphertext range (1, ..., N).
o Ensures encrypted values maintain relative order (but not actual values).
• Example:
o OPE transforms values while preserving order:

▪ Original: 10 < 20 < 30

▪ Encrypted: X1 < X2 < X3 (unknown values, but still ordered).

• Implementation:
o Uses a negative hypergeometric distribution (NHG).
o Encrypts values via binary search and probabilistic assignments.
• Advantage:
o Enables efficient range queries without decrypting data.
• Limitation:
o Trade-off between security and searchability (attackers may infer order).

6. Searchable Symmetric Encryption (SSE)

• Use Case: Secure searches on encrypted cloud databases.
• Principle:
o Client stores only a cryptographic key.

o Client encrypts query → sends to cloud → gets encrypted result → decrypts locally.
• Benefits:
o Protects against data leaks by encrypting queries & responses.
o Prevents explicit data exposure to the cloud provider.
• Potential Weakness:
o Query pattern leakage (attackers may infer patterns).
• Advancements:
o SSE now supports:
▪ Boolean queries

▪ Multi-keyword searches

▪ Phrase & substring searches

▪ Wildcard & range searches

 7. Encryption-based Defensive Measures
• Strong encryption before storage (AES, RSA, ECC, FHE).
• Controlled access via cryptographic key management.
• Secure multi-party computation for data processing.

)
Question No.: 4
Question: Explain how database services are secured in a cloud-based system.

Security of Database Services in a Cloud-Based System

Database-as-a-Service (DBaaS) is a key component of cloud computing, offering users scalable, managed
database solutions. However, delegating database management to cloud providers raises serious security
concerns regarding data integrity, confidentiality, and availability.

Entities Involved in DBaaS Security

1. Data Owners
• Individuals or organizations that generate and own the data.
2. Database Users
• Clients accessing the DBaaS for queries and data retrieval.
3. Cloud Service Providers (CSPs)
• The companies that host and manage cloud databases.
4. Third-Party Auditors (TPAs)
• Independent entities that verify compliance and security.

Security Measures for DBaaS

1. Strong Authentication and Access Control
• Implement multi-factor authentication (MFA).
• Enforce role-based access control (RBAC) to limit user privileges.

2. Data Encryption and Secure Storage

• Encrypt data at rest and in transit using strong cryptographic standards.
• Use homomorphic encryption to allow computations on encrypted data without decryption.

3. Secure Backup and Disaster Recovery

• Maintain regular backups with version control.
• Implement geo-redundancy to ensure data availability in case of disasters.
 4. Auditing and Monitoring
• Enable log tracking for access and modification records.
• Utilize anomaly detection systems to detect suspicious database activity.

Major Security Threats to DBaaS

1. Data Integrity and Confidentiality Risks
• Unauthorized Access - Weak authentication and access control mechanisms expose databases to
unauthorized users.
• Insider Threats - Superusers with excessive privileges can manipulate, leak, or delete sensitive data.
• Encryption Issues - Inconsistent use of encryption or weak encryption keys can make stored data
vulnerable.

2. External Attacks
• SQL Injection - Attackers manipulate database queries to gain unauthorized access or modify data.
• Man-in-the-Middle (MitM) Attacks - Interception of data transmitted between users and DBaaS.
• Side Channel Attacks - Exploiting patterns in database access to infer confidential information.

3. Multi-Tenancy Risks
• Data Leakage - Different users sharing the same physical infrastructure increases the risk of data
leaks.
• Illegal Data Recovery - Improperly sanitized storage devices can allow retrieval of previously deleted
data.

4. Availability Risks
• Denial-of-Service (DoS) Attacks - Overloading the database service to make it inaccessible.
• Resource Exhaustion - Inefficient allocation of database resources can lead to system crashes.

Question No.: 6
Question: Explain how virtual machines are secured in cloud environments.

Virtual Machine Security in Cloud Environments

Definition of Virtual Machine Security
VM security refers to the protection of virtualized environments from unauthorized access, data
breaches, malware attacks, and system vulnerabilities. It involves securing both the hypervisor and guest VMs
to maintain data confidentiality, integrity, and availability.

Importance of VM Security
 • Ensures data confidentiality and prevents unauthorized access.
• Protects shared resources in multi-tenant cloud environments.
• Prevents hypervisor attacks that can compromise multiple VMs.
• Safeguards virtual networks from malware and lateral attacks.
• Supports regulatory compliance (e.g., GDPR, HIPAA, ISO 27001).

Key Components of Virtual Machine Security

1. Virtual Machine Monitor (VMM) / Hypervisor
• The hypervisor is the software layer that manages VMs and hardware resources.
• If compromised, an attacker can control all guest VMs on a server.
• Types of Hypervisors:
o Type 1 (Bare-metal): Runs directly on hardware (e.g., VMware ESXi, Microsoft Hyper-V, Xen).
o Type 2 (Hosted): Runs on a host OS (e.g., VirtualBox, VMware Workstation).
• Security Concern: Hypervisors have privileged access to the system and are prime targets for
attackers.

2. Guest Virtual Machines

• Each VM operates independently and may run a different OS.
• Security Concern: A compromised VM can attack the host system or other VMs (VM escape attacks).

3. Virtual Networking
• Virtual switches and routers manage traffic between VMs.
• Security Concern: Misconfigured virtual networks can expose VMs to external attacks.

4. Virtual Storage
• Cloud-based storage (e.g., Amazon S3, Google Cloud Storage) is used to store VM data.
• Security Concern: Data exposure or loss due to misconfigured access controls.

Common Virtual Machine Security Threats

NIST security group distinguishes two groups of threats, hypervisor-based and VM-based.
Hypervisor-based threats
1. Starvation of resources and denial of service for some VMs
Probable causes:
(a) badly configured resource limits for some VMs.
 (b) a rogue VM with the capability to bypass resource limits set in hypervisor.
2. VM side-channel attacks
Probable causes:
(a) lack of proper isolation of inter-VM traffic due to misconfiguration of the virtual network
residing in the hypervisor.
(b) limitation of packet inspection devices to handle high-speed traffic.
(c) presence of VM instances built from insecure VM images.
3. Buffer overflow attacks

VM-based threats
1. Deployment of rogue or insecure VM
Probable cause:
Improper configuration of access controls on VM administrative tasks such as instance creation,
launching, suspension, re-activation and so on.
2. Presence of insecure and tampered VM images in the VM image repository
Probable causes:
(a) lack of access control to the VM image repository.
(b) lack of mechanisms to verify the integrity of the images, e.g., digitally signed image.

Privilege Escalation Attacks

• Attackers exploit vulnerabilities to gain higher-level privileges on a VM or hypervisor.

Question No.: 8
Question: What is XOAR? Discuss its role in providing trusted hypervisor support in cloud security.

XOAR – Breaking the Monolithic Design of the Trusted Computing Base (TCB)
Introduction
• Xoar is a modified version of Xen designed to enhance system security.
• Security model assumptions:
o System is professionally managed.
o Only system administrators have privileged access.
o Administrators are trusted and do not have incentives to violate user trust.
• Sources of Security Threats:
o Malicious guest VMs attempting to compromise:

▪ Data integrity.

▪ Confidentiality of other guest VMs.

 ▪ Guest VM execution processes.
o Bugs in initialization code of the management VM.
• Key Innovation:
o Xoar follows microkernel design principles to increase security.
o Unlike Xen, Xoar is modular, explicitly defining exposure risks.

Role of Xoar in Providing Trusted Hypervisor Support in Cloud Security

Design Goals
1. Maintain the functionality of Xen.
2. Ensure transparency with existing management and VM interfaces.
3. Tightly control privileges – each component should only have the minimum required privileges.
4. Minimize component interfaces – reduce possible attack vectors.
5. Eliminate unnecessary sharing.
6. Explicitly define sharing to enable proper logging and auditing.
7. Reduce attack exposure window – minimize the time components are active.

Xoar Component Architecture

Xoar redesigns Xen into modular components and classifies them into four types:
1. Permanent Components
• XenStore-State – Maintains the state of the system.

• Critical component → Must be hardened against attacks.

2. Self-Destructing Components
• PCIBack – Virtualizes access to PCI bus configuration.
• Bootstrapper – Coordinates hardware initialization and booting.

• Removed before any user VM starts → Reduces security risks.

3. Components Restarted on Request
• XenStore-Logic – Manages system state changes.
• Toolstack – Handles VM management requests.
• Builder – Creates and initializes guest VMs.
• Minimizes exposure time to attacks.
4. Components Restarted on Timer
• BlkBack – Exports physical storage drivers.
• NetBack – Exports network drivers.
• Restarts periodically to ensure security freshness.
 Security Enhancements
• Most privileged components (PCIBack and Bootstrapper) are removed after booting.
• Builder (VM initialization) is small – Only 13,000 lines of code.
• XenStore is split into two parts:

• XenStore-Logic → Handles changes.

• XenStore-State → Maintains records and includes a small monitor module for security checks.
• Guest VMs only share essential services.
• Users can choose to share service VMs only with their own VMs (tagging system).
• Benefit: Reduces security risks by restricting unnecessary interactions between components.

Secure Auditing and Logging

• Every VM action (start, stop, delete, restart) is recorded.
• Audit logs are stored on a separate secure server.
• Append-only logging mechanism prevents tampering.

Enhancing Security with Snapshots

• Service VMs take a snapshot when ready to process a request.
• Snapshots of components are taken immediately after initialization and before interacting with other
components or guest VMs.
• Implemented using "Copy-on-Write" (COW) mechanism.
• Ensures VMs return to a known good state without full reboot overhead.
• Prevents persistence of malware or unauthorized modifications.