What attackers do. Attackers set up programs to start automatically when a system boots or a user logs on, using locations such as registry run keys, startup folders, login items or authentication packages. This serves Persistence and Privilege Escalation.
How to defend. Monitor the common autostart locations with endpoint tools and baseline what normally runs at startup. Use application control so new autostart entries cannot launch untrusted code, and limit admin rights that many autostart methods require.
Signs to look for. Look for new run key entries pointing to user folders, shortcuts added to startup folders, unusual login items on macOS and changes to authentication or security packages. A common gap is checking only the most common registry keys while attackers use less known ones.