Skip to content

Shared Signals

Overview

The (SSF) lets systems exchange security events, such as “this user’s session was revoked” or “this user’s account was disabled”, as they happen. Britive can receive events and act on the affected user, and it can send its own events to other systems.

Events use the and event types. Each event is sent as a signed .

Shared Signals is configured in Admin → Security → Shared Signals, which has three tabs. The guides in this section follow the same layout.

Console tabWhat it configuresDirection
TransmittersExternal systems, such as an identity provider, that send events to Britive. Britive runs a Britive action on the user for each event.Inbound
ReceiversExternal systems, such as a SIEM, that Britive sends its own events toOutbound
EventsEvents Britive accepted or sent, with the resultBoth

The tab names describe the external system’s role: a sends events and a receives them. To receive events in Britive, add a transmitter. To send events from Britive, add a receiver.

Permissions

ConsoleAPIPermissionBuilt-in roles
View the Transmitters, Receivers, and Events tabsGET /api/ssf/admin/..., GET /api/ssf/resultssecurityadmin.security.view, securityadmin.security.listTenantAdminRole, SecurityAdminRole, TenantAuditorRole, SecurityViewRole
Add, change, or delete transmitters, receivers, and their mappingsPOST, PATCH, PUT, DELETE /api/ssf/admin/...securityadmin.security.manageTenantAdminRole, SecurityAdminRole

Guides

Reference

Standards:

Last updated on