Skip to content

Instantly share code, notes, and snippets.

@kmontenegro
Last active March 7, 2018 11:49
Show Gist options
  • Save kmontenegro/3056c337fedfb5d400069df0d0f2fee2 to your computer and use it in GitHub Desktop.
Save kmontenegro/3056c337fedfb5d400069df0d0f2fee2 to your computer and use it in GitHub Desktop.
Endpoint thresholds

Endpoint Thresholds

Securint endpoints is hard. Between user account management, patch management, and secure physical access, there are so many things that can go wrong.

Below are some potential baselines considerations for endpoint protection of Windows machines:

  1. Make sure the machine is part of a patch management routine
  2. Use the Microsoft Security Baseline Recommendations and, where possible, apply them by Group Policy Object
  3. Always grant least priviledges to your users. If applications required local admin rights, please work with the vendor to identify how that window of user rights can be restricted.
  4. Enable application control. This not only helps keep your patch surface small, it also helps identify what the machine's purpose is and what corallary threat vectors are. See if AppLocker or the app whitelisting in Device Guard help you establish a baseline posture/practice.
  5. PowerShell is great but does it need to installed in all machines? Can you run it only in "Constrained Language" mode?
  6. Tighetn up macro security in Microsoft Office documents. You can do this trough a GPO whereby a user has to intentionally bring a document out of "protected" mode.
  7. Use DNS to your your advantage: be it OpenDNS or other providers, there are more and more ways to prevent malicous traffic from reaching your endpoints. These small steps can help protect your endpoints from malicious activity such as ransomware.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment