Join our Newsletter — 33% off our NHI Course
Home› Guides› Social Media Security Policy Template: Rules for Staff…
Template Security Policies & Awareness

Social Media Security Policy Template: Rules for Staff Accounts, Disclosure and Impersonation

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 14 November 2026 12 min read
On this page

Attackers read your staff's social media before they phish, call the help desk or pose as a recruiter, and they take over your organisation's own accounts to scam your customers. A social media security policy sets the rules for both sides of that risk: how official accounts are owned, secured and recovered, and what staff may share about their work on personal profiles. This template is written for security, communications and HR teams to adopt together. It covers official accounts, personal use that identifies the organisation, confidential information, endorsement disclosure, impersonation, social engineering through social platforms, third-party tools, and incident reporting. It deliberately does not repeat general acceptable use rules, which belong in the Acceptable Use Policy Template. Have employment counsel review it before adoption.

How to use this template

  • Replace text in square brackets, such as [Organisation], [Head of Communications] and [24 hours], with your own names and values.
  • "Must" and "must not" are mandatory. "Should" is recommended practice where a documented exception may be justified.
  • Platform-specific settings (2-step verification methods, admin roles, recovery options) change often. Keep them in a supporting standard and link it from section 4, so the policy does not need reissuing each time a platform changes. The Social Media Account Security for Small Businesses Guide gives platform detail you can draw on.
  • Rules on what staff may say about work affect employment rights. In the United States, the National Labor Relations Board states it is unlawful to maintain work rules that reasonably tend to inhibit employees from exercising their rights under Section 7 of the National Labor Relations Act. Other jurisdictions have their own protections for speech and whistleblowing. Do not adopt sections 5 and 6 without legal review.
  • The response steps for a hijacked official account are in the Social Media Account Takeover Playbook. Reference it from section 10 rather than copying it.

1. Purpose

This policy protects [Organisation], its people and its customers from harm caused through social media: takeover or misuse of official accounts, disclosure of information that helps attackers, impersonation of the organisation or its staff, and social engineering carried out through social platforms. It sets out what is required for official accounts and what is expected of staff when their personal use of social media identifies them with [Organisation].

2. Scope

  1. This policy applies to all employees, contractors, temporary staff, interns and third parties, including agencies, who act for [Organisation] ("staff").
  2. It applies to every official [Organisation] presence on social media, video, community, messaging-channel and review platforms ("official accounts"), whoever created it and whether or not it is active.
  3. It applies to personal accounts only where the content identifies the author as connected with [Organisation], discusses [Organisation] business, or uses [Organisation] information.
  4. It applies to the tools, apps and API tokens connected to official accounts, such as scheduling, analytics, social listening and customer service platforms.

3. Roles and responsibilities

RoleResponsibilities
[Head of Communications]Owns the register of official accounts; approves new accounts, authorised posters and connected tools; approves official statements.
[CISO]Owns the security standard for official accounts; approves exceptions to section 4; leads response to account compromise and impersonation.
[HR Director]Includes this policy in onboarding and offboarding; applies the disciplinary procedure; advises on personal use cases.
[Legal / Data Protection Officer]Advises on endorsement disclosure, regulated communications, monitoring and takedown requests.
Account ownersOne named owner per official account, accountable for its security, access list, recovery details and connected tools.
Authorised postersPost only on accounts they are authorised for, from approved tools and devices, following sections 4 and 7.
All staffFollow sections 5 to 10 and report suspected impersonation, compromise or approaches through social media.

4. Official accounts

4.1 Creation and register

  1. Only [Head of Communications] may approve the creation of an official account. Staff must not create accounts that use the [Organisation] name, logo or brand without approval.
  2. Every official account must be recorded in the [social media account register] with platform, handle, purpose, owner, authorised users, recovery email and phone, connected tools and date of last review.
  3. Dormant accounts must be secured and kept, or formally closed. A handle must not be abandoned in a way that lets someone else claim it.

4.2 Access and authentication

  1. Where the platform supports it, staff must access official accounts through named individual roles (for example business manager or page roles), not a shared login.
  2. Where a shared login is unavoidable, its password must be stored in [approved password manager], shared only through it, and changed whenever someone with access leaves.
  3. 2-step verification must be enabled on every official account and on every personal account that holds an admin role over one. Phishing-resistant methods (passkeys or security keys) must be used where the platform offers them; SMS codes are the last resort.
  4. Recovery email addresses and phone numbers must be [Organisation]-controlled shared mailboxes or numbers, never a personal address or an individual's mobile.
  5. Admin roles must be limited to [two to three] named people per account, and reviewed every [quarter].
  6. Access must be removed on the same day a person leaves or changes role. See the Employee Offboarding Security Checklist.

4.3 Connected tools and tokens

  1. Only tools on the [approved social media tools list] may be connected to official accounts. Each connection grants an access token to a third party and must have an owner.
  2. Connected apps must be reviewed every [quarter] and removed when no longer used. The Social Platform App Tokens Guide describes how to review them.

4.4 Publishing

  1. Statements on security incidents, legal matters, financial results or regulated topics must be approved by [Head of Communications] and [Legal] before publishing.
  2. Official accounts must never ask customers for passwords, one-time codes, card details or payment through direct messages.

5. Personal use that identifies [Organisation]

  1. Staff may say where they work and describe their role in general terms.
  2. Staff who comment on [Organisation] business should make clear that they speak for themselves, not for [Organisation], unless they are authorised to speak for it.
  3. Staff must not use [Organisation] email addresses to register personal social media accounts, and must not reuse [Organisation] passwords on any social platform.
  4. Staff in [high-exposure roles: executives, finance, IT administrators, help desk, HR, executive assistants] should limit public detail about their responsibilities, systems used, reporting lines and travel, because these are the details attackers use for targeting. See the Executive Protection and Digital Footprint Guide.
  5. Nothing in this policy restricts lawful discussion of terms and conditions of employment, or lawful whistleblowing through the channels the law provides.

6. Confidential information and disclosure

Staff must not post, on any account, information classified above [Public] under the Data Classification Policy Template. In particular they must not post:

  1. Photographs or video showing screens, whiteboards, badges, access cards, keys, building layouts, network equipment labels or documents.
  2. Names of internal systems, security tools, versions, project code names or vendor relationships that have not been publicly announced.
  3. Customer names, deals or data, unless already public and approved.
  4. Details of security incidents, vulnerabilities or investigations, including hints that something is wrong.
  5. Organisation charts, internal contact lists, or the names and roles of colleagues who have not chosen to be public.
  6. Live location or travel plans of executives and staff on sensitive business.

If something is posted in error, the author must delete it and report it to [security operations] at once. Deletion does not remove copies already taken.

7. Endorsements and disclosure of connection

  1. Staff who promote, review or share [Organisation] products or services on their own initiative must disclose their connection in the post itself, for example "I work at [Organisation]". A job title on a profile page is not enough.
  2. Staff must not post reviews of [Organisation] or competitor products on review sites without disclosing their connection.
  3. Any programme that encourages staff to post about [Organisation] products must be approved by [Legal], must remind participants of this section, and must include monitoring of the resulting posts.

8. Impersonation

  1. [Communications] must monitor for accounts impersonating [Organisation], its brands and its executives, at least [weekly], and report them to the platform using its impersonation process.
  2. Staff must report any account that impersonates [Organisation], a colleague or themselves in connection with their job to [security operations].
  3. [Organisation] will publish on its website the list of official accounts and state that it will never request payment, credentials or one-time codes through social media messages.
  4. Where impersonation forms part of a fraud, deepfake or lookalike domain campaign, response follows the Brand Impersonation and Lookalike Domain Takedown Playbook.

9. Social engineering through social platforms

  1. Staff must treat unsolicited approaches through social platforms (connection requests, recruiter messages, job offers, "collaboration" invitations, requests from apparent colleagues) as untrusted until verified through a known channel.
  2. Staff must not open files, run tests, install software or join calls on unfamiliar platforms because of a social media approach, and must not share credentials, codes or internal documents in response to one.
  3. A request through social media that appears to come from an executive or colleague and asks for payment, gift cards, access or data must be verified by calling a number from the [Organisation] directory.
  4. Staff must report suspicious approaches to [security operations] with a screenshot and the profile link.

10. Incidents and account compromise

  1. Suspected compromise of an official account must be reported to [security operations] and [Head of Communications] immediately, and within [1 hour] of discovery.
  2. Suspected compromise of a personal account that holds an admin role over an official account must be reported in the same way.
  3. Response follows the Social Media Account Takeover Playbook. Staff must not post publicly about the incident unless [Head of Communications] approves.

11. Monitoring

  1. [Organisation] monitors official accounts, their admin and login activity where platforms provide it, and public mentions of [Organisation].
  2. [Organisation] does not monitor staff personal accounts, except where content is publicly posted and reported as breaching this policy, or as permitted by law and set out in the [staff privacy notice].

12. Compliance, exceptions and review

  1. Breaches of this policy may lead to action under the [disciplinary procedure], and to removal of access to official accounts.
  2. Exceptions to section 4 must be requested from [CISO], documented with a reason and an expiry date, and reviewed at expiry.
  3. Staff must acknowledge this policy at onboarding and on each major revision.
  4. This policy is reviewed every [12 months], and after any significant social media incident.

Implementation guidance

Where the design choices come from

  • Rules of behaviour for social media: NIST SP 800-53 Rev. 5 control PL-4(1) Social Media and External Site/Application Usage Restrictions sits under PL-4 Rules of Behavior and adds restrictions on social media use, on posting organisational information on public websites, and on using organisational identifiers to create external accounts. Sections 5 and 6 implement it, and section 5.3 covers the identifier rule.
  • Reconnaissance: MITRE ATT&CK T1593.001 Social Media describes adversaries searching social media for information about victims, and T1585.001 Social Media Accounts describes attackers creating persona accounts. Sections 6, 8 and 9 target these.
  • 2-step verification: the NCSC recommends turning on 2-step verification wherever it is available and reporting fake accounts to the platform, which sections 4.2 and 8 make mandatory for official accounts.
  • Endorsements: the US Federal Trade Commission says employees should disclose their employment in the post itself when promoting their employer's products, that a profile listing is not enough, and that companies should remind staff of the requirement and monitor programmes they actively encourage. Section 7 reflects this.

Rollout

  1. Build the official account register first by searching every platform for your brand and asking teams, agencies and regional offices what they run.
  2. Bring each account into compliance with section 4: named roles, 2-step verification, organisation-controlled recovery details, connected app review.
  3. Agree sections 5 to 7 with HR, Legal and staff representatives, then publish with a short briefing and real examples of photos that leaked information.
  4. Add sections 8 and 9 to awareness training, with a simple reporting route.
  5. Test section 10 with a tabletop exercise on a hijacked official account.

Measures

MeasureTarget
Official accounts in the register with a named owner100%
Official accounts with 2-step verification and organisation-controlled recovery details100%
Leavers removed from official accounts on their last day100%
Connected apps reviewed in the last quarter100%
Median time to report impersonation accounts to the platformUnder [2 working days]
Staff reports of suspicious social media approachesRising after training, then stable

Framework mapping

FrameworkReferencePolicy sections
NIST SP 800-53 Rev. 5PL-4 Rules of Behavior; PL-4(1) Social Media and External Site/Application Usage Restrictions5, 6, 12.3
NIST SP 800-53 Rev. 5AT-2 Literacy Training and Awareness9, rollout step 4
NIST SP 800-53 Rev. 5IR-6 Incident Reporting6, 10
MITRE ATT&CK v20T1593.001 Social Media; T1585.001 Social Media Accounts6, 8, 9

Failure patterns this policy is written to prevent

  • An official account created by a former employee or agency, recovered to a personal email address nobody can reach.
  • A shared password for the brand account that never changes when people leave.
  • A photo from an office celebration showing a whiteboard with system names or a badge in close-up.
  • A help desk agent whose public profile names the identity tools they administer, used to script a convincing call.
  • A fake recruiter approach that ends with a staff member running a "coding test" on a work laptop.

Standards and references

Related NHI Mgmt Group resources: Acceptable Use Policy Template, Social Media Account Takeover Playbook, Social Media Privacy Settings Guide, Executive Protection and Digital Footprint Guide, Impersonation Scams Guide.

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

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
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 14 November 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.