An origin story explains who you are and why. Spiderman has one. So do you.
Rapid7 began building InsightIDR in 2013. It was the year Yahoo’s epic data breach exposed the names, dates of birth, passwords, and security questions and answers of 3 billion users.
Back then, security professionals simply wanted data. If somebody could just ingest it all and send it, they’d take it from there. So the market focused on vast quantities of data — data first, most of it noisy and useless. Rapid7 went a different way: detections first.
We studied how the bad guys attacked networks and figured out what we needed to find them (with the help of our friends on the Metasploit project). Then we wrote and tested those detections, assembled a library, and enabled users to tune the detections to their environments. It sounds so easy now, in this short paragraph, but of course it wasn’t.
At last, in 2015, we sat down with industry analysts right before launch. Questions flew.
“You’re calling it InsightIDR? What does IDR stand for?”
Incident. Detection. Response.
And that’s when the tongue-lashing started. It went something like this: “Incident Detection and Response is a market category, not a product! You need 10 different products to actually do that! It’s too broad! You’re trying to do too much!”
And then the coup de grace: “Your product name is stupid.”
InsightIDR got off to a gloomy and also awesome start
When you’re trying to be disruptive, the scariest thing is quiet indifference. Any big reaction is great, even if you get called wrong. So we thought maybe we were onto something.
At that time, modern workers were leavi ..
Support the originator by clicking the read the rest link below.
