OpenParable
Skip to content
← Back to skills

T1219.003_remote-access-hardware

DevOps & Security

An adversary may use legitimate remote access hardware to establish an interactive command and control channel to target systems within networks.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/mitre_attack/TA0011_command-and-control/T1219.003_remote-access-hardware/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/t1219-003-remote-access-hardware, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

T1219.003 Remote Access Hardware

Sub-technique of: T1219

High-Level Description

An adversary may use legitimate remote access hardware to establish an interactive command and control channel to target systems within networks. These services, including IP-based keyboard, video, or mouse (KVM) devices such as TinyPilot and PiKVM, are commonly used as legitimate tools and may be allowed by peripheral device policies within a target environment.

Remote access hardware may be physically installed and used post-compromise as an alternate communications channel for redundant access or as a way to establish an interactive remote session with the target system. Using hardware-based remote access tools may allow threat actors to bypass software security solutions and gain more control over the compromised device(s).

Kill Chain Phase

  • Command and Control (TA0011)

Platforms: Linux, macOS, Windows

What to Check

  • Identify if Remote Access Hardware technique is applicable to target environment
  • Check Linux systems for indicators of Remote Access Hardware
  • Check macOS systems for indicators of Remote Access Hardware
  • Check Windows systems for indicators of Remote Access Hardware
  • Verify mitigations are bypassed or absent (1 known mitigations)
  • Assess detection coverage (1 detection strategies)

How to Test

Manual Testing

  1. Identify Attack Surface: Determine if the target environment is susceptible to Remote Access Hardware by examining the target platforms (Linux, macOS, Windows).

  2. Assess Existing Defenses: Review whether mitigations for T1219.003 are in place. If defenses are absent or misconfigured, this technique may be exploitable.

  3. Execute Test: Use tools and methods described in the MITRE ATT&CK page and external references below.

Note: No Atomic Red Team tests available for this technique. See Atomic Red Team GitHub for updates.

Remediation Guide

M1034 Limit Hardware Installation

Block the use of IP-based KVM devices within the network if they are not required.

Detection

Detect Remote Access via USB Hardware (TinyPilot, PiKVM)

Risk Assessment

FindingSeverityImpact
Remote Access Hardware technique applicableLowCommand And Control

CWE Categories

CWE IDTitle
CWE-300Channel Accessible by Non-Endpoint

References