Skip to content

Persistence

github-actions[bot] edited this page Nov 19, 2026 · 2 revisions

Windows persistence techniques mapped to MITRE ATT&CK, covering registry, service, scheduled task, and application-based persistence mechanisms. Source: Pentest Laboratories.

Purpose: A defensive inventory of Windows mechanisms that can make code re-execute after reboot, logon, or another trigger. It is host-level persistence (surviving a reboot or logoff), distinct from Domain Persistence, which covers persistence at the AD/domain level.

Function: The techniques cluster into families based on what triggers re-execution: logon-time (Winlogon Helper, Registry Run Keys, PowerShell Profile, Screensaver), service-based (New/Modified Service, Port Monitors, Time Providers - all run as SYSTEM), event-driven (WMI Event Subscription - fires on arbitrary system conditions, not just boot/logon), and hijacking-based (DLL Search Order, COM Hijacking, Netsh Helper DLL, DLL Proxy Loading - abuse how Windows locates and loads code rather than registering a new autostart entry at all). Visibility varies by mechanism and telemetry; hijacking techniques can alter legitimate load paths and may require targeted checks.

Goal: Help defenders inventory relevant autostart locations and validate detection and recovery coverage. This list is not exhaustive; coverage depends on Windows versions, configuration, and telemetry. During a controlled exercise, simulate only the mechanisms necessary to answer a defined test question.

When & how to use this: During red-team work, use a lab or a specifically approved simulation, one mechanism at a time, with a documented rollback and cleanup verification. Do not plant multiple live mechanisms as the default test approach. During defensive/hunt work, use this as a structured sweep list - most EDR "autoruns"-style tooling covers the registry/service/scheduled-task items natively, but the hijacking-family items (DLL search order, COM hijacking) usually require manual or purpose-built hunting since they don't register in a conventional autostart location.


Persistence control validation workflow: define scope, simulate one approved mechanism, observe controls, then remove it and verify restoration

Code Technique Mitre
PE-001 Winlogon Helper DLL T1547.004
PE-002 Port Monitors T1547.010
PE-003 Accessibility Features T1546.008
PE-004 Shortcut Modification T1547.009
PE-005 Modify Existing Service T1543.003
PE-006 DLL Search Order Hijacking T1574.001
PE-007 Change Default File Association T1546.001
PE-008 New Service T1543.003
PE-009 Scheduled Tasks T1053.005
PE-010 Service Registry Permission Weakness T1574.011
PE-011 Registry Run Keys T1547.001
PE-012 WMI Event Subscription T1546.003
PE-013 Security Support Provider T1547.005
PE-014 AppInit DLLs T1546.010
PE-015 Component Object Model Hijacking T1546.015
PE-016 Netsh Helper DLL T1546.007
PE-017 Office Application Startup T1137
PE-018 Application Shimming T1546.011
PE-019 Screensaver T1546.002
PE-020 Image File Execution Options Injection T1546.012
PE-021 BITS Jobs T1197
PE-022 Time Providers T1547.003
PE-023 PowerShell Profile T1546.013
PE-024 Waitfor N/A
PE-025 RID Hijacking N/A
PE-026 AMSI N/A
PE-027 Print Spooler N/A
PE-028 Certificates N/A
PE-029 Notepad++ N/A
PE-030 Event Log N/A
PE-031 Event Log Online Help N/A
PE-032 Context Menu N/A
PE-033 Service Control Manager N/A
PE-034 DLL Proxy Loading N/A
PE-035 Windows Telemetry N/A
PE-036 Scheduled Task Tampering N/A
PE-037 Junction Folder N/A
PE-038 Library Files N/A
PE-039 Disk Clean-up N/A
PE-040 Windows Setup Script N/A
PE-041 Visual Studio Code Extensions N/A
PE-042 Explorer N/A

๐Ÿ“– Use These Checklists Responsibly: Authorization is MANDATORY

Attack techniques are powerful - use them ethically and legally.

Repository: ULTIMATE CYBERSECURITY MASTER GUIDE

Maintained by: Pacific Northwest Computers


โš ๏ธ Authorized testing only: confirm authority and scope before active testing. โš ๏ธ

โš ๏ธ Legal consequences depend on the conduct and applicable law; see 18 U.S.C. ยง1030 and DOJ CFAA charging policy. โš ๏ธ

โš ๏ธ For systems you do not own or administer, confirm authorization in advance and document scope in writing where policy, law, or contract requires it. โš ๏ธ

โญ Star this repo if you find it useful! โญ

## Related Files - [README.md](https://github.com/Pnwcomputers/ULTIMATE-CYBERSECURITY-MASTER-GUIDE/wiki/Checklists) - Checklists section index

๐Ÿ“„ Source: Checklists/Persistence.md | โœ๏ธ Suggest an edit | โฌ…๏ธ Back to Checklists

Clone this wiki locally