Reply to thread

Message

<blockquote data-quote="danb" data-source="post: 638472" data-attributes="member: 62850">Potentially, but please keep in mind that this rule / setting does not apply to everything.&nbsp; As a silly example, we have to exclude explorer.exe from this rule / setting, hehehe for obvious reasons <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite110" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />.&nbsp; It would allow pretty much everything <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite110" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />.So there are several checks in this rule, otherwise, yeah, we could accidentally allow something we did not want to.&nbsp; I have spent a very long time refining these rules, in an effort to automatically allow as much good stuff as possible, while blocking as much bad stuff as possible, simply to enhance our usability.As you and I have discussed... application control is a very robust and secure technology, but no one uses it because it is too much of a PITA.&nbsp; That is where VS comes in... we are the only user-friendly computer lock.&nbsp; The way we see it... just because traditional application whitelisting is not user-friendly enough for people adopt, that does not mean that the endpoint should not be locked when it is at risk <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite110" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />.Having said that... if you can find a way around this, please let me know!&nbsp; As I always say... there is not a chance that I thought of everything.</blockquote>

[QUOTE="danb, post: 638472, member: 62850"] Potentially, but please keep in mind that this rule / setting does not apply to everything. As a silly example, we have to exclude explorer.exe from this rule / setting, hehehe for obvious reasons ;). It would allow pretty much everything ;). So there are several checks in this rule, otherwise, yeah, we could accidentally allow something we did not want to. I have spent a very long time refining these rules, in an effort to automatically allow as much good stuff as possible, while blocking as much bad stuff as possible, simply to enhance our usability. As you and I have discussed... application control is a very robust and secure technology, but no one uses it because it is too much of a PITA. That is where VS comes in... we are the only user-friendly computer lock. The way we see it... just because traditional application whitelisting is not user-friendly enough for people adopt, that does not mean that the endpoint should not be locked when it is at risk ;). Having said that... if you can find a way around this, please let me know! As I always say... there is not a chance that I thought of everything. [/QUOTE]

Verification