Skip to content
Signals
Monitoring NVD, CISA KEV, EPSS and the Dragons Community ransomware tracker in near-real timeMonitoring NVD, CISA KEV, EPSS and the Dragons Community ransomware tracker in near-real time

Acceptable Use Policy Framework

· Document
By Dragons Community GRC· acceptable-use · policy · governance

All intelligence content is fictional, redacted and defensive. No real credentials, stolen data, exploit instructions, malware links, payment information or private personal data is published. This is a template framework, not legal advice. Bracketed placeholders and every clause must be reviewed and adapted by your legal, HR, and privacy teams for the laws, employment regulations, and works-council or union obligations of each jurisdiction in which you operate before adoption.

An Acceptable Use Policy (AUP) defines how members of an organisation may use its information systems, networks, and data, and what is forbidden. This framework provides adaptable, template-style clauses an organisation can lift, tailor, and ratify rather than draft from scratch. It is deliberately defensive and governance-focused: the aim is to set clear expectations, protect people and data, and create a fair basis for enforcement, not to enable surveillance for its own sake. Replace every bracketed placeholder such as [Organisation] with your own values, delete clauses that do not apply, and have the result reviewed by legal and HR before publication. Pair the policy with awareness training and a signed acknowledgement so that it is understood, not merely posted.

Purpose and Scope

This policy sets out the acceptable use of [Organisation] information systems, including networks, devices, applications, cloud services, email, and data. Its purpose is to protect [Organisation], its staff, its customers, and its partners from harm arising from misuse, whether deliberate or inadvertent, and to ensure use that is lawful, ethical, and consistent with business objectives.

This policy applies to all workers, employees, contractors, temporary staff, interns, and third parties who access [Organisation] systems or data, on any device, whether on-premises or remote. It covers organisation-owned assets and personal devices used for work. Where a more specific policy exists for a given system, that policy applies in addition to this one.

  • State the systems, data, and locations the policy covers, including remote and cloud use.
  • Name every population bound by the policy: employees, contractors, temporary staff, and third parties.
  • Confirm coverage of both organisation-owned and personally owned devices used for work.
  • Reference related policies (data classification, information security, incident response) it works alongside.
  • Record the policy owner, approval authority, effective date, and review cadence.

General Use and Ownership Principles

Access to [Organisation] systems is a privilege granted for legitimate business purposes and may be modified or withdrawn at any time. Users are accountable for activity performed under their credentials and must use systems with the same care and good judgement expected in all professional conduct. Limited, reasonable personal use may be permitted at management discretion provided it does not interfere with duties, consume undue resources, or breach this policy.

All data created, stored, sent, or received on [Organisation] systems remains the property of [Organisation], subject to applicable law. Users should have no expectation of privacy in material stored on organisation systems beyond the limited protections described in the Monitoring and Privacy section and required by law.

  • State that access is a privilege tied to legitimate business need and may be revoked.
  • Make users accountable for all activity performed under their accounts and credentials.
  • Define whether and how limited personal use is permitted, and its boundaries.
  • Clarify organisational ownership of data created or stored on its systems, subject to law.
  • Cross-reference the Monitoring and Privacy section rather than overstating ownership.

Acceptable Use

Users may use [Organisation] systems to perform their assigned duties, communicate with colleagues, customers, and partners, and access information and services required for their role. Users are expected to follow security requirements such as locking unattended devices, using approved software, storing data in approved locations, and reporting anything that looks suspicious.

Acceptable use means lawful, professional, and proportionate use that respects the rights of others and the security of [Organisation]. When in doubt about whether an action is permitted, users should ask their manager or the [Security Team] before proceeding.

  • Use systems and data only for assigned business duties and authorised purposes.
  • Use only approved, licensed software and approved data storage locations.
  • Lock or log off devices when unattended and protect screens in public spaces.
  • Keep credentials private and use multi-factor authentication where provided.
  • Store and classify information according to the data classification policy.
  • Ask a manager or the [Security Team] before acting when permissibility is unclear.

Prohibited Use

The following activities are prohibited without exception unless explicitly authorised in writing for a legitimate business reason (for example, authorised security testing). This list is illustrative, not exhaustive; any use that is unlawful, harmful, or contrary to the spirit of this policy is prohibited even if not listed below.

Users who become aware of any prohibited activity, including their own inadvertent breach, must report it promptly under the Incident Reporting section rather than attempting to conceal or quietly correct it.

  • No unlawful activity, harassment, discrimination, or creation or distribution of offensive material.
  • No unauthorised access, scanning, penetration testing, or attempts to bypass security controls.
  • No installing unlicensed, pirated, or unapproved software, or disabling security tooling.
  • No sharing credentials, or accessing accounts, data, or systems beyond your authorisation.
  • No exfiltrating, selling, or removing confidential data to personal accounts or storage.
  • No knowingly introducing malware, or circumventing network, content, or DLP controls.
  • No using systems for personal commercial gain, gambling, or unauthorised cryptocurrency mining.

