ATT&CK Data Sources
Which log actually carries each ATT&CK data source, on each platform.
ATT&CK names the data source a technique leaves evidence in, and stops there. The next questions are which log that means, whether you collect it, and whether the setting that makes it useful is on.
That last part is where most coverage claims fall apart, so each row ends with what the source cannot tell you.
16 rows.
| Source | Component | What it is |
|---|---|---|
| Process | Process Creation | A process started, with its command line and its parent. |
| Command | Command Execution | The command text itself, including what an interpreter was told to run. |
| File | File Creation / Modification / Deletion | A file appeared, changed or vanished. |
| Windows Registry | Registry Key Modification | A registry value was written. |
| Network Traffic | Network Connection Creation / Traffic Content | A connection was made, and optionally what crossed it. |
| Logon Session | Logon Session Creation | An account authenticated somewhere. |
| User Account | User Account Creation / Modification | An account was created, changed, or given new privileges. |
| Service | Service Creation / Modification | A service was installed or altered, which is the most common persistence mechanism on Windows. |
| Scheduled Job | Scheduled Job Creation | Something was scheduled to run later. |
| Module | Module Load | A DLL or shared library was loaded into a process. |
| Script | Script Execution | An interpreter ran script content. |
| WMI | WMI Creation | A WMI subscription or a remote WMI execution. |
| Active Directory | Active Directory Object Modification | A directory object was queried or changed. |
| Application Log | Application Log Content | Whatever an application itself chose to record. |
| Domain Name | Domain Name / Active DNS | A name was resolved, or a domain was registered. |
| Driver | Driver Load | A kernel driver was loaded. |