Skip to main content

UC Berkeley chooses Firewire's "Virtual Victim" approach


When UC Berkeley learned of the FireEye 4200 appliance and its virtual victim machine security approach, a solution to their wireless security concerns was in sight. The University deployed FireEye 4200’s alongside the central wireless controllers to offer accurate, agent-less network malware control protecting the internal EECS network against zero-day, targeted malware that sought to take remote control over university and student computing resources.

In particular, FireEye offered

- Targeted malware security
- A network-based security approach
- Reliable, automated quarantines
- Easy deployment, use, & management

FireEye specializes on preventing self-propagating malware from spreading throughout the internal network. The FireEye Attack Confirmation Technology (FACT) engine uses virtual victim machines to analyze real-time network traffic flows pinpointing targeted malware and remote control attacks–all without relying on signatures or IT forensic analysis. The FACT engine enables the FireEye 4200’s unparalleled ability to accurately identify malicious attacks, including targeted attacks that seek to compromise and take over remote control of computing assets.


Interesting approach, this FACT technology. Take a look at it here.



This blog is carrying the news

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