Staff Breach At OneLogin Exposes Password Storage Feature (cso.com.au)

River Tam quotes a report from CSO Australia: Enterprise access management firm OneLogin has suffered an embarrassing breach tied to a single employee's credentials being compromised. OneLogin on Tuesday revealed the breach affected a feature called Secure Notes that allowed its users to "store information." That feature however is pitched to users as a secure way to digitally jot down credentials for access to corporate firewalls and keys to software product licenses. The firm is concerned Secure Notes was exposed to a hacker for at least one month, though it may have been from as early as July 2 through to August 25, according to a post by the firm. Normally these notes should have been encrypted using "multiple levels of AES-256 encryption," it said in a blog post. Several thousand enterprise customers, including high profile tech startups, use OneLogin for single sign-on to access enterprise cloud applications. The company has championed the SAML standard for single sign-on and promises customers an easy way to enable multi-factor authentication from devices to cloud applications. But it appears the company wasn't using multi-factor authentication for its own systems. OneLogin's CISO Alvaro Hoyos said a bug in its software caused Secure Notes to be "visible in our logging system prior to being encrypted and stored in our database." The firm later found out that an employees compromised credentials were used to access this logging system. The company has since fixed the bug on the same day it detected the bug. CSO adds that the firm "also implemented SAML-based authentication for its log management system and restricted access to a limited set of IP addresses."

Comments

you put all your eggs in a basket...

[RussellTheMuscle]

where are your eggs?

employee login to access production data?

[4wdloop]

How come a company with business based on being secure allows employee logins to access production data?

Re:employee login to access production data?

[pushing-robot]

Well, being able to access production *logs* is useful. The problem was that sensitive data was being written to those logs, not that a developer had access to them.

The cause was probably as simple as some debug code accidentally left in, but something as obvious as private data being logged should have been caught by any of the frequent security audits they claim to have.

Was it hacked?

[Anonymous Coward]

Why would hackers bother? All they need to do is create a website "Store your critical logins here to save a bit of time" and the sheep go and store their passwords there.

Why not hand your passwords out to random strangers??

FFS. How can you tell the difference between being hacked (i.e. your password out of your control and in the hands of people you don't know who might use it for malicious purposes) and stored on one of these password services (i.e.your password out of your control and in the hands of people you don't know who might use it for malicious purposes).

Re:+1 for closed proprietary SaaS, cloud

[upuv]

The cracker is the actual password DB's were safe. Just some developer wrote the affected sections to log file as well. In the clear BTW.

Always audit the log file.