Prepared by NetAssist (M) Sdn Bhd
Managed SOC guide
A SIEM is software that collects and correlates logs and raises alerts; a SOC is the team that investigates those alerts and responds. This guide draws on the US National Institute of Standards and Technology (NIST), the UK National Cyber Security Centre (NCSC), the US Cybersecurity and Infrastructure Security Agency (CISA) and Malaysia’s National Cyber Security Agency (NACSA).
Published 2 November 2026
- NIST defines security information and event management (SIEM) software as “a program that provides centralized logging capabilities for a variety of log types.”
- The UK NCSC says most security operations centres (SOCs) are responsible for detecting and responding to cyber attacks.
- The NCSC says alert rules are typically implemented in SIEM tools, and that staff are needed to build and maintain them.
- NACSA’s licensing FAQ says managed SOC monitoring is a licensed service under the Cyber Security Act 2024, while tools such as hardware and software are not required to be licensed.
A SIEM is software that collects logs from your systems, correlates events and raises alerts. A SOC is the team and process that investigates those alerts and responds to attacks. They work together: the SIEM gives the SOC its data and alerts, and the SOC builds the SIEM’s rules and decides what the alerts mean. If you want attacks detected and acted on, you need both, run in-house or through a managed SOC.
On this page9
What is the difference between a SIEM and a SOC?
A SIEM is a tool and a SOC is a function. The SIEM collects log data and flags what looks significant; the SOC’s analysts decide what each alert means and respond to real attacks. The SIEM tells people where to look; the SOC’s people do the looking and the responding.
| Question | SIEM | SOC |
|---|---|---|
| What is it? | Software that centralises, analyses and stores logs | A team, its processes and its tools |
| Main job | Collect, correlate and prioritise events from many log sources | Detect and respond to cyber attacks |
| Output | Alerts and reports | Investigated alerts and responses to attacks |
| Who staffs it | Staff who build and maintain its alert rules | Analysts and incident responders |
The NCSC puts the purpose of a SOC this way:
“The role of a SOC is to limit the damage to an organisation by detecting and responding to cyber attacks that successfully bypass your preventative security controls.”– UK National Cyber Security Centre, Building a Security Operations Centre (SOC)
What does a SIEM do?
A SIEM gathers logs in one place and makes sense of them. NIST’s 2006 log management guide, SP 800-92, says a SIEM server analyses the data from all the different log sources, correlates events among the log entries, and identifies and prioritises significant events. The same 2006 guide said SIEM products usually included “support for several dozen types of log sources, such as OSs, security software, application servers (e.g., Web servers, e-mail servers), and even physical security control devices such as badge readers.”
NIST’s 2025 incident response guidance, SP 800-61 Revision 3, recommends using tools such as SIEM and security orchestration, automation and response (SOAR) to continuously monitor log events for known malicious and suspicious activity, and using event correlation to gather related data captured by multiple sources.
What does a SOC do that a SIEM cannot?
A SOC supplies the judgement a SIEM lacks. The NCSC says detection tools typically generate alerts for human analysts to investigate, and that for custom detection use-cases, “Staff are needed to build and maintain these alerts and their logic.” People decide what a SIEM should look for, whether an alert is real, and what to do about it.
The NCSC gives an example of an alert rule: you might want to know if files are being emailed out of the business outside working hours. A typical monitoring platform can detect that, it says, “providing you configure the alert rules to do so.” Threat hunting, which the NCSC describes as the human-centric identification of cyber threats that have evaded existing security controls, “requires the highest investment in skilled staff.”
NIST SP 800-61 Revision 3 describes the same split. Because the volume of potential events is high, it says organisations should rely on technical solutions to filter them down to a subset suitable for human viewing. It also recommends manual reviews of logs from technologies that automation cannot monitor sufficiently. For the kinds of attack a SOC looks for, see our article on what types of cyber attacks a SOC can detect.
Do you need both a SIEM and a SOC?
If you want attacks detected and acted on, yes, because each depends on the other. A SIEM without people produces alerts that nobody investigates, and a SOC without centralised logs has little to analyse. The real choice is who runs each part: some organisations buy a SIEM and staff their own SOC, while others use a managed SOC, where a provider does the monitoring on contract.
NIST’s 2006 guide also noted that SIEM software was usually much more complicated and expensive to deploy than a centralised syslog set-up, so buying the software is the start of the work. NIST SP 800-61 Revision 3 lists outsourcing a SOC to a managed security services provider (MSSP) as one way to have that capability on contract. Our guide to choosing a managed SOC or an in-house SOC covers that decision.
What should you settle before buying a SIEM or a managed SOC?
Settle what the SIEM will collect, who will write and tune its rules, who investigates alerts, who acts on a confirmed incident and what happens to your logs if the contract ends. These questions apply whether you buy software or a service.
As general guidance drawn from NIST and CISA:
- Choose the log sources. CISA’s SIEM guidance set includes advice on prioritising log ingestion into a SIEM. Our article on what managed SOC onboarding includes covers the usual first sources.
- Name who builds and tunes the rules. NIST says monitoring should be tuned to reduce false positives and false negatives.
- Name who investigates and who acts. NIST recommends that alerts go to staff such as the SOC and incident responders. Agree who confirms an incident and who carries out the response.
- Ask about formats and exit. NIST’s 2006 guide noted that “there are no standards specific to SIEM, so each SIEM product stores and transmits data in any format it chooses.” NIST also lists provisions for what happens after a service agreement ends as part of supply chain risk planning.
- Check access. NIST notes that service providers often have privileged access to organisational systems and may have access to sensitive data.
Does Malaysian law treat SIEM software and a managed SOC service differently?
Yes. Under the Cyber Security Act 2024 (Act 854), NACSA’s licensing FAQ does not name SIEM, but says tools such as hardware and software are not required to be licensed, while a cyber security service related to managed security operation centre monitoring is. A provider offering managed SOC monitoring needs a licence, subject to exceptions the FAQ lists, such as a service provided by a Government Entity.
The NACSA licensing FAQ, citing the Cyber Security (Licensing of Cyber Security Service Provider) Regulations 2024 [P.U. (A) 221/2024], defines a managed SOC monitoring service as one for monitoring another person’s computer or computer system to identify or detect cyber security threats, or for determining the measures needed to respond to, recover from and prevent incidents. It says the licence applies to anyone who intends to provide such a service or holds itself out as a provider, and that the application process “will commence on 1st October 2024.”
How does NetAssist’s managed SOC use a SIEM?
At NetAssist, our managed SOC runs on a commercial SIEM. We collect logs from firewalls, endpoints, servers, Active Directory, cloud platforms and applications. Our SOC analysts review alerts and determine whether they are true or false positives, and we tune detection rules to reduce false positives and improve accuracy.
We offer 24/7 monitoring, or a hybrid model where our SOC does the monitoring after office hours. Your team handles a confirmed incident, supervised by our senior SOC team, unless you purchase our additional Managed Security Services (MSS). We hold NACSA licences for managed SOC monitoring and penetration testing. See our managed SOC service for how onboarding works. SIEM is also one of the security technologies on our technology and solutions page.
FAQ
Is a SIEM the same as a SOC?
No. A SIEM is software: NIST defines it as a program that provides centralised logging capabilities for a variety of log types. A SOC is the team and process that the NCSC says is responsible for detecting and responding to cyber attacks.
Can a SIEM respond to an attack by itself?
Some can start a response. NIST SP 800-92 says a SIEM server can initiate responses to events if desired. The NCSC, however, says detection tools typically generate alerts for human analysts to investigate, and that for custom detection use-cases, “Staff are needed to build and maintain these alerts and their logic.”
What is SOAR?
SOAR stands for security orchestration, automation and response. NIST SP 800-61 Revision 3 names SIEM and SOAR together as tools for monitoring log events and correlating related data, and CISA has published guidance for organisations seeking to procure SIEM and SOAR platforms.
Does a SIEM need a licence in Malaysia?
Not on NACSA’s wording. Its licensing FAQ does not name SIEM, but says tools such as hardware and software are not required to be licensed under the Cyber Security Act 2024, while a service related to managed security operation centre monitoring is, unless an exception applies, such as a Government Entity providing it.
Do I need a SIEM if I use a managed SOC?
A managed SOC still runs on log collection and alert rules, which the NCSC says are typically implemented in SIEM tools; the difference is that the provider does the monitoring. At NetAssist, our managed SOC runs on a commercial SIEM. Ask any provider whose SIEM it uses and who keeps your logs if the contract ends.
Sources
- NIST SP 800-92: Guide to Computer Security Log Management, US National Institute of Standards and Technology, September 2006 (opened 3 Nov 2026)
- Glossary: Security Information and Event Management, NIST Computer Security Resource Center (opened 3 Nov 2026)
- NIST SP 800-61 Revision 3: Incident Response Recommendations and Considerations for Cybersecurity Risk Management, US National Institute of Standards and Technology, April 2025 (opened 3 Nov 2026)
- Building a Security Operations Centre (SOC), UK National Cyber Security Centre, published 23 May 2022 (opened 3 Nov 2026)
- Building a SOC: Detection approaches, UK National Cyber Security Centre (opened 3 Nov 2026)
- Licensing of Cyber Security Service Provider FAQ, National Cyber Security Agency (NACSA) Malaysia (opened 3 Nov 2026)
- Guidance for SIEM and SOAR Implementation, US Cybersecurity and Infrastructure Security Agency (opened 3 Nov 2026)
Weighing a SIEM against a managed SOC?
Tell us your critical assets, systems and applications, and the log sources you have today. We can customise our plan for different requirements.

