Viewing Server Fingerprints
Scenario
Check the server asset fingerprints collected by HSS and handle asset anomalies.
- For details about how to view the asset fingerprint summary information of all servers, see Viewing the Fingerprints of All Servers.
- For details about how to view the asset fingerprint information of a single server, see Viewing the Asset Information of a Single Server.
Viewing the Fingerprints of All Servers
- Log in to the HSS console.
- Click
in the upper left corner and select a region or project. - Choose .
- (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.
- View the server fingerprint overview.
Figure 1 Viewing server fingerprints
- Click a fingerprint type in the fingerprint list, for example, Installed Software, to view its details.
The meanings of the numbers in Figure 2 are as follows:
- 1: the fingerprint list and the number of associated servers
- 2: The fingerprint details list. You can click a fingerprint in the fingerprint list on the left to view its details.
- (Optional) Remove risky assets.
If you find unsafe assets after counting, remove them in a timely manner.
If you receive port alarms, you can set Dangerous Port to Yes in the search box of the Open Ports area to filter dangerous ports. You are advised to handle unsafe ports as follows:
- If HSS detects open high-risk ports or unused ports, check whether they are really used by your services. If they are not, disable them. For dangerous ports, you are advised to further check their program files, and delete or isolate their source files if necessary.
- 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.
For more information, see High-risk port list.
Viewing the Asset Information of a Single Server
- Log in to the HSS console.
- Click
in the upper left corner and select a region or project. - In the navigation pane, choose . Click the Servers tab.
- (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.
- Click the name of the target server. On the server details page that is displayed, choose .
Figure 3 Viewing asset fingerprints of a single server
- In the Fingerprints list, click a fingerprint type to view details.
Figure 4 Viewing server fingerprint details
- (Optional) Remove risky assets.
If you find unsafe assets after counting, remove them in a timely manner.
If you receive port alarms, you can set Dangerous Port to Yes in the search box of the Open Ports area to filter dangerous ports. You are advised to handle unsafe ports as follows:
- If HSS detects open high-risk ports or unused ports, check whether they are really used by your services. If they are not, disable them. For dangerous ports, you are advised to further check their program files, and delete or isolate their source files if necessary.
- If a detected high-risk port is actually a normal port used for services, you can ignore it. Ignored alarms will neither be recorded as unsafe items and nor trigger alarms.
For more information, see High-risk port list.
High-risk port list
Table 1 lists the high-risk ports identified by the asset fingerprint function of HSS. If a high-risk port is enabled in your asset, check whether they are really used by your services.
|
Port |
Description |
Protocol |
|---|---|---|
|
31 |
Trojan horses Master Paradise and Hackers Paradise |
TCP, TCP6, UDP, UDP6 |
|
456 |
Trojan horses HACKERSPARADISE |
TCP, TCP6, UDP, UDP6 |
|
555 |
Trojan horses PhAse1.0 Stealth Spy and IniKiller |
TCP, TCP6, UDP, UDP6 |
|
666 |
Trojan horses Attack FTP and Satanz Backdoor |
TCP, TCP6, UDP, UDP6 |
|
1001 |
Trojan horses Silencer and WebEx |
TCP, TCP6, UDP, UDP6 |
|
1011 |
Doly Trojan |
TCP, TCP6, UDP, UDP6 |
|
1025 |
Trojan netspy |
TCP, TCP6, UDP, UDP6 |
|
1033 |
Trojan netspy |
TCP, TCP6, UDP, UDP6 |
|
1070 |
Trojan horses Streaming Audio Trojan, Psyber Stream Server, and Voice |
TCP, TCP6, UDP, UDP6 |
|
1234 |
Trojan horses SubSeven2.0 and Ultors Trojan |
TCP, TCP6, UDP, UDP6 |
|
1243 |
Trojan SubSeven 1.0/1.9 |
TCP, TCP6, UDP, UDP6 |
|
1245 |
Trojan Voodoo |
TCP, TCP6, UDP, UDP6 |
|
1270 |
MOM-Encrypted Microsoft Operations Manager (MOM) |
TCP, TCP6 |
|
1492 |
Trojan FTP99CMP |
TCP, TCP6, UDP, UDP6 |
|
1600 |
Trojan Shivka-Burka |
TCP, TCP6, UDP, UDP6 |
|
1807 |
Trojan SpySender |
TCP, TCP6, UDP, UDP6 |
|
1981 |
Trojan ShockRave |
TCP, TCP6, UDP, UDP6 |
|
1999 |
Trojan BackDoor |
TCP, TCP6, UDP, UDP6 |
|
2000 |
Trojans GirlFriend 1.3 and Millenium 1.0 |
TCP, TCP6, UDP, UDP6 |
|
2001 |
Trojan Millenium 1.0 and Trojan Cow |
TCP, TCP6, UDP, UDP6 |
|
2023 |
Trojan Pass Ripper |
TCP, TCP6, UDP, UDP6 |
|
2115 |
Trojan Bugs |
TCP, TCP6, UDP, UDP6 |
|
2140 |
Trojan Deep Throat 1.0/3.0 |
TCP, TCP6, UDP, UDP6 |
|
3150 |
Trojan Deep Throat 1.0/3.0 |
TCP, TCP6, UDP, UDP6 |
|
6711 |
Trojan SubSeven1.0/1.9 |
TCP, TCP6, UDP, UDP6 |
|
6776 |
Trojan horses SubSeven2.0 and Ultors Trojan and SubSeven1.0/1.9 |
TCP, TCP6, UDP, UDP6 |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot
