What Network Audit does
This page explains what MIT Network Audit records, what it shows you, and where its limits are, so you can decide whether it answers your question.
Who this is for: administrators, security officers and buyers who want to know what the module does before they install it. You need: nothing yet. This page is background reading.
The question it helps with
MIT ships its commercial modules, such as MailDesk and the licence locker, in obfuscated form. You cannot read their code. A common question follows from that: "Which connections do these modules make from my Odoo system?"
MIT Network Audit does not read the other modules. It watches the network connections that your Odoo processes make and receive. It records each connection as one row and tells you which installed module made it. You can then compare the list with what you expect.
What it records
For each connection that it captures, the module stores metadata:
- the direction (inbound or outbound), the channel (for example
requests,imap,smtporsocket), the method and the status; - the destination host, URL path, the names of query parameters (not their values), and the IP address and port;
- the size of the request and the response, and the time;
- the Odoo module that made the call, its author, and the place in the code where the call was made;
- request and response headers. The values of sensitive headers (for example
AuthorizationandCookie) are masked. Other header values are stored as they are; - a salted fingerprint of the method, host and path. It lets you group identical requests. It is not a fingerprint of the message content.
In normal use the module does not store request or response bodies.
What you see
The module gives you three views of the same records:
- The Trust Report is a dashboard. It sorts destinations into MIT-bound and third-party, shows a verdict, and lists the destinations.
- The Audit Log lists every recorded connection, one row each. It opens filtered to Outbound; remove the filter to see inbound rows.
- The Export Signed Audit wizard writes a signed JSON file that another person can check outside Odoo.
The Trust Report. Open it from Network Audit ▸ Trust Report.
A destination counts as MIT-bound when it matches an entry in the Egress Components list, either by host pattern or by the module that made the call. Everything else is third-party. Administrators can edit that list. See Change audit settings.
What it does not do
Limits
- It does not block anything. It is not a firewall and not a sandbox.
- It does not capture everything. WebSocket connections, connections to the same machine (including PostgreSQL), traffic from other programs on the server, and anything that happens while auditing or a channel is switched off are not recorded. Events can also be dropped when the internal buffer is full. See Security and capture limits.
- A verdict is not a proof. An all-clear verdict means that the recorded traffic passed a simple rule. It does not mean that no other connection exists.
- Optional forensic body capture can store bodies. It is off by default, only a user in the Network Forensic Officer group can use it, and it needs an allowlist of modules.
- Speed impact has not been measured. Do not assume that the module adds no load. Test it on a copy of your system first if load matters to you.
Next step
Related: Read your first report.