Release 2.44 introduces connection management and SIEM integration, giving users more control over active browser sessions and helping security teams monitor Uniqkey activity through existing security tools.
What's new
Manage active connections
Users can stay signed in across multiple browsers and revoke connections that are old, unknown, or no longer trusted.
SIEM integration
Security teams can retrieve Uniqkey audit logs in Microsoft Sentinel, Elastic, Splunk, and other SIEM platforms that support pull based integrations.
Manage active connections
Users can now stay signed in to Uniqkey across multiple browsers at the same time, without being logged out of existing sessions. The new Connections view shows where users are currently signed in and when each connection was last active.
- See active browser connections in one place
- Revoke individual browsers that are no longer trusted
- Sign out all other active browsers when needed
Users can quickly review active browsers and revoke access if a device is lost, replaced, or no longer trusted.
Monitor audit logs in your SIEM
Uniqkey audit logs can now be retrieved by Microsoft Sentinel, Elastic, Splunk, and other SIEM platforms that support pull based integrations. This helps security teams include Uniqkey activity in existing dashboards, alerts, searches, and investigation workflows.
- Monitor Uniqkey activity through existing security tools
- Support investigations across systems from one place
- Access audit log events only, without exposing encrypted passwords or secured content
What this means to you
- Stay signed in to Uniqkey across multiple browsers at the same time
- Identify and remove old or unrecognised connections
- Respond quickly if a device is lost or compromised
- Monitor Uniqkey activity in your existing SIEM
- Strengthen oversight without exposing protected data