Free Republic
Browse · Search
General/Chat
Topics · Post Article

To: Libloather

There is no excuse for this. Some IT controls and discipline within the organization is all that it takes to stop it. For example lockdown the ability for a user to start any unapproved “.exe” file. It is also a necessary move to segregate “process” and “business” systems from each other.


5 posted on 06/10/2021 3:15:23 AM PDT by mad_as_he$$
[ Post Reply | Private Reply | To 1 | View Replies ]


To: mad_as_he$$
There is no excuse for this. Some IT controls and discipline within the organization is all that it takes to stop it. For example lock down the ability for a user to start any unapproved “.exe” file. It is also a necessary move to segregate “process” and “business” systems from each other.

Spot-on. It's a pain in the ass to do however whitelisting executable files works.

So does automatically sandboxing suspicious emails and blocking email from domains less than 90 days old.

And that's just for starters.

Logically isolate the user from the data center, micro-segmentation of the network, and locking down the user's workstation/laptop preventing any configuration changes including installation of any new unapproved software and you've got a good start on preventing ransomware from getting installed on your network.

10 posted on 06/10/2021 4:35:03 AM PDT by usconservative (When The Ballot Box No Longer Counts, The Ammunition Box Does. (What's In Your Ammo Box?))
[ Post Reply | Private Reply | To 5 | View Replies ]

Free Republic
Browse · Search
General/Chat
Topics · Post Article


FreeRepublic, LLC, PO BOX 9771, FRESNO, CA 93794
FreeRepublic.com is powered by software copyright 2000-2008 John Robinson