Adversaries may attempt to mimic features of valid code signatures to increase the chance of deceiving a user, analyst, or tool. Code signing provides a level of authenticity on a binary from the developer and a guarantee that the binary has not been tampered with. Adversaries can copy the metadata and signature information from a signed program, then use it as a template for an unsigned program. Files with invalid code signatures will fail digital signature validation checks, but they may appear more legitimate to users and security tools may improperly handle these files.(Citation: Threatexpress MetaTwin 2017)
Unlike Code Signing, this activity will not result in a valid signature.
View in MITRE ATT&CK®Capability ID | Capability Description | Mapping Type | ATT&CK ID | ATT&CK Name | Notes |
---|---|---|---|---|---|
CM-2 | Baseline Configuration | Protects | T1036.001 | Invalid Code Signature | |
CM-6 | Configuration Settings | Protects | T1036.001 | Invalid Code Signature | |
IA-9 | Service Identification and Authentication | Protects | T1036.001 | Invalid Code Signature | |
SI-7 | Software, Firmware, and Information Integrity | Protects | T1036.001 | Invalid Code Signature |
Capability ID | Capability Description | Mapping Type | ATT&CK ID | ATT&CK Name | Notes |
---|---|---|---|---|---|
adaptive_application_controls | Adaptive Application Controls | technique_scores | T1036.001 | Invalid Code Signature |
Comments
Once this control is activated, it generates alerts for any executable that is run and is not included in an allow list. Because signatures generated via this technique are not valid, these malicious executables would be detected via any form of allow list, including publisher-based. Events are calculated once every twelve hours, so its temporal score is Partial.
References
|