Reply to thread

Message

<blockquote data-quote="BVLon" data-source="post: 867358">I have already shared everything I do or don&#039;t do in my thread &quot;Consumer Hardening&quot;, that was a bit polluted by coronavirus-related posts <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite116" alt=":D" title="Big grin&nbsp; &nbsp; :D" loading="lazy" data-shortname=":D" />VodooShield is not useful to me personally, but it&#039;s interesting to test and play around with.It will be best utilised by organisations that allow staff to work outside of the company. This action might present an enormous risk, so VoodooShield in its most aggressive configuration will have to be installed and running at all times. Especially organisations with IT to OT... Simply relying on AI, IPS and other common methods might not always suffice and as we know, all breaches start with human element... if you are able to adapt your security approach dynamically to the user&#039;s needs you will both close all gaps that traditional approaches leave, whilst in the same time, avoid security &quot;fatigue&quot; where users just want to shut down your software or allow everything so it finally shuts up.</blockquote>

[QUOTE="BVLon, post: 867358"] I have already shared everything I do or don't do in my thread "Consumer Hardening", that was a bit polluted by coronavirus-related posts :D VodooShield is not useful to me personally, but it's interesting to test and play around with. It will be best utilised by organisations that allow staff to work outside of the company. This action might present an enormous risk, so VoodooShield in its most aggressive configuration will have to be installed and running at all times. Especially organisations with IT to OT... Simply relying on AI, IPS and other common methods might not always suffice and as we know, all breaches start with human element... if you are able to adapt your security approach dynamically to the user's needs you will both close all gaps that traditional approaches leave, whilst in the same time, avoid security "fatigue" where users just want to shut down your software or allow everything so it finally shuts up. [/QUOTE]

Verification