Detection is the easy part now. The hard part is the 40,000 log entries a day that arrive behind it, and the judgment call about which twenty of them are worth interrupting your Tuesday for. AllTech runs a security operations center that reads them around the clock, including the 2 a.m. ones and the ones that turn out to be nothing.
Most businesses that get breached had the product that would have caught it. It was installed, it was licensed, and it fired an alert. The alert went to a dashboard nobody had logged into that week, or to a distribution list that everyone had filtered into a folder six months earlier.
That's the usual failure: the product was there, and nobody read what it said. Security tools are built to be sensitive, because a tool that stays quiet gets blamed. So they flag the new local account, the sign-in from an unusual country, the remote access tool that just installed itself as a service. All three are routine most of the time, and all three are also exactly what an attacker does. Nothing in the alert tells you which one you're looking at.
Sorting that out takes a person who knows what normal looks like on your network, has the context to check it against the rest of the environment, and is awake at the time it happens. A security operations center provides that person. Without one, you're mostly paying for licenses.
A SOC is only as good as what it can see. Ours pulls from every layer of the environment we manage, well past the endpoints:
The Windows security log on every workstation and server, covering account creation, group membership changes, service installation, and logon activity. This layer catches an attacker who already has valid credentials and isn’t running anything a scanner would flag.
Behavioral detections and malware mitigations from the endpoint agents, escalated into the same queue as everything else rather than sitting in a separate console.
Where the login came from, whether the location fits the account’s history, and whether the pattern matches credential stuffing or a legitimate trip.
Microsoft’s own identity risk signals, such as anonymous IP address use, unfamiliar sign-in properties, and anomalous token activity. We pull them in and triage them instead of leaving them in a portal.
Mailbox rule changes, role assignments, and permission grants: the post-compromise activity that never generates a failed login.
Perimeter activity correlated against what the endpoints and cloud accounts were doing at the same time.
Correlation rules that fire on a sequence of events rather than any single one, catching the patterns that look ordinary in isolation.
Last month that added up to more than 1,200 endpoint agents, 44 firewalls, and more than 800 Microsoft 365 accounts under continuous monitoring, feeding a single queue reviewed 24 hours a day, 365 days a year.
Most security marketing quotes the big number and stops, but it's the least interesting one. Here is the whole funnel from a single month across the environments we monitor:
logs and events triaged
Roughly 40,000 a day, collected across every monitored environment and reviewed in a single queue.
incidents raised
About two a day. Roughly 19,000 log entries behind every incident that reached a human as a real question.
investigated / tuned out
Thirty-nine worked to closure. Twenty-four closed as expected activity and tuned so the same benign pattern wouldn’t raise a second one.
still open at month end
Every incident raised in the period was closed within the period.
Incidents landed on 23 of the 31 days in the period, and nine of them arrived on a weekend. The longest completely quiet stretch was three days. This can't work as a business-hours service.
Figures from AllTech SOC monitoring, June 1 – July 1, 2026, aggregated across all monitored environments.
Twenty-four of last month's sixty-three incidents, thirty-eight percent of the queue, were suppressed. Each one was reviewed, matched against known activity in that environment, closed, and tuned so the same benign pattern wouldn't raise a second one.
The clearest example is one alert type, a new local user account created on a Windows machine. It fired eleven times last month, on eleven different computers. Ten were technicians imaging hardware, setting up a kiosk, or standing up a service account, and were closed as expected. One wasn't, and was worked as a real investigation.
If you had bought that detection and pointed it at your own inbox, you would have received eleven identical alerts, ignored the first four, and been trained by the fifth to ignore the eleventh. That's how the alert that mattered gets missed. It's there, just buried in the volume.
Deciding which of the eleven was different is the job. It requires knowing what that environment's technicians were doing that week, and it cannot be done by a rule.
Anonymized, from last month:
A managed machine logged a new service installation for a commercial remote-support application. It’s legitimate, widely used software, and also one of the most common tools in active intrusions. Attackers install it because it looks like IT. We escalated it, traced it back to who installed it and why, and closed it.
Two separate endpoints, two installer files masquerading as PDF utilities, both stopped by the agent before execution. The tool did its job. The SOC’s job was confirming nothing else on those machines had changed first.
The attachment was blocked. The investigation was about the four related events behind it and whether anyone else had received the same message.
Two related detections for behavior consistent with an attempt to bypass endpoint monitoring. This kind of activity has no file to scan and never appears in an antivirus report.
A user was added to a security group on a domain controller outside a change window. Across 1,220,546 log entries that month, this is the one that got a phone call rather than a ticket.
One account produced successful foreign logins across most of the month, including a single day with over 1,500 associated events. We investigated, escalated, and closed it. A tool on its own would have alerted on the first login and then produced 1,500 more. A SOC works out what it is on day one and handles the rest without the noise.
All identifying detail removed.
Broken down by origin, last month's 63 incidents split like this:
Microsoft 365 sign-ins, risk detections, role changes
Account creation, group changes, service installs
The layer most businesses think of as “security”
Just five of the 63 came from antivirus or EDR firing on something malicious. That is the layer most businesses think of as “security,” and it accounted for under eight percent of what actually needed looking at.
The majority started with a valid credential being used in a way that didn't fit: a login from the wrong country, an account added to a group it shouldn't be in, a new local user on a machine at midnight. Those involved no malware, so there was nothing for antivirus to catch.
This is the argument for monitoring the whole environment rather than buying one product for the part of it that has a good marketing budget.
Every one of those 63 incidents happened. You need detection and response because prevention is never complete, but it’s the second layer and doesn’t replace the first. If your endpoints are unpatched and your accounts don’t have MFA, fix that before you buy monitoring.
Twenty-four decisions last month were “this is expected activity in this environment.” We think all twenty-four were right. A SOC trades a small risk of tuning out something real against the certainty that an untriaged alert stream gets ignored entirely. Every suppression is logged and reviewable.
Every incident closed last month, but some of them closed because someone at the client confirmed what a login or an account change was. A SOC with no one to escalate to stalls at the escalation step.
That is the total across everything we monitor, not one company’s month. A typical monitored client saw two or three. If you are expecting a dramatic weekly report, this is the wrong service. Most months are quiet. You are paying for the coverage on the month that isn’t.
Probably not worth it if: you have a staffed internal security team already, or you're small enough that your entire environment is a handful of laptops and a Microsoft 365 tenant with MFA enforced. We'll tell you if that's the case.
We inventory what you have, what’s reporting, and what isn’t. Most environments have at least one security product that stopped sending data months ago and nobody noticed.
Agents go on endpoints, cloud connectors go into Microsoft 365, firewall logs get pointed at the collector. Then we spend the first few weeks learning what normal looks like in your environment, which is what makes suppression possible later.
Alerts land in the queue 24/7. Analysts triage, investigate, and either close them or escalate. You hear from us when something needs you, not when something fires.
Real incidents come to you with what happened, what we’ve already done, and what you need to decide. Monthly reporting shows the full picture, including everything we closed without calling.
We operate the monitoring, triage, and escalation for your environment, on a platform built for multi-tenant security operations. What matters practically is that the escalation path ends with the people who already manage your network — not with a ticket queue that has to ask you what a domain controller is.
Alerts are triaged around the clock. Escalation speed depends on severity — a privileged group change on a domain controller gets a phone call; a suppressed duplicate gets logged. Last month every incident raised in the period was closed within the period.
Usually not. The SOC ingests from what you have where the integration exists. The assessment tells you where there’s a real gap versus where there’s just a console nobody opens.
It gets triaged at 3 a.m. Whether you get woken up depends on what it is, and we agree on that threshold with you during onboarding rather than guessing.
Ask them who reads the alerts, when, and what the escalation path is at midnight on a Saturday. It’s a fair question and it has a specific answer. Nine of last month’s incidents arrived on a weekend.
The opposite is the point. Of 1.2 million log entries last month, 63 became incidents and 39 needed any client involvement at all.
The agents that generate a share of what the SOC reads. Five of last month’s 63 incidents came from this layer.
Most cloud identity incidents start with a message. Filtering reduces what the SOC has to catch later.
The network layer of the same picture — what a device did after it was compromised.
Half of last month’s incidents originated in cloud identity. Conditional access and MFA policy are where most of them get prevented instead of detected.
What we deliver remotely vs. what needs someone on-site, in one place.
A ClickFix-style attack on a Cache Valley business skipped the disk entirely: a memory-only PowerShell payload that dropped a signed-runtime backdoor.
A high-severity alert at a small-town Utah police department began with a pasted command. How it was detected, investigated, and closed in 15 minutes.
A backup you have never restored is a guess. Here is how to test a restore, what to check and how often, and why ransomware makes the test matter.
We'll inventory your security tools, check which ones are still reporting and to whom, and show you what a month of your own alert data looks like once someone sorts it. Most businesses find at least one product they're paying for that stopped sending data and never said so. You get plain findings and no sales pressure.
Trusted by dozens of businesses
AllTech