At this point SSLv3 is somewhat old news, but there are still businesses that have SSLv3 (and worse, sometimes SSLv2) accepted on their client machines, this can lead to a multitude of security vulnerabilities that can be easily exploited (i.e. POODLE). The purpose of this post is to show you how to disable the insecure protocols on standalone workstations or via Group Policy if you are on a corporate network with a domain controller.
In very recent news you have likely heard of someone putting infected USB drives into mailboxes, although this is happening in Australia it is still incredibly relevant no matter where in the world you may be. It is always in good practice to never, and I mean never, plug in a random USB thumb drive you might have found out in the wild. This is one of the tried and true methods that gets malware installed on your computer because of a built-in “feature” of Windows called AutoPlay in addition to AutoRun, and also because most people will think one of two things:
- Oh, free thumb drive!
- Oh, someone might have lost this, let me see if their name or contact information is on it!
The best course of action is to just throw them away. But, in the off chance that you do put a USB thumb drive in your computer, you better hope that AutoPlay and Autorun is disabled. That is what I’m going to show you how to configure today on standalone workstations and on a domain with Group Policy.
One of the most effective ways to protect your company and its computers is to implement the blocking of macros in Microsoft Office documents (this includes: Word, PowerPoint, Excel, Publisher, Outlook, Access, and Visio). Blocking macros is a relatively straight-forward and simple process as it can be done via Group Policy, and that is what I will be covering in this post.