{"id":73634,"date":"2025-09-17T13:54:19","date_gmt":"2025-09-17T12:54:19","guid":{"rendered":"https:\/\/www.n-able.com\/?p=73634"},"modified":"2025-11-19T10:56:39","modified_gmt":"2025-11-19T10:56:39","slug":"securing-n-central-with-n-able-sso-entra-id-and-adlumin","status":"publish","type":"post","link":"https:\/\/www.n-able.com\/de\/blog\/securing-n-central-with-n-able-sso-entra-id-and-adlumin","title":{"rendered":"Securing N‑central with N‑able SSO, Entra ID, and Adlumin"},"content":{"rendered":"

One of the reasons I love attending in-person events and visiting customers is the conversations. You pick up insights, tricks, and real-world stories you\u2019d never stumble across if you were permanently stuck in the virtual world. A standout moment for me this year happened during lunch at Empower in Berlin, when Florian from one of our Austrian customers sat down next to me. What started as a casual chat quickly turned into a fascinating deep dive into how they\u2019ve secured their N‑central environment using N‑able SSO, Entra ID, and Adlumin.<\/span><\/p>\n

There had been plenty of buzz around the new features in N‑central, and rightly so. They unlock powerful new capabilities for partners. But a key requirement to accessing them is logging in to your N‑central server via N‑able SSO. For customers on hosted instances of N‑central, this is already the default. However, many self-hosted partners still rely on standard authentication methods or direct Entra ID integration. As a result, they\u2019re missing out on the growing set of enhancements we are seeing in N‑central.<\/span><\/p>\n

The fact that I know not all our customers are accessing these new features yet is exactly why I found Florian\u2019s story so compelling. Not only is he leveraging N‑able SSO to access these enhancements in N‑central, he\u2019s taken it a step further by combining it with Entra ID and Adlumin to create a highly secure, streamlined environment, both for his team and the customers they support.<\/span><\/p>\n

When you\u2019re using a remote monitoring or unified endpoint management solution<\/a> like N‑central, securing that environment isn\u2019t optional, it\u2019s absolutely critical. These platforms sit at the heart of an MSP\u2019s operations, with deep access into customer systems, networks, and endpoints. A breach wouldn\u2019t just be catastrophic for the MSP; it could have devastating consequences for every client they serve. That\u2019s why getting authentication, access control, and monitoring right is so important, and why Florian\u2019s layered approach caught my attention.<\/span><\/p>\n

The Challenge<\/strong><\/h2>\n

That level of risk is exactly what makes securing access to N‑central so vital, and so complex. In the past, when Florian\u2019s team hosted their own N‑central instance, they relied on tried-and-true methods like firewall-based IP and country restrictions. It worked well because they had full control over the infrastructure. And many self-hosted partners still follow this model today.<\/span><\/p>\n

But things change when you move to a hosted environment. You no longer own or manage the underlying systems, so you can\u2019t rely on network-layer controls like you used to. The challenge then becomes: how do you maintain \u00a0or even improve your security posture without that level of direct control?<\/span><\/p>\n

The Solution<\/strong><\/h2>\n

\"\"<\/p>\n

 <\/p>\n

As shown in the diagram above, Florian\u2019s team implemented a secure, layered login and monitoring process by combining N‑able MSP SSO, Microsoft Entra ID, and Adlumin. Here\u2019s how the process works step by step:<\/span><\/p>\n