A Proven Methodology to Secure the Budget You Need
summary
Explains how to secure cybersecurity funding by addressing the four key questions budget approvers ask and demonstrates using the Duty of Care Risk Analysis (DoCRA) methodology to provide the required information to obtain the necessary budget.
AI-written summary · about
chapters (19)
- 0:00Intro
- 2:45Establishing Trust and Confidence
- 5:25How Are InfoSec and C-Level Speaking Different Languages?
- 7:04When Budget Approvers Don't Receive the Information They Need, You Don't Receive the Budget You Need!
- 9:24How does DoCRA create a Common Language?
- 12:09Example: Calculated Acceptable Risk Definition (CARD)
- 15:20Does the Narrative and How We Provide Information to Budget Approvers Really Matter?
- 17:07Proven Budget Request Narrative Documenting Trust and Enabling Confidence
- 17:52Big Picture - Program Progress Over Time
- 18:36Since Our Last Review - Program Changes
- 19:14Roadmap - Planned vs. Actual Risk Level
- 20:38Budget Request: Level 1 - Budget Level
- 23:11Budget Request: Level 2 - Project Level
- 24:06Budget Request: Level 3 - Risk Level
- 25:09Is Risk Level Request Sufficient?
- 27:16Traditional Approach - DLP Budget Request
- 31:28Risks That Require Treatment
- 33:00Budget Request: Level 3- Risk Level
- 33:44Proven Budget Narrative Approach Does Management have information to answer the 4 questions?
related talks
19mGetting Your Security Budget Approved Without FUD
40mGetting Cybersecurity Funding from Your CEO: the 5 Critical Steps
47mYour Cybersecurity Budget Is a Horse’s Behind
48mSecuring Buy-In for Security Budgets
15mFrom Risk to Return: Measuring Cybersecurity ROI with Data Analytics
46mBusinesses Run On Risk And Debt: Why Communicating Security Risk Is Hard
47mTechniques to Evolve Risk Governance and Comply with SEC Cybersecurity Rule
30mEffective security on a tight budget