Updated on 2024-07-12 GMT+08:00

Viewing Server Asset Fingerprints

HSS can collect server asset fingerprints, including information about ports, processes, web applications, web services, web frameworks, and auto-started items. You can centrally check server asset information and detect risky assets in a timely manner based on the server fingerprints. HSS does not touch your assets. You need to manually eliminate the risks.

Prerequisite

HSS enterprise edition, premium edition, WTP edition, or container edition has been enabled for the server.

Viewing Asset Information of All Servers

  1. Log in to the management console.
  2. Click in the upper left corner of the page, select a region, and choose Security > Host Security Service.
  3. Choose Asset Management > Server Fingerprints to view all server assets.

    Table 1 Asset fingerprints

    Item

    Description

    Supported OS

    Check Frequency

    Account Information

    Check and manage all accounts on your servers to keep them secure.

    You can check real-time and historical account information to find suspicious accounts.

    • Real-time account information includes the account name, number of servers, server name/IP address, login permission, root permission, user group, user directory, shell started by the user, and the last scan time.
    • Historical account change records include the server name/IP address, change status, login permission, root permission, user group, user directory, shell started by the user, and the last scan time.

    Linux and Windows

    Real-time check

    Open Ports

    Check open ports on your servers, including risky and unknown ports.

    You can easily identify high-risk ports by checking local ports, protocol types, server names, IP addresses, statuses, PIDs, and program files.

    • Manually disabling high-risk ports

      If HSS detects open high-risk ports or unused ports, check whether they are really used by your services. For high-risk ports, check program files. If there are risks, delete or isolate the source files.

      It is recommended that you handle the ports at the Dangerous risk level promptly and handle the ports at the Unknown level based on the actual service conditions.

    • Ignore risks: If a detected high-risk port is actually a normal port used for services, you can ignore it. The port will no longer be regarded risky or generate alarms.

    Linux and Windows

    Real-time check

    Processes

    Check processes on your servers and find abnormal processes.

    You can easily identify abnormal processes based process paths, server names, IP addresses, startup parameters, startup time, users who run the processes, file permissions, PIDs, and file hashes.

    If a suspicious process has not been detected in the last 30 days, its information will be automatically deleted from the process list.

    Linux and Windows

    Real-time check

    Installed Software

    Check and manage all software installed on your servers, and identify insecure versions.

    You can check real-time and historical software information to determine whether the software is risky.

    • Real-time software information includes the software name, number of servers, server names, IP addresses, software versions, software update time, and the last scan time.
    • Historical software change records include the server names, IP addresses, change statuses, software versions, software update time, and the last scan time.

    Linux and Windows

    Automatic check every day

    Auto-startup

    Check for auto-startup items and quickly locate Trojans.

    • Real-time information about auto-started items includes their names, types (auto-started service, startup folder, pre-loaded dynamic library, Run registry key, or scheduled task), number of servers, server names, IP addresses, paths, file hashes, users, and the last scan time.
    • The historical change records of auto-started items include server names, IP addresses, change statuses, paths, file hashes, users, and the last scan time.

    Linux and Windows

    Real-time check

    Websites

    You can check statistics about web directories and sites that can be accessed from the Internet. You can view the directories and permissions, access paths, external ports, certificate information (to be provided later), and key processes of websites.

    Linux

    Once a week (06:00 a.m. every Monday)

    Web Frameworks

    You can check statistics about frameworks used for web content presentation, including their versions, paths, and associated processes.

    Linux

    Once a week (06:00 a.m. every Monday)

    Middleware

    You can check information about servers, versions, paths, and processes associated with middleware.

    Linux and Windows

    Once a week (06:00 a.m. every Monday)

    Web Services

    You can check details about the software used for web content access, including versions, paths, configuration files, and associated processes of all software.

    Linux

    Once a week (06:00 a.m. every Monday)

    Web Applications

    You can check details about software used for web content push and release, including versions, paths, configuration files, and associated processes of all software.

    Linux and Windows (only Tomcat is supported)

    Once a week (06:00 a.m. every Monday)

    Databases

    You can check details about software that provides data storage, including versions, paths, configuration files, and associated processes of all software.

    Linux and Windows (only MySQL is supported)

    Once a week (06:00 a.m. every Monday)

Viewing Asset Information of a Single Server

  1. Log in to the management console.
  2. Click in the upper left corner of the page, select a region, and choose Security > Host Security Service.
  3. In the navigation pane, choose Asset Management > Servers & Quota. Click the Servers tab.
  4. Click the name of the target server. On the server details page that is displayed, choose Asset Fingerprints > Servers.
  5. Click a fingerprint in the fingerprint list to view its asset information. For more information, see Table 1.