Reply to thread

Message

<blockquote data-quote="danb" data-source="post: 1069113" data-attributes="member: 62850">Hey guys, I will respond to the posts that need a response when I get a chance, but real quick...Thank you for creating a list of file managers, I will add them all in a few days once we have all of them accounted for.As far as the allow by parent process feature goes, I just tested it and so far it is working as expected, but I will look into this more to be sure, especially since the new attack chain feature is integrated into the parent process feature.&nbsp; But please keep in mind, the allow by parent process feature is a feature that is designed to reduce unnecessary blocks.&nbsp; It is not a feature that is designed to block all child processes.&nbsp; In other words, if one of the other CyberLock features auto allows an item, disabling the allow by parent process feature will not automatically block the child process.&nbsp; You can look in the C:\ProgramData\CyberLock\DeveloperLog.log to see why an item was auto allowed, when you were not expecting that item to be auto allowed.&nbsp; CyberLock has many different &quot;usability features&quot; that automatically and safely allow items, to reduce unnecessary blocks as much as possible, and this includes the allow by parent process feature.I hope this makes sense, if not, please let me know and I can think of another way to explain it.&nbsp; And if anyone is still having an issue with this feature, please let me know.</blockquote>

[QUOTE="danb, post: 1069113, member: 62850"] Hey guys, I will respond to the posts that need a response when I get a chance, but real quick... Thank you for creating a list of file managers, I will add them all in a few days once we have all of them accounted for. As far as the allow by parent process feature goes, I just tested it and so far it is working as expected, but I will look into this more to be sure, especially since the new attack chain feature is integrated into the parent process feature. But please keep in mind, the allow by parent process feature is a feature that is designed to reduce unnecessary blocks. It is not a feature that is designed to block all child processes. In other words, if one of the other CyberLock features auto allows an item, disabling the allow by parent process feature will not automatically block the child process. You can look in the C:\ProgramData\CyberLock\DeveloperLog.log to see why an item was auto allowed, when you were not expecting that item to be auto allowed. CyberLock has many different "usability features" that automatically and safely allow items, to reduce unnecessary blocks as much as possible, and this includes the allow by parent process feature. I hope this makes sense, if not, please let me know and I can think of another way to explain it. And if anyone is still having an issue with this feature, please let me know. [/QUOTE]

Verification