Adversaries may configure system settings to automatically execute a program during system boot or logon to maintain persistence or gain higher-level privileges on compromised systems. Operating systems may have mechanisms for automatically running a program on system boot or account logon.(Citation: Microsoft Run Key)(Citation: MSDN Authentication Packages)(Citation: Microsoft TimeProvider)(Citation: Cylance Reg Persistence Sept 2013)(Citation: Linux Kernel Programming) These mechanisms may include automatically executing programs that are placed in specially designated directories or are referenced by repositories that store configuration information, such as the Windows Registry. An adversary may achieve the same goal by modifying or extending features of the kernel.
Since some boot or logon autostart programs run with higher privileges, an adversary may leverage these to elevate privileges.
View in MITRE ATT&CK®Capability ID | Capability Description | Mapping Type | ATT&CK ID | ATT&CK Name | Notes |
---|---|---|---|---|---|
file_integrity_monitoring | Microsoft Defender for Cloud: File Integrity Monitoring | technique_scores | T1547 | Boot or Logon Autostart Execution |
Comments
This control can detect boot or logon autostart execution.
References
|
alerts_for_linux_machines | Alerts for Linux Machines | technique_scores | T1547 | Boot or Logon Autostart Execution |
Comments
This control is only relevant for Linux endpoint machines and the only sub-technique relevant for Linux is Kernel Modules and Extensions.
References
|
alerts_for_windows_machines | Alerts for Windows Machines | technique_scores | T1547 | Boot or Logon Autostart Execution |
Comments
This control's detection is specific to a minority of this technique's sub-techniques resulting in a Minimal Coverage score and consequently an overall score of Minimal.
References
|
defender_for_app_service | Microsoft Defender for Cloud: Defender for App Service | technique_scores | T1547 | Boot or Logon Autostart Execution |
Comments
This control only covers one platform and procedure for two of this technique's many sub-techniques, resulting in a Minimal score.
References
|
Capability ID | Capability Description | Mapping Type | ATT&CK ID | ATT&CK Name | Notes |
---|---|---|---|---|---|
google_secops | Google Security Operations | technique_scores | T1547 | Boot or Logon Autostart Execution |
Comments
Google Security Ops is able to trigger an alert based on creation or changes of registry keys and run keys found on Windows platforms.
This technique was scored as minimal based on low or uncertain detection coverage factor.
https://github.com/chronicle/detection-rules/blob/783e0e5947774785db1c55041b70176deeca6f46/mitre_attack/T1547_001_windows_registry_run_keys_startup_folder.yaral
References
|
Technique ID | Technique Name | Number of Mappings |
---|---|---|
T1547.014 | Active Setup | 2 |
T1547.012 | Print Processors | 10 |
T1547.010 | Port Monitors | 2 |
T1547.009 | Shortcut Modification | 13 |
T1547.005 | Security Support Provider | 8 |
T1547.003 | Time Providers | 12 |
T1547.004 | Winlogon Helper DLL | 17 |
T1547.001 | Registry Run Keys / Startup Folder | 5 |
T1547.006 | Kernel Modules and Extensions | 22 |
T1547.002 | Authentication Package | 7 |
T1547.013 | XDG Autostart Entries | 17 |
T1547.007 | Re-opened Applications | 12 |
T1547.008 | LSASS Driver | 9 |