Network and System Access

Access to [Organisation] networks and systems is granted on a least-privilege, need-to-know basis and tied to the user's role. Users must authenticate with their own unique credentials, protect those credentials, and use multi-factor authentication wherever it is offered. Connections to internal networks, including remote access, must use approved methods such as the [Organisation] VPN and approved, managed endpoints.

Users must not extend, bridge, or alter the network, for example by attaching unauthorised wireless access points, routers, or rogue DHCP services, and must not connect untrusted or unmanaged devices to protected network segments without authorisation.

  • Authenticate only with your own unique credentials and enable MFA where available.
  • Access only the systems and data your role authorises, on a need-to-know basis.
  • Use approved remote-access methods (for example the [Organisation] VPN) from managed endpoints.
  • Do not attach unauthorised network devices such as access points, switches, or routers.
  • Do not connect untrusted or personal devices to protected network segments without approval.
  • Report lost or stolen devices and suspected credential compromise immediately.

Data Handling and Confidentiality

Users must handle information according to its classification under the [Data Classification Policy] and protect the confidentiality, integrity, and availability of [Organisation] and customer data. Confidential and regulated data (for example personal data, financial records, or health information) must be stored only in approved systems, encrypted in transit and at rest where required, and shared only with authorised recipients through approved channels.

Users must not transfer confidential data to personal email, personal cloud storage, removable media, or other unapproved locations. When data is no longer needed it must be retained and disposed of in line with the [Records Retention Policy] and applicable law.

  • Classify and handle data according to the [Data Classification Policy].
  • Store confidential and regulated data only in approved, access-controlled systems.
  • Encrypt sensitive data in transit and at rest where required by policy or law.
  • Share data only with authorised recipients through approved channels.
  • Never move confidential data to personal email, cloud, or removable media.
  • Retain and dispose of data per the [Records Retention Policy] and legal requirements.
  • Report any suspected or actual data loss or exposure under Incident Reporting.

Personal Devices and BYOD

Where [Organisation] permits the use of personal devices (Bring Your Own Device) to access organisation data, that use is conditional on enrolment in approved management (for example mobile device management or a managed work profile) and compliance with minimum security standards. Personal devices used for work must be kept patched, protected by a passcode or biometric lock, and capable of remote wipe of organisation data.

Users consent that [Organisation] may enforce security controls on, and selectively wipe its data from, enrolled personal devices, and that loss or theft of any device holding organisation data must be reported immediately. Personal devices that cannot meet these standards must not be used to access [Organisation] data.

  • Enrol personal devices in approved management before accessing organisation data.
  • Keep the device patched and running a supported operating system version.
  • Protect the device with a passcode or biometric lock and full-device encryption.
  • Allow remote wipe of organisation data and acknowledge selective-wipe consent.
  • Do not store organisation data in unmanaged personal apps or backups.
  • Report loss or theft of any device holding organisation data immediately.
  • Do not use jailbroken, rooted, or end-of-life devices for work.

Cloud, SaaS and Shadow IT

Users may use only cloud and software-as-a-service applications that have been approved and, where required, contracted and security-reviewed by [Organisation]. Procuring or signing up for new cloud services with organisation data, or paying with personal or corporate funds outside the approved process, constitutes shadow IT and is prohibited because it bypasses security, privacy, and contractual safeguards.

Before requesting a new service, users should check the approved-applications catalogue and route new needs through [IT or Procurement] for review. Organisation data must not be uploaded to unapproved cloud services, AI tools, or file-sharing platforms.

  • Use only cloud and SaaS applications approved and listed in the [approved-applications catalogue].
  • Route requests for new services through [IT or Procurement] for security and privacy review.
  • Do not sign up for or purchase cloud services that process organisation data outside the approved process.
  • Do not upload confidential or personal data to unapproved cloud, AI, or file-sharing tools.
  • Use single sign-on and organisation accounts rather than personal accounts for work services.
  • Report discovered shadow IT so it can be reviewed or sanctioned.

Email, Messaging and Social Media

Email and messaging systems must be used professionally and securely. Users must remain alert to phishing and social-engineering attempts, verify unexpected requests through a second channel, and report suspicious messages using the [report-phishing] mechanism rather than clicking, replying, or forwarding them. Users must not use organisation email to send confidential data to unauthorised recipients or to register for unrelated personal services.

