Skip to main content

Shared Signals Beta

Enforcement checks a device at sign-in. Shared Signals adds the time in between: when a device stops passing your policy, XFA tells your identity provider within minutes, so it can end the device's active sessions instead of waiting for the next sign-in.

XFA is a transmitter in the Shared Signals Framework (SSF) and sends CAEP security events. Where an identity provider cannot receive those events, XFA calls the provider's API instead.

Beta

Shared Signals is in beta and is turned on per organization on request. Email support@xfa.tech with the name of your organization and the identity provider you want to connect. Once it is on, Shared Signals appears under Device security in the menu of the XFA dashboard.

Supported identity providers

Identity providerHow XFA connectsWhat the identity provider receives
Okta Identity Threat ProtectionXFA pushes events to your Okta org; no tokendevice-compliance-change events, so Okta's own policies decide what happens
Google Workspace (closed beta at Google)SSF stream, created by Google with a connection tokensession-revoked events when a device becomes not compliant
Microsoft Entra IDMicrosoft Graph, no SSF streamXFA revokes the user's sign-in sessions when a device becomes not compliant
Other SSF receiversSSF stream, created by the receiver with a connection tokenThe CAEP events the receiver requests: device-compliance-change and session-revoked

What "not compliant" means

Every device that checks in with XFA gets a compliance state for your organization:

  • Not compliant: at least one device check is failing with a block outcome under a policy that is attached to at least one of your applications. The same checks, settings and plan features that would block the device at sign-in decide here, so a device is not compliant exactly when a sign-in through XFA would be blocked on it.
  • Compliant: everything else, including failing checks that only warn, checks the device has no data for yet, and policies that are not attached to any application.

Affiliation, multi-factor authentication, skipping a check and whether the XFA client is installed are part of the sign-in flow, not of the device checks. They never make a device not compliant. Devices that are only discovered, skipped or run an unsupported operating system have no compliance state and never send an event.

When XFA sends an event

XFA only sends an event when the state of a device changes: from compliant to not compliant, or back. A device that stays in its state sends nothing. The state is evaluated:

  • at every check-in of the XFA client, so a change on the device reaches your identity provider within minutes, and
  • once an hour for every device of your organization, which catches changes that happen without a check-in: a policy edit, a new operating system release that makes a version outdated, or a change of plan.

Turning Shared Signals on sends events only for the devices that are not compliant at that moment.

What leaves XFA

An event names the user by email, the device by its XFA device identifier, the previous and current state, the time of the evaluation and the names of the failing checks (for example disk_encryption or chrome.up_to_date). No other device data is sent.

Data processing

With Shared Signals, facts about the security posture of your users' devices leave XFA and are processed by your identity provider under its own terms. Check that your data processing agreements with XFA and with the identity provider cover this before you turn it on.

What a revoked session does and does not do

For Google Workspace and Microsoft Entra ID the outcome of a non-compliant device is a revoked session: the user is signed out of the identity provider and has to sign in again.

A revoked session only keeps the device out when that next sign-in goes through XFA. If the user signs in to the identity provider without an XFA device check in the flow, they are back in on the same device. Make sure the sign-in is enforced by XFA for the users you cover:

Okta decides itself what a device-compliance-change event does, from re-evaluating the session to signing the user out, based on your Okta policies.

The Shared Signals page

Open Device security > Shared Signals in the XFA dashboard. The page has two parts:

  • Transmitter: the Transmitter URL, the Well-known configuration URL and the JWKS URL of XFA, each with a copy button. A receiver needs one of these to trust XFA's events.
  • Connections: one connection per receiver that should get events. Add connection asks for a Name and the Receiver (Okta, Google Workspace, Microsoft Entra or Other). What happens next depends on the receiver, as each guide explains:
    • Okta asks for your Okta org URL, and XFA creates the stream to your Okta org itself. There is no token.
    • Microsoft Entra sends you to Microsoft with Continue to Microsoft, where a Microsoft Entra administrator grants consent and signs in once more to confirm the tenant. XFA adds the connection and its stream when you return. There is no token.
    • Google Workspace and Other return a token, shown once, that the receiver uses to create its own stream with XFA. Rotate token issues a new one and stops the old one at once.

Each connection lists its streams with their status, the time and result of the last delivery, Send test event, and Pause or Resume. A connection can be renamed with Rename and deleted with Remove, which also deletes its streams. Setup guide opens the matching page of these docs.

The Okta, Google Workspace and Microsoft tiles on the Integrations page also show a Shared Signals action that counts the connections for that provider and opens this page.

Organization administrators make changes on the page; read-only users can see the connections and their status.

Other receivers

Any receiver that implements the Shared Signals Framework with push delivery can connect to XFA:

  1. On the Shared Signals page, click Add connection, enter a name, choose Other (any SSF receiver) as the Receiver and click Add connection.
  2. Copy the token from the dialog. It is shown once.
  3. In the receiver, add XFA as a transmitter with the Well-known configuration URL (https://ssf.xfa.tech/.well-known/ssf-configuration) and the token as the bearer token.
  4. The receiver creates its stream with XFA. It appears under the connection; use Send test event to check the delivery.

XFA sends the CAEP device-compliance-change and session-revoked events that the stream requests, and the SSF verification event. A stream covers every user of your organization by default; the receiver can exclude users from its side.