Vulnerability Scan
HSS can scan for Linux, Windows, Web-CMS, application, and emergency vulnerabilities. Automatic, scheduled, and manual scans are supported.
- Automatic scan
By default, Linux, Windows, and Web-CMS vulnerabilities are automatically scanned every day. Application vulnerabilities are automatically scanned every Monday. The time of an automatic application vulnerability scan changes with the middleware asset scan time. For details about how to view and set the latter, see Asset Discovery.
If a manual or scheduled vulnerability scan has been performed in a day, HSS will not automatically scan for vulnerabilities on that day.
- Scheduled scan
By default, a full server vulnerability scan is performed once a week. To protect workloads, you are advised to set a proper scan period and scan server scope to periodically scan server vulnerabilities.
- Manual scan
If you want to view the vulnerability fixing status or real-time vulnerabilities of a server, you are advised to manually scan for vulnerabilities.
This section describes how to manually scan for vulnerabilities and configure a scheduled scan policy.
Constraints
- If the agent version of the Windows OS is 4.0.18 or later, application vulnerability scan is supported. If the agent version of the Linux OS is 3.2.9 or later, emergency vulnerability scan is supported. For details about how to upgrade the agent, see Upgrading the Agent.
- The Server Status is Running, Agent Status is Online, and Protection Status is Protected. Otherwise, vulnerability scan cannot be performed.
- For details about the types of vulnerabilities that can be scanned by different HSS editions, see Types of Vulnerabilities That Can Be Scanned and Fixed.
- For details about the OSs supported by Linux and Windows vulnerability scan, see Table 1. Emergency vulnerability scan supports x86 Ubuntu, CentOS, EulerOS, Debian, and AlmaLinux.
Table 1 OSs supporting vulnerability scan OS Type
Supported OS
Windows
- Windows Server 2019 Datacenter 64-bit English (40 GB)
- Windows Server 2019 Datacenter 64-bit Chinese (40 GB)
- Windows Server 2016 Standard 64-bit English (40 GB)
- Windows Server 2016 Standard 64-bit Chinese (40 GB)
- Windows Server 2016 Datacenter 64-bit English (40 GB)
- Windows Server 2016 Datacenter 64-bit Chinese (40 GB)
- Windows Server 2012 R2 Standard 64-bit English (40 GB)
- Windows Server 2012 R2 Standard 64-bit Chinese (40 GB)
- Windows Server 2012 R2 Datacenter 64-bit English (40 GB)
- Windows Server 2012 R2 Datacenter 64-bit Chinese (40 GB)
Linux
- EulerOS 2.2, 2.3, 2.5, 2.8, and 2.9 (64-bit)
- CentOS 7.4, 7.5, 7.6, 7.7, 7.8 and 7.9 (64-bit)
- Ubuntu 16.04, 18.04, 20.04, 22.04 (64-bit)
- Debian 9, 10, and 11 (64-bit)
- Kylin V10 (64-bit)
- SUSE 12 SP5, 15 SP1, and 15 SP2 (64-bit)
- UnionTech OS V20 server E and V20 server D (64-bit)
Manual Vulnerability Scan
- Log in to the management console.
- In the upper left corner of the page, select a region, click , and choose Security & Compliance > HSS.
- In the navigation pane, choose Risk Management > Vulnerabilities.
- Click Scan in the upper right corner of the Vulnerabilities page.
To scan for emergency vulnerabilities, locate the row of an emergency vulnerability, and click Scan in the Operation column.
- In the Scan for Vulnerability dialog box displayed, set the vulnerability types and scope to be scanned. For more information, see Table 2.
Table 2 Parameters for manual scan vulnerabilities Parameter
Description
Example Value
Type
Select one or more types of vulnerabilities to be scanned. Possible values are as follows:
- Linux
- Windows
- Web-CMS
- Application
- Emergency
Select all
Scan
Select the servers to be scanned. Possible values are as follows:
- All servers
- Selected servers
You can select a server group or search for the target server by server name, ID, EIP, or private IP address.
NOTE:The following servers cannot be selected for vulnerability scan:
- Servers are protected by basic edition HSS.
- Servers that are not in the Running state
- Servers whose agent status is Offline
All servers
- Click OK.
- Click Manage Task in the upper right corner of the Vulnerabilities page. On the Manage Task slide-out panel displayed, click the Scan Tasks tab to view the status and scan result of the vulnerability scan task.
Click the number next to the red icon in the Scan Result column to view information about the servers that fail to be scanned.
You can also choose
and scan a single server for vulnerabilities on the Servers tab. The procedure is as follows:- Click a server name.
- Choose Vulnerabilities.
- Choose the vulnerability type to be scanned and click Scan.
Scheduled vulnerability scan
- Log in to the management console.
- In the upper left corner of the page, select a region, click , and choose Security & Compliance > HSS.
- In the navigation pane, choose Risk Management > Vulnerabilities.
- In the upper right corner of the Vulnerabilities page, click Scheduled Scan Policy. The Configure Scheduled Scan Policy dialog box is displayed.
- In the dialog box, configure parameters such as the period and scope for scheduled vulnerability scanning.
- Scheduled Vulnerability Scan: Select whether to enable scheduled vulnerability scan. indicates it is enabled.
- Type: Select the type of vulnerabilities to be scanned.
- Scan Period: Select Every day, Every three days, or Every week. The default scan duration is 00:00:00 - 07:00:00 and cannot be changed.
- Servers: Select the server to be scanned.
The following servers cannot be selected for vulnerability scan:
- Servers are protected by basic edition HSS.
- Servers that are not in the Running state
- Servers whose agent status is Offline
- Click Manage Task in the upper right corner of the Vulnerabilities page. On the Manage Task slide-out panel, click the Scan Tasks tab to view the status and scan results of the vulnerability scan task.
Click the number next to the red figure in the Scan Result column to view information about the servers that fail to be scanned.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.