Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1008
  • Last Modified:

Netscreen-25 configuration for port blocking


 How to block ports in Netscreen-25 firewall?
0
ragot
Asked:
ragot
  • 10
  • 7
  • 3
4 Solutions
 
deimarkCommented:
Which kind of port blocking are you looking for?  Is it physical port or logical port you are meaning?  Ie the physical interface or the application port?
0
 
ragotAuthor Commented:
hi delmark, its the logical port. i want to block unncessary ports for forest trusting.
0
 
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
Are you using a "permit any-any-any" type of setup? That is, have you defined a policy allowing any traffic? By default all traffic crossing zones (Trust and Untrust) is rejected.
0
NEW Internet Security Report Now Available!

WatchGuard’s Threat Lab is a group of dedicated threat researchers committed to helping you stay ahead of the bad guys by providing in-depth analysis of the top security threats to your network.  Check out this quarters report on the threats that shook the industry in Q4 2017.

 
ragotAuthor Commented:
hi qlemo, for now yes we are allowing any traffic
0
 
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
I still have no idea of your config. You can only block traffic crossing zones, because then policies are applied to the traffic. If you want to block traffic from one to another ethernet port in the same zone, you need to use the much more complicated policy-based routing.
Please describe what you want to do, and tell us more about your existing config. Is a VPN involved? Are you crossing zones?
0
 
deimarkCommented:
Not true qlemo. You don't need to use PBR to apply a policy on intrazone traffic. Simply tick the box for "intrazone block" on the zone and then you will need to add specific policies ultimate allow the traffic.

@ ragot. Can you give us a but more info on what you are trying to do her?  Please give an example if the policlcies you have already and exactly what you are trying to achieve ie block http from x to y

We can certainly help you here but we need a but more info to advise correctly
0
 
ragotAuthor Commented:
hi qlemo, delmark

i have policies here that allow all, of course that is not secure. now i want to allow only ports use for forest trusting.

thanks for your replies.
0
 
ragotAuthor Commented:
@qlemo: yes there is vpn involved. im connected to main office with all traffic allow
0
 
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
Do you use a route based or policy based VPN? Anyway, you will have a policy allowing the VPN traffic?! You can just modify that to allow only some ports: Create custom services containing NetBIOS (135, 137-139, each udp and tcp, and 445/tcp) or use the predefined ones.  Than include those as service in your VPN or Permit policy instead of "any".
0
 
deimarkCommented:
Have a look at the below link here

http://www.juniper.net/techpubs/software/screenos/screenos6.0.0/index.html

This is a great one stop shop for how to's and examples on how to achieve certain goals.

Have a look at volume 2, the fundamentals which gives a great grounding on what zones and policies are as well as volume 5, the VPN doc.

0
 
ragotAuthor Commented:

thanks for both of you on your answers.

 i saw a guide on how to create custom services, there are fields like :

 Source Port : Low and High
 Destination Port : Low and High
 ICMP : Low and High

 from this article : http://support.microsoft.com/kb/179442  there is client and server port. it is the source and destination port field right? but where will i put the port numbers? low or high?

thanks
0
 
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
The source port is always from the sender / requester of a service, the destination port always to the receiver. Most of the time only the destination port is fixed. For example, if we monitor a RDP connection, it is:
Source requests to open destination port 3389, source port is dynamic.
The appropriate service entry would look exactly like that. "low" and "high" are the boundaries of your service ports, and in this case they are 3389 & 3389 (source), 0 & 65535 (destination, no restriction).

However, you should not need to create custom services in this case, all services should be predefined already. You need destination porst 135, 137-139, 445, 389 (ldap, for Active Directory).
If you are uncertain about whether you can restrict the source port or udp/tcp, just allow for more general traffic, and switch on logging in the policy for a short period of time. You will see a detailled log of connection attempts including ports and protocols.
0
 
ragotAuthor Commented:
thanks qlemo for your reply. im reading thru your last 2 posts and i sum it up as this :

create custom service or predefined services and add the services into policy instead of any..

so in this case the firewall will be limited to predefined ports and services which will be secure. am i correct?
0
 
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
Yes. The default policy (invisible) is deny-all, so anything you do not allow is denied.
0
 
ragotAuthor Commented:
what if the default policy has been changed to allow all? does it need to be deleted and create a new policy?
0
 
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
Just create a deny or reject policy for all addresses as last one.
0
 
ragotAuthor Commented:

 will there be no conflicts on that? thanks a lot qlemo :)
0
 
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
No, no conflicts. Policies are applied top-down, so you should define the most specific on top, the most generic on bottom.
0
 
ragotAuthor Commented:
thanks a lot ! you are very helpful !
thanks to delmark also..
0
 
ragotAuthor Commented:
awesome!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

The Firewall Audit Checklist

Preparing for a firewall audit today is almost impossible.
AlgoSec, together with some of the largest global organizations and auditors, has created a checklist to follow when preparing for your firewall audit. Simplify risk mitigation while staying compliant all of the time!

  • 10
  • 7
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now