MIT Network Audit docs
Questions and terms

Common questions

5 min read Odoo 18.0

Short answers about MIT Network Audit, with links to the pages that explain them. The answers are checked against the Odoo 18 copy of the module.

Does it slow Odoo down?

We do not know. The effect on speed has not been measured, so this documentation makes no claim about it. The module does a small amount of work per captured call: it reads the call stack, builds a metadata event and puts it in a buffer. The Trust Report reads a summary table, not every row.

If load matters to you, test the module on a copy of your system first. You can reduce the work with Disabled channels or the Network auditing enabled switch. Read the warning about which processes these settings reach in Change audit settings.

Can it break my email or my network calls?

It is designed not to. The module catches errors inside capture, attribution, redaction and saving, so that they do not stop the call that is being observed. The code is open, and you can read it. This has not been proven for every possible fault.

The usual result of a fault is a missing row in the log. See What the audit log can and cannot show.

Does it store my email contents, documents or AI prompts?

Not in normal auditing. The log has no field for request or response bodies. It stores metadata:

  • destination host, URL path and the names of query parameters;
  • addresses, ports, sizes, times and status;
  • the module that made the call;
  • request and response headers. The values of sensitive headers (for example Authorization and Cookie) are masked. Other header values are stored;
  • a salted fingerprint of the method, host and path. It is not a fingerprint of the content.

Be aware that a token that is part of a URL path, or in a header with an unusual name, is stored. Strict redaction removes the path and the query names.

Forensic body capture is the exception

An optional forensic body capture can store request and response bodies, without redaction. It is off by default, needs an allowlist of modules, and only users in the Network Forensic Officer group can use it. Changes to its settings and each reading of a body are logged. See Change audit settings.

Can the log be changed or deleted?

The module blocks it in normal use and makes changes visible afterwards:

  • The log model refuses edits and deletes in Odoo, except for the retention job. A database trigger blocks changes to sealed rows and gates deletes.
  • Each row's hash includes the previous row's hash. Verify chain recomputes them and names the first row that does not match.
  • A daily signed head records how far the chain had reached, so that cut-off newest rows can be detected with the standalone verifier and the key.

There are limits. A person with full control of the database can lift the delete gate or rebuild the chain, and the signing key is stored in the same database. The export's enrichment block is not covered by the chain. See Verify the log and export evidence.

Does an intact log mean that every connection was recorded?

No. The integrity check only covers the rows that are in the log. Some traffic is not captured at all, for example WebSocket connections, connections to the same machine and traffic from other processes. See Security and capture limits.

What counts as MIT-bound?

A call is MIT-bound if its host or its module matches an entry that has MIT-bound switched on in Network Audit ▸ Configuration ▸ Egress Components. The seeded licence-server entry matches the host patterns *license*, *mit-odoo* and *metzler* and the licence module. Other seeded entries cover Odoo services and mail channels. Everything else is third-party. A MIT host that is not on the list shows as third-party, and administrators can edit the list. See Understand the Trust Report.

Do I have to configure anything?

No. After installation the module records traffic with its defaults. The settings are Network auditing enabled, Strict redaction, Audit retention (days) (default 365, 0 keeps everything) and Disabled channels. For full coverage on your own server, add the module to server_wide_modules. See Install MIT Network Audit.

Is it open source?

Yes. The module is not obfuscated, and the project's build checks that no obfuscation tool has touched it. You can read the code before you install it. This does not check the copy that you run. MIT's commercial modules, such as MailDesk, are obfuscated.

Does it work on Odoo.sh and on Odoo 17 or 19?

On Odoo.sh you can install it from Apps. If you cannot add the module to server_wide_modules in your hosting, each process installs the interceptor when its registry loads, and traffic before that is not recorded.

This documentation is written and checked against Odoo 18 only. Copies of the module for Odoo 17 and 19 exist but differ from it. Do not assume that they behave the same way.

What is self-egress?

Self-egress means an outbound call attributed to MIT Network Audit itself. The module is designed to make none, and the Trust Report turns to alarm if it counts one. The code that names the responsible module skips the module's own frames, so a quiet Self-egress chip is a weak signal. See What the report verdict means.

How long are rows kept?

For the number of days in Audit retention (days). The default is 365. 0 keeps everything. A daily job deletes older rows, but never at or after the latest signed head. Until the first head has been signed, this protection does not exist yet. See Change audit settings.

Does it block traffic?

No. It records and reports. It is not a firewall and not a sandbox. To block traffic, use your network controls.

Where do I start?

Install MIT Network Audit, then Read your first report.