AI SOC Software vs MDR: Five Tests for Buyers

The same investigation screen can sit behind a software license or a 24/7 managed outcome. That is why AI SOC software vs MDR cannot be settled by watching the agent work.

Artificial intelligence (AI) Security Operations Center (SOC) software is a platform the customer runs itself, where agents investigate alerts and the buyer's own analysts keep the queue. Managed detection and response (MDR) is a service in which the provider monitors, investigates, and responds under a service level agreement (SLA), selling the outcome rather than the tool. Co-managed delivery sits between them and splits the work by case type, by hour, or by action.

The product boundary is collapsing, but the contract remains sharp. Test queue ownership and the SLA together, then response permissions, required humans, integration burden, and commercial alignment. Those five tests establish whether you are buying capacity or transferring an outcome.

A buyer can run identical alerts through either model and still receive a different service. Software returns an investigation into a queue the customer operates. MDR adds people, process, escalation, and an obligation to keep that queue moving. The decision starts with the operating state you can sustain after launch, including nights, weekends, incidents, and vendor failures. Feature parity does not create accountability parity.

Key takeaways

• AI SOC software leaves the alert queue, escalation, and closure with the buyer, while managed detection and response (MDR) transfers those duties to the provider under a service level agreement.
• Five contract tests separate AI SOC software from MDR: queue and SLA ownership, response authority, required humans, integration burden, and pricing alignment.
• Dropzone stays purely software and lets managed security service provider (MSSP) partners keep the services revenue, while Exaforce, 7AI, and TENEX sell platform and managed modes from the same technology.
• Vendor autonomy claims describe capability, not authority: the contract decides which actions an AI SOC agent may take without a human approver.
• Practitioners report AI SOC pricing drifting back toward per-alert and per-ingest units, so compare cost per correctly resolved case rather than subscription price.

Why the Product Boundary Is Collapsing

Software vendors are adding analysts while MDR operators build software. The interface no longer reveals the responsibility beneath it, and the same blurring runs through the five business models mapped across AI IT and security services.

Dual-mode platforms

Exaforce sells a customer-operated platform built on four Exabots and also offers Exaforce MDR with human analysts and 24/7 monitoring (Exaforce MDR). 7AI similarly offers a customer-run foundation, PLAID ELITE managed service, and a base for partner-built services (7AI).

The same technology can therefore support two businesses. In one, the customer operates the queue and keeps the productivity gain. In the other, the vendor supplies coverage and captures more of the service revenue.

Operators now expose platforms

AirMDR documents an agentic workflow that ingests alerts, selects investigation playbooks, gathers evidence, and records decisions (AirMDR). TENEX offers security information and event management (SIEM) optimization, co-managed Agentic Overwatch, and fully managed Agentic MDR on Google SecOps and Microsoft Sentinel (TENEX). Both combine software with human operation.

Dropzone provides the cleaner software boundary. It says it is 100% software and that MSSP partners retain services revenue (Dropzone).

Category labels now describe a center of gravity, not a complete offer. Read the order form, SLA, response matrix, and staffing schedule before deciding what you bought, and normalize every proposal against the same contract fields:

Exaforce and 7AI can occupy more than one column because they sell different delivery modes. TENEX deliberately spans implementation, Overwatch, and MDR. AirMDR centers managed delivery, while Dropzone stays closest to the software column (Exaforce, 7AI, TENEX, AirMDR, Dropzone). Column position is the first thing that separates the five AI SOC vendors compared feature by feature.

That table belongs in the buying memo and in whatever vendor scorecard you keep. It stops procurement comparing a license with a staffed service and calling the cheaper line item the winner.

Test 1: Who Owns the Queue and the SLA

Start with one question: who is responsible for every alert still open at 2am?

Self-operated queue

With software, the customer's analysts own intake, review, escalation, response, and closure. The platform may handle most evidence gathering, but unfinished or uncertain cases return to the buyer. Dropzone's channel model keeps the service and the revenue with the MSSP, which also keeps that operating obligation (Dropzone).

Co-managed backstop

Co-managed delivery splits the work. TENEX's Agentic Overwatch leaves the queue with the customer while adding its agentic operating layer (TENEX). That suits a capable team that needs investigation capacity but wants to retain response and customer communication.

The split needs precision. Define which cases the provider reviews, escalation hours, handoff acceptance, queue aging, and who acts if neither side recognizes an owner.

Provider-owned outcome

AirMDR positions human experts as supervisors and exception handlers around its virtual analyst (AirMDR). Exaforce MDR provides continuous monitoring with analysts and Exabots (Exaforce MDR). PLAID ELITE and TENEX Agentic MDR also move daily operation toward the provider (7AI, TENEX).

Request a responsibility matrix covering monitoring, investigation, containment, notification, remediation, and post-incident work, then test it with four cases before signing: a routine false positive, an urgent true positive, an unavailable customer approver, and a surge across several environments. Record who accepts each case, when the SLA starts, when ownership changes, and what happens when the receiving party never acknowledges the handoff. If queue ownership is vague, the staffing obligation is only hidden.

