Viewing and Processing Baseline Check Results

Constraints

Only enterprise edition, premium edition, web tamper protection edition, and container edition are supported.

Detection Description

The MySQL baseline detection of Linux OS is based on the MySQL 5 security configuration specifications. If MySQL 8 is installed on your server, the following check items are not displayed in the detection results, because they are discarded in that version. The detection results are displayed only on the server whose MySQL version is 5.

• Rule: Do not set old_passwords to 1.
• Rule: Set secure_auth to 1 or ON.
• Rule: Do not set skip_secure_auth.
• Rule: Set log_warnings to 2.
• Rule: Configure the MySQL binlog clearing policy.
• Rule: The sql_mode parameter contains NO_AUTO_CREATE_USER.
• Rule: Use the MySQL audit plug-in.

Viewing Baseline Check Overview Information

1. Log in to the management console.
2. In the upper left corner of the page, select a region, click , and choose Security & Compliance > HSS.
3. In the navigation pane on the left, choose Risk Management > Baseline Checks.
   

   If your servers are managed by enterprise projects, you can select an enterprise project to view or operate the asset and scan information.

4. Click different tabs on the displayed page to check detected unsafe configurations. Figure 1 lists the corresponding parameters.
   To view the check results of servers under different manual baseline check policies, you can switch between baseline check policies.

   Figure 1 Baseline check overview
   

   Table 1 Baseline check overview

   Parameter	Description
   Baseline check policy	Available baseline check policies that have been added. You can select, create, edit, and delete these policies.
   Scanned servers	Total number of detected servers.
   Security baselines	Number of baselines executed during the server detection.
   Baseline check items	Total number of checked server configuration items.
   Safe settings rate	Percentage of configuration items that passed the baseline check to the total number of check items. Failed items are displayed by risk level.
   Top 5 servers with unsafe settings	Statistics on servers with server configuration risks. The top 5 servers with the highest risks are preferentially sorted. If no high-risk settings exist, the servers are sorted into medium-risk and low-risk ones in sequence.
   Servers with weak passwords	Total number of detected servers, as well as the numbers of servers with weak passwords, those without weak passwords, and those with weak password detection disabled.
   Top 5 servers with weak passwords	Statistics on the top 5 servers with most weak password risks.
   Unsafe configuration	Alarms generated for servers with configuration risks and the risk statistics.
   Password complexity policies	Statistics on servers with passwords that do not meet the complexity requirements in the baseline.
   Common weak passwords	Statistics on servers with weak passwords and accounts.

Viewing and Processing Configuration Check Results

1. Click the Unsafe Configurations tab to view the risk items. For more information, see Table 2.
   Figure 2 Viewing unsafe configuration details
   

   Table 2 Parameter description

   Parameter	Description
   Risk level	Level of a detection result. High Low Medium Secure
   Baseline name	Name of the baseline that is checked.
   Type	Policy type of the baseline that has been checked. Cloud security practices DJCP MLPS
   Check item	Total number of configuration items that are checked.
   Risky item	Total number of the risky configurations.
   Affected servers	Total number of servers affected by the detected risks in a baseline.
   Last scanned	Time when the last detection was performed.
   Description	Description of a baseline.

2. Click the target baseline name in the list to view the baseline description, affected servers, and details about all check items.
   Figure 3 Viewing baseline check details
   

