duplicability of VMs (A.2), single target for attack
or failure (A.3), complex or inefficient provisioning
(A.4), non-compliance with licensing or service
level agreements (A.5), and audit/event logging
(A.6).
5.2 Logical Access
The logical access virtualization risks and the
recommendations for mitigation of these risks
are detailed in Table 3. Server and hardware
consolidation lead to the collapsing of domain,
Table 2: Security, administration and control risks and mitigating controls.
Ref Risk Description of mitigating control
A.1
Dynamic migration and the seamless portability of VMs between hosts
leading to inadequate change management, lack of visibility contributing
to inadequate VM tracking and an increased volume of risk exposures,
software licensing violations and misconfigurations (VMware Inc., 2006,
Ormandy, 2007, Hoesing, 2006, Enterprise Management Associates,
2008, Campbell and Jeronimo, 2006, Barrett, 2008).
Management reviews and approves the configuration and
implementation of information security tools and techniques
ensuring appropriate setup of clusters so that VMs are migrated
within secure groups and between servers with the same
infrastructure and security, and the implementation of monitoring
and management tools proving visibility to all VMs and VM
configuration (i.e. V-Tracker) (Ormandy, 2007, Gardner, 2009,
Baldwin et al., 2008).
A.2
Duplicability of VMs (creating copies of VMs by using templates or
cloning existing VMs) leading to replication of insecure security setup
based on the “templates” or cloning, increased server sprawl,
misconfigurations and inappropriate access to the cloned or newly created
VMs (VMware Inc., 2006, Ormandy, 2007, Hoesing, 2006, Enterprise
Management Associates, 2008, Campbell and Jeronimo, 2006, Barrett,
2008).
Changes to the virtual environment should be documented, tested
and approved by the appropriate level of management prior to
implementation. This includes the following change scenarios:
cloning or copying of VMs to ensure adequate and secure
configuration, controls ensuring adequate and secure setup of
VM “templates” including regular updating and patching, and
unauthorized attempts to copy or clone VMs should be detected
to ensure that sensitive information is not exposed outside secure
and authorized environments.
A.3
If the host machine is experiencing problems or if compromised, it could
have a direct impact on the virtual machine(s) being hosted. The host is
perceived as a single target for attack or failure (Hoesing, 2006,
Campbell and Jeronimo, 2006).
Security policies and minimum baseline security standards are
implemented and processes are in place to regularly review
configurations and the secure setup of the virtualization layers
(hosts) (Ormandy, 2007, Gartner Executive Programs (EXP),
2010, Baldwin et al., 2008).
A.4
Complex or inefficient provisioning due to manual procedures or lack of
adequate tools leading to errors or misconfigurations, and possible could
inhibition of the productivity of the administrators (VMware Inc., 2006,
Strom, 2008, Sgallari, 2009, Senft and Gallegos, 2009, Robb, 2008,
Newman, 2009, Killalea, 2008, Humphreys and Grieser, 2006, Hoesing,
2006, Hernandez, 2009, Gardner, 2009, Enterprise Management
Associates, 2008, Campbell and Jeronimo, 2006, Bass, 2009).
The following controls should be in place: adequate and secure
virtualization environment configuration based on approved
standards and policies, adherence to change management policies
and procedures for VMs and virtual environments, and
independent monitoring and control mechanisms to assist with
provisioning requests (Ormandy, 2007, Gardner, 2009, Baldwin
et al., 2008).
A.5
Complexities such as different virtualization vendors, multiple platforms
and lack of visibility and asset tracking could increase company risk of
non-compliance with licensing or service level agreements (Enterprise
Management Associates, 2008, Campbell and Jeronimo, 2006) as well as
more difficulties concerning security, management and control (VMware
Inc., 2006, Senft and Gallegos, 2009, Gardner, 2009, Enterprise
Management Associates, 2008, Barrett, 2008).
Management monitors and ensures that information system
service level and licensing agreements allow for all virtualization
components and requirements (Campbell and Jeronimo, 2006).
A.6
Audit/event logging was cited as a current barrier to virtualization
implementation, providing the complexities of the virtual environment.
The risk augments even further when management and monitoring tools
and controls are not adequate or efficient (VMware Inc., 2006, Enterprise
Management Associates, 2008).
Security tools are implemented to record security events (e.g.
security violation, unauthorized attempts to access VMs) for the
virtual environment. Reports are regularly reviewed and a root
cause established where applicable (Baldwin et al., 2008).
Table 3: Logical access risks and mitigating controls.
Ref Risk Description of mitigating control
B.1
A risk conveyed through server and hardware consolidation is the
collapsing of domain, security and network administrator roles. The
virtual administrator is now responsible for the entire virtual
environment, creating possible segregation of duty problems. To
further augment this risk, segregation of duty problems could also lead
to human error (as a result of not being trained properly or not
encompassing the required skill), the intentional or unintentional
disruption of critical services, and misconfiguration of VMs
(Ormandy, 2007, Hoesing, 2006, Campbell and Jeronimo, 2006).
Roles and responsibilities related to virtualization security
administration are defined and privileged access limited to
appropriate personnel based on approval from management.
Privileged access is logged and reviewed on a regular basis
(Ormandy, 2007, Hoesing, 2006, Campbell and Jeronimo, 2006,
Baldwin et al., 2008).
B.2
Server and hardware consolidation lead to the reduction of access
controls. Should an attacker gain unauthorised access to the virtual
host, access to all VMs on that host are compromised. Also, a VM
image is essentially a file containing data. The data could therefore be
copied and run in an unsecure environment circumventing security
controls and providing a means for unauthorized access to data
(Ormandy, 2007, Hoesing, 2006, Campbell and Jeronimo, 2006,
Berman, 2009).
Logical security tools and techniques are implemented to restrict
access to the virtualization layer, virtual hard disks, VM images,
data storage, VM backups, and VM management and monitoring
tools (Ormandy, 2007, Hoesing, 2006, Campbell and Jeronimo,
2006, Baldwin et al., 2008).
CLOSER 2011 - International Conference on Cloud Computing and Services Science
20