What the report verdict means
This page explains the three verdicts on the Trust Report, how the report reaches each one, and what to do next.
Who this is for: administrators and security officers who read the report. You need: a user in the Network Audit group, and the module recording traffic.
Before you begin
- Open Network Audit ▸ Trust Report and click Refresh, so that the verdict uses current data.
- Know how the report is built. See Understand the Trust Report.
- Know the limits: the verdict covers only recorded traffic. See Security and capture limits.
How the verdict is decided
The report applies a fixed rule to the summary data. It does not read the content of any connection.
- If the log contains one or more outbound rows attributed to MIT Network Audit itself, the verdict is alarm.
- Otherwise, if there are MIT-bound events and either they transfer more than 64 KiB in total, or the log has at least 100 events and more than 10 percent of them are MIT-bound, the verdict is attention.
- Otherwise the verdict is all-clear.
A destination is MIT-bound when it matches an entry in the Egress Components list, by host pattern or by the module that made the call. The seeded list contains a licence-server entry that matches host patterns such as *license*, *mit-odoo* and *metzler*, and the licence module itself. Administrators can change the list. If a MIT host is not on it, the report shows that host as third-party.
The Trust Report with an all-clear verdict.
What a verdict does not say
The verdict does not run Verify chain. The card text can sound reassuring, for example "No customer data is leaving to MIT." The rule behind it only compares the counts and sizes of recorded MIT-bound traffic with fixed limits. It cannot know what was sent, and it does not see traffic that the module does not capture.
All-clear
What it means: in the summary data there is no self-egress, and MIT-bound traffic is small or absent.
What to do: nothing is required. To look closer:
- Open the MIT-bound destinations panel and check that the hosts are the ones you expect and the sizes are small.
- Click Verify chain. What you should see: Audit chain verified OK — no tampering detected.
- If you need a record for someone else, use Export signed proof. See Verify the log and export evidence.
Attention
What it means: MIT-bound traffic is above the report's limits. The report text suggests that this may be expected after a module update or remote diagnostics. The report does not know the reason.
What to do:
- Open the MIT-bound destinations panel and find the host and module that cause the numbers. Click a row to open the matching rows in the Audit Log.
- Open one row. Read the module (Addon), the author, the call site, the sizes and the time. See Understand a recorded event.
- Decide whether the traffic fits something you know, for example an update or a licence check. The log shows sizes, not content, so it cannot show you what was sent.
- If you cannot explain it, click Verify chain, then export a signed proof for the time window and keep it. Contact MIT with the file.
Start with the MIT-bound destinations panel when you review an attention verdict.
Alarm
What it means: the log contains at least one outbound row attributed to MIT Network Audit itself. The module is designed to make no outbound calls of its own, so this is unexpected. The Self-egress chip shows the count. The count covers all rows still in the log, not only the current period. The verdict stays at alarm until those rows are removed by the retention job.
The report cannot tell you the cause. A modified build is one possibility.
Why a quiet Self-egress chip is weak evidence
The code that names the responsible module skips frames that belong to MIT Network Audit itself. A call made by this module can therefore show up with a blank Addon, or under the next module further up the call stack, instead of under mit_network_audit. A Self-egress value of 0 is useful, but it is not proof that the module made no calls. Also look at rows with a blank Addon in the Audit Log.
What to do, in this order:
- Click Verify chain. If it names a broken row, note the number.
- Open Network Audit ▸ Audit Log, filter on the module mit_network_audit, and open the rows. Read the host, the call site and the time.
- Export a signed proof for the affected time window. See Verify the log and export evidence.
- Report it to your security contact and to MIT, and send the exported file.
The three verdicts at a glance
| Verdict | Rule | First action |
|---|---|---|
| all-clear | No self-egress. MIT-bound traffic below the limits. | None. Optionally click Verify chain. |
| attention | MIT-bound events above 64 KiB, or at least 100 events with more than 10 percent MIT-bound. | Review the MIT-bound destinations panel and the rows behind it. |
| alarm | One or more self-egress rows. | Click Verify chain, inspect the rows, export, escalate. |
If it does not work
- The verdict does not change after new traffic: click Refresh. The report reads a summary table.
- A MIT host shows as third-party: the host is not on the Egress Components list. Ask an administrator to check the list.
- You see an alarm after you changed the module: the rows stay until the retention job removes them. Check their time stamps.
Next step
Inspect recorded network activity.
Related: Verify the log and export evidence.