News for hackers. Stuff that matters.
Re:MongoHQ Security breach by bdcravens on Tuesday October 29, 2013 @05:24PM (#6637552)
detected unauthorized access to an internal support application using a password that was shared with a compromised personal account

Someone's updating their resume tonight.

Re:MongoHQ Security breach by richadams on Tuesday October 29, 2013 @05:36PM (#6637653)
Seems a bit harsh to fire someone for that. People make mistakes. If anything, you know that this person isn't going to make the same mistake ever again.

Of course, if they do, then firing might be the way to go. First time mistake, second time incompetence.

Re:MongoHQ Security breach by bdcravens on Wednesday October 30, 2013 @02:40PM (#6642290)
Perhaps something like this should be in a policy handbook?

"Employees may not use passwords that are used with any service outside of the company."

Zero enforceability (but some companies would probably ask for a list of outside passwords I'm sure), but in the face of a direct policy violation, 100% fireable, and can help a company in terms of liability.

Re:MongoHQ Security breach by meowface on Tuesday October 29, 2013 @05:28PM (#6637587)
I doubt he'll be fired just for that, but yeah, that is a big mistake on his part.

In general though, in any security breach the most common way to pivot is via password re-use. You'll see this happen with many privileged employees at almost every company.

Re:MongoHQ Security breach by darkarmani on Tuesday October 29, 2013 @10:54PM (#6639149)
> Someone's updating their resume tonight.

At a start-up, it most likely was not an engineering decision, but an agility trade-off. Get that product out the door now!

Re:MongoHQ Security breach by alexkus on Wednesday October 30, 2013 @08:54AM (#6640378)
"Move fast and break (other people's) things!" ?