A cybersecurity policy that lives in a signed PDF changes nothing. The useful version names who does what, what evidence is kept, how often it is checked and who signs it off. It is a working document that a small business can run without a security department.
This checklist is built for that purpose. Each line has an owner, a piece of evidence, a frequency and a sign-off. Delete what does not apply, record the exception and set a review date. The result is not a certification and not legal advice, but it gives an auditor, a bank or a customer a clear view of how security is actually managed.
Running the checklist as a working document
Assign the roles before the first review: policy owner, IT or operations lead, finance lead, HR lead and incident lead. In a small company one person may hold several roles, which is acceptable if the conflict is recorded and reviewed. Store evidence in one folder with the date in each file name, and keep an exceptions log for controls that cannot be met yet. If a control has no evidence, treat it as not implemented, even if everyone believes it is.
A 30-day start sequence
- Week 1: appoint the owners, draft the scope and open the exceptions log.
- Week 2: verify accounts, multi-factor authentication and leaver access; fix the highest-risk gaps first.
- Week 3: confirm the backup scope and run a restore test, recording what was restored and how long it took.
- Week 4: approve version one, set the review dates and brief staff on how to report a suspected incident.
1. Scope, ownership and review
| Check | Owner | Evidence | Frequency | Sign-off |
| Name a policy owner and a deputy | Managing director | Appointment note | Annual | Managing director |
| List systems, data and premises in scope | Policy owner | Asset and data register | Annual | Policy owner |
| Approve the review cycle and current version | Policy owner | Signed policy | Annual or on change | Managing director |
| Record exceptions with an expiry date | Policy owner | Exceptions log | Quarterly | Managing director |
2. Accounts and access
| Check | Owner | Evidence | Frequency | Sign-off |
| Use unique accounts and remove shared logins | IT lead | User list | Quarterly | Policy owner |
| Require multi-factor authentication on email, banking, admin and cloud | IT lead | MFA status report | Quarterly | Policy owner |
| Grant least privilege and review access by role | System owners | Role matrix | Quarterly | Policy owner |
| Remove leaver access within one working day | HR and IT | Offboarding ticket | On change | HR lead |
3. Devices and software
| Check | Owner | Evidence | Frequency | Sign-off |
| Maintain an inventory of laptops, phones and servers | IT lead | Asset register | Monthly | Policy owner |
| Patch operating systems and browsers | IT lead | Patch report | Monthly | IT lead |
| Enable disk encryption and automatic screen lock | IT lead | Device check | Annual | Policy owner |
| Run endpoint protection and limit administrator rights | IT lead | Console report | Monthly | IT lead |
4. Data, backup and recovery
| Check | Owner | Evidence | Frequency | Sign-off |
| Classify data and map where it is stored | Data owner | Data map | Annual | Policy owner |
| Back up the systems that the business needs | IT lead | Backup log | Daily | IT lead |
| Restore a sample and record the result | IT lead | Restore record | Quarterly | Policy owner |
| Retain and dispose of records securely | Data owner | Disposal log | Annual | Policy owner |
5. Email, web and payments
| Check | Owner | Evidence | Frequency | Sign-off |
| Provide a phishing report button and a response path | IT lead | Report queue | Quarterly | Policy owner |
| Verify changes to payment details by callback | Finance lead | Procedure and sample | On change | Managing director |
| Keep browser and email filtering current | IT lead | Configuration evidence | Quarterly | IT lead |
| Set rules for personal devices and social accounts | HR lead | Signed acknowledgement | Annual | HR lead |
6. Vendors and cloud services
| Check | Owner | Evidence | Frequency | Sign-off |
| Keep a vendor register with the data each one can access | Operations lead | Vendor register | Annual | Policy owner |
| Include security and breach terms in contracts | Finance and legal | Signed contract | On contract | Managing director |
| Test data return and access removal at exit | Operations lead | Exit checklist | On exit | Policy owner |
| Review critical vendors against the register | Operations lead | Review note | Annual | Managing director |
7. Incident response
| Check | Owner | Evidence | Frequency | Sign-off |
| Name an incident lead and a contact tree | Managing director | Contact sheet | Quarterly | Managing director |
| Define severity levels and response times | Incident lead | Incident playbook | Annual | Managing director |
| Preserve evidence and log decisions | Incident lead | Incident log | On incident | Incident lead |
| Decide on notification with legal advice | Managing director | Advice record | On incident | Managing director |
8. Training and assurance
| Check | Owner | Evidence | Frequency | Sign-off |
| Run onboarding and annual awareness training | HR lead | Attendance record | Annual | HR lead |
| Train finance, IT and managers on their specific duties | Policy owner | Training record | Annual | Managing director |
| Run a tabletop incident exercise | Incident lead | Exercise report | Annual | Managing director |
| Report security measures to management | Policy owner | Quarterly report | Quarterly | Managing director |
For personal data, add the notice, consent and retention position to the scope section and take local legal advice where the business operates across borders. The policy should say where those records are kept, not merely that they exist.
Sign-off block
- Policy version: number and date of the approved version.
- Approved by: name and role of the managing director or board delegate.
- Next review: a fixed date, not "annually" in a diary nobody owns.
- Exceptions accepted: the control, the reason, the compensating measure and the expiry date.
- Evidence location: the folder or system where the records in this checklist are kept.
Keeping the policy alive
Review the full checklist at the fixed date, but review access, backups and incidents at the frequencies shown. When a control fails, record the failure, the temporary measure and the date of the next test. Report exceptions to management rather than hiding them; an honest exception is easier to audit than a fictional pass. A policy that is never tested is a hope with a version number.
How we support the policy
Our Managed Technology & Cybersecurity division helps small businesses turn a policy into working controls, from identity and backups to monitoring and incident readiness. The pricing page explains how an assessment and an ongoing retainer are scoped. For the human side of the same problem, read what phishing prevention for employees costs in Bangladesh.
Sources
- NIST, Cybersecurity Framework 2.0, accessed 17 November 2026.
- NIST SP 800-50, Building an IT Security Awareness and Training Program, accessed 17 November 2026.
- UK National Cyber Security Centre, Small business guidance: response and recovery, accessed 17 November 2026.
- DataGuidance, Bangladesh jurisdiction overview, accessed 17 November 2026.
- NIST SP 800-63B, Digital Identity Guidelines: Authentication and Lifecycle Management, accessed 17 November 2026.
E
EncryptTechBD
Written by the EncryptTechBD delivery team. We publish only what we can defend in a client meeting.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.