Posts Tagged ‘honeypot’

Update for windows Honey@home software

Friday, May 16th, 2008

Honey@home logoAn updated version of windows Honey@home has been released. The new version has been developed using the Microsoft .NET 2.0 framework. New features in this version include an installation wizard, a registration wizard, settings manager and automatic updating.

The application is available from the Honey@home website. Continue reading for more details on the new features.

Click to continue reading “Update for windows Honey@home software”

Eudaemon: Argos-like protection on the desktop

Tuesday, May 6th, 2008

“Essentially, Eudaemon is a ‘good spirit’ that possesses processes in order to protect them form evil.”

Despite all of the attractive properties of Argos and the various signature generators, we are still missing some attacks: those on the client-side. Honeypots have as a disadvantage that they mostly act like servers and wait for attackers to contact them. However, client-side attacks are on the rise. In such attacks, the client visits a malicious website and is infected by the content. Honeypots never see such attacks.

Moreover, the Argos honeypot only protects the exact configuration that it is actually running on top of its emulator. If the production machines have a slightly different configuration (e.g., a different version of the OS, applications, or plugins), Argos may miss attacks. So, ideally we would like to protect the `real’ machines.

In the Eudaemon project, some of the groundwork is done for implementing techniques to bring Argos-like honeypot technology to the desktop of normal users. In other words: client-side protection. This is a major challenge as the emulator that implements all the required instrumentation to detect attacks incurs a slowdown of a factor 15-20. As a result, running a desktop PC in instrumented mode constantly is probably not acceptable.

Instead, the idea is to take over running processes and force them to continue running in honeypot mode when needed or when possible. For instance, in the former case one may run a browser in honeypot mode when we click on an unknown URL in an email message. The browser is then protected against browser attacks by malicious server content. In the latter case, one may switch all of the user’s networking applications to honeypot mode when the machine is idle. For instance, we may switch to honeypot mode as a screensaver.

The mechanism for doing this is described in the Eudaemon paper presented at EUROSYS 2008 in Glasgow. [bibtex]

Argos version 0.4.0 released

Friday, March 14th, 2008

Finally, the long awaited port to QEMU 0.9.* series is here. Argos v0.4.0 is based upon QEMU v0.9.1.

Some useful changes follow:

version 0.9.1:

  • TFTP booting from host directory (Anthony Liguori, Erwan Velu)
  • Tap device emulation for Solaris (Sittichai Palanisong)
  • Monitor multiplexing to several I/O channels (Jason Wessel)
  • CPU model selection support (J. Mayer, Paul Brook, Herve Poussineau)
  • Read-only support for Parallels disk images (Alex Beregszaszi)
  • SVM (x86 virtualization) support (Alexander Graf)
  • Intel mainstone II board emulation (Armin Kuster)
  • VMware SVGA II graphics card support (Andrzej Zaborowski)

version 0.9.0:

  • Support for relative paths in backing files for disk images
  • Async file I/O API
  • New qcow2 disk image format
  • Support of multiple VM snapshots
  • Linux: specific host CDROM and floppy support
  • SMM support
  • Moved PCI init, MP table init and ACPI table init to Bochs BIOS
  • several x86 and x86_64 emulation fixes
  • Mouse relative offset VNC extension (Anthony Liguori)
  • PXE boot support (Anthony Liguori)
  • ‘-daemonize’ option (Anthony Liguori)

Additional changes, besides the port, include a double taintness check before executing a part of code to ensure attackers’ injected code is always detected at the moment it is first executed. The check is performed whenever a TB is scheduled to be executed, as well as within the translated code whenever EIP is modified. This is to cover TB chaining performed by QEMU to speed up emulation. In the future we might consider disabling chaining, if a single check offers a significant performance gain.

For more information on Argos visit: http://www.few.vu.nl/argos