Integration finding details
Every check on an integration’s Findings tab opens its own page. Select the check’s name in the table. Microsoft 365 checks run through Maester and have their own pages; see Microsoft 365 (Maester).
The page has five tabs.
Overview
Section titled “Overview”The result Keel recorded on the latest collection, when it ran, what the check looks at, the controls a passing result counts as evidence for, and how many items need attention.
Affected items
Section titled “Affected items”The repositories, projects, branches, merge requests, users, admins or policies behind the result, with failures listed first. Each row shows:
| Column | Meaning |
|---|---|
| Item | The repository, user or policy. Links open the item in the vendor’s console where Keel has a link for it. |
| Status | Fail, Warn, N/A or Pass for that item alone. |
| Detail | Why that item got its status. |
| Belongs to | The project or repository a branch or merge request sits in. |
A check that reports one result for the whole account, such as AWS’s root account checks, shows no items. For every other check, items appear after the next collection runs. Keel stores up to 500 items per check, failures first.
How to fix
Section titled “How to fix”Keel’s own steps for the setting behind the check, with a link to the vendor’s documentation. Steps name the vendor’s menus as they read when the steps were written; if a vendor has renamed a menu, the linked documentation has the current path.
Explain with AI tailors those steps to the items that failed. It costs AI credits (shown on the button) and the credits are refunded if the explanation fails. Keel sends the check, the written steps and the names of up to 25 failing items. It never sends links, item details or credentials. The newest explanation stays on the tab with the time it was made. Auditors can read it but cannot run it.
AI drafts can be wrong. Check them against the written steps before changing a setting.
Triage
Section titled “Triage”Set what the workspace has decided about the check. Owners and admins can change it; every change is kept in the Decision log on the same tab, with who made it, when and why.
| State | Use it when | Change alerts | Ends |
|---|---|---|---|
| Open | No decision yet. This is the default. | Sent | |
| Out of scope | The check does not apply to this workspace. | Not sent | When someone reopens it |
| Accepted risk | The workspace knows about the failure and accepts it for now. | Sent | On the review date |
| Muted | The failure is being fixed and the alerts are noise until then. | Not sent | After the muted-until date |
Every state needs a reason of 5 to 500 characters. Accepted risk needs a review date and Muted needs an end date, each after today and within 366 days. When the date passes, the check is Open again and the lapsed decision stays visible on the tab. A muted check still shows its real status everywhere; only the change alerts to chat and webhooks pause.
The State column on the integration’s Findings tab shows each check’s current state.
History
Section titled “History”The check’s status on each of the last 30 collections, newest first, with the runs where the status changed marked.
Each integration has a Scope tab next to Findings. It lists every record the integration reported: projects, repositories, accounts, users, IAM users and policies, with how many of their items fail and whether each is in scope. Microsoft 365 has no Scope tab.
To leave a record out, such as a test repository or a service account:
- Open the integration’s Scope tab.
- Select the record’s name, or its edit icon.
- Enter a reason of 5 to 500 characters and select Mark out of scope.
To change many records at once, tick them on the Scope tab or on a check’s Affected items tab, choose Mark out of scope or Bring back into scope in the bar at the bottom, enter one reason for all of them, and select Apply.
Keel collects again as soon as you save, so check results and your program score update right away. If that collection can’t run, they update on the next one. The record’s items stop counting toward every check that is decided by its items: the check is worked out again from the items still in scope, by the same rule it always uses. For example, if the only member without a reported two-factor status is out of scope, the two-factor check passes. A check passes only when Keel saw everything it needs. If Keel inspected only some of your projects, the best result is Warn. If nothing in scope is left, the check shows N/A. A check decided by a setting, such as an organization’s two-factor requirement or an AWS account password policy, keeps its result. The detail says how many items were left out. The items stay listed on the check’s Affected items tab, so an auditor can see what was excluded.
Accounts on GitHub, Cloudflare and Neon, and people from Microsoft Entra ID and Google Workspace, share their out-of-scope mark with Access reviews. Marking one out of scope in either place applies to both. For those, the account or person must already be synced.
To undo it, open the record and select Bring back in scope. Owners and admins can change scope, and every change is logged.
After you fix something
Section titled “After you fix something”Select Collect now on the integration’s Findings tab, or wait for the daily collection. The check and its items update on that run.