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

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op