N-able
N-able offers a portfolio covering adding expert monitoring and response to supported telemetry, connecting security signals across supported domains, protecting recoverable data and organizing restoration, keeping supported software and devices maintained and organizing access to shared or individual credentials. The entries in this catalog include Adlumin MDR, Adlumin XDR, Cove Data Protection, N-able N-central, N-able N-sight and N-able Passportal. Adlumin MDR focuses on managed threat detection and response. Adlumin XDR focuses on cross-domain threat detection and security investigation. Cove Data Protection focuses on cloud-managed backup and recovery. When reviewing N-able, compare the named products individually: a platform family, a specific module and a managed service can have different scopes and purchasing requirements. Selection should account for supported data sources, response authority, escalation responsibilities and the actions included in the service agreement. Portfolio detail - Adlumin MDR: the catalog lists Managed threat monitoring, Response and containment support, Incident communication. - Adlumin XDR: the catalog lists Cross-domain detection, Automated response, Threat hunting. - Cove Data Protection: the catalog lists Backup and restore workflows, Ransomware recovery support, Immutable storage options. - N-able N-central: the catalog lists Automated patch deployment, Remote endpoint management, Policy-driven automation. - N-able N-sight: the catalog lists Automated patch deployment, Remote endpoint management, Policy-driven automation. - N-able Passportal: the catalog lists Encrypted password vaults, Administrative policies, Password generation. For procurement, map each required capability to a named offering and confirm the edition, dependencies and delivery responsibility with the vendor. Product-level entries below provide the operational context and evaluation questions for that comparison.
Documented Software Products (5)
Adlumin XDR
Adlumin XDR from N-able focuses on cross-domain threat detection and security investigation. It is extended detection and response technology used for connecting security signals across supported domains. Capabilities - Cross-domain detection: Connects observations from supported security domains rather than treating every alert as an isolated event. - Automated response: Connects detected activity with the response actions documented for the platform. - Threat hunting: Supports proactive investigation across the telemetry included in the deployment. - Third-party security integrations: Uses the documented connections to bring external security products into the analysis workflow. - Endpoint telemetry: Adds endpoint context to the security domains covered by the product. - Cloud security telemetry: Adds cloud environment context where the platform's documented integrations include it. Use and operational context Adlumin XDR is relevant to security operations teams investigating activity that spans multiple systems when the requirement centers on connecting security signals across supported domains. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Before adoption, review telemetry coverage, correlation quality, response permissions and integration with existing protection products. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Adlumin XDR focuses on connecting security signals across supported domains. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
Cove Data Protection
Cove Data Protection from N-able focuses on cloud-managed backup and recovery. It is backup and recovery technology used for protecting recoverable data and organizing restoration. Capabilities - Backup and restore workflows: Creates recoverable copies of the data or workloads within the product's documented protection scope. - Ransomware recovery support: Supports planning for recovery scenarios in which malicious activity has affected production systems. - Immutable storage options: Provides an option intended to protect stored recovery data from alteration under the documented configuration. - Recovery orchestration: Supports coordinating recovery steps instead of treating each restore as an isolated activity. - Microsoft 365 backup: Includes the Microsoft cloud productivity workloads named in the vendor documentation. - Backup isolation: Separates recovery data or its access path according to the isolation mechanism described by the product. - Recovery verification: Provides a way to assess whether protected data can be recovered as intended. Use and operational context Cove Data Protection is N-able's cloud-managed data protection entry. Review the protected workload scope and the administration workflow used by the organization or service provider, then perform a recovery test that reflects the customer's retention and availability needs. Deployment and evaluation Deployment: Cloud service / SaaS. Before adoption, review protected workloads, retention settings, recovery location and a practical restore test using representative business data. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Cove Data Protection focuses on protecting recoverable data and organizing restoration. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
N-able N-central
N-able N-central from N-able focuses on endpoint monitoring and patch management. It is endpoint administration and patching technology used for keeping supported software and devices maintained. Capabilities - Automated patch deployment: Helps distribute software updates across the endpoints included in the management scope. - Remote endpoint management: Supports administering devices without relying on an administrator being physically present. - Policy-driven automation: Turns repeatable endpoint administration tasks into configured management workflows. - Patch compliance reporting: Helps teams identify devices or software that still require update attention. Use and operational context N-central addresses administration of an endpoint estate through N-able's management environment. Review device organization, patch scheduling and automation permissions, with particular attention to how operators manage multiple networks or customer environments in the intended deployment. Deployment and evaluation Before adoption, review application coverage, deployment scheduling, restart behavior and a pilot group that represents production devices. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? N-able N-central focuses on keeping supported software and devices maintained. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
N-able N-sight
N-able N-sight from N-able focuses on remote endpoint monitoring and patching. It is endpoint administration and patching technology used for keeping supported software and devices maintained. Capabilities - Automated patch deployment: Helps distribute software updates across the endpoints included in the management scope. - Remote endpoint management: Supports administering devices without relying on an administrator being physically present. - Policy-driven automation: Turns repeatable endpoint administration tasks into configured management workflows. - Patch compliance reporting: Helps teams identify devices or software that still require update attention. Use and operational context N-sight addresses remote monitoring and administration within N-able's portfolio. Evaluate the organization's day-to-day device support tasks, including how monitoring information, maintenance actions and software updates are handled by the operators responsible for the managed endpoints. Deployment and evaluation Before adoption, review application coverage, deployment scheduling, restart behavior and a pilot group that represents production devices. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? N-able N-sight focuses on keeping supported software and devices maintained. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
N-able Passportal
N-able Passportal from N-able focuses on service-provider credential and password management. It is business password management technology used for organizing access to shared or individual credentials. Capabilities - Encrypted password vaults: Stores credentials within the protected vault model described by the vendor. - Administrative policies: Gives organizations controls for governing how the password manager is used. - Password generation: Helps users create passwords without relying on manually chosen patterns. - Access reporting: Provides visibility into the administrative or credential activity included in the product. - Directory or identity integration: Connects organizational identity processes with password manager deployment or account administration. Use and operational context N-able Passportal is relevant to organizations governing employee credential use when the requirement centers on organizing access to shared or individual credentials. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Deployment: Cloud service / SaaS. Before adoption, review vault permissions, account recovery, identity integration and a controlled onboarding and offboarding process. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? N-able Passportal focuses on organizing access to shared or individual credentials. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
Documented Managed Services (1)
Managed services provide outsourced human-led operations, threat hunting, or perimeter maintenance.
Adlumin MDR
Adlumin MDR is a managed security service offered by N-able. Its documented scope centers on managed threat detection and response. Capabilities - Managed threat monitoring: Adds a service team to the monitoring and assessment of supported security signals. - Response and containment support: Assists with the response steps included in the service agreement and technical deployment. - Incident communication: Provides a channel for communicating findings and the actions required from the customer. Use and operational context Adlumin MDR is relevant to organizations seeking external security operations support when the requirement centers on adding expert monitoring and response to supported telemetry. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Deployment: Managed service with provider-led monitoring and response within the agreed service scope. Before adoption, review supported data sources, response authority, escalation responsibilities and the actions included in the service agreement. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Adlumin MDR focuses on adding expert monitoring and response to supported telemetry. - What should a proof of concept establish? Test the listed capabilities against representative service deliverables, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.