What to inspect
- Service name.
- Image path.
- Start type.
- Service account.
- Creation time.
- Change ticket or deployment context.
Investigate newly created Windows services as possible administrative changes or persistence-related evidence.
Event ID 7045 can record the creation of a new service. A new service may be legitimate software installation or administration, so context is essential.
Use this page after the daily quiz: learn the concept first, then follow the investigation workflow and examples.
What context should you validate before classifying a new Windows service as suspicious?
Quiz flow: introduce this topic briefly on social media, ask the question, reveal the answer, then send learners here for the detailed investigation.
Service installation events can help identify persistence or a legitimate software deployment. Validate service name, binary path, start type, installer or change ticket, creating account, host role, and nearby process events before escalating.
In the simulated case, compare the service’s creation time with deployment activity and inspect the path and owner. A new service is an investigation lead, not a verdict; follow local change records and preserve evidence before remediation.
Continue practicing: open a fictional mission and test your reasoning against the simulated evidence.