Detection of Malicious Code

reportActive / Technical Report | Accesssion Number: AD1201268 | Open PDF

Abstract:

Problem: DoD uses much software produced by various supply chains. These supply chains can be compromised by an adversary: Network intrusion; Insider threat. Failing to detect malicious code can be very costly. Detection is currently impractical. Specifically, we aim to detect two types of malicious code: Exfiltration of potentially sensitive information (e.g., keyloggers); Timebombs / logic bombs, Remote-Access Trojans, etc: Calling a potentially sensitive system API call (e.g., writing to a file, starting a new process, etc.) in response to a potentially questionable trigger (e.g., on a specific date, in response to incoming network packets, etc.).

Security Markings

DOCUMENT & CONTEXTUAL SUMMARY

Distribution Code:
A - Approved For Public Release
Distribution Statement: Public Release

RECORD

Collection: TRECMS
Identifying Numbers
Subject Terms