Following the Able2Shell vulnerability disclosure, N-able took its hosted N-central environments offline and advised on-premises customers to keep their servers offline until N-able confirms they can safely be brought back online.
For current service status, remediation instructions, and restoration guidance, refer to N-able’s incident updates.
Impact on Liongard inspections
Liongard cannot collect data from your N-central instance while it is offline or unreachable. N-central inspections may fail during this disruption, and previously collected data will not refresh until successful inspections resume.
Once your instance is safely restored and accessible to Liongard, inspections are expected to resume on their normal schedule. If failures continue after connectivity is restored, please contact Liongard Support.
Additional monitoring available in Liongard
Liongard has added five metrics and associated alerts to the Metrics Library to help you monitor your N-central server once it is back online:
Server build version
Administrator roles
Roles that can run scripts, automation, or commands on endpoints
Access groups and members, including API and service accounts
Scheduled jobs
These metrics help establish a baseline of your server’s build, accounts, permissions, and jobs and support alerts when changes are detected.
Review the N-able N-central: Server Build, Administrator, and Access Review Metrics entry for metric and alert details and setup guidance.
Monitoring limitations
These metrics do not detect the Able2Shell vulnerabilities, determine whether a server has been compromised, or verify that a hotfix has been applied. N-able may apply a hotfix without changing the server’s build number.
Liongard requires the N-central server to be online and accessible to collect this information. Follow N-able’s guidance on when to restore service.