Security Policy - US access only

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.
Palo Alto Networks Approved
Palo Alto Networks Approved
Community Expert Verified
Community Expert Verified

Security Policy - US access only

L1 Bithead

Hello,

I'm trying to configure a Security Policy to only allow US-region IP addresses to hit our network.   I added as a first rule to allow any untrust us region to destination untrust US region.  I am not sure if this is correct.  maybe I'm allowing all traffic within US, that probably is not supposed to be allowed.  

thanks

 

#urlfiltering #regionfiltering

1 accepted solution

Accepted Solutions

Cyber Elite
Cyber Elite

@YParreno,

I wouldn't set this rule up like this. Instead, I would setup an entry that lists US as the source with the negate-source option enabled and set the application and service to any and the action to deny. This will drop any and all traffic that doesn't originate from the US, while allowing the rest of your rulebase to actually handle traffic.

As you've presently configured things as you've described, you're allowing all traffic from the US to hit your untrust zone, which you likely don't want to do. 

View solution in original post

3 REPLIES 3

Cyber Elite
Cyber Elite

How about:

first rule to allow any untrust us region to destination untrust US region, with destination of your public IP of your FW?

You did not mention/relay that you have any destination NAT rules, so I presume there are none., so no outside US traffic will hit the inside of your network.  Is this correct?

 

Help the community: Like helpful comments and mark solutions

Cyber Elite
Cyber Elite

@YParreno,

I wouldn't set this rule up like this. Instead, I would setup an entry that lists US as the source with the negate-source option enabled and set the application and service to any and the action to deny. This will drop any and all traffic that doesn't originate from the US, while allowing the rest of your rulebase to actually handle traffic.

As you've presently configured things as you've described, you're allowing all traffic from the US to hit your untrust zone, which you likely don't want to do. 

L1 Bithead

thank you, that is exactly what i did.

  • 1 accepted solution
  • 2178 Views
  • 3 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!