ClearBreach

In the middle of a breach?

ClearBreach shows whether you must report, to whom and by when, under each law that applies, and writes the reports.

What to do now →

← Quick reference guides·All breach response guides →

Your SituationWe had a privacy incident →

PIPEDAAB PIPABC PIPAAll sectors

Cloud Storage Misconfiguration, Quick Reference Guide

By Yong DuPublished Reviewed

Share on LinkedIn

Immediate steps when an S3 bucket, Azure blob, or cloud container is accidentally left publicly accessible, PIPEDA, Alberta PIPA, and BC PIPA.

Typical verdict

RROSH present in most cases, sensitive data in a public bucket is accessible to automated scanners within hours; access logs are often unavailable

Reporting deadline

As soon as feasible (PIPEDA) or without unreasonable delay (Alberta PIPA) once RROSH is determined, do not wait to confirm unauthorized access if access logs are absent

Documents you will need

  • → Internal Incident Record (required under PIPEDA; good practice otherwise)
  • → Cloud configuration history showing when bucket was made public (if available)
  • → Access log export for the exposure window (if logging was enabled)
  • → OPC PIPEDA Breach Report (if PIPEDA RROSH triggered)
  • → OIPC Alberta Notification Form (if AB PIPA applies)
  • → OIPC BC voluntary report (optional, if BC PIPA applies)
  • → Individual Notification Letter
  • → AB PIPA Individual Notice s.19.1 (if AB PIPA individual notification required)

Do not

  • ✕ Make the bucket private and treat the matter as closed, remediation is step one, not the end of your response
  • ✕ Assume no access occurred because you have no access logs, absent logs mean unknown access, not confirmed no-access
  • ✕ Delete the bucket or its contents before completing the breach record, they are evidence
  • ✕ Use your discovery date as the exposure start date, the exposure started when the misconfiguration occurred, which may be weeks or months earlier

First 30 minutes

  • Preserve evidence before changing any configuration: screenshot the current access settings, note the bucket name and region, confirm that any existing access logs are saved
  • Make the bucket private, after evidence is preserved
  • Pull your cloud configuration history (AWS CloudTrail, Azure Activity Log, Google Cloud Audit Logs) to identify when the bucket was made public
  • Designate an incident lead, all communications and decisions route through them
  • Record the exact date and time you discovered the misconfiguration, this starts your response clock

Within 24 hours

  • Determine the exposure window: from when the bucket was misconfigured to when you restricted it
  • Inventory every file and object stored in the bucket during the exposure window: what categories of personal information, whose information (customers, employees, patients), how many individuals
  • Check whether access logging was enabled, if yes, pull all logs for the exposure window; if no, document that access logs are unavailable
  • Search engine check: query the bucket URL or file names to determine whether any content was indexed during the exposure window
  • Identify which provinces' residents are affected, this determines whether AB PIPA and BC PIPA apply in addition to PIPEDA
  • Begin your ClearBreach assessment, do not wait for full log analysis to start

Within 72 hours

  • Complete your RROSH assessment in ClearBreach and review your verdict
  • If PIPEDA RROSH threshold is met: file OPC Breach Report as soon as feasible, do not wait until access is confirmed if logs are unavailable
  • If Alberta PIPA applies and RROSH is met: notify OIPC Alberta (breachnotice@oipc.ab.ca) and affected individuals simultaneously
  • If BC PIPA applies: BC PIPA has no breach reporting duty: a report to the OIPC BC is voluntary and encouraged for significant breaches, and the BC Commissioner expects affected people to be told directly where there is a risk of harm
  • Send individual notifications: explain that cloud storage was accidentally left publicly accessible, what data was accessible, the exposure period, and what individuals can do to protect themselves
  • If a security researcher or third party reported the finding, acknowledge their disclosure appropriately, do not make any public statement before individuals are notified

Ongoing, until resolution

  • Update your Internal Incident Record as log analysis or third-party disclosure adds new information, if material new facts emerge after notifying, send follow-up notifications to regulators and affected individuals
  • Confirm the bucket remains private and no other storage containers in your environment are misconfigured
  • Monitor for signs of data misuse: credential stuffing, phishing using exposed contact data, identity fraud reports from affected individuals
  • Retain all records, configuration history, access logs, internal assessment records, notifications sent, for 24 months minimum from date of discovery
  • Conduct a full cloud storage audit: identify all buckets and containers, verify access controls, enable access logging going forward, implement an infrastructure policy to prevent public buckets

Alberta PIPA, specific steps

  • If the exposed data came from your Alberta activity, file your OIPC Alberta notification and send individual notices on the same day, this qualifies the file for the streamlined review track and a private closing letter instead of a full investigation
  • Use OIPC Alberta's official notification form itself, not an email summary of the incident
  • Attach the AB PIPA Individual Notice (s.19.1) as Section D of that form, not as a separate document
  • Address the completed package to breachnotice@oipc.ab.ca

BC PIPA, specific steps

  • BC PIPA applies to your activity in BC, wherever the bucket is hosted. Serving BC clients from another province is interprovincial and falls under PIPEDA
  • If the exposure window was long or you have no access logs to rule anything out, consider a voluntary report to the OIPC BC; BC PIPA has no reporting duty, but a report puts a good-faith record on file before a complaint does
  • If you report, use the OIPC BC's online breach reporting form or privacy breach checklist (oipc.bc.ca)
  • Where there is a risk of harm, the BC Commissioner expects each affected person to be told directly; a website notice is for when direct notice is not possible

MSPs, if managing this for a client

  • If you administer the client's cloud environment, hand over the full technical picture immediately: which bucket, how long it was public, what was in it, and whether any logging exists, the client cannot start their own assessment without these specifics
  • Your client is the accountable party for their own individuals' data, you're supplying the facts their RROSH determination depends on, not making the call yourself
  • Set up the assessment under your MSP account so the client's determination is built on your findings rather than a second-hand summary
  • Where the misconfiguration traces back to your own deployment or configuration work, note that separately, it's a contractual liability question between you and the client, distinct from what they owe their affected individuals under PIPA

Privacy case of the month

Once a month, a five-minute read: a real case a Canadian privacy commissioner investigated, what went wrong, and what to check in your own organization so it doesn't happen to you. Written for organizations under federal, Alberta and BC privacy law. Not written for Quebec.

We send one email to confirm. Nothing else arrives until you confirm, and an unconfirmed address is deleted after 7 days. Sent by ClearBreach Technologies Inc. Mailing address and contact details · Privacy policy

This guide is educational and does not constitute legal advice. It is grounded in the text of PIPEDA, Alberta PIPA, and BC PIPA and published guidance from the OPC, OIPC Alberta, and OIPC BC. If your situation involves regulatory investigation, litigation risk, or circumstances not addressed here, engage a qualified privacy lawyer.

Want the full background?

Read the educational playbook for this scenario.

Read playbook →

Find out what this incident requires of you

See whether you must report, to whom and by when, under each privacy law that applies to you.

How ClearBreach handles a breach →

See plans and pricing →