Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Adversaries may use scripts automatically executed at boot or logon initialization to establish persistence.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-14 | ✗→✓ | ▲ Improved | -25% | 0% |
| case-15 | ✗→✓ | ▲ Improved | -35% | 0% |
| case-20 | ✗→✓ | ▲ Improved | 72% | 0% |
| case-02 | ✓→✓ | = Same ✓ | 38% | 0% |
| case-03 | ✓→✓ | = Same ✓ | 27% | 0% |
Adversaries may use scripts automatically executed at boot or logon initialization to establish persistence. Initialization scripts can be used to perform administrative functions, which may often execute other programs or send information to an internal logging server. These scripts can vary based on operating system and whether applied locally or remotely.
Adversaries may use these scripts to maintain persistence on a single system. Depending on the access configuration of the logon scripts, either local credentials or an administrator account may be necessary.
An adversary may also be able to escalate their privileges since some boot or logon initialization scripts run with higher privileges.
Platforms: macOS, Windows, Linux, Network Devices, ESXi
> Note: No Atomic Red Team tests available for this technique. See Atomic Red Team GitHub for updates.
Ensure proper permissions are set for Registry hives to prevent users from modifying keys for logon scripts that may lead to persistence.
Restrict write access to logon scripts to specific administrators.
| Finding | Severity | Impact | | --------------------------------------------------------- | -------- | ----------- | | Boot or Logon Initialization Scripts technique applicable | High | Persistence |
| CWE ID | Title | | ------- | ----------------------------- | | CWE-276 | Incorrect Default Permissions |
Other measured skills in the registry, with their headline benchmark lift.