VK WorkSpace Federation Enables Secure Multi-Organization On-Premise Messaging Without Infrastructure Merge
VK Tech has introduced federation support for VK WorkSpace that links separate On-Premise installations while ensuring each organization retains complete sovereignty over its servers, databases, and security policies.
The solution addresses the common requirement for project teams to communicate with contractors, partners, and subsidiary companies without moving work conversations to public services. In the initial November 2025 pilot, two installations could exchange messages after one side issued an invitation and the other confirmed the trust relationship. The July 2026 release 26.2 removed the pairwise limitation, allowing a single group chat to include participants from multiple independent On-Premise environments.
Access is governed at two levels. First, a mutual trust is established between installations. Second, each administrator explicitly grants external-communication rights to selected employees for that specific trust. Only approved users see external contacts and can initiate dialogues or join federated group chats. The corporate directory is not replicated; only minimal profile data—name, work email, and organization flag—is shared.
Three architectural approaches were evaluated. A single-host model with proxy access was rejected because loss of the host would break history availability for all other parties. Adoption of the open Matrix protocol was also declined because it would have required extensive remapping of existing entities, rights, and APIs. The chosen design replicates only federation-related objects and events at the application layer so that each installation stores its own copy of permitted messages and files.
This local-replication model delivers several security and operational benefits: data remains under each organization’s control, local DLP, audit, and retention policies continue to apply, and no user session is created in a foreign environment. When a trust is revoked, already-received history stays in the local instance.
Client applications continue to connect exclusively to their own installation. A dedicated federation layer intercepts relevant operations, forwards them through secure gateways, and replays them via the local messenger API on the receiving side. The core messenger logic remains unchanged, although every new feature must still be validated for multi-party federation compatibility.
Extensive dogfooding on internal test stands helped refine both the protocol and the user interface, particularly the hiding of unsupported actions to prevent user errors. The feature is now deployed in production On-Premise environments at several customer sites.
Related articles
Survey Shows 42% of Organizations Unify Multi-Vendor Security Tools into Single Protection Contour
A live AM Live broadcast on cybersecurity ecosystems revealed that 42% of participants have already combined solutions from multiple vendors into one unified security contour. Another 23% reported partial integration of tools, while 24% keep their protections operating independently and only 11% rely exclusively on a single vendor. Panelists emphasized the need for clear responsibility assignment, seamless data exchange, and formation of shared security context across products. Key selection criteria for ecosystems included breadth of product lines for 32% of viewers and discounts or bonuses for 28%. Experts advised practical testing of interoperability and evaluation of total cost of ownership before committing to any model. Service provider responsibilities for integration, SLA compliance, and outcomes must be defined in advance, according to CURATOR director Edgar Mikaelyan. After the session, 32% of attendees stated plans to launch or expand a security ecosystem project.
Yandex Tests Compass Device for Taxi Navigation During GPS Outages
Yandex is conducting trials of a compact Compass device in 10,000 taxis connected to its service to maintain accurate vehicle positioning when GPS signals are lost or jammed. The device connects to the OBD diagnostic port and pulls wheel speed data via the CAN bus while using its built-in gyroscope and accelerometer to determine direction of travel. These readings are sent over Bluetooth to the Yandex Pro driver app, which combines them with the last known GPS coordinates and frequent Wi-Fi access point scans to update the map in real time. The initiative addresses ongoing navigation problems that have affected Russian cities since spring 2022 and have been compounded by regular mobile internet outages since spring 2025. Earlier, Yandex tested a similar OBD-connected gadget called Yandex Pathfinder in 2023. The company has not disclosed timelines for completing the current trial or rolling the solution out more widely, though it plans to make Compass available to ordinary drivers later. Yandex navigation apps have also offered an offline step-by-step routing mode since 2025.
Apple Attributes Widespread Service Outage to Faulty Internal IT Update
Apple has confirmed that the large-scale outage affecting its systems and user services on November 17, 2026, was caused by an incorrect internal update within the company's IT infrastructure. The incident impacted multiple consumer-facing services including the App Store, iCloud, Apple Pay, and Apple ID authentication. Users reported inability to download applications, sign in to accounts, or activate devices during the disruption. Internal corporate tools such as AppleWeb, AppleConnect, employee VPN access, corporate calendars, and the internal incident-tracking site were also taken offline. Retail operations in Apple Stores worldwide experienced interruptions to sales, repairs, and customer service processes. Company engineers restored most systems within four hours and stated they were working to return remaining services to normal operation as quickly as possible. Apple explicitly ruled out any external cyberattack or third-party interference as the cause of the outage.
Global Outage Disrupts Apple Services Including App Store, iCloud and Apple Pay
On November 17, 2026, widespread disruptions affected multiple Apple services worldwide, including the App Store, iCloud, Apple Pay, and Apple ID authentication systems. The incident impacted users attempting to download applications on iPhone devices, sign into accounts, or activate new hardware. Apple confirmed problems with Apple Music and App Store functionality, along with performance degradation or complete unavailability of iCloud for all users. The outage was explicitly stated as unrelated to any country-level internet traffic filtering or restrictions. Service interruptions prevented normal operation of cloud storage, music streaming, and payment processing features tied to Apple ID. No official timeline for full restoration was provided in the initial reports from the company.