MIT Network Audit docs
The Trust Report

Understand the Trust Report

5 min read Odoo 18.0

This page explains each part of the Trust Report, so you know what a number or a chip tells you and what it does not.

Who this is for: administrators and security officers who read the report. You need: a user in the Network Audit group (Odoo administrators are in it automatically). The report shows metadata only. It never shows message bodies.

Before you begin

  1. Install the module and let it record traffic.
  2. Open Network Audit ▸ Trust Report and click Refresh.
  3. Remember that the report reads a summary table. It is as current as your last Refresh or the last run of the daily summary job.

The hero verdict card with the trust chips below it The verdict card and the trust chips are at the top of the report.

The header buttons

Button What it does
Refresh Rebuilds the summary table for the last few days from the Audit Log, then redraws the report. It records nothing new.
Verify chain Recomputes the hash chain of the stored Audit Log. A short notification says Audit chain verified OK — no tampering detected. or names the first row that does not match. Read it before it fades. The same check is in the Action menu of the Audit Log. See Verify the log and export evidence.
Export signed proof Downloads a signed JSON file for the whole log at once. To export only a date range or the last N days, use Network Audit ▸ Export Signed Audit instead.
Audit Log Opens the list of all recorded connections.

The status banner

The banner under the header tells you whether forensic body capture is on:

  • Forensic body capture is OFF — only metadata is recorded. This is the default.
  • Forensic body capture is ACTIVE. The banner lists the modules whose bodies are captured, the retention in days and the number of stored bodies.

The banner does not show whether the interceptor is installed. To check that, see Install MIT Network Audit.

The verdict card

The card shows one of three states. The state comes from a fixed rule on the summarised data:

Verdict Rule
all-clear No self-egress rows, and the MIT-bound traffic stays below the attention thresholds.
attention There are MIT-bound events, and either they transfer more than 64 KiB in total, or there are at least 100 events in total and more than 10 percent of them are MIT-bound.
alarm The log contains at least one outbound row attributed to MIT Network Audit itself (self-egress).

The thresholds are fixed in the report. You cannot change them. See What the report verdict means for what to do in each case.

The verdict is a simple rule, not a proof

The verdict compares counts and sizes. It does not read content, and it does not check that the log is intact. The card text can sound stronger than the evidence. Treat it as a pointer to the destination panels, not as a guarantee.

The trust chips

The chips sit under the verdict card.

Chip What it tells you
Append-only log The log model refuses edits and deletes in Odoo, apart from the retention job. A database trigger blocks changes to sealed rows, and blocks deletes unless the retention job allows them. A person with full control of the database could still get around the delete guard.
Hash-chained Each row's hash includes the hash of the row before it. The number is the position (seq) of the latest row. The chip does not run the check. Click Verify chain for that.
Bodies OFF (or Bodies captured) Forensic body capture is off (or on). In normal auditing the log has no field for bodies.
Self-egress 0 The number of outbound rows ever attributed to MIT Network Audit itself, among the rows still in the log. It should be 0. The attribution code skips this module's own frames, so a call made by the module itself may not be counted here. Treat 0 as a useful signal, not as proof.

The summary cards and charts

The three summary cards: Total events, MIT-bound events, Third-party events The summary cards count the events in the summary table.

  • Total events is the number of recorded events.
  • MIT-bound events counts events whose destination or module matches an entry in Egress Components. The card also shows how many bytes they transferred.
  • Third-party events counts all other events.

A destination counts as MIT-bound only if it matches the Egress Components list. A destination that is missing from the list is shown as third-party, even if it belongs to MIT. Administrators can edit the list. See Change audit settings.

The traffic distribution donut next to the bytes transferred bars Left: the share of events by side. Right: the request and response bytes by side.

The Traffic distribution donut shows the share of events. The Volume · bytes transferred bars show the request and response sizes for each side. A few large transfers can hide behind a small event count, so look at both. The sizes tell you how much data moved. They do not tell you what it was.

The destination panels

The MIT-bound and third-party destination panels side by side The two destination panels.

The MIT-bound destinations and Third-party destinations panels list host, module (Addon), events and request and response sizes. Click a row to open the Audit Log filtered to that host. Open a single row to read its recorded event.

What the report cannot tell you

Limits

  • The report covers only what the module captured. See Security and capture limits.
  • It is not a firewall. It does not block traffic.
  • A clean report does not prove that no connection to MIT exists outside what the module records.

If it does not work

  • The report is empty: click Refresh, and check the installation.
  • A host you expected is missing: check whether the channel is disabled in Settings, or whether the connection is one of the kinds that are not captured.
  • A MIT host shows as third-party: add it to Egress Components (administrators only).

Next step

What the report verdict means.