Skip to main content

Aikido

Written by Brady Price

Connecting the Integration

Aikido is a security platform that helps teams identify and remediate vulnerabilities across both code and cloud infrastructure. Integrating Aikido with Secureframe enables you to automate the evaluation process and evidence collection required by compliance frameworks.

Prerequisite (Aikido plan, not Secureframe): Connecting this integration requires a paid Aikido subscription on the Aikido side. A free Aikido plan is not sufficient. This is an Aikido product requirement, not a Secureframe subscription or Secureframe plan limitation. See Aikido’s Secureframe integration page for Aikido’s plan details.

Navigate to Integrations, locate Aikido on the Available Integrations page, and click Connect.
​(If your plan includes the Custom Integration feature, select Add native connection instead.)

Follow the form steps and connect the integration.

Once connected, the Aikido integration appears on your Integrations page, where you can manage it using the following actions:

  • Check the connection status

  • Run a sync

  • Rename the connection

  • Archive the connection

  • Reconnect

Does connecting Aikido require a paid Aikido subscription?

  • Yes. You need a paid Aikido subscription with Aikido. A free Aikido plan will not work for this connection.

  • This is gated by Aikido, not by Secureframe. Your Secureframe plan does not control whether Aikido allows the integration.

  • Confirm your Aikido plan with Aikido before you start the connection in Secureframe.

If I ignore or suppress a finding in Aikido, what happens in Secureframe?

  1. Findings ignored in Aikido show as Closed in Secureframe after the next sync.

  2. The Ignored status is only used for findings ignored directly in Secureframe, where you add a reason and justification.

  3. Aikido doesn’t send a reason with ignored findings, so manual and automatic ignores are handled the same way.

  4. If you remove the ignore in Aikido, the finding goes back to Open after the next sync.

Did this answer your question?