<story><title>Security Hole in Sendgrid</title><url>https://chunkhost.com/blog/15/huge_security_hole_in_sendgrid</url><text></text></story><parent_chain></parent_chain><comment><author>jtchang</author><text>Social engineering will almost always work. I don&amp;#x27;t really fault Sendgrid for this (though I could see this not working as well if you were using Amazon SES...no support to even talk to!). It sucks that they got caught with their pants down but I bet a good social engineering attempt on ChunkHost might have yielded similar results.&lt;p&gt;The lesson here is to have multiple defenses. 2 factor auth is a great start and it worked in this case.</text></comment>
<story><title>Security Hole in Sendgrid</title><url>https://chunkhost.com/blog/15/huge_security_hole_in_sendgrid</url><text></text></story><parent_chain></parent_chain><comment><author>MasterScrat</author><text>The problem is that it was technically possible, for a representative, to make this change without the proper verification. You just can&amp;#x27;t rely on humans for that.</text></comment>