Skip to content
Cyber Defense Technologies

Insights

Building a SOC That Fits a Mid-Size Contractor

A security operations center does not have to mean a room full of screens and a 24/7 staff of twenty. How a mid-size organization can get real detection and response: what to monitor first, which roles it needs, when to build and when to partner, and how to measure whether it works.

By Cyber Defense Technologies November 20, 2026 4 min read

Ask a mid-size defense contractor whether it has a security operations center (SOC) and the answer is often "not really." There is an IT team, a firewall, endpoint protection and a lot of logs nobody reads. Then an incident arrives, and the question becomes how long the attacker had been inside.

A SOC is not a room full of screens. It is a capability: the people, process and technology that notice an attack and respond to it. This article describes how to build one that fits an organization of a few hundred people.

What a SOC actually does

  • Monitor: collect the signals that reveal attacks.
  • Detect: turn those signals into alerts that mean something.
  • Triage: decide quickly which alerts are real.
  • Respond: contain, investigate and recover.
  • Improve: learn from every incident and exercise, and feed that back into detection.

What a SOC does

  1. 1 Monitor

    Collect signals from identity, endpoints, edge devices, email and sensitive systems.

  2. 2 Detect

    Turn signals into alerts a person will act on.

  3. 3 Triage

    Decide quickly which alerts are real.

  4. 4 Respond

    Contain, investigate and recover.

  5. 5 Improve

    Feed lessons from incidents and exercises back into detection.

Every incident and exercise makes the next detection better.

Monitor what matters first

Logging everything is expensive and noisy. Start where attacks begin and where they do the most damage:

  1. Identity. Sign-ins, MFA events, new accounts, privilege changes and new mailbox rules. Most modern intrusions involve stolen or misused credentials; see Identity Is the New Perimeter.
  2. Endpoints. Endpoint detection and response (EDR) on every laptop and server, with alerts going somewhere a person will see them.
  3. Edge devices. Firewalls, VPNs and remote access gateways, which are among the most attacked systems on the internet.
  4. Email. Delivered phishing, user reports and suspicious forwarding.
  5. Sensitive systems. Access to the servers, enclaves and applications that hold your most valuable data.

Our guide to Logging That Helps an Investigation covers what to keep and for how long.

Turn signals into useful alerts

Tools arrive with hundreds of default rules. Most organizations drown in alerts within a month. Instead:

  • Prioritize detections for the techniques attackers actually use against organizations like yours, such as credential theft, living-off-the-land activity and ransomware precursors.
  • Tune ruthlessly. Every alert should be something a person will act on. If an alert is always ignored, fix it or remove it.
  • Write runbooks for the most common alerts, so triage is consistent no matter who is on shift.

The roles you need

A mid-size SOC does not need a large staff, but it needs clear roles:

  • A SOC lead who knows the business, owns the program and makes decisions during incidents.
  • Analysts who triage alerts and investigate.
  • An engineer who maintains log sources, tools and detections.
  • An incident response lead, often the SOC lead, with authority to contain systems.
  • Executive contacts for decisions about business impact, legal obligations and communication.

In a small organization, one person may wear several hats. What matters is that every role has a name.

Build, buy or hybrid

Fully in-house gives the most control but is hard to staff around the clock. Covering 24 hours a day, 7 days a week, with time off and training, takes more people than most mid-size organizations can justify.

Fully outsourced provides coverage quickly but can leave a provider monitoring an environment it does not understand, sending alerts nobody inside can act on.

Hybrid works best for most: an in-house lead and a small team who know the business, with a managed security partner providing after-hours monitoring and surge capacity. The partner watches; the internal team owns decisions.

Measure whether it works

  • Time to detect: how long between an attacker's first action and an alert a person sees.
  • Time to respond: how long from alert to containment.
  • Coverage: the share of critical systems sending the logs your detections need.
  • Detection testing: how often you confirm, through purple team exercises or simulation, that detections fire when they should.

Run a tabletop exercise at least twice a year so the response side is rehearsed, not just the monitoring side.

How CDT can help

CDT's managed security service provides monitoring and response alongside your team, our cyber hunt team looks for threats your tools missed, and our incident response team is ready when something gets through.

Sources

Let's talk

Ready to strengthen your security posture?

Talk with a CDT engineer about your mission, your systems and your deadlines. We'll tell you honestly what it takes.