- Domain category blocking triggered
App banner
Blocked URL visited
Browser extension blocked or enabled
Clipboard blocking
Cloned login page detected
Custom detection
File download blocking
File upload blocking
Malicious browser extension detected
Malicious copy and paste detected
MFA enforcement event
Password logging prevention
Phishing tool detected
Protected password entered
Stolen credentials detected
Strong password enforcement event
SSO password used
Domain category blocking...
Security
X-Signature
A domain category blocking rule was triggered for an employee.
The unique identifier for the event. Use this as an idempotency key.
Example:"c478966c-f927-411c-b919-179832d3d50c"
The unique identifier of the tenant the event belongs to.
Example:"4f9d2e7a-1b3c-4d5e-8f6a-7c8b9d0e1f2a"
When the event occurred, formatted as a UNIX timestamp (in seconds).
Example:1698604061
The description of the event. Note: this is subject to change and should not be used to match on this object.
Example:"employee@example.com was blocked from casino.example.com"
The friendly name of this object. Note: this is subject to change and should not be used to match on this object.
Example:"Domain category blocking"
POST
curl -i -X POST \
https://api.pushsecurity.com/domain-category-blocking-event \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Content-Type: application/json' \
-H 'X-Signature: X-Signature: t=1492774577,v1=5257a869...' \
-d '{}'