Security Operations

Managed SIEM monitoring Act on real threats, not noise

Security information and event management (SIEM) software centralizes your security logs and raises alerts. U.S. agencies found signs of state-sponsored threat actors inside some critical infrastructure networks for at least five years. The software runs continuously, and our security team reviews its alerts and escalates high-severity events to you.

Who it is for
Critical infrastructure and growing businesses that need log review
How it runs
Recurring monthly, with high-severity events escalated when found
What you get
An alert review report, escalation record and log source list

What a SIEM does with your logs

The National Institute of Standards and Technology (NIST) describes a SIEM tool as one that gathers security data from your systems and presents it "as actionable information via a single interface." That means one view of alerts instead of a separate log on every system.

A log is "a record of the events occurring within an organization's systems and networks," in NIST's definition. Log management covers the whole life of those records, which NIST lists as "generating, transmitting, storing, analyzing, and disposing of log data." A SIEM does the collecting and the analysis.

Logs also matter after an incident. Event logging guidance from the Cybersecurity and Infrastructure Security Agency (CISA), the Australian Cyber Security Centre and other agencies says logs help responders see how far a compromise reached.

Managed SIEM, MDR and SOC as a service compared

The difference is who looks at an alert and what they may do about it. A SIEM is software. Managed SIEM adds a team that runs the software and reviews its alerts. MDR, short for managed detection and response, adds response to detection, as the name says.

SOC stands for security operations center. Before you buy SOC as a service, ask who staffs it, at which hours, and what it is allowed to do on your systems.

Our Managed Logging and SIEM Monitoring service is managed SIEM. Advanced SOC and MDR Monitoring is a separate service, listed below with what it covers.

SIEM monitoring and the services you can add

The first is our managed SIEM service. The other three are separate services.

  • Managed Logging and SIEM MonitoringAlerts from your systems in one place, reviewed by our security team.
  • Advanced SOC and MDR MonitoringRound-the-clock monitoring for your computers and systems, through our security operations.
  • Logging Governance and Retention ManagementClear rules for which system records you keep and for how long, with proof they were reviewed.
  • Incident Response SupportHands-on help to contain an incident and coordinate the recovery.

How our SIEM monitoring runs

  1. 01 ScopeYou approve which systems send logs to the SIEM.
  2. 02 ConnectWe connect those systems, using the access you provide.
  3. 03 CollectThe SIEM gathers the logs and raises alerts continuously.
  4. 04 ReviewOur security team reviews the alerts and the events behind them.
  5. 05 EscalateWe escalate high-severity events to the contacts you name and record each one.
  6. 06 ReportEach month you receive a report on the alerts we reviewed.

Your SIEM reports and escalation records

Each month you get records you can file and show a reviewer.

  • 01Log source listWhich systems send logs to the SIEM, as you approved them.
  • 02Alert review reportThe alerts our security team reviewed during the month.
  • 03Escalation recordEach high-severity event we escalated to you.
  • 04SIEM dashboard exportA copy of the SIEM dashboard for your own files.

What HIPAA, FTC, NERC CIP and CIS say about logs

Each of these rules and frameworks asks for logging or for reviews of activity. Each name links to our program for it.

  • HIPAA Security Rule, audit controlsUnder the Health Insurance Portability and Accountability Act (HIPAA), audit controls must record and examine activity in systems holding electronic patient data (45 CFR 164.312(b)). Regular review of activity records, such as audit logs, is also required (45 CFR 164.308(a)(1)(ii)(D)).
  • FTC Safeguards Rule, user activity logsThe Federal Trade Commission (FTC) rule covers non-bank financial firms, including tax preparers. They must have controls designed to "monitor and log the activity of authorized users and detect unauthorized access" to customer information (16 CFR 314.4(c)(8)). The exemption for firms holding customer information on fewer than 5,000 consumers does not lift this clause (314.6).
  • NERC CIP-007-6, Requirement R4Requirement R4 of this North American Electric Reliability Corporation (NERC) Critical Infrastructure Protection (CIP) standard applies only to registered entities' high and medium impact Bulk Electric System (BES) Cyber Systems. It requires logs of logins, failed access and login attempts, and detected malicious code. For some systems, it also requires alerts and a review of a summary or selection of logged events at least every 15 calendar days (CIP-007-6).
  • CIS Controls v8.1, Control 8The Center for Internet Security (CIS) sets priorities with three Implementation Groups. In all three, it asks for a written audit log process and logging turned on across your assets (Safeguards 8.1 and 8.2). Groups 2 and 3 add central collection, usually in a SIEM, and log reviews at least weekly (8.9 and 8.11).
  • NIST Cybersecurity Framework (CSF) 2.0Its outcomes include log records made available for continuous monitoring (PR.PS-04), and monitoring of networks and of personnel activity and technology use (DE.CM-01 and DE.CM-03).

Which logs to collect and how long to keep them

Start with the log sources covered in the 2025 priority logs guidance from CISA and the Australian Cyber Security Centre: endpoint detection and response (EDR) tools, the operating systems on your computers and servers, and cloud and network devices.

For systems that hold sensitive data, CIS Safeguard 8.5 asks Implementation Groups 2 and 3 for detailed logs, with fields such as the event source, date, username, timestamp, and source and destination addresses.

