Skip to content

What Should Network Threat Monitoring Cover?

Managed SOC guide

Network threat monitoring is only as good as what it can see. This guide sets out what a network threat monitoring service should watch, where it goes blind and what Malaysian rules say about the provider, drawing on the UK National Cyber Security Centre (NCSC), the US National Institute of Standards and Technology (NIST), Bank Negara Malaysia and NACSA.

Published 9 November 2026

Key takeaways

  • NIST’s Cybersecurity Framework 2.0 lists, as outcome DE.CM-01, that networks and network services are monitored to find potentially adverse events.
  • The UK NCSC lists web traffic, email metadata, IP connections to other networks and IP connections between security zones among the log sources to consider collecting.
  • NIST SP 800-94 (2007) says network-based intrusion detection cannot detect attacks inside encrypted traffic, including VPN connections, HTTPS and SSH sessions.
  • NACSA’s licensing FAQ says a managed security operation centre monitoring service must be licensed, while tools such as hardware and software need no licence.
What should network threat monitoring cover?

It should cover the traffic and logs where attacks show up: web traffic to and from the internet, email metadata, connections to other networks, connections between internal security zones and activity on the hosts themselves. It should combine known-threat signatures with checks against normal behaviour, account for encrypted traffic it cannot read, and come from a provider that meets Malaysia’s licensing rules.

On this page9

What is network threat monitoring?

It is a continuous watch over your network for signs of an attack. NIST’s Cybersecurity Framework 2.0 describes the outcome as networks and network services being monitored to find potentially adverse events (DE.CM-01). A second outcome in the same framework is that information is correlated from multiple sources (DE.AE-03).

NACSA’s licensing FAQ describes a managed security operation centre monitoring service in similar terms: monitoring another person’s computer systems by acquiring, identifying or scanning the information stored in, processed by or transmitted through them, to detect cyber security threats.

“Good monitoring is more than simply the collection of logs. It is also the use of appropriate tools and skilled analysis to identify indicators of compromise in a timely manner so that appropriate action can be taken.”– UK National Cyber Security Centre, Cyber Assessment Framework, Principle C1

Which traffic and logs should be monitored?

Start where attacks cross boundaries. The NCSC’s Cyber Assessment Framework lists web traffic, email traffic, IP connections between your network and others, IP connections between security zones, host-based activity and deviations from normal behaviour as log sources to consider. If you do not monitor traffic crossing your network boundary, the NCSC rates your monitoring as not achieved.

Log sources the NCSC suggests considering, and what they help find
Log source What to capture or look for What it helps find
Web traffic to and from the internet Domain names, URLs and IP addresses Malware beaconing, unauthorised access attempts, potential DoS attacks
Email traffic Metadata about what is sent and received Phishing delivered over email
Connections to other networks, including the internet IP connections Unusually high outbound data volumes to unknown or untrusted IP addresses
Connections between security zones 5-tuple metadata at critical zone boundaries Evidence of adverse activity inside your network
Host-based activity Unusual or unauthorised activity by users or software Activity that might evade detection focused on network interfaces
Deviations from normal User activity outside normal working hours, unexpected traffic Anomalies worth investigating

NIST SP 800-94 notes that network-based intrusion detection sensors are most commonly placed at boundaries between networks, near border firewalls or routers, VPN servers, remote access servers and wireless networks. The NCSC adds that new systems should be designed to produce the log data monitoring needs before they go live, so coverage keeps up as the network changes.

How does monitoring tell an attack from normal activity?

By combining two methods. NIST SP 800-94 says signature-based detection is very effective at detecting known threats but largely ineffective at detecting previously unknown ones, while anomaly-based detection compares a definition of normal activity with what is observed. The NCSC says automated monitoring should use both, for example spotting known command and control traffic and an abnormally large amount of data leaving the network.

Anomaly detection needs a baseline. The NCSC calls working out what normal or expected looks like a fundamental step towards identifying anomalies, and warns that something abnormal is not necessarily a sign of adverse activity. NIST adds that network intrusion detection typically requires considerable tuning and customisation to the monitored environment. For the financial institutions it covers, Bank Negara’s RMiT policy lists among a SOC’s required functions advanced behavioural analysis to detect signature-less and file-less malware and anomalies at endpoints and network layers. Our earlier post covers what type of cyber attacks a SOC can detect.

What can network monitoring miss?

Anything it cannot see. NIST SP 800-94 (2007) says network-based intrusion detection cannot detect attacks within encrypted traffic, including VPN connections, HTTPS and SSH sessions. Its answer is to monitor traffic after it has been decrypted, such as traffic that has passed through a VPN gateway, or to use host-based monitoring on the systems at either end. The NCSC likewise says host monitoring can catch activity that evades network-focused detection.

Cloud services are a second gap. NIST’s framework treats the activities and services of external service providers as something to monitor in their own right (DE.CM-06). For the institutions it covers, RMiT says a financial institution should understand the scope of its cloud service providers’ responsibility for cybersecurity monitoring, and that the agreement should cover how long relevant logs are kept for forensic purposes and the right to access them.

What should you ask a monitoring provider in Malaysia?

