I'm LongbridgeAI. Here is the key information I extracted- Financial institutions must move beyond superficial security reports and compliance checks to implement rigorous penetration testing that examines core business logic and attack paths.…
Key Points
Recent supplier security incidents have affected the payment, banking and digital asset sectors. Faced with rapidly evolving attacks, institutions need to re-examine the quality of security testing and reduce supply chain risks by focusing on supplier management, access control, business verification and emergency drills.
Payment Security Observation 04
Visa, HSBC, Ledger.
Recently, the names of these institutions have appeared in reports of supply chain security incidents.
On November 17, Visa confirmed that a third-party service provider in its Asia-Pacific region had experienced a security incident. Visa stated that its own system was not affected and there was no indication that payment data such as card numbers were affected. The name of the service provider and details of the incident have not yet been disclosed. [1]
Just the day before, the website service provider Optimizely was attacked.
Security researchers found that malicious code appeared in the website scripts of 178 institutions through the service, including HSBC and Ledger. [2] Earlier, French bank Crédit Mutuel Arkéa disclosed that attackers launched fraudulent transactions through a service provider's platform, and about 100 million euros were stolen. [3] The three incidents, with different impacts, all point to a common problem faced by financial institutions: As businesses develop, institutions access more and more external services. Are these connections secure enough? Attackers are also using AI to speed up the search for credentials, analyze systems, and execute attacks, leaving institutions with less time to discover and deal with problems. [4] Are the supplier's qualification materials and penetration test reports really enough to reassure people? A supplier's incident can have far-reaching consequences throughout the business. A financial or payment institution often relies on multiple service providers to complete its daily operations: cloud service providers handle infrastructure, technology vendors provide systems, payment service providers process transactions, and outsourced teams handle maintenance or customer support. These partners perform different tasks and have varying levels of access. If a supplier experiences a security incident, the impact can extend to customer data, websites, and business operations, and even affect financial transactions. Optimizely Attacked, Affecting 178 Institutional Websites. Optimizely provides website testing and other services to businesses. On November 16, attackers exploited vulnerabilities in its services to inject malicious code into some customer projects. Security researchers found that 188 scripts from 178 institutions were affected. The institutions named included HSBC, Ledger, and several trading and financial services companies. Researchers found that the malicious code had the ability to replace cryptocurrency addresses and steal some payment form information. [2] Here, "affected" means that the relevant websites loaded the infected scripts; public information does not mean that these institutions have suffered financial losses. French bank hacked, about 100 million euros stolen On November 4, the bank disclosed that attackers used a service provider's platform to launch fraudulent transactions to other banks using the bank's own account. According to Reuters, about 100 million euros were stolen. The bank said that customer assets were not affected; some funds have been recovered, and the final amount of loss is still to be confirmed. [3] From website scripts to financial transactions, once external services are integrated into the business, they need to be included in continuous security management. Penetration test reports: are they for approval or for discovering risks? When purchasing suppliers, security qualifications are an unavoidable hurdle. ISO 27001, SOC 2, PCI DSS, and various security assessments and penetration test reports often appear on the audit list. But after receiving the report, there is a more important question to ask: Was this penetration test for approval or to seriously find security problems in the system? In some projects, testing is treated as a procurement process that needs to be completed from the beginning. The client wants the report as soon as possible, the supplier wants it approved quickly, and the tester is also required to complete the work within a limited time. Ultimately, all parties receive the necessary materials, but perhaps no one truly asks: Where could the attacker have entered? What could they have accessed? Could they have affected funds and customer data? These types of tests often exhibit the following characteristics: The testing scope avoids complex core business processes and third-party connections; it relies primarily on automated scanning, lacking in-depth verification of business logic and attack paths; after discovering vulnerabilities, the focus is only on whether the report can be delivered, without follow-up remediation and retesting; the system, permissions, and suppliers have changed, yet past test results are still being used. A report can be very comprehensive, but the actual business processes may never have been carefully examined. Even more alarming is this mindset: that having certificates and reports means assuming security issues are resolved. Security certification and testing have clear scope, methods, and timelines; they are important management tools. Their value depends on whether an organization is willing to invest sufficient resources in real-world business operations, confront identified problems, and drive remediation. If the goal of testing is merely to "obtain a report," that report easily becomes a comfort. Of course, publicly available information does not fully disclose the certification and testing details of the organizations mentioned in this article. The above discussion concerns cautionary practices within the industry, not judgments about the causes of individual incidents. Faced with supply chain risks, what can financial institutions do? Supplier security management cannot stop at the procurement stage. For payment institutions, financial institutions, and other companies undertaking financial transactions, they can start from the following four aspects. Figure 1: Supplier Security Action List 01 Identify Key Suppliers and Clarify Business Dependencies First, list service providers related to funds, sensitive data, and core business operations, including payment processing, cloud infrastructure, wallets, customer support, and risk control services. For each key supplier, at least clarify: What business does it handle? Which systems and data does it have access to? Which customers and operations would be affected if service was interrupted or a security incident occurred? Who within the organization is responsible for managing this partnership? When there are many suppliers, start with partners who can influence cash flow, account permissions, and core services. 02 Tighten Access Permissions and Manage Accounts and Keys Suppliers may need to access the backend, call APIs, or access customer data for development, operation, and troubleshooting. Each access should have a clear purpose, scope, and responsible person. Key checks: Whether there are accounts shared by multiple people; Whether tokens and keys are valid indefinitely and whether there are rotation and revocation mechanisms; Whether the same credentials or permissions are used in the test and production environments; Whether access permissions are promptly revoked after project completion or personnel departure; Whether operations such as querying data, modifying accounts, and initiating transactions are authorized separately. When a set of vendor credentials is compromised, an organization should be able to quickly answer: what can it access, how to immediately disable it, and what operations have already occurred. 03 Conduct a genuine penetration test and continue. If penetration testing is only for obtaining reports, it's easy to miss risks that impact business operations. For critical vendors and payment systems, a thorough business-level penetration test is necessary first. After clearly defining authorization and testing boundaries, examine external entry points, vendor identities, API permissions, and critical business operations from an attacker's perspective to verify whether individual issues can be chained into an attack path that ultimately affects customer data or financial security. After discovering issues, follow up with remediation and retesting. New vendor onboarding, system updates, or permission adjustments can all introduce new risks. Organizations need to continuously conduct penetration testing and promptly verify after significant changes to ensure security defenses keep pace with business changes. In the future, AI can assist security teams in quickly identifying assets, discovering changes, and analyzing potential attack paths; security experts can verify risks and assess impacts in conjunction with business scenarios, and follow up on remediation and retesting. The combination of these two approaches helps improve verification frequency. 04. Advance Drills: What to Do When a Supplier Has an Incident? After a security incident, organizations typically need to accomplish several things simultaneously: understand the impact, restrict access, protect customers, maintain business operations, and collaborate with suppliers on the investigation. Advance preparation is essential for a timely response when an incident occurs.
Agree with key suppliers in advance on:
Who will notify whom after an incident occurs;
How to share logs and necessary information related to the investigation;
Which accounts, interfaces, and keys need to be suspended or rotated;
What alternative process will be used when critical services are interrupted;
How to securely exit when a key supplier cannot continue to provide services.
After the plan is formulated, regular drills are also necessary. Having the security, technology, business, and supplier teams go through the process together is essential to identify practical problems such as the inability to contact the responsible person, the inability to revoke permissions in a timely manner, and the inability to use backup plans.
Strengthening security defenses before an attack occurs
AI is accelerating the speed at which attackers discover and exploit vulnerabilities.
Improving security defenses before an attack occurs
AI is accelerating the speed at which attackers discover and exploit vulnerabilities.
