Connect Jira

Before you start

You need the Jira Cloud admin rights described below, and in Trusterio the right to manage integrations (owners and admins have it). Anybody else sees the page read-only.

Connect it

1. Open Automation and choose Connect on the Jira Cloud card. (The link opens the dialog straight away.)
2. Give it a name under What to call it, and read What to grant: every permission and what it is for.
3. Press Add it and enter the credential. You land on the connection’s own page.

Jira checks nothing. It is where your remediation tasks go: you send a task from Findings, Trusterio creates the issue, and reads back when it is done. So a Jira connection has no tests or findings of its own.

In Jira

1. Use a dedicated Atlassian user that may Browse projects and Create issues in one project, and nothing else.
2. Signed in as that user, open the API tokens page directly: id.atlassian.com on its own sends an organisation admin to admin.atlassian.com. Press Create API token, not the one “with scopes”. An organisation ID and API key from admin.atlassian.com do not work here: they manage the organisation, and Jira does not accept them. If the page says you may not create tokens, an organisation admin can allow them in admin.atlassian.com.
3. A token lasts at most a year. Note when it expires, and save a new one before then.

In Trusterio

Fill in the Jira site URL (https://yoursite.atlassian.net; Jira Cloud only), the Project key, the Issue type (Task unless you say otherwise), the Account email and the API token. Press Save credentials Trusterio then asks Jira, without creating anything, whether that account may see the project and create issues of that type in it, and the connection says what it found. It asks again at every sync.

What it writes, and when

• Only when somebody asks. On Findings, open a finding and press Add a task; the task then has Send to with the name of your Jira connection.
• That creates one issue in your project, with the task’s title and description. No evidence and no file goes with it.
• The issue’s key appears beside the task, as a link.
• Trusterio never edits, moves or deletes an issue.

What it reads back

Each reading looks at the project’s issues updated in the last two weeks. An issue that is done closes its task, never the finding: the finding closes when a later reading of your systems shows it fixed. Until then the task is listed as Done, and not yet proven.

After it is connected

• Press Sync now for the first reading. The Tests tab shows each check: what it should be, what was found, and what is affected.
• New connections are read by hand until you choose a schedule: in Monitoring, on the Collection tab, pick Every hour, Every 6 hours, Daily or Weekly.
• The page says when it was last read and its health; Sync History keeps every run.

A connection marked Beta on the Automation screen has not been tried on a real account yet: its permission list is our reading of the provider’s documentation. AWS, Azure, Google Cloud and Jira have been. If a permission is wrong, tell us.

Disconnect

On the connection’s page, choose Disconnect. Reading stops and its credentials are deleted; its history, checks and evidence stay. Then remove what you created at the provider:

• Revoke the API token, and remove the service account from the project.