How to Create a Network Access Rule

ZeroLock® Network Access rules allow the system administrator to restrict what process has access to networking functionality.


Using this functionality, you can limit incoming and/or outbound network traffic.

Rule Creation

  1. To create a Network Access rule, from the ZeroLock® Management Console (ZMC) go to Dashboard | Control Policies | Rules. Under the Actions drop down menu select Add New Rule.
    Policy Rules Actions Add New Rule 2.0.1-1

  2. On the New Policy Rule pop-up, select Network Access from the drop-down menu.
     
  3. Using the variety of features offered for this Rule Type, craft a rule that fits the exact network access control action you want ZeroLock to monitor.


    Each field of the Network Access Rule screen is described below:

    Name

    1

    The name of the rule as it will appear on your Rules page as well as when adding to a policy. 

    Description

    2

    The description of the rule as it will appear on your Rules page as well as when adding to a policy. It is useful for explaining the purpose of the rule.

    Rule Type

    3

    Selecting what type of rule to create (SSH-MFA, Hash, Canary, File Access, Network Access, or Program Execution). This can only be changed during initial rule creation.

    Once the rule is created, this is the only field that can no longer be edited.

    Source Type

    4

    Select between ProcessExecutable, or Command.

    Process will trigger based on the name of the process (either child, parent process, or both, as defined in "Scope" below) that is running in memory.

    Executable will trigger based on the actual program's filename running in directories such as /bin, /sbin, and others.

    Command will trigger based on the full command line arguments used to launch a process.

    Source Process/
    Executable/ Command

    5

    Designate the Regex that matches on the ProcessExecutable, or Command that is going to be either allowed or blocked from executing another specific ProcessExecutable, or Command. This allows for some granularity of allowing some processes to execute a program but not others. If you do not want ANY process executing your target program, simply put a .* in this field.

    Target Type

    6

    Select between ProcessExecutable, or Command.

    Process will trigger based on the name of the process (either child, parent process, or both, as defined in "Scope" below) that is running in memory.

    Executable will trigger based on the actual program's filename running in directories such as /bin, /sbin, and others.

    Command will trigger based on the name of the shell command used to launch and process or executable. 

    Target Process/
    Executable/ Command 

    7

    Designate the Regex that matches on the actual ProcessExecutable, or Command that is going to be either allowed or blocked from executing.

    Scope

    8

    Specifies if the rule applies to the ProcessExecutable, or Command that is occurring as a parent process, a child of another process, or either.

    Block Operation

    9

    Designate whether or not the source ProcessExecutable, or Command will be Blocked or Allowed from making a connection. Checking the box Blocks, while leaving it unchecked Allows the connection.

    Alert Level

    10

    When this rule triggers, designate whether the alert that appears on the Alerts page will be a Low, Medium, or High-level alert.

    Send Email Alerts

    11

    When this rule triggers, designate whether it will send an email alert to all Users that are assigned to the Endpoint Group of the endpoint that this rule triggered on. Email alerts can be configured on the System Configuration | System Settings page. 

    Note: The SMTP server must be configured under System Settings. Emails will be sent to all ZMC users.

    Response Type

    12

    When this rule triggers, designate what response actions ZeroLock will take.

    Do Nothing will simply trigger an alert on the Alerts page where an administrator can either Release the alert or choose to manually Kill & Remediate the triggering connection.

    Suspend will lock the triggering connection but not end it immediately, waiting for an administrator to choose to Release the alert and allow the connection to continue or to Kill & Remediate it.

    Kill will automatically end the connection, but any actions taken by the connection will remain in place.

    Finally, Remediate will both end the connection and remediate any actions taken on the system by restoring the system to an unaltered state using the backup cache.

    Auto Quarantine

    13

    When this rule triggers, designate whether the endpoint will be automatically set to Quarantine until administrator manually Unquarantine the endpoint on the Endpoints page.

  4. Once the Network Access Rule is properly configured, click the Create button at the bottom of the New Policy Rule pop-up menu.
Network Access Policy Rule 2.0.1

Add New Policy

Before implementing a rule onto an endpoint, it must first be applied to a policy.

  1. Navigate to the Control Policies | Policies page.  Then select the Add New Policy button.Add New Policy 2.0.1-3

  2. On the New Policy pop-up menu, give your new policy a name and description. To add the new network access rule, click the Add Rules button.
    Network Access Policy Creation 2.0.1-2
  3. On the Policy Rules menu, select any rules you want to add to the new policy. When all are selected, click the Add Selected button at the bottom. 

    Policy Rule List 2.0.1
  4. The following screen appears when Add Selected is chosen.Network Access Policy with 2 Rules 2.0.1
  5. When all preferred rules have been added to the policy, you can configure what order your lockdown rules will be evaluated. Lockdown rules (File Access, Network Access, and Program Execution rules) are evaluated top-to-bottom, with rules on top resolving actions before moving onto later rules down the chain.
    Similar to a firewall, if an action matches on a lockdown rule that is at the top of the list, it will take the actions specified for that rule and stop evaluating any rules below it. If it does not match, it will pass to the next rule in line until it matches. If no rules match, then the action is allowed.New Policy Rules Reordered 2.0.1

Create a New Configuration Profile

In order to apply a policy to an endpoint, the policy must first be applied to a 
Configuration Profile.

  1. Navigate to the System Configuration | Config Profiles page.  Select Add New Profile.
    Config Profile Add New Profile 2.0.1
     
  2. On the New Configuration Profile pop-up menu you can configure exactly what actions ZeroLock will take for each protection engine. Here, settings can be fine-tuned for Ransomware, Cryptojacking, and Tampering protection, as well as settings for all Hash Rules set to deny based on a SHA-256 hash.

    In order to apply the policy that was created, navigate to the Default Control Policy drop-down menu, and select the preferred policy. Only one policy may be applied to a Configuration Profile at a time. Once complete, select the Create button at the bottom of the menu.
    Config Profile Net Access Creation v3.0.2


Apply to New Profile to an Endpoint

Once a Configuration Profile has been created, it must be applied to an endpoint so the settings can take effect.

  1. Go to Endpoints and select an endpoint that you want to apply the Network Access policy to.  Then, from the Actions drop-down menu, select Set Endpoint Config.
    Endpoint Actions Dropdown 2.0.1

     
  2. On the Set Endpoint Configs pop-up menu, select the created configuration profile from the drop-down menu. Then click the Set Configs button and the new profile has been assigned to Endpoint #2.Set Endpoint Configs 2.0.1
  3. Your endpoint is now properly configured with the desired profile, rules and policies.Endpoint Profile Assigned 2.0.1