Security Test Cases

The Compatibility Testing tool has integrated security test cases.

The following test case describes the specific test procedures for each security test item in the Compatibility Testing tool.

Table 1 describes the security test case.

**Table 1** Security test case
Item	Description
Case Name	Security_Base_Port
Objective	Check whether the runtime monitoring ports of the target software are consistent with the port matrix.
Prerequisites	The environment preparations are complete for the compatibility test, that is, the test environment must remain idle (no load). The target software can be started, and the load can be increased so that CPU utilization exceeds the default idle level after startup. The load may be generated using a performance testing tool selected based on user-specific service characteristics (configurable in the configuration script of the Compatibility Testing tool) or through manual service simulation. The nmap tool is available. Using CentOS 7.6 as an example, the tool comes from the *nmap..rpm** package. It is recommended to mount the ISO file and configure a yum repository for installation.
Procedure	Start the target software by running the software startup command or script in the configuration file of the Compatibility Testing tool. If the command or script is not configured, wait until the software is manually started. After the target software is started, keep services running under a certain pressure, and record the scan result when the target software is running. Commands for scanning ports using the nmap tool: TCP port scanning: nmap -sS -A -v --reason -p- -n -Pn -oA tcp192.168.18.231 192.168.18.231 // The IP address can be any IP address in the test environment. UDP port scanning: nmap -sU -A -v --reason -p- -n -Pn -T4 -oA udp192.168.18.231 192.168.18.231 // The IP address can be any IP address in the test environment. Protocol port scanning: nmap -sO -v --reason -n -oA proto192.168.18.231 192.168.18.231 // The IP address can be any IP address in the test environment. Stop the target software by running the software shutdown command or script in the configuration file of the Compatibility Testing tool. If the command or script is not configured, wait until the software is manually stopped.
Expected Result	Ports excluded from the port matrix are disabled.

Parent topic: Test Cases