1200KM / detection
T1037 Boot or Logon Initialization Scripts — Detection Rules
Detection workspace for T1037 Boot or Logon Initialization Scripts: 0 Sigma sources, 0 Atlas concepts and 0 anomaly models. No live detection validation.
Source-backed rule directory
No reviewed association in this snapshot.
Atlas deterministic concepts
No exact concept selected.
Anomaly models
No exact Atlas model in this snapshot.
ATT&CK analytic guidance
DET0112 Boot or Logon Initialization Scripts Detection Strategy
AN0311 Analytic 0311
Monitoring modification and execution of user or system logon scripts such as in registry Run keys or startup folders.
AN0312 Analytic 0312
Detection of changes or execution of shell initialization scripts like .bashrc, .profile, or /etc/profile for persistence.
AN0313 Analytic 0313
Monitoring for modification and execution of login hook scripts or LaunchAgents/LaunchDaemons used for persistence.
AN0314 Analytic 0314
Detection of modification to ESXi rc.local.d or rc scripts that are used to execute on boot.
AN0315 Analytic 0315
Detection of changes to device startup-config files that include boot scripts or scheduled execution routines.
Connected ecosystem references
Linked tags
Simulation, tools and telemetry
- File Access · DC0055
- File Metadata · DC0059
- File Modification · DC0061
- Process Creation · DC0032
- Scheduled Job Creation · DC0001
- Script Execution · DC0029
- Service Metadata · DC0041
- Windows Registry Key Modification · DC0063
No reviewed association in this snapshot.
Threat actor context
These are explicit actor-to-technique associations in the existing Threat Matrix snapshot, not attribution of an event or proof that a detector identifies the actor. No tool-to-actor relationship is inferred.
Existing anomaly research
Complete technique engineering workbook
Collection configuration and event examples · Anomaly models and design worksheet · Tools and documented software · Simulation procedures · Offline synthetic collection check
Exact source tags are not semantic relevance verdicts. Review actual rule conditions and observation points; imported rules are not backend-compiled or live-validated.
Pinned research references. No browser attack runner or production-validated detector is asserted. Imported procedures remain unvalidated; any bounded lab evidence has its own scope. ATT&CK / Atomic provenance · Detection provenance.