--- title: "How to set up activity log forwarding in NordLayer" slug: "how-to-forward-activity-logs-to-siem" updated: 2026-11-18T14:11:14Z published: 2026-11-18T14:11:14Z canonical: "help.nordlayer.com/how-to-forward-activity-logs-to-siem" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.nordlayer.com/llms.txt > Use this file to discover all available pages before exploring further. # How to set up activity log forwarding in NordLayer Activity log forwarding integration lets you send NordLayer security and audit data to your Security Information and Event Management (SIEM) tool. With all your logs in one place, it's easier to meet compliance requirements, spot threats, and investigate incidents. NordLayer sends its security and audit telemetry to the third-party SIEM you choose. You set up the integration yourself in the Control Panel, with no developer or support involvement needed. ## What logs are collected and sent Connection logs record who connected, from where, and for how long: - Initiator ID, email, name, and IP address - Device name and ID - Connection ID - Server IP and country - Gateway name - Organization ID - Connected and disconnected timestamps Action logs record audit events and configuration changes in your organization: - Initiator ID, email, name, and IP address - Organization ID - Event type and version - Event data - Time the event occurred NordLayer collects logs into batches and sends them to your SIEM every 5 minutes through AWS Firehose. Expect a short delay between an event happening and it showing up in your SIEM. If a delivery fails, NordLayer tries again automatically. If failures continue, your data is stored safely, and our team is alerted so the problem can be fixed. ## How to set up SIEM integration 1. Log in to the **NordLayer Control Panel**. 2. Go to **Integrations** and toggle on **Activity log forwarding**. 3. Pick your SIEM vendor from the list. Supported vendors include Splunk, Coralogix, Datadog, Dynatrace, Elastic, Honeycomb and others. 4. Fill in the vendor-specific fields, such as: - **HTTP endpoint URL:** the endpoint where your SIEM receives data - **Authentication:** the credential NordLayer uses to authenticate - **Content encoding:** how the logs are formatted when sent 5. Click **Finish setup**, then activate the integration. Note After you save, a message will tell you that setup is in progress. Provisioning the delivery stream can take a few minutes, and logs won't flow until it's done. ### Check if the integration works 1. Go to the **Activity Log** in the Control Panel. 2. Look for an event saying **SIEM integration enabled for [Vendor Name]**. This event appears only once the integration is fully active. 3. Wait at least 5 minutes, then check your SIEM for incoming NordLayer logs. ## Destination setup ### Amazon S3 Before you enable the integration, you must allow NordLayer to write to your S3 bucket. #### 1. Check the bucket settings In the AWS Management Console, go to S3 and open your bucket (using a separate bucket for NordLayer logs only is recommended). - In the **Permissions** tab, set **Object Ownership** to **Bucket owner enforced**. - In the **Properties** tab, check **Default encryption**: - **SSE-S3:** No additional setup needed. Skip Step 3. - **SSE-KMS with your own KMS key:** Complete all steps. - **SSE-KMS with the AWS managed key (`aws/s3`):** Change the encryption to SSE-S3 or your own KMS key (this key can't be shared with other AWS accounts). - Copy the bucket Amazon Resource Name (ARN) from the **Properties** tab (`arn:aws:s3:::your-bucket-name`). #### 2. Add a bucket policy In the **Permissions** tab, find **Bucket policy** and click **Edit**. Paste the policy below and replace `your-bucket-name` with the name of your bucket. (If your bucket already has a policy, add only the statement to the existing list). Click **Save changes**. ``` { "Version": "2012-10-17", "Statement": [ { "Sid": "AllowNordLayerLogDelivery", "Effect": "Allow", "Principal": { "AWS": "arn:aws:iam::992382702163:root" }, "Action": [ "s3:GetBucketLocation", "s3:ListBucket", "s3:ListBucketMultipartUploads", "s3:AbortMultipartUpload", "s3:GetObject", "s3:PutObject", "s3:PutObjectAcl" ], "Resource": [ "arn:aws:s3:::your-bucket-name", "arn:aws:s3:::your-bucket-name/*" ], "Condition": { "ArnLike": { "aws:PrincipalArn": "arn:aws:iam::992382702163:role/nl-siem-cfn-production-*-firehose-role" } } } ] } ``` #### 3. Update the KMS key policy *(Only if your bucket uses SSE-KMS with your own key)* In the AWS Console, go to KMS and open the key your bucket uses. In the **Key policy** tab, click **Edit** and add the statement below. Click **Save changes**. Copy the key ARN (`arn:aws:kms:<region>:<account-id>:key/<key-id>`). ``` { "Sid": "AllowNordLayerLogDelivery", "Effect": "Allow", "Principal": { "AWS": "arn:aws:iam::992382702163:root" }, "Action": [ "kms:GenerateDataKey", "kms:Decrypt", "kms:Encrypt" ], "Resource": "*", "Condition": { "ArnLike": { "aws:PrincipalArn": "arn:aws:iam::992382702163:role/nl-siem-cfn-production-*-firehose-role" } } } ``` #### 4. Enable the integration in NordLayer Follow the general setup steps above, select **Amazon S3**, and fill in: - **S3 bucket ARN:** The bucket ARN from Step 1. - **S3 bucket KMS key ARN:** The key ARN from Step 3 (leave empty if using SSE-S3). #### 5. Check the files in your bucket New files usually appear within 1-2 minutes after new activity. They are GZIP-compressed files with events in JSON format, stored in: ``` //data//// ``` Troubleshooting If no files appear, verify your bucket policy name and KMS key ARN. Logs that can't be delivered to your bucket are not stored anywhere else. ### Amazon OpenSearch Service Your domain must have public access, and fine-grained access control must be turned off. 1. In the AWS Console, go to Amazon OpenSearch Service and open your domain. Copy the **Domain endpoint** and **Domain ARN**. 2. In the **Security configuration** tab, click **Edit** and add this statement to the access policy (replace the `Resource` value with your domain ARN, keeping `/*` at the end): ``` { "Sid": "AllowNordLayerLogDelivery", "Effect": "Allow", "Principal": { "AWS": "arn:aws:iam::992382702163:root" }, "Action": [ "es:ESHttpGet", "es:ESHttpPost", "es:ESHttpPut" ], "Resource": "*", "Condition": { "ArnLike": { "aws:PrincipalArn": "arn:aws:iam::992382702163:role/nl-siem-cfn-production-*-firehose-role" } } } ``` 1. In the NordLayer Control Panel, select **Amazon OpenSearch Service** and enter the domain endpoint, domain ARN, and an index name (e.g., `nordlayer-activity`). NordLayer creates a new index every day. ### Coralogix 1. In Coralogix, go to **Data Flow → API Keys** and create a **Send-Your-Data** API key. 2. In the NordLayer Control Panel, select **Coralogix**: - **HTTP endpoint URL:** Select the endpoint for your Coralogix region (e.g., `eu2`). - **Private key:** Paste the API key. Logs appear in **Explore → Logs** with the application name NordLayer. ### CrowdStrike Falcon Next-Gen SIEM 1. In the Falcon console, go to **Next-Gen SIEM → Data onboarding → Data connections**. 2. Find **Nord Security NordLayer Data Connector**, click **Configure**, and create the connection. 3. Click **Generate API key** and copy the API URL and the API key. 4. In the NordLayer Control Panel, select **CrowdStrike**: - **Ingest URL:** Paste the API URL. - **API token:** Paste the API key. Logs appear in **Investigate → Advanced Search**. ### Datadog 1. In Datadog, go to **Organization Settings → API Keys** and copy an API key (don't use an application key). 2. In the NordLayer Control Panel, select **Datadog**: - **HTTP endpoint URL:** Select the endpoint for your Datadog site (e.g., [https://aws-kinesis-http-intake.logs.datadoghq.eu/v1/input](https://aws-kinesis-http-intake.logs.datadoghq.eu/v1/input)). - **API key:** Paste the API key. Logs appear in **Logs → Log Explorer**. ### Dynatrace 1. In Dynatrace, search for **Access Tokens** and generate a new token with the **Ingest logs** scope. Copy it immediately. 2. In the NordLayer Control Panel, select **Dynatrace**: - **API URL:** `https://<environment-id>.live.dynatrace.com/api/v2/logs/ingest/aws_firehose` - **API token:** Paste the token. Logs appear in the **Logs** app. ### Elastic *(Note: This works with Elastic Cloud. Self-managed Elasticsearch isn't supported.)* 1. In Kibana, go to **Integrations** and open **Amazon Data Firehose**. In the **Settings** tab, click **Install Amazon Data Firehose assets**. Do the same for the AWS integration. 2. Open **Connection details** from the help menu. Copy the **Elasticsearch endpoint** and create an API key in the **Encoded** format. 3. In the NordLayer Control Panel, select **Elastic**: - **Elastic endpoint URL:** Paste the Elasticsearch endpoint. - **API key:** Paste the API key. Logs appear in **Discover**, in the `logs-awsfirehose-default` data stream. ### Honeycomb 1. In Honeycomb, go to **Manage Environments → API Keys** and create an **Ingest** key. 2. In the NordLayer Control Panel, select **Honeycomb**: - **HTTP endpoint URL:** `https://api.honeycomb.io/1/kinesis_events/<dataset-name>`. For an EU account, use `api.eu1.honeycomb.io`. - **API key:** Paste the ingest key. Honeycomb creates the dataset when the first logs arrive. ### HTTP Endpoint Use this option to send logs to your own HTTPS endpoint. It must: - Use HTTPS on port 443. - Accept POST requests with a JSON body that has `requestId`, `timestamp` and `records` (Base64-encoded). - Reply with status 200 and a JSON body echoing the `requestId` and `timestamp`. In the NordLayer Control Panel, select **HTTP Endpoint**: - **HTTP endpoint URL:** Enter your endpoint URL. - **Access key:** Optional. NordLayer sends it in the `X-Amz-Firehose-Access-Key` header. ### MongoDB Atlas MongoDB Atlas receives logs via a deployed receiver app in your AWS account. AWS charges for API Gateway and Lambda apply. 1. In MongoDB Atlas, copy your cluster connection string (**Connect → Drivers**). In **Network Access**, ensure the receiver can connect. 2. In AWS, deploy **MongoDB-Firehose-Ingestion-App**. Enter your connection string, database name, and collection name. 3. Add the `ApiKeyValue` to the Authorizer function and turn off API key required in API Gateway. 4. Copy the **WebEndpoint** URL and the API key value. 5. In the NordLayer Control Panel, select **MongoDB Atlas**: - **API Gateway URL:** Paste the WebEndpoint URL. - **API key:** Paste the API key value (not its ID). ### New Relic 1. In New Relic, go to **API Keys** and create a key with the **Ingest - License** type. 2. In the NordLayer Control Panel, select **New Relic**: - **HTTP endpoint URL:** Select the US or EU endpoint. - **API key:** Paste the license key. Logs appear in **Logs**. ### Snowflake NordLayer writes logs into a Snowflake table and signs in with a key pair. 1. On your computer, create a key pair: ``` openssl genrsa 2048 | openssl pkcs8 -topk8 -inform PEM -out rsa_key.p8 -nocrypt openssl rsa -in rsa_key.p8 -pubout -out rsa_key.pub ``` 1. In Snowflake, run the script below as `ACCOUNTADMIN`. You can change the names, but keep the column name `CONTENT`. Paste the public key from `rsa_key.pub` without the BEGIN and END lines. ``` CREATE DATABASE NORDLAYER_SIEM; CREATE SCHEMA NORDLAYER_SIEM.LOGS; CREATE TABLE NORDLAYER_SIEM.LOGS.ACTIVITY_LOGS (CONTENT VARIANT); CREATE ROLE NORDLAYER_ROLE; GRANT USAGE ON DATABASE NORDLAYER_SIEM TO ROLE NORDLAYER_ROLE; GRANT USAGE ON SCHEMA NORDLAYER_SIEM.LOGS TO ROLE NORDLAYER_ROLE; GRANT INSERT, SELECT ON TABLE NORDLAYER_SIEM.LOGS.ACTIVITY_LOGS TO ROLE NORDLAYER_ROLE; CREATE USER NORDLAYER_USER TYPE = SERVICE DEFAULT_ROLE = NORDLAYER_ROLE RSA_PUBLIC_KEY = ''; GRANT ROLE NORDLAYER_ROLE TO USER NORDLAYER_USER; ``` 1. In the NordLayer Control Panel, select **Snowflake**: - **Snowflake account URL:** `https://<organization>-<account>.snowflakecomputing.com` - **User login:** `NORDLAYER_USER` - **Private key:** The content of `rsa_key.p8` on a single line, without the BEGIN and END lines. - **Passphrase:** Leave this empty unless your private key is encrypted. - **Snowflake database, Snowflake schema, Snowflake table:** `NORDLAYER_SIEM`, `LOGS`, `ACTIVITY_LOGS` Each log appears as one row in the `CONTENT` column. ### Splunk 1. In Splunk, go to **Settings → Data inputs → HTTP Event Collector → New Token**. Turn on **Enable indexer acknowledgement** and copy the **Token Value**. 2. In the NordLayer Control Panel, select **Splunk**: - **Splunk cluster endpoint:** Your HEC URL (e.g., `https://splunk.example.com`). - **Authentication token:** Paste the Token Value. Logs appear in **Search & Reporting**. ### Sumo Logic You need the **Manage Collectors** permission in Sumo Logic. 1. In Sumo Logic, go to **Data Management → Data Collection → Collection**. 2. Click **Add Collector → Hosted Collector** and save it. 3. Click **Add Source → AWS Kinesis Firehose for Logs**. You can also set a Source Category (e.g., `nordlayer/activity-logs`). Save the source and copy the **HTTP Source Address**. 4. In the NordLayer Control Panel, select **Sumo Logic**: - **HTTP Source Address:** Paste the address. Logs appear in **Log Search**. For example, search for `_sourceCategory=nordlayer/activity-logs`. ## Rules and limitations - **One integration per organization.** You can have only one active SIEM integration at a time. - **Settings can't be edited.** To change the vendor, endpoint, or credentials, disable the current integration and create a new one. - **It turns off automatically if your subscription is inactive.** If your subscription stays inactive for 10 days, the integration is disabled and its delivery resources are removed. Once your subscription is active again, you'll need to set up the integration again. - **Available on all plans.** Any NordLayer plan can use SIEM integration, as long as the subscription is active. - **Changes are logged.** Enabling or disabling the integration is recorded in the Activity Log. --- **Note**: In case you have any questions or issues, press '**Chat with support**' at the bottom of the page.