| ID | Name |
|---|---|
| ATAGS-T1107.001 | Code Signing |
| ATAGS-T1107.002 | Code Signing Policy Modification |
| ATAGS-T1107.003 | Gatekeeper Bypass |
| ATAGS-T1107.004 | Install Root Certificate |
| ATAGS-T1107.005 | Mark-of-the-Web Bypass |
| ATAGS-T1107.006 | SIP and Trust Provider Hijacking |
Threat Actors may tamper with SIP and trust provider components to mislead the operating system and application control tools when conducting signature validation checks. In user mode, Windows Authenticode digital signatures are used to verify a file's origin and integrity, variables that may be used to establish trust in signed code (ex: a driver with a valid Microsoft signature may be handled as safe). The signature validation process is handled via the WinVerifyTrust application programming interface (API) function, which accepts an inquiry and coordinates with the appropriate trust provider, which is responsible for validating parameters of a signature.
This type of attack technique cannot be easily mitigated with preventive controls since it is based on the abuse of system features.