Skip to main content

Security & Compliance: Accountability a big issues in Virtual Infrastructure

No you don't have to panic here. you have all the staff in place to take over these replacing responsibilities (note, I didn't say additional since they will eventually have to let go of a lot of old habits and practices, it that offers some relief).

Your Security staff, SOX team or whatever you have in place and/or other folks are the ones who must define standards and frameworks that are compliant to the typical security audit scenarios. Obviously this can also be a means to bring a lot of folks from other domains to participate in the whole "virtualization party" (as it is often, sarcastically mentioned by the guys who have no idea who these "virtualization team" is) actively.

Security is undoubtedly a very improtant arena, in the older world, it just didn't take off. I still remember when I was pushing , that was 7 years back, some auditing practices that could give us more granular control on operational FGAC on the databases, people just looked at me like "Are you nuts?". I found out that there were no security standards and if they existed they were never put into practice.

Although I still believe that we are a bit too late with the security push into the virtualization party, this is fortunately being taken very seriously while we move towards the Cloud Computing discussions, which I often call the Virtualization 4.0.

Anyways, this survey is definitely interesting:



Despite differences in organizational size and structure, and the inevitability that the terms “ensuring” and “responsibility” can mean different things to some people, a greater consensus should be expected on the questions of who within IT is answerable for security, change control and compliance on virtual servers. Even across respondents representing Operations and Security, neither group overwhelmingly considered themselves responsible.
Source

Comments

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus

OS Virtualization comparison: Parallels' Virtuozzo vs the rest

Virtuozzo's main differentiators versus hypervisors center on overhead, virtualization flexibility, administration and cost. Virtuozzo requires significantly less overhead than hypervisor solutions, generally in the range of 1% to 5% compared with 7% to 25% for most hypervisors, leaving more of the system available to run user workloads. Customers can also virtualize a wider range of applications using Virtuozzo, including transactional databases, which often suffer from performance problems when used with hypervisors. On the administration side, customers need to manage, maintain and secure just a single OS instance, while the hypervisor model requires customers to manage many OS instances. Of course, the hypervisor vendors have worked hard to automate much of this process, but it still requires more effort to manage and maintain multiple operating systems than a single instance. Finally, OS virtualization with Virtuozzo has a lower list price than the leading hypervisor for comme...