When using social media, whether on personal or organisation accounts, users must not disclose [Organisation] confidential information, speak on behalf of [Organisation] without authorisation, or post content that could reasonably harm the organisation, its staff, customers, or partners. Personal opinions must be clearly identified as personal.

  • Use email and messaging professionally and only for appropriate purposes.
  • Report suspected phishing via the [report-phishing] mechanism instead of interacting with it.
  • Verify unexpected payment, credential, or data requests through a separate trusted channel.
  • Do not email confidential data to unauthorised recipients or personal accounts.
  • Do not disclose confidential information or speak for [Organisation] on social media without authorisation.
  • Identify personal opinions as personal and avoid posts that could harm the organisation.
  • Follow brand and disclosure rules when posting on official organisation accounts.

Monitoring and Privacy Notice

To protect its systems and data, [Organisation] may log, monitor, and review use of its networks, devices, and accounts to the extent permitted by applicable law, including security logging, email and web-traffic inspection, and review of activity where there is a legitimate need such as investigating a security or policy incident. Monitoring is proportionate, conducted for defined purposes such as security, compliance, and system management, and is not intended for routine surveillance of individuals.

Where local law, employment regulation, or works-council agreement imposes additional notice, consent, or limitation requirements, those requirements take precedence and must be reflected here. Personal data processed through monitoring is handled in line with the [Privacy Policy] and applicable data-protection law.

  • State clearly that systems may be logged, monitored, and reviewed, and for what purposes.
  • Limit monitoring to defined, legitimate purposes such as security, compliance, and operations.
  • Commit to proportionality and to compliance with local privacy and employment law.
  • Reference the [Privacy Policy] for how personal data from monitoring is handled.
  • Incorporate jurisdiction-specific notice, consent, or works-council requirements where they apply.
  • Have legal and privacy teams review this section for every operating jurisdiction.

Incident Reporting

Users must promptly report any actual or suspected security incident, policy breach, lost or stolen device, suspected malware, phishing, or data exposure, through the [Security Team / service desk] using the [defined reporting channel]. Early reporting limits harm; users who report promptly and in good faith, including reporting their own honest mistakes, will be supported rather than penalised for the act of reporting.

Users must not attempt to investigate, contain, or conceal an incident on their own beyond immediate safe steps (such as disconnecting a clearly compromised device when instructed), and must preserve evidence and follow the instructions of the [Incident Response] team.

  • Report suspected incidents, breaches, and lost devices immediately via the [defined reporting channel].
  • Report your own honest mistakes promptly; good-faith reporting is supported, not punished.
  • Do not attempt independent investigation, containment, or concealment beyond instructed safe steps.
  • Preserve evidence and follow [Incident Response] team instructions.
  • Know the after-hours reporting route for urgent incidents.
  • Report suspected phishing and social engineering even if no harm appears to have occurred.

Enforcement and Consequences

Compliance with this policy is mandatory. Suspected violations will be investigated fairly and consistently, and confirmed violations may result in disciplinary action up to and including termination of employment or contract, in line with [Organisation] disciplinary procedures and applicable law. Where activity is unlawful, [Organisation] may refer the matter to law enforcement and pursue civil or criminal remedies.

Enforcement is proportionate to the nature and severity of the violation and considers intent, harm, and whether the user reported in good faith. Managers and the [Security Team] are responsible for applying this policy consistently and without arbitrary or discriminatory treatment.

  • State that compliance is mandatory and violations will be investigated fairly.
  • Define the range of consequences, up to termination, aligned with disciplinary procedures.
  • Reserve the right to involve law enforcement for unlawful activity.
  • Make enforcement proportionate to severity, intent, and harm.
  • Credit good-faith self-reporting as a mitigating factor.
  • Require consistent, non-discriminatory application by managers and the [Security Team].

Acknowledgement

All individuals covered by this policy must read it and confirm their understanding and agreement before being granted or retaining access to [Organisation] systems, and again whenever the policy is materially updated or on a periodic basis (for example annually). Acknowledgement may be captured by signature or through an approved electronic system, and records must be retained as evidence of compliance.

By acknowledging, the user confirms that they have read and understood this policy, agree to abide by it, and understand that breach may lead to disciplinary or legal consequences. Questions about the policy should be directed to [the policy owner or Security Team] before acceptance.

  • Require acknowledgement before initial access and after material updates or annually.
  • Capture acknowledgement by signature or an approved electronic system.
  • Retain acknowledgement records as auditable evidence of compliance.
  • State that acknowledgement confirms understanding and agreement to comply.
  • Provide a route to ask questions before accepting the policy.
  • Track outstanding acknowledgements and follow up on non-completion.
Acceptable Use Policy Framework — Document | Dragons Community