Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Sephora Offers Monitoring Services in Wake of Data Breach
Newest First  |  Oldest First  |  Threaded View
User Rank: Ninja
7/31/2019 | 8:53:37 AM
Re: Sephora, we have a problem
Thank you for the commentary, I am glad that individuals are reading the comments as well as the article (that is good for the group).

And yes, the system is an overseas system but even with that said, they still have the same problems as those of us in the US (ask Capital One, ex. employee). But there really needs to be an oversight group that constantly monitors the systems on a monthly basis (dependent on the level of priority and risk).

"The security incident was limited to a database serving our Southeast Asia, Hong Kong SAR and Australia/New Zealand customers who used our online services," Sephora stated, adding that it was safe for customers to continue using its website and mobile app. Read more at https://www.channelnewsasia.com/news/asia/sephora-data-breach-singapore-malaysia-indonesia-thailand-nz-11763006"

Interesting, databases replicate with one another so if someone from Thailand flies to Malaysia or Singapore, then they should be able to access their data from anywhere. This is referred to as Transactional or Mirrored replication (dependent upon the distance the data replicates from an to, ACID based transactions but it also depends on the type of DB as well).  

So this tells me, the hacker did not have enough time to do research, the data is segmented based on zones (n + 1) or the information they gave is incorrect and/or the actor was able to move horizontally to extract information using known tools in their arsenal without being detected.

The red-team from China could have done this because of their attention to detail (they clean up everything) or APT teams from Russia could have done this as well (I am not leaving out North Korea because this is practiced on a regular). 

It sounds to me that this was an inside job but the case is still under investigation.


User Rank: Ninja
7/30/2019 | 9:37:35 PM
Re: Sephora, we have a problem
If the database operated independently, then how did the actors obtain the usernames, first & last name, encrypted passwords among other things. I assume there are ways to navigate between systems and links obviously
User Rank: Ninja
7/30/2019 | 9:36:10 PM
Re: Sephora, we have a problem
identifying a breach is not indicative of when it actually took place Agree on this. More work is needed to identify what really happened.
User Rank: Ninja
7/30/2019 | 9:34:25 PM
I really have not heard this company, it may be outside of US.
User Rank: Ninja
7/29/2019 | 7:33:47 PM
Sephora, we have a problem

The company also said it detected the data breach "over the last two weeks" and immediately appointed independent experts to investigate. Affected customers were notified as soon as the details of the incident had been verified. 
  • Wait, they investigated the breach "over the last two weeks", and they notified the experts immediately (so when did the breach actually occur because identifying a breach is not indicative of when it actually took place)?. This could have happened days, months or years before. so the statement leaves room for interpretation.  

A spokesperson from Brunswick Group, a strategy advisory firm working with Sephora Southeast Asia, told CNA that the company's regional databases operate independently.
  • If the database operated independently, then how did the actors obtain the usernames, first & last name, encrypted passwords among other things. In most databases, there is a foreign key that connects the primary table with other tables or to external tables (that is if it is a relational DB).  So if they were able to access this first database containing the table, then they would have had access to the other data or at least parts of it.

Sephora customers who are not from the involved markets are "not affected in any way by this incident", the spokesperson said.
  • I think the first question I would ask is "who is from the involved markets"?

The external independent experts engaged by Sephora also concluded that there was "no major vulnerability" found on Sephora's Southeast Asia websites and also did not find any traces of a cyberattack.
  • Isn't that a marketing ploy to try and save face so to minimize the damage that has already occurred, because if the breach was minimal, then why did they bring a cyber-group who are experts in the field to the scene?. Almost like bringing big guns to look at a small problem. 

"We can also confirm no credit card information was accessed and have no evidence that any personal data has been misused," the spokesperson added. 
  • Hmm, in most breaches, the hacker looks for a buyer on the black market, it takes time for them to find someone who can use this person's data, so even though it did not take place now, it will in time. 

This is an interesting story, sounds like certain things are not adding up but that is usually part of the marketing team trying to save face to reduce the already tainted and damaged reputation of the company.


I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Current Issue
Everything You Need to Know About DNS Attacks
It's important to understand DNS, potential attacks against it, and the tools and techniques required to defend DNS infrastructure. This report answers all the questions you were afraid to ask. Domain Name Service (DNS) is a critical part of any organization's digital infrastructure, but it's also one of the least understood. DNS is designed to be invisible to business professionals, IT stakeholders, and many security professionals, but DNS's threat surface is large and widely targeted. Attackers are causing a great deal of damage with an array of attacks such as denial of service, DNS cache poisoning, DNS hijackin, DNS tunneling, and DNS dangling. They are using DNS infrastructure to take control of inbound and outbound communications and preventing users from accessing the applications they are looking for. To stop attacks on DNS, security teams need to shore up the organization's security hygiene around DNS infrastructure, implement controls such as DNSSEC, and monitor DNS traffic
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2023-05-26
Craft is a CMS for creating custom digital experiences. Cross site scripting (XSS) can be triggered by review volumes. This issue has been fixed in version 4.4.7.
PUBLISHED: 2023-05-26
Django-SES is a drop-in mail backend for Django. The django_ses library implements a mail backend for Django using AWS Simple Email Service. The library exports the `SESEventWebhookView class` intended to receive signed requests from AWS to handle email bounces, subscriptions, etc. These requests ar...
PUBLISHED: 2023-05-26
Highlight is an open source, full-stack monitoring platform. Highlight may record passwords on customer deployments when a password html input is switched to `type="text"` via a javascript "Show Password" button. This differs from the expected behavior which always obfuscates `ty...
PUBLISHED: 2023-05-26
Craft is a CMS for creating custom digital experiences on the web.The platform does not filter input and encode output in Quick Post validation error message, which can deliver an XSS payload. Old CVE fixed the XSS in label HTML but didn’t fix it when clicking save. This issue was...
PUBLISHED: 2023-05-26
GDSDB infinite loop in Wireshark 4.0.0 to 4.0.5 and 3.6.0 to 3.6.13 allows denial of service via packet injection or crafted capture file