+ All Categories
Home > Documents > T12: Virtualization: IT Audit and Security Perspectives ·  · 2010-10-19Virtualization: IT Audit...

T12: Virtualization: IT Audit and Security Perspectives ·  · 2010-10-19Virtualization: IT Audit...

Date post: 22-May-2018
Category:
Upload: duongnguyet
View: 213 times
Download: 1 times
Share this document with a friend
19
T12: Virtualization: IT Audit and Security Perspectives Jason Chan, VMware
Transcript

T12: Virtualization: IT Audit and Security Perspectives

Jason Chan, VMware

1

Virtualization: IT Audit and Security PerspectivesSecurity Perspectives

Jason Chan

Director of Security, VMwarey,

Agenda

o Background and Disclaimers

o Virtualization Basics and Business Drivers

o Audit and Security Topics of Interest

o New Attack Vectors

o Architectural Options and Opportunities

2

o Summary

2

Background and Disclaimers

o I work at VMware– In IT (not R&D or Marketing)

o Security consulting and audit background– @stake, Symantec, iSEC Partners

Presentation Focus

o x86 server virtualization– Application, desktop, storage virtualization

(while interesting) are not covered

o Not VMware-specific

o Not comprehensive

o What is interesting about server o What is interesting about server virtualization from a security and IT audit perspective?

4

3

Virtualization Basics and Business Drivers

5

Server Virtualization in 30 secs

• Virtualization: Separation of the service request from the underlying physical service delivery

• Abstraction of hardware to allow multiple “virtual machines” to co-exist on single physical system

• The hypervisor manages VM &

6

hardware interaction

4

Common Virtualization Terminology

o Host

o Guest

o Hypervisor Types– Type 1/Bare Metal/Non-Hosted/Native

– Type 2/Hosted

P i t li tio Paravirtualization

o VM Migration

7

Server Virtualization in the Real World

o General implementation order:– Dev and Test

– LOB

– Production/Mission Critical

o Overall workload virtualization is estimated around 16% as of 10/2009around 16% as of 10/2009

o Expected to be ~50% by 2012

8

5

Business Drivers: Cost

o Do more with lessC li d i i i– Centralize administration

– Drive a higher server/admin ratio

o Hardware, space, and power– Consolidate and contain infrastructure

– Less hardware, fewer racks

– Lower power and cooling costs

Business Drivers: Agility

o Flexibility and ease of deployment and change

Simple provisioning– Simple provisioning

– Multiple OS on a single server

– Easily scale up, down, in, and out

o High availability – Simple clustering

L ti i d d t ilit f DR – Location-independent agility for DR

10

6

Mapping Business Drivers to Security and Audit Concerns

o Or, there’s no such thing as a free lunch

Business Benefit

Security and Audit Issues

11

Mapping Business Drivers to Security and Audit Concerns

Business Driverso Server consolidation

Concernso Management infrastructure

o Centralized administrationo Higher server/admin ratioo Quick provisioningo Simple reconfigurationo Multiple OS on single

platform

go SoD/RBACo “Physical” accesso Licensing complianceo Change managemento Capacity/SLA planningo Platform security,

o Agility across locationsy,

hardening & isolation

12

7

Audit and Security Topics

13

Segregation of Duties

o Hypervisor and virtualization infrastructure are new components to managenew components to manage

o Server, storage, network, and security duties are collapsed

o Critical considerations:– Role-mapping within IT– RBAC capabilities of virtualization platform

L d t l ( t d t t d)– Layered controls (prevent, detect, respond)o Unfortunately, often given short shrift because

of deployment patterns

14

8

Physical Security?!?

o Consider traditional data center controls in i t l t ta virtual context

– Cameras – prevent theft, monitor physical access

– Biometrics, guards, man traps – control physical access

– Locked racks – prevent theft of physical assets

15

Virtual Corollaries to Physical Security

o Virtual console– Accessible without respect to physical location– Accessible without respect to physical location– Protect with idle timeouts, access control

o Storage of virtual disks– “Theft” of a system possible without physical access– Maintain control of virtual machine files (including

templates and backups)

o “Rack and stack”– Rogue provisioning without data center access– Emphasize management infrastructure access controls

and monitoring

16

9

Change and Configuration Management

