Join our Newsletter — 33% off our NHI Course
Home› Glossary› Cyber Security› MBOX
Cyber Security

MBOX

← Back to Glossary
By NHI Mgmt Group Updated November 16, 2026 Domain: Cyber Security

MBOX is a plain text mailbox file format that stores many email messages in one file, usually separated by message headers and body boundaries. It is widely used for mail export, archiving and migration, and its contents can expose mail data if the file is copied or mounted without access controls.

What MBOX Is and How It Organises Mail

MBOX is a simple mailbox format that stores multiple email messages in one plain text file. Each message is typically separated by headers and body boundaries, which makes the format easy to transport, export, and inspect. That same simplicity also means the file can expose email content whenever it is moved, copied, or mounted without proper file-level protections.

Why MBOX Is Used for Export, Archiving, and Migration

MBOX remains common because it is widely supported by mail clients, backup tools, and migration workflows. It is useful when an organisation needs a single portable container for many messages, especially for long-term retention or transfer between systems.

Its portability is also its main trade-off. A single MBOX file may contain large volumes of sensitive correspondence, attachments, or metadata, so the operational convenience of one file must be balanced against the security implications of concentrating many messages into one object.

MBOX File Structure and Parsing Behaviour

An MBOX file is readable text, not a binary database. The messages are usually concatenated in sequence, with message separators and mail headers embedded directly in the file content. Because the format is plain text, it is easy for tools to process, but also easy for a person or another process to read if they gain access to the file.

That structure also creates compatibility and integrity considerations. Different mail systems may handle message boundaries, line endings, or escaping differently, so a migration or import can sometimes alter message presentation or recoverability if the file is not handled carefully.

Security Implications of Storing Mail in MBOX

MBOX can become a sensitive data concentration point. If the file is copied to a backup location, exposed through shared storage, or mounted on a system with weak permissions, every message inside the archive may become accessible at once. For that reason, MBOX should be treated as mail data at rest, not as a harmless transport artifact.

It can also complicate visibility because security controls often sit around the file system rather than inside the mailbox format itself. Access controls, encryption, retention handling, and export hygiene matter more here than the file extension alone.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-53 Rev 5 sets the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5AC-3 — Access EnforcementMBOX exposure depends on enforcing file and storage access restrictions.
SC-28 — Protection of Information at RestMBOX is sensitive stored mail content that needs at-rest protection.
MP-6 — Media SanitizationMBOX exports and copies may persist on removable or transferred media.
Recommendation — Enforce access rules so only authorised users and processes can read exported mailbox files. Protect mailbox archives at rest with encryption or equivalent storage safeguards. Sanitise media and residual copies after mailbox export, transfer, or disposal.
ISO/IEC 27001:2022A.5.12 — Classification of informationMBOX files should be classified according to the sensitivity of the messages they contain.
A.5.15 — Access controlAccess to MBOX archives is an information access-control decision.
A.8.24 — Use of cryptographyEncryption is a direct protective control for MBOX files stored or transferred.
Recommendation — Classify mailbox exports so handling rules match the sensitivity of contained mail. Limit access to mailbox files to approved roles and workflows. Encrypt mailbox archives when they are stored, backed up, or transported.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org