Inventory service accounts with their recent authentication context

Use this document to connect an official requirement or behavior to observable evidence: Inventory service accounts with their recent authentication context. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official Investigate and protect Service Accounts from Microsoft supports the following bounded statements:

• Service accounts often have elevated privileges but generally cannot use modern authentication protections such as MFA in the same way as human accounts. The research record locates this support at Opening risk overview.
• Automatic discovery identifies gMSA and sMSA accounts and user accounts meeting criteria such as an SPN plus password-never-expires, and presents recent authentication sources and destinations. The research record locates this support at Auto-discovery section.

The source support ends with the statements listed above. Use them to examine identity alerts, investigations, remediation roles, evidence retention, escalation, exclusions, and incident workflows in the applicable environment, not to imply a wider guarantee.

What the source does not establish

Classification criteria identify candidates, not confirmed business purpose, ownership, necessity, or compromise. No current deployment state or change approval follows from the source alone. Validate Active Directory, Windows DNS, time, cloud portals, endpoint data, network telemetry, privileged access, and response staffing, and treat examples or options as conditional inputs rather than defaults.

Applicability questions

• For source statement 1 at Opening risk overview, which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Auto-discovery section, which observable configuration, record, or test can confirm applicability here?
• Which deployed instance of identity alerts, investigations, remediation roles, evidence retention, escalation, exclusions, and incident workflows will be compared with the source, and why that instance?
• How will the review distinguish a source mismatch from a failure in Active Directory, Windows DNS, time, cloud portals, endpoint data, network telemetry, privileged access, and response staffing?
• Who approves the conclusion, exception, test window, and rollback threshold?

DSE recommendation:

DSE recommends using the cited source as the evidence anchor for this decision. Make the source, asset scope, owner, and expected outcome explicit in the review record. Record the source location, examined part of identity alerts, investigations, remediation roles, evidence retention, escalation, exclusions, and incident workflows, observed and expected states, owner, and reason for deviation.

Do not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify Active Directory, Windows DNS, time, cloud portals, endpoint data, network telemetry, privileged access, and response staffing. Handle credentials, keys, recovery data, and personal information through approved secure channels.

Verification and evidence

Evidence should let another reviewer reproduce this decision. Retain observations beside the traced locations Opening risk overview; Auto-discovery section. Favor alert records, investigation timelines, analyst actions, tuning or exclusion approvals, remediation results, and case closure, linked to stable identifiers, time, and operator.

Record the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.

Official references

• Investigate and protect Service Accounts — Microsoft