Managed SOC

SOC as a ServiceAnalysts on your alerts. Response on your terms.

Our 24/7 security operations team monitors the security telemetry you already have, investigates what fires, escalates real cases to your named contacts and acts only within the authority you give us.

Active incident?Call +1 (587) 821-5997at any time.

Managed SOC at a glance

Who runs it
Our 24/7 security operations team, on the GuardsArm platform
What is watched
Endpoint, identity, cloud, network and agreed server logs
Who acts
Our team, only within the actions you pre-approve; the rest waits for you
Agreed during scoping
Coverage hours, notification timings, retention and where telemetry is stored

Who it serves

For organizations that need analysts on their alerts, not another console

Managed SOC suits teams that have security tools producing alerts but nobody to watch them at every hour, and that need a written record of what was seen and done.

Regulated organizations

Healthcare, financial services, public sector and SaaS providers that must show auditors, insurers or customers that security events are monitored and handled.

IT teams without a SOC

An internal IT team or managed service provider that runs the environment well, but cannot staff security monitoring and investigation alongside it.

Teams that need evidence

Organizations preparing for an audit or an insurance renewal that need monitoring records, case write-ups and regular reporting.

Probably not the right fit if:

Scope

What is monitored, and what is not

Clear boundaries matter more than long feature lists. This is the typical split; your agreement sets the exact source list.

Telemetry our team monitors

  • Endpoint telemetry from the detection and response agents on workstations and servers
  • Sign-ins, MFA events and directory changes from your identity provider
  • Cloud and productivity-suite audit logs: admin changes, mailbox rules, data access
  • Firewall, VPN and DNS logs for remote access, command and control and exfiltration
  • Critical server and application logs agreed during onboarding
  • The health of the log feeds themselves, so a silent source is noticed and raised

Not included unless agreed separately

  • Systems and sources that were not onboarded, including unmanaged personal devices
  • Patching, configuration changes and day-to-day IT administration
  • Full forensic investigation and recovery after a major incident (available as incident response)
  • Operational technology networks, unless OT monitoring is in scope
  • Physical security and fraud outside your digital systems

Usually you keep the security tools you already run. Where a gap matters, for example servers without endpoint agents or audit logging switched off, we say what to add and why.

Investigation and escalation

How an alert becomes a case your team can act on

A SOC is a chain: telemetry has to arrive, detections have to fire, a person has to look, and the right person on your side has to hear about it.
  1. Triage

    Every alert from your sources is reviewed by an analyst on our team: is it real, and what else happened around it? False positives are closed and the detection tuned so the same noise does not return.
  2. Investigation

    Real activity becomes a tracked case. The analyst scopes it across your other sources (which user, which device, how far it went) and attaches the evidence and reasoning to the case.
  3. Escalation to your named contacts

    Cases go to the people you named during onboarding, by severity and by the channel agreed for that severity: a phone call for the most serious, a written case for the rest.
  4. Response, only as authorized

    Our team takes only the actions you pre-approved, on the systems you pre-approved them for. Anything else is recommended with the evidence, and waits for a decision from someone with authority on your side.
  5. Close and report

    The case record says what happened, what was done, what was not done and what remains for you. Trends and gaps go into the regular report.

Who hears what, by severity

Response and notification timings are set in your service agreement, agreed during scoping. The pattern below is how cases are typically handled and what we need from you at each level.

Escalation by severity
SeverityTypical examplesWhat our team doesHow you are toldWhat we need from you
CriticalRansomware behaviour, confirmed admin account takeover, active data theftInvestigates at once; takes pre-approved containment actionsPhone call to the on-call contact, then the escalation list until someone answersA decision on any action that was not pre-approved, and someone with authority on the call
HighConfirmed compromise of one user or device, malware that executed, suspicious admin activityInvestigates and scopes; contains within pre-approved limitsPhone call and written caseConfirmation of business context (was this expected?) and follow-up actions
MediumSuspicious but contained activity, policy violations, blocked malware on one deviceInvestigates, documents and recommendsWritten caseRemediation within an agreed window, such as patching or reimaging
Low / informationalHygiene findings, misconfigurations, noise worth knowing aboutLogs and trends it; tunes detectionsIncluded in the regular reportNothing urgent; planned fixes

Response authority

You decide what our team may do on your behalf

Agreed before anything happens: which actions run immediately, which are pre-approved and which wait for a person on your side.

Read-only lookups change nothing in your environment, so analysts run them as soon as an alert needs context. Every lookup is recorded in the case.

Examples

  • Pulling the process tree from an endpoint
  • Checking a user’s recent sign-ins and MFA methods
  • Looking up a hash, IP address or domain in threat intelligence
  • Searching for the same indicator across your other sources

During onboarding you decide which containment actions our team may take without waiting for you, and on which systems. Many organizations allow laptop isolation and session revocation for standard users, but not for servers or executives.

Actions that change an endpoint need two GuardsArm people to approve them, and every action is logged in the case and reported to your contact.

