What Should You Write in Your Information Security Policy?
Writing an information security policy has to cover more than attacks from hackers, malware, viruses, and botnets. It also has to govern how employees use company devices, cloud apps, social networks, and generative AI assistants, because routine work can expose sensitive information when approved tools and handling rules are unclear.
So what should you write in your information security policy? The ten controls below give a small business a practical structure for assigning ownership, setting rules, and testing whether its protections work.
What Should an Information Security Policy Include?
An effective policy addresses both outside attacks and the mistakes, unclear permissions, and unapproved tools that can expose information during ordinary work. The following steps can help you boost business cyber-security and protect your business.
1. Manage Your Technology Life Cycle
Hardware and software become a security problem when vendors stop supporting them, critical patches no longer apply, or the equipment cannot run the controls your business requires. Your Information Security Policy should require an accurate inventory and define who monitors support dates and patch status.
Develop a technology life cycle plan for all computer hardware and software assets. Write the vendor support end date next to every asset, then base replacement priorities on support status, patchability, business criticality, and recovery needs. The NIST small-business cybersecurity guide recommends maintaining an inventory and keeping software and operating systems patched.
2. Establish a Password Security Policy
Make sure your computers, servers, Wi-Fi connections, and cloud accounts all have authentication controls. Open devices and connections create avoidable exposure, but there are several ways your business can improve cybersecurity beyond simply closing them.
Close those connections and use unique credentials for each user. Favor long passphrases over short complex strings, screen new passwords against known compromised-password lists, and give staff a password manager so unique credentials are practical. NIST Special Publication 800-63B says verifiers should not require routine periodic password changes and should require a change when there is evidence of compromise. The current requirements are in the NIST digital identity guidelines. Your IT Security Policies should add multi-factor authentication for email, remote access, and administrative accounts, rate limiting for failed login attempts, and immediate disablement of former employee accounts.
3. Back Up Your Data Frequently
Many businesses say they have a backup plan, but are their servers backed up frequently enough? What about individual PCs: do they contain data or applications that are not on the servers? Are they backed up, and should they be?

Are backups taken off-site? Have you tried to restore your backups onto a machine that is not the one they came from? Are you using cloud-based apps but unsure whether your cloud data are backed up appropriately? For policy and procedure documents stored in Bizmanualz OnPolicy procedure management software, hosted backups are managed centrally rather than by each user.
Test the backup process before an attack or system failure makes recovery urgent. Ransomware operators may try to delete or encrypt accessible backups. The CISA #StopRansomware Guide advises organizations to maintain offline, encrypted backups of critical data and regularly test their availability and integrity in a disaster recovery scenario. Your IT Security Policies should specify regular backups, at least one copy kept offline or immutable, and restore tests on a documented cadence with a named owner.
4. Use Malware and Virus Protection
People can inadvertently download malicious files or follow deceptive prompts. The next thing you know, that computer, or even the network, may be compromised. You should have a Computer Malware Procedure that says who isolates the machine, who investigates, and who decides it is safe to return to the network.
When you develop an information security policy, centralize anti-malware management instead of making each user responsible for a separate device. Enable scheduled scanning, automatic updates, and alerts when protection is disabled or a subscription lapses. Require endpoint tools that can monitor suspicious behavior as well as known file signatures, but do not treat any single product as complete protection.
5. Secure Your Mobile Devices
If employees handle sensitive information on laptops, phones, or tablets, develop a Mobile Device Management Plan that addresses data loss prevention, access, and the other IT policies and procedures templates that support it. Include disk encryption, screen-lock enforcement, a current device inventory, and the ability to wipe a managed device when it is lost or misused.
If employees may not use personal devices to handle company information, state that rule and explain how it will be enforced. The same decision applies to consumer cloud storage and public AI assistants. Name the approved tools in the policy and state what company information must never be entered into an unapproved service. CISA advises users not to submit sensitive, confidential, or personally identifiable information to public AI tools in its public AI safety guidance.
6. Communicate Your Information Security Policies
Imagine you have created a new password policy, invested in anti-malware software, and developed a Mobile Device Management Plan but have not told anyone. How useful will those measures be in helping secure your information?

