Updated on 2025-08-26 GMT+08:00

Collecting Server Asset Fingerprints

Scenarios

HSS can collect server fingerprints, including information about ports, processes, web applications, web services, web frameworks, and auto-started items. You can centrally check server information and detect risky assets in a timely manner based on the server fingerprints. This section describes server asset fingerprints and their collection method.

Constraints

The server fingerprint function is available in HSS enterprise, premium, WTP, and container editions. For details about how to purchase and upgrade HSS, see Purchasing an HSS Quota and Upgrading a Protection Quota.

Server Fingerprint Collection Items

Server fingerprints: accounts, open ports, processes, software, auto-started items, web applications, web services, web frameworks, websites, middleware, kernel modules, and databases. For details, see Server Fingerprint Collection Items.

Table 1 Server fingerprint collection items

Item

Description

Supported OS

Accounts

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, the last scan time, and the first 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

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 dangerous or unnecessary ports are found enabled, check whether they are mandatory for services, and disable them if they are not. For dangerous ports, you are advised to further check their program files, and delete or isolate their source files if necessary.

    It is recommended that you handle the ports at the Dangerous risk level promptly and handle the ports at the Unknown risk 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

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

Installed software

Check and manage all software installed on your containers, 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, the last scan time, and the first 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

Auto-started items

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

Websites

Check information 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.

Information about the following websites can be collected: Linux-based Apache, Nginx, and Tomcat.

Linux

Web frameworks

Check information about frameworks used for web content display, including their versions, paths, and associated processes.

The following types of web frameworks based on Linux support data collection:

  • Java language framework: Struts, struts2, spring, hibernate, webwork, quartz, velocity, turbine, FreeMarker, flexive, stripes, vaadin, vertx, wicket, zkoss, jackson, fastjson, shiro, MyBatis, Jersey and JFinal.
  • Python framework: Django, Flask, Tornado, web.py, and web2py.
  • PHP language framework: Webasyst, KYPHP, CodeIgniter, InitPHP, SpeedPHP, ThinkPHP, and OneThink
  • Go framework: Gin, Beego, Fasthttp, Iris, and Echo.

Linux

Middleware

Check information about servers, versions, paths, and processes associated with middleware.

Linux and Windows

Kernel module

Check information about all the program module files running in kernels, including associated servers, version numbers, module descriptions, driver file paths, file permissions, and file hashes.

Linux

Web services

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

The following types of web services support data collection:

  • Linux: Apache, Nginx, Tomcat, Weblogic, WebSphere, JBoss, Wildfly, and Jetty
  • Windows: Tomcat

Linux and Windows

Web applications

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

The following types of web applications support data collection:

  • Linux: PHPMailer, PHPMyadmin, DedeCMS, WordPress, ThinkPHP, BigTree, JPress, Jenkins, Zabbix, Discuz!, and ThinkCMF.
  • Windows: Chanjet

Linux and Windows

Databases

Check details about the software that provides data storage, including versions, paths, configuration files, and associated processes of all software.

Information about the following types of databases can be collected:

  • Linux: MySQL, Redis, Oracle, MongoDB, Memcache, PostgreSQL, HBase, DB2, Sybase, Dameng database management system, and KingbaseES database management system.
  • Windows: MySQL

Linux and Windows

Server Fingerprint Collection Modes

Server fingerprints can be collected automatically or manually. For details about how each type of fingerprints is collected, see Table 2.

After the agent is installed on a server, the fingerprints of the server will be collected for the first time immediately. By default, the automatic collection period starts from the time when the agent installation succeeded.

If you are using the HSS premium edition or higher, you can customize the interval for automatically collecting data of middleware, web frameworks, kernel modules, web applications, websites, web services, and databases. For details, see Asset Discovery.
Table 2 Server fingerprint collection modes

Item

Automatic Check Frequency

Manual Collection Method

Accounts

Automatic check every hour

Manually Collecting the Latest Asset Fingerprints of All Servers

Open ports

Automatic check every 30 seconds

Manually Collecting the Latest Asset Fingerprints of All Servers

Processes

Automatic check every hour

Manually Collecting the Latest Asset Fingerprints of All Servers

Installed software

Automatic check every day

Manually Collecting the Latest Asset Fingerprints of All Servers

Auto-started items

Automatic check every hour

Manually Collecting the Latest Asset Fingerprints of All Servers

Websites

Once a week (04:10 a.m. every Monday)

Web frameworks

Once a week (04:10 a.m. every Monday)

Middleware

Once a week (04:10 a.m. every Monday)

Kernel module

Once a week (04:10 a.m. every Monday)

Web services

Once a week (04:10 a.m. every Monday)

Web applications

Once a week (04:10 a.m. every Monday)

Databases

Once a week (04:10 a.m. every Monday)

Manually Collecting the Latest Asset Fingerprints of a Single Server

If you want to obtain the latest data of assets such as web applications, web services, web frameworks, websites, middleware, kernel modules, and databases in real time, you can manually collect fingerprint 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 > Host Security Service.
  3. In the navigation pane, choose Asset Management > Servers & Quota. Click the Servers tab.
  4. (Optional) If you have enabled the enterprise project function, select an enterprise project from the Enterprise Project drop-down list in the upper part of the page to view its data.
  5. Click the name of the target server. On the server details page that is displayed, choose Asset Fingerprints > Servers.
  6. Click a fingerprint in the fingerprint list, and click Discover Assets on the upper area of the list on the right.

    Currently, only the information about web applications, web services, web frameworks, websites, middleware, kernel modules, and databases can be manually collected and updated in real time. Information about other types is automatically collected and updated every day.

    Figure 1 Collecting data now

  7. After the automatic execution is complete, the last scan time is updated and the latest server asset information is displayed.

Manually Collecting the Latest Asset Fingerprints of All Servers

To view the latest fingerprints of all server assets in real time, you can manually collect fingerprints.

  1. Log in to the management console.
  2. In the upper left corner of the page, select a region, click , and choose Security & Compliance > Host Security Service.
  3. Choose Asset Management > Server Fingerprints.
  1. In the upper right corner of the page, click Update Asset Fingerprints.
  2. Select the server update scope and click OK.

    Figure 2 Updating asset fingerprints

  3. After the Updating Asset Fingerprints status disappears from the button in the upper right corner of the page, you can view the latest asset fingerprints.

Follow-up Procedure

After the server fingerprints are collected, you can view the latest asset fingerprint data. For details, see Viewing Server Asset Fingerprints.