Jump to content

Rule conflict in HIPS leads to looping (EES 9.1.2051)

Recommended Posts


I tried to implement using HIPS in EES 9.1.2051 such a scenario as blocking the launch of any applications from a specific folder except those allowed. Is such a scenario even possible?

To do this, two rules were created in HIPS.

The first rule allows all applications to run programs at C:\New folder\write.exe, and the second rule blocks all applications from running programs at C:\New folder\*.

This setting results in the fact that each time C:\New folder\write.exe is launched, one processor core is loaded, the resources of which begin to be consumed by the parent application.

After that, the parent application cannot be terminated in any way.

Also, the problem repeats if you simply specify the path as C:\New folder\write.exe in the blocking rule.



Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...