@devries-cameron20 / composio Mirror · read-only / commits / 8749cd034
Fork 0

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

Mirrored from https://github.com/Camo67/composio.git

Synced Nov 21, 04:45 UTC

docs: surface security and compliance review guidance

Brendan O'Leary committed Nov 13, 2026 at 14:35 UTC 8749cd03472ef970985772d80d0d192da86cb774
5 files changed +66 -39
docs/content/docs/meta.json
+10 -3
@@ -35,8 +35,15 @@
35 "sessions-vs-direct-execution",
36 "tools-direct",
37 "auth-configuration",
38 - "---Migration and security---",
39 - "migration-guide",
40 - "security"
38 + "---Security and Compliance---",
39 + "security/overview",
40 + "[Vendor security review](/kb/guide/platform-compliance-data-handling)",
41 + "security/token-custody",
42 + "security/data-retention",
43 + "security/zero-data-retention",
44 + "security/audit-logs",
45 + "security/outbound-ips",
46 + "---Migration---",
47 + "migration-guide"
48 ]
49 }
docs/content/docs/security/overview.mdx
+14 -24
@@ -1,42 +1,32 @@
1 ---
2 -title: Security
3 -description: How Composio secures your data, credentials, and tool execution, and where to find our compliance reports.
2 +title: Security overview
3 +description: Start a security and compliance review of Composio with links to data handling, credential architecture, controls, and review evidence.
4 keywords: [security, compliance, SOC 2, trust center, encryption, isolation]
5 ---
6
7 -Composio is built with security at its core. We use least-privilege defaults, isolate every organization and project, encrypt credentials, and give you controls over what we store.
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.
8
9 ## Compliance and the Trust Center
10
11 -Composio is SOC 2 Type II compliant. For our latest reports and certifications (the SOC 2 Type II report, our sub-processor list, and more), visit the [Composio Trust Center](https://trust.composio.dev).
12 -
13 -## Isolation and access control
14 -
15 -- Organizations and projects isolate your resources. Data from one project is not visible to another.
16 -- API keys are scoped, support per-key IP allowlisting, and can opt in to capabilities such as Proxy Execute at creation.
17 -- Scoped project API keys separate **Session management** (creating, viewing, configuring, and deleting sessions) from **Session tool execution** (search, tool execution, proxy execution, and session-linked MCP access). See [API key permissions](/reference/authenticating-to-composio/project-api-key-permissions) to configure access.
18 -- Multi-factor authentication (MFA) is available for Dashboard sign-in and can be enforced by an organization admin.
19 -- Organization admins can see who changed members, projects, API keys, and other settings in [audit logs](/docs/security/audit-logs).
11 +Start with the [Composio Trust Center](https://trust.composio.dev) for current compliance reports and the subprocessor list. Read the [vendor-review guidance](/kb/guide/platform-compliance-data-handling) for data-processing terms, model-training requirements, and enterprise reviews.
12
13 ## Credential protection
14
23 -See [Token custody architecture](/docs/security/token-custody) for credential boundaries, server-side execution, default API redaction, and deployment options.
15 +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.
16 +
17 +## Isolation and access control
18
25 -- Connected-account credentials, auth configs, and API keys are encrypted at rest using AES-256-GCM, and all traffic is encrypted in transit using TLS.
26 -- Connected-account tokens are redacted by default in API responses, for both Composio-managed and custom auth configs. To act on a provider directly, use [Proxy Execute](/docs/extending-sessions/proxy-execute).
27 -- Webhook deliveries are signed; verify the `webhook-signature` header when handling trigger events. For custom OAuth webhook setup, see [Custom OAuth webhooks](/docs/setting-up-triggers/custom-oauth-webhooks).
19 +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.
20
21 ## Your responsibilities
22
31 -Composio executes the tools and connections you configure. You control which toolkits are enabled, which accounts are connected, and what your agents are allowed to do. Review the access you grant, and treat connected-account scopes as you would any production credential.
23 +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.
24
33 -## Reporting a vulnerability
25 +## Related resources
26
35 -To report a security issue, contact `security@composio.dev`. Please do not disclose vulnerabilities publicly until we have addressed them.
27 +- Read [data retention and handling](/docs/security/data-retention) to map logs, files, model processing, and downstream providers.
28 +- 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.
29
37 -## Related resources
30 +## Reporting a vulnerability
31
39 -- [Data retention and handling](/docs/security/data-retention): what we store and for how long, on every plan.
40 -- [Zero Data Retention](/docs/security/zero-data-retention): how to stop storing call payloads, and what ZDR covers.
41 -- [Outbound IP addresses](/docs/security/outbound-ips): the addresses to allowlist for services that only accept trusted IPs.
42 -- [Composio Trust Center](https://trust.composio.dev): security certifications and compliance.
32 +Report vulnerabilities privately to [security@composio.dev](mailto:security@composio.dev).
docs/lib/home-navigation.ts
+16 -1
@@ -244,7 +244,22 @@ export const DOCS_PRODUCTS = {
244 { type: 'page', url: '/docs/production-readiness' },
245 { type: 'page', url: '/docs/authentication/white-labeling-authentication' },
246 { type: 'folder', path: 'poc-to-prod' },
247 - { type: 'folder', path: 'security', label: 'Security and data' },
247 + ],
248 + },
249 + {
250 + label: 'Security and Compliance',
251 + items: [
252 + { type: 'page', url: '/docs/security/overview' },
253 + {
254 + type: 'link',
255 + url: '/kb/guide/platform-compliance-data-handling',
256 + label: 'Vendor security review',
257 + },
258 + { type: 'page', url: '/docs/security/token-custody' },
259 + { type: 'page', url: '/docs/security/data-retention' },
260 + { type: 'page', url: '/docs/security/zero-data-retention' },
261 + { type: 'page', url: '/docs/security/audit-logs' },
262 + { type: 'page', url: '/docs/security/outbound-ips' },
263 ],
264 },
265 {
docs/tests/static/navigation.test.ts
+3 -2
@@ -61,7 +61,8 @@ describe("Navigation - meta.json validity", () => {
61 "---Governance---",
62 "---Guides---",
63 "---Direct execution (legacy)---",
64 - "---Migration and security---",
64 + "---Security and Compliance---",
65 + "---Migration---",
66 ]);
67
68 expect(pages.slice(1, pages.indexOf("---Core concepts---"))).toEqual([
@@ -89,7 +90,7 @@ describe("Navigation - meta.json validity", () => {
90 expect(
91 pages.slice(
92 pages.indexOf("---Direct execution (legacy)---") + 1,
92 - pages.indexOf("---Migration and security---")
93 + pages.indexOf("---Security and Compliance---")
94 )
95 ).toEqual([
96 "sessions-vs-direct-execution",
docs/tests/static/product-navigation.test.ts
+23 -9
@@ -11,7 +11,7 @@ import {
11 shouldAnimateDocsProductSwitch,
12 } from '../../lib/home-navigation';
13 import { buildProductPageTree, pageTreeUrls } from '../../lib/product-page-tree';
14 -import { referenceSource, source } from '../../lib/source';
14 +import { knowledgeBaseSource, referenceSource, source } from '../../lib/source';
15
16 describe('Docs product navigation', () => {
17 test('defines the product labels, descriptions, landings, and themes once', () => {
@@ -175,24 +175,38 @@ describe('Docs product navigation', () => {
175
176 const securityUrls = [
177 '/docs/security/overview',
178 - '/docs/security/audit-logs',
178 + '/kb/guide/platform-compliance-data-handling',
179 '/docs/security/token-custody',
180 - '/docs/security/outbound-ips',
180 '/docs/security/data-retention',
181 '/docs/security/zero-data-retention',
182 + '/docs/security/audit-logs',
183 + '/docs/security/outbound-ips',
184 ];
184 - const security = platformTree.children.flatMap(node =>
185 - node.type === 'folder' ? [node, ...node.children] : [node],
186 - ).find(node => node.type === 'folder' && node.name === 'Security and data');
187 - expect(security?.type).toBe('folder');
188 - if (security?.type !== 'folder') throw new Error('Security and data folder missing');
189 - expect(security.children.flatMap(node => node.type === 'page' ? [node.url] : [])).toEqual(
185 + const securityStart = platformTree.children.findIndex(
186 + node => node.type === 'separator' && node.name === 'Security and Compliance',
187 + );
188 + expect(securityStart).toBeGreaterThan(-1);
189 + const securityPages = platformTree.children.slice(
190 + securityStart + 1,
191 + platformTree.children.findIndex(
192 + (node, index) => index > securityStart && node.type === 'separator',
193 + ),
194 + );
195 + expect(securityPages.map(node => node.type === 'page' ? node.url : null)).toEqual(
196 securityUrls,
197 );
198 for (const url of securityUrls) {
199 expect(platformUrls.filter(candidate => candidate === url)).toHaveLength(1);
200 expect(forYouUrls).not.toContain(url);
201 }
202 + expect(knowledgeBaseSource.getPage(['guide', 'platform-compliance-data-handling'])?.url).toBe(
203 + '/kb/guide/platform-compliance-data-handling',
204 + );
205 + const governance = platformTree.children.find(
206 + node => node.type === 'folder' && node.name === 'Governance',
207 + );
208 + expect(governance?.type).toBe('folder');
209 + expect(securityPages).not.toContain(governance);
210
211 const readiness = platformTree.children.flatMap(node =>
212 node.type === 'folder' ? [node, ...node.children] : [node],