“Unfortunately, we will continue to see large-scale breaches of the applications and services we rely on until security and privacy become board-level priorities,” cautioned Malcolm Harkins, Chief Security and Trust Officer for Cylance.
Then they must enforce that approach with next-gen access to verify every user, validate their devices, limit access and privilege, and learn and adapt to user behavior.” Kemp explained, “The new mandate is ‘never trust, always verify.’ To protect against breaches that exploit weak or stolen credentials, companies need to adopt a Zero Trust Security model, which assumes that untrusted actors already exist both inside and outside the network.
It isn’t enough to just try and guard the gate and keep unauthorized users out-there has to be a way to monitor what’s going on inside the network as well, and whether or not there is anomalous or suspicious activity to be concerned about. Whether an attack is executed by a trusted employee or an external cybercriminal, it is most often done using valid, authorized user credentials. There aren’t any details yet, but there’s a good chance Kemp is right. “The traditional cybersecurity approach of ‘trust, but verify’ simply does not work anymore in today’s mobile-first, cloud-enabled world where employees can be anywhere and working on multiple devices.” “The details about how Under Armour was breached are not available yet, but it would not be surprising to find that the company is joining Yahoo, Uber, Equifax, and others who have been exploited via identity and access,” shared Tom Kemp, CEO of Centrify. It explains that Under Armour is notifying all MyFitnessPal users to provide information about how to protect their data, requiring all users to change their passwords, working with law enforcement to investigate and continuing to monitor for suspicious activity, and exploring enhancements to help detect and prevent similar unauthorized access in the future. A post on the MyFitnessPal site shares the details known so far and offers some guidance for affected users.
0 kommentar(er)
