Cybersecurity Policy and Incident Response Plan Writing

Cybersecurity policy and incident response plan writing is the preparation of the written rules and the written response plan an organisation needs, drafted around how your business actually works, not copied from a template.

Documents written for your organisation PDPA breach notification steps built into the response plan Documentation only: no drills or technical testing

Policy and Incident Response Plan Writing

What it is

A documentation service that writes or updates your core cybersecurity policies and an incident response plan, with roles, escalation steps and contact sheets, and hands them over ready for management approval.

Why organisations need it

Customers, insurers, auditors and regulators increasingly ask to see written policies and a response plan. A template downloaded from the internet rarely matches your systems, and an out-of-date plan fails when it is needed. Written documents also give staff and IT clear rules and give management something concrete to approve. The incident response plan matters most when an attack starts, so it must name who decides, who is called and when personal data breach notification starts.

What the engagement covers

Information security policy

The top-level policy that sets management's expectations and responsibilities.

Core supporting policies

Acceptable use, access control, password and multi-factor authentication, backup, remote working and supplier security, as relevant to you.

Incident response plan

Roles, severity levels, escalation steps, evidence handling and communication.

Breach notification steps

When the PDPA clock starts, who decides, and the 72-hour and 7-day steps.

Contact sheet

Internal and external contacts, including out-of-band options if email is down.

Approval and review

Version control, an owner for each document and a yearly review date.

What the business gets out of it

Documents that match reality

Written after understanding how you work.

Ready for questionnaires and audits

Written evidence you can share.

Clear rules for staff and IT

Plain language, short and usable.

A response plan people can follow

Decisions are made in advance.

Less effort for your team

Your team reviews rather than drafts.

How it works

How the engagement runs

01

Discovery

Review your systems, existing documents and obligations.

02

Drafting

Write the policy set and response plan.

03

Review

Your team comments and we revise.

04

Approval

Management signs off.

05

Hand-over

Walk through the documents and agree owners and review dates.

Deliverables

What you receive

Policy set

Information security policy and the supporting policies agreed at scoping.

Incident response plan

Roles, escalation, communication and breach notification steps.

Contact sheet

Including out-of-band contacts.

Document register

Owners, versions and review dates.

Who it is for

Who this is built for

Industries

Financial servicesHealthcare and clinicsEducationManufacturingLogisticsRetail and e-commerceProfessional servicesPublic sector bodies

Company sizes

SMEsMid-marketLarge enterpriseGroup structures

Departments

ManagementIT and securityComplianceLegalHR
FAQ

FAQ

No. This service is documentation only. A facilitated tabletop exercise is available separately through our incident response planning service.

Yes, we can align the structure to ISO/IEC 27001 controls where you plan to certify later. We do not certify, and a certificate comes only from an accredited certification body.

Usually three to five weeks, depending on how many policies are in scope and how quickly your team can review drafts.

We include the requirements you tell us apply, such as your sector regulator's expectations. We do not give legal advice, and your counsel should approve anything with legal effect.

Yes. We review the existing documents against how you operate today and update them.