Typical pre-approved actions

  • Isolating a workstation from the network
  • Revoking sessions and blocking sign-in for a compromised account
  • Removing a malicious mailbox forwarding rule

Some actions carry business risk: isolating a production server or disabling an executive account has a cost. For those, our team explains the evidence, recommends an action and waits for someone with authority on your side. Remediation such as patching, reimaging or firewall changes is carried out by your team or IT provider unless agreed otherwise.

Usually needs your decision

  • Isolating servers and production systems
  • Disabling privileged or executive accounts
  • Blocking traffic for a whole site
  • Anything that would interrupt operations or customers

What you provide

What we need from your side

Monitoring is a shared job. These are the things that make it work, and the things that slow onboarding down when they are missing.
  • Read access to the log sources in scope: identity provider, endpoint tooling, cloud tenants, firewalls and the servers agreed during scoping
  • Named escalation contacts, with after-hours numbers and a backup for each
  • A decision on which containment actions are pre-approved, and on which systems
  • Your change windows and planned maintenance, so expected changes are not escalated as attacks
  • Business context: which systems and accounts matter most, and who owns them
  • One onboarding owner on your side who can grant access and answer questions

Onboarding

From signed agreement to live monitoring

The order is indicative. How long each step takes depends mostly on how many sources you have and how quickly access can be granted on your side.
  1. Scoping and kickoff

    We agree the source list, coverage hours, named contacts, escalation paths, pre-approved actions, retention and where telemetry is stored. It is written down, not assumed.
  2. Connect sources

    Identity and endpoint telemetry first, because that is where most intrusions show up. Then cloud audit logs, firewalls, servers and anything specific to your environment.
  3. Verify and baseline

    Each source is checked for completeness and parsing before it counts as covered. Noisy but benign activity is tuned out with your input.
  4. Go live and review

    Monitoring starts at the agreed coverage hours. After the first reporting cycle we review what was found, what was noisy and which sources would close remaining gaps.

What you receive

The record your team, auditor and insurer can read

Monitoring nobody can see the output of is hard to justify. These are the artefacts the service produces.

Case records

One per real incident: timeline, evidence, reasoning, actions taken and what remains for you to do.

Regular report

What was detected, how cases were resolved, source health and the gaps we recommend closing, written for non-specialists.

Service reviews

A regular conversation, at a cadence set in your agreement, to review trends, tune detections and plan new sources.

Audit evidence

Monitoring and incident records you can hand to an auditor. Monitoring supports frameworks such as SOC 2, PCI DSS and HIPAA; it does not replace their other controls.

Illustrative example, not client data. A sample case record built on fictional names and reserved example addresses, to show the format you would receive.

Example escalation: suspected business email compromise

Case
EXAMPLE-0001 (sample data)
Severity
High
Organization
Example Co. (fictional)
Affected account
j.doe@example.com, finance team
Escalated to
Named on-call contact by phone, then a written case to the IT lead

What happened and what was done

  1. Signal: Successful sign-in with MFA approved, from a device and country this user has never used (source 203.0.113.45).

  2. Correlation: A new mailbox rule forwards messages containing “invoice” or “payment” to an external address. The two events are linked into one alert.

  3. Investigation: Analyst reviews recent sign-ins, the MFA method used and the forwarding address. The pattern matches business email compromise. No other accounts show the same source.

  4. Actions taken (pre-approved): Sessions revoked, sign-in blocked and the forwarding rule removed, as authorized during onboarding for standard user accounts.

What is needed from you

  • Reset the password with the user, in person or by a verified call
  • Ask the finance team to check for payment or bank-detail changes since the sign-in
  • Decide whether to replace MFA push approval with number matching
Real case records follow the same structure. What our team may do on its own, and how you are told, depends on what you authorize during onboarding.

People, data and software

Where the monitoring happens, and where your data lives

Three different things that are easy to blur. Only the first is the same for every managed SOC customer.
Managed SOC

Canadian-operated monitoring

The analysts who triage, investigate and escalate your cases are our security operations team.
Managed SOC

Where your telemetry is stored

Storage location, who can access it and how long it is kept vary by customer. They are agreed during scoping and set out in your service agreement, so ask about them in the walkthrough.
Separate offer

Platform on your infrastructure

If your data must stay on infrastructure you control, the GuardsArm platform runs on your own servers or cloud tenancy and your team operates it.
See the SIEM on your infrastructure

Pricing

What affects a quote

We scope against your environment before quoting. These four things move the price most.

Sources and endpoints

How many log sources, endpoints, cloud tenants and servers are in scope, and whether any need a custom parser.

Hours of coverage

Business hours, extended hours or around the clock. Agreed during scoping.

Response authority

Notify-only, or pre-approved containment on some or all systems, and how many escalation contacts and paths there are.

Retention

How long telemetry and case records must be kept, usually set by your regulator, auditor or insurer.

A walkthrough covers your sources, contacts and response authority, so the quote that follows is based on your environment.

Interactive tool

SOC Coverage Mapper: what could your SOC actually see?

