Endpoint Protection

 View Only
Expand all | Collapse all

Need to block incoming traffic for particular port from Public Ip Address

ℬrίαη

ℬrίαηJul 16, 2013 10:33 AM

  • 1.  Need to block incoming traffic for particular port from Public Ip Address

    Posted Jul 16, 2013 07:38 AM

    Hi,

    I need to block incoming traffic for particular port from Public IP Address allowing private address. how to set the firewall policy for this for wide range of public ip address ?



  • 2.  RE: Need to block incoming traffic for particular port from Public Ip Address

    Posted Jul 16, 2013 08:00 AM

    What is the range?

    You need two rules.

    You can create a block rule based on IP range if needed. Move it to the top.

    Create the allow rule for the private subnets and move it under the block rule



  • 3.  RE: Need to block incoming traffic for particular port from Public Ip Address

    Posted Jul 16, 2013 08:24 AM

    for first rule...Public ranges are more, if you have ready public ip ranges with mask then it will be good, else i have to explore it.

    for 2nd rule-- I have enabled

    Action--Allow

    App-Any

    Host--10.0.0.0/255.0.0.0 , 172.16.0.0/255.240.0.0, 192.168.0.0/255.255.0.0

    Service Any

     

     

    is this ok ?



  • 4.  RE: Need to block incoming traffic for particular port from Public Ip Address

    Posted Jul 16, 2013 08:35 AM

    Yes, you can do a subnet and add the mask

    Yes, allow rule looks fine.



  • 5.  RE: Need to block incoming traffic for particular port from Public Ip Address

    Posted Jul 16, 2013 09:15 AM

    for block rule--public masks are many more than 100 entires, if im not wrong, so is there any simple solution ?



  • 6.  RE: Need to block incoming traffic for particular port from Public Ip Address

    Posted Jul 16, 2013 10:33 AM

    You would need to enter manually



  • 7.  RE: Need to block incoming traffic for particular port from Public Ip Address

    Posted Jul 17, 2013 01:28 AM

    ok can i have like this

     

    Block port for all ip's & allow only for set of ip's.

    i did like this, but its not working for allowed ip as well.

    in first rule--I set Block all ip's for partiuclar ip.

    2nd rule--I allowed required ips for particular ip.



  • 8.  RE: Need to block incoming traffic for particular port from Public Ip Address

    Broadcom Employee
    Posted Jul 17, 2013 01:52 AM

    do you know the IP range, why not set the firewall rule on gateway ?



  • 9.  RE: Need to block incoming traffic for particular port from Public Ip Address

    Posted Jul 17, 2013 02:33 AM

    We are using UltraVNC at office & when users plugs at home Broadband he is out of our network, user is  finding unwanted request attempts on VNC when user is at home, so i want to block this unwated requests from outside world except selected few ip's in my office..

     

    Baiscally i want like this

     

    Block vnc port 5900 & 5800 from all ip's & allow only for few selected ip's.



  • 10.  RE: Need to block incoming traffic for particular port from Public Ip Address

    Broadcom Employee
    Posted Jul 17, 2013 02:38 AM

    in that case create anetwork adapters as exception which can use VNC



  • 11.  RE: Need to block incoming traffic for particular port from Public Ip Address

    Posted Jul 17, 2013 02:53 AM

    but user uses normal ethernet adapter to plug at home broadband..so if we had exception, i don't think this will serve the purpose.



  • 12.  RE: Need to block incoming traffic for particular port from Public Ip Address

    Posted Jul 17, 2013 04:19 AM

    HI, 

    Creating a firewall policy

    The Symantec Endpoint Protection includes a default Firewall policy with default firewall rules and default firewall settings for the office environment. The office environment is normally under the protection of corporate firewalls, boundary packet filters, or antivirus servers. Therefore, it is normally more secure than most home environments, where limited boundary protection is available.

    When you install the console for the first time, it adds a default Firewall policy to each group automatically.

    Every time you add a new location, the console copies a Firewall policy to the default location automatically. If the default protection is not appropriate, you can customize the Firewall policy for each location, such as for a home site or customer site. If you do not want the default Firewall policy, you can edit it or replace it with another shared policy.

    When you enable firewall protection, the policy allows all inbound IP-based network traffic and all outbound IP-based network traffic, with the following exceptions:

    ·         The default firewall protection blocks inbound and outbound IPv6 traffic with all remote systems.

    Note:

    IPv6 is a network layer protocol that is used on the Internet. If you install the client on the computers that run Microsoft Vista, the Rules list includes several default rules that block the Ethernet protocol type of IPv6. If you remove the default rules, you must create a rule that blocks IPv6.

    ·         The default firewall protection restricts the inbound connections for a few protocols that are often used in attacks (for example, Windows file sharing).

    Internal network connections are allowed and external networks are blocked.

     describes the tasks that you can perform to configure a new firewall policy. You must add a firewall policy first, but thereafter, the remaining tasks are optional and you can complete them in any order.

    Table: How to create a firewall policy

    Task

    Description

    Add a firewall policy

    When you create a new policy, you give it a name and a description. You also specify the groups to which the policy is applied.

    A firewall policy is automatically enabled when you create it. But you can disable if you need to.

    Create firewall rules

    Firewall rules are the policy components that control how the firewall protects client computers from malicious incoming traffic and applications. The firewall automatically checks all incoming packets and outgoing packets against these rules. It allows or blocks the packets based on the information that is specified in rules. You can modify the default rules, create new rules, or disable the default rules.

    When you create a new Firewall policy, Symantec Endpoint Protection provides default firewall rules.

    The default firewall rules are enabled by default.

    Enable and customize notifications to users that access to an application is blocked

    You can send users a notification that an application that they want to access is blocked.

    These settings are disabled by default.

    Enable automatic firewall rules

    You can enable the options that automatically permit communication between certain network services. These options eliminate the need to create the rules that explicitly allow those services. You can also enable traffic settings to detect and block the traffic that communicates through NetBIOS and token rings.

    Only the traffic protocols are enabled by default.

    .

    If the Symantec Endpoint Protection client detects a network attack, it can automatically block the connection to ensure that the client computer is safe. The client activates an Active Response, which automatically blocks all communication to and from the attacking computer for a set period of time. The IP address of the attacking computer is blocked for a single location.

    This option is disabled by default.

    Configure protection and stealth settings

    You can enable settings to detect and log potential attacks on the client and block spoofing attempts.

    You can enable the settings that prevent outside attacks from detecting information about your clients.

    All of the protection options and stealth options are disabled by default.

    Integrate the Symantec Endpoint Protection firewall with the Windows firewall

    You can specify the conditions in which Symantec Endpoint Protection disables the Windows firewall. When Symantec Endpoint Protection is uninstalled, Symantec Endpoint Protection restores the Windows firewall setting to the state it was in before Symantec Endpoint Protection was installed.

    The default setting is to disable the Windows firewall once only and to disable the Windows firewall disabled message.

    Configure peer-to-peer authentication

    You can use peer-to-peer authentication to allow a remote client computer (peer) to connect to another client computer (authenticator) within the same corporate network. The authenticator temporarily blocks inbound TCP and UDP traffic from the remote computer until the remote computer passes the Host Integrity check.

    Note:

    You can only view and enable this option if you install and license Symantec Network Access Control.

    This option is disabled by default.

     

    Best practices for Firewall policy settings

    Firewall policy best practices

    Scenario

    Recommendation

    Remote location where users log on without a VPN

    The following settings are recommended as best practice for the Firewall policy:

    ·         Assign the strictest security policies to clients that log on remotely without using a VPN.

    ·         Enable NetBIOS protection.

    Note:

    Do not enable NetBIOS protection for the location where a remote client is logged on to the corporate network through a VPN. This rule is appropriate only when remote clients are connected to the Internet, not to the corporate network.

    ·         To increase security, also block all local TCP traffic on the NetBIOS ports 135, 139, and 445.

    Remote location where users log on through a VPN

    The following settings are recommended as best practice for the Firewall policy:

    ·         Leave as-is all the rules that block traffic on all adapters. Do not change those rules.

    ·         Leave as-is the rule that allows VPN traffic on all adapters. Do not change that rule.

    ·         For all rules that use the action Allow, change the Adapter column from All Adapters to the name of the VPN adapter that you use.

    ·         Enable the rule that blocks all other traffic.

    Note:

    You need to make all of these changes if you want to avoid the possibility of split tunneling through the VPN.

    Office locations where users log on through Ethernet or wireless connections

    Use your default Firewall policy. For the wireless connection, ensure that the rule to allow wireless EAPOL is enabled. 802.1x uses the Extensible Authentication Protocol over LAN (EAPOL) for connection authentication.

    Regards

    Ajin



  • 13.  RE: Need to block incoming traffic for particular port from Public Ip Address
    Best Answer

    Posted Jul 17, 2013 07:14 AM

    Hello,

    a firewall is meant to block anything except what you allow hence it is enough one only rule like "allow incoming connection to port X only from <the subnet(s) you want to allow>", while all the rest which does not meet this rule will be blocked.

    Just in case there's another rule (a custom or a default one) that would allow more connections to that port than you want, you may:
    - refine that rule
    - add another rule "block all to port X" just below the one "allow incoming connection to port X only from <the subnet(s) you want to allow>", so that what is not blocked by the previous rule will be blocked by this one, no sense in listing all public IP ranges.

     



  • 14.  RE: Need to block incoming traffic for particular port from Public Ip Address

    Posted Jul 17, 2013 09:41 AM

    Beppe---I did the way you told, but still from other ip's im able to connect. to vnc

     

    Action--Allow ( rule on top )

    App-Any ( tried with application process name & path )

    ip address: 192.168.248.111( even tried with ip range/subnet )

    Service Any ( tried with applicaiton port number also )

     

    Still with this rule im able to connect from other ip address in my office network.



  • 15.  RE: Need to block incoming traffic for particular port from Public Ip Address

    Posted Jul 17, 2013 10:05 AM

    Try to add another rule "block all to port X" just below the one "allow incoming connection to port X only from <the subnet(s) you want to allow>", so that what is not blocked by the previous rule will be blocked by this one, no sense in listing all public IP ranges.



  • 16.  RE: Need to block incoming traffic for particular port from Public Ip Address

    Posted Jul 18, 2013 01:38 AM

    Beppe--I did the same wayyou told

     

    1st rule:

    Action--Allow ( rule on top )

    App-Any ( tried with application process name & path )

    ip address: 192.168.248.111( even tried with ip range/subnet )

    Service Any ( tried with applicaiton port number also )

     

    2nd rule:

     

    ACtion: Block ( rule below Allow rule )

    App- application process name & path

    Ip address--Any

    Service--tried with applicaiton port number

     

     

    if I do this way..Im not able to connect from allowed subnet also..

    Let us know how to proceed on this



  • 17.  RE: Need to block incoming traffic for particular port from Public Ip Address

    Posted Jul 18, 2013 02:48 AM

    ok..finally I was able to accompalish this task.

     

    but im quite confused in Host list ( source/desntination or local/remote ) & same in service also

     

    What is the difference in Source/desntination & local/remote options. in my case after selecting Source/Denstination, then rules started working as expected.



  • 18.  RE: Need to block incoming traffic for particular port from Public Ip Address

    Posted Jul 18, 2013 03:01 AM

    Hello,

    I am happy to read that you were finally able to implement what I suggested.

    To know more about Source/desntination & local/remote options just click the Help button there for more details, but I believe in few minutes someone else with more time than me will copy and paste it here for you.

    Remember to flag your request as resolved, please!



  • 19.  RE: Need to block incoming traffic for particular port from Public Ip Address

    Posted Jul 18, 2013 03:10 AM

    i didn't notice the Help button ..thanks for the help...