Findings and deadlines

​

One queue

Each connected tool reports problems in its own way. Tierity maps them onto one scale (critical, high, medium, low) so a critical from Wiz and a critical from Okta mean the same thing, and puts them in one list on the Workbench. Every finding links back to the tool that raised it.

​

How findings stay current

Integrations re-sync on a schedule. On each sync:

• New problems become new findings. Re-syncing never creates duplicates.
• When the tool reports a problem fixed, its finding is resolved automatically.
• If a resolved problem comes back, the finding reopens.
• Findings you’ve marked as accepted risk or a false positive are left as you set them.

​

Deadlines (SLA policies)

Set how many days your team has to fix each severity in Config → Admin → SLA Policies (Admin role). The defaults are 7 days for critical, 14 for high, 30 for medium and 90 for low. Each finding’s due date is counted from when it was first seen, and findings close to their deadline are marked at risk. Overdue findings are flagged on the Workbench and counted in the SLA figures on your dashboards, so you can see at a glance what’s late and whether the team is keeping up.

​

Tickets

Open a finding and choose Create Issue to send it to Linear or Jira. The ticket includes the finding’s title, severity, details and a link back to Tierity, and its due date carries through from the deadline. Linear ticket status syncs back to Tierity, so you can see which findings are being worked on.

​

Asking the assistant

The AI assistant can read your findings. Ask it what’s overdue, what to fix first, or how to remediate a specific finding.