3. Handle risk items.
   • Ignoring risks

     Click Ignore in the Operation column of the target check item to ignore a check item. Select multiple check items and click Ignore to ignore them in batches.

     Figure 4 Ignoring risks
     
   • Fixing risks
     1. Click View Details in the Operation column of the target risk item to view the check item details.
     2. View the content in the Audit Description, Suggestion, and Affected Servers. Rectify the unsafe configurations.
        

        • Currently, one-click fixing is supported for some EulerOS baseline configurations and CentOS 8 baseline configurations. You can simply click Fix in the Operation column of the target EulerOS or CentOS check item to fix the unsafe configurations. If some parameters need to be configured during restoration, retain the default values.
        • You are advised to fix the settings with high severity immediately and fix those with medium or low severity.
     3. After the repair is complete, click Verify on the Affected Servers tab page to verify the result.
        If a failed check item has been fixed, you can update its status through verification.

        

        • Currently, baseline checks are not supported for Windows OSs.
        • The agent status of the target server must be online.
        • Only one risk item can be verified at a time. Other risk items can be verified only after the risk items are verified.
        • Baseline checks are supported for the following Linux OSs: Apache 2, Docker, MongoDB, Redis, MySQL 5, Nginx, Tomcat, SSH, vsftp, CentOS 6, CentOS 7, CentOS 8, EulerOS, Debian 9, Debian 10, Debian 11, Red Hat 6, Red Hat 7, Red Hat 8, Ubuntu 12, Ubuntu 14, Ubuntu 16, Ubuntu 18, SUSE 12, SUSE 15.
     4. Click Verify.
     5. Return to the check item list page and view the status of the risk item.

        The status changes to Verifying. The system starts automatic verification. After the verification is complete, check the status. If a check item failed to be fixed, click View Cause to view the cause. Then, fix it again.

Viewing and Processing the Password Complexity Policy Detection Result

1. Click the Password Complexity Policy Detection tab to view the risk statistical items and handling suggestions. For more information, see Table 3.
   Figure 5 Viewing password complexity policy detection details
   

   Table 3 Parameter description

   Parameter	Description
   Server	Name and public/private IP address of the detected server.
   Password length	Whether the password length policy of the target server meets the requirements. Passed Failed
   Uppercase letters	Whether the uppercase letter policy used for passwords on the target server meets the requirements. Passed Failed
   Lowercase letters	Whether the lowercase letter policy used for passwords on the target server meets the requirements. Passed Failed
   Digits	Whether the numeric policy used for passwords on the target server meets the requirements. Passed Failed
   Special characters	Whether the special character policy used for passwords on the target server meets the requirements. Passed Failed
   Suggestion	Suggestion for the password complexity policy of the target server.

2. Modify the password complexity policy on the server as recommended.
   • To monitor the password complexity policy on a Linux server, install the Pluggable Authentication Modules (PAM) on the server. For details, see How Do I Install a PAM in a Linux OS?
   • For details about how to modify the password complexity policy on a Linux server, see How Do I Install a PAM and Set a Proper Password Complexity Policy in a Linux OS?
   • For details about how to modify the password complexity policy on a Windows server, see How Do I Set a Secure Password Complexity Policy in a Windows OS?

3. After modifying the password complexity policy, perform a manual check in the upper part of the Baseline Checks page to verify the result.

   If you do not perform a manual verification, HSS will automatically check the settings at 00:00:00 the next day.

Viewing and Processing Common Weak Password Detection Results

1. Click the Common Weak Password Detection tab to view the statistics of risky weak password accounts on the server. For more information, see Viewing common weak password detection.
   Figure 6 Viewing common weak password detection
   

   Table 4 Parameter description

   Parameter	Description
   Server	Name and public/private IP address of the detected server.
   Account name	Accounts with weak passwords that are detected on the target server.
   Account type	Type of an account.
   Usage duration (Days)	Period for using a weak password.

2. Log in to the server and change the weak password.
   

   • To enhance server security, you are advised to modify the accounts with weak passwords in a timely manner, such as SSH accounts.
   • To protect internal data of your server, you are advised to modify software accounts that use weak passwords, such as MySQL accounts and FTP accounts.

   • A password should contain more than eight characters, including uppercase letters, lowercase letters, digits, and special characters.

3. After the weak password is changed, perform a manual check in the upper part of the Baseline Checks page to verify the result.

   If you do not perform a manual verification, HSS will automatically check the settings at 00:00:00 the next day.