TechKnowSurge
NIST CSF DE.CM-01 NIST 800-53 SI-4 CompTIA CySA+ 1.1 CompTIA Security+ 4.4
TechKnowSurge Catalog Videos Benchmarking
VideoSecurityFree

Benchmarking

Benchmarking establishes a baseline for normal system performance, enabling IT teams to quickly determine whether observed metrics represent a real problem or standard operating behavior. It is a foundational component of effective network troubleshooting and infrastructure monitoring.

⚑ Complete this video to capture a CTF flag worth 1 point.

About this video

Benchmarking is the process of documenting normal operating conditions for systems, devices, and network infrastructure so that deviations can be recognized and acted upon quickly. Rather than evaluating metrics in isolation, benchmarking provides the historical and operational context needed to determine whether a reading is cause for concern or simply a reflection of how a system has always behaved. Logging and monitoring tools play a central role in this process by continuously collecting performance data and making it possible to compare current conditions against established norms. In a practical troubleshooting scenario, a router showing 90% CPU utilization might appear alarming at first glance, but without a benchmark, there is no reliable way to know whether that reading is abnormal. If monitoring data shows the router has consistently operated at 90%, that metric is unlikely to be the source of a current network problem. Conversely, if the established benchmark for that device is 20% CPU usage, the spike to 90% becomes a significant finding that warrants deeper investigation. Benchmarking transforms raw data into actionable intelligence, allowing engineers to prioritize their efforts and avoid pursuing false leads. Without it, infrastructure troubleshooting lacks the reference point needed to separate symptoms from root causes.

What you'll learn

What's covered

Benchmarking in IT Infrastructure

Aligned to

NIST CSF
DE.CM-01 Networks and network services are monitored to find potentially adverse events.
NIST 800-53
SI-4 System Monitoring
CompTIA CySA+
1.1 Explain the importance of system and network architecture concepts in security operations.
CompTIA Security+
4.4 Explain security alerting and monitoring concepts and tools.

Key terms

Benchmarking
The process of establishing standard performance metrics for a system to serve as a reference point for identifying abnormal behavior during troubleshooting.
Baseline
A documented set of minimum security standards or performance metrics used as a reference point.
Bandwidth
The maximum rate of data transfer across a network path, typically measured in bits per second.
Latency
The time delay between sending a request and receiving a response over a network.
Simple Network Management Protocol
SNMP
A protocol used to monitor and manage network devices such as routers, switches, and servers.

Topics

Benchmarking Network Troubleshooting Baseline Metrics Performance Monitoring Infrastructure Monitoring Networking

Transcript

One thing that these different logging and monitoring systems will do is they'll start creating benchmarking. Benchmarking is an important part of troubleshooting and figuring out what's going on within your infrastructure. So let's talk about benchmarking and what it looks like.

Is it really the problem?

Let's say there's an issue on our network and we start troubleshooting what is going on on our network. Maybe there's some really slow network bandwidth that's happening and we need to figure out where it's coming from. We look on one of our routers and we notice that the router is sitting at 90% CPU usage. And so a lot of the resources are being used up on this router. But is that the problem? Or is it just something that's related to the problem, not the problem itself? Or perhaps this doesn't have anything to do with the problem at all. Well, how can we tell? Well, one way we can tell is by benchmarking.

Setting the standard

Benchmarking is when we set the standard, or what is the standard operating procedure, what is the standard way in which things operate. And if we have tested and set up all of our monitoring ahead of time, and maybe we're always sitting at 90%, now we just recognize it because we have an issue, and maybe it's not part of the issue that we're having right now. So that's what benchmarking is used for.

Or maybe perhaps we notice now that benchmarking is usually set at 20% for CPU rate. Now we know that this 90% is off, and that we might want to dig into it further and spend more time researching why are we getting 90%, because that could be the core of what the issue is.

So really benchmarking is a huge part. Without it, we're kind of blindly troubleshooting, but with it we are able to really quickly identify.

About TechKnowSurge

TechKnowSurge builds IT and cybersecurity professionals through hands-on, concept-first training built around real understanding — not memorization. Free interactive tools, structured programs, and 25+ years of real-world experience, all in one place.

Explore free tools and programs →