Separate product uptime from outcome coverage. A platform can be available while a critical alert waits in the customer's queue. An MDR SLA can promise monitoring while excluding response for an unsupported connector. Ask for queue-aging reports, escalation time by severity, service credits, manual fallback, and the capacity plan for incident surges.

TENEX's three-path model is useful because it exposes how ownership can move in stages (TENEX). Map AirMDR, Exaforce MDR, and 7AI's managed option onto the same continuum, then write the exact local responsibility split. The product name cannot do that work.

Test 2: What Can the Agent Do Without Approval

An investigation conclusion and a containment action carry different risk. Vendor claims about autonomy often blur them.

Investigate versus contain

Reading logs, enriching an identity, and building a timeline are usually reversible. Disabling an account, isolating a server, or blocking traffic can interrupt the business. Exaforce spans detection through response, but the customer still needs explicit action boundaries in either platform or MDR mode (Exaforce MDR).

AirMDR describes a documented workflow with escalation and human review for critical alerts (AirMDR). Dropzone describes autonomous investigation through existing tools, while the buyer or MSSP remains the service owner (Dropzone).

Approval is a product decision

Classify every action as read-only, automatically permitted, one-click approved, or prohibited. Then assign an owner, an expiry time, and a fallback. A response requiring approval is only useful if an authorized person is available inside the promised window.

Build the ladder during the pilot. Begin with read-only evidence collection and case creation. Add reversible blocks once conclusions are repeatable. Keep account disablement, endpoint isolation, production changes, and regulatory notification behind explicit authority until rollback and escalation have been tested.

Audit and rollback

For every action, retain the source evidence, the recommendation, the stated confidence or uncertainty, the approver, the application programming interface (API) call, the result, and the reversal. Then feed in contradictory evidence. The system should update its conclusion and preserve the earlier reasoning rather than overwrite the record.

Managed delivery does not remove this requirement. Exaforce MDR spans investigation and response, AirMDR uses human review for critical cases, and TENEX changes ownership by service path (Exaforce, AirMDR, TENEX). The contract must still say what may happen without the customer and what waits for approval. An agent's capability should never exceed the contract's authority.

The safest vendor is not the one claiming the most autonomy. It is the one that exposes uncertainty, constrains authority, and makes each action governable.

Test 3: Which Humans Are Still Required

AI changes the labor mix. It does not remove human accountability from any credible model reviewed here.

Software shifts labor to the buyer

A self-operated platform still needs detection engineering, integration ownership, quality review, incident response, and customer-specific judgment. Junior evidence gathering may shrink while senior review and platform administration grow.

Anton Chuvakin, a security advisor at Google, warns that AI SOC risks repeating the security orchestration, automation and response (SOAR) era, when a playbook promised to replace one analyst's workload and ended up needing two engineers to keep it running (post on X). That is one analyst's read rather than measured data, but it names the failure mode precisely. Labor does not vanish. It changes job title, and the new title usually costs more.

MDR supplies a human backstop

AirMDR says its analysts supervise the virtual analyst and handle critical or judgment-heavy cases (AirMDR). TENEX describes named analysts and forward-deployed engineers around its managed operation (TENEX). Exaforce MDR combines its Exabots with human experts (Exaforce MDR). 7AI describes humans on the loop who set intent and govern higher-consequence decisions (7AI).

Those are product facts about the operating design, not proof of a productivity level. Company-reported percentages on hours saved or work automated are not comparable without a baseline, a cohort, a definition of automated, and human-review time. Ask each vendor for those fields, then reproduce the result on your own cases.

Some decisions remain customer-owned

Only the customer knows whether isolating a production asset is safer than leaving it online, whether an executive's travel explains a login, or whether a regulator must be notified. A managed provider can recommend and execute within authority. It cannot absorb every business trade-off.

Model loaded cost per correctly resolved case, including software, provider fee, internal review, escalation, engineering, incident response, playbook maintenance, permission review, connector failure, and monthly service governance. That number reveals whether labor disappeared or moved. Track correction and escalation by seniority as well: if every uncertain case lands with the most expensive responder, an impressive automated-closure rate can coexist with weak economics.

Break the work into four buckets: evidence gathering, analyst review, platform engineering, and high-judgment response. Software should shrink the first and can swell the second and third during adoption. MDR moves more of the first three to the provider, while the customer keeps service governance and business decisions. The measure that matters is correctly resolved work at acceptable risk, not alerts touched.

Test 4: Integration, Data, and Time to Value

The cleverest agent is blind without the evidence needed to reconstruct the incident.

Existing-stack software

Dropzone works through the tools and data sources the buyer already uses (Dropzone documentation). That reduces rip-and-replace work, but each connector must expose the fields and actions a real investigation needs.

Full data layer and hyperscaler-native paths

Exaforce uses a unified real-time security data layer across its Exabots (Exaforce). TENEX runs natively on Google SecOps and Microsoft Sentinel and says it supports more than 300 connectors, a company-reported count (TENEX). AirMDR says it offers more than 240 integrations and custom integrations in two to four weeks, also first-party claims (AirMDR).

