Three ways to work with GuardsArm. The real differences are who runs the tooling, who may act on an alert, and where your data lives. Terms that vary by customer are agreed during scoping.
The short version: with managed SOC and MDR our team does the watching; with the self-hosted SIEM your team does, on your own infrastructure.
Managed SOC, MDR and self-hosted SIEM compared
Question
Managed SOCWe monitor and escalate
MDRWe detect and contain
Self-hosted SIEMYou run the GuardsArm platform
Who operates the tooling
Our Canadian security operations team runs the monitoring on the GuardsArm platform, alongside the security tools you already have.
Our team runs detection and response on the GuardsArm platform, using the endpoint, identity and cloud tools you already have.
Your security team, or your managed service provider, runs the platform day to day. GuardsArm supplies the software.
Telemetry covered
Broad: endpoint, identity, cloud and productivity-suite audit logs, firewall, VPN and DNS, agreed servers and applications, plus the health of each feed.
Focused on where attacks show up first: endpoint, identity and cloud audit logs. Other sources by agreement.
Whatever you connect: roughly seventy-five decoded source formats across hosts, network gear, cloud, identity, containers and mail, plus custom parsers.
Who investigates alerts
Our analysts triage every alert, investigate and open a case with the evidence.
Our analysts confirm whether an alert is real, scope it and record the evidence.
Your analysts. The platform decodes, correlates and categorises events for them.
Who authorizes and performs response actions
You authorize. Read-only lookups run at once; our team takes containment only within the actions you pre-approve; anything else waits for your named contact. Your team or IT provider does remediation.
You authorize, as for managed SOC. Pre-approved containment (isolating a device, revoking a session, removing a mailbox rule) is the core of the service.
Your team decides and acts. Automated responses run only as your team configures them.
Data location and access
Monitoring is operated from Canada. Where telemetry is stored and who can access it: agreed during scoping and set out in your agreement.
Monitoring is operated from Canada. Where telemetry is stored and who can access it: agreed during scoping and set out in your agreement.
On infrastructure you control: your data centre, private cloud or your own cloud tenancy. Your team controls access.
Retention
Agreed during scoping, usually set by your regulator, auditor or insurer.
Agreed during scoping.
You set retention policies on your own storage.
What drives the quote
Number of log sources and endpoints, hours of coverage, response authority and retention.
Number of endpoints and sources in scope, the response options you choose and hours of coverage.
Your environment and how you intend to operate the platform. Licensing is not metered per gigabyte.
Best fit
Organizations that want a team watching broad telemetry, escalating real cases and producing audit evidence, without building a SOC.
Organizations whose priority is stopping attacks on endpoints and accounts early, with containment agreed in advance.
Organizations with their own security staff or MSP, that need security data to stay on infrastructure they control.
Our Canadian security operations team runs the monitoring on the GuardsArm platform, alongside the security tools you already have.
Telemetry covered
Broad: endpoint, identity, cloud and productivity-suite audit logs, firewall, VPN and DNS, agreed servers and applications, plus the health of each feed.
Who investigates alerts
Our analysts triage every alert, investigate and open a case with the evidence.
Who authorizes and performs response actions
You authorize. Read-only lookups run at once; our team takes containment only within the actions you pre-approve; anything else waits for your named contact. Your team or IT provider does remediation.
Data location and access
Monitoring is operated from Canada. Where telemetry is stored and who can access it: agreed during scoping and set out in your agreement.
Retention
Agreed during scoping, usually set by your regulator, auditor or insurer.
What drives the quote
Number of log sources and endpoints, hours of coverage, response authority and retention.
Best fit
Organizations that want a team watching broad telemetry, escalating real cases and producing audit evidence, without building a SOC.
Our team runs detection and response on the GuardsArm platform, using the endpoint, identity and cloud tools you already have.
Telemetry covered
Focused on where attacks show up first: endpoint, identity and cloud audit logs. Other sources by agreement.
Who investigates alerts
Our analysts confirm whether an alert is real, scope it and record the evidence.
Who authorizes and performs response actions
You authorize, as for managed SOC. Pre-approved containment (isolating a device, revoking a session, removing a mailbox rule) is the core of the service.
Data location and access
Monitoring is operated from Canada. Where telemetry is stored and who can access it: agreed during scoping and set out in your agreement.
Retention
Agreed during scoping.
What drives the quote
Number of endpoints and sources in scope, the response options you choose and hours of coverage.
Best fit
Organizations whose priority is stopping attacks on endpoints and accounts early, with containment agreed in advance.
Your security team, or your managed service provider, runs the platform day to day. GuardsArm supplies the software.
Telemetry covered
Whatever you connect: roughly seventy-five decoded source formats across hosts, network gear, cloud, identity, containers and mail, plus custom parsers.
Who investigates alerts
Your analysts. The platform decodes, correlates and categorises events for them.
Who authorizes and performs response actions
Your team decides and acts. Automated responses run only as your team configures them.
Data location and access
On infrastructure you control: your data centre, private cloud or your own cloud tenancy. Your team controls access.
Retention
You set retention policies on your own storage.
What drives the quote
Your environment and how you intend to operate the platform. Licensing is not metered per gigabyte.
Best fit
Organizations with their own security staff or MSP, that need security data to stay on infrastructure they control.
No response-time, detection-time or uptime figure applies across these offers. Timings for managed SOC and MDR are agreed during scoping and set out in your service agreement.
Where your data lives
Canadian-operated is not the same as Canadian-hosted
Managed SOC and MDR are operated by our Canadian security operations team: the people who see and act on your alerts are in Canada. Where the telemetry itself is stored, and for how long, varies by customer and is agreed during scoping.
The self-hosted SIEM is software that runs on your own infrastructure, wherever you host it. Your data stays there, and your team controls who can see it.
Most buyers can tell after one conversation. A SOC walkthrough covers your sources, contacts and response authority; if the self-hosted platform suits you better, we will say so.