3 ms·
How You Respond to Security Researchers Says Everything About You
- daniealapt 4y agoCompany culture matters! — LastPass support did not seem to have a culture or awareness of security. If this was embedded into all roles, then a support rep would have understood and escalated the matter. Additionally, maybe there is no culture of escalating? Maybe customer support needs to “keep all tickets away from engineering?” If customer support cannot escalate this thread, what hope is this for team A to escalate a vulternability to team B? With very little data, this all seems like cultural red flags.
- LewisVerstappen 4y agoRick is the VP of Engineering at 1Pass btw. Very impressive.
- machina_ex_deus 4y agoDid this guy seriously try to reach the security team through the normal customer support channel that's probably automated with bots, and then judged the company according to that? And that's after they do have a bug bounty program, and instead of speaking with bugcrowd who denied him, he decided to go through a channel that's clearly not meant to handle these kinds of issues. This is just such a poor understanding of how companies work. If he just emailed a real person in the company he'd have a real chance of getting a real response. Imagine judging a pizza company by how the pizza ordering hotline didn't take your vulnerability disclose. This sounds ridiculous. Now customer support is just like pizza ordering line. If you want to contact a company on something they usually don't have a normal channel, you need to speak to the right people. Need to write a nice email, even if they don't have "security.txt", to some manager or someone else you could contact, and ask nicely who to contact further about it. And try more than one person. If you're not a customer, do not go through customer support. It's the worst channel in every company because they need to serve bulk communication. And they see an incredible amount of shit from confused customers, so don't expect them to realize that there's something important going on. And be nice. If you're acting like an asshole, you could have a million dollar issue and you won't get past customer support. They are asshole filter. They are meant to filter out all the assholes trying to reach the corporation. Their number 1 instinct is to block assholes. If you sound like trouble, it's literally their job to filter you.
- plaguepilled 4y agoWat? If the "ordering hotline" in this instance didn't know what to do, surely they should tell their manager? That's how it works in most businesses. Why is it suddenly different for hackable pizza stores?
- machina_ex_deus 4y agoAt most they would refer you elsewhere, but most probably they would kindly ask you contact someone else so they can serve people looking to order pizzas. They get prank calls and all sorts of nonsense. They get customers asking all kinds of weird questions constantly, and they can't distinguish them from Mr important security researcher here that's not even a customer. They will just get confused, return an automated reply and move on to next request because they are paying them to handle bulk requests. They are not meant to escalate to manager, it's literally their job not to do it. And their manager is just another customer support person.
- some_furry 4y ago> and they can't distinguish them from Mr important security researcher here that's not even a customer Bold of you to assume that I wasn't a customer. (I was, at one point. Not that it's relevant today.)
- machina_ex_deus 4y agoIt's interesting that after all my points, you decide to nitpick that one sentence where I didn't assume you weren't a customer, I stated the fact that you didn't contact them as a customer. It's interesting because it's similar to how you decided to base your entire judgement of this company on encounter with customer support. You can't just throw everything into bad or good bucket because of how it triggers you emotionally. I bet I quite annoyed you. Doesn't mean the best thing to do is just find that one sentence where I'm slightly wrong and judge me on that. Try to emotionally detach. When a bug is pissing you off, do you throw the whole program with it? Or do you understand what's going on and what is there to learn, despite the annoying bug? Do I have something to learn from this incredibly annoying person that embarrassed me on HN? Or should I just find something to nitpick? I'm not your enemy. Customer support isn't your enemy. And the security researcher coming to your company with some anoying bug bounty isn't an enemy either. There's that saying, Homo homini lupus. Don't be like that.
- jph 4y agoSomething that helps, in my experience, is what Colin Percival teaches: use the phrasing of "coordinated disclosure" , rather than "responsible disclosure". This helps company staff understand that the disclosure and the bug are both happening, and the company can choose to coordinate or not, and there's no need to debate what's responsible or not. Send a link that explains your position, and how the company can respond. Here's mine and feel free to use it... https://github.com/joelparkerhenderson/coordinated-disclosure https://github.com/joelparkerhenderson/coordinated-disclosur...
- puffoflogic 4y ago[flagged]
- some_furry 4y agoI don't wear a hat, I wear a fursuit head. Any judgments (white hat, black hat, etc) are invalid and often little more than projection.
- no_furries_plz 4y ago[flagged]
- codesniperjoe 4y agoTDLR: How You Respond to Security Researchers Says Everything ... [ About Your Business State ].
- colpn 4y ago[flagged]