Today we released two updates:

1. New Jira Receptor
2. Action Required: New Service Role - requires making a new selection on the Scope Page

New Jira Receptor

The Jira receptor enables adding Jira issues and Jira users as evidence to controls. The Jira issues are selected with Jira filters, which are then matched to controls in Trustero. This enables, for example, automatically importing access request tickets stored in Jira to control IAM02, which needs those tickets as evidence. More details: Jira Receptor.

Configuring the Jira receptor to send issues to control IAM02

Action Required: New Service Role

The previous "Incident Management and Communication" service role was too broad, so we split it into two new categories:

1. Renamed the existing category to "Incident Management and External Communication"
2. Added "Internal Security Event and Incident Management Communication"

This makes it easier to track services used for internal and external communication separately, which improves the recommendations the platform provides. 

As a result of this change, not all services roles will be fulfilled in the platform, which will raise warnings. To fix it, just select the service(s) used for this role on the scope page.

Warnings You Might See in the Platform

Initial scoping page showing service roles not fulfilled warning

Dashboard showing only 20 of 21 service roles fulfilled

Fix by Answering on the Scope page

To fix those issues, just select which services are used on the Scope page