Windows Security
  Home arrow Windows Security arrow Page 3 - Hardening Communications
ASP Free Forums 
.NET  
ASP  
ASP Code  
ASP.NET  
ASP.NET Code  
BrainDump  
C#  
Code Examples  
Database  
Database Code  
IIS  
Microsoft Access  
MS SQL Server  
Silverlight  
Visual Basic.NET  
Windows Scripting  
Windows Security  
XML  
Mobile Linux 
App Generation ROI 
IBM® developerWorks 
ASP Web Hosting  
ASP.NET Web Hosting 
Windows Web Hosting
 
Weekly Newsletter
 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid 
Request Media Kit
Contact Us 
Site Map 
Privacy Policy 
Support 
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
WINDOWS SECURITY

Hardening Communications
By: McGraw-Hill/Osborne
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 5 stars5 stars5 stars5 stars5 stars / 5
    2004-10-06

    Table of Contents:
  • Hardening Communications
  • Use IPSec Policies
  • Use IPSec for Confidentiality
  • Use IPSec to Manage Connections
  • Protect IPSec-Protected Computers During Startup
  • Protect WAN Communications
  • Harden NT 4.0 Remote Access Server Configuration
  • Harden Client Access
  • Use L2TP/IPSec VPNs
  • Harden Remote Access Clients
  • Secure Wireless Access

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article
     
     
    ADVERTISEMENT


    Hardening Communications - Use IPSec for Confidentiality


    (Page 3 of 11 )

    To protect communications between two computers, use an IPSec negotiation policy. The following steps outline how to build a policy that encrypts communication between computer A with an IP address of 192.168.7.55 and computer B, which has an IP address of 192.168.7.155.

    1. Add the IP Security Policy Management snap-in to an MMC console on computer A.

    2. Right-click the IP Security Policies on Local Computer container, as shown here, and select Create an IP Security Policy.

    3. Click Next on the Welcome page.

    4. Enter the name Encrypt1 for the policy and click Next.
    5. Uncheck Activate the Default Response Rule.

       

    6. Click Next; then click Finish. 

    7.  On the Encrypt1 Rules page, click Add, as shown here, to add a new rule:

    8. On the New Rule Properties IP Filter List page, click Add to create the filter list.

    9. Enter Encrypt to name the filter list.

    10. Uncheck the Use Add Wizard box and click Add to add a filter.

    11. In the Source address drop-down list box, select A Specific IP Address.

    12. Enter the IP address of computer B, 192.168.7.155.

    13. In the Destination address drop-down list box, select My IP address, as shown here:

    14. Click OK to close the IP Filter Properties list page and click OK to close the IP Filter List page.

    15. In the IP Filter List tab, select the Encrypt entry (the list you just created), as shown in the following illustration, and then click the Filter Action tab.

    16. Click to deselect the Use Add Wizard button and click Add to add a filter action.

    17. On the New Filter Action Properties page, select Negotiate Security.

    18. Click Add to add a security method. The default selection, Integrity and Encryption, is acceptable. By default, 3DES and SHA1 are selected. Click OK.

    19. Click Accept Unsecured Communication, But Always Respond Using IPSec, as shown here:

    20. Select the General page and enter Negotiate for the Filter Action name; then click OK.

    21. Select Negotiate on the Filter Action page.

    22. Select the Authentication Methods page and click Add.

    23. Select Use This String (Preshared Key). Enter a long, complex key and then click OK.

    24. Select Kerberos in the Authentication Method Preference Order box and click Remove. Click OK to respond to the pop-up. Note in the following illustration that the shared key is partially visible in the interface.

    25. Click Close twice to exit the policy.

    26. Export the policy and import it on computer B, or re-create the policy on computer B and in both cases change the Source address to that of computer A.

    27. On computer A, in the IPSec console, right-click the policy, and select Assign to assign the policy. Until you assign the policy, it is not in effect.

    28. Repeat on computer B. (Don’t forget to change the IP address you entered in step 11.)

    This is from Hardening Windows Systems, by Roberta Bragg, (McGraw-Hill/Osborne, ISBN: 0072253541). Check it out at your favorite bookstore today. Buy this book now.

    More Windows Security Articles
    More By McGraw-Hill/Osborne


     

    WINDOWS SECURITY ARTICLES

    - Which Version of Windows 7 Should You Use?
    - Choosing the Best Windows XP Firewall
    - Finding the Correct Drivers for Windows XP D...
    - Windows Network Troubleshooting: Tips and Te...
    - Windows XP Home Network Setup: Essential Ste...
    - Using Windows Recovery Console to Fix Blue S...
    - Fix Blue Screen of Death in Windows XP: Corr...
    - Storing Data with Windows Skydrive
    - Windows System Administrator`s Toolbox
    - Solving Windows Genuine Advantage Problems
    - Encrypted Browsing in Windows using OpenSSH
    - Working with the Hosts File on Windows XP
    - Inventorying HDDs Remotely on Windows
    - Inventorying RAMs Remotely on Windows
    - Vital Windows Security Guidelines





    © 2003-2009 by Developer Shed. All rights reserved. DS Cluster 2 Hosted by Hostway
    For more Enterprise Application Development news, visit eWeek