Information security policy
The top-level policy that sets management's expectations and responsibilities.
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.
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.
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.
The top-level policy that sets management's expectations and responsibilities.
Acceptable use, access control, password and multi-factor authentication, backup, remote working and supplier security, as relevant to you.
Roles, severity levels, escalation steps, evidence handling and communication.
When the PDPA clock starts, who decides, and the 72-hour and 7-day steps.
Internal and external contacts, including out-of-band options if email is down.
Version control, an owner for each document and a yearly review date.
Written after understanding how you work.
Written evidence you can share.
Plain language, short and usable.
Decisions are made in advance.
Your team reviews rather than drafts.
Review your systems, existing documents and obligations.
Write the policy set and response plan.
Your team comments and we revise.
Management signs off.
Walk through the documents and agree owners and review dates.
Information security policy and the supporting policies agreed at scoping.
Roles, escalation, communication and breach notification steps.
Including out-of-band contacts.
Owners, versions and review dates.