SOC as a Service
Managed cybersecurity for SMBs.
Your company does not need to build a security team to be protected. We install a lightweight agent on every computer and server, connect your cloud services, and our analysts watch, investigate and contain threats with AI-assisted triage. The same team that attacks companies for a living tells you whether you would detect it.
How it works
Collect, detect, respond. Then prove it.
1
Collect
A lightweight agent on every computer and server, plus your cloud services. Nothing to buy or rack.
2
Detect
Rules mapped to MITRE ATT&CK and Sigma, plus behavioural baselines for every device and user. Alerts in seconds.
3
Triage with AI
AI groups, enriches and prioritizes every alert. An analyst decides what is real.
4
Respond
Block a malicious IP or domain on the device, isolate a compromised computer, disable a session. Reversible and logged.
5
Prove
Our offensive team runs the techniques the SOC says it detects. You get proof, not a promise.
6
Report
A one-page monthly report for management, the technical annex for IT, and evidence for your auditor.
What we watch
- Windows, macOS and Linux computers and servers
- Microsoft 365 and Google Workspace
- Sign-ins, identities and privileged accounts
- Cloud logs and SaaS activity
- Software inventory and known vulnerabilities
- File integrity on critical systems
What we detect
- Ransomware and malware behaviour
- Compromised accounts and impossible travel
- Intrusions that start with phishing
- Lateral movement inside the network
- Data exfiltration
- New admin accounts and suspicious persistence
Why it is different
The team that attacks is the team that watches.
Most SOCs tell you they would detect an attack. We run the attack. Every finding from our pentests becomes a detection rule, and every rule is tested by our offensive team. If a technique gets through, we fix the detection and show you the before and after.
pentest> reused credentials on the VPN
-> access to the internal network
rule> VPN sign-in from a new ASN
+ service account outside hours
test> technique re-run by the offensive
team: ALERT in 11 s, contained
status> detected and provenPackages
Sized to your company.
The technology is the same in every package. What changes is how many hours a human is watching, how fast we respond and how deep the compliance goes. Quotes after a 30-minute call.
| Small1–50 employees | Mid-size50–250 employees | Enterprise250+ or regulated | |
|---|---|---|---|
| For | Companies with no security team, often no in-house IT | Companies with IT but no security specialists, or that need audit evidence | Regulated entities and critical infrastructure |
| Devices and cloud services | Up to 25 devices, 2 cloud services | Up to 100 devices, 5 cloud services | 250+ devices, cloud sources as needed |
| Human monitoring | Mon–Fri 8:00–18:00, on-call for critical incidents | Mon–Sat 7:00–22:00, on-call 24/7 | 24/7/365, analyst on shift |
| Automatic containment | 24/7 for known threats | 24/7, plus manual containment by the analyst | 24/7, with playbooks agreed with you |
| Response time, critical | 1 hour | 30 minutes | 15 minutes |
| Log retention | 90 days | 180 days | 180 days, extended archive on request |
| Threat hunting | Monthly inventory and vulnerability review | Quarterly | Monthly |
| Detection validation by our offensive team | Once a year | Twice a year | Every quarter, purple team |
| Incident response included | Triage and containment | 8 hours a year | 40 hours a year, forensic report for major incidents |
| Compliance and reporting | Monthly executive report | ISO 27001 / SOC 2 / NIST CSF evidence, quarterly review | Regulator mapping (SUGEF, PCI DSS), board presentation |
| Channel | Email and on-call WhatsApp | Dedicated Teams or Slack channel | Lead analyst assigned |
Protected in four weeks
The SLA starts in week 4, not at signature, because a SOC that has not learned your normal only produces noise.
Week 0
Contract, data-processing agreement, escalation contacts and containment authorization
Week 1
Agents deployed and cloud services connected
Weeks 1–2
Baseline: the platform learns what normal looks like for every device and user
Weeks 2–3
Tuning to remove noise and agree what is contained automatically
Week 4
SLA starts and you receive your first security posture report
What it does not include
- Deep remediation such as patching or network redesign (we recommend it, or deliver it as Consulting)
- Managing your perimeter firewalls or network equipment
- Data recovery or ransom negotiation
- Devices without the agent: we cannot watch what we cannot see
Your data
Monitoring data is handled under a data-processing agreement and the data-protection law that applies to you, with our technology providers listed as sub-processors in the contract. AI analysis runs with zero data retention.
Talk to us about the SOC