Persistence through account manipulation involves creating new accounts or modifying existing ones to maintain long-term access to a compromised system. Attackers leverage these accounts to avoid detection and regain access even after reboots or security measures.
Attackers can establish persistence in two main ways:
LocalAccountTokenFilterPolicy, granting full admin privileges remotely.| Event ID | Description | Notes |
|---|---|---|
| 4720 ⭐ | User Account Created | Detects new local/domain account creation. |
| 4732 ⭐ | Member Added to a Privileged Group | Flags privilege escalation (e.g., adding a user to Administrators). |
| 4738 | User Account Modified | Useful for detecting suspicious changes (e.g., enabling disabled accounts). |
| 4781 | Account Name Changed | Could indicate an attacker trying to mask activity. |
| 4624 | Successful Logon | Logon Type 10 (RDP) or 3 (Network) can indicate persistence use. |
| 4648 | Explicit Credential Use | Detects account switching (e.g., runas). |
| 4672 ⭐ | Special Privilege Assigned | Indicates high-privilege login (e.g., Administrator, SYSTEM). |
| Event ID | Description | Notes |
|---|---|---|
| 1 ⭐ | Process Creation | Track suspicious processes (e.g., net user, wmic, PowerShell). |
| 12 | Registry Modification | Detects changes to LocalAccountTokenFilterPolicy (UAC Bypass). |
| 13 ⭐ | Registry Key/Value Modification | Look for HKLM\\SAM\\SAM\\Domains\\Account\\Users. |
| 3 | Network Connection | Monitor for unexpected remote access via SMB, WinRM, RDP. |