View source for Procedure: CC-Blast Data Breach Prevention

= Procedure: CC-Blast Data Breach Prevention =

== Overview ==

A '''CC-Blast Data Breach''' occurs when someone mistakenly uses the '''CC (Carbon Copy)''' field instead of '''BCC (Blind Carbon Copy)''' when sending emails to multiple recipients. This exposes the personal email addresses of all recipients to each other.

This is considered a '''personal data breach''' under the '''Data Privacy Act of 2012''' and must be handled with urgency, professionalism, and compliance with the organization's Privacy Manual.

== Key Terms and Definitions ==

* '''CC Blast''' – Accidentally exposing multiple recipients' email addresses by placing them in the CC or To field instead of BCC.
* '''BCC Blast''' – Correctly sending a bulk email using the BCC field, which hides all recipient email addresses.
* '''Reply Storm (Reply-All Storm)''' – When recipients start replying-all in a CC blast chain, causing an uncontrollable cascade of unnecessary or sensitive emails to all parties.
* '''Clawback Limitation''' – Once personal emails are exposed in a CC blast, they cannot be taken back; the data has already been leaked.

== Precautionary Measures ==

# '''Always Check Before Sending:''' When emailing multiple external contacts (students, clients, partners, etc.), '''use BCC instead of CC'''.
# '''Tagging Personal Emails:''' Configure email systems to '''alert or warn''' when sending to recipients tagged as personal email domains (e.g., Gmail, Yahoo, Hotmail). Business/work accounts should be tagged separately.
# '''Use Templates:''' Provide standardized email templates for OJTs, interns, and staff with the '''BCC field pre-configured'''.
# '''Two-Person Verification:''' For mass external communications, have another team member verify that recipients are properly placed in the BCC field before sending.

== Response Procedure (If a CC-Blast Data Breach Happens) ==

# '''Do Not Reply-All:''' Immediately stop and '''avoid adding to the breach'''.
# '''Send a BCC Notification:''' Draft a short apology and clarification email to all recipients, but '''send it via BCC''' to prevent further exposure. Include instructions to avoid replying to the group email.
# '''Notify Management:''' Escalate the incident to the '''Privacy Officer''' and '''Data Protection Officer (DPO)'''.
# '''Mandatory Reporting:''' Evaluate the incident. If it meets reporting criteria, '''notify the National Privacy Commission (NPC)''' within the prescribed timeframe.
# '''Document the Incident:''' Record the event details (number of recipients, exposed emails, response actions, corrective measures) in the '''Privacy Incident Register'''.

== Accountability and Training ==

* '''Staff and OJTs''' must undergo periodic reminders and training distinguishing '''CC vs. BCC usage'''.
* '''Supervisors''' must enforce the policy: ''"External personal emails = BCC only."''
* '''IT/Admin''' should deploy or configure systems that:
** Alert when sending to large groups of external addresses.
** Warn or block when multiple personal emails are detected in the CC field.
** Suggest converting CCs to BCCs automatically when thresholds are exceeded.

== Conclusion ==

A CC-blast is a preventable human error that exposes personal data and risks compliance violations. Once it occurs, '''the exposure cannot be undone''', but '''swift containment using BCC communication and incident reporting''' can reduce further harm. The long-term solution lies in a '''combination of staff awareness, training, and technical safeguards'''.

[[Category:Security]]
[[Category:Data Privacy]]
[[Category:Procedures]]
[[Category:Comfac]]