NC4

Transparent Incident Communication

Minimal communication framework for incident updates, safety messaging, and trust protection.

Public Safety Update Template

We detected unauthorized activity affecting one of our digital channels.

Verification is ongoing and updates will be shared through official channels only.

Users should reset passwords and avoid unverified links/messages.

Next update will be issued at [time/date].

Institutional Incident Notice Template

An incident was identified at [time] affecting [service/system].

Containment and restoration activities are active.

Users are advised to enable MFA and monitor accounts.

A consolidated update will be released at [time/date].

CII Coordinated Notice Template

A cybersecurity incident affecting [critical service] is under active containment.

Continuity safeguards and agency coordination are in progress.

Stakeholders will receive structured status updates.

Sensitive technical indicators are shared through secure channels only.

Before issuing an update

  • State verified facts only.
  • Provide clear user protection actions.
  • Declare next update time and source channel.
  • Coordinate legal, technical, and management approval.

Protect sensitive information

  • Do not speculate on root cause or attribution before verification.
  • Do not publish sensitive indicators, credentials, or exploitable details publicly.
  • Do not use multiple unofficial communication channels.

Follow-up

NC4 can acknowledge incoming reports quickly with a tracking reference. Detailed follow-up depends on incident severity, national impact, and active response workload.