Skip to main content

Reflex VSA and Storm worm

Revisiting the Refelx VSA, which we evaluated in june last year.

The so-called “Storm worm” is a backdoor Trojan Horse botnet that creates a network of infected computers that can be issued commands by an external malicious operator.

“The Storm worm attacks are the most widespread and dynamic we’ve seen in the last two years,” said Hezi Moore, CTO of Reflex Security. “Enterprise employees are likely to have received numerous e-mails with phony invitations to e-cards and fake news bulletins that lead them to unfamiliar URL addresses that can potentially lead to their computer being infected with the malicious software known as the Storm worm.”

Recently, variants of the widespread Storm worm go beyond infecting physical networks, and can now detect two virtual environments: VMware and Microsoft's Virtual PC. If the Storm worm detects a virtual machine, it will bypass traditional host-based security systems by modifying its behavior, and restarting the system.

Reflex Security Stops Storm Worm
Reflex Security stops the storm worm through three different security mechanisms. First, Reflex VSA detects the e-card executable and blocks the infection before the e-card reaches the server. Second, Reflex VSA blocks any attempts to connect to an external malicious website. Third, the Reflex Security solution will thwart any attempt by the malicious website to exploit a browser to compromise the user’s system. Reflex VSA’s network discovery employs an anomaly behavior module which will detect frequent reboots of the worm and unusual behavior of the virtual machine.


Check out their news release.

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

Virtualization is hot and sexy!

If this does not convince you to virtualize, believe me, nothing will :-) As you will hear these gorgeous women mention VMware, Akkori, Pano Logic, Microsoft and VKernel. They forgot to mention rackspace ;-) virtualization girl video I'm convinced, aren't you? Check out their site as well!