Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

A supplier told me they were breached and my customers' data may be involved

Short answer

First learn exactly what of yours the provider held and what they say was taken. Then change every password, key and token you ever gave them, reduce their access to the minimum and keep their notice. What you must tell customers depends on law and contract, so ask a lawyer.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • An email says a provider I use had a security incident.
  • The notice is vague and says 'some customer data may have been affected'.
  • I do not remember exactly what data or access that provider had.
  • My customers might receive scam messages that mention things only the provider knew.
  • The provider is asking me to reset passwords or rotate keys.

Why does this happen?

  1. Your data lives wherever your providers keep it

    Customer lists, files, logins and keys are copied into many services over time. A breach at one of them reaches you even though your own systems were never touched.

  2. Access given once is never reviewed

    Providers keep API keys, admin users and connections long after the project that needed them. The wider the access, the more a breach can reach.

  3. Stolen logins are a way into your other systems

    If a password or key you gave the provider also works somewhere else, the breach continues in your own accounts, because stolen logins keep working until they are replaced.

  4. Provider notices are written to be careful, not clear

    They say what is known so far, and the early version is often incomplete. Treat the first notice as a starting point and ask for updates.

What can I do about it today?

  1. Save the notice and write down the dateKeep the email, any status page text and the names of people at the provider you spoke to.
  2. List what that provider holds of yoursCustomer details, files, payment data, keys, connections to your other tools. Mark which are personal data about your customers.
  3. Change the passwords and keys connected to themReset the logins of everyone who used the service, and ask whoever manages your systems to replace any keys or tokens connected to it, in your own systems and in the provider's.
  4. Turn on a second sign-in step wherever it is offeredDo this for the provider account and for the email that receives its resets.
  5. Ask the provider written questionsWhat was accessed, when, whether your records were included, what they have fixed and what you should do. Keep the answers.
  6. Hold off on telling your customers until you know the facts and the rulesWhether and when you must notify depends on where you and your customers are and on your contract. Ask a lawyer.

When should I bring someone in?

  • The provider's answers do not tell you whether your data was involved.
  • The provider held keys or access to your servers, app or payments.
  • You cannot list what is connected to the provider because nobody documented it.

How do I handle it?

  1. Map what the provider can reachI list every key, user and connection tied to that service across your apps, servers and other tools.
  2. Replace secrets in a safe orderKeys and tokens are rotated one at a time, with a way back, so that your own product keeps working while the old ones stop.
  3. Reduce what stays connectedAccess the service does not need is removed, and what remains is given the minimum rights.
  4. Look in your own logs for signs of misuseI check whether the old keys were used from anywhere unexpected and report what I find and what I cannot tell.
  5. Hand you a written summaryYou get a plain record of what was changed and what is still open, to show customers or advisers if you choose.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Do I have to tell my customers?

That depends on the law where you and they live and on your contracts. I cannot give legal advice, so ask a lawyer before you decide either way.

Should I stop using the provider?

Not as a first move. First find out what was affected and secure your side. Whether to stay is a business decision for after you have their answers.

Is changing my password enough?

No. Keys, tokens and connections that the provider held also need replacing, and other accounts that shared the password need changing.

How was this page made?

I drafted this page with AI assistance. It is general guidance for business owners, not advice for your own system. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.