Logo
Cybersecurity

Your Vendors Hold Your Customer Data. Who Is Securing It?

Cyber incidents involving JPMorgan Chase, Visa and Mastercard show how customer information can be exposed through external service providers, even when a company's own payment infrastructure remains unaffected.

ITSEC AsiaITSEC Asia
|
Nov 20, 2026
Your Vendors Hold Your Customer Data. Who Is Securing It?

A company can have strong internal security controls and still face a data exposure through an external provider.

That risk became visible on 19 November, when JPMorgan Chase, Visa and Mastercard disclosed separate incidents involving third-party service providers. The disclosures raised questions about how customer information is handled outside the systems that companies directly operate.

The details differ. JPMorgan Chase said attackers may have accessed marketing data held by vendors, potentially including some customer names and email addresses. Mastercard reported that a limited number of email addresses belonging to a small subset of cardholders in a specific benefits programme had been exposed. Visa said claims were associated with an incident involving a third-party service provider in Asia-Pacific. It said its own systems were not involved and payment data, including card numbers, was unaffected. [1][2]

These statements do not establish that all three companies were affected by one breach or shared the same provider. Each disclosure needs to be assessed on its own facts.

The companies also said their core banking or payment services were not disrupted. That limits the reported operational impact, but it doesn't make the data exposure irrelevant.

Why an email address can become a security problem

Names and email addresses may seem less sensitive than passwords, payment credentials or financial records. In the wrong hands, however, they can make social engineering more convincing.

An attacker who knows a person's name, email address and relationship with a financial service can write a message that looks like a genuine account notification, benefit-program update or customer-support request. Add a phone number or information about a recent interaction and the message can become even more credible.

This is why organisations should assess data exposure by considering how information can be combined and misused, not only by counting the number of records involved.

The group known as n0n claimed responsibility and published datasets it attributed to the companies. Reuters reported that it could not independently verify the authenticity of the material. Those claims should therefore remain separate from what the companies have confirmed. [1]

The vendor relationship is part of the security perimeter

Third-party providers often need access to customer information to run marketing campaigns, manage loyalty programmes, provide customer support or deliver other business services.

That access creates a chain of responsibility. The organisation collecting the data remains accountable for understanding where the information goes, why a provider needs it and what happens if that provider is compromised.

Four controls deserve closer attention.

1. Give vendors less data.

Before sharing information, ask whether the provider needs every field. A marketing partner may need an email address but not a full customer profile. Remove unnecessary data, limit retention periods and define when information must be deleted.

2. Restrict and review access.

Vendor access should be limited to approved systems, users and business purposes. Use named accounts, multi-factor authentication and time-bound permissions where possible. Review access regularly and revoke it when a contract or task ends.

3. Monitor the relationship, not just the contract.

A signed security questionnaire is not continuous assurance. Organisations should review the provider's security controls, subcontractors, access patterns, incident history and changes in service delivery. Critical providers need deeper and more frequent scrutiny than suppliers with no access to sensitive information.

4. Agree on what happens during an incident.

Contracts should specify notification timelines, investigation support, evidence preservation, escalation contacts and responsibilities for customer and regulator communications. These details need to be tested before an incident occurs.

The response starts before the breach

A third-party incident can create a difficult question for leadership: who knows what happened, who can confirm the facts and who is authorised to communicate with customers?

Security teams need a clear route to obtain evidence from the provider. Legal, privacy, procurement, communications and business owners need defined roles. Customer notifications should be based on verified information and explain what data was involved, what action has been taken and what customers should watch for.

The earlier JPMorgan service disruption caused by a software bug was separate from the cyber incident. Keeping those events distinct is a basic part of credible incident communication. [1][2]

The lesson for organisations is direct: vendor risk cannot sit only in a procurement checklist. It needs to be part of security governance, data management and incident response.

Your vendors may operate outside your network. Their access to your customers' information still creates risk for your organisation.

Build the skills to manage that risk. The ITSEC Cyber & AI Academy helps organisations and professionals develop the cybersecurity knowledge needed to assess threats, strengthen controls and prepare for incidents.

Explore the Academy: https://www.itsec.academy/

References

