Jira

Teddy connects to Jira with a scoped service account to link compliance work to the tickets your teams already use.

What Teddy does

• Links remediation tasks to Jira issues
• Pulls change and incident tickets as evidence
• Shows the status of remediation in Teddy

Frameworks and controls

• ISO 27001:2022: A.8.32 Change management, A.5.24 to A.5.26 incident management, A.8.8 Management of technical vulnerabilities
• SOC 2: CC8.1 change management, CC7.4 incident response
• NIS2: Article 21(2)(b) incident handling and 21(2)(e) vulnerability handling

How it works

1. You approve the permission list and choose the projects Teddy may read.
2. Gaps from a gap audit become Jira issues in the project you choose.
3. Teddy follows the status and collects closed change and incident tickets as evidence.

Access

You approve the permission list before anything is connected.

Will Teddy create tickets on its own?

Only in the projects you allow, and only for remediation tasks. Every ticket Teddy creates is labelled and logged.