Transcription Firm Tigerfish Secures S3 Server After Exposing Police Interviews and Customer Data
Transcription Firm Fixes Cloud Security Lapse
According to original reporting by TechCrunch (source link), San Francisco-based transcription company Tigerfish has successfully resolved a data security lapse. The incident involved an Amazon-hosted cloud server that accidentally left internal data open to the public web. Tigerfish caters to a prominent roster of clients, including government departments, law enforcement agencies, and Silicon Valley technology giants.
The exposed data repository contained a significant amount of sensitive material. Among the files accessible online were customer transcriptions, raw audio and video footage, police interviews, and body-worn camera footage. Additionally, the unprotected cloud storage contained customer invoices, featuring records from various police departments and prosecutors' offices.
Discovery by Independent Security Researcher
The security issue was uncovered by Anurag Sen, a good-faith security researcher who specializes in locating exposed datasets. Sen found the unprotected files on an Amazon S3 cloud server that was openly listed. The server lacked any password protection, allowing anyone to access the files via an easy-to-guess web address.
Sen discovered the exposed data in October. He initially attempted to alert Tigerfish to the issue, but he did not receive a response from the company. Following the initial lack of communication, Sen provided the details of the incident to TechCrunch to help flag the problem and prompt a resolution.
TechCrunch verified the source of the leak and the contents of the database before contacting Tigerfish directly. Shortly after media contact was established, Tigerfish acted to secure the vulnerable cloud storage.
Company Response and Uncertainty Regarding Customer Notification
Adam Goldberg, the president of Tigerfish, addressed the incident in an email statement. Goldberg confirmed that public access to the affected bucket had been blocked, stating that directory listings and individual files are no longer exposed. Furthermore, Goldberg noted that the company verified that all other S3 buckets are successfully blocked from public access and that the organization is continuing to review and strengthen its broader storage security policies.
Regarding the initial warning email sent by the researcher, Tigerfish explained that the message had unfortunately been caught in the company's spam filter. However, it remains entirely unclear whether Tigerfish has formally notified its affected customers about the exposure, as the company did not respond to subsequent follow-up inquiries.
The Underlying Issue: Basic Human Error
This incident highlights a broader trend in cybersecurity where simple configuration mistakes lead to major exposures. Sen, who operates from his home in Indonesia and describes his work as acting as an unpaid air-traffic controller for the internet, spends his days scanning for unprotected databases. His past discoveries include compartmentalized U.S. military emails, national license plate surveillance systems, and public SMS verification codes.
Despite growing concerns regarding artificial intelligence accelerating vulnerability discovery, Sen emphasized that the vast majority of data leaks stem from straightforward human error rather than sophisticated cyber attacks. A common scenario involves an engineer setting up a test cloud database before the weekend, temporarily disabling authentication, and failing to secure the system properly before logging off.
While public fear often focuses on shadowy hackers, Sen argues that the genuine crisis lies in leaving sensitive systems entirely unshielded on the public internet without a password. Major cloud platforms and newer development tools continue to introduce safeguards to prevent these user mistakes, but incidents like the Tigerfish exposure demonstrate that basic security lapses remain an ongoing threat to organizations worldwide.
Post a Comment