MIT Network Audit docs
Getting started

Install MIT Network Audit

4 min read Odoo 18.0

This page shows you how to install the module and how to check that it is recording connections.

Who this is for: the Odoo server administrator. You need: an Odoo administrator account (to install apps), and for your own server also access to the server configuration and permission to restart Odoo. The module depends on the Odoo apps base, web and mail.

Odoo version

These steps are written and checked against Odoo 18. Copies of the module for Odoo 17 and 19 exist but differ. This page does not claim that they behave the same way.

Before you begin

  1. Decide where your Odoo runs: on a server or container you control, or on Odoo.sh. See Choose your path below.
  2. Make sure you can read the Odoo log. You need it to check the installation.
  3. Read the limits of the module. It does not capture all traffic, and coverage depends on how you install it.
  4. Plan one restart of Odoo if you use your own server.

Choose your path

Your Odoo runs on What you do Coverage
Your own server, Docker or Kubernetes Install the app and add mit_network_audit to server_wide_modules. Best. The interceptor installs when each Odoo process starts, before it serves requests.
Odoo.sh, or any hosting where you cannot change server_wide_modules Add the module to your repository and install it from Apps. Partial. Each process installs the interceptor when its registry loads. Traffic before that moment is not recorded.

Install on your own server

  1. Put the mit_network_audit folder in a directory that is on your Odoo addons_path.
  2. Open your Odoo configuration file. Add mit_network_audit to server_wide_modules and keep the entries that are already there. A typical line looks like this:

    ini [options] server_wide_modules = base,web,mit_network_audit

    If you start Odoo from the command line, use --load=base,web,mit_network_audit instead. On Docker or Kubernetes, put the same setting into your container arguments, for example in the command: of your compose file or pod spec. 3. Restart Odoo. 4. Sign in to Odoo as an administrator. Open Apps, click Update Apps List, search for MIT Network Audit and click Activate.

What you should see: the Network Audit menu appears in the top menu bar.

Install on Odoo.sh

  1. Add the mit_network_audit folder to your Odoo.sh repository and push the branch.
  2. Wait until the build finishes.
  3. Open Apps, click Update Apps List, search for MIT Network Audit and click Activate.

What you should see: the Network Audit menu appears in the top menu bar.

Check that capture works

There is no screen in Odoo that shows whether the interceptor is installed. The banner on the Trust Report only shows whether forensic body capture is on or off. Use the Odoo log and the Audit Log instead.

  1. Search the Odoo log for the line mit_network_audit: interceptor installed. Each Odoo process that installs the interceptor writes this line once. It also lists the channels that it wraps.

    What you should see: at least one such line after the last restart or registry load. 2. Use Odoo for a few minutes in a normal way, for example open pages and let a scheduled job or mail sync run. 3. Open Network Audit ▸ Audit Log.

    What you should see: new rows with a recent Logged time. Rows are saved in batches (after 200 events, or at the next event once 30 seconds have passed), so recent rows can appear with a delay. Keep using Odoo and look again. 4. Open Network Audit ▸ Trust Report and click Refresh.

    What you should see: the summary cards show event counts, and destinations appear in the two destination panels. The report reads a summary table, so it stays empty until you click Refresh or the daily job has run.

The Trust Report after installation, with the verdict, summary cards and destination panels filled The Trust Report after some traffic has been recorded and you clicked Refresh.

If it does not work

Symptom Check Safe next step
The log has no interceptor installed line. Look for install failed — auditing OFF or interceptor is OFF warnings. If the installation fails, Odoo keeps running and auditing stays off. Only a log warning tells you. Fix the cause named in the log, then restart Odoo.
The line appears, but the Audit Log is empty. Open Settings and check Network auditing enabled under Network Audit (Network Audit ▸ Configuration ▸ Settings). Check Disabled channels. Switch auditing on, generate some traffic, and look again.
The Trust Report is empty, but the Audit Log has rows. The report reads a summary table. Click Refresh.
Only some traffic appears (Odoo.sh or no server_wide_modules). Traffic from before the registry loaded is not recorded. On your own server, add the module to server_wide_modules and restart.
The Network Audit menu is missing. The menu shows only for users in the Network Audit group. Administrators have it automatically. Add the user to the group. See Security and capture limits.

How installation works

This section is for administrators and developers.

  • The module has a post_load step. Odoo runs it once per process when the module is in server_wide_modules, before any database loads. It installs the interceptor.
  • Without server_wide_modules, the module installs the interceptor from a hook in ir.http (_register_hook). Odoo runs this hook when a registry loads in each process. Both routes call the same install step, which runs only once per process, so they do not wrap the network functions twice.
  • The install step is fail-open. If installation fails, the process starts without auditing and writes a warning to the log.
  • Every Odoo worker process installs its own interceptor. Each process keeps a buffer of up to 5,000 events and saves them in batches on its own database cursor. If the buffer is full, new events are dropped. Events are also dropped while a module install or upgrade is running, and in test mode.

Next step

Read your first report.