Lab 3: Malicious Users

The following lab tasks will guide you the configuration of the Malicious User Configuration which can be used to implement a variety of security controls.

Expected Lab Time: 15 minutes

Task 1: Creating a User Identification Policy

In this task you will build a user identification policy which will be the basis of identifying clients/users for machine learning driven analysis for malicious user mitigation and actions.

  1. Within Web App & API Protection in the F5 Distributed Cloud Console, Manage > Load Balancer > HTTP Load Balancers and use the Action Dots and click Manage Configuration.

  2. Click Edit Configuration in the top right-hand corner.

    lab001

    lab002

  3. Click Common Security Controls in the left-hand navigation and locate User Identification.

  4. Click the drop-down under User Identifier and select User Identification Policy from the list.

    lab003

  5. Click the dropdown for User Identification Policy and select Add Item.

    lab004

  6. In the User Identification window, in the Metadata section enter user-id for the Name and then click configure under User Identification Rules.

    lab005

  7. In the resulting window for User Identification Rules, click Add Item.

    lab006

  8. In the User Identification Rule window click the drop-down for Identifier Type.

    Select TLS Fingerprint and click Apply.

    lab007

  9. Returning to the window for User Identification Rules, observe the prior selection and click Add Item.

    lab008

  10. In the User Identification Rule window click the drop-down for Identifier Type. Select Client IP Address and click Apply. (It should be already selected)

    lab009

  11. Review the two User Identification Rules and click Apply.

  12. Returning to the User Identification window, note that User Identification Rules are now Configured and click Continue.

    lab010

    lab011

Task 2: Enable Malicious User Detection and Mitigation Actions

In this task you will leverage the user identification policy just built and then enable malicious user detection and create a malicious user mitigation and challenge.

  1. Click Common Security Controls in the left-hand navigation.

  2. Click the dropdown for Malicious User Detection and select Enable.

    lab012

  3. Click the dropdown for Malicious User Mitigation And Challenges and select Enable.

    lab013

  4. Click the dropdown for Malicious User Mitigation Settings and select Custom.

    lab014

  5. Click the dropdown for Custom. Observe the two other policies.

    shared/lab-sec-user-mitigation

    ves-io-shared/ves-io-default-malicious-user-mitigation

    Note

    Using shared namespace Malicious User Mitigation provides the ability to use API-updated mitigation controls to implement common service security across multiple resources.

  6. Select Add Item.

    lab015

  7. In the Metadata section enter security-user-mitigation for the Name and then click Add Item under Rules.

    lab016

  8. In the resulting window, click the dropdown for Threat Level and select Low.

  9. Click the dropdown for Action and select Java Script Challenge.

  10. Select Apply.

    lab017

  11. In the Malicious User Mitigation window review the rule just created and click Add Item again.

    lab018

  12. In the resulting window, click the dropdown for Threat Level and select Medium.

  13. Click the dropdown for Action and select Captcha Challenge.

  14. Select Apply.

    lab019

  15. In the Malicious User Mitigation window review the rules just created and click Add Item again.

    lab020

  16. In the resulting window, click the dropdown for Threat Level and select High.

  17. Click the dropdown for Action and select Block Temporarily.

  18. Select Apply.

    lab021

  19. Observe the three Rules created and select Continue.

    lab022

  20. Note the updated Malicious User Mitigation and Challenges section and click on Other Settings in the left-hand navigation or scroll to the bottom of the window and click the Save and Exit button.

    lab023

    lab024

End of Lab 3: This concludes Lab 3, feel free to review and test the configuration.

A Q&A session will begin shortly to conclude the overall lab.

labend