Skip to main content
MuonPartners
Services
Architecture

Solution design and technology roadmapping

Solution AssessmentTechnology RoadmapsIntegration DesignSolution ArchitectureTechnical Design
Cyber Security

Security assessments, IAM, and compliance

AssessmentsIAMComplianceSecurity BaselineCyber Innovation
Network and Platform

Network architecture and cloud platforms

Network DesignCloud StrategyModernisation
Enterprise Architecture

Business-technology alignment

Business AlignmentPortfolio AnalysisGovernance
View all services
ProjectsCase StudiesInsightsToolsAbout
Contact Us

Services

Architecture
Solution AssessmentTechnology RoadmapsIntegration DesignSolution ArchitectureTechnical Design
Cyber Security
AssessmentsIAMComplianceSecurity BaselineCyber Innovation
Network and Platform
Network DesignCloud StrategyModernisation
Enterprise Architecture
Business AlignmentPortfolio AnalysisGovernance
ProjectsCase StudiesInsightsToolsAboutContact
Get in Touch
MuonPartners

Strategic technology consulting for Australian organisations navigating complexity.

Services

  • Architecture
  • Cyber Security
  • Network and Platform
  • Enterprise Architecture

Company

  • About
  • Products
  • Frameworks
  • Cross-Framework Mapping
  • Projects
  • Case Studies
  • Insights
  • Contact

Contact

  • [email protected]
  • Australia
  • LinkedIn

© 2026 Muon Partners. All rights reserved.

ABN 50 669 022 315 · A Muon Group company.

Privacy PolicyTerms of Service
  1. Frameworks
  2. >ATTACK
  3. >Command And Control
  4. >ATTACK-T1071
ATTACK-T1071Active

Application Layer Protocol

Statement

Adversaries may communicate using OSI application layer protocols to avoid detection/network filtering by blending in with existing traffic. Commands to the remote system, and often the results of those commands, will be embedded within the protocol traffic between the client and server.

Adversaries may utilize many different protocols, including those used for web browsing, transferring files, electronic mail, DNS, or publishing/subscribing. For connections that occur internally within an enclave (such as those between a proxy or pivot node and other nodes), commonly used protocols are SMB, SSH, or RDP.(Citation: Mandiant APT29 Eye Spy Email Nov 22)

Location

Tactic
Command and Control

Technique Details

Identifier
ATTACK-T1071
ATT&CK Page
View on MITRE

Tactics

Command And Control

Platforms

LinuxmacOSWindowsNetwork DevicesESXi

Detection

Detection of Command and Control Over Application Layer Protocols

Mitigations

Network Intrusion Prevention: Use intrusion detection signatures to block traffic at network boundaries.

Filter Network Traffic: Employ network appliances and endpoint software to filter ingress, egress, and lateral network traffic. This includes protocol-based filtering, enforcing firewall rules, and blocking or restricting traffic based on predefined conditions to limit adversary movement and data exfiltration. This mitigation can be implemented through the following measures:

Ingress Traffic Filtering:

  • Use Case: Configure network firewalls to allow traffic only from authorized IP addresses to public-facing servers.
  • Implementation: Limit SSH (port 22) and RDP (port 3389) traffic to specific IP ranges.

Egress Traffic Filtering:

  • Use Case: Use firewalls or endpoint security software to block unauthorized outbound traffic to prevent data exfiltration and command-and-control (C2) communications.
  • Implementation: Block outbound traffic to known malicious IPs or regions where communication is unexpected.

Protocol-Based Filtering:

  • Use Case: Restrict the use of specific protocols that are commonly abused by adversaries, such as SMB, RPC, or Telnet, based on business needs.
  • Implementation: Disable SMBv1 on endpoints to prevent exploits like EternalBlue.

Network Segmentation:

  • Use Case: Create network segments for critical systems and restrict communication between segments unless explicitly authorized.
  • Implementation: Implement VLANs to isolate IoT devices or guest networks from core business systems.

Application Layer Filtering:

  • Use Case: Use proxy servers or Web Application Firewalls (WAFs) to inspect and block malicious HTTP/S traffic.
  • Implementation: Configure a WAF to block SQL injection attempts or other web application exploitation techniques.
SP 800-53
SP800-53-AC-4relatedvia ctid-attack-to-sp800-53
SP800-53-CA-7relatedvia ctid-attack-to-sp800-53
SP800-53-CM-2relatedvia ctid-attack-to-sp800-53
SP800-53-CM-6relatedvia ctid-attack-to-sp800-53
SP800-53-CM-7relatedvia ctid-attack-to-sp800-53
View in graphReport an issue
← Back to Command and Control
Command and Control41 controls
ATTACK-T1001Data ObfuscationATTACK-T1001.001Junk DataATTACK-T1001.002SteganographyATTACK-T1001.003Protocol or Service ImpersonationATTACK-T1008Fallback ChannelsATTACK-T1071Application Layer ProtocolATTACK-T1071.001Web ProtocolsATTACK-T1071.002File Transfer ProtocolsATTACK-T1071.003Mail ProtocolsATTACK-T1071.004DNSATTACK-T1071.005Publish/Subscribe ProtocolsATTACK-T1090ProxyATTACK-T1090.001Internal ProxyATTACK-T1090.002External ProxyATTACK-T1090.003Multi-hop ProxyATTACK-T1090.004Domain FrontingATTACK-T1092Communication Through Removable MediaATTACK-T1095Non-Application Layer ProtocolATTACK-T1102Web ServiceATTACK-T1102.001Dead Drop ResolverATTACK-T1102.002Bidirectional CommunicationATTACK-T1102.003One-Way CommunicationATTACK-T1104Multi-Stage ChannelsATTACK-T1105Ingress Tool TransferATTACK-T1132Data EncodingATTACK-T1132.001Standard EncodingATTACK-T1132.002Non-Standard EncodingATTACK-T1219Remote Access ToolsATTACK-T1219.001IDE TunnelingATTACK-T1219.002Remote Desktop SoftwareATTACK-T1219.003Remote Access HardwareATTACK-T1568Dynamic ResolutionATTACK-T1568.001Fast Flux DNSATTACK-T1568.002Domain Generation AlgorithmsATTACK-T1568.003DNS CalculationATTACK-T1571Non-Standard PortATTACK-T1572Protocol TunnelingATTACK-T1573Encrypted ChannelATTACK-T1573.001Symmetric CryptographyATTACK-T1573.002Asymmetric CryptographyATTACK-T1665Hide Infrastructure