Customer Responsibility Matrix
Which security controls Aikido handles for you and which ones your team is responsible for.
A Customer Responsibility Matrix (CRM) explains which security controls Aikido handles for you and which ones your team is responsible for.
| Area | Aikido | You (the customer) |
|---|---|---|
| Login | Aikido accepts your single sign-on (SSO) and never stores passwords. | You run the identity provider: multi-factor authentication (MFA), passwords, Personal Identity Verification (PIV) and Common Access Card (CAC), and who is allowed to sign in. |
| Users in Aikido | Aikido enforces the roles you assign. | You invite people, pick their role, review access, and remove them when they leave. |
| What Aikido scans | Aikido runs the scans and shows findings. | You connect GitHub, cloud accounts, and domains, and choose what is in scope. |
| Your cloud and code | Aikido assumes a least-privilege role that you install. | You deploy that role, keep it scoped, and secure those accounts. |
| Findings | Aikido detects, prioritizes, and alerts. | You fix issues in your systems, or ignore or snooze them with intent. |
| Exporting data | Aikido controls who can export data and delivers it over HTTPS. | Once data leaves Aikido (reports, APIs, notifications), you protect and retain it. |
| API and integrations | Aikido authenticates tokens and rate-limits the API. | You create, store, and rotate API tokens and webhook URLs. |
| Devices and sessions | Aikido times out idle sessions after 15 minutes. | You lock and protect the laptops and browsers used to open Aikido. |
| The platform | Aikido runs, encrypts, backs up, and isolates the SaaS in AWS GovCloud. | You use the Aikido app. |