[1] Reuters, “JPMorgan, Visa, Mastercard say third-party vendors targeted in cyberattack,” 19 November 2026. https://www.reuters.com/legal/government/jpmorgan-says-third-party-vendors-targeted-cyberattack-2026-11-19/

[2] The Register, “Chase, Visa, Mastercard confirm third-party cyberattacks that may have exposed customers' info,” 19 November 2026. https://www.theregister.com/security/2026/11/19/chase-visa-mastercard-confirm-third-party-cyberattacks-that-may-have-exposed-customers-info/

[3] Associated Press, “A cyberattack leaks thousands of Chase customer emails and some phone numbers,” 19 November 2026. https://apnews.com/article/8470d475450721b66858bdace47091c0

Share this post

You may also like

Cybersecurity Roadmap: Why It Is Essential for Managing Enterprise Risk Today
Cybersecurity

Cybersecurity Roadmap: Why It Is Essential for Managing Enterprise Risk Today

INTRODUCTION Many organizations invest heavily in security tools, yet still struggle to explain their overall security posture. This is not always due to lack of technology, but often due to lack of direction. As digital environments grow more complex, security decisions are made across cloud platforms, remote endpoints, third-party integrations, and increasingly, AI-driven systems. According to findings highlighted in the World Economic Forum [https://www.weforum.org/], cyber risk today is less about a single vulnerability and more about how fragmented security efforts accumulate across interconnected environments. Without a clear plan, security initiatives tend to be reactive. Controls are added in response to incidents, audits, or vendor recommendations, rather than as part of a coordinated strategy. This is where a Cybersecurity Roadmap becomes critical. A roadmap provides a structured way to define priorities, sequence improvements, and align security with business risk. Industry guidance from NIST Cybersecurity Framework [https://www.nist.gov/cyberframework] emphasizes that this approach enables organizations to move from isolated security actions toward a cohesive and resilient defense posture. WHAT IS A CYBERSECURITY ROADMAP? A Cybersecurity Roadmap is a strategic,

ITSEC AsiaITSEC Asia
|
Jan 22, 2026 — 5 minutes read
What Information Security Process Manager Actually Does and Why Most Organizations Getting It Wrong
Cybersecurity

What Information Security Process Manager Actually Does and Why Most Organizations Getting It Wrong

INTRODUCTION Here is a number worth sitting with: organizations that detect breaches with a security AI and automation program save an average of USD 2.2 million compared to those that do not. Yet the operational role responsible for building, owning, and continuously improving those detection and response processes, the Information Security Process Manager, remains one of the least formally defined positions in enterprise security. Most organizations have the tools. Very few have the structured ownership that makes those tools work together as a system. ITSEC Asia, the cybersecurity leader in Indonesia with operations across Singapore, Australia, and the UAE, works directly with organizations to fill exactly this gap: turning fragmented security investments into managed, measurable, and genuinely effective programs. Sources: IBM Cost of a Data Breach Report 2024 [https://www.ibm.com/reports/data-breach] WHAT THE ROLE ACTUALLY OWNS An Information Security Process Manager is the operational architect of a security program. Where a CISO sets direction and a security analyst executes individual tasks, the Process Manager is responsible for defining, documenting, improving, and governing the processes that

|
Mei 25, 2026 — 5 minutes read
A Breach Doesn't End When Services Come Back Online
Cybersecurity

A Breach Doesn't End When Services Come Back Online

On 7 November 2026, Chainalysis announced that its Reactor platform, KYT transaction-monitoring interface and API, and Address Screening products were back online after a security incident. The company said the services had been restored with enhanced security measures and asked customers to reconnect through a specific process. [1] Chainalysis first disclosed the incident on 30 October. It said an external actor had used what it described as “offensive agentic techniques” to access its systems and internal tools without authorisation. Its initial notice reported access to user IDs, names, email addresses and organisational role labels, but said there was no evidence at that stage that investigation content, authentication credentials or session tokens had been accessed. [1] The assessment changed as the investigation progressed. In an update on 4 November, Chainalysis said names, usernames, password hashes and “live tokens” for all users had been exposed. It separately confirmed that an on-path attack exposed passwords belonging to a subset of customers. The company said that attack path had been contained and remediated. It

ITSEC AsiaITSEC Asia
|
Nov 09, 2026 — 3 minutes read

Receive weekly
updates on new posts

Subscribe