MIT Network Audit docs
Security

Security and capture limits

4 min read Odoo 18.0

This page lists what MIT Network Audit does not capture, who can see what, and how forensic body capture is controlled.

Who this is for: security officers and Odoo administrators. You need: an Odoo administrator account to assign groups. The statements are checked against the Odoo 18 copy of the module.

Before you begin

  1. Read the limits below before you rely on a report or an export.
  2. Decide who needs to read the audit, and who (if anyone) should hold the Network Forensic Officer role.
  3. Know your own setup: which Odoo version, own server or Odoo.sh, and how many worker processes.

Capture limits

The module records what it can observe

Not captured:

  • WebSocket upgrades (for example the real-time bus). They pass straight through.
  • Connections to the same machine: 127.0.0.1, ::1, localhost and unix sockets. This includes PostgreSQL on the same host.
  • Traffic from other processes: shell scripts, external cron jobs and subprocesses that do not run inside an Odoo process.
  • Anything while the Network auditing enabled switch or the channel is off.
  • Calls made before the interceptor is installed in a process. Without server_wide_modules (for example on Odoo.sh when you cannot set it), this includes the start of each process.
  • Events that are dropped when the buffer (5,000 events per process) is full, while a module install or upgrade runs, and in test mode.

Also remember:

  • The module does not block anything. It is not a firewall.
  • If installation fails, auditing stays off and only a log warning tells you.
  • A person with full control of the server or the database can stop the module, change settings, or rebuild the log. The hash chain and the signed head make some of these actions visible. They do not prevent them.
  • A MIT host that is not on the Egress Components list appears as third-party.

A report or an export that passes its checks therefore means: "the recorded rows are consistent". It does not mean: "nothing else happened".

Who can see what

Group Can do Cannot do
Network Audit Read the Trust Report, Traffic Summary, Audit Log and Egress Components. Run Verify chain. Download exports. See how many bodies exist for an event. Read captured bodies. Change settings.
Odoo administrators (Settings) Everything in Network Audit (implied), plus Configuration: settings and editing Egress Components. Read captured bodies, unless also in the officer group.
Network Forensic Officer Everything in Network Audit, plus Forensic Capture: configure body capture and read captured bodies. (This is the most sensitive role.)

Both groups are in a hidden category, so the normal user form may not list them. To assign one, turn on developer mode, open Settings ▸ Technical ▸ Security ▸ Groups, open the group (Network Audit or Network Forensic Officer) and add the user. Administrators are not in the officer group automatically.

What an administrator can change

An Odoo administrator can edit the Egress Components list, and so change what the report calls MIT-bound. Changes apply to new rows. Old rows keep their flag.

What the normal log stores

The normal log stores metadata: destination, URL path, names of query parameters, addresses and ports, sizes, times, the module that made the call, and header names. The values of sensitive headers are masked. Other header values and the full URL path are stored as they are, so a token that sits in a path or in an unusual header can end up in the log. Strict redaction removes the path and the query names. It does not change header handling. See Change audit settings.

The log has no field for message bodies.

Forensic body capture

Forensic body capture is the one feature that stores bodies.

  • Off by default. An officer must switch it on.
  • Allowlist. It captures only for the modules on the allowlist. An empty list captures nothing.
  • Size and age limits. Bodies are cut off at a maximum size (default 64 KB) and deleted after a retention period (default 30 days, at most the retention of the normal log).
  • Officer only. Only users in the Network Forensic Officer group can configure it and read bodies.
  • Logged. Changes to the settings and each reading of a body are written to the audit log.
  • Stored as received. Bodies are not redacted. They can contain passwords or personal data.

Treat captured bodies as the most sensitive data in your database

Keep the officer group small. Switch capture off when the case is closed. Remember that backups of the database contain the bodies too.

Append-only protection

In Odoo, the log model refuses edits and deletes, even for sudo. The retention job is the exception. A database trigger blocks changes to the hashed and chain fields of sealed rows, and blocks deletes unless the retention job sets a session flag.

That flag can be set by anyone who controls the database session, so the trigger is not protection against such a person. The hash chain and the signed head show some changes afterwards. The signing key is stored in the same database. See Verify the log and export evidence.

If it does not work

  • A user cannot see the Network Audit menu: add the user to the Network Audit group.
  • You cannot find Forensic Capture: the user is not in the Network Forensic Officer group.
  • You need to know whether a specific connection is captured: check it against the list above, then test on a copy of your system.

Next step

What the audit log can and cannot show.

Related: Change audit settings.