Colour theme
Book a consultation

Reviewing a cloud provider's privacy and security

Questions Canadian businesses should ask about cloud contracts, data locations, access controls, incident reporting and getting their information back.

A blue cloud icon with smaller grey clouds.

A cloud provider’s security page is a starting point for review. You still need to know how the service handles your information, what your team must configure, and what happens if the provider has an incident or you leave.

Before signing, give the supplier a description of the records you’ll store and the work the service will support. Ask for answers that apply to the product and subscription you’re buying.

Decide what the service may hold

List the information involved: client files, employee details, patient records, payment information or ordinary project documents. Identify who owns the business decision and who will administer access. If card payments are involved, the PCI DSS requirements set by your payment processor apply too.

The Privacy Commissioner’s cloud guidance for smaller organizations explains that outsourcing personal information doesn’t remove your accountability. Review the contract, permitted uses and your ability to maintain control.

An Ontario health information custodian also needs to assess PHIPA. The Ontario IPC’s third-party provider case shows why a provider’s incident can still engage the custodian’s duties. Ask your privacy adviser to identify sector and contractual requirements before uploading sensitive records.

Ask where information can go

Request locations for primary storage, backups, support access and processing. Ask which other companies provide those functions and how you’ll be told when they change. A Canadian storage region doesn’t answer every question about who can access the information.

PIPEDA doesn’t impose a blanket ban on processing outside Canada. The Commissioner’s cross-border guidance explains that you stay accountable, need comparable protection through contractual or other means, and must be open about the arrangement. Provincial, sector or client requirements can add constraints.

For organizations subject to Quebec’s private-sector law, the Quebec regulator’s guidance on disclosure describes privacy impact assessment requirements before communicating personal information outside Quebec. Have the applicable rules checked before selecting the service or region.

Write down the security responsibilities

Ask the provider to explain what it operates and what your administrator must configure. Record the answers in your own service documentation. Review these settings before launch:

  • Separate administrator accounts and multi-factor authentication.
  • Access by job role, including guests and shared links.
  • Logs you can obtain, how long they’re kept and which events they capture.
  • Encryption and who can access the keys.
  • Recovery options, backups and what a restore includes.
  • Account removal when a staff member leaves.

Ask for evidence behind any assurance claim, including its scope and date. A certificate for one part of the provider’s business won’t tell you whether your own configuration meets your obligations.

Plan for an incident and an exit

Put incident contacts and notification expectations in the agreement. Ask which details you’ll receive, how quickly the provider will supply updates, and how you’ll obtain logs needed for your own assessment.

Test an export with sample information before relying on it. Check whether it includes attachments, history and a usable file format. Establish what deletion covers, when backups expire and what happens when the subscription ends.

Keep the contract, review answers and configuration decisions together. Revisit them when the service introduces new features, changes providers or begins handling a more sensitive kind of information.


Featured Image Credit