> For the complete documentation index, see [llms.txt](https://academy.shade.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.shade.inc/help-center/security/shade-siem-documentation.md).

# SIEM integration

Integrating Shade with external security providers for comprehensive documentation and auditing

### Overview

Security Information and Event Management (SIEM) systems aggregate and analyze security logs from across an organization's infrastructure to detect threats and maintain compliance. Shade provides comprehensive logging capabilities that can be integrated with your organization's SIEM platform for enterprise-level customers.

### Log Export Capabilities

Once audit logging is enabled for your workspace, there are two ways to bring Shade activity logs into your SIEM solution:

* **Audit Log Streaming**: stream audit log events continuously to your SIEM or another supported destination. Set this up in **Settings > Enterprise > Audit Log Streaming**.
* **CSV export**: export logs from the Enterprise portal (**Settings > Enterprise > View Audit Logs**) and import them into your SIEM platform for centralized security monitoring and analysis.

For audit logging support, please contact the Shade team and we would be more than happy to assist setting it up for your workspace.

### Available Log Types

#### Audit Logs

Comprehensive tracking of user activities within your workspace, including:

* File and folder operations (create, modify, delete, share)
* Permission and access changes
* User management actions
* Workspace configuration changes

Each audit log entry includes the actor, action, affected resources, timestamp, and IP address.

For more information on audit logging, please refer here [Audit logging](https://academy.shade.inc/help-center/security/audit-logging.md)

#### Security Events

Monitoring and logging of security-relevant events, including:

* Access attempts (successful and denied)
* Authentication events
* Permission violations
* Unusual activity patterns

#### System Logs

Infrastructure and application-level logging covering:

* Network activity and traffic patterns
* System performance and health metrics
* Automated alerts and notifications
* DDoS protection events

### Log Protection & Retention

* All logs are protected against tampering and unauthorized access
* Logs are retained according to our data management policy and your enterprise agreement
* Automated alerting is configured for critical security events
* Regular access reviews are conducted and documented

### Integration Process

1. **Enable audit logging** for your workspace (contact your account representative)
2. **Stream logs to your SIEM** from **Settings > Enterprise > Audit Log Streaming**, or:
   * **Access the Enterprise portal** to view and export logs
   * **Export logs as CSV** for the desired time period
   * **Import into your SIEM** following your platform's ingestion procedures

### Monitoring & Alerting

Shade maintains real-time monitoring through integrated tools including Datadog and PagerDuty, which can be easily integrated into your workspace. While these internal monitoring systems provide immediate incident response for our infrastructure, the exported audit logs allow your security team to incorporate Shade activity into your organization's broader security monitoring strategy.

For questions about SIEM integration or to enable audit logging, please contact your account manager or enterprise support.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://academy.shade.inc/help-center/security/shade-siem-documentation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
