PANv11 FE Lab 03
PANv11 FE Lab 03
0 ESSENTIALS
Palo Alto Networks, PAN-OS, WildFire, RedLock, and Demisto are registered trademarks of Palo Alto Networks, Inc. All other marks mentioned herein may
be trademarks of their respective companies.
Lab 3: Managing Firewall Administrator Accounts
Contents
Introduction ................................................................................................................................................ 3
Objective ..................................................................................................................................................... 3
Lab Topology ............................................................................................................................................... 4
Theoretical Lab Topology ............................................................................................................................ 4
Lab Settings ................................................................................................................................................. 5
Lab Guidance............................................................................................................................................... 5
1 Managing Firewall Administrator Accounts – High Level Lab Steps................................................... 6
1.1 Apply a Baseline Configuration to the Firewall .......................................................................... 6
1.2 Create a Local Database Authentication Profile ......................................................................... 6
1.3 Create a Local User Database Account ....................................................................................... 6
1.4 Create an Administrator Account ............................................................................................... 6
1.5 Commit the Configuration .......................................................................................................... 6
1.6 Log in With New Admin Account ................................................................................................ 6
1.7 Configure LDAP Authentication .................................................................................................. 6
1.8 Commit the Configuration .......................................................................................................... 7
1.9 Log in With New Admin Account ................................................................................................ 7
1.10 Configure RADIUS Authentication .............................................................................................. 7
1.11 Commit the Configuration .......................................................................................................... 8
1.12 Log in With New Admin Account ................................................................................................ 8
1.13 Configure an Authentication Sequence ...................................................................................... 8
2 Managing Firewall Administrator Accounts – Detailed Lab Steps...................................................... 9
2.1 Load Lab Configuration ............................................................................................................... 9
2.2 Create a Local Database Authentication Profile ....................................................................... 12
2.3 Create a Local User Database Account ..................................................................................... 14
2.4 Create an Administrator Account ......................................................................................... 16
2.5 Configure LDAP Authentication ............................................................................................ 21
2.6 Configure RADIUS Authentication ........................................................................................ 29
2.7 Configure and Authentication Sequence .............................................................................. 38
Introduction
When you deploy the firewall into your production network, you need to make sure that other
members of your team have administrative access to the device. You want to leverage an existing LDAP
server that maintains account and password information for members of your team. However, your
organization recently merged with another company whose administrative accounts are maintained in
a RADIUS database.
No one has had time yet to migrate all the accounts from RADIUS into LDAP, so you need to configure
the firewall to check both LDAP and RADIUS to authenticate an account when an administrator logs in.
Objective
Lab Topology
Lab Settings
The information in the table below will be needed in order to complete the lab. The task sections
below provide details on the use of this information.
Lab Guidance
You are not required to complete both the High-Level Lab Guide and the
Detailed Lab Guide for each lab. Instead, please select the appropriate section
based on your familiarity with Palo Alto Networks Firewalls.
It is recommended to use this section if you possess significant experience in working with Palo Alto
Networks firewalls. In case you require more comprehensive instructions to achieve the objectives,
please utilize the Detailed-Lab Steps section in Task 2.
Base DN dc=panw,dc=lab
Bind DN cn=admin,dc=panw,dc=lab
• Use the information in the table below to create an LDAP Authentication Profile.
Name LDAP-Auth-Profile
Type LDAP
• Use the information in the table below to create a new administrator account that will be
authenticated by LDAP.
Name adminSally
Port 1812
• Use the information in the table below to create a RADIUS Authentication Profile.
Name RADIUS-Auth-Profile
Type RADIUS
• Use the information in the table below to create a new administrator account that will be
authenticated by RADIUS.
Name adminHelga
It is recommended to use this section if you prefer detailed guidance to complete the objectives for
this lab. It is strongly recommended that you use this section if you do not have extensive experience
working with Palo Alto Networks firewalls.
In this section, you will connect to the Firewall and load the Firewall configuration file.
If you do not immediately see the login page, please wait an additional
1-3 minutes for the Firewall to fully initialize. If needed, refresh the
page.
7. Navigate to Device > Setup > Operations in the web interface and click on Load named
configuration snapshot underneath the Configuration Management section.
8. In the Load Named Configuration window, select edu-210-11.0a-03.xml from the Name drop-down
box and click OK.
9. In the Loading Configuration window, a message will show Configuration is being loaded. Please
check the Task Manager for its status. You should reload the page when the task is completed. Click
Close to continue.
10. Click the Tasks icon located at the bottom-right of the web interface.
11. In the Task Manager – All Tasks window, verify the Load type has been completed. Click Close
12. Click the Commit link located at the top-right of the web interface.
13. In the Commit window, click Commit to proceed with committing the changes.
The commit process takes changes made to the Firewall and copies
them to the running configuration, which will activate all configuration
changes since the last commit.
15. Leave the Palo Alto Networks Firewall open and continue to the next task.
In this section, you will create a local database authentication profile. Local database profiles allow the
firewall to authenticate administrators who need access to the firewall web interface through Captive
Portal or GlobalProtect.
1. In the PA-VM web interface, navigate to Device > Authentication Profile. Click Add at the bottom
of the window.
2. In the Authentication Profile window, under the Authentication tab, enter Local-Database for the
Name, for Type, use the drop-down list to select Local Database.
3. Select the Advanced tab, in the Allow List section, click Add. Select All and click OK.
4. Leave the firewall web interface open to continue with the next task.
In this section, you will create a new entry in the Local User Database on the firewall. This entry will be
for a new team member, adminBob.
1. In the web interface, select Device > Local User Database > Users. In the bottom left corner of the
window, click Add. You may need to use the scroll bar to locate the Local User Database drop
down.
2. In the Local User window, type adminBob for the Name field. Enter Pal0Alt0! for Password and
Confirm Password. Click OK.
3. Leave the firewall web interface open to continue with the next task.
In this task, you will create an administrator account for adminBob. The adminBob account will use the
Local-Database Authentication Profile.
1. In the web interface, select Device > Administrators. Click Add at the bottom of the window.
2. In the Administrator window, enter adminBob for the Name. For the Authentication Profile, select
Local-Database. Click OK.
3. Click the Commit button at the upper right of the PA-VM web interface.
4. In the Commit window, click Commit to proceed with committing the changes.
6. Log out of the firewall web interface by clicking the Logout button in the bottom left corner of the
window.
8. Log back into the firewall as username adminBob, password Pal0Alt0!. Click Log In.
10. Select Monitor > Logs > System. Look for an entry with Type > Auth. You may need to scroll
through the logs to find the auth type.
Note that the entry in the firewall system log indicates that adminBob
was successfully authenticated against the Local-Database.
13. Log back into the firewall with the admin/Pal0Alt0! credentials.
14. Leave the firewall web interface open to continue with the next task.
Your organization uses an LDAP server to maintain a database of users, including network
administrators. Your team of security personnel is growing each month and you want to leverage the
existing LDAP server to authenticate administrators when they attempt to log into the firewall.
The first step in this process is to define an LDAP server profile which contains specific information that
the firewall can use when sending queries for authentication.
1. In the web interface, select Device > Server Profiles > LDAP. At the bottom of the window, click
Add.
2. In the LDAP Server Profile window, enter LDAP Server Profile for the Profile Name. Under the
Server List, click Add. Enter ldap.panw.lab for the Name, 192.168.50.89 for the LDAP Server,
and confirm 389 populates for the Port number.
3. In the Server Settings section, enter dc=panw,dc=lab for Base DN, enter
cn=admin,dc=panw,dc=lab for Bind DN, enter Pal0Alt0! for Password and Confirm Password
and uncheck Require SSL/TLS secured connection. Click OK.
With your LDAP Server Profile in place, you will now create an
Authentication Profile and reference the LDAP Server Profile you just
created.
6. In the Authentication Profile window, type LDAP Auth Profile for the Name. Select LDAP for the
Type and LDAP Server Profile for the Server Profile. Click Advanced.
7. On the Advanced tab, in the Allow List, click Add. Select all and click OK.
9. In the Administrator window, type adminSally for the Name. Select LDAP Auth Profile for the
Authentication Profile. Click OK.
10. Click the Commit link located at the top-right of the web interface.
11. In the Commit window, click Commit to proceed with committing the changes.
12. When the commit operation successfully completes, click Close to continue.
13. Log out of the firewall web interface by clicking the Logout button in the bottom left corner of the
window.
15. Log back into the firewall as username adminSally, password Pal0Alt0!. Click Log In.
17. Select Monitor > System. Look for an entry with Type > Auth. You may need to scroll through the
logs to find the auth type.
Note that the entry in the firewall system log indicates that adminSally
was successfully authenticated against the LDAP Server.
20. Log back into the firewall with the admin/Pal0Alt0! credentials.
21. Leave the firewall web interface open to continue with the next task.
Your organization has recently acquired another company. The newly acquired company maintains all
network administrator accounts in a RADIUS server. You need to incorporate RADIUS authentication
for the firewall so the new network administrators who have joined your team can access the firewall
for management purposes.
For this section, you will configure RADIUS Authentication and test the user adminHelga can login in.
2. In the RADIUS Server Profile window, enter RADIUS Server Profile for the Profile Name. For the
Authentication Protocol, select CHAP. Under the Servers section, click Add. For the server Name
field, enter radius.panw.lab. For the RADIUS Server field, enter 192.168.50.150. Enter
Pal0Alt0! for Secret and Confirm Secret. Leave the Port set to 1812. Click OK.
4. In the Authentication Profile window, enter RADIUS Auth Profile for the Profile Name. For the
Type, select RADIUS. For the Server Profile, select RADIUS Server Profile. Click the Advanced tab.
5. Under the Allow List, click Add. Select all and click OK.
7. In the Administrator window, enter adminHelga for the Name. For the Authentication Profile,
select RADIUS Auth Profile. Click OK.
8. Click the Commit link located at the top-right of the web interface.
9. In the Commit window, click Commit to proceed with committing the changes.
10. When the commit operation successfully completes, click Close to continue.
11. Log out of the firewall web interface by clicking the Logout button in the bottom left corner of the
window.
13. Log back into the firewall as username adminHelga, password Pal0Alt0!. Click Log In.
15. Select Monitor > Logs > System. Look for an entry with Type > Auth. You may need to scroll
through the logs to find the auth type.
Note that the entry in the firewall system log indicates that
adminHelga was successfully authenticated against the RADIUS
Profile.
18. Log back into the firewall with the admin/Pal0Alt0! credentials.
19. Leave the firewall web interface open to continue with the next task.
Since the acquisition, some administrator accounts exist in LDAP and other accounts exist in RADIUS.
With administrator accounts in these two different systems, you need to configure the firewall so that
it can check both external databases when an administrator attempts to log in.
In this section you will accomplish this by creating an Authentication Sequence. The sequence will
instruct the firewall to check an account against LDAP first and then against RADIUS if the account does
not exist in LDAP (or if the LDAP server is unavailable).
2. In the Authentication Sequence window, type LDAP then RADIUS for the Name. Under the
Authentication Profiles, click Add. Select LDAP Auth Profile. Click Add again and select RADIUS
Auth Profile. Click OK.
Note the Move Up and Move Down buttons. These allow you to
change the order of the Authentication Profiles if necessary. In this
example, the firewall will use the LDAP-Auth-Profile first when an
administrator logs in to attempt authentication; if the user account
does not exist in LDAP (or if the LDAP server is unavailable), the
firewall will use the RADIUS-Auth-Profile to attempt authentication.
3. Click the Commit link located at the top-right of the web interface.
4. In the Commit window, click Commit to proceed with committing the changes.