Palo Alto Networks firewall detects traffic from an endpoint that matches a configured security policy using the endpoint’s auth table entry. It determines the role(s) associated with that user and allows or denies the traffic based on the actions configured in the security policy.
Policy rules on the firewall use security zones to identify the source and the destination of the traffic. The data traffic flows freely within a zone and not between different zones until you define a security policy rule that allows it. To enable User-ID enforcement, you must enable User Identification on both inbound and outbound zones traversed by the end-user traffic.
To enable User Identification:
1.Select Palo Alto Networks > Network > Zones.
2.For each zone that serves as an inbound or outbound zone for enforced traffic, click the zone name (For example, trust, untrust, and so on).
3.Select Enable User Identification and click OK.
Provisioning of Resource Access Policies from PPS to the Palo Alto Networks Firewall Enforcer is not supported. You must configure the required security policies on the firewall.
Dynamic address groups allow you to create policy that automatically adapts to changes-adds, moves, or deletions of servers. It also enables the flexibility to apply different rules to the same server based on its role on the network or the different kinds of traffic it processes.
To configure a dynamic address group:
1.Select Palo Alto Networks > Objects > Address Groups.
2.Click Add and enter a Name and a Description for the address group.
3.Select Type as Dynamic. Define the match criteria. You can select dynamic and static tags as the match criteria to populate the members of the group.
4.Enter the role name of the users. The role name in the Match section should match the roles that are configured in PPS.
Dynamic discovery of users and their roles is not supported on the Palo Alto Networks firewall.
Security policies protect network assets from threats and disruptions and aid in optimally allocating network resources for enhancing productivity and efficiency in business processes. On the Palo Alto Networks firewall, security policies determine whether to block or allow a session based on traffic attributes such as the source and destination security zone, the source and destination IP address, the application, user, and the service.
To configure security policies associated with dynamic address groups:
1.Select Palo Alto Networks > Policies > Security.
2.Click Add to create a new security policy rule. In the Source Address tab, select the previously-configured address group, as shown in figure.
3.In the User tab, enable known-user.
When the known-user is enabled, the resource access is revoked immediately once the user disconnects from PPS.
4.Configure the other options to meet your security requirements. Traffic from the endpoint is allowed or blocked based on the action chosen under the Action tab.
5.Click Commit to complete the configuration. The completed security configuration on the Palo Alto Networks firewall is shown below.
PAN device certificate validation enhances the security between PPS and the PAN device. It allows PPS to verify whether the server certificate is from a trusted source. This topic describes how to configure the PPS for validating device certificates, creating certificates on PAN, and checking the validity of the certificate.
To create a Certificate Signing Request (CSR) for sending to public third-party Certificate Authority (like Verisign, Globalsign, Entrust, and so on). For more information, see https://www.paloaltonetworks.com/documentation/60/pan-os/pan-os/certificate-management/obtain-certificates
1.Select Device > Certificate Management > Certificates > Device Certificates.
2.Enter a Certificate Name (save this name for later).
3.In the Common Name field, enter the IP address of the interface where you will configure the service that will use this certificate.
4.Select the Certificate Authority (CA) check box for self-signed root CA certificate. Exporting the CSR and Importing the Signed Certificate are not applicable for self-signed certificates.
Uncheck the Certificate Authority check box if you are using enterprise CA, or trusted third-party CA certificates.
5.Complete the remaining details such as Country, Organization, and so on. Check with the Certificate Authority (CA) about their requirements for Certificate Attribute formatting and criteria.
Ensure that the SSL/TLS service profile is enabled while creating the server certificate.
Once the CSR is created, you must export the CSR to a third-party CA for signature.
To export the CSR:
1.Click the check box next to the Certificate Name.
2.Click Export and save the file.
3.Send the exported CSR to a third-party Certificate Authority. The CA will respond with a signed certificate.
Once the CA responds with the signed certificate, you must import the signed certificate from the certificate authority.
To import the signed certificate:
1.Note the name, including capitalization, of the certificate to import. (This must match the CSR request from above.)
3.In the Import Certificate dialog, type the name of the pending certificate. It must match exactly.
4.Go to the signed certificate received from the Certificate Authority and click OK.
5.Do not click the Import Private Key check box.
6.Depending on the certificate authority used, it may be necessary to chain the intermediate certificate with the server certificate and import it before completing this step.
You can use the Trusted Server CAs page to import the trusted root certificate.
To configure device certificate verification:
1.Select System > Trusted Server CAs > Import Trusted Server CA.
2.Click Browse and select the certificate file.
3.Click Import Certificate. The Trusted Server CA page appears.
4.Verify if the certificate is imported successfully and click Done.
5.Click Configuration > Certificates > Trusted Server CAs and verify that the certificate is from a trusted source.