First off, thanks for the feedback -- here are a few responses to questions people have raised:
1. Why .Net? - We're not.big .Net fans either. If you read the whitepaper, you'll notice that we are expressly not concerned with developing the GUI. The goal is to extend a set of API's for rootkit detection that other tools can call into. The current GUI is only used to demonstrate this, and is written in .Net because that was the quickest way to slap a GUI together. However, point noted, we will look at developing frontends and interfaces using the MFC. However, obviously our priorities are on developing core detection technology.
2. Patents –We know that nobody can patent public domain material. What you see on the website is the PUBLIC RELEASE of Helios. There are indigenously developed unique techniques that are not in the public release. These will be made available as soon as we decide our strategy with regard to the product development.
3. Open-source – quoting from our FAQ:
“If it wasn't for the community and sites like rootkit.com, the following statements would be true:
1. The antivirus companies would be far behind with this technology
2. The hacker underground would be even further ahead with this technology
3. The antivirus companies would be happy because we wouldn't know what they're not catching.
We could not have built Helios without the help of this community of brilliant people.”
There is a definite roadmap to open-sourcing parts of the product. We believe firmly that you can only use a security product when you can see what happens under the hood
4. Detection - We know there are techniques out there that we have not dealt with in the alpha. If you point us to something we don't detect, we'll try and get it in. Rootkit technology is an extremely vast area, there's lots of ground to cover.
5. Inoculation - Once again from the whitepaper - we agree that if code actually does execute, it's game-over! Detection is a less-desirable condition. If you are able to get your code into the kernel while Helios' inoculation features are turned on, we'd be concerned. :) If a kit is installed before security software, it has a free reign over the system. Our energies are being spent trying to prevent this from happening.
6. Features - Background scanning in our opinion is critical. There is no point having to run a tool AFTER the damage has been done (see point 5). We believe this is a significant advantage over on-demand scanners. We also have application integrity (which we haven't seen in other public tools) , inoculation features for NTFS ADS, physical memory blocking, driver loading protection, file & folder access control. We added these features because we felt they were missing in other tools.
Summing up - Once we get the APIs into a decent shape, you can add rootkit detection to ANY product you want (HIDS / HIPS / AV / etc). This ability should benefit the security community as a whole. We built this for the community and will make every possible effort to incorporate the features you want.
Check back often, we will be updating regularly.