o Virtualization enables fast and highly automated provisioning and changeautomated provisioning and change– Responsibilities may be consolidated

o Licensing compliance can become an issue without adequate controls

o Process needs to keep pace to leverage advantages while managing risk

R ifi ti f r CMDB?– Ramifications for CMDB?o Emphasize both preventative and detective

controls

17

Capacity Management

o Virtual capacity is a new discipline for it d l bilit icapacity and scalability engineers

– Power, network, CPU, etc.

o Dynamic capabilities of virtual workloads puts increased importance on planning

o HA DR and planned maintenance can o HA, DR and planned maintenance can cause capacity issues if not properly addressed at design-time

10

Infrastructure Hardening

o Hypervisor/VMM system hardeningS it f d i i t ti d t o Security of administrative and support infrastructure– Service accounts, networking

o Management network isolation– Consolidation of functions makes this even

more critical

o Virtual network configuration

Platform Security

o Security characteristics and capabilities of i t li ti l tf d dyour virtualization platforms and vendors

o Software security quality

o Resource isolation across VMs– Memory, disk, CPU, network

R li it d tio Resource limits and reservations

o Management infrastructure– RBAC, monitoring, remote administration, APIs

11

Security Advantages and Opportunities

o Interesting options for control placement and implementationimplementation– Patching, firewalls, IPS, DLP, etc.

o Centralized view of resources– Management, monitoring, etc.

o Full system lifecycle management and visibility– Actions on system state are traceable– Decommissioning is auditable

o Templates provide new opportunities for configuration management and refresh

New Attack Vectors

22

12

VM Escape

o Considered “holy grail” of virtualization l itexploits

o “Escaping” through the virtualization layer to attack:– The host

– Other virtual machines (out of band)Other virtual machines (out of band)

o Cloudburst– Presented at Black Hat 2009

23

Hyperjacking

o VMBRs (Virtual Machine Based Rootkits)

o Inserting a hypervisor underneath a running OS

o Can target a physical or virtual system

o Relies on hardware virtualization extensions

o Blue Pill, SubVirt, Vitriol

24

13

VM Migration Attacks

o HA/DR/maintenance feature

o Involves moving a VM across hardware– Server, cluster, storage

o Attacks involve sniffing, capturing, and/or modifying VM traffic during migration

25

Virtualization and Security Architecture

26

14

Traditional Architectural Drivers

Populations – Hi to Lo Trust• Employees

Environments – Hi to Lo Trust• Mission Critical

• Contractors/Consultants• Partners• Public• Competitors

• Intranet• Extranet• DMZ• Internet

These considerations are key drivers for:

27

• Security policy and standards

• Network design and segmentation

• Access controls

• Etc . . . 

All Physical (Traditional)

28

15

Virtualization Within Trust Zones

29

Virtualization Across Trust Zones

30

16

Fully Virtualized

31

What Considerations Arise?

o Degree of resource utilization

o Cost to acquire and operate

o Complexity of design

o Reliance on virtualization

o Manageability of environment

o The “right” answers depend on organizational capabilities and risk management approach

32

17

Comparison of Approaches

33

* For discussion purposes only – not to scale

Recommendations

o Understand:– Virtualization security concerns and possibilities

– How existing processes and controls can be leveraged and will need to be enhanced

– Security controls offered by your virtualization platforms

o Have the architectural conversations– Determine what’s organizationally appropriate

18

References

o http://www.gartner.com/it/page.jsp?id=1211813o http://www2.catbird.com/pdf/press/Catbird_ComputerTechnol

R i F b4 2009%5B1%5D dfogyReview_Feb4,2009%5B1%5D.pdfo http://www.vmware.com/files/pdf/dmz_virtualization_vmware_

infra_wp.pdfo http://www.virtualizationpractice.com/blog/?p=5726o http://www.blackhat.com/presentations/bh-usa-

09/KORTCHINSKY/BHUSA09-Kortchinsky-Cloudburst-PAPER.pdfo http://www.eecs.umich.edu/virtual/papers/king06.pdfo http://www vmware com/files/pdf/VMware paravirtualization po http://www.vmware.com/files/pdf/VMware_paravirtualization.p

dfo Martin Carbone, Wenke Lee, Diego Zamboni. “Taming

Virtualization”. IEEE Security & Privacy. Jan/Feb 2008.


Recommended