In my many years of working in the field of risk management, I've come across a wide variety of ways that different organizations and people use to prioritize risks.  These are commonly referred to as "Risk Scoring Methodologies".  In SimpleRisk, we currently support six different risk scoring methodologies:

Anyone who has studied for the CISSP exam knows that the "textbook" definition of risk scoring is Risk = Likelihood x Impact.  Typically, the Likelihood and Impact values are represented by ordinal numbers, which are mapped to some qualified value.  We then use a matrix to represent the intersection of these values in order to obtain a final risk score.  Some organizations will use a 3x3 matrix.  Some may use a 10x10.  Here at SimpleRisk, we've seen just about every combination you could imagine in-between, but the most common scenario is a matrix with five Likelihood values and five Impact

Has the number of security issues you deal with on a routine basis ever made you feel a bit like Atlas carrying the world on your shoulders?  I can’t tell you the number of conversations I’ve had with discontented security practitioners who lament to me the woes of trying to speak with management about the latest Heartbleed or Spectre/Meltdown vulnerabilities and “management just doesn’t understand”.  Even worse, when management inevitably turns a blind eye to the issue, the security practitioner worries that they’ll be searching for a new job if the vulnerability is ever exploited.  As the

Subscribe to vulnerabilities