Broader context can improve investigation and enlarge onboarding scope at the same time. Data residency, retention, permissions, API limits, normalization, tenancy, and model access all become part of implementation.

Integration claims need labels. TENEX's 300-plus connectors and AirMDR's 240-plus integrations and custom-delivery timing establish advertised breadth, not completeness in your environment (TENEX, AirMDR). A managed service provider (MSP) focused reviewer who tested AirMDR's free tier reached the same conclusion from the other direction, finding real value in Tier 1 triage and evidence documentation while flagging hallucination risk, dependence on clean telemetry, and the need for human approval gates before scaling (video review). His closing advice was to validate vendor and customer reported numbers in your own environment.

Prove coverage on your telemetry

Select known historical incidents and live controlled alerts, then map every evidence source and response action. Measure missing data, incorrect enrichment, analyst corrections, time to a reliable conclusion, and behavior during connector failure. Keep a telemetry worksheet for each source: fields available, historical window, normal delay, peak delay, tenant boundary, write actions, API limits, and failure behavior.

Then export one complete investigation with raw evidence, enrichment, reasoning, approvals, and response history. If that record is only useful inside the vendor interface, the data layer creates switching cost as well.

Do not accept time to value as the date connectors turn green. It is the date analysts trust conclusions, governance approves the permissions, and the operation can recover from failure.

Test 5: Pricing Unit, Margin, and Channel Conflict

An MSSP can buy automation that quietly competes with its own service. The commercial model matters as much as the product.

Price the responsibility

Software may be priced by data, alerts, users, usage, or another private unit. Managed service should also price coverage, analysts, response, and the SLA. None of the reviewed official pages published normalized list pricing, so every quote needs identical workload assumptions: data volume, alerts, tenants, integrations, coverage hours, response rights, onboarding, support, and contract term. Keep the recurring price separate from implementation, storage, usage, premium connectors, and managed analysts.

Practitioner sentiment on pricing is blunt. Scott Ponte, who leads security operations at Robinhood, posted from Black Hat that he sees little real differentiation between AI SOC vendors beyond interface polish, and that the category is quietly reintroducing pay-per-alert, pay-as-you-ingest SIEM-style pricing (LinkedIn post). An independent researcher summarizing interviews with early adopters on r/cybersecurity landed in the same place from the opposite direction: vendors are not sure what to charge, and buyers cannot attach a quantifiable gain to what they are buying (r/cybersecurity thread). Both are sentiment rather than survey data, and both argue for pricing the workload you actually expect instead of the unit the vendor prefers.

Avoid agent-seat comparisons. Calculate total cost per correctly completed investigation after integration, data, internal labor, provider labor, and escalation. The move from input units to outcome units is the same one working through MSP AI pricing models more broadly.

Protect services margin

Dropzone says directly that MSSP partners keep services revenue (Dropzone). 7AI lets service providers build offerings on its foundation (7AI). Those are clearer enablement positions than a vendor whose managed service targets the same end customer.

Managed providers can still be the right partner when coverage is missing, and partnering is only one of an MSSP's buy, partner, build or compete options. Put brand, account protection, customer data, renewal ownership, response liability, termination, and direct-sales limits in writing. Public sources do not establish universal white-label terms for AirMDR, TENEX, or Exaforce, so do not assume them.

For an MSSP, model the end-customer fee less vendor cost, data, internal review, response, account management, and support. Then test control of the account. Who invoices, contacts, renews, upsells, and exports the operating record? Dropzone and 7AI answer those questions publicly for partners (Dropzone, 7AI).

Follow the automation margin

If software lowers analyst cost and the MSSP holds price, the MSSP captures the gain. If an MDR provider sells the outcome, the provider captures more of it. Buyers should seek lower risk and predictable service, not merely cheaper labor. Providers should move pricing toward outcomes before customers renegotiate the saving away.

Recalculate at each scale point. Software becomes more attractive as a working SOC spreads fixed cost across volume. MDR can stay better for a smaller team when it replaces genuine 24/7 staffing and specialist depth.

For related analysis, see AI SOC economics and the MSP tool stack.

Buyer Decision Tree

1. If you own analysts, response, and customer trust, buy software and retain the service.
2. If you own the customer but lack 24/7 coverage, use a co-managed or partner model with account protection.
3. If you need the complete operated outcome, buy MDR and define the response boundary.
4. If you expect operating maturity to change, choose a hybrid with a written migration path.

Before choosing a branch, complete a 30-day baseline: alert volume, handling time, analyst touches, reopened cases, response delay, known misses, coverage gaps, and loaded cost. Then run a 60-day shadow pilot on the same measures. Do not grant high-impact response until the evidence and rollback path are repeatable.

The contract should also cover transition. A customer moving from managed to self-operated delivery needs case history, playbooks, connectors, permissions, and training. A customer moving into MDR needs an explicit transfer of queue, escalation, and response duties. A hybrid option is worth paying for only if both paths are operationally and commercially real.

FAQ