What Is Zero Trust Architecture?
Also known as: zero trust, ZTA, zero trust security ERP
Definition
Zero trust is a security model that assumes no user, device or network location is trusted by default. Every request is verified for identity, device health and authorization, and access is limited to the minimum needed.
Zero Trust Architecture Explained
Zero trust replaces the older castle-and-moat idea, where anything inside the corporate network was trusted. Its core principles are to verify explicitly, use least-privilege access, and assume breach. NIST describes it in Special Publication 800-207, and US federal guidance has pushed contractors toward it.
For an ERP this has concrete meaning. Users reach the application through an identity-aware proxy or VPN-less access gateway with MFA, not by being on the plant LAN. The database server is not reachable from user workstations, only from the application tier. Integration accounts have narrow, rotated credentials. Admin access is just-in-time and logged. Legacy plant-floor and ERP servers sit in their own network segments.
On-prem ERPs are often flat networks with old service accounts, shared admin logins and open database ports, so zero trust is a program of incremental steps rather than a product: inventory identities, enforce MFA, segment the network, remove standing admin rights, then monitor. Cloud ERPs shift some of this to the vendor, but identity, roles and data export still belong to the customer.
It applies equally to AI. An AI assistant that queries the ERP should authenticate as a defined identity, receive only the data the asking user may see, and have its queries logged. Private model hosting inside the network boundary removes one outside trust relationship entirely.
Why It Matters
- Ransomware and credential theft usually spread by moving laterally through trusted internal networks, which segmentation and verification limit.
- Defense and aerospace supply chains increasingly ask for zero-trust-aligned controls in contracts and questionnaires.
- It forces a real inventory of service accounts and integrations that often hold excessive ERP rights.
- It gives a structure for governing AI agents, which are new non-human identities touching sensitive data.
In Practice
A job shop with an on-prem ERP moves from a flat network to three segments: users, application servers and database. It puts remote access behind MFA, removes the shared domain admin login used by the ERP service, and limits the database port to the application server. The project is spread over a quarter and mostly uses existing firewall and directory features.
Frequently Asked Questions
Is zero trust a product I can buy?
No. It is an approach built from identity, device, network and monitoring controls. Vendors sell components, but the model is a way of designing access.
Does zero trust mean moving the ERP to the cloud?
No. It can be applied to on-prem, hybrid or cloud ERP. What changes is how access is verified and how the network is segmented.
Where should a manufacturer start?
Inventory identities and service accounts, enforce MFA for all remote and admin access, then segment the ERP database and application servers from general user networks.
Related Terms
Single Sign-On (SSO)
Single sign-on lets users authenticate once with a central identity provider and reach the ERP and other apps without separate passwords. It uses standards such as SAML 2.0 or OpenID Connect.
Role-Based Access Control (RBAC)
Role-based access control grants ERP permissions to roles that match job functions, then assigns users to roles, instead of setting permissions user by user. It makes access consistent, reviewable and easier to remove.
NIST SP 800-171
NIST SP 800-171 is the National Institute of Standards and Technology publication that defines the security requirements for protecting Controlled Unclassified Information in nonfederal systems, and it is the technical baseline behind DFARS 252.204-7012 and CMMC Level 2.
Air-Gapped AI
Air-gapped AI is the deployment of AI models on a network that has no physical or logical connection to the internet or to any less-trusted network, so all model files, dependencies, and data must be transferred through a controlled process.
Sovereign AI
Sovereign AI is the principle that a nation or organization should retain legal and physical control over the AI models, data, and computing infrastructure it depends on, rather than relying on systems governed by another jurisdiction.
Go Deeper
ERP Security Posture Checklist
Work through 30 concrete security controls across access, patching, network, data protection, and monitoring, with the highest-risk items flagged.
Free ToolOn-Prem AI Security Hardening Checklist
A practical control checklist for securing self-hosted language models, covering model provenance, network isolation, data governance, host hardening, and audit readiness.
ERP Security Best Practices Guide
Implement comprehensive ERP security best practices covering access control, encryption, monitoring, and compliance aligned with NIST CSF and CIS Controls frameworks.
ERP Hybrid Cloud Architecture Guide
Design a hybrid cloud architecture for ERP systems balancing on-premise and cloud workloads. Covers Azure Arc, AWS Outposts, connectivity, and data residency patterns.
ERP Cloud Compliance and Regulatory Guide
Ensure ERP cloud compliance with SOX, GDPR, HIPAA, and industry regulations. Covers data residency, audit trails, encryption, and compliance automation strategies.
Working with Zero Trust Architecture in a live environment? Our engineers do this every day - and our AI agents automate most of it.