Skip to content

Integrations

Integrations connect Devici to the tools your teams already use to plan, build, and deliver software.

By integrating threat modeling into existing workflows, Devici helps ensure security considerations remain visible and actionable throughout the development lifecycle.

What Integrations Enable

Integrations allow you to:

  • Send workflow tasks to external systems
  • Track threat modeling work alongside delivery tasks
  • Reduce context switching between tools
  • Embed threat modeling into existing processes

Integrations are commonly used with workflows, but can also support reporting and operational visibility.

Supported Integrations

Devici currently supports integrations with:

  • Jira
  • Azure DevOps
  • Devici REST API
  • Code Genius

Each integration is configured independently and may require administrative permissions.

How Integrations Work with Devici

Most integrations are used in combination with:

  • Collections to group threat models
  • Workflows to trigger actions
  • Workflow Actions to create external tasks

For example, when a workflow is configured with a Jira or Azure DevOps output, Devici automatically creates and updates tickets as threat modeling tasks progress.

Permissions and Setup

Integration setup typically requires:

  • Administrative access in Devici
  • Appropriate permissions in the external system
  • Configuration of credentials or tokens

Refer to the individual integration guides for detailed setup instructions.

When to Use Integrations

Use integrations when you want to:

  • Align threat modeling tasks with delivery work
  • Track security reviews in Jira or Azure DevOps
  • Automate follow-up actions from threat modeling
  • Extend Devici functionality through the API

Integrations help move threat modeling from a standalone activity into a shared engineering workflow.