Enhanced Security Measures in Place:   To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.

RFC1918

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

RFC1918

L4 Transporter

Basic trust to untrust policy I see internal address sending snmp to addresses like 10.0.0.1, 192.168.1.x.

 

Do people create a policy to block internal traffic going to RFC1918 on the untrusted interface?

3 REPLIES 3

Cyber Elite
Cyber Elite

I usually block trust to untrust RFC1918.

Although ISP routers drop it anyway I like to keep it clean.

It is really common for many applications like Skype for example to scan internal ranges for peers.

Enterprise Architect, Security @ Cloud Carib Ltd
Palo Alto Networks certified from 2011

L1 Bithead

Do you have the one line policy.

 

Trust to untrust  ( the builtin PAN addresses appear confusing.

 

TrRUST or INSIDE zones

ANY

UNTRUST  

  • 10.0.0.0  10.255.255.255  (10/8 prefix)
  • 172.16.0.0  172.31.255.255  (172.16/12 prefix)
  • 192.168.0.0  192.168.255.255 (192.168/16 prefix)

Action Block/deny

This is  the first policy I believe

Cyber Elite
Cyber Elite

Hello,

If you follow a DENY ALL allow by exception methodology, just put a DENY ALL policy at the bottom of the Security Policies. This way only traffic that you 'allow' is allowed to go between zones, etc.

 

Regards,

  • 2587 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!