>
    Create a Security Policy Rule
    Focus
    Download PDF
    Focus
    1. Home
    2. Network Security
    3. Network Security: Security Policy
    4. Security Rules
    5. Create a Security Policy Rule
    Download PDF
    Network Security

    Create a Security Policy Rule

    Table of Contents

    Create a Security Policy Rule

    Learn how to create a security rule.
    Where Can I Use This?What Do I Need?
    • NGFW (Cloud Managed)
    • NGFW (PAN-OS & Panorama Managed)
    • Prisma Access (Managed by Strata Cloud Manager)
    • Prisma Access (Managed by Panorama)
    Check for any license or role requirements for the products you're using.
    Security security rules allow you to enforce rules and take action, and can be as general or specific as needed. The security rules are compared against the incoming traffic in sequence, and because the first rule that matches the traffic is applied, the more specific rules must precede the more general ones. For example, a rule for a single application must precede a rule for all applications if all other traffic-related settings are the same.
    For traffic that doesn’t match any user-defined rules, the default rules apply. The default rules—displayed at the bottom of the security rulebase—are predefined to allow all intrazone traffic (within the zone) and deny all interzone traffic (between zones). Although these rules are part of the predefined configuration and are read-only by default, you can Override them and change a limited number of settings, including the tags, action (allow or deny), log settings, and security profiles.
    After you create a rule, you can track it in your rulebase and view security rule usage to determine when and how many times traffic matches the Security rule to determine its effectiveness. As your rulebase evolves, change and audit information can get lost over time unless you archived this information at the time the rule is created or modified. You can Enforce Security Rule Description, Tag, and Audit Comment to ensure that all administrators enter audit comments so that you can view the audit comment archive and review comments and configuration log history and can compare rule configuration versions for a selected rule. Together, you now have more visibility into and control over the rulebase.

    Create a Security Policy Rule (Strata Cloud Manager)

    Learn how to create a security rule.
    To ensure that end users authenticate when they try to access your network resources, authentication is evaluated before Security policy. For details, see Authentication.
    1. Add a rule. Select ManageConfigurationNGFW and Prisma AccessSecurity ServicesSecurity PolicyAdd Rule and build your rule by configuring the following rulecomponents. Components marked with an asterisk(*) are mandatory.
    2. SectionElementDetails
      General*NameGive your rule a name the tells other administrators what it does.
      DescriptionYou can give your rule a detailed description of the rule's intent.
      TagYou can add tags to your rules to group them using keywords or phrases.
      ScheduleYou can limit a security rule to specific times using a schedule.
      Match CriteriaSourceDefine the matching criteria for the source fields in the packet.
      • Select a *Zone.
      • Specify source IP *Addresses or leave the value set to Any.
      • Specify source *Users or leave the value set to Any. You can select Users to enforce policy for individual users or a group of users. If you're using GlobalProtect™ with host information profile (HIP) enabled, you can also base the policy on information collected by GlobalProtect. For example, the user access level can be determined from the HIP that informs your environment about the user's local configuration. The HIP information can be used for granular access control based on the security programs that are running on the host, registry values, and many other checks such as whether the host has antivirus software installed.
      If you decide to Negate a region as a source address, ensure that all regions that contain private IP addresses are added to the source address to avoid connectivity loss between those private IP addresses.
      DestinationDefine the destination zone or destination address for the traffic.
      • Select a *Zone.
      • Specify source IP *Addresses or leave the value set to Any.
      If you decide to Negate a region as the destination address, ensure that all regions that contain private IP addresses are added to the destination addresses to avoid connectivity loss between those private IP addresses.
      As a best practice, use address objects as the destination address to enable access to only specific servers or specific groups of servers especially for commonly exploited services, such as DNS and SMTP. By restricting users to specific destination server addresses, you can prevent data exfiltration and command-and-control traffic from establishing communication through techniques such as DNS tunneling.
      Application / ServiceSpecify the application that the rule will allow or block. Add the Application you want to safely enable. You can select multiple applications or you can use application groups or application filters. Keep the Service set to Application Default to ensure that any applications that the rule allows are allowed only on their standard ports. An administrator can also use an existing App-ID signature and customize it to detect proprietary applications or to detect specific attributes of an existing application. Custom applications are defined in ObjectsApplications.
      As a best practice, always use application-based Security policy rules instead of port-based rules and always set the Service to application-default unless you're using a more restrictive list of ports than the standard ports for an application.
      URL Category / Tenant Restriction(Optional) Specify a URL category as match criteria for the rule. Select URL Category or Tenant Restriction to specify a specific TCP and/or UDP port number, a URL category, a tenant restriction as match criteria in the security rule. If you select a URL category, only web traffic will match the rule and only if the traffic is destined for that specified category.
      ActionsActionDefine what Action you want taken for traffic that matches the rule. See Security Rule Actions for a description of each action.
    3. Configure the log settings.
      • By default, the rule is set to Log at Session End. You can disable this setting if you don’t want any logs generated when traffic matches this rule or you can select Log at Session Start for more detailed logging.
      • Select a Log Forwarding profile.
      As a best practice, don't select the check box to Disable Server Response Inspection (DSRI). Selecting this option prevents the inspection of packets from the server to the client. For the best security posture, both the client-to-server flows and the server-to-client flows must be inspected to detect and prevent threats.
    4. Attach security profiles to scan all allowed traffic for threats.
      Make sure you create best practice security profiles that help protect your network from both known and unknown threats.
      In ActionsProfile Group, select a Profile Group from the drop-down to attach to the rule.
    5. Select Save to save the security rule, then Push Config to your devices.
    6. Monitor the security rule usage status and determine the effectiveness of the security rule, and optimize if needed.

    Create a Security Policy Rule (PAN-OS & Panorama)

    Learn how to create a security rule.
    To ensure that end users authenticate when they try to access your network resources, authentication is evaluated before Security policy. For details, see Authentication Policy.
    The interface includes components for defining Security rules. Familiarize yourself with them before you get started.
    1. (Optional) Delete the default Security rule.
      By default, the firewall includes a security rule named rule1 that allows all traffic from Trust zone to Untrust zone. You can either delete the rule or modify the rule to reflect your zone naming conventions.
    2. Add a rule.
      1. Select PoliciesSecurity and Add a new rule.
      2. In the General tab, enter a descriptive Name for the rule.
      3. Select a Rule Type.
    3. Define the matching criteria for the source fields in the packet.
      1. In the Source tab, select a Source Zone.
      2. Specify a Source IP Address or leave the value set to any.
        If you decide to Negate a region as a Source Address, ensure that all regions that contain private IP addresses are added to the Source Address to avoid connectivity loss between those private IP addresses.
      3. Specify a Source User or leave the value set to any.
    4. Define the matching criteria for the destination fields in the packet.
      1. In the Destination tab, set the Destination Zone.
      2. Specify a Destination IP Address or leave the value set to any.
        If you decide to Negate a region as the Destination Address, ensure that all regions that contain private IP addresses are added to the Destination Address to avoid connectivity loss between those private IP addresses.
        As a best practice, use address objects as the Destination Address to enable access to only specific servers or specific groups of servers especially for commonly exploited services, such as DNS and SMTP. By restricting users to specific destination server addresses, you can prevent data exfiltration and command-and-control traffic from establishing communication through techniques such as DNS tunneling.
    5. Specify the application that the rule will allow or block.
      As a best practice, always use application-based security rules instead of port-based rules and always set the Service to application-default unless you're using a more restrictive list of ports than the standard ports for an application.
      1. In the Applications tab, Add the Application you want to safely enable. You can select multiple applications or you can use application groups or application filters.
      2. In the Service/URL Category tab, keep the service set to application-default to ensure that any applications that the rule allows are allowed only on their standard ports.
    6. (Optional) Specify a URL category as match criteria for the rule.
      In the Service/URL Category tab, select the URL Category.
      If you select a URL category, only web traffic will match the rule and only if the traffic is destined for that specified category.
    7. Define what action you want the firewall to take for traffic that matches the rule.
      In the Actions tab, select an Action. See Security Rule Actions for a description of each action.
    8. Configure the log settings.
      • By default, the rule is set to Log at Session End. You can disable this setting if you don’t want any logs generated when traffic matches this rule or you can select Log at Session Start for more detailed logging.
      • Select a Log Forwarding profile.
      As a best practice, don't select the check box to Disable Server Response Inspection (DSRI). Selecting this option prevents the firewall from inspecting packets from the server to the client. For the best security posture, the firewall must inspect both the client-to-server flows and the server-to-client flows to detect and prevent threats.
    9. Attach security profiles to enable the firewall to scan all allowed traffic for threats.
      Make sure you create best practice security profiles that help protect your network from both known and unknown threats.
      In the Actions tab, select Profiles from the Profile Type drop-down and then select the individual security profiles to attach to the rule.
      Alternatively, select Group from the Profile Type drop-down and select a security Group Profile to attach.
    10. Click Commit to save the security rule to the running configuration on the firewall.
    11. To verify that you have set up your basic Security policies effectively, test whether your security rules are being evaluated and determine which security rule applies to a traffic flow.
      The output displays the best rule that matches the source and destination IP address specified in the CLI command.
      For example, to verify the security rule that will be applied for a server in the data center with the IP address 208.90.56.11 when it accesses the Microsoft update server:
      1. Select DeviceTroubleshooting, and select Security Policy Match from the Select Test drop-down.
      2. Enter the Source and Destination IP addresses.
      3. Enter the Protocol.
      4. Execute the Security policy match test.
    12. After waiting long enough to allow traffic to pass through the firewall, View Security Rule Usage to monitor the security rule usage status and determine the effectiveness of the policy rule.

    © 2024 Palo Alto Networks, Inc. All rights reserved.