Cybersecurity Foundation Lab 5: Using Two-Factor Authentication To Secure The Firewall
Cybersecurity Foundation Lab 5: Using Two-Factor Authentication To Secure The Firewall
Palo Alto Networks and the Palo Alto Networks logo are trademarks or registered trademarks of Palo Alto Networks, Inc.
Lab: 5 Using Two-Factor Authentication to secure the Firewall
Contents
Introduction ........................................................................................................................ 3
Objective ............................................................................................................................. 3
Lab Topology ....................................................................................................................... 4
Lab Settings ......................................................................................................................... 5
5 Using Two-Factor Authentication to Secure the Firewall ........................................... 6
5.0 Load Lab Configuration ....................................................................................... 6
5.1 Create Local User Account ................................................................................ 11
5.2 Generate Certificates......................................................................................... 12
5.3 Create a Certificate Profile ................................................................................ 15
5.4 Export Certificate and Commit .......................................................................... 18
5.5 Test Connectivity and Import Certificate on the Client .................................... 21
Introduction
In this lab, you will configure the Firewall to use two-factor authentication using a
certificate, along with a username and password.
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.
5. You will see a “Your connection is not private” message. Click on the ADVANCED
link.
8. In the web interface, navigate to Device > Setup > Operations and click on Load
named configuration snapshot underneath the Configuration Management
section.
10. 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.
11. Click the Tasks icon located at the bottom-right of the web interface.
12. In the Task Manager – All Tasks window, verify the Load type has successfully
completed. Click Close.
13. Click the Commit link located at the top-right of the web interface.
14. In the Commit window, click Commit to proceed with committing the changes.
15. When the commit operation successfully completes, click Close to continue.
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.
In this section, you will create a local user account, lab-user. This account will be used
for authentication against the Firewall.
2. In the Administrator window, type lab-user in the Name field. Then, type
Pal0Alt0 in the Password and Confirm Password fields. Finally, click the OK
button.
In this section, you will generate two certificates. The first is a self-signed Root
Certificate Authority (CA) certificate, which is the top-most certificate in the certificate
chain. The Firewall can use this certificate to automatically issue certificates for other
uses. In this lab, you will use the Root CA certificate to generate a certificate for use on
the Client machine that is associated with the local user account, lab-user.
3. In the Generate Certificate window, type lab-local in the Certificate Name field.
Then, type 192.168.1.254 in the Common Name field. Next, click the Certificate
Authority checkbox. Finally, click the Generate button.
6. In the Generate Certificate window, type lab-user in the Certificate Name field.
Then, type lab-user in the Common Name field. Next, select lab-local in the
Signed By dropdown. Finally, click the Generate button.
In this section, you will create a certificate profile. A certificate profile defines user and
device authentication for multiple services on the Firewall. The profile specifies which
certificates to use, how to verify certificate revocation status, and how that status
constrains access. In this lab, the certificate profile is created to tell the Firewall to use
the common-name of the certificate as a username. Then, you will tell the Firewall to
use this Certificate Profile to authenticate users.
1. Navigate to Device > Certificate Management > Certificate Profile > Add.
Notice the Username Field, when set to Subject, it will use “common-
name” as the default. The Firewall will now use the “common-name”
as the username. The lab-user certificate you generated earlier has a
common-name of lab-user and will therefore use lab-user to
authenticate the client machine.
This maps back to the lab-local CA certificate you created earlier, and
the Firewall will use this to verify the authenticity of the client
supplied certificate, lab-user.
6. Click the gear icon on the Authentication Settings section, located in the center.
In this section, you will export the lab-user certificate you generated on the Firewall.
Then, you will commit changes, causing the Firewall to start using certificates for
authentication.
2. Select the lab-user certificate and click on the Export Certificate button.
3. In the Export Certificate - lab-user window, select Encrypted Private Key and
Certificate (PKCS12) in the File Format dropdown. Then, type paloalto for the
Passphrase and Confirm Passphrase fields, then click on the OK button.
4. In the Save File window pop-up, verify the name of cert_lab-user.p12 is correct
in the Name field, verify the .p12 file is being saved in the Downloads folder, and
click Save.
5. Click the Commit link located at the top-right of the web interface.
6. In the Commit window, click Commit to proceed with committing the changes.
Notice the warning about the Web server being restarted, this is
because of the authentication changes you made. You will need to
click the Close button when it gets to 99%, since the web server is
restarting, you will not see it get to 100%.
In this section, you will test connectivity to the Firewall. Then, you will import the lab-
user certificate on the Client machine and try again.
3. You will see a “Your connection is not private” message. Click on the ADVANCED
Link.
5. You will see a “400 Bad Request - No Required SSL certificate was sent” message.
Click the X in the upper-right to close Chromium.
Notice you get a HTTP 400 Bad Request error. This is because the lab-
user certificate is not installed on the Client machine. The Firewall
administrators are not allowed to login unless they have the
certificate installed and have an account and password. These two
factors make up the Two-Factor Authentication in this lab.
8. Scroll down and click on the Advanced settings in Chromium and then click on
Manage Certificates.
10. In the Open File window, select cert_lab-user.p12 and then click the Open
button.
11. In the Enter your certificate password window, enter paloalto and click OK.
12. In the Manage Certificates window, expand the org-lab-user view and verify the
lab-user certificate has been imported.
15. In the Chromium address field, type https://192.168.1.254 and press Enter.
16. In the Select a certificate window, verify the lab-user certificate is selected and
click OK.
17. You will see a “Your connection is not private” message. Click on the ADVANCED
link).
19. The Firewall login window will be displayed. Type Pal0Alt0 for the Password
field. Then, click the Log In button.
21. You are now at the Palo Alto Networks Web GUI, logged on as lab-user. Notice
the username in the lower-left.
22. The lab is now complete; you may end the reservation.