%20(500%20x%20162%20px)(1).png)
Lab 3: SSL Scanning Lab Activity
SSL Scanning Lab Activity
Welcome to Lab 3. In this lab, we will be configuring the SSL scanning job to search a network for certificates located on an endpoint. In this lab, we are going to define a network to scan within the lab environment. Since our lab is a single server, we are going to borrow some address space from the internet to scan.
SSL Scan Job Creation instructions:
Navigate to Locations > SSL Discovery.
Click New Network on the ribbon menu.
Configure your SSL Network Definition with the following settings:
Configuration | Value |
Basic Tab |
|
Name | Azure Websites |
Description | This is a subset of networks supporting the azurewebsites.net domain |
Orchestrator Pool | Default Agent Pool |
Discovery Schedule | Interval every 5 minutes |
Monitoring Schedule | Interval every 1 hour |
Notification Recipients | email@keyfactor.lab |
Network Ranges Tab |
|
Type | Network Notation |
CIDR Block | 168.62.48.183/24:443 then click Add |
Click the Validate button to ensure the ranges entered are in the correct format.
Click Save to close the SSL Network Definition.
At this point, our job has been scheduled. You can refresh the table to see an update on the scan's progress. Once the status is updated, we can find the results in the Orchestrators > Jobs menu under the Job History tab.
Note: This scanning job will be saved, but you receive errors (visible in the notification bell in the top right corner) stating “Orchestrator Pool Empty” and “No Capable Orchestrators”.
Q: Why is the scanning job failing in our lab environment?
A: We have not installed the Keyfactor Universal Orchestrator. For now, let's disable our scanning job and we will revisit this step when we install the orchestrator.