Skip to content
EncryptTechBD
Home Industries Our Work Blog Pricing About Contact Discuss Your Project
বাংলা (BN)
Privacy & Compliance 5 min read

Cybersecurity policy for small business: a working checklist

A practical cybersecurity policy checklist for small businesses, with owners, evidence, frequency and sign-off for each control, plus an approval page.

E
EncryptTechBD · 0 comments
Woman writing in a notebook at a desk
Photo: Rawpixel

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

  1. Week 1: appoint the owners, draft the scope and open the exceptions log.
  2. Week 2: verify accounts, multi-factor authentication and leaver access; fix the highest-risk gaps first.
  3. Week 3: confirm the backup scope and run a restore test, recording what was restored and how long it took.
  4. Week 4: approve version one, set the review dates and brief staff on how to report a suspected incident.

1. Scope, ownership and review

CheckOwnerEvidenceFrequencySign-off
Name a policy owner and a deputyManaging directorAppointment noteAnnualManaging director
List systems, data and premises in scopePolicy ownerAsset and data registerAnnualPolicy owner
Approve the review cycle and current versionPolicy ownerSigned policyAnnual or on changeManaging director
Record exceptions with an expiry datePolicy ownerExceptions logQuarterlyManaging director

2. Accounts and access

CheckOwnerEvidenceFrequencySign-off
Use unique accounts and remove shared loginsIT leadUser listQuarterlyPolicy owner
Require multi-factor authentication on email, banking, admin and cloudIT leadMFA status reportQuarterlyPolicy owner
Grant least privilege and review access by roleSystem ownersRole matrixQuarterlyPolicy owner
Remove leaver access within one working dayHR and ITOffboarding ticketOn changeHR lead

3. Devices and software

CheckOwnerEvidenceFrequencySign-off
Maintain an inventory of laptops, phones and serversIT leadAsset registerMonthlyPolicy owner
Patch operating systems and browsersIT leadPatch reportMonthlyIT lead
Enable disk encryption and automatic screen lockIT leadDevice checkAnnualPolicy owner
Run endpoint protection and limit administrator rightsIT leadConsole reportMonthlyIT lead

4. Data, backup and recovery

CheckOwnerEvidenceFrequencySign-off
Classify data and map where it is storedData ownerData mapAnnualPolicy owner
Back up the systems that the business needsIT leadBackup logDailyIT lead
Restore a sample and record the resultIT leadRestore recordQuarterlyPolicy owner
Retain and dispose of records securelyData ownerDisposal logAnnualPolicy owner

5. Email, web and payments

CheckOwnerEvidenceFrequencySign-off
Provide a phishing report button and a response pathIT leadReport queueQuarterlyPolicy owner
Verify changes to payment details by callbackFinance leadProcedure and sampleOn changeManaging director
Keep browser and email filtering currentIT leadConfiguration evidenceQuarterlyIT lead
Set rules for personal devices and social accountsHR leadSigned acknowledgementAnnualHR lead

6. Vendors and cloud services

CheckOwnerEvidenceFrequencySign-off
Keep a vendor register with the data each one can accessOperations leadVendor registerAnnualPolicy owner
Include security and breach terms in contractsFinance and legalSigned contractOn contractManaging director
Test data return and access removal at exitOperations leadExit checklistOn exitPolicy owner
Review critical vendors against the registerOperations leadReview noteAnnualManaging director

7. Incident response

CheckOwnerEvidenceFrequencySign-off
Name an incident lead and a contact treeManaging directorContact sheetQuarterlyManaging director
Define severity levels and response timesIncident leadIncident playbookAnnualManaging director
Preserve evidence and log decisionsIncident leadIncident logOn incidentIncident lead
Decide on notification with legal adviceManaging directorAdvice recordOn incidentManaging director

8. Training and assurance

CheckOwnerEvidenceFrequencySign-off
Run onboarding and annual awareness trainingHR leadAttendance recordAnnualHR lead
Train finance, IT and managers on their specific dutiesPolicy ownerTraining recordAnnualManaging director
Run a tabletop incident exerciseIncident leadExercise reportAnnualManaging director
Report security measures to managementPolicy ownerQuarterly reportQuarterlyManaging 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

Services that deliver this

Want this implemented properly?

Pricing →

Every engagement starts with a written scope. If a requirement is outside it, we quote it separately before starting.

Responses (0)

No comments yet. Add the first one below.

Leave a response

Your email address will not be published. Required fields are marked *.

Keep reading

More field notes