Ridgebot Security Automated Penetration Testing

Network > Data Exfiltration Test tab, the Server and Client Configurations are shown. By default, RidgeBot uses the HTTP server hosted by the Ridge Security Data Center located in the United States. If a RidgeBot deployment does not have internet access or you choose to host your own server, the Data Exfiltration server must have a network connection accessible by RidgeBot. To set up your own server, first download the BlindMonitor server program by clicking the “Download the server program”, then install the program. When done, specify values for the server in the RidgeBot configuration. Figure 108: Data Exfiltration Test Configuration Configure the server with the same information as in the BlindMonitor configuration and click “Apply” to save the parameters. Update the HTTP Service Address and TCP Service Address in RidgeBot’s Client Configuration. Select Test to verify communication between the client and the BlindTest Service. The communication test passes if the configuration is set up correctly. Click “Save”. Page 119 of 147 RidRgeid Sgec Suercituyr Titeyc Thencohlnoogylo Ignyc .I n |c . w| w ww.rwid.greidsgeecsuercituyr.iatiy .aiFigure 109: Data Exfiltration Client Configuration Test Note: • Ridge security provides a BlindMonitor server at 66.220.31.40. RidgeBot will use this server to validate data exfiltration from the target during exploitation. • Only the Blind Monitor HTTP server program provided as a download from the RidgeBot GUI is compatible with RidgeBot. Starting in version 4.2, RidgeBot has a built-in blind monitor using port 40001. The internal blind monitor does not support DNS lookup. Page 120 of 147 RidRgeid Sgec Suercituyr Titeyc Thencohlnoogylo Ignyc .I n |c . w| w ww.rwid.greidsgeecsuercituyr.iatiy .aiConfiguring the Bind Domain The Bind Domain is used as RidgeBot’s internal DNS service. To assign an IP address to a host name, select the Domain Name and enter the information in the dialog box. Figure 110: Bind Domain Configuration Connection Test RidgeBot provides Ping and Traceroute tools to diagnose network problems. To use the tools, follow these steps: Page 121 of 147 RidRgeid Sgec Suercituyr Titeyc Thencohlnoogylo Ignyc .I n |c . w| w ww.rwid.greidsgeecsuercituyr.iatiy .ai1. In the Navigation Bar, mouse over the System Settings icon, and select Connection Test from the drop- down menu. 2. Under the Ping tab, enter an IP address to ping the target, and under the Traceroute tab, enter values for the parameters to trace a route to a target. 3. Tip: Use traceroute to test if a target network port is open. For example, use traceroute to check if RidgeBot can reach the license server on port 8001. User Log The User Log contains a history of the activities performed by RidgeBot admin users, such as actions taken, configuration operations, and task operations. To view the User Log, follow these steps: • In the Navigation Bar, mouse over the System Settings icon, and select User Log from the drop-down menu. • The User Log entries are displayed on the page. To search for specific log entries, enter a keyword into the search text box and then search. System Usage RidgeBot system information is collected and shown in the System Log dashboard, including CPU, memory, disk and network traffic information. To view the system information, on the Navigation Bar, mouse over the System Settings icon, and select System Usage from the drop-down menu. All system information is shown in graphical format. Page 122 of 147 RidRgeid Sgec Suercituyr Titeyc Thencohlnoogylo Ignyc .I n |c . w| w ww.rwid.greidsgeecsuercituyr.iatiy .aiFigure 111: System Usage Graphical Display Disk space is automatically managed by RidgeBot. When a task or a backup file is deleted, RidgeBot cleans up the data and frees up the associated disk space. RidgeBot Disk Usage: • System: 14GB • Task: Approximately 250MB. Actual disk usage depends on the number of targets and the results of the task. Backing Up Configurations and Logs RidgeBot’s configuration backup allow user to create a restore point of RidgeBot settings and task information. When user creates a restore point, RidgeBot will back up all the settings, scenarios, tasks, assets, and reports into a configuration backup file. User can restore the RidgeBot back to the same restore point as needed. Here are some rules governing the back configuration feature: Page 123 of 147 RidRgeid Sgec Suercituyr Titeyc Thencohlnoogylo Ignyc .I n |c . w| w ww.rwid.greidsgeecsuercituyr.iatiy .ai1. The backup and restore configuration file can only be applied to the same RidgeBot. User can delete, restore and download the configuration file. 2. The restore configuration should be applied to RidgeBot that has the same software version as the backup configuration (Note: to find the configuration file software version, check the configuration file date and Update History) 3. If RidgeBot has been upgraded to a newer software version, it is not advised to restore RidgeBot using configuration backup from an older version. RidgeBot backup log is a snapshot of RidgeBot system logs. This log does not contain the target test data, only its IP address as an exception. This log is useful to assist Ridge Security engineer to do troubleshooting. RidgeBot’s configurations and backup logs can be backed up periodically. You can download or delete past backups. On the Navigation Bar, mouse over the System Settings icon, and select Backup from the drop-down menu. To back up a configuration immediately, click the Backup Now button. When it has completed, a backup entry is added to the backup list. To schedule automatic backups, click on the Automatic Backup option to select Weekly or Monthly. The backup is performed at the specified time and completed backup entries are displayed in the backup list on the page. To download a backed-up configuration, click Download in the Action column. To restore the system to a backed-up configuration, click Restore in the Action column. To delete multiple backup entries, select the checkboxes of the entries to be deleted in the backup list, and then click the delete button in the upper right corner. To search for a specific backup entry, enter a keyword into the Search text box at the upper right corner of the page, and then click the search button. You can use similar steps in the Log Backup section of the same page to back up, download or delete user logs. Dictionary: Modifying Contents of the System Dictionary The System Dictionary page contains the dictionary of username and password for different service types. The dictionary only has a small subset of commonly used username and password. RidgeBot will use the credential from the appropriate dictionary during a brute-force attack. Ridgebot supports two type brute-force password matching options: password guessing or password spray. Password guessing method is to match one username with many passwords. Password spray method is to match one password with many usernames. The dictionary service type can be selected in a Task’s Exploitation configuration page. The service type option is shown based on the selected scenario. The below screenshot is an example of the service type options from a Full Penetration scenario. Page 124 of 147 RidRgeid Sgec Suercituyr Titeyc Thencohlnoogylo Ignyc .I n |c . w| w ww.rwid.greidsgeecsuercituyr.iatiy .aiThe Category pull-down menu provides access to specific dictionaries: All, username, password, URL, and Subdomain. Figure 112: System Dictionary Display To modify the contents in the System Dictionary, follow these steps: Page 125 of 147 RidRgeid Sgec Suercituyr Titeyc Thencohlnoogylo Ignyc .I n |c . w| w ww.rwid.greidsgeecsuercituyr.iatiy .ai1. On the Navigation Bar, mouse over the System Settings icon, and select Dictionary from the drop-down menu. The Dictionary page is displayed. 2. Click the Category drop-down menu, and filter the dictionary contents by selecting the category you’re interested in. Detailed contents of the selected category are then listed on the page. 3. From the table, click Edit on the far right of the entry you want to change, then the Edit Dictionary dialog box is shown. 4. Click the Upload File button, select the appropriate content file and then click Save. The file type of the uploaded file must be in .txt in UTF-8 format, and each line in the file may not exceed 100 characters. Note: Users are highly recommended to update these dictionaries with the commonly used credentials in their organization. About Information On the Navigation Bar, mouse over the System Settings icon, and select About from the drop-down menu. The display shows RidgeBot product, module and quota information, and allows you to do an offline upgrade as well as adding a license file. About: Managing Your License A license is required to use RidgeBot. This section discusses how to manage the license files and the license server. Importing a License File Use one of the following methods to import a license file into the system: 1) At the bottom of the About page, drag the license file into the authentication file area. 2) At the bottom of the About page, click to choose an authentication file. Page 126 of 147 RidRgeid Sgec Suercituyr Titeyc Thencohlnoogylo Ignyc .I n |c . w| w ww.rwid.greidsgeecsuercituyr.iatiy .aiFigure 113: Importing a License File Changing the IP address of the License Server To change the IP of the license server, follow these steps: 1. On the Navigation Bar, mouse over the System Settings icon, and select About from the drop- down menu. 2. If you click the Edit icon of the License Server, the text box becomes editable. Figure 114: Changing the License Server 3. Enter the new IP address or URL in the text box. Caution: You should not change the license server URL. Port 8001 on the License Server is required to be opened. RidgeBot cannot run a new task if it is unable to communicate with the License Server on port 8001, except when it is deployed in the appliance offline mode. The little dot to the right of the Edit icon shows the connection status of the License Server: • Green: Connect to the license server • Red: Disconnect from the license server Note: User can verify the license server communication in RidgeBot management console using the “check-license” command. See the latest version of RidgeBot Deployment Quick Start Guide for more detail. Migrating a License License migration is used to transfer a license from one RidgeBot to another RidgeBot. User can request a license migration from one RidgeBot to another RidgeBot via the online RidgeBot license request in the Partner Portal. License migration policy will be shown in the License migration policy section. To migrate a license, follow these steps: 1. On the Navigation Bar, mouse over the System Settings icon, and select About from the drop-down menu. 2. Click the License Migration link to export the current license file. Page 127 of 147 RidRgeid Sgec Suercituyr Titeyc Thencohlnoogylo Ignyc .I n |c . w| w ww.rwid.greidsgeecsuercituyr.iatiy .aiFigure 115: Export the License File for License Migration 3. Send the exported license file (ridgebot.lic) to the Ridge Security Support team for them to generate a new license file that includes the remaining quota from your exported license. 4. Import the new license file into the system. Note: The system is disabled after you export the license. You can access any existing task data but cannot create a new task. The system is re-enabled after a new license file is imported. Exporting License Usage Information The license usage function exports a report on your current license quota usage, including the time, as well as IP address or URL that was executed. To export license usage information, click the License Usage Export link on the About page. A usage_info.csv file is downloaded to your desktop. The usage info file includes the following information: • id: The identifier. • timestamp: The timestamp in Unix format with a link to the conversion tool: https://www.epochconverter.com/ • target: The target, in either IP or FQDN format. • target_type: In IP or Web format. • task name: The task’s name. • status: 1 or -1: a. 1 indicates this target is valid and does not require additional license quota if the task is restarted. This is subject to the restriction of the Pro-X license or End-User Annual Subscription License. b. -1 indicates this target is now invalid and requires a new license quota if the task is restarted. Page 128 of 147 RidRgeid Sgec Suercituyr Titeyc Thencohlnoogylo Ignyc .I n |c . w| w ww.rwid.greidsgeecsuercituyr.iatiy .aiLicense Type RidgeBot supports three different license types: 1) MSV – This license is a single use for MSSP. The license is a one-time used. It is consumed once the task is completed and does not have a 14-days grace period . This MSV license type has a one-year expiration date for the unused license. 2) ProX – This license is a single use for MSSP that has two 14-days test windows and a time limit consumption model. A task will trigger the ProX license first test window and this test window will expire in 14 days as the license “first use”. This license will be consumed after the completion of the task using the same IP or URL in the 2nd test window within 6 months or the license will expire in 6 months after the “first use”. The unused ProX license does not have an expiration date. Example of the ProX license and the quota in RidgeBot “about” page Page 129 of 147 RidRgeid Sgec Suercituyr Titeyc Thencohlnoogylo Ignyc .I n |c . w| w ww.rwid.greidsgeecsuercituyr.iatiy .aiExample of a task that uses the web license on the 1st test window 3) End User Annual subscription – This license is an annual subscription for End User only. This license allows unlimited testing on the same IP or URL within the subscription period. Note: MSSP is Managed Security Service Provider License Migration policy ProX Ridgebot license migration policy 1) ProX license can be transferred from the original RidgeBot to another RidgeBot per user request. The license issue to the new RidgeBot will be referred to as migrated license. Since ProX license is based on usage or count, the migrated license will have the original license term and condition and only has the remaining or unused license quota from the original RidgeBot. License count that has been used are not transferred. The original license will be invalidated 2) ProX license does not apply to de-commissioned asset. End User Annual subscription (EUAS) license migration policy 1) EUAS license transfers from the original RidgeBot to a new RidgeBot. End User annual subscription will be allowed end user to transfer a license in the following condition: a) End-User will request the reseller to request a License migration from Ridge Security Partner Portal b) The request will be reviewed and approved by Ridge Security at its sole discretion c) If the request is approved, Ridge Security will be invalidated the original license and issue a migrated license. d) The migrated license will have the same original license term and condition. The migrated license start date is the date when the migrated license is issue, and the license expiration date is the same date as the original license. e) The RidgeBot license migration only transfers the license quota to the new RidgeBot. The configuration and data of the original RidgeBot are not transferred. 2) End User Annual subscription license transfers for de-commissioned asset in the same RidgeBot – End User annual subscription will be allowed end user to transfer a license from a decommissioned asset in the same RidgeBot in the following condition: a) The de-commission asset can only be transferred after the asset is not active for 90 days or more b) End-User will request the reseller to request a License migration from Ridge Security Partner Portal c) Ridge Security will review the request and may approved the request at its sole discretion d) Once the license request is approved, Ridge Security will credit end user the same number and type of license from the de-commission assets. The original license will be invalidated. e) The new license will have the same original license term and condition. The new license start date is the date when the new license is issue, and the license expiration date is the same date as the original license. Page 130 of 147 RidRgeid Sgec Suercituyr Titeyc Thencohlnoogylo Ignyc .I n |c . w| w ww.rwid.greidsgeecsuercituyr.iatiy .aiLicense Requirement Exception RidgeBot needs to be activated to run, but there are one scenario and beta features that do not require license as listed below: • PT scenario: Attack Surface Identification • ACE Scenario: Scenario marked with Beta* • Targets defined in the Ranger of Lateral Movement of the Task Post Exploitation configuration* Note *: license will be required to use these features in the future version of the software. Software and Plugin Library Upgrades Software Upgrade Package The software upgrade package is to upgrade the RidgeBot software to the latest software version. The software package can be download online (starting in version 4.2) or offline. IMPORTANT: 1. License file for version 4.2 is not compatible with the license file from version 4.1.1 or earlier. 1. RidgeBot software version 3.9 cannot be upgraded from the previous releases. Plugin Library Upgrade Package • The plugin library upgrade package is to add new plugins including plugin bug fix to the current ridgebot. • The RidgeBot Plugin Library package is to add new plugins or update the plugins in the RidgeBot. The Plugin Library is available in the same software folder as the RidgeBot system software. • The RidgeBot Plugin Library can be upgraded directly to the latest version. Intermediate versions of the Plugin Library can be skipped during an update. For example: RidgeBot v3.6 is bundled with Plugin Library version 2.7.2. During an update, you can skip Plugin Library version 2.9.2 and update directly to RidgeBot Plugin Library version 2.10.1. • The RidgeBot software upgrade package filename is in the format CUP-version-EN-date.bin, where the “date” is the release date. For example, the upgrade package name to update the RidgeBot Plugin Library is CUP-V2.10.1-EN-20211013.bin. Note: As of version 3.7, the Plugin Library upgrade package extension has changed from .zip to .bin. Page 131 of 147 RidRgeid Sgec Suercituyr Titeyc Thencohlnoogylo Ignyc .I n |c . w| w ww.rwid.greidsgeecsuercituyr.iatiy .aiSoftware Upgrade and Plugin Library Process Starting in software version 4.2, RidgeBot supports upgrade online and upgrade the software or plugin library in the offline mode. click on the appropriate upgrade button and follow the instruction of the pop-up dialog box. Software Upgrade Process Software Online Upgrade Process • Make all the tasks are completed or stopped before starting the online upgrade process • In the About page, the button is now enabled. When user clicks on the button, RidgeBot will access the upgrade server for update. A pop-up dialog box shows a message if RidgeBot current software version is up to date or there is a newer software version available to be upgraded. Figure 116: Online Upgrade pop-up dialog box • User can select to download the package and Click on “Install” or click on “download and Install” to start the upgrade process. • RidgeBot will download the package and start the installation (sample upgrade installation screenshot) Page 132 of 147 RidRgeid Sgec Suercituyr Titeyc Thencohlnoogylo Ignyc .I n |c . w| w ww.rwid.greidsgeecsuercituyr.iatiy .ai• When finished, it will show the status as “Upgrade success” or “upgrade fail”. This process may take approximately 30 minutes Software Offline Upgrade Process To use the offline procedure to upgrade the RidgeBot software, follow these steps: 1. Download the “RUP_XXXX” upgrade package from the software download folder 2. Make all the tasks are completed or stopped before starting the online upgrade process. 3. In the system setting -> about page, click the button. 4. In the pop-up dialog, click the Upload button to select the RidgeBot Software patch as a .bin file (note: the software patch file is shown in the dialog box—if it is the incorrect file, you must click the delete button and upload the correct file). 5. In the pop-up dialog box (as shown below), click on Upload and select the “RUP_XXXX” upgrade package Page 133 of 147 RidRgeid Sgec Suercituyr Titeyc Thencohlnoogylo Ignyc .I n |c . w| w ww.rwid.greidsgeecsuercituyr.iatiy .ai6. After the file upload to RidgeBot then click on “Upgrade” to start the upgrade installation 7. Once the upgrade is completed, click “Experience Now” Page 134 of 147 RidRgeid Sgec Suercituyr Titeyc Thencohlnoogylo Ignyc .I n |c . w| w ww.rwid.greidsgeecsuercituyr.iatiy .ai8. Click the button in the About page -> System Information or run the “restart-service” from the management console. (this step is only required as stated in the README First instruction). Note: It is important to read the “README First” file in the software download directory. This “README first” file contains specific upgrade procedures for each version. Plugin Library Upgrade Process Online Update Process: • Make all the tasks are completed or stopped before starting the online upgrade process • In the About page, the “Check for updates” button is now enabled. When user clicks on the button, a pop- up dialog box shows a message if current version is up to date or there is a new version available to upgrade. • If an upgrade is available, user can select to download the package and Click on “Install” to start the upgrade process. When finished, it will show the status as “Upgrade success” or “upgrade fail” as in the software upgrade process. Offline Update Process: The Plugin Library information is listed on the About page. You can upgrade the Plugin Library by importing a new plugin package. The latest Plugin Library and RidgeBot software are available on the Partner Portal. To use the offline procedure to upgrade the Plugin Library, follow these steps: Page 135 of 147 RidRgeid Sgec Suercituyr Titeyc Thencohlnoogylo Ignyc .I n |c . w| w ww.rwid.greidsgeecsuercituyr.iatiy .aiFigure 117: Offline Plugin Library Upgrade 1. Request a software download: You need the ISO Installation package on the Partner Portal to get access to the Plugin Library. 2. Download the Plugin Library to your PC. 3. In the System Information section, click the button. 4. In the pop-up dialog, click the Upload button to select the plugin package (CUP-Vxxx.bin file) from your PC. 5. Click the Upgrade button to start the Plugin Library upgrade process (note: the plugin file is shown in the dialog box—if it is the incorrect file, you must click the delete button to remove the file before you can upload the correct file). 6. Click the Update History button to see the update history. Page 136 of 147 RidRgeid Sgec Suercituyr Titeyc Thencohlnoogylo Ignyc .I n |c . w| w ww.rwid.greidsgeecsuercituyr.iatiy .aiChapter 10 Management API As of version 3.5, RidgeBot provides an API to integrate with 3rd party tools to manage user tasks and reports. For each new software version, RidgeBot may include a new version of API which may be compatible with the previous version. Note: • The RidgeBot API documentation and user guide are available on Partner Portal for download. • The RidgeBot API documentation can be accessed from RidgeBot at https://your_RidgeBot_IP/public/api/ This chapter has the following sections: • API compatibility chart • Identity Token • Supported API Functions API Compatibility The current API version is V4 Identity Token Each user has an Identity Token used to manage the user’s task. Follow these steps to get an Identity Token to be used as the API access key: 1. Click on the Username in the GUI’s upper right corner to access the User Center. 2. Select Identity Token on the lefthand workflow. 3. Click on Generate or Regenerate to create a Token. 4. Once the Token is generated, the Action options are to Copy the Token or Delete the Token (deleting the Token disables access to this user’s tasks). 1 3 2 4 Figure 118: User Center Page 137 of 147 RidRgeid Sgec Suercituyr Titeyc Thencohlnoogylo Ignyc .I n |c . w| w ww.rwid.greidsgeecsuercituyr.iatiy .aiSupported API Functions As of version 4.1.1, the following actions can be invoked from the API: • Assets: To get, add, delete, or input a host, site or user. • Task Management: To manage a list of user tasks. • Task Data: To retrieve an ACE summary and trend information. • Scenario Management: To access the scenario list and information about scenarios. • Report: To access the list of reports, or to generate, delete or download a report. • ErrorCode: To retrieve the list of error code • Test: To use an API call to RidgeBot to check connection and to valid the API token To access RidgeBot API JSON file, type in the below URL in the web browser: https://RidgeBot_IPADDR/public/api Page 138 of 147 RidRgeid Sgec Suercituyr Titeyc Thencohlnoogylo Ignyc .I n |c . w| w ww.rwid.greidsgeecsuercituyr.iatiy .aiChapter 11 – Integration JIRA Integration RidgeBot supports the integration with JIRA (on-prem) in 4.1.1 software version. User can define multiple JIRA servers and projects to be used in a task. User can configure RidgeBot to automatically open a JIRA case during a task creation or user can manually open a JIRA by selecting the vulnerabilities from the task vulnerability table. Create a JIRA server To setup JIRA integration (On Prem only), go to the Asset tab and select “Integration Connectors” Click on Create to create a JIRA connection Page 139 of 147 RidRgeid Sgec Suercituyr Titeyc Thencohlnoogylo Ignyc .I n |c . w| w ww.rwid.greidsgeecsuercituyr.iatiy .aiAfter the required information is input, click on “Test” to verify and “Save” to create the Jira connector The Integration Connectors will list the Jira connector for each server with the connector status. User can modify or delete the connector from the option in Operation. Example of Jira servers and status Page 140 of 147 RidRgeid Sgec Suercituyr Titeyc Thencohlnoogylo Ignyc .I n |c . w| w ww.rwid.greidsgeecsuercituyr.iatiy .aiOpen Jira case from a Task • Enable DevSecOps in the Task Quick Configuration • Select a Jira server and its project 1. Select a Server from the Integration Connectors list – Click “Select” in the Server Name 2. Select Project Name and Issue Type. This is the project folder where RidgeBot will put newly created case with the selected issue type. The Project Name/ID and Issue Type Name/ID are the categories created by user in the selected Jira Server. 3. Security findings selection allows the user to select a category that will automatically generate a Jira case. Example of a server configuration in a task Page 141 of 147 RidRgeid Sgec Suercituyr Titeyc Thencohlnoogylo Ignyc .I n |c . w| w ww.rwid.greidsgeecsuercituyr.iatiy .ai• Example of a Jira case opened by RidgeBot. In Jira Server – user needs to review and updates the Jira cases accordingly. Page 142 of 147 RidRgeid Sgec Suercituyr Titeyc Thencohlnoogylo Ignyc .I n |c . w| w ww.rwid.greidsgeecsuercituyr.iatiy .aiOpen a Jira case manually from a task’s vulnerability table • Click on the “ConfigureDevSecOps Connector” and Select a Jira server and its project from a task vulnerability table • Select the desired vulnerabilities and then click the “create bug cases” button. The DevSecOps Status shows “Created successfully” in the status column. Page 143 of 147 RidRgeid Sgec Suercituyr Titeyc Thencohlnoogylo Ignyc .I n |c . w| w ww.rwid.greidsgeecsuercituyr.iatiy .ai• Example of a Jira case opened by RidgeBot. In Jira Server – user needs to review and updates the Jira cases accordingly. Page 144 of 147 RidRgeid Sgec Suercituyr Titeyc Thencohlnoogylo Ignyc .I n |c . w| w ww.rwid.greidsgeecsuercituyr.iatiy .aiAppendices Reference Documents • RidgeBotTM Deployment QuickStart Guide • RidgeBotTM Release Notes • RidgeBotTM API user Guide • RidgeBotTM API Reference • RidgeBotTM POC Best Practice Guideline Q&A Q: Where can I find the RidgeBot documents? A: RidgeBot documents are available in the Ridge Security Partner Portal. Q: During initial installation, I get a License Validation File error when upload the license file. A: Please check the following: • Refresh your web browser and upload the license file again. • In the RidgeBot management console, run “service-restart” and then refresh your web browser and upload the license file again. • Check that the machine code is correct. • Click Close on the License dialog box, login as admin and then upload the license file from the RidgeBot System->About page. • If the above steps are unable to resolve license file validation, you need to re-install the RidgeBot software. Q: Using offline upgrade to update the software or plugin library, why does the System Information still show the previous version of the software or plugin library? A: Please check the following: • Refresh your web browser. • Before uploading the upgrade file, make sure the previous version has been removed (if there is a filename in the dialog box, click delete to remove it before uploading the latest version of the software). Page 145 of 147 RidRgeid Sgec Suercituyr Titeyc Thencohlnoogylo Ignyc .I n |c . w| w ww.rwid.greidsgeecsuercituyr.iatiy .aiQ: Why can’t I access the RidgeBot System? A: Please check your environment for the following: • Whether the HTTPS protocol is used, and whether HTTPS is the right protocol. • Whether the IP address, DNS and gateway are configured properly. • Whether the network connection is correct. Q: What type of user can do a license authentication? A: Users with a system administrator role can import the license file from the About page. One exception is that the installer can upload the license file during the first login onto Ridgebot during installation. Q: Why don’t I receive a task report when the task completes, even though email notification is configured for the task? A: No email is sent when a report generation fails. Q: What do I do if a report generation fails? A: Click retry to regenerate the report. Q: Why does a task is finish without test results? A: Check whether the target is reachable. Q: Why is a specific target not shown in the topology map? A: RidgeBot does not display an un-detected object in the topology map. Q: Does RidgeBot interfere with targets’ execution due to its large number of threads? Page 146 of 147 RidRgeid Sgec Suercituyr Titeyc Thencohlnoogylo Ignyc .I n |c . w| w ww.rwid.greidsgeecsuercituyr.iatiy .aiA: The PT operation is safe if the target is used as a common server. There are general guidelines to reduce the risks on the target during Penetration testing. Q: When a user launches multiple tasks in RidgeBot, why is a task Progress is in “Queuing”? A: RidgeBot has reached the concurrent task limit. Any task above this limit will be in a Queue. When a task is completed, RidgeBot will automatically start another task in the Queuing state. Q: When a user launches multiple tasks in RidgeBot, one of the tasks sometimes does not make any progress? A: The RidgeBot web crawler is assigned to one task at a time. If multiple tasks require the web crawler, the remaining tasks wait until web crawler becomes available. Q: Why I can not install Botlet in Windows 10/11 or Windows Server 2016 or later? A: In Release 4.0.x, the Botlet does not have the digital certificate. Therefore, it can not be installed in Windows with the Microsoft Defender or antivirus. This is a known issue that will be addressed in future release. Page 147 of 147 RidRgeid Sgec Suercituyr Titeyc Thencohlnoogylo Ignyc .I n |c . w| w ww.rwid.greidsgeecsuercituyr.iatiy .ai">