Cut through threat intelligence jargon with three practical steps: use the MoSCoW method to prioritize features, align requirements with the NIST Cybersecurity Framework, and assign one person to actually manage the platform. Many organizations buy tools and abandon them, wasting money.
One of the biggest mistakes, because let's be honest, products, threat intel, all security products, there's a lot of noise, a lot of new adjectives, a lot of new abbreviations that can be very confusing for customers. And so, I had kind of 3 key tips, and one was building requirements. Threat intel folks are very good at requirements overall, but not always necessarily in procuring a technology like a platform for themselves. And so, we talk about and we introduce like what a Moscow method is, and that, the must-have, nice-to-have, right, will-not-have type of, uh, tiering, as well as applying that to like the, uh, NIST Cybersecurity Framework, if depending on how deep you want to go, and then assigning a point person. It is unbelievable how often people are like, let's buy a platform and then we just like turn it on and then we're going to walk away.
