SET
Security Event Token, a specialized token format based on JWT, designed to carry security-related event notifications between systems. It specifies the event encapsulation format, signing mechanism, and URI naming conventions for event types.
Timeline (last 90 days)
Because SET is based on JWT, events are inherently signable and verifiable, making them more secure than bare HTTP callbacks.
RFC 9967 defines a standardized set of event expressions for SCIM provisioning changes, built on top of SET (Security Event Token).
SET (Security Event Token) is defined by RFC 8417 and is essentially a special type of JWT designed specifically for carrying security-related event notifications.
The SET event model reuses the event delivery mechanism from the Shared Signals Framework in the OpenID ecosystem.
Implementors typically maintain a jti (JWT ID) deduplication table for each SET to achieve idempotent processing.
When a system needs to integrate with multiple heterogeneous identity sources, the standardization benefits of adopting the SET event model are relatively pronounced.
If only a single identity source is integrated and the existing Webhook operates stably without security pain points, the cost-benefit ratio of migrating to the SET model may not be worthwhile.
Open-source frameworks such as Gophish and SET (Social Engineering Toolkit) exist that can generate phishing pages with a single click.
All Facts (8)
Because SET is based on JWT, events are inherently signable and verifiable, making them more secure than bare HTTP callbacks.
50%UnverifiedRFC 9967 defines a standardized set of event expressions for SCIM provisioning changes, built on top of SET (Security Event Token).
50%UnverifiedSET (Security Event Token) is defined by RFC 8417 and is essentially a special type of JWT designed specifically for carrying security-related event notifications.
50%UnverifiedThe SET event model reuses the event delivery mechanism from the Shared Signals Framework in the OpenID ecosystem.
50%UnverifiedImplementors typically maintain a jti (JWT ID) deduplication table for each SET to achieve idempotent processing.
50%UnverifiedWhen a system needs to integrate with multiple heterogeneous identity sources, the standardization benefits of adopting the SET event model are relatively pronounced.
50%UnverifiedIf only a single identity source is integrated and the existing Webhook operates stably without security pain points, the cost-benefit ratio of migrating to the SET model may not be worthwhile.
50%UnverifiedOpen-source frameworks such as Gophish and SET (Social Engineering Toolkit) exist that can generate phishing pages with a single click.
50%