threat-intelligence alerts about a potential employee data leak<\/a>, while asserting that customer data and operational systems remain unaffected. The attacker reportedly claimed to have used password spraying and MFA fatigue as attack vectors. TCS says the allegedly exposed data is over four years old and limited to basic employee information, and that controls against both techniques have been in place for more than two years. Shares dipped 0.80 percent on the BSE.<\/p>\nWhat this means for your business<\/h2>\n
The story that quietly matters here isn’t the breach itself but the attack vector. MFA fatigue, where attackers repeatedly push authentication prompts until a tired employee taps “approve,” is no longer exotic. It brought down Uber in 2022 and Rockstar Games shortly after. If your organization treats MFA as a finished checkbox rather than an active defense requiring configuration hardening and user training, TCS’s disclosure is a mirror, not just a news item about a competitor.<\/p>\n
TCS’s public posture follows a familiar incident-response playbook: minimize scope, emphasize staleness of data, confirm customer insulation, and assert existing controls. That framing may well be accurate, but it also happens to be the framing that limits regulatory exposure and client anxiety, so it warrants independent verification rather than face-value acceptance. The detail that TCS claims its anti-spray and anti-fatigue controls predate the alleged attack by two years is either genuinely reassuring or raises the harder question of why alerts are arriving at all.<\/p>\n
The vendor-risk angle is the one most CISOs underweight. TCS runs infrastructure and applications for a significant portion of Global 2000 firms. Even if customer systems are clean today, an employee directory exposure at a major managed-services provider gives attackers a social-engineering asset, names, roles, org structures, that can be weaponized in spear-phishing campaigns targeting those clients months later. The age of the data doesn’t neutralize that risk; org charts change slowly. I’d revise this concern downward only if TCS confirms the exposed records contain no role or organizational metadata, which the current disclosure does not address.<\/p>\n
Concept deep-dive: MFA Fatigue<\/h2>\n
MFA fatigue is an attack technique where an adversary who already has a valid username and password floods the target with push-based authentication requests, betting the user will eventually approve one just to make the noise stop. Think of it as a doorbell held down until someone answers. It exploits human behavior, not cryptographic weakness, which is why technically sound MFA deployments still fail. The business fix is number-matching or phishing-resistant FIDO2 keys, not just having MFA switched on.<\/p>\n
Based on reporting from TCS Investigates Potential Employee Data Leak, Assures No Customer Impact, ETHRWorld<\/a>, originally published 2026-08-10 12:35:00.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"Share with your CISO Tata Consultancy Services, India’s largest IT company, disclosed Monday that it received threat-intelligence alerts about a potential employee data leak, while asserting that customer data and operational systems remain unaffected. The attacker reportedly claimed to have used password spraying and MFA fatigue as attack vectors. TCS says the allegedly exposed data […]<\/p>\n","protected":false},"author":1,"featured_media":8364,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[149],"tags":[238],"tmauthors":[],"class_list":["post-8363","post","type-post","status-publish","format-standard","has-post-thumbnail","category-ai-hr","tag-ciso"],"_links":{"self":[{"href":"https:\/\/workai.tv\/news\/wp-json\/wp\/v2\/posts\/8363","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/workai.tv\/news\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/workai.tv\/news\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/workai.tv\/news\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/workai.tv\/news\/wp-json\/wp\/v2\/comments?post=8363"}],"version-history":[{"count":0,"href":"https:\/\/workai.tv\/news\/wp-json\/wp\/v2\/posts\/8363\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/workai.tv\/news\/wp-json\/wp\/v2\/media\/8364"}],"wp:attachment":[{"href":"https:\/\/workai.tv\/news\/wp-json\/wp\/v2\/media?parent=8363"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/workai.tv\/news\/wp-json\/wp\/v2\/categories?post=8363"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/workai.tv\/news\/wp-json\/wp\/v2\/tags?post=8363"},{"taxonomy":"tmauthors","embeddable":true,"href":"https:\/\/workai.tv\/news\/wp-json\/wp\/v2\/tmauthors?post=8363"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}