{"id":1350,"date":"2026-11-15T05:30:00","date_gmt":"2026-11-15T05:30:00","guid":{"rendered":"https:\/\/cotocus.org\/blog\/?p=1350"},"modified":"2026-11-16T14:30:00","modified_gmt":"2026-11-16T14:30:00","slug":"soc-ops-six-myths","status":"publish","type":"post","link":"https:\/\/cotocus.org\/blog\/soc-ops-six-myths\/","title":{"rendered":"Six SOC Ops Myths That Refuse to Die (and What Is Actually True)"},"content":{"rendered":"<p>Spend a week around security and IT teams and you will hear the same confident sentences again and again. Some are half right. Some are quite wrong, and a few cost real money. Below are six popular claims about <strong>SOC Ops<\/strong> and checks each against what the published guidance says, using <a href=\"https:\/\/www.xopsschool.com\/soc-ops\/\">the Ops Atlas page for SOC Ops<\/a> as the main reference. Grab a coffee; we will keep it light.<\/p>\n<h2>Myth 1: &#8220;A SIEM plus SOAR means we can drop tier one&#8221;<\/h2>\n<p>It is a lovely idea, and vendors do not discourage it. Reality is more modest. MITRE&#8217;s own wording, which the Atlas relays, is that automation shrank the triage pool but did not eliminate it. Tools can enrich alerts, group duplicates and run lookups. They still hand a pile of ambiguous cases to a person, because deciding whether odd-but-legitimate activity is harmless needs judgement and context.<\/p>\n<p>There is a sequencing point as well. Government guidance quoted by the Atlas says SOAR is usually unsuitable for immature environments. You need a stable, trusted log platform first. Automating a noisy process gives you a faster noisy process.<\/p>\n<h2>Myth 2: &#8220;SOC means SOC 2&#8221;<\/h2>\n<p>This one trips up newcomers constantly because the letters match. They are unrelated. SOC 2 is an assurance report produced under the accounting profession&#8217;s AICPA framework, mostly used to give customers confidence about a service provider&#8217;s controls. A security operations centre is a team that watches for trouble. A company can have either, both or neither. If a sales form asks for a SOC 2 report, nobody is asking about your monitoring room.<\/p>\n<h2>Myth 3: &#8220;SOC and NOC are the same room with different screens&#8221;<\/h2>\n<p>They are distinct functions. A network operations centre watches availability and performance, asking whether things are up and fast. A security operations centre asks whether something is being misused. The two share tools and sometimes talk, but a dashboard full of green availability lights says nothing about an intruder who keeps the network healthy. The Atlas explicitly lists the NOC as out of scope.<\/p>\n<h2>Myth 4: &#8220;If we outsource, the risk goes with it&#8221;<\/h2>\n<p>Contracts can move work. They cannot move accountability. Per MITRE, as the Atlas relays it, the people who own the systems, and the executives above them, stay on the hook. Practically, that means a managed provider deserves the same scrutiny as an internal team: ask for the outcomes recorded per alert, the escalation acceptance rate and the reopen rate, not only the average time to close. Speed-only contract measures tend to reward premature closure.<\/p>\n<h2>Myth 5: &#8220;Our false-positive rate is 30 percent, so we need better detections&#8221;<\/h2>\n<p>Two things are wrong with this sentence. First, the figure on most dashboards is really the share of alerts that turned out not to be real, which statisticians call the false discovery rate (one minus precision). A true false-positive rate would need a count of true negatives, and a SOC never sees those. Second, research cited by the Atlas found that most things people call false positives are benign positives, legitimate activity that lacked context. Rewriting the detection is often the wrong lever. Adding context for the analyst is usually cheaper.<\/p>\n<h2>Myth 6: &#8220;We track MTTR, so we are covered&#8221;<\/h2>\n<p>Which MTTR? The abbreviation can stand for time to respond, recover, repair or resolve, and teams argue about it in the same meeting without noticing. The Atlas suggests naming the exact interval instead: time to first human triage, time to decision, time to containment. It also warns against reporting any of them as a single mean. MITRE gives a memorable illustration of one two-day-old email wrecking an average. Medians with a 90th percentile are harder to distort.<\/p>\n<p>A related slip is treating the first-line analyst as an entry-level chore. The Atlas describes tier one as a growth position rather than an underclass, and the reasoning is sound: the person who sees the raw alert first shapes everything downstream. Teams that rotate people through triage, and let them propose rule improvements, tend to keep their analysts longer and learn faster about their own environment.<\/p>\n<h2>A bonus misunderstanding about the name<\/h2>\n<p>You may notice the term itself is a little slippery. The Atlas says the function is established, while &#8220;SOC Ops&#8221; as a phrase is its own informal label. MITRE lists seven different names for such teams, and the European agency ENISA notes that a small firm often has one group doing both jobs under whichever name it likes. So if a colleague insists the proper term is something else, they may well be right, and it does not change how the work should run.<\/p>\n<h2>Why these myths persist<\/h2>\n<p>Each myth is attractive because it promises a shortcut: automation replaces people, a certificate stands in for operations, a contract hands off risk, a single number summarises health. Operations teams in any discipline know the pattern. When you read about incident handling in other settings, such as our guide to <a href=\"https:\/\/cotocus.org\/blog\/mastering-incident-management-with-aiops-for-faster-resolution\/\">managing incidents faster with intelligent operations tooling<\/a>, the same warning appears: tools support judgement, they do not substitute for it. And the planning perspective in <a href=\"https:\/\/cotocus.org\/blog\/aiops-roadmap-a-practical-guide-for-devops-sre-and-operations-teams\/\">a practical route for operations teams to adopt machine-assisted tooling in stages<\/a> makes a similar point about sequencing.<\/p>\n<p>Next time one of these six comes up in a meeting, you have a polite reply. Ask which interval is being measured, which function is meant, who stays accountable and what the closing reason was. Those four questions defuse most of the myths before lunch.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Six stubborn myths about SOC Ops, from automation replacing tier one to SOC 2 confusion and the so-called false-positive rate, each checked against the record.<\/p>\n","protected":false},"author":4,"featured_media":1351,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[130],"tags":[],"class_list":["post-1350","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-it-operations"],"_links":{"self":[{"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/posts\/1350","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/comments?post=1350"}],"version-history":[{"count":1,"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/posts\/1350\/revisions"}],"predecessor-version":[{"id":1450,"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/posts\/1350\/revisions\/1450"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/media\/1351"}],"wp:attachment":[{"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/media?parent=1350"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/categories?post=1350"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cotocus.org\/blog\/wp-json\/wp\/v2\/tags?post=1350"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}