Collecting Container Asset Fingerprints

HSS can collect container asset fingerprints, including container clusters, services, workloads, accounts, ports, and processes. You can centrally check container asset information and detect risky assets in a timely manner based on the container fingerprints. This section describes how to collect container asset fingerprints.

Constraints and Limitations

The container fingerprint function is supported only by the HSS enterprise edition. For details about how to purchase HSS, see Purchasing an HSS Quota.

Container Asset Fingerprint Collection Items

Table 1 lists the collection items of container asset fingerprints. The fingerprint items except clusters, services, workloads, and container instances are automatically collected periodically. You can customize the asset fingerprint collection period. For details, see Asset Discovery.

**Table 1** Container asset fingerprints
Item	Description	Automatic Detection Period
Account Information	Check and manage all accounts on your containers to keep them secure. 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, container name, container ID, and the last scan time.	Automatic check every hour
Open Ports	Check open ports on your containers, including risky and unknown ports. You can easily find high-risk ports on containers 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 with the Dangerous risk level promptly and handle the ports with 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.	Automated check every 30 seconds
Processes	Check processes on your containers and find abnormal processes. You can easily identify abnormal processes on your containers 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.	Automatic check every hour
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, 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.	Automatic check every day
Auto-startup	Check for auto-started 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, container name, container ID, and the last scan time.	Automatic check every hour
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.	Once a week (04:10 a.m. every Monday)
Web Framework	You can check statistics about frameworks used for web content presentation, including their versions, paths, and associated processes.	Once a week (04:10 a.m. every Monday)
Middleware	You can also check information about servers, versions, paths, and processes associated with middleware.	Once a week (04:10 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.	Once a week (04:10 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.	Once a week (04:10 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.	Once a week (04:10 a.m. every Monday)
Clusters	Collect statistics on and display cluster details. You can view the type, node, version, and status of all clusters.	-
Services	Collect statistics on and display details about services and breakpoints. You can view information about all services, such as namespaces and clusters to which the services belong.	-
Workloads	Collect statistics on and display details about workloads (StatefulSets, deployments, DaemonSets, normal jobs, cron jobs, and container groups). You can view the status, number of instances, and namespace of all workloads.	-
Pods	Collect statistics on and display container instance details. You can view the status, pod, and cluster of all container instances.	-

Collecting the Latest Asset Fingerprints of a Single Container

To view the latest data of web applications, web services, web frameworks, websites, middleware, and databases in real time, you can manually collect their fingerprints.

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 Asset Management > Servers & Quota. Click the Servers tab.

If your servers are managed by enterprise projects, you can select an enterprise project to view or operate the asset and scan information.
Click the name of the target server. On the server details page that is displayed, choose Asset Fingerprints > Containers.
Click a fingerprint in the fingerprint list, and click Discover Assets on the upper area of the list on the right.

Currently, only Web Applications, Web Services, Web Frameworks, Websites, Middleware, and Databases support real-time manual collection and update. Information about other types is automatically collected and updated every day.

Figure 1 Collecting data now
After the automatic execution is complete, the last scan time is updated and the latest container asset information is displayed.

Manually Collecting the Latest Asset Fingerprints of All Containers

To view the latest data of accounts, open ports, processes, software, auto-started items, websites, web frameworks, middleware, web services, web applications, and databases in real time, you can manually collect their fingerprints.

Log in to the management console.
In the upper left corner of the page, select a region, click , and choose Security & Compliance > HSS.
Choose Assets > Container Fingerprints.

In the upper right corner of the page, click Update Asset Fingerprints.
Select the server update scope and click OK.

Figure 2 Updating asset fingerprints
After the update is complete, view the latest asset fingerprints.

Collecting Clusters, Services, Workloads, and Containers Information

The information about clusters, services, workloads, and containers is not collected automatically. If your assets change, manually collect the latest data referring to this section.

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 Asset Management > Container Fingerprints.
Choose Clusters and click Synchronize in the upper left corner.

Figure 3 Manually synchronizing cluster assets
Last Synchronized indicates the CCE cluster, service, workload, and container data is synchronized successfully.