Skip to main content

Bluelane continues to educate the industry on Virtual Security!



I have regular contact with Greg Ness (VP Marketing, BlueLane) and am amazed the amount of work these people put up besides their regular day jobs. I'm sure the Virtualization community has a lot of work to do before they have a fully secure Virtual Infrastructure. Good jobs.

Check out the latest podcast here.

Summary:

1. Introduction
2. Commoditized Virtualization
3. Key elements of virtualization
4. hypervisor gaining more functionality
5. VM Sprawl to laptops
6. VMotion can break firewall rules
7. Virtual Appliances
8. New threats to VMs
9. Patch Challenges
10. VirtualShield
11. Security at the Network level
12. VirtualShield sits between the hypervisor and the Virtual Machine
13. 0-Day protection
14. Fixing the root cause
15. Setting up VirtualShield
16. Integration with VirtualCenter
17. Customer Feedback
18. Hardware level security without the hardware
19. Closing
Labels:

Comments

Post a Comment

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
Post a Comment
Read more

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
Post a Comment
Read more