Common concept
Self-protection
Verification of own components
Inbound and outbound protection
Process protection
File and component protection
Driver protection
Service protection
Registry protection
Protection of other system resources
Parent process control
Control of automatically started programs
Sniffing protection
Protection of system resources
No ring3 hooks
Process protection
File and component protection
Driver protection
Service protection
Registry protection
These five security measures are generally covered by a classic HIPS (Host-based Intrusion Detection System), something that Comodo is aspiring to eventually include in a later release of their firewall. Their current release does, to some extent, offer some of this protection with its Application Component Authentication and Application Behavior Analysis, but certainly not to the extent an all-out HIPS would offer. BTW, I am running the latest beta CPFW with System Safety Monitor HIPS and the two work extremely well together.
The learning curve on SSM is fairly steep, but it’s not too bad if you spend some quality time at it. I think I’ve got most of it figured out, at least the important stuff
Anti-Hook in my opinion is far better then SSM and uses a fraction of the resources…i have never seen anti-hook go over 1% usage and i dont remember the exact ram usage but it was very small
lol so much for Anti-Hook being small i just downloaded their newest version 3.0 and while it blocks just about everyleaktest there is on its own it uses damn near 60megs between the ram and the virtuall ram…cant wait for the next major release of CPF (R)
I find prosecurity free better then ssm free but ssm paid is better.
I couldn’t run them both together but not because of conflicts but because Comodo and prosecurity kept popping up at same time so basically Comodo PF already has a hips since its behavior analysis keeps going off same time.
What kind of geniuses have you got to make a HIPS at only 1mb! You Geniuses!