A SOC can only detect what it can see. Tick the log sources you collect today to see which stages of an attack (the MITRE ATT&CK tactics) would leave a trace, where your blind spots are, and which source to add next.
Log sources you have today

1. Tick the log sources you collect today

Count a source only if its logs are kept and someone could search them.

2. Your visibility across the MITRE ATT&CK tactics

0%No sources ticked yet

Tick the sources on the left, or start with a preset. Not sure what you collect? Most organizations start with endpoint and identity logs.

Not sure? Ask an analyst
  • Initial AccessBlind spot
  • ExecutionBlind spot
  • PersistenceBlind spot
  • Privilege EscalationBlind spot
  • Defense EvasionBlind spot
  • Credential AccessBlind spot
  • DiscoveryBlind spot
  • Lateral MovementBlind spot
  • CollectionBlind spot
  • Command and ControlBlind spot
  • ExfiltrationBlind spot
  • ImpactBlind spot

Indicative mapping. Visibility means the activity is recorded; detection also needs rules, tuning and someone watching.

Buyer’s checklist

Questions to ask any SOC provider

Including us. The answers tell you more than a feature list.

Security logs contain usernames, IP addresses and sometimes message subjects. Ask for the country of storage, of processing and of the analysts who can see it. Our monitoring team is in Canada; where your telemetry is stored is agreed during scoping and written into your agreement.

A notification at 3 a.m. that nobody reads until 8 a.m. is not response. Ask which actions the provider can take without waking you, how they are approved and how they are reversed.

A source that is connected but not parsed gives a false sense of security. Ask how gaps in log flow are detected and reported. Ours are: a source that goes quiet is raised with you as a finding.

Ask for an example. A good one shows the timeline, the evidence, the reasoning, the actions taken and what is needed from you. There is an illustrative one on this page.

Patching, firewall changes, full forensic investigations and recovery work are often separate. Knowing the boundary before an incident avoids surprises during one.

Watch

Managed security operations in under a minute

Too Many Security Alerts, Not Enough People?

Thousands of alerts a day and nobody has time to read them all. How automated triage surfaces the incidents that need a person.

No Security Team Overnight?

Most organizations cannot staff a security team around the clock. Monitoring, investigation and response, 24/7, so the morning starts with answers.

4 Questions to Ask Any Managed SOC or MDR Provider Before You Sign

Comparing managed security providers? Ask each one where the operations centre is, whether analysts can contain a threat at 2 a.m., whether you see the same console, and whether there is a minimum size.

SOC as a Service: frequently asked questions

What is SOC as a Service?

SOC as a Service gives you a security operations center without building one. Our analysts collect and correlate your security telemetry, investigate alerts during the coverage hours you choose, escalate real cases to your named contacts and contain threats only within the actions you authorize. You get the monitoring, detection engineering and response capability of an in-house SOC as a managed service.

How is SOC as a Service different from MDR?

The terms overlap. SOC as a Service usually covers broad log monitoring across endpoints, identity, cloud, network and applications, plus reporting for audits. MDR focuses on detection and active response, often centred on endpoint telemetry. Many organizations need both, and we scope the mix to your environment.

What data sources do you monitor?

Typical sources include endpoint detection and response agents, identity providers such as Microsoft Entra ID, firewalls, VPNs, cloud platforms, email security and critical servers. Identity and endpoint telemetry come first because that is where most intrusions show up. We agree the source list during onboarding.

Where is the SOC located?

Our security operations team is in Canada and supports organizations across Canada and the United States. Where your telemetry is stored, and for how long, is agreed during scoping and set out in your service agreement.

How is SOC as a Service priced?

Four things move the price most: the number of log sources and endpoints in scope, the hours of coverage, the response authority you give us, and how long data must be retained. Request a SOC walkthrough and we will scope it against your environment before quoting.

Can the SOC support our compliance audits?

Yes. Continuous monitoring, incident records and monthly reporting produce evidence that auditors ask for under frameworks such as SOC 2, HIPAA and PCI DSS. Monitoring supports compliance; it does not replace the other controls those frameworks require.

Do we need to replace our existing security tools?

Usually not. The GuardsArm platform ingests telemetry from the EDR, identity, email, firewall and cloud tools you already run. Where a gap matters, for example servers without EDR or Microsoft 365 audit logging switched off, we recommend what to add and why.

Can the SOC take action, or does it only alert us?

Both, by agreement. During onboarding you decide which containment actions the SOC may take on its own, such as isolating a laptop or revoking a compromised session. Actions that change an endpoint require two GuardsArm people to approve them, and anything with business risk waits for your named contact.

What happens if a log source stops sending data?

Log flow is itself monitored. A source that goes quiet is treated as a finding and raised with you, because a silent firewall or a disabled audit log can be a sign of an attacker as well as a configuration problem.

How long does onboarding take?

It depends mainly on the number of sources and how quickly access can be granted on your side. Identity and endpoint sources are connected first, so the most valuable coverage starts early while the rest is added.

See how managed SOC would work for your environment

In a walkthrough we go through your log sources, escalation contacts and response authority, show you what a case record looks like, and explain what would shape the quote.