WABI-COMP-IRR-001·v1.0·2026-11-22

Incident Response Runbook

Operated by Tek Asia Sdn Bhd · SSM 202501011675 (1613089-U) · DPO [email protected]

This runbook is the standing-orders document for any suspected security incident or personal data breach at Tek Asia Sdn Bhd. It defines who decides, who notifies whom, by when. Every engineer with production access is expected to know this procedure cold.

1 · Severity ladder

Severity is set by the on-call engineer at first sighting and may be re-classified by the Incident Commander.

SEVDefinitionPage
SEV-1Confirmed personal-data exfiltration · cross-tenant data leak · production database compromise · auth bypass · ransomwareImmediate — DPO + CTO + on-call
SEV-2Suspected breach awaiting verification · full service outage > 15 min · auth degradation · webhook signature failures > 1% rateOn-call + DPO within 15 min
SEV-3Single-tenant data integrity issue · degraded performance · failed sub-processor (LLM provider down) · single user account compromiseOn-call; DPO informed in daily standup
SEV-4Suspicious activity pattern · failed brute-force attempts (already throttled) · low-impact bugLogged for review; no immediate page

2 · Roles

  • Incident Commander (IC): the most senior engineer on-scene; owns the response, makes call/no-call decisions, runs the timeline.
  • Data Protection Officer (DPO): owns regulator and customer notification timing. [email protected].
  • Communications Lead: drafts customer messaging, updates status page, coordinates support.
  • Scribe: takes the timeline in #incident-response channel; nothing happens that isn't logged.

3 · The clock — PDPA 2024 amendment

Under the PDPA Amendment Act A1709 (in force 2025), data breach notification timelines are statutory. Miss them and the company faces fines up to RM 1,000,000 and/or imprisonment.

To the PDPC (regulator)
72 hours
from becoming aware of the breach
To affected individuals
7 days
from confirmation of significant-harm breach
To affected tenants
72 hours (contractual)
from confirmation
Internal post-incident review
14 days
from incident closure

4 · Response phases

4.1 Detect

Sources: Sentry alerts, Postgres anomaly alerts, audit-log scans, rate-limiter trips, tenant reports, security researcher reports sent to [email protected]. Any of these can open an incident.

4.2 Triage (first 15 minutes)

  1. On-call opens #incident-NNNN in the team channel.
  2. Sets initial SEV.
  3. Pages IC and (if SEV-1/2) DPO.
  4. Starts the timeline log — every action timestamped.
  5. Decides: is personal data involved? If yes → assume regulatory clock has started, even if not confirmed.

4.3 Contain

  • Rotate compromised credentials (Meta tokens, JWT signing key, Stripe API key).
  • Revoke active sessions if a tenant is implicated.
  • Disable affected sub-processor integration if the leak is upstream.
  • Block source IPs at the gateway if appropriate.
  • Do not delete logs — they are evidence.

4.4 Investigate

  • Establish scope: which tenant(s), which data categories, how many records.
  • Establish root cause (5 whys).
  • Establish exfiltration likelihood: was data merely accessible, or actually accessed?
  • Preserve audit logs, webhook delivery records, Postgres WAL.

4.5 Notify

DPO owns the call. If personal data was breached AND there is a real risk of harm (financial loss, reputational damage, identity theft):

  • PDPC notification within 72 hours — template at §6 below.
  • Tenant notification within 72 hours — email + dashboard banner.
  • End-user notification via the affected tenant (the tenant is the controller of those end users; we, as processor, supply the facts they need to notify).

4.6 Recover

  • Restore service to pre-incident state.
  • Verify the vulnerability is closed (regression test).
  • Update status page with resolution.
  • Close the incident channel; archive timeline.

4.7 Post-incident review (within 14 days)

  • Blameless retro with all responders.
  • Root cause analysis written up.
  • Action items filed in the issue tracker with owners + dates.
  • Runbook updated if the response surfaced gaps.

5 · Drills

Tabletop exercise once per quarter. Live restore-from-backup drill twice per year. Drill outcomes logged and reviewed by the DPO.

6 · PDPC notification template

To: [email protected]
Subject: Personal Data Breach Notification — Tek Asia Sdn Bhd — [Incident ID]

1. Reporting entity
   Name: Tek Asia Sdn Bhd
   SSM: 202501011675 (1613089-U)
   Address: Level 9, Integra Tower, The Intermark, 348 Jalan Tun Razak, 50400 Kuala Lumpur, Malaysia
   DPO: [email protected]

2. Description of the breach
   [What happened, when, how detected]

3. Nature of personal data affected
   [Categories: e.g. phone numbers, message content]

4. Number of data subjects affected
   [Approximate count + identification method]

5. Likely consequences
   [Harm assessment]

6. Measures taken / proposed
   [Containment, notification, prevention]

7. Contact point for further info
   [email protected]

7 · Ownership

Owner: Data Protection Officer ([email protected]).
Review cadence: every 6 months, or after every SEV-1/SEV-2 incident.