Ask what it will see, how it decides and what you get back. A provider should be able to list the log sources it will collect, explain how it handles encrypted traffic and hosts, say when it monitors and show how alerts are tuned. The NCSC also advises against black box tools that do not allow flexible querying or show the reasoning behind their results.

  1. Coverage. Which network boundaries, internal zones, hosts and cloud services will send logs, and which will not.
  2. Hours. When the monitoring runs. The NCSC’s top rating is logs monitored continuously in near real time.
  3. Tuning. How detection rules are customised and tuned to reduce false positives.
  4. Time and retention. Whether log sources share an accurate common time source, how long logs are kept and who can access them. The NCSC calls the duration and level of logging a business decision and asks you to consider data protection laws on the collected information.
  5. Escalation. How alerts reach the people who respond. The NCSC says monitoring should work seamlessly with incident management.
  6. Licence. Whether the provider holds a NACSA licence for managed SOC monitoring.

What do Malaysian rules say about monitoring providers?

NACSA’s licensing FAQ says any cyber security service related to a managed security operation centre monitoring service must be licensed under the Cyber Security (Licensing of Cyber Security Service Provider) Regulations 2024. Tools such as hardware and software need no licence, and the regulations do not apply where the computer system concerned is located outside Malaysia. The FAQ says a licence is valid for one year.

The FAQ also says a subcontractor providing the service on behalf of the main contractor must be licensed. For financial institutions, Bank Negara’s RMiT policy document (issued 25 September 2026) requires the SOC to operate on a 24×7 basis with disaster recovery capability, to have a holistic and end-to-end view including internal and external facing perimeters, and to provide a monthly threat assessment report. Its Appendix 12, a Code of Practice for national critical information infrastructure (NCII) entities designated by Bank Negara, which “comes into effect upon endorsement by the CE of NACSA”, says such an entity that engages external providers for SOC monitoring “shall appoint a cyber security service provider that holds a valid license issued under NACSA”, with exceptions such as a computer system “located outside of Malaysia”. How these rules apply to your organisation is a question for your own advisers.

How does NetAssist’s managed SOC watch a network?

At NetAssist, we monitor and detect threats across your digital infrastructure by observing log sources. When we onboard a customer, we collect logs from firewalls, endpoints, servers, Active Directory, cloud platforms and applications, and our SOC then continuously monitors security events. We hold NACSA licences for managed SOC monitoring and penetration testing.

We offer 24/7 monitoring or a hybrid model where our SOC monitors after office hours. Our SOC analysts investigate alerts and decide whether they are true or false positives, and we tune detection rules to reduce false positives. When an incident is confirmed, your team handles it, supervised by our senior SOC team, unless you buy our additional Managed Security Services (MSS). Our reports are monthly as standard, with weekly or bi-weekly reports on request. See our managed SOC service, what managed SOC onboarding includes, or whether you need a SIEM, a SOC or both.

FAQ

Is network threat monitoring the same as a SOC?

Not quite. Network monitoring is one input to a SOC. Bank Negara’s RMiT policy lists a SOC’s functions as including log collection with an event correlation engine, incident coordination and response, vulnerability management and threat hunting. The NCSC’s top rating for security monitoring includes both host-based and network monitoring.

Can network monitoring see inside encrypted traffic?

Not without decrypting it. NIST SP 800-94 (2007) says network-based IDPSs ‘cannot detect attacks within encrypted network traffic, including virtual private network (VPN) connections, HTTP over SSL (HTTPS), and SSH sessions’, and advises analysing payloads ‘before they are encrypted or after they are decrypted’, or using host-based monitoring on the systems at either end.

Does a network monitoring provider need a licence in Malaysia?

Generally, yes for a managed SOC monitoring service. NACSA’s licensing FAQ says any cyber security service related to a managed security operation centre monitoring service is required to be licensed under the 2024 licensing regulations, with exceptions such as a service for a computer system “located outside Malaysia”; tools such as hardware and software “are not required to be licenced”.

How long should network logs be kept?

The NCSC calls the duration and level of logging a business decision that balances risk, regulatory requirements and the need to query data during and after an incident.

Sources

  1. Cyber Assessment Framework, Principle C1 Security monitoring, UK National Cyber Security Centre (opened 10 Nov 2026)
  2. The NIST Cybersecurity Framework (CSF) 2.0, US National Institute of Standards and Technology, 26 February 2024 (opened 10 Nov 2026)
  3. NIST SP 800-94: Guide to Intrusion Detection and Prevention Systems (IDPS), US National Institute of Standards and Technology, February 2007 (opened 10 Nov 2026)
  4. Licensing of Cyber Security Service Provider FAQ, National Cyber Security Agency (NACSA) Malaysia (opened 10 Nov 2026)
  5. Risk Management in Technology (RMiT) policy document, Bank Negara Malaysia, issued 25 September 2026 (opened 10 Nov 2026)

Planning network threat monitoring?

Tell us which networks, systems and cloud services you want watched, and we will explain which log sources our managed SOC would collect and how monitoring would run.

Discuss managed SOC monitoring

Ready to get a best solution for your business?

Talk to NetAssist about the cyber security services your organisation needs.