Native Functionality Abuse - IMP-0007
Definition
Native Functionality Abuse is the deliberate use or triggering of functionality that already exists within a spacecraft architecture. An adversary may invoke the function directly or create conditions that cause it to activate. The function may operate exactly as designed, but the adversary uses it for an unauthorized or harmful purpose. This mechanism includes platform, payload, autonomous, and mission-specific capabilities. It also includes custom flight software functions. The adversary may misuse a function by activating it at the wrong time, repeating it, interrupting it, or directing it toward an unintended purpose. Vector: Illustrative Application Collect: If the objective is Collect, an adversary could invoke native diagnostic, memory-dump, sensing, or data-export functionality to obtain information outside authorized mission operations. Pivot: If the objective is Pivot, an adversary could use native crosslink, relay, or routing functionality to route activity through the spacecraft toward another connected asset or trust domain. Subvert: TIf the objective is Subvert, an adversary could deliberately trigger legitimate fault-response or diagnostic functions to disrupt mission operations and divert defenders from other adversary activity. Seize: If the objective is Seize, an adversary could use native command and mission-tasking functionality to assume control of a payload or spacecraft capability and repurpose it for unauthorized operations. Disable: If the objective is Disable, an adversary could use legitimate pointing functionality to expose a mission-critical sensor to the Sun beyond acceptable limits, leaving the spacecraft unable to conduct its intended mission or an essential mission function.
D3FEND Inferred Relationships
There are no artifacts defined on this offensive technique (yet). Please consider contributing an addition to D3FEND.