Reply to thread

Message

<blockquote data-quote="danb" data-source="post: 1058178" data-attributes="member: 62850">You probably already know this, but please make sure you disable the option &quot;Automatically deactivate after 10 minutes of system idle&quot; in CyberLock Settings / Basic tab prior to the red team testing.&nbsp; CyberLock is designed to protect the endpoint while the user is engaging in risky activities, so we left this option on by default.&nbsp; We should probably automatically disable this option after 2-4 weeks, or prompt the user to see if they would like to disable this option at that time.&nbsp; Also, please remember when testing CyberLock, to reset the whitelist when retesting a certain attack.I would also like to mention that locking the endpoint down to the point where it is completely unusable is actually the easy part.&nbsp; The difficult part is to lock the endpoint down as tightly as possible, WHILE making it user-friendly enough to actually be able to use.&nbsp; For example, could you imagine if a military department was at war and they were unable to execute software necessary to complete their mission?A wise women once asked me a simple question with an analogy while trying to make a point about security in general.&nbsp; Here question was &quot;What is the best exercise equipment?&nbsp; (e.g. Bowflex, Peloton).&nbsp; Her answer was simply... &quot;It is the one that you use&quot;.</blockquote>

[QUOTE="danb, post: 1058178, member: 62850"] You probably already know this, but please make sure you disable the option "Automatically deactivate after 10 minutes of system idle" in CyberLock Settings / Basic tab prior to the red team testing. CyberLock is designed to protect the endpoint while the user is engaging in risky activities, so we left this option on by default. We should probably automatically disable this option after 2-4 weeks, or prompt the user to see if they would like to disable this option at that time. Also, please remember when testing CyberLock, to reset the whitelist when retesting a certain attack. I would also like to mention that locking the endpoint down to the point where it is completely unusable is actually the easy part. The difficult part is to lock the endpoint down as tightly as possible, WHILE making it user-friendly enough to actually be able to use. For example, could you imagine if a military department was at war and they were unable to execute software necessary to complete their mission? A wise women once asked me a simple question with an analogy while trying to make a point about security in general. Here question was "What is the best exercise equipment? (e.g. Bowflex, Peloton). Her answer was simply... "It is the one that you use". [/QUOTE]

Verification