Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is Log Source Criticality?

Log source criticality ranks your sources by how much detection and investigation depend on them. The ranking decides what gets monitored for silence, retained longest, and restored first.

Illustration for the cybersecurity term Log Source Criticality
Home / Blog / Cybersecurity Terms / What Is Log Source Criticality?
17 November 2026

What Is Log Source Criticality?

What Is Log Source Criticality?

Not all logs are worth the same. The authentication records from your identity provider answer the first question of nearly every investigation; the debug output of an internal reporting tool answers none. Log source criticality is the deliberate ranking that makes that difference explicit, so that attention, budget, and retention follow value rather than volume.

What Drives the Ranking

A Workable Tiering

TierExamplesExpectations
Tier 1Identity provider, domain controllers, EDR, VPN and remote access, cloud control planeSilence alerts within 15 minutes, 12 months retention, loss treated as an incident
Tier 2Firewall, proxy, DNS, email gateway, critical application audit trailsSilence alerts within an hour, 6 to 12 months retention
Tier 3General server and workstation logs, non-critical applicationsDaily health check, 90 days retention
Tier 4Development environments, verbose debug outputBest effort, short retention or not collected

The cloud control plane deserves its tier-one place more than most organisations grant it. AWS CloudTrail, Azure activity logs, and Google Cloud audit logs are the only record of administrative action in environments where a single API call can expose a database, and they are frequently onboarded late because nobody owns them.

The Point of the Exercise: Detecting Silence

Classification is only useful if it changes behaviour, and the behaviour it should change first is how quickly you notice a source has stopped. A tier-one source that goes quiet is a potential attacker action, since disabling logging is a standard step before anything noisy. Build volume baselines per source by hour of day and alert on deviation, with the alerting threshold and the response time set by tier.

Treat prolonged silence from a tier-one source as an incident rather than a ticket. The common objection is that these alerts are usually caused by maintenance, which is true and is exactly why the change process should tell the SOC in advance.

Using the Ranking Elsewhere

The tiers answer several questions that are otherwise argued about repeatedly. Which sources go in the expensive hot tier, which is the first input to retention planning. Which sources are restored first when the logging platform fails. Which onboarding request jumps the queue. And which sources justify redundant collection paths, because a tier-one source behind a single collector is a single point of failure for a large part of your detection estate.

The ranking should also be reconciled with your detection coverage map. A technique you believe you cover, depending on a source ranked tier three and monitored weekly, is covered less well than the map suggests.

Keeping It Current

Review the classification when a new source is onboarded, when a rule set changes materially, and after any incident where a missing source cost time. The usual drift is downward: sources added for a project stay at their initial tier long after detections have come to depend on them. A quarterly reconciliation between the rule inventory and the source list catches most of it.

Finally, publish the list. Platform teams who know that a server’s logs are tier one behave differently during a migration than those who think logging is a background concern, and that change in behaviour prevents more outages than any monitoring rule. At Privia Security, source tiering is one of the first deliverables in our SOC maturation services, because it makes every later decision easier to justify.

FAQ – Frequently Asked Questions

Which Log Sources Are Always Tier One?

Identity and authentication systems, domain controllers, endpoint detection telemetry, remote access and VPN, and the cloud control plane. These support the largest share of detections and answer the questions every investigation begins with. Add any system that is the sole record of access to regulated data, since uniqueness matters as much as volume when evidence is needed later.

How Quickly Should a Missing Log Source Be Noticed?

Within 15 minutes for tier-one sources and within an hour for tier two. Silence is both an operational failure and a potential attacker action, because disabling logging is a standard precursor to noisy activity. Build per-source volume baselines by hour of day, alert on significant deviation, and ensure planned maintenance is communicated so genuine gaps stand out.

Does Criticality Change the Retention Period?

Yes, and it is the main input. Tier-one sources justify twelve months or more with a long hot window, because they answer how an intrusion began and are irreplaceable. Lower tiers can be retained for shorter periods or kept only as aggregates. Setting retention per tier rather than globally is what makes long retention affordable for the sources that actually need it.

Who Should Own the Classification?

Security operations should own it, because they know which detections depend on which sources, with input from platform owners on feasibility and from compliance on mandated sources. Publish the list so infrastructure teams understand the consequence of a change, and reconcile it quarterly against the rule inventory, since dependencies accumulate faster than classifications are reviewed.

Related Terms

You May Be Interested In These

What Is Nuclei?

Cybersecurity Terms

17 November 2026

What Is Nuclei?

Read More
What Is AI-Assisted Phishing?

Cybersecurity Terms

17 November 2026

What Is AI-Assisted Phishing?

Read More
What Is C2PA Content Provenance?

Cybersecurity Terms

17 November 2026

What Is C2PA Content Provenance?

Read More