MIT Network Audit docs
Configuration

Change audit settings

6 min read Odoo 18.0

This page shows you the settings of MIT Network Audit, what each one changes, and how forensic body capture is set up and protected.

Who this is for: Odoo administrators. Forensic body capture is for users in the Network Forensic Officer group. You need: an Odoo administrator account for Settings and Egress Components. The module works without any change to these settings.

Before you begin

  1. Install the module and check that it records traffic.
  2. Decide why you want to change a setting. The defaults record everything that the module can capture, with the normal level of detail.
  3. After each change, open the Audit Log and check the effect. Some settings apply only in part of your system. See the warning below.

Open the settings

  1. Click Network Audit ▸ Configuration ▸ Settings. The same block is in the Odoo Settings app under Network Audit.
  2. Change a value and click Save.

The Network Audit block in Odoo Settings with four settings The Network Audit block in Settings.

Which settings apply where

Network auditing enabled and Disabled channels are applied to the Odoo process that handles your Save. We found no code that applies the saved values to the other Odoo worker processes, or again after a restart. In a system with several workers, or after a restart, the audit may keep recording as before. After you change either setting, open the Audit Log over some time and check whether new rows still appear. If they do, restart Odoo and check again. Strict redaction is applied in the saving process at once and in other processes when they load the database. Audit retention (days) is read by the daily job.

The settings

Setting What it does Default
Network auditing enabled Master switch. When off in a process, that process records no new rows. On
Strict redaction New rows keep no URL path, no query parameter names and no fingerprint. They keep the host, IP address, port, sizes, time, status and the module. Off
Audit retention (days) The daily retention job deletes rows older than this number of days. 0 keeps everything. 365
Disabled channels Comma-separated channel names that are not recorded, for example socket,smtp. Empty means all channels. Empty

What you should see: after you save, the Audit Log gets new rows (or stops getting rows, if you switched something off), as described in the warning above.

Network auditing enabled

Leave it on unless you have a reason. While auditing is off in a process, that process records nothing. The rows that exist stay. The time without rows is a gap in the log, and the log does not mark it.

Strict redaction

Standard auditing stores the URL path and the names of query parameters. Strict redaction removes them from new rows. Rows that exist already are not changed. Headers are not changed by this setting. Sensitive header values are masked in both modes. See Understand a recorded event.

Audit retention (days)

The retention job runs once a day. It does not delete any row at or after the position of the latest signed head, so the signed head keeps its meaning. A short retention period therefore still keeps the rows from the last signing onward. Before the first daily signing there is no signed head, so this protection does not apply yet. See Verify the log and export evidence.

Disabled channels

Channels are the ways the module captures calls. Their names are requests, urllib (the standard-library HTTP client), httpx, smtp, imap, pop3, ssl, socket and http_inbound (inbound HTTP requests). If you disable a channel, calls made through it are not recorded, unless another channel records them. The exact channel names are listed in the log line interceptor installed (channels: …). See Install MIT Network Audit.

Egress Components: what counts as MIT-bound

  1. Click Network Audit ▸ Configuration ▸ Egress Components.
  2. Read the list. Each entry has host patterns, module names and a channel, and the flags MIT-bound and License only.

The Egress Components list with the known destinations and their MIT-bound flag The Egress Components list.

When the module saves a row, it takes the first matching entry. Specific host and module rules win over channel rules. If nothing matches, the row is third-party. Only entries with MIT-bound switched on count as MIT-bound.

The list decides what the report shows

The seeded licence-server entry matches the host patterns *license*, *mit-odoo* and *metzler*, and the licence module. A MIT host that matches none of these shows as third-party. A host of yours that matches one of them shows as MIT-bound. Administrators can edit, add and delete entries. Changes apply to new rows. Old rows keep the classification they had when they were saved.

Forensic body capture

Forensic body capture can store request and response bodies. Use it only for a legal or incident need.

Bodies are stored as they are

A captured body can contain personal data, passwords or message content. Bodies are stored in your Odoo database without redaction. Only users in the Network Forensic Officer group can read them. Keep that group small, and switch capture off when the case is closed.

How it is protected

  • It is off by default.
  • It has its own group, Network Forensic Officer. Odoo administrators are not in this group automatically. A user in this group can also read the normal audit.
  • The list of modules is an allowlist. If it is empty, nothing is captured, even when capture is on.
  • Each body is cut off at the maximum size (default 64 KB).
  • Bodies are deleted after the body retention period (default 30 days). It cannot be longer than the retention of the normal log.
  • Turning capture on or off, changing the allowlist, and reading a body are written to the audit log.

Turn it on

  1. Sign in as a user in the Network Forensic Officer group.
  2. Click Network Audit ▸ Forensic Capture ▸ Capture Settings.
  3. Fill in Allowlist addons with the technical names of the modules, for example maildesk_mail_client. Add a reference to your approval in Consent reference.
  4. Check Body retention days and Max body bytes, switch Enabled on and save.

What you should see: the banner on the Trust Report changes to Forensic body capture is ACTIVE and lists the modules.

Read captured bodies

  1. Click Network Audit ▸ Forensic Capture ▸ Captured Bodies.
  2. Open a record and click View decoded body.

Users who are only in the Network Audit group see the number of captured bodies on an event, but cannot open them.

If it does not work

Symptom Check Safe next step
A setting seems to have no effect. Look at the Audit Log over some time. Restart Odoo and check again.
Configuration is missing in the menu. Your user is not an Odoo administrator. Ask an administrator.
Capture is on, but Captured Bodies is empty. The allowlist may be empty, or the module made no matching call. Check the allowlist and make a test call from a listed module.
You cannot find Forensic Capture. Your user is not in the Network Forensic Officer group. An administrator can add you to the group. See Security and capture limits. Decide first whether you should hold this role.

Next step

Security and capture limits.

Related: Understand the Trust Report.