<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Liam Roy</title>
    <description>The latest articles on DEV Community by Liam Roy (@liamroy).</description>
    <link>https://dev.to/liamroy</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4246446%2Fcab2d6f6-f7a1-4b8a-a0c2-67b4766c20ad.png</url>
      <title>DEV Community: Liam Roy</title>
      <link>https://dev.to/liamroy</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/liamroy"/>
    <language>en</language>
    <item>
      <title>What a 24/7 NOC Actually Monitors — and What It Doesn't</title>
      <dc:creator>Liam Roy</dc:creator>
      <pubDate>Sun, 15 Nov 2026 19:07:26 +0000</pubDate>
      <link>https://dev.to/liamroy/what-a-247-noc-actually-monitors-and-what-it-doesnt-24ol</link>
      <guid>https://dev.to/liamroy/what-a-247-noc-actually-monitors-and-what-it-doesnt-24ol</guid>
      <description>&lt;p&gt;If you run a 30–80-person company, someone has probably tried to sell you "24/7 monitoring." It sounds like a person watching your network around the clock. Sometimes it is. Often it isn't — it's a dashboard that emails someone the next morning.&lt;/p&gt;

&lt;p&gt;I work at &lt;a href="https://amensecurity.ca" rel="noopener noreferrer"&gt;Amen Security&lt;/a&gt;, a Winnipeg MSP that runs monitoring for small and mid-sized companies. This is the honest version of what a NOC (network operations centre) watches, what it can't watch, and the questions worth asking before you pay for it.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a NOC actually monitors
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;1. Is it up?&lt;/strong&gt;&lt;br&gt;
The basics: servers, firewalls, switches, internet links, and key services (email, file shares, line-of-business apps). A ping or health check every minute or two. If something stops answering, an alert fires. This is the least glamorous part and the most valuable — most outages are found this way, not by a user phoning in.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Is it about to break?&lt;/strong&gt;&lt;br&gt;
Disk filling up, memory exhausted, a UPS battery degrading, a backup job that ran long or failed outright. Good monitoring watches trends, not just thresholds: a disk growing 2% a week will be full in a month, and that's a ticket today, not an outage later.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Is something behaving strangely?&lt;/strong&gt;&lt;br&gt;
A login at 3 a.m. from a country nobody on your team is in. A server suddenly talking to an address it has never contacted. A mailbox rule created that forwards everything externally. These are the signals that matter most — and the ones a threshold alert will never catch on its own. They need someone who knows what "normal" looks like for your company.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Are the safety nets intact?&lt;/strong&gt;&lt;br&gt;
Backups completed — and, more importantly, restorable. Patch levels current. Antivirus/EDR agents actually reporting in, not silently uninstalled or expired. Certificates not about to expire. The unglamorous checks are the ones that decide whether a bad day becomes a disaster.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it doesn't monitor
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;It doesn't read your employees' minds — or their inboxes.&lt;/strong&gt; A NOC sees that email is flowing; it doesn't know that the "invoice" your accounts person just opened was a phishing lure until the EDR or the user reports it. User awareness is still a layer no dashboard replaces.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;It doesn't fix your business processes.&lt;/strong&gt; Monitoring will tell you the CRM is down. It won't tell you that half the sales team has been working around a broken workflow for six months. It measures systems, not whether the systems serve the work.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;It doesn't see inside encrypted traffic it has no business seeing.&lt;/strong&gt; A NOC that promises to inspect everything is either breaking your privacy or overselling. The right scope is metadata and behaviour — what's connecting, how much, how often — not the contents of your team's work.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;It doesn't prevent everything.&lt;/strong&gt; Monitoring shortens the time between "something broke" and "someone is fixing it." It does not make hardware immortal or attackers polite. Anyone selling zero downtime is selling a feeling, not a service.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to ask before you buy it
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Who answers the alert at 2 a.m., and how fast?&lt;/strong&gt; A dashboard that pages a human is different from one that sends an email nobody reads until 9 a.m. Ask for the actual response times in writing.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;What's excluded?&lt;/strong&gt; Printers, personal devices, that one server under someone's desk — the exclusions list is where surprises live.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;How do you know the backup works?&lt;/strong&gt; "Backup completed successfully" is not proof. A restore test is. Ask how often restores are tested and whether you get the report.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;What does an alert look like to me?&lt;/strong&gt; You should get a plain-language summary, not a raw log dump. If you can't understand the report, you can't judge the service.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;What happens when you find something?&lt;/strong&gt; Monitoring without a defined response — who calls whom, who can approve a shutdown, who talks to your team — is just a more expensive way to watch things break.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The short version
&lt;/h2&gt;

&lt;p&gt;A real NOC watches uptime, capacity trends, strange behaviour, and the safety nets — and it has a human who acts on what it sees. It doesn't watch your people, fix your processes, or promise nothing will ever break. If a provider can't tell you plainly what they monitor, what they don't, and who responds at 2 a.m., you're not buying monitoring. You're buying the word "monitoring."&lt;/p&gt;




&lt;p&gt;&lt;em&gt;I'm Liam Roy, CMO at Amen Security — managed IT and web/app development for 30–80-person companies in Winnipeg and across Canada and the US. We start every engagement with a free assessment: we look, report what we find, and only then talk about a contract. &lt;a href="https://amensecurity.ca" rel="noopener noreferrer"&gt;https://amensecurity.ca&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

</description>
      <category>msp</category>
      <category>monitoring</category>
      <category>cybersecurity</category>
      <category>smb</category>
    </item>
  </channel>
</rss>
