A browser integration component that lets an extension communicate with software running on the operating system outside the browser sandbox. It is useful for legitimate workflows, but it also creates a bridge from browser context into host-level execution if not tightly governed.
Expanded Definition
A native messaging host is the installed operating-system component that enables a browser extension to send messages to local software outside the browser sandbox. In practice, it is a controlled bridge between web extension logic and host-level processes, which makes it useful for desktop integrations but materially different from ordinary browser-only communication.
In NHI security terms, the host should be treated as an identity-bearing integration point, not just a convenience feature. It can expose local files, certificates, command execution paths, or privileged APIs if registration, allowlisting, and message validation are weak. Guidance varies across vendors on the exact trust boundary, but the core security expectation is consistent: the browser extension, the native host, and the OS permissions must each be governed separately. That aligns with NIST Cybersecurity Framework 2.0 principles for controlled access and resilience, even though no single standard governs native messaging hosts directly.
NHIMG’s research on Ultimate Guide to NHIs shows why this matters: NHIs outnumber human identities by 25x to 50x in modern enterprises, and the blast radius expands quickly when a software connector is granted more trust than its function justifies. The most common misapplication is treating the native host as a harmless extension helper, which occurs when browser teams approve it without host-level threat modeling or permission review.
Examples and Use Cases
Implementing native messaging rigorously often introduces deployment and support overhead, requiring organisations to weigh user convenience against tighter host hardening, signing, and update control.
- A password manager extension uses a native host to read a locally stored vault service, but the host is restricted to a single signed executable and a narrow message schema.
- An enterprise browser extension sends approved commands to a desktop document scanner app, with input validation enforced before any local process action occurs.
- A security tool uses a native host to collect endpoint telemetry from the browser session, while OS policy blocks any request to launch additional binaries.
- A finance portal extension interacts with a local certificate utility for signing workflows, but the host only accepts requests from an approved extension ID and origin.
- A developer tool integrates with local Git or CLI software through a native host, yet the organisation monitors registrations, file paths, and binary hashes as part of software supply chain control.
For broader identity context, Ultimate Guide to NHIs is useful for understanding lifecycle and privilege exposure, while the NIST Cybersecurity Framework 2.0 provides a practical structure for identifying, protecting, detecting, responding, and recovering around the host component.
Why It Matters in NHI Security
Native messaging hosts matter because they collapse the separation between browser trust and operating-system trust. If an extension is compromised, the host can become the path from a web-facing session into local execution, secrets access, or data exfiltration. That is why the host should be governed like any other high-impact NHI component: explicit allowlisting, least privilege, code signing, version control, and revocation procedures.
NHIMG research shows that 97% of NHIs carry excessive privileges, and 96% of organisations store secrets outside secrets managers in vulnerable locations such as code, config files, and CI/CD tools. Those conditions make a native host especially dangerous when it can reach local credential stores or invoke system utilities. The same governance logic that protects service accounts applies here, even though the component lives inside a browser ecosystem rather than an IAM console.
Ultimate Guide to NHIs is the clearest NHIMG reference for this risk pattern, because host-level bridges often become visible only after credential theft, unauthorized execution, or unexpected outbound traffic. Organisations typically encounter native messaging host abuse only after an extension compromise or endpoint investigation, at which point the term becomes operationally unavoidable to address.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP Non-Human Identity Top 10 and OWASP Agentic AI Top 10 address the attack and risk surface, while NIST CSF 2.0, NIST Zero Trust (SP 800-207) and NIST SP 800-63 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP Non-Human Identity Top 10 | NHI-02 | Native hosts expand secret and execution exposure, which NHI-02 is designed to reduce. |
| NIST CSF 2.0 | PR.AC-4 | Least-privilege access is central when a browser extension can trigger host actions. |
| NIST Zero Trust (SP 800-207) | SC-7 | Trust boundaries must be enforced between browser, host, and local OS resources. |
| NIST SP 800-63 | AAL2 | Strong assurance is relevant when native hosts mediate access to sensitive local capabilities. |
| OWASP Agentic AI Top 10 | A3 | Tool-use bridges can create unintended action paths from browser context to local execution. |
Inventory native hosts, restrict their permissions, and validate message handling and secret access.
Related resources from NHI Mgmt Group
- What is the difference between patching a host and governing the blast radius of a kernel flaw?
- How should security teams prioritize vulnerabilities in cloud-native applications?
- Why do static scanners miss some cloud-native attack paths?
- How should teams govern Oracle ERP Cloud access beyond native controls?
Deepen Your Knowledge
Reviewed and updated by the NHIMG editorial team on August 1, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org
