Prepared by NetAssist (M) Sdn Bhd
Managed SOC guide
Managed SOC onboarding brings your systems into a security operations centre’s view, from the logs it receives to how confirmed incidents are handled and reported. Public guidance on logging, onboarding and incident response comes from the US Cybersecurity and Infrastructure Security Agency (CISA), the UK National Cyber Security Centre (NCSC) and the US National Institute of Standards and Technology (NIST). At NetAssist, a Malaysian managed security service provider, SOC onboarding runs in six steps.
Published 20 October 2026 · Updated 27 October 2026
- The UK NCSC calls authentication, security-control and DNS logs “must-have” quick wins for a SOC.
- NIST SP 800-61 Revision 3 (April 2025) says responsibilities passed to a provider should be clearly defined in a contract, and the incident response team should know how they are divided, including who has authority to act on the organisation’s behalf.
- NetAssist’s SOC onboarding flow has six steps: Assess, Onboard, Monitor & Detect Threats, Investigate Alerts, Incident Response, and Report & Post Assessment.
Managed SOC onboarding includes identifying the critical assets and attack surfaces to watch, sending logs from sources such as firewalls, endpoints, servers, identity systems, cloud platforms and applications, checking that alerts are reviewed and tuned, and agreeing how confirmed incidents are reported and who acts on them. It also sets the reporting cycle, and it carries on as systems change.
On this page10
What does onboarding mean in a managed SOC?
In a managed SOC, onboarding means bringing systems into the SOC’s scope so their logs can be monitored. The UK NCSC defines it as adding systems to the scope of a SOC and making sure their logs are collected by or sent to the SOC systems. The NCSC calls it a key part of SOC operation for established SOCs as well as new ones.
“Onboarding is a key part of SOC operation, particularly for new SOCs but also for established SOCs; no IT estate will perpetually stay the same.”— UK National Cyber Security Centre, Onboarding systems and log sources
The NCSC lists ways to choose what to onboard, from common log sources or the output of risk assessments to every log source available, and itself describes a threat-led approach.
Which log sources should a managed SOC receive first?
A managed SOC should first receive the logs that show who is signing in, what security controls are seeing and which domains devices are looking up. The UK NCSC calls authentication, security-control and DNS logs “must-have” quick wins, and splits log sources into four broad categories: application, host, network and cloud. CISA adds that effective logs should contain enough detail to aid incident responders.
| Log source | What the NCSC says about it |
|---|---|
| Authentication (must-have) | Where and when users logged on to a system, or attempted to. |
| Security controls (must-have) | Anti-malware, firewalls and access control list changes, which “provide a first indication of something going wrong”. |
| DNS (must-have) | Requests that may give the first indications of a compromised device. |
| Application | Logs that “will often provide an invaluable insight into user actions”. |
| Host | Operating system and application logs, often collected by deploying an agent to the device. |
| Network | Information about connected devices and services across the estate. |
| Cloud | Any of the above, plus cloud management and compute services with their own logs. |
Swipe sideways to see every column
CISA’s logging guidance for small and medium businesses lists similar data, from user activity to network traffic, and recommends centralising logs:
“Centralization makes it easier to detect unusual activity.”— CISA, Use Logging on Business Systems
How are alerts reviewed and tuned once logs reach the SOC?
Once logs reach a managed SOC, alerts are reviewed and tuned so that the ones that fire can be properly investigated. The UK NCSC says it is common to perform a baselining exercise when building a SOC, to learn what “normal” looks like, and that addressing false positives “is a challenge for all SOCs”. It recommends regular reviews of commonly triggered alerts and testing detection use cases.
Logs reach a SOC by being collected by, or sent to, its systems; host logs often involve deploying an agent to the device. The NCSC calls a single platform where analysts can see and query log data from all onboarded systems “invaluable”, and says custom detection rules are typically implemented in SIEM tools. CISA’s guidance adds alerts for high-risk events, such as failed login attempts and privilege escalation.
At NetAssist, this work is steps 04 and 06 of our onboarding, Investigate Alerts and Report & Post Assessment, and our SOC uses a commercial SIEM. The NCSC also suggests red or purple team exercises to test detection; our 2025 article on purple teaming in NetAssist’s managed SOC covers that approach.
Who acts when a managed SOC confirms an incident?
Who acts on a confirmed incident depends on the managed SOC contract. NIST SP 800-61 Revision 3 calls this arrangement a shared responsibility model, in which an organisation transfers some of its responsibilities to a provider. NIST says those responsibilities should be clearly defined in a contract, and that the incident response team should know how they are divided, including who has authority to act on the organisation’s behalf.
Section 2.2 of the NIST publication adds: “This also includes restrictions on what the service provider can do, such as sharing sanitized incident information with other customers or making and implementing operational decisions (e.g., immediately deactivating certain services to contain an incident).” It notes that “Some third parties may fill a primary role (e.g., an MSSP performing incident detection, response, and recovery activities)”.
Before you sign, ask who remediates, whether the provider acts on your systems and with what access, and how you can check what was done.
Is managed SOC monitoring a licensed service in Malaysia?
Managed security operation centre monitoring is a licensed service in Malaysia. Malaysia’s National Cyber Security Agency (NACSA) says so in its licensing FAQ: question 1 names the services that need a licence under the Cyber Security Act 2024 (Act 854), which came into operation on 26 August 2024, as “Any cyber security service related to managed security operation centre monitoring service and penetration testing service.”
NetAssist holds NACSA licences for managed SOC monitoring and penetration testing.
How does NetAssist’s own SOC onboarding work?
At NetAssist, SOC onboarding follows six steps, from the first assessment to reporting: Assess, Onboard, Monitor & Detect Threats, Investigate Alerts, Incident Response, and Report & Post Assessment. We offer 24/7 monitoring, or a hybrid model where our SOC does the monitoring after office hours, and we can customise our plan for different requirements.
- Assess. Identify critical assets, systems, applications and potential attack surfaces.
- Onboard. Collect logs from firewalls, endpoints, servers, Active Directory, cloud platforms and applications.
- Monitor & Detect Threats. Continuously monitor security events through the SOC.
- Investigate Alerts. SOC analysts review alerts and determine whether they are true or false positives.
- Incident Response. Prioritise confirmed incidents based on severity and impact.
- Report & Post Assessment. Tune detection rules to reduce false positives and improve accuracy.
Need a risk assessment or a security test first? See our security posture assessment and consultancy services or our guide to choosing a penetration test or a vulnerability assessment. To discuss onboarding for your systems, choose “Security Operation Centre (SOC)” on our contact page.
What happens at NetAssist when an incident is confirmed?
At NetAssist, when an incident is confirmed, we inform the customer immediately, within our committed SLA (service level agreement). The customer’s team handles the incident, supervised by our senior SOC team and following our actionable alerts and instructions, so control of what is done can stay tightly with the customer. Customers who want us to act for them can add our Managed Security Services (MSS).
When we act for a customer to block malicious attacks at their request, especially outside working hours, we do it through a specific admin account with limited authority that the customer creates for that purpose. Afterwards the customer gets a full report and can audit our actions. The full service is on our Managed SOC services page.
What reporting and metrics does NetAssist provide?
At NetAssist, we track security performance using MTTD (mean time to detect), MTTR and actionable operational insights, against an SLA matrix, and MTTD and MTTR targets can be set and customised for each customer. Customers get monthly reports as standard, and weekly or bi-weekly reports on request. We can tailor reports to each customer’s requirements, with report types for technical teams, middle management and the C-suite.
Our compliance support is tailored to ISO 27001, and we enable an audit trail, so customers can audit us to meet their compliance requirements.
FAQ
How long does managed SOC onboarding take?
There is no single figure; it depends on the environment. Factors include the number and kind of log sources, whether host logs need an agent deployed to the device, how much tuning the first alerts need, and what the Assess step finds to cover.
What should we prepare before managed SOC onboarding?
It helps to have these ready (from CISA and NCSC guidance and our Assess and Onboard steps):
- a list of your critical assets, systems and applications;
- the log sources you can share, such as firewalls, endpoints, servers, Active Directory, cloud platforms and applications;
- any recent risk assessment;
- named contacts for a suspected incident;
- your log retention and compliance needs.
What continues after onboarding?
Onboarding continues after monitoring starts. The UK NCSC says “no IT estate will perpetually stay the same”, so new systems and log sources keep being added, and it recommends regular reviews of commonly triggered alerts. At NetAssist, step 06, Report & Post Assessment, is where we tune detection rules to reduce false positives and improve accuracy.
Sources
- Onboarding systems and log sources, UK NCSC (opened 20 Oct 2026)
- Log sources, UK NCSC (opened 20 Oct 2026)
- Detection practices and Detection approaches, UK NCSC (opened 20 Oct 2026)
- Use Logging on Business Systems, CISA (opened 20 Oct 2026)
- SP 800-61 Revision 3 and its full text (PDF), section 2.2, NIST (opened 20 Oct 2026)
- Licensing FAQ (PDF), question 1 and Act 854 page, NACSA (opened 27 Oct 2026)
Planning a managed SOC?
On our contact page, choose “Security Operation Centre (SOC)”, tell us which systems matter most, and ask how our six-step onboarding applies to you.

