Subscribe to Windows IT Pro

 

Get Newsletters

  • Get the Latest News
  • Product Updates
  • Helpful Tricks
  • Productivity Tips

Subscribe Now!

December 27, 2005 12:00 AM

Protecting Data When You Can't Restrict Physical Access to Machines

Windows IT Pro
InstantDoc ID #48517
Rating: (0)

I work for a midsized bank that's expanding into store-front branches at grocery stores. I've always been able to limit physical access to our telecommunications room to the bank manager and our IT department. However, storefront branches will share a telecommunications room with other businesses, and I'm concerned about the vulnerability of financial and customer information traversing our network. What are our Windows encryption options?

You can use an IP Security Policy to help secure your company's confidential data. On the servers at the datacenter that your branch computers communicate with, you can create an IP Security Policy that requires Encapsulating Security Payload (ESP) mode IPsec connections from computers within the subnets of your store-front branches. Then you need to enable the Client (Respond Only) IP Security Policy on all computers at the new store-front branches. You can automate the process of enabling the policy and ensure that new computers deployed at the branches receive the policy by assigning the Client (Respond Only) policy in a Group Policy Object (GPO) linked to the site corresponding to that branch. With this approach, even employees who use laptops and visit the branch site will pick up the policy.

If you want to avoid using site-linked GPOs—or if you don't have Active Directory (AD) site objects defined for each branch—you can enable Client (Respond Only) on all computers in the domain. That policy doesn't initiate IPsec communications; it simply allows computers to comply when a server requires IPsec.

Enabling Client (Respond Only) on all computers also eliminates the possibility that a user from the bank's headquarters might take a hibernating laptop to a branch site. If such a laptop came back up on the branch's subnet, it would receive a new IP address, but it wouldn't reapply Group Policy until the next scheduled refresh. The laptop wouldn't pick up the site-linked GPO that enables IPsec, and therefore wouldn't be able to access the datacenter servers that require IPsec until it refreshes.

Be aware that the bank might have legal requirements for the types of encryption (e.g., algorithm, key size) that it must use, so be sure to comply with those requirements.

Related Content:

ARTICLE TOOLS

Comments
    There are no comments to display. Be the first one!
You must log on before posting a comment.

Are you a new visitor? Register Here

advertisement

advertisement

White Papers

Get your Windows 7 deployment off to the right start by implementing PC lockdown. A locked-down environment is easier and cheaper to support since users are less likely to make unnecessary changes to the core system configuration - read more here!

Essential Guides

Is your iSCSI "lossy"? The reality is that most off-the-shelf Ethernet hardware deployed for iSCSI can lose packets, resulting in slow performance or application downtime. Learn how to assess your current iSCSI infrastructure and engineer an advanced iSCSI SAN infrastructure.

Web Seminars

What's the best way to keep your network safe from malware? In this web seminar, security expert Greg Shields suggests an alternative method to the traditional blacklisting approach that is common with anti-virus and anti-malware solutions.

eLearning Series

We bring the experts direct to you to share their real-world perspective and expertise. During each event, three sessions stream in real time, so you can learn, ask questions, and get solutions.
Upcoming event: Getting the Most with Exchange 2010 with Paul Robichaux

Subscribe to Windows IT Pro!

Windows is a trademark of the Microsoft group of companies. Windows IT Pro is used by Penton Media Inc. under license from owner.