Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
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.

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.
| Tier | Examples | Expectations |
|---|---|---|
| Tier 1 | Identity provider, domain controllers, EDR, VPN and remote access, cloud control plane | Silence alerts within 15 minutes, 12 months retention, loss treated as an incident |
| Tier 2 | Firewall, proxy, DNS, email gateway, critical application audit trails | Silence alerts within an hour, 6 to 12 months retention |
| Tier 3 | General server and workstation logs, non-critical applications | Daily health check, 90 days retention |
| Tier 4 | Development environments, verbose debug output | Best 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.
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.
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.
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.
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.
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.
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.
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.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.