Webhooks

EasyPSK can push events to an external system over webhooks, so that activity in a context can be forwarded to a SIEM, a log-management platform, or a custom endpoint. This is the supported way to stream EasyPSK activity into an organization’s own tooling.

What is emitted

EasyPSK emits configuration-audit events: each administrative change inside the context (for example creating, renaming, or removing a Wireless Personal Network, rotating a key, or changing a self-service user) is published as an event recording what changed, who changed it, and when. Secrets such as keys are redacted in the payload.

Delivery

• Destination: an HTTPS endpoint that the organization controls.
• Mode: events can be delivered in real time, or batched and delivered on an interval.
• Security: a secret token can be attached so the receiver can verify that a delivery came from the platform.
• Resilience: if the receiving endpoint does not accept a delivery, the platform retries with an increasing back-off before marking the delivery failed, and recent delivery history is retained for inspection.

Monitoring

The Administration Portal shows the configured webhooks, the events pending delivery, and a history of recent deliveries with their outcome, so an administrator can confirm that events are reaching the destination.

Related sections

• Audit Log: the record of administrative configuration changes.
• Logging, Reporting, and Retention: the platform-wide logging and event model.