On this page
Your SituationWe had a privacy incident →
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.
Cloud Storage Misconfiguration, What Canadian Organizations Must Do
By Yong Du · Updated June 14, 2026
A misconfigured cloud storage bucket triggers PIPEDA and PIPA obligations even without evidence of unauthorized access, exposure alone is enough.
⚡ In an active breach right now?
Use the quick reference guide, built for use during an incident.
This playbook 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.
A cloud storage folder left open to the public is a breach even if nobody is known to have looked. Note the settings and save any logs before you lock it, then find out what it held and for how long it was open. Sensitive data left open more than a couple of days has very likely been found by automated scanners.
Which laws apply
| Jurisdiction | Applies when | Regulator |
|---|---|---|
| PIPEDA | The misconfigured storage held personal information used in commercial activity; or the affected individuals are in provinces without substantially similar legislation (Ontario, Manitoba, New Brunswick, and others) | Office of the Privacy Commissioner of Canada (OPC), priv.gc.ca |
| Alberta PIPA | The breach involves your organization's activity in Alberta, including its employees there | OIPC Alberta, oipc.ab.ca / breachnotice@oipc.ab.ca |
| BC PIPA | The breach involves your organization's activity in BC, including its employees there | OIPC BC, oipc.bc.ca |
More than one of these can apply. If the threshold is met, report separately to the OPC and the OIPC Alberta where each applies; a report to the OIPC BC is voluntary.
What makes this scenario different
In every other breach scenario covered in these playbooks, an external party initiates the incident, a phishing email, a ransomware deployment, an employee acting outside their authorization. In a cloud storage misconfiguration, your organization caused the exposure. No attacker was required.
This creates four features that distinguish this scenario from all others.
You may not know how long the data was exposed. A misconfigured S3 bucket or Azure blob storage container can remain publicly accessible for days, months, or years before anyone notices. Cloud storage configuration errors often go undetected because they generate no alerts by default, the data is simply accessible to anyone who knows the URL or runs a cloud scanning tool. When discovery happens, the first question, how long was this public?, is often the hardest to answer.
Someone else usually finds it first. Organizations most often learn of an open storage folder from a security researcher's scan, a threat intelligence service, a journalist, a customer or competitor who stumbled on the link, or an alert that the data is for sale. If you are reading this because a security researcher just emailed you, that email is evidence that your data was accessible and was found. The question of whether it was also accessed by someone with malicious intent is now the relevant question for your RROSH assessment, not whether it was accessible.
Access logs are often not enabled. Cloud providers do not enable access logging on storage buckets by default in most configurations. This means that even after you discover the misconfiguration, you may have no record of which IP addresses accessed which files during the exposure window. The absence of logs does not mean no access occurred, it means you have no evidence either way. Your RROSH assessment must account for this honestly: unknown access to sensitive data is not the same as confirmed no-access.
The data may already be indexed or archived. Search engine crawlers, web archive services, and automated scanning tools index publicly accessible URLs continuously. If the bucket was public for more than a few days, copies of the exposed files may exist in places you cannot reach. Restricting the bucket does not un-expose data that was already cached, downloaded, or indexed.
Immediate steps, this scenario specifically
1. Restrict the bucket immediately, but preserve evidence first. Before you change any setting, do two things. Record the current settings exactly: who has access, what permissions exist, and when they last changed. And make sure any access logs are saved. Then restrict the bucket to private access. Do not delete the bucket or its contents, they are evidence.
2. Determine the exposure window. Check your infrastructure configuration history (CloudTrail in AWS, Activity Log in Azure, Audit Logs in Google Cloud) to identify when the bucket was made public. If you use infrastructure-as-code, check your version control history for the configuration change. The exposure window runs from the date the bucket was misconfigured to the date you restricted it. Document this date range precisely. It defines the scope of your RROSH assessment.
3. Inventory what data the bucket held. List every file, folder, or object that was stored in the bucket during the exposure window. Find out what kinds of personal information were there, such as financial records, health data, SINs, passwords, government ID or contact details. Then whose it was, how many people, and whether any file held a mix that together enables identity theft.
4. Check whether access logs exist. If access logging was enabled on the bucket, pull the logs for the entire exposure window. If logs were not enabled, document that explicitly, it is relevant to your assessment and to regulators. If the bucket was managed by a cloud provider, contact them to determine whether any logging exists at the platform level even if application-level logging was off.
5. Do not issue any public statement yet. Premature or inaccurate public disclosure before you have completed your assessment creates confusion, may be legally problematic, and may undermine individual notification. Complete your RROSH assessment first.
What drives RROSH in this scenario
Here the test of a real risk of significant harm (RROSH) turns on two things: what data was exposed, and how likely it is that someone reached it while it was open.
Factors that push toward RROSH:
- The bucket contained sensitive categories: health data, financial records, SINs, passwords, government-issued ID numbers, or information about minors
- The bucket contained enabling combinations: name + date of birth + address + SIN is more dangerous than any field alone
- The bucket was public for more than a few days, public cloud storage is scanned by automated tools continuously
- A third party (researcher, journalist, competitor) found and reported the bucket, confirming active discovery
- The bucket was indexed by a search engine or web archive during the exposure window
- Access logs show downloads of specific files
- The bucket contained employee records including banking information for payroll
Factors that push against RROSH:
- The bucket contained only generic non-identifying information: product documentation, marketing materials, aggregated statistics with no individual identifiers
- The exposure window was confirmed to be very short (hours) and access logs show no external access
- All files in the bucket were encrypted and encryption keys were not included in or accessible from the bucket
- The bucket held only publicly available information that conveyed no additional risk through aggregation
The no-access-log default: When access logs are absent, the RROSH assessment must account for the realistic probability of access given the exposure window and data sensitivity. For a bucket containing sensitive personal information that was public for more than 48 hours, the probability of access by an automated scanner is very high, not speculative. That probability, combined with the consequence if the data is misused, typically results in RROSH being present even without confirmed access.
Likely verdict range
| Scenario | Typical verdict |
|---|---|
| Bucket contained SINs, financial records, or health data; exposure window more than 48 hours | RROSH, sensitive data + high probability of access |
| Bucket contained employee records including banking or compensation details | RROSH, financial data combination |
| Security researcher or third party confirmed they accessed and viewed the files | RROSH, access confirmed |
| Bucket contained customer name, email, and phone number; short exposure window; logs show no external access | Case-by-case, depends on volume and whether data enables harm without additional context |
| Bucket contained internal documents with no personal information | No reporting obligation, but document the assessment and investigate the root cause |
| Bucket contained only publicly available content (e.g., a public website's static assets) | No reporting obligation, no personal information at risk |
| Bucket was public but all files were encrypted and keys were stored separately and were not compromised | Likely no reporting obligation, but confirm encryption scope before concluding |
Was your storage open long enough, with data sensitive enough, to need reporting? That is the decision ClearBreach makes, under PIPEDA, Alberta PIPA and BC PIPA at once. See it made on a real case →
Scenario-specific obligations and complications
If RROSH is determined:
- OPC notification (PIPEDA): Report to the Office of the Privacy Commissioner of Canada as soon as feasible after determining RROSH. Use the OPC breach report form at priv.gc.ca. The OPC does not require you to know the full scope before filing, file when RROSH is determined and supplement with additional information as your investigation continues.
- OIPC Alberta notification (AB PIPA): Notify the OIPC Alberta without unreasonable delay. Email breachnotice@oipc.ab.ca. Use the official OIPC Alberta notification form.
- OIPC BC (BC PIPA): No legal duty to report; a voluntary report is encouraged for a significant breach in your BC activity.
- Individual notification: Notify each affected individual directly (required under PIPEDA; in Alberta when the commissioner directs, and best sent with the report; expected in BC). The notice should describe what happened, what information was involved, what steps the organization is taking, and what the individual can do to protect themselves. For a cloud misconfiguration, this includes advising individuals to monitor their financial accounts and credit reports if financial or identity-enabling data was exposed.
If RROSH is not determined:
- No regulator notification required under PIPEDA or Alberta PIPA.
- No individual notification required.
- Internal breach record, required under PIPEDA and good practice otherwise: document the exposure window, data inventory, access log findings, and your RROSH assessment with reasoning.
- Fix the misconfiguration root cause: was this a manual error? A deployment pipeline failure? A missing infrastructure policy? The internal record should capture what failed and what was changed to prevent recurrence.
BC PIPA, voluntary reporting option. BC PIPA has no breach reporting or notification duty, so any report to the OIPC BC is voluntary. For a significant breach in your BC activity, the BC Commissioner encourages a report and expects the people affected to be told where there is a risk of harm. See BC PIPA Breach Reporting.
For Ontario organizations. Ontario has no provincial private-sector privacy legislation, PIPEDA is the applicable framework. Report to the OPC at priv.gc.ca. No separate provincial regulator report is required. See Ontario Data Breach Reporting Requirements.
Complications specific to this scenario:
The exposure window cannot be precisely determined. If your cloud environment does not log configuration changes with timestamps, you may not be able to confirm exactly when the bucket became public. In this case, use the earliest plausible date, the last known-private configuration or the creation date of the bucket, as your conservative exposure window start. Document the basis for your estimate. Regulators understand that configuration history is not always available; they expect you to use the most conservative reasonable estimate, not the most optimistic one.
The data was indexed by a search engine or web archive. If you discover the bucket URL appears in search engine results or a web archive like the Wayback Machine, the data was accessed by an automated crawler. This is confirmed access. It does not mean the data was accessed by a human with malicious intent, but it means the data exists in a form you cannot fully control. Note this in your individual notifications and advise individuals accordingly.
A security researcher disclosed the finding publicly before notifying you. Some security researchers disclose findings publicly before contacting the affected organization, or disclose simultaneously. If your misconfiguration is already public knowledge, individual notification becomes more urgent, affected individuals may be hearing about it from news sources before hearing from you. Accelerate your assessment and notification timeline accordingly.
The bucket contained files from multiple clients or customers. If you are a service provider and the bucket held data belonging to multiple client organizations, each client organization is the accountable party under PIPEDA and PIPA for their own individuals. You may have a contractual obligation to notify each client promptly. Each client then conducts their own RROSH assessment and determines their own notification obligations. Your obligation and theirs are separate.
Documents you will need
Regardless of RROSH determination:
- Internal breach record: date discovered, exposure window, bucket contents inventory, access log findings (or confirmation logs were not available), RROSH assessment and outcome, root cause, remediation steps taken
- Cloud configuration history showing when the bucket was made public (if available)
If RROSH is determined, also:
- OPC breach report (PIPEDA)
- OIPC Alberta breach notification (AB PIPA), if the breach involves your Alberta activity; email breachnotice@oipc.ab.ca
- OIPC BC voluntary report (BC PIPA), if the breach involves your BC activity and is significant
- Individual notification letters, one per affected individual or one per household
ClearBreach tells you which of these you need, and gives you the regulator reports and notification letters from your assessment answers.
Common mistakes in this scenario
Treating remediation as the end of the response. The most common mistake in cloud misconfiguration breaches is making the bucket private and considering the matter closed. Remediation is step one of your response. Your PIPEDA and PIPA obligations begin when the misconfiguration is discovered, not when it is fixed.
Assuming nobody looked because you saw nobody. "We have no evidence anyone accessed it" is not "nobody accessed it." Without access logs, you have no evidence either way. Presenting the absence of logs as evidence of no access is not a defensible position with regulators.
Deleting the bucket or its contents before completing the assessment. Deleting files or the bucket itself destroys evidence and may prevent you from accurately determining the scope of what was exposed. Preserve the bucket contents until your breach record is complete.
Not knowing what was in the bucket. Cloud storage is frequently used as a general-purpose dumping ground for files. Organizations often cannot immediately answer what personal information was stored in a misconfigured bucket because no one maintained a data inventory for it. The RROSH assessment cannot proceed without a data inventory. After this incident, implement a data classification policy for all cloud storage.
Underestimating the exposure window. Organizations often anchor on when they discovered the misconfiguration as the exposure start date. The actual exposure start date is when the misconfiguration occurred, which may be weeks, months, or years earlier. Using the discovery date rather than the misconfiguration date understates the exposure window and is not a credible position with regulators.
Sending a template notice that does not say what happened. Tell people plainly that you accidentally made files public, which files, for how long, and what they can do now. A generic "we experienced a security incident" notice does not meet the regulatory standard.
Real-world example, cloud storage misconfiguration
A national online retailer learned that a file of customer records had been left in cloud storage that was publicly accessible for more than two years. It held the names, birth dates, contact details and order history of 63,759 Albertans, and it had been posted on a breach forum, from which it could not be taken down.
OIPC Alberta found a real risk of significant harm and required the customers to be notified. Once the file was circulating, nobody could argue that the exposure had gone unnoticed.
The practical implication for any organization using cloud storage: cloud defaults are not privacy-safe defaults. The major platforms default to private access in some configurations and not in others, and the distinction is not always visible to the person creating the bucket or container. "We did not mean it to be public" is not the same as "it was not public." Checking storage permissions regularly, especially folders created during development, a migration or a vendor setup, is the only way to know who can actually reach them.
Source: OIPC Alberta, Decision P2023-ND-013, Breach notification decisions
MSP note
If you manage cloud infrastructure for clients and this misconfiguration occurred in a client's cloud environment that you administer:
The client organization is the accountable party under PIPEDA, AB PIPA, and BC PIPA for their individuals' personal information. Your role is to determine the exposure window, inventory the exposed data, preserve logs, and assist the client with their RROSH assessment, not to make notification decisions on their behalf.
If the misconfiguration resulted from your own configuration work or a deployment you managed, you may have contractual liability to the client. That contractual matter is separate from the client's regulatory obligations to their individuals.
Document your findings clearly and provide them to the client as soon as possible. The client's response timeline starts when they are informed of the breach, your disclosure to them is the trigger.
Ready to assess this breach? Find out whether you must report it, to whom and by when, under each law that applies, with the regulator reports and notification letters to send. See it done on a worked case →
The demonstration is the real assessment, already answered for a fictional company, with three answers left for you to change. It ends on the verdict and the documents it produced. See a real verdict → to run it on your own breach.
This playbook covers PIPEDA, Alberta PIPA, and BC PIPA obligations for private-sector organizations. If your organization handles personal health information under provincial health legislation, such as Alberta's Health Information Act or BC's E-Health (Personal Health Information Access and Protection of Privacy) Act, additional obligations may apply when health information is exposed through a cloud misconfiguration. Those obligations are not covered here.
Related guides
- How Canadian Regulators Decide Whether a Breach Must Be Reported. More real regulator decisions, across every type of breach
- PIPEDA Breach Reporting Requirements, when and how to notify the OPC under PIPEDA
- Alberta PIPA Breach Notification, AB PIPA notification obligations and OIPC process
- BC PIPA Breach Reporting, what BC PIPA does and does not require after a breach, and the OIPC BC process
- What Is RROSH?, the real risk of significant harm standard explained
- Cloud Storage Misconfiguration, Quick Reference, checklist for use during the incident
Frequently asked questions
Our cloud storage bucket was left publicly accessible by mistake, is this a reportable breach?
It depends on what was stored in the bucket and whether RROSH, real risk of significant harm, is present. The misconfiguration is a breach of security safeguards under PIPEDA regardless of whether unauthorized access is confirmed. You cannot assume no one accessed the data simply because you have not detected it. Public cloud storage buckets are actively scanned by threat intelligence services, data brokers, and security researchers within hours to days of being misconfigured. If the bucket contained sensitive categories of personal information, financial records, health data, SINs, passwords, or enabling combinations like name plus date of birth plus address, RROSH is likely present even without confirmed access, because the probability of access is high and the consequence if accessed is significant.
We have no access logs for the misconfigured bucket, how do we assess RROSH without knowing who accessed it?
The absence of access logs does not suspend your obligation, it informs your RROSH assessment. When you cannot confirm whether data was accessed, you assess RROSH based on the nature of the exposed information and the realistic probability of access. A publicly accessible cloud storage bucket containing personal information should be treated as likely accessed, not likely not accessed, for the purpose of your assessment. Regulators do not expect perfect certainty before notification, they expect a documented, good-faith assessment that accounts for uncertainty honestly. Enable access logging immediately for all cloud storage going forward.
A security researcher notified us that our bucket was publicly accessible, do we need to report to regulators?
A security researcher notification confirms the bucket was accessible and was found by someone actively looking. That eliminates one of the main unknowns in your RROSH assessment. The question is not whether the bucket was accessible, it was, but whether a real risk of significant harm to affected individuals exists. If the bucket held sensitive personal information, RROSH is almost certainly present. File your OPC breach report and any applicable provincial notifications as soon as feasible after completing your assessment, and thank the researcher in a way that does not constitute public disclosure before individuals are notified.
We fixed the misconfiguration, do we still need to go through the full breach assessment and potentially notify?
Yes. Remediating the technical issue does not extinguish your obligations under PIPEDA, Alberta PIPA, or BC PIPA. The breach occurred during the period the storage was publicly accessible. Fixing the configuration is the right first response, but it is the beginning of your response, not the end. You still need to assess RROSH, determine whether notification is required, document the incident, and, if RROSH is present, notify the applicable regulator and affected individuals. Remediation without assessment and notification, where notification was required, is a compliance failure.
Ready to assess this breach?
See whether you must report, to whom and by when, under each privacy law that applies to you, with the reports and letters to show for it.
How ClearBreach handles a breach →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