Notion

This guide walks through how to set up Notion audit logs in Scanner Collect, using Notion's Custom SIEM integration to send events directly to Scanner's HTTP receiver.

Prerequisites

Before you begin, make sure you have:

• A Notion Enterprise plan. SIEM connections are only available on Enterprise.
• Workspace owner permissions in Notion. Only workspace owners can add a security & compliance connection.
• Permissions in Scanner to create the integration.

Create a Collect Rule

1

Create a New Source

In the Scanner UI, go to the Collect tab.

• From the Overview page click the '+' icon in the upper right corner
• Select create new Collect Rule
• Choose Notion
• Choose the Log Type notion:audit

2

Configure the Source

• Set a Display Name such as my-org-notion-logs.
• Leave the Payload Format as the default: JSON: Generic.

3

Configure Authentication

• Keep the default Authentication Type: Bearer Token.
• Generate a secure Bearer token. You can use a command like: echo "token_$(uuidgen | tr '[:upper:]' '[:lower:]')" and specify that here (we'll refer to it as BEARER_TOKEN)

4

Configure Destination

• Select the S3 bucket where you want raw logs delivered.
• (Optional) Enter a bucket prefix. The default is fine for most setups.

5

Review and Create

• Review your configuration.

After creation, Scanner will display a unique Endpoint URL like:

https://collect.your-org-and-region.scanner.dev/receiver/v1/http/<id>

6

Configure in Notion

• Log in at app.notion.com as a workspace owner.
• Open the workspace switcher and click Settings.
• Go to the Connections tab and select Custom SIEM integration. You may need to use the search bar, or filter to SIEM, for this option to appear.
• Set the Webhook URL to the endpoint URL provided by Scanner.
• Add a new Webhook Header, and set the Key to Authorization, and the value to Bearer ${BEARER_TOKEN}.

  • Replace ${BEARER_TOKEN} with the actual Bearer token you generated in the Configure Authentication step.
• Click Connect to finish.

Notion begins streaming audit log events to the endpoint immediately.

Once routing is complete, logs will flow from Notion → Scanner HTTP Receiver → S3 → Scanner index.

Create an Index Rule

Logs flow from Notion → Scanner's HTTP receiver → your S3 bucket. Create an Index Rule to have Scanner index those logs for fast search and detections.

Create an Index Rule

Notion Defaults

When you create the Index Rule from the Collect Rule, the following defaults are pre-populated:

• Transformations: Add Metadata, Parse JSON Columns
• Timestamp Field: event.timestamp