Se rendre au contenu

Security & Compliance

Lynx Compliance - Jira Connector

Pulls compliance evidence from Atlassian Jira Cloud - project + user inventory, recently-resolved issues (change management), open critical issues, audit log - via the Jira REST API v3.

Talk to sales See pricing

lynx_compliance_connector_jira · v19.0.1.0.0 · Premium

What this solves

Lynx Compliance - Jira Connector

Compliance evidence from Atlassian Jira Cloud. Jira is the canonical source-of-truth for change management at most software shops, so this connector targets the change-management + open-incident audit questions auditors examine first:

  • Issues resolved recently (CSF PR.PS-02, ISO A.8.32): every issue moved to Done in the trailing 90 days, with assignee, priority, status changes. The four-eyes-principle / change-review evidence for SOC 2.

  • Open critical issues (CSF RS.MA-01, ISO A.5.24): unresolved Highest-priority issues — a hot-list that should always have an owner.

  • Audit log (CSF DE.CM-01, ISO A.8.16): admin / governance actions, member lifecycle, permission scheme changes.

Authentication is Basic auth using a tenant user's email + an API token from id.atlassian.com. Treat the token as a bearer credential.

Key Features

  • Jira connector type - Basic auth via JSON {"email": "...", "api_token": "..."} in credential_secret + Atlassian site (e.g. acme.atlassian.net) in config_json.site.

  • Five resource pulls - projects, users, recently-resolved issues, unresolved critical issues, audit log.

  • Pre-seeded collectors - five collectors covering ID.AM-04 (project inventory), PR.AA-01 (user inventory), PR.PS-02 (change management), RS.MA-01 (open critical issues), DE.CM-01 (audit log).

  • JQL filters configurable - pre-seeded queries are sane defaults; customers can edit per their workflow (e.g. swap "status = Done" for "status in (Closed, Resolved, Done)").

Integrates With

  • lynx_compliance_connectors - registers under the connector framework.

  • lynx_compliance_evidence_collectors - shipped collectors use the standard schedule.

  • Atlassian Jira Cloud REST API v3 via the requests HTTP client.

Depends on

base lynx_compliance lynx_license_enforcer lynx_base lynx_compliance_evidence_collectors lynx_compliance_connectors lynx_compliance_certification

Try Lynx Compliance - Jira Connector on your team.

Free trial, no credit card. Talk to sales when you're ready.

Start free trial Browse all modules