Non-Standard Port
Description
Adversaries may communicate using a protocol and port pairing that are typically not associated. For example, HTTPS over port 8088(Citation: Symantec Elfin Mar 2019) or port 587(Citation: Fortinet Agent Tesla April 2018) as opposed to the traditional port 443. Adversaries may make changes to the standard port used by a protocol to bypass filtering or muddle analysis/parsing of network data. Adversaries may also make changes to victim systems to abuse non-standard ports. For example, Registry keys and other configuration settings can be used to modify protocol and port pairings.(Citation: change_rdp_port_conti)
Mapped SPARTA techniques
No techniques mapped to this control.
Cross-framework references
Relationships published by the source frameworks themselves, reproduced here with attribution. They are not SafeMode Space mappings and carry no confidence rating of ours.
Countered by 11 in MITRE D3FEND (Defensive Techniques)
- D3-APCAApplication Protocol Command Analysis
- D3-CSPPClient-server Payload Profiling
- D3-NTCDNetwork Traffic Community Deviation
- D3-NTFNetwork Traffic Filtering
- D3-NTSANetwork Traffic Signature Analysis
- D3-OTFOutbound Traffic Filtering
- D3-PHDURAPer Host Download-Upload Ratio Analysis
- D3-PMADProtocol Metadata Anomaly Detection
- D3-RPARelay Pattern Analysis
- D3-RTSDRemote Terminal Session Detection
- D3-UGLPAUser Geolocation Logon Pattern Analysis
Cite as SafeMode Space, mitre-attack-enterprise T1571.