On paper, the stack is complete: an RMM for day-to-day operations, an endpoint protection for defence. Yet one important question remains unanswered in between: how secure is the IT infrastructure, really?
The RMM answers: which devices do I manage, and can I reach them? The endpoint protection answers: what is happening right now on the devices I protect? How large the attack surface actually is, and which vulnerabilities currently deserve the highest priority, is something neither tool answers on its own.
For MSPs, this is more than a question of which tools are in place – it is a question of proof. They sell systems, and their customers generally assume those systems are secure. But are they? That is exactly the job of vulnerability management.
The Modern MSP Stack at a Glance
Three pillars, three jobs. The first enables operations, the second creates transparency, the third protects:
Pillar | Category | Description | Functions | Analogy |
|---|
Operations | Remote Monitoring & Management (RMM) | Managing and operating IT systems | Device monitoring, patch management, remote maintenance, IT automation | The Arm |
Visibility | Vulnerability Management (VM) | Identifying and reducing security risks | Vulnerability detection, risk prioritisation, remediation management, security reporting | The Eyes |
Protection | Endpoint Protection (EP) | Protecting endpoints against cyber attacks | Malware protection, attack detection, threat defence, incident response | The Immune System |
Pillar 1: Operations – The RMM as the Arm of the Stack
It all starts with the ability to reach and manage systems. The RMM takes on central tasks here: it deploys agents, maintains systems remotely, monitors them and automates routine work. This is also how the lywand agent can be rolled out efficiently to endpoints and servers. We have set out what an RMM can do and where it stops right here.
Many MSPs also use the RMM for patch management. That makes sense, because an RMM is well suited to rolling out updates and monitoring their installation. The risk-based assessment of vulnerabilities, however, is not its focus. An available update is not automatically the most urgent one. Which vulnerability in a specific environment should be fixed first has to be assessed separately. How far apart patch management and reality can be is shown in this field report.
That assessment is crucial. Germany's Federal Office for Information Security (BSI) now counts an average of 119 new vulnerabilities per day – roughly 24 percent more than in the same period a year earlier – and notes that the gap between patch availability and exploitation has been shrinking for years. Anyone who patches solely on the basis of availability may be giving the actual risk too little weight.
Pillar 2: Visibility – Vulnerability Management for MSPs
The second pillar is about attack surface intelligence. Lywand examines the IT infrastructure independently of the RMM and endpoint protection. This gives MSPs an additional, objective assessment of security risks. Why this independence matters is explained here.
The assessment runs from two perspectives:
1. Internal Perspective (Network)
Agent Check: The lywand agent is rolled out via the RMM and analyzes endpoints and servers for misconfigurations, hardening gaps and local vulnerabilities. It also assesses conformity with the CIS Benchmarks and highlights deviations from established security standards.
Asset Discovery: Lywand also finds the devices that appear on no inventory list. According to Trend Micro (2025), 74 percent of companies have already experienced a security incident caused by an unknown or unmanaged asset. Find out how Asset Discovery uncovers shadow IT.
Network Check: Detected network devices can then be systematically checked for open ports and known vulnerabilities. More on the agent-based Network Check.
2. External Perspective (Attacker's View)
In parallel, lywand scans the external infrastructure the way an attacker would – including forgotten subdomains, open ports, exposed services and vulnerabilities in web applications.
The result is not a mere list of vulnerabilities but a risk-based prioritisation – an essential component of attack surface management. Because what counts is not the number of vulnerabilities found, but which of them actually represent a risk.
Of 237,687 published CVEs, only around 6 percent have ever been exploited in the wild (FIRST and Cyentia Institute). Anyone who treats all vulnerabilities the same wastes valuable resources and risks leaving critical gaps open for too long. Lywand prioritises vulnerabilities by their actual risk and shows MSPs where action is needed first. Remediation then follows in a targeted way: through patches via the RMM, configuration adjustments, or deactivating exposed services.
For its assessment, lywand considers three key factors, among others:
First, the severity of a vulnerability via the Common Vulnerability Scoring System (CVSS),
second, the probability of exploitation within the next 30 days via the Exploit Prediction Scoring System (EPSS), and
third, whether it appears in CISA's KEV catalog (Known Exploited Vulnerabilities).
The outcome is a risk-based prioritisation rather than a plain sort by severity score. (You will find further details in our service description.)
That means: a vulnerability that is already being actively exploited generally deserves higher priority than a gap that is dangerous only in theory. For your team, this primarily means one thing – it can focus on the most important risks first instead of working through hundreds of findings one by one.
How this differs from a classic vulnerability scanner is set out in a direct comparison.
Pillar 3: Protection – Endpoint Protection as the Immune System
The third pillar is endpoint protection (EP). It detects and blocks threats on endpoints – for example malware, suspicious processes or specific attack activity.
Vulnerability management and endpoint protection do not replace each other; they complement each other. Vulnerability management helps to identify, prioritise and specifically fix vulnerabilities. This reduces the attack surface. Endpoint protection additionally defends against threats, including when attackers exploit previously unknown or not yet remediated vulnerabilities.
Endpoint protection on its own, however, does not replace systematic vulnerability scanning. Even a blocked attack does not automatically mean that the underlying vulnerability has been fixed.
The Three Pillars Working Together
Only in combination do the three areas form a holistic security concept. If one pillar is missing, important tasks remain unaddressed:
RMM and EP without VM? You manage and protect endpoints, but you have no independent, comprehensive view of existing vulnerabilities and their priority.
VM and EP without RMM? You identify risks and protect endpoints, but central management and automated implementation of measures become considerably more laborious.
RMM and VM without EP? You identify and fix vulnerabilities, but an additional layer of protection for detecting and defending against ongoing attacks is missing.
Scaling: Why This Only Works Centrally
With a handful of customers, vulnerabilities can still be reviewed and prioritised manually. At 50 or 150 customers, that quickly becomes time-consuming. A central platform enables MSPs to assess risk across all customers and coordinate measures in a targeted way. If the same vulnerability appears at several customers, remediation can be planned centrally and rolled out, for example, via the RMM. This allows MSPs to serve even large customer environments efficiently.
Quick Check: How Blind is Your Current Stack?
The BSI notes that around 80 percent of the attacks reported in 2024 targeted small and medium-sized enterprises – precisely the customers you serve. So use three questions to check how well your current setup is positioned:
Do you know today exactly which three vulnerabilities in your customer's network represent the highest real risk?
Do you have a complete list of all active devices (including unmanaged devices) in your customer environments?
Are your patch cycles based on a risk-based analysis, or primarily on the availability of updates?
If you answer any of these questions with "no" or "not sure", you are missing one of the three pillars or the links between them.
Conclusion: Understand Security as Architecture
A modern MSP stack built on three interlocking pillars is not a tool decision but an architectural one. It brings calm to day-to-day operations, because it answers the question that gets lost in the daily grind: where do we stand right now?
It is not about finding the one "perfect tool", but about combining the strengths of the individual solutions in a meaningful way.
In the end, what counts is the evidence you can show the customer: a traceable assessment that demonstrates how their security posture has developed and which measures come next. The decisive question for MSPs is therefore not only which tools they use, but how they can demonstrate their effectiveness to their customers.
Make Your Customers' Infrastructure Visible
Prioritise vulnerabilities by risk instead of solely by update availability. In a short demo, we will show you how lywand complements your RMM and endpoint protection, and how you can present the results transparently to your customers.
FAQ