Then decide how long to keep the logs. The event logging guidance warns that default retention periods are often too short to support an incident investigation. CIS Safeguard 8.10 sets a minimum of 90 days for Implementation Groups 2 and 3. NERC CIP-007 asks for at least the last 90 consecutive calendar days, where technically feasible, for high impact systems and for medium impact systems at control centers. HIPAA's audit control and activity review sections set no period.

Within those rules, the period is your decision, and so is the storage it needs. Logging Governance and Retention Management puts your retention rules in writing, with proof they were reviewed.

What we do with logs and alerts, What stays with you

The 2025 SIEM guidance from CISA and the Australian Cyber Security Centre says the division of responsibility for detecting and responding should be clear.

CyberBlip

  • Connect the log sources you approve
  • Review alerts and the security events behind them
  • Escalate high-severity events to the people you name
  • Preserve the evidence from alerts and escalations
  • With Advanced SOC and MDR Monitoring: coordinate setup, manage escalations, explain findings and support your response

You

  • Approve which systems send logs
  • Provide the access needed to connect them
  • Approve the storage and retention costs
  • Name your escalation contacts
  • Decide who can authorize a response
  • Make the business and risk decisions

What SIEM monitoring will not do

A SIEM only sees the logs it receives, and an alert only helps when someone acts on it.

  • A SIEM is not a tool you install and forget. The 2025 SIEM guidance says it needs skilled people and ongoing tuning, and that a poorly tuned SIEM can swamp a team with false alerts.
  • Escalation is not containment. Containing an incident is part of Incident Response Support, a separate service.
  • Advanced SOC and MDR Monitoring covers only the systems in its agreed scope, and only while that service is active.
  • Our NERC CIP work is IT-scoped. It does not take over a utility's own compliance for its grid systems.
  • Our reports are records, not an auditor's opinion. Decisions about breach notices belong to your counsel. Our data breach readiness program covers the planning before a breach.

Questions about SIEM monitoring and MDR

Do you monitor our systems 24/7?

The SIEM software does: it collects logs and raises alerts continuously. Our security team reviews those alerts and escalates high-severity events to the contacts you name. Round-the-clock monitoring for your computers and systems, through our security operations, is a separate service: Advanced SOC and MDR Monitoring.

We already have antivirus or EDR. Why add a SIEM?

Antivirus and EDR tools watch your computers. A SIEM puts their alerts next to the logs from your other systems, so related events can be seen together. NIST's Cybersecurity Framework lists correlating information from multiple sources as part of analyzing suspicious events (DE.AE-03).

Is a SIEM enough for HIPAA, the FTC rule or NERC CIP?

Not on its own. A SIEM supports the logging and review clauses, but each rule asks for more, such as the risk analysis HIPAA requires. Our compliance programs for regulated industries are built around those wider rules, and our alert review reports and escalation records give a reviewer evidence that monitoring took place.

Who pays for storing our logs?

You approve the storage and retention costs. The 2025 SIEM guidance notes that most SIEM pricing depends on how much data the SIEM takes in. So the systems you connect drive the cost, and so does how long you keep their logs.

What happens when you find something serious?

We escalate it to the contacts you named and record the escalation. What happens next should be agreed before that moment. NIST's framework expects incidents to be declared when events meet criteria defined in advance (DE.AE-08), and Incident Response Readiness gives you a response plan and practice drills, so everyone knows their role.

Sources

Show all 15 sourcesHide sources
  1. PRC State-Sponsored Actors Compromise and Maintain Persistent Access to U.S. Critical Infrastructure (AA24-038A) CISA, NSA and FBI, 2024-02-07
  2. Glossary: security information and event management (SIEM) tool (from SP 800-128) NIST
  3. Glossary: log (from SP 800-92) NIST
  4. Glossary: log management (from SP 800-92) NIST
  5. The NIST Cybersecurity Framework (CSF) 2.0, NIST CSWP 29 NIST, 2024-02-26
  6. Alert announcing Best Practices for Event Logging and Threat Detection CISA, 2024-08-21
  7. Best practices for event logging and threat detection Australian Signals Directorate, Australian Cyber Security Centre, 2024-08-22
  8. Guidance for SIEM and SOAR Implementation CISA
  9. Implementing SIEM and SOAR platforms: Executive guidance Australian Signals Directorate, Australian Cyber Security Centre, 2025-05-27
  10. Priority logs for SIEM ingestion: Practitioner guidance Australian Signals Directorate's Australian Cyber Security Centre, with CISA and partners, 2025-05-27
  11. CIS Controls Assessment Specification for Controls v8.1, Control 8: Audit Log Management Center for Internet Security
  12. 16 CFR Part 314, Standards for Safeguarding Customer Information (FTC Safeguards Rule) eCFR, 2026-11-13
  13. Technical safeguards, 45 CFR 164.312 eCFR, 2026-11-13
  14. 45 CFR 164.308, Administrative safeguards (HIPAA Security Rule) eCFR, 2026-11-13
  15. CIP-007-6, Cyber Security: Systems Security Management NERC, 2016-01-21

Next step

Find out where you stand

Tell us how we can best support you.

Icons: Tabler Icons, MIT License. License text: /licenses/tabler-icons.txt