Friday, July 7, 2006

Home /isa server /Simplifying Access Rules for ISA Firewall / Simplifying Access Rules for ISA Firewall

Simplifying Access Rules for ISA Firewall

We are all familiar with creating firewall access rule policies on ISA Server 2004.  Let’s say we want to create a two way Firewall access rule.  How do you do it?  We can create two one way firewall rules from Source to Target and from Target to Source.  If you’re like me, you are too lazy to create two firewall policies if we can find an easier method.  Here is a simple trick to achieve this without creating two separate one way firewall policies.  The trick is to select the same “Source” and “Destination” networks in the Firewall Access Rule.  Here is an example:
My goal is to create a single Access Rule policy to enable two way communications between the Main office and Branch office.
  1. Open ISA Sever Management Console
  2. In the right pane, right click on the Firewall Policy, select New and select Access Rule
  3. Enter the name of the Access Rule in the Welcome window.  Click Next
  4. Select Allow in the Rule Action window.  Click Next
  5. Select appropriate traffic in the Protocols window.  Click Next.
  6. In the Access Rule Sources window, select the Internal and Branch networks.  Click Next.
  7. In the Access Rule Destinations window, select the Internal and Branch networks.  Click Next.
  8. Click Next in the User Sets window. 
  9. Click Finish to complete the access rule creation.
The “From” and “To” tabs in the Access Rule properties look like the following:

image

SS

Santhosh Sivarajan

Microsoft MVP · Identity & Cybersecurity Architect

Santhosh has 30+ years of hands-on enterprise experience in Identity and Access Management, Microsoft Entra ID, Active Directory, Microsoft 365 and Zero Trust architecture. He is the author of two books on Windows Server and security, and leads consulting, assessments and training at SAG Business Group.

0 comments:

Post a Comment

Popular Posts
Workstation Trust Relationship Issue Issue: You receive the following error message, when you try to login to the domain.  The security database on the server does not have ... ADMT Service Account - Permission and Configuration The ADMT service account needs to have proper permission in source and target domains.  You don’t need to use 2 separate accounts.  You can ... My First Peek into Microsoft Exchange 2010 By Santhosh Sivarajan Before I really dive into Exchange 2010, I thought I would install and play with it first. I took some screen shots and notes during the ins... ObjectSID and Active Directory What is an objectSID in Active Directory? When a new object is created in Active Directory, Domain Controller assigns a unique value used ... AD Group Report - List Group Members in Active Directory–PowerShell Script Updated Script - http://portal.sivarajan.com/2011/10/search-ad-collect-local-admin-group.html Script #1 This script... Add Users to a Group–PowerShell Script Purpose – Add users to a group from an input file – PowerShell V2 Script.  Input file – Input file (Users.csv) contains samAccountName in... User Account Migration and Merging – Part I (ADMT) Part I - User Account Migration and Merging Using ADMT Part II - User Account Migration and Merging Using QMM pre-creating user account ... User Account Migration and Merging – Part II (Quest Migration Manager) Part I - User Account Migration and Merging Using ADMT Part II - User Account Migration and Merging Using QMM Pre-creating user account in... Delete Stale or Inactive Computer Accounts from Active Directory Here is an easy way to identify and delete inactive or stale computers in an Active Directory environment.  Using the dsquery command you c... Converting PowerShell (PS1) to EXE / Standalone Application As we know, there many applications available to convert a PowerShell file to a standalone executable file.  Based on my experience, PowerSh...