The HIPS engine lets you define what any program may do: reading or writing files, editing the registry, creating processes or accessing the network.
Anatomy of a rule
A rule consists of the target program, action type, object and response, precise down to folders and processes.
- Match by program path or signature
- Actions cover read, write, execute and network
- Responses: allow, block or prompt
Import and reuse
Rules can be exported as files and shared with other machines; the business edition supports bulk delivery and grouping.
- Import and export rules
- Rule groups and notes
- Centralized delivery in business edition
FAQ
Can a bad rule break my system?
It can block system programs. Test rules on a single program first and keep a backup of the defaults.
Do regular users need this?
Usually not. The default protection rules already cover most situations.