An AUP focuses on how employees and other users may use company technology, data, and networks. A broader security policy covers the organization’s overall security framework, including risk management, incident response, access control, and physical security. The AUP is one user-facing control within a larger governance structure.
How the two policies differ in scope
An Acceptable Use Policy, or AUP, is usually a user behaviour policy. It tells employees, contractors, and other users what they may and may not do with company systems, data, accounts, and networks. A broader security policy is the umbrella document that sets the organisation’s overall security direction, priorities, and control expectations across governance, operations, and technical safeguards.
The practical distinction is that the AUP answers “how should people use company resources?”, while the broader security policy answers “what security principles, controls, and responsibilities must the organisation maintain?” In mature programmes, the AUP sits underneath the broader policy set and translates high-level intent into everyday user rules.
That makes the AUP narrower in audience and purpose, but not necessarily weaker. It is often the policy most likely to be acknowledged by end users, which is why it is commonly used to set expectations around email, internet use, data handling, device use, social media, and acceptable personal use of corporate tools.
What the broader security policy usually covers
A broader security policy typically defines the organisation’s security model, control objectives, and accountability structure. It may cover risk management, access control, incident response, asset protection, logging, physical security, acceptable standards for third-party access, and governance for exceptions or policy waivers.
It is also the policy layer that connects operational practice to management intent. For example, if the organisation expects least privilege, security monitoring, or formal incident reporting, those expectations normally belong in the broader policy rather than only in the AUP. The AUP then inherits the user-facing behaviours that support those expectations.
When organisations compress the two into one document, the result is usually confusion. Users get a long, technical policy they will not read, while security teams lose a clear place to define organisation-wide requirements. Separating the documents makes it easier to assign ownership, review cadence, and audience-specific language.
How to tell which document should carry a rule
A useful test is whether the rule is mainly about user conduct or enterprise security architecture. If the rule tells a user what they can do on a laptop, in email, in cloud apps, or with company data, it belongs in the AUP. If the rule defines the organisation’s security baseline, control objectives, escalation paths, or assurance requirements, it belongs in the broader security policy.
- Put user behaviour rules in the AUP, such as personal use, prohibited software, password sharing, or data posting restrictions.
- Put enterprise security requirements in the broader policy, such as access approval, logging, incident handling, or risk acceptance.
- Use supporting standards, procedures, and guidelines to hold the detailed technical steps, because policy should stay stable even when tools and processes change.
For teams formalising acceptable use, Acceptable Use Policy Template is a practical example of how user rules can cover accounts, cloud services, devices, and privileged users without turning the document into a full security programme.
Risk and Threat Considerations
The main risk is policy confusion: if the AUP is treated as the whole security policy, organisations often leave gaps in governance, incident response, and access control. The opposite problem also appears, where a broad security policy is written so generically that no one can tell what users are actually allowed to do.
Failure mechanism: A narrow user policy cannot replace enterprise control design, and a broad policy without user-level rules leaves too much interpretation to individuals and managers. That creates inconsistent enforcement, weak exception handling, and avoidable exposure when users make day-to-day decisions about data and system use.
Impact: The organisation may suffer misuse of systems, inconsistent disciplinary action, poor evidence for audits or investigations, and higher likelihood of data leakage or shadow IT behaviour. The gap becomes more serious when the user policy does not clearly support controls around sensitive data, remote access, or approved tool use.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST CSF 2.0 and NIST SP 800-53 Rev 5 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST CSF 2.0 | GV.PO-01 — Policy | AUP and security policy are policy artefacts within governance. |
| Recommendation — Define separate policy layers for user conduct and enterprise security. | ||
| NIST SP 800-53 Rev 5 | PL-1 — Security and Privacy Planning Policy and Procedures | Security policy sets organisation-wide security direction and procedures. |
| PL-4 — Rules of Behavior | An AUP is the user-facing rules-of-behaviour layer. | |
| Recommendation — Document and maintain an organisation-wide security policy baseline. Publish and enforce user rules of behaviour for system use. | ||
| ISO/IEC 27001:2022 | A.5.1 — Policies for information security | Both documents are policy instruments under an ISMS. |
| Recommendation — Establish information security policies with clear scope and ownership. | ||
Practitioner Guidance
What to verify: Confirm that the AUP can be read and acknowledged by non-specialists in a few minutes, while the broader security policy remains detailed enough for governance, audit, and control ownership. If both documents contain the same content, one of them is probably too broad.
What good looks like: The AUP is short, behaviour-focused, and easy to enforce, while the security policy establishes the organisation’s control framework and decision rights. The two documents should reference each other, but they should not compete for the same job.
Practitioner takeaway: Treat the AUP as the user contract and the broader security policy as the organisation’s security rulebook, because clarity at that boundary is what makes policy enforceable in practice.
Related resources from NHI Mgmt Group
- What is the difference between AI security policy and a general acceptable use policy?
- How should security teams use ABAC without creating policy sprawl?
- How should security teams use context-based access control without creating policy sprawl?
- How should security teams govern GitHub Actions workflows that use secrets to update policy stores?
Deepen Your Knowledge
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.
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org