Join our Newsletter — 33% off our NHI Course
Home› FAQ› Cyber Security› How should SOC teams decide what logs to…
Cyber Security

How should SOC teams decide what logs to collect first?

← Back to all FAQ
By NHI Mgmt Group Editorial Team Updated November 2, 2026 Domain: Cyber Security

They should start with the investigative questions the SOC must answer, such as who performed an action, what changed, and whether privilege or control state was altered. Collection should follow mission risk and detection goals, not available integrations or log volume. That approach keeps telemetry aligned to actual response needs and reduces low-value overcollection.

What should drive the first wave of log collection?

Start with the questions your analysts must answer during an investigation, then collect the telemetry that proves or disproves those questions. For a SOC, that usually means event sources that show actor identity, action, change, and privilege state. If a log source cannot help answer a likely incident question, it should not outrank a source that can.

The practical test is simple: if an analyst needs to establish who did what, when, from where, and with what level of authority, the log source belongs near the top of the queue. That makes logging a response capability, not a storage exercise, and keeps collection aligned to detection and containment decisions rather than vendor coverage.

How do mission risk and detection goals set the priority order?

Priority should follow the business and security scenarios that matter most, not the easiest integrations to switch on. High-value identity events, admin actions, authentication failures, changes to access rights, and modification of critical systems usually come before broad, low-signal telemetry. The goal is to reduce uncertainty in the cases that would force escalation or containment.

A useful way to rank sources is by the harm that delayed visibility would create. Logs tied to privileged access, critical assets, or externally exposed services tend to deserve earlier collection because they shorten the time to confirm compromise and scope impact. By contrast, logs that are interesting but rarely decisive can wait until the core investigative trail is in place.

For a broader SOC roadmap, NHIMG’s SOC Guide is useful for placing log priorities inside the wider operating model, while the Building a SOC from Scratch Guide helps connect first-year logging choices to charter, first functions, and log source priorities.

What does good early log collection look like in practice?

Good early collection is narrow enough to be manageable but broad enough to support triage and reconstruction. Teams should aim to capture sources that reveal authentication, privilege changes, administrative activity, and changes to security-relevant configuration or control state. That gives analysts a defensible path from alert to root cause without forcing them to rely on guesses or manual reconstruction.

It also helps to collect logs in the same order you expect to use them. If your first incident questions involve account activity, privilege escalation, or service misuse, then the first log feeds should support those questions directly. If the first wave is too infrastructure-driven, teams often end up with lots of data and very little investigative leverage.

For log retention and investigation design, Identity Telemetry Requirements is a useful reference because it focuses on the event fields and sources needed for investigations, not just raw collection volume. For operational handoff and continuity, the SOC Shift Handover Template is relevant where logs must support open cases, containment actions, and accepted risk across shifts.

Risk and Threat Considerations

Poor log ordering creates two common failures: blind spots in the incidents that matter most, and noisy collection that overwhelms analysts before it improves detection. Attackers benefit when the earliest telemetry does not cover identity, privilege, or security control changes, because those are often the events that show initial access, escalation, or persistence.

Failure mechanism: Teams collect whatever is available first, so the SOC gets high-volume telemetry before it has the event trail needed to answer core investigative questions. That weakens both triage speed and post-incident reconstruction, especially where access abuse or control-state changes are part of the attack path.

Impact: The SOC may detect later, scope incidents less accurately, or miss the evidence needed to confirm whether privileged action occurred. In the worst case, containment decisions are made with incomplete context, which can prolong attacker dwell time or cause unnecessary disruption.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

MITRE ATT&CK addresses the attack and risk surface, while NIST CSF 2.0, NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST CSF 2.0DE.CM-01 — Networks and services are monitored to find potentially adverse eventsSOC log collection directly supports monitoring for adverse events.
Recommendation — Prioritise telemetry that improves continuous monitoring for adverse events.
NIST SP 800-53 Rev 5AU-2 — Event LoggingThe question is fundamentally about which events should be logged first for investigations.
AU-6 — Audit Record Review, Analysis, and ReportingCollected logs must support analysis that answers who acted and what changed.
Recommendation — Define event categories to log based on investigative need and mission risk. Select logs that enable timely analysis, correlation, and reporting.
CIS Controls v8CIS-8 — Audit Log ManagementThe subject is log prioritisation for security operations and investigation.
Recommendation — Focus log collection on events needed for detection, investigation, and response.
MITRE ATT&CKTA0006 — Credential AccessIdentity and privilege events help reveal credential abuse and compromise paths.
Recommendation — Map early logs to credential-access behaviors you need to detect and investigate.

Practitioner Guidance

What to prioritise: Collect the sources that answer your top investigative questions first, especially identity, authentication, privilege, and control-state telemetry. If a log feed cannot help resolve a realistic incident scenario, it belongs behind sources that can.

Decision rule: If two sources compete for implementation time, choose the one that most directly supports who-did-what and privilege-change analysis. Save broad, low-yield telemetry until the SOC can already reconstruct the incidents it expects to face.

Practitioner takeaway: The right collection order is the one that most quickly turns an alert into a defensible incident narrative, not the one that produces the most data.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 2, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org