Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
docs: give security review personas direct resource tables
Brendan O'Leary committed
Nov 13, 2026 at 15:23 UTC
999974d581c54f02501f5dd07c7a35be670ce60d
1 file changed
+27
-18
docs/content/docs/security/overview.mdx
+27
-18
@@ -4,37 +4,46 @@ description: Start a security and compliance review of Composio with links to da
4
keywords: [security, compliance, SOC 2, trust center, encryption, isolation]
5
---
6
7
-Composio stores credentials and executes tool calls on your behalf. Use this guide to review the data your application sends, the controls you need, and the evidence for your vendor assessment.
7
+Composio stores credentials and executes tool calls on your behalf. Start with the resources for your role.
8
9
-## Start your review
9
+<span id="start-your-review" className="block scroll-m-28" />
10
11
-<Cards>
12
- <Card title="I'm evaluating Composio" href="/docs/security/overview#compliance-and-the-trust-center" description="Find compliance reports, agreements, and data-handling guidance for your vendor review." />
13
- <Card title="I'm building with Composio" href="/docs/security/overview#credential-protection" description="Review credential custody, access permissions, and retention controls for your application." />
14
-</Cards>
11
+## I'm evaluating Composio
12
16
-## Compliance and the Trust Center
13
+Gather the evidence and data-handling terms you need for a vendor security review.
14
18
-Start with the [Composio Trust Center](https://trust.composio.dev) for current compliance reports and the [subprocessor register](https://trust.composio.dev/subprocessors). Review the [Data Processing Addendum](https://composio.dev/legal/dpa) and [Business Associate Agreement](https://composio.dev/legal/baa) for the terms that apply to your workload.
15
+<span id="compliance-and-the-trust-center" className="block scroll-m-28" />
16
+<span id="related-resources" className="block scroll-m-28" />
17
20
-Read the [vendor-review guidance](/kb/guide/platform-compliance-data-handling) for data-processing terms, model-training requirements, and enterprise reviews.
18
+| Review area | Where to go |
19
+| --- | --- |
20
+| Compliance reports and certifications | [Composio Trust Center](https://trust.composio.dev) |
21
+| Downstream providers | [Subprocessor register](https://trust.composio.dev/subprocessors) |
22
+| Data-processing agreements | [Data Processing Addendum](https://composio.dev/legal/dpa) and [Business Associate Agreement](https://composio.dev/legal/baa) |
23
+| Logs, files, model processing, and retention | [Data retention and handling](/docs/security/data-retention) |
24
+| Vendor-review requirements | [Compliance and vendor-review guidance](/kb/guide/platform-compliance-data-handling) |
25
22
-## Credential protection
26
+## I'm building with Composio
27
24
-Provider credentials are encrypted at rest using AES-256-GCM, and traffic uses TLS. Review [token custody architecture](/docs/security/token-custody) for how Composio stores and uses credentials, what API redaction covers, and which [deployment options](/docs/security/token-custody#deployment-options) meet your custody requirements.
28
+Review the controls for your application's credentials, permissions, and retained data.
29
26
-## Isolation and access control
30
+<span id="isolation-and-access-control" className="block scroll-m-28" />
31
28
-Check [API-key permissions](/reference/authenticating-to-composio/project-api-key-permissions) and [provider scopes](/docs/authentication/controlling-scopes) against the operations your application needs. Use [audit logs](/docs/security/audit-logs) to review administrative changes and [outbound IP addresses](/docs/security/outbound-ips) to configure network allowlists.
32
+| Review area | Where to go |
33
+| --- | --- |
34
+| Credential custody and deployment options | [Token custody architecture](/docs/security/token-custody) |
35
+| Permissions for your application | [API-key permissions](/reference/authenticating-to-composio/project-api-key-permissions) and [provider scopes](/docs/authentication/controlling-scopes) |
36
+| Payload storage, coverage, and exclusions | [Zero Data Retention](/docs/security/zero-data-retention) |
37
+| Administrative changes | [Audit logs](/docs/security/audit-logs) |
38
+| Network allowlists | [Outbound IP addresses](/docs/security/outbound-ips) |
39
30
-## Your responsibilities
40
+### Credential protection
41
32
-You authenticate your users and decide which accounts and tools they can access. Review those choices alongside your application's own logs and model-provider policies.
42
+Provider credentials are encrypted at rest using AES-256-GCM, and traffic uses TLS. Composio uses credentials during execution. ZDR controls storage of covered payloads, not processing during execution.
43
34
-## Related resources
44
+### Your responsibilities
45
36
-- Read [data retention and handling](/docs/security/data-retention) to map logs, files, model processing, and downstream providers.
37
-- Review [Zero Data Retention](/docs/security/zero-data-retention) before enabling it. Check coverage and exclusions against your workload. ZDR controls storage of covered payloads, not processing during execution.
46
+You authenticate your users and decide which accounts and tools they can access. Review those choices alongside your application's own logs and model-provider policies.
47
48
## Reporting a vulnerability
49