Imagine investing heavily to lock the front door of your business, only to discover that the information you were protecting was stolen through a service entrance managed by someone else.
Your company’s perimeter is no longer just your office walls or your own servers. Your data lives in payroll systems, email marketing platforms, cloud storage, and customer relationship management software. When one of those providers suffers a breach, the consequences can reach your business, even if your own systems remain secure.
The Maileva incident in France illustrates that exposure. On November 14, 2026, La Poste confirmed to AFP that a cyberattack in mid-September had resulted in the theft of names and postal addresses belonging to approximately 22 million people. These individuals were recipients of communications sent by Maileva’s business customers. They did not necessarily choose the platform or know it was handling their information.
For small businesses across Europe and the United States, the lesson is clear: outsourcing your software does not mean outsourcing all your risk.
You may not control the provider’s servers. But when customers need an explanation, employees cannot access a service, or payments stop moving, your business still has to respond.
Information reviewed as of November 15, 2026. This article provides general business guidance, not legal or cybersecurity advice for a specific incident.
The Ripple Effect: From Exposed Data to Interrupted Business
Maileva is a business-mailing platform. Its work sounds routine: helping organizations send correspondence. Yet a routine task performed for many customers can create a substantial concentration of personal information.
According to the company statement reported by AFP, the confirmed exposure included first names, last names, and postal addresses. Banking details were not involved in that disclosure. The figure should not be described as 22 million passwords, bank accounts, or complete customer files, and the public material reviewed does not establish the precise technical entry point.
Those limits do not make the incident irrelevant. Names and addresses can help make impersonation more credible when combined with information obtained elsewhere. A caller who knows a customer’s details is not necessarily legitimate. That is a possible consequence of exposure, not evidence that the Maileva information has already been used in such attacks.
But confidentiality is only one part of vendor risk. The next question is what happens when the service itself stops.
The 2024 Change Healthcare attack demonstrated that problem in the United States. UnitedHealth Group’s public updates described disruption to claims, pharmacy, and payment services, alongside an investigation into exposed personal and health information.
For a smaller healthcare practice dependent on those services, the impact reached beyond privacy. Claims still needed processing. Staff still needed paying. Ordinary expenses continued while essential functions were being restored.
You do not need to operate a clinic to recognize that dependency. Your accounting platform, order-management system, or payroll service may occupy a similar position in your business.
A Secure Cloud Does Not Automatically Mean a Secure Account
A third example shows why the relationship cannot be reduced to whether the provider is reputable.
During the 2024 campaign against Snowflake customer environments, Mandiant traced the incidents it investigated to compromised customer credentials. It found no evidence that the access resulted from a breach of Snowflake’s enterprise environment. Contributing factors included accounts without multifactor authentication and previously stolen credentials that remained valid.
The distinction matters. The provider’s infrastructure and the customer’s account are not the same security boundary.
A platform may offer strong controls while leaving the customer responsible for enabling them, deciding who becomes an administrator, and approving connections to other applications. Buying a capable service does not automatically configure it safely.
Together, these cases reveal three different exposures:
- Concentrated information: an ordinary service can hold data about many organizations’ customers.
- Operational dependency: if a critical provider becomes unavailable, your ability to work or receive payment may be affected.
- Customer-controlled access: a secure platform can still contain accounts or integrations that your business has not adequately protected.
These are not identical attacks, and they do not prove that outsourcing is inherently unsafe. They show why the relationship needs management after the subscription has been purchased.
The Three Traps Small Businesses Fall Into
The following are common organizational patterns, not findings about what caused the Maileva incident.
Digital Hoarding: Keeping Everything “Just in Case”
Storage is inexpensive, so deleting information rarely feels urgent. Old customer exports, identity documents, and outdated mailing lists remain in shared folders because somebody might need them later.
Over time, the business can lose track of why each copy exists. If an account or service is compromised, the available information may extend far beyond what is needed for current work.
The answer is not indiscriminate deletion. Some records must be retained for tax, employment, contractual, litigation, or other reasons. Start by separating information kept for a defined purpose from information kept because nobody has made a decision.
Reducing unnecessary retention will not prevent every intrusion. It can reduce what is available to steal.
Ghost Accounts: Access That Outlasts the Work
A contractor finishes a project, an employee leaves, or a tool is replaced. Their access remains because removing it never becomes urgent.
A former employee’s login may still work. An application connected for one campaign may continue reading customer records. A temporary administrator permission may become permanent.
Access management means keeping permissions aligned with current responsibilities, not simply creating accounts when people join.
The “Someone Else Is Handling It” Assumption
The owner assumes the IT contractor checks the settings. The contractor assumes the provider enforces them. The provider’s documentation explains that the customer must enable them.
Nobody necessarily intended to leave a gap. Responsibility was never made explicit.
A named internal owner helps close that gap. This person does not need to perform every technical task. They need to know who performs it, what remains unresolved, and whether the work has been completed.
Your Three-Step Vendor Survival Guide
You do not need an enterprise compliance department to begin. A small business can make meaningful progress by focusing on a few critical services and agreeing on a routine that people can actually maintain.
Step 1: Map Your “Life Support” Apps
Do not start by auditing every application your team has ever used. Begin with services holding sensitive information or supporting work that cannot easily stop: email, payroll, accounting, payments, customer management, and industry-specific software.
Create a short record for each one.
| Record | What to Capture |
|---|---|
| Business purpose | The activity that depends on the service |
| Information held | The customer, employee, financial, or other records involved |
| Internal owner | The person responsible for the relationship |
| Access | Administrators, users, and connected applications |
| Emergency contact | Verified provider support or security details |
| Fallback | Available exports, backups, and alternative working arrangements |
For payroll, for example, record who administers the account, whether an outside accountant has access, and how payroll would be prepared during an outage.
The goal is not a perfect spreadsheet. It is to avoid discovering these dependencies during an emergency.
Once the important services are visible, review relevant provider evidence. Contracts, independent assurance reports, certifications, and technical documentation can help establish what the provider handles and what remains with your business.
A SOC 2 Type II report may be useful, but its scope, period, and exceptions matter. It is evidence to evaluate, not a guarantee against a breach.
Step 2: Clean House: Access and Data
Work with whoever manages your systems to review the critical accounts first.
Confirm appropriate multifactor authentication, prioritizing administrator, email, and remote-access accounts. This adds another proof beyond a password. Phishing-resistant methods are preferable where available and appropriate.
Then review former users, unnecessary administrator rights, and unused connections to other applications. Confirm an unfamiliar account’s purpose before disabling it: a rushed cleanup can interrupt legitimate operations.
Keep a brief record of changes. Give unresolved issues a responsible person and target date.
Apply the same discipline to information. Identify duplicate exports and outdated records, check retention requirements, and agree on approved deletion. Active files, archives, and backups may follow different schedules.
You cannot eliminate all exposure. You can avoid protecting unnecessary copies indefinitely.
Step 3: Rehearse the “What If They Go Offline?” Scenario
Choose one essential provider and work through a short outage.
For an appointment-based business, that could mean accessing tomorrow’s schedule and recording changes. For an accounting team, it could mean retrieving records and managing pending work without the main platform.
Open an export. Test a restoration in a safe environment. Confirm that the records are usable rather than assuming a successful download proves recovery is possible.
Then consider the people and process: who makes decisions, where temporary records are stored, and how they will be reconciled afterward.
The fallback must protect information too. Copying unnecessary personal details into an unsecured spreadsheet can create a second problem while trying to solve the first.
Backups Are Necessary, but Not the Whole Plan
Backups remain essential for recovering from deletion, corruption, or ransomware. They do not necessarily replace the provider’s software, integrations, or transaction network.
They also cannot retrieve information already copied by an attacker or prevent its publication.
That does not make backups obsolete. It means the business needs to distinguish three tasks:
- Protect confidentiality: restrict access and reduce unnecessary information.
- Recover data: maintain protected backups or exports and test them.
- Continue operating: establish an alternative process while systems are unavailable.
Encryption has limits as well. It may protect data in particular circumstances, but an attacker using a legitimate account may be able to read information that the account is authorized to access.
No single safeguard covers every part of the problem.
What to Do When a Vendor Announces a Breach
A provider’s notice may arrive before the investigation is complete. Your business may need to make decisions while some details remain unknown.
1. Verify the Notice
Use an established support channel or access the provider’s website independently rather than relying on unexpected links. Confirm that the message is genuine, preserve it, and create an incident record.
A real breach can itself become material for phishing attempts.
2. Establish Your Specific Exposure
A headline may describe millions of affected people. You need to know which services and information relate to your organization.
Request the relevant dates, data categories, customer-specific findings, containment measures, and required actions. Record what remains unknown and when another update is expected.
Your technical contact should assess whether credentials, sessions, connected applications, or systems need attention. Preserve relevant evidence while containing the problem.
3. Bring in the Right Advisers
Legal, contractual, and insurance requirements may apply before every forensic detail is available. Do not assume the provider has handled all obligations on your behalf.
In the United States, notification requirements vary by state and sector. The information involved, contractual roles, and circumstances affect the analysis.
For organizations subject to the GDPR, controllers generally must notify the competent supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of a personal data breach, unless it is unlikely to result in a risk to individuals’ rights and freedoms.
Communication to affected individuals follows a separate high-risk test and applicable exceptions. Processors also have obligations, including notifying controllers without undue delay.
The risk assessment informs whether notification is required; it should not be treated as a reason to postpone considering the deadline. Document the assessment and obtain advice appropriate to the incident.
4. Communicate Without Guessing
Where communication is required or appropriate, explain what is confirmed, what remains under investigation, what the company is doing, and what affected people should do next.
Advice must match the exposure. Do not recommend password changes when passwords were not involved, or promise that exposed information cannot be misused.
Restoring service does not establish that stolen information has been recovered from an attacker. Keep those messages separate.
A Short Checklist to Keep
- Know the dependencies: identify providers holding important information or supporting essential work.
- Name an owner: assign responsibility for each critical service.
- Review access and retention: remove what is no longer needed, subject to operational and legal requirements.
- Test the fallback: confirm usable records and a safe alternative working process.
- Prepare the response: keep verified contacts and decision-making responsibilities accessible.
Conclusion
Outsourcing software is often smart business. Treating the provider relationship as something that needs no further attention is where the blind spot develops.
You may not own the servers, investigate the intrusion, or repair the platform. But you still have a relationship with the people whose information you collected and the employees who depend on that service to do their jobs.
Protecting that relationship begins with ordinary decisions: closing an account that should no longer work, removing an unnecessary export, testing a backup, and saving the contact needed during an incident.
Your front door still matters. So does knowing who manages the other entrances.
Sources
- TV5Monde: Une filiale de La Poste victime d’un vol de données massif
- UnitedHealth Group: Update on the Change Healthcare cyberattack
- Mandiant: UNC5537 Snowflake data theft and extortion
- NIST: Cybersecurity Framework 2.0 Small Business Quick-Start Guide
- CISA and MS-ISAC: Ransomware Guide
- FTC: Data Breach Response Guide for Business
- EUR-Lex: General Data Protection Regulation (GDPR)