This release focuses on security hardening, communication reliability, and overall stability improvements across Take Control Standalone agents. While no new end‑user features were introduced, both Windows and Linux agents received important updates to strengthen backend communication, encryption, and operational stability.
Continue readingA new Release Candidate (RC) version of the Patch Management Engine is being made available to N-central assets configured to use the RC channel. This release includes fixes focused on improving patch metadata accuracy, handling of new Microsoft update formats, and overall patch detection reliability.
We’re releasing a new version of the N-sight Mac agent, version 3.10.1, as a Release Candidate today. This release includes security improvements and improves device classification by ensuring laptops are correctly displayed in the N‑sight console.
We’re pleased to announce an upcoming release for N-able Risk Intelligence, scheduled for delivery starting on Tuesday, March 3rd, 2026.
This release is focused on upgrades to our back-end systems addressing several security related improvements and infrastructure enhancements.
There may be brief moments of downtime during the maintenance windows, which may result in usability issues or errors within the application. After the maintenance windows, all operations should resume as normal.
In the following period, we will be releasing an update to MAV and AVD Bitdefender agents, starting with Tuesday, March 3rd. For MAV, the changes will be available across all regions by the end of the week (March 6th).
The initial AVD release will support AVD Updates, and by March 11th, we will support fresh installs, upgrades, repair tools, and uninstall tools.
🛠️ Key Changes:
🔧 Resolved issues:
🗓️ Deployment Schedule:
In Cove 26.2, Critical Configuration Changes is now generally available for all customers, allowing users to create event-based alerts for indicators of compromise in their backup policies. With real-time visibility into critical changes made to backup policies, users can take just-in-time action to resolve these changes before recovery efforts are impacted.
Other enhancements made include the migration of One-Time Restore to Azure to our new UI design system and improving the reliability of general Continuity functionality.
Continue readingThis release focuses on enhanced security compliance, improved performance, and key quality updates across the standalone Windows agent.
We are pleased to announce that on Tuesday February 24, Adlumin will release a new set of detection rules for Fortinet. This update expands your visibility into threats in Fortinet-protected environments by analyzing the Fortinet syslog data you already send to Adlumin. In practical terms, these new detections help identify a wider range of malicious activities including, wireless network attacks, misused or high-risk applications, and unusual data exfiltration attempts using the Fortinet log information currently forwarding to our platform.
Continue readingThis release introduces new end-user access capabilities, automated device lifecycle management, expanded APIs, and platform hardening across the Cloud environment.
Exclusive Direct Links for End-User Area
Automatic Deletion of Inactive Devices
SentinelOne is deprecating Legacy Deep Visibility and S1QL 1.0 custom detection rules. This change impacts both API-based integrations and in-app workflows that still rely on legacy capabilities. You can continue using Deep Visibility Enhanced in the Management Console and Event Search in the Singularity Operations Center.
If you use Legacy Deep Visibility APIs (or legacy UI features that depend on them), you must migrate before February 15, 2027 to avoid disruption.
Required actions (before February 15, 2027):
To support the transition, you can use “Migrate Queries” in legacy Deep Visibility to move saved queries to Deep Visibility Enhanced and Event Search.
Starting February 15, 2026, you can create new custom detection rules only using S1QL 2.0.
All existing S1QL 1.0 custom detection rules will be automatically migrated to S1QL 2.0. No action is required for existing rules.
You are likely impacted if you:
If you only use Deep Visibility Enhanced and Event Search, you can continue as-is.
For full details, see:
Offline Help → Management Console Release Notes → Deprecation Notes
You must be logged in to post a comment.