SlideShare utilise les cookies pour améliorer les fonctionnalités et les performances, et également pour vous montrer des publicités pertinentes. Si vous continuez à naviguer sur ce site, vous acceptez l’utilisation de cookies. Consultez nos Conditions d’utilisation et notre Politique de confidentialité.
SlideShare utilise les cookies pour améliorer les fonctionnalités et les performances, et également pour vous montrer des publicités pertinentes. Si vous continuez à naviguer sur ce site, vous acceptez l’utilisation de cookies. Consultez notre Politique de confidentialité et nos Conditions d’utilisation pour en savoir plus.
Risk quantification can be a valuable tool for selling transformation to executives. It’s also important to understand how your company looks at risk. Most CEOs will have a certain amount of risk they’re willing to take called their risk tolerance. This will help you to understand if your project is worth pursuing. If your project won’t offset more risk than the risk tolerance, then it’s unlikely to be funded if it’s not a new feature or product.
We’ll explore how we can go about quantifying risk in real-world situations I’ve faced in presenting transformation initiatives. This information will help you to understand how a business looks at risk and the associated value of mitigating that risk. Want to start a new CI/CD initiative, bake in the risk averted by putting SAST and DAST in your pipeline. This would have helped Equifax avoid their breach and the risk of such a breach is very high and carries a very large cost.
We’ll also take a look at some additional resources to help you assess risk such as data on breaches, attacks, the FAIR tool, and other resources you can use once you leave the session.
▪ Average data breach = $7.3M (IBM and Ponemon Institute)
▪ Third-parties raise the cost (IBM and Ponemon Institute)
▪ 668 breaches in 2018 (Privacy Rights Clearinghouse)
▪ 1,369,452,404 records stolen in 2018 (Privacy Rights Clearinghouse)
▪ 71% increase OSS breaches from 2014 (State of the Software Supply Chain)
▪ 57% of proprietary applications are OSS (helpnetsecurity.com)
▪ Equifax = over $700M
▪ Our base risk was ~$14.4B
▪ Hundreds of millions of records
▪ Financial/Health data (highest cost)
▪ Limited patching capabilities (manual)
▪ Hundreds of different applications
▪ $50M risk budget for CEO
▪ $14.4B didn’t seem reasonable
▪ We had some protections
▪ Focused on fixing patching
▪ Analyzed our riskiest apps
▪ Calculated the risk
▪ How many likely records x number of
vulnerabilities x average cost per
record x average likelihood
▪ 50,000,000 x 7 x 144 x 1% = $504M
▪ Investment to fix the issues = $100M
▪ $500M - $100M = $400M
A better way
Factor Analysis of Information Risk (FAIR)
▪ The Open Group
− Open FAIR
▪ The FAIR Institute
▪ Free to use on your own
▪ License to use with another company
▪ RiskLens and RSA Archer