Help Center> Host Security Service (New)> User Guide (Ankara Region)> Risk Prevention> Baseline Inspection> Fixing Unsafe Settings
Updated on 2024-04-15 GMT+08:00
View PDF

Fixing Unsafe Settings

This topic provides suggestions on how to fix unsafe settings found by HSS.

Constraints

Servers that are not protected by HSS do not support baseline-related operations.

Modifying the Password Complexity Policy

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.

Improving Password Strength

  • To enhance server security, you are advised to modify the accounts with weak passwords for logging in to the system 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.

After modifying weak passwords, you are advised to manually check the result immediately. If you do not perform a manual verification, HSS will automatically check the settings at 00:00:00 the next day.

Fixing Unsafe Configurations on a Server

Unsafe configurations in key applications in the host system may be exploited by hackers to intrude the system. Such configurations include insecure encryption algorithms used by SSH and Tomcat startup with root permissions.

HSS can detect unsafe configurations provide detailed suggestions.

  1. On the HSS console, choose Asset Management > Servers & Quota and click the Servers tab.
  2. Search for the target server and click the server name to go to the server details page.
  3. Click the Baseline Checks and click the Unsafe Configurations tab. Click the icon before a risk item to expand and view all check item details.
  4. 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.

    • 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 and Suggestion and rectify the unsafe configurations.
        • You are advised to fix the settings with high severity immediately and fix those with medium or low severity.
    • Verification

      If a failed check item has been fixed, you can update its status through verification.

      If a check item failed to be fixed, click View Cause to view the cause. Then, fix it again.
      • 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, and Ubuntu 18.
      1. Click Verify in the Operation column of the row that contains the target risk item.
      2. In the displayed dialog box, click OK. The status changes to Verifying. The system starts automatic verification. After the verification is complete, check the status.

Fixing Risky Configurations on all Servers

Risky configurations in key applications in the host system may be exploited by hackers to intrude the system. Such configurations include insecure encryption algorithms used by SSH and Tomcat startup with root permissions.

HSS can detect unsafe configurations provide detailed suggestions.

  1. Log in to the management console.
  2. In the upper left corner of the page, click , select a region, and choose Security > Host Security Service.
  3. In the navigation pane on the left, choose Prediction > Baseline Checks.
  4. Click the Unsafe Configurations tab to view the risk items. For more information, see Table 1.

    To view the server configuration check results under a specified baseline check policy, select a policy in the Baseline Check Policy drop-down list.
    Table 1 Parameter description

    Parameter

    Description

    Risk Level

    Level of a detection result.

    • High
    • Low
    • Medium
    • Safe

    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.

  5. Click the target baseline name in the list to view the baseline description, affected servers, and details about all check items.
  6. 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.

    • Fixing risks
      1. Click View Details in the Operation column of the target risk item to view the check item details.
      2. View content in the Audit Description and Suggestion text boxes, and handle the risks based on the suggestions or Expected Result described in the Test Cases area.
        • 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. Click Affected Servers to view the servers affected by the check item.

        Click Verify to update the list of affected servers.

    • Verification

      If a failed check item has been fixed, you can update its status through verification.

      If a check item failed to be fixed, click View Cause to view the cause. Then, fix it again.
      • 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, and Ubuntu 18.
      1. Click Verify in the Operation column of the row that contains the target risk item.
      2. In the displayed dialog box, click OK. The status changes to Verifying. The system starts automatic verification. After the verification is complete, check the status.

Parent topic: Baseline Inspection