Best practices for using restriction policy whitelists
When dealing with application permissions, does the number of "good" applications make whitelisting an unreasonable option?

    Requires Free Membership to View

    SearchSecurity.com members gain immediate and unlimited access to breaking industry news, virus alerts, new hacker threats, highly focused security newsletters, and more -- all at no cost. Join me on SearchSecurity.com today!

    Michael S. Mimoso, Editorial Director

    By submitting your registration information to SearchSecurity.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSecurity.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

I recently wrote a brief tip about how to configure such restrictions in Windows using Group Policy, as well as the capabilities of new enterprise endpoint security suites. Applying this concept depends on the particular computer system and its use.

For a general-purpose computer used for all manner of things (surfing the Web, reading email, running enterprise applications, evaluating new software, etc.), such restrictions are highly unwieldy and difficult to keep up to date. But, for a computer that doesn't have to do very many different things (like one used for just reading email and surfing the Internet with a small number of helper applications), such restrictions can greatly improve security. Unfortunately, most enterprise systems fall somewhere in the middle of these two extremes.

I recommend surveying system administrators to determine where your organization has pockets of relatively simpler computers, and then start using them to experiment with software restriction policy whitelists. Gradually move up to more complex classes of systems over time, until you reach the point of diminishing returns in maintaining such lists from an operational perspective. That point will likely be reached quickly, keeping whitelists on only the simplest of computers. Still, for those boxes, security will have improved significantly.

For more information:

  • In this Q&A, learn if using whitelists and blacklists is an effective method for preventing spam.
  • Michael Cobb unveils whether allowing only whitelist email messages will stop image spam.
  • This was first published in April 2008