Communicate your IT security policies and train employees to carry out the required controls. Do not send one email that says, “Here is our IT Security Policy,” and leave it at that. Show employees why the policy matters, how to follow it, and how to report a suspected incident.
Ensure that employees understand the password policy, what endpoint protection does, what “acceptable use” means, and how to protect mobile devices. Track training and acknowledgment of the current policy so you can identify gaps, follow up with staff, and show which version each person received. The FTC cybersecurity guidance for small businesses recommends regular staff training and tracking participation.
7. Restrict Access to Your Data
Microsoft Windows, Linux, and other operating systems provide account and permission controls that support your written access controls. Identify what each user role requires for data, network, or peripheral access, for example read only, read/write, or execute. Too much access increases the risk of misuse and data loss, while restrictions that are too tight can prevent employees from doing their jobs. The right boundary changes as roles, systems, and data change.
Two habits keep the line in roughly the right place. Grant access by role rather than by person, so a job change updates permissions automatically, and review the access list on a schedule, paying particular attention to administrator rights and to shared cloud folders that quietly became company-wide.
8. Implement a Contingency Plan
A computer, IT, or data center disaster recovery plan is an important element of securing your computer data. There are more than hackers and trusting (or untrustworthy) employees, there are acts of nature that threaten your business’s continuity, too.
You never know when fire, flood, tornado, civil disruption, robbery, or other catastrophic events will occur, but if one of them does strike, how long will it take you to get your business back online? Without a disaster plan in place, it will take too long.
Your IT Security Policies should include hardware and software replacement, data recovery, and key configuration, restoration, or installation details. It should include appropriate software license numbers, insurance numbers, and key contractor or supplier numbers. It should cover testing, validation, and performance criteria. Write down the recovery time you are actually aiming for per system, and keep a printed copy of the plan and the contact list, because a plan that lives only on the encrypted file server is not available on the day you need it. Furthermore, you need to thoroughly test your recovery plan before you need it.
9. Block Would-Be Intruders from Your Network
You cannot block every intrusion attempt, but you can make entry more difficult by installing a business-class firewall and updating it regularly. Close firewall ports you do not use. Retire legacy wireless encryption, use WPA3 where access points and clients support it, use WPA2 where they do not, and keep guest devices on a separate network. The FTC small-business guidance recommends WPA2 or WPA3 encryption and a separate guest network.
Restrict DNS zone transfers to authorized hosts, as recommended in NIST secure DNS guidance. Add an intrusion prevention system that monitors network and system events for malicious activity. Remote access deserves the same attention as the perimeter: require multi-factor authentication on VPN and remote desktop services, and do not expose remote desktop directly to the Internet.
10. Close Holes in Your IT Security Policy
As the quality principle says, “You do not know what you do not know.” This is true for IT security as well. To find gaps in your computer security system, perform regular IT security audits and network inspections. Check firewall, identity, endpoint, and server logs for signs of a threat.
Verify that you have implemented measures to address the first nine points above. Enable automatic updates across operating systems, browsers, and third-party applications, and use patch-management or vulnerability-scanning reports to confirm that updates landed rather than assuming they did. Make sure anti-malware systems are also updated automatically and monitored for failures.
Consider using an independent computer security expert to audit the information security program and conduct appropriate tests, such as vulnerability assessment and authorized penetration testing, on a cadence based on the systems and risks involved. If you want the written framework to organize these controls, the IT Security Policies and Procedures Manual gives you editable documents to start from.
Write Information Security Policies
Implementing these ten controls will not make an IT system perfect, but it can reduce common risks and make detection, response, and recovery more consistent. The policy becomes useful when each rule has an owner, evidence that the control operates, and a trigger for review or testing.
Use the control matrix below to turn the ten topics into accountable policy statements. Adapt each trigger to the sensitivity of your data, your recovery objectives, and any legal or contractual requirements that apply to your business.
Information Security Policy Control Matrix
This worked matrix is a starting point for assigning each policy area to an owner and deciding what evidence to retain. Replace the example roles and triggers with responsibilities that match your organization.
| Policy area | Required rule | Accountable owner | Evidence to retain | Review or test trigger |
|---|---|---|---|---|
| Technology life cycle | Inventory hardware and software, record support dates, and replace unsupported assets according to risk. | IT owner | Asset inventory and patch report | Vendor end-of-support notice or failed patch |
| Passwords and authentication | Use unique accounts, block compromised passwords, support password managers, apply rate limiting, and require MFA for sensitive access. | Identity administrator | Authentication configuration and access report | Compromise, role change, or control review |
| Backups | Back up critical data, maintain an offline or immutable copy, and test restoration. | IT operations | Backup log and restore-test record | Documented schedule or major system change |
| Malware protection | Manage endpoint protection centrally and define isolation, investigation, and return-to-service steps. | Security or IT owner | Coverage report and incident record | Alert, disabled protection, or subscription lapse |
| Mobile devices and AI tools | Define approved devices and services, prohibited data classes, encryption, screen locks, and lost-device response. | IT and HR | Device inventory and employee acknowledgment | Lost device, new service, or policy exception |
| Communication and training | Train staff on current rules and incident reporting, then record acknowledgment and participation. | HR and policy owner | Training roster and signed acknowledgment | New hire, policy revision, or recurring training date |
| Access control | Grant access by role, remove access promptly, and review privileged and shared access. | System owner | Approval, offboarding, and review logs | Role change, departure, or scheduled review |
| Contingency planning | Set recovery objectives and maintain offline recovery instructions and contact details. | Business continuity owner | Recovery plan and exercise record | Exercise, supplier change, or system change |
| Network protection | Maintain firewalls, secure wireless networks, restrict remote access, and control DNS transfers. | Network administrator | Configuration backup and review report | Configuration change, alert, or scheduled review |
| Audit and improvement | Review logs, verify patching, assess vulnerabilities, and track corrective actions. | Security or risk owner | Audit findings and remediation log | Incident, material change, or risk-based assessment date |
Frequently Asked Questions
What should an information security policy actually contain?
At minimum: scope and who it applies to, acceptable use of company devices and accounts, password and multi-factor authentication rules, role-based access, mobile and remote-work rules, backup and recovery requirements, patching and asset-life-cycle expectations, incident reporting steps, and a named owner and review trigger for each control.
How often should employees be forced to change passwords?
Do not require routine calendar-driven password changes. Require long passwords, screen new choices against compromised-password lists, support password managers, turn on multi-factor authentication for sensitive access, and require a change when there is evidence of compromise.
How often should we test our backups?
Test real restoration on a documented cadence based on recovery needs and after material system changes. Include a restore to an alternate environment when practical, keep at least one copy offline or immutable, and record who performed the test, whether it succeeded, and how long it took.
Does a small business really need a written security policy?
Yes. A written policy assigns ownership, makes rules consistent, supports employee training, and gives the business a record of the controls it expects people to follow. Keep it concise enough to use, but detailed enough to define responsibilities, evidence, and incident-reporting steps.