Connecting AppSec to Enterprise Value Case Study
Post 4 of 4 in the "From Defects to Dollars" Series
In Post 1, we established the language of value creation: who determines value, what delivers it, and how cybersecurity operations support the enterprise value agenda. In Post 2, we explored the psychology of business decisions through the scientific method, the WRAP process, choice architecture, and the Six Sources of Influence. In Post 3, we examined the practical building blocks of a business case: stakeholder analysis, business model alignment, the SCIPAB communication framework, and cyber risk quantification.
This final installment brings those frameworks together in a composite case study. We follow a hypothetical CISO at a fictional PE-backed B2B SaaS company whose application security posture threatens revenue, operating margins, and enterprise value. The case study shows, step by step, how to build and present a business case that persuades the organization to act.
Readers who have followed the series will recognize the tools as they appear. This article also stands on its own, although the earlier installments explain the concepts in greater depth and provide useful context for applying them here.
The Scenario: Meet the Company
Consider Meridian, a fictional B2B SaaS company that provides mission-critical financial calculation software to enterprise customers. The company has $120M in annual recurring revenue and 200+ enterprise clients. It is owned by a private equity firm that acquired it four years ago. The PE sponsor’s investment thesis centers on operational efficiency and EBITDA margin expansion, with an exit window opening in 18–24 months.
Meridian’s platform processes billions of dollars in financial transactions annually. Its customers include Fortune 500 companies with rigorous security requirements, regulated industries with compliance mandates, and increasingly, organizations that require SOC 2 Type II attestation, robust vulnerability management, and evidence of a mature application security posture before signing or renewing contracts.
The CISO, hired two years ago, has built a security team from scratch, implemented endpoint detection, established a governance council, and achieved SOC 2 Type II certification. Security maturity has materially improved against the program’s control framework. Most controls that the security team could implement independently are now in place. Addressing the remaining gaps requires changes across the organization, with application security the largest outstanding concern.
Illustrative Case Study Only: Not Real Company Data
Meridian is a fictional composite drawn from real-world patterns. All figures, including ARR, CVE counts, deal values, investment costs, loss estimates, and valuation ranges, are hypothetical and have been created for instructional purposes. They do not reflect the performance, financials, or operations of any real organization. Readers should substitute their own data when applying these frameworks.
The Problem: A Cascade of Consequences
Application security problems rarely remain isolated. At Meridian, an end-of-life Ruby on Rails application stack powers 85% of the revenue-generating platform. That single technical condition creates operational problems with consequences across the business.
This pattern occurs regularly in practice. Technical debt that engineering teams consider “manageable” can represent material business risk when assessed against its effect on value creation. The table below traces those connections.
|
Technical Condition |
Operational Consequence |
Business Impact |
|
EOL stack (Rails 5.x / Ruby 2.x) |
Legacy Rails app running on Passenger/Unicorn cannot be containerized using modern base images without significant refactoring, because native gem dependencies compiled against EOL OpenSSL fail Docker builds, significantly impeding adoption of modern CI/CD pipelines |
12+ hours unplanned downtime per month; SRE burnout and developer toil |
|
No automated testing |
Manual QA cycles extend release cadence from weekly to monthly; security scans run infrequently |
Roadmap delays reduce bookings velocity; vulnerable code persists longer in production |
|
Accumulated CVEs |
47 high/critical CVEs across Rack middleware, ActiveRecord, and bundled gems; Gemfile.lock conflicts block automated remediation |
Customer security questionnaires flagged; two enterprise deals paused pending remediation evidence |
|
No SAST/SCA in pipeline |
Vulnerabilities discovered post-deployment via annual pen test rather than at commit time |
6–30x remediation cost vs. shift-left detection (IBM/NIST); unresolved pen test findings accumulate as audit observations |
|
Hard-coded secrets |
API keys and service account credentials embedded in source code repositories |
Material finding in SOC 2 audit (CC6.1); cyber insurance underwriters flag as a coverage risk, increasing premiums or limiting claim recovery for related incidents |
|
Aggregate posture |
Tech diligence during M&A reveals 85% of revenue running on EOL Rails/Ruby stack |
Potential discount on enterprise value; escrow holdbacks; delayed close timelines |
Tracing an outdated runtime through its operational consequences gives the CFO, CRO, and board a view of the problem in terms they already use: revenue, operating costs, and enterprise value. This is the “Defects to Dollars” translation that gives the series its name. The technical facts remain the same, but connecting each defect to its downstream financial consequences turns a technical debt discussion into a business risk discussion.
Veracode’s State of Software Security report finds that applications grow roughly 40% year-on-year regardless of their original size. As applications age, flaws accumulate and create security debt. Flaws that remain unfixed for more than a year exist in 42% of applications and 71% of organizations. The Synopsys BSIMM14 report presents a similar picture: organizations using automated security testing throughout the development lifecycle consistently outperform those relying on point-in-time assessments. Visibility and measurement therefore strengthen both security practice and the evidence supporting the business case.
The growth of agentic software adds further complexity to these problems and to the work required to address them.
Step 1: Identify the Value at Stake
In Post 1, we established that the CISO must “think like the money people.” At a PE-backed company, this means understanding how the sponsor evaluates revenue growth, operating margins, capital efficiency, and treasury integrity, the four levers of the Defensible Security Budget framework. The NIST Cybersecurity Framework functions (Identify, Protect, Detect, Respond, Recover, Govern) connect to these levers. Application security needs to be assessed in the same terms.
At Meridian, application security affects all four:
Revenue growth: Enterprise customers increasingly require evidence of a mature application security posture before signing. Meridian’s difficulty responding confidently to security questionnaires slows deals. The sales team reports that 12% of qualified pipeline, approximately $4.2M in ARR, is lost annually to competitors that can satisfy security due diligence faster.
Operating costs: The EOL Rails stack forces manual processes that automated pipelines would eliminate. Twelve hours of unplanned downtime per month translates to $1.44M annually in direct costs, including SRE labor, revenue impact, and customer credits. IBM and NIST research puts the cost of post-deployment vulnerability remediation at 6 to 30 times that of shift-left detection, depending on severity and phase. Meridian pays that premium on every finding.
Capital efficiency: Manual testing, security firefighting, and workarounds for the EOL stack consume engineering capacity that could otherwise support product innovation. The opportunity cost appears in roadmap features that are not delivered, affecting competitive positioning and renewal rates.
Treasury integrity / Enterprise value: Exit readiness is a direct concern for the PE sponsor. The acquiring party’s technology due diligence will examine a platform where 85% of revenue depends on an end-of-life Rails/Ruby stack with unresolved critical CVEs. Practitioners and deal advisors consistently report valuation adjustments for material application security deficiencies through remediation cost estimates, escrow holdbacks, and price renegotiation. The magnitude varies by deal size and severity of findings.
These figures give the CFO a basis for evaluating the proposed investment alongside other capital allocation decisions. The request to fix vulnerabilities is supported by an assessment of $8.88M in annualized operational risk exposure, plus deal-specific M&A valuation risk, and a proposal to reduce that exposure.
Step 2: Map the Stakeholders
In Post 3, we introduced stakeholder analysis as the discipline of mapping influence, support, and motivation before preparing a presentation. For Meridian’s CISO, that analysis identifies the following stakeholders:
|
Stakeholder |
Quadrant |
Primary Concern |
Message Frame |
Key Metric |
|
CFO |
Persuadable |
Operating cost; EBITDA margin |
Risk quantification; ROI |
Annualized loss expectancy reduction vs. investment cost |
|
CTO |
Champion |
Engineering velocity; tech debt |
Architectural alignment |
Release cadence improvement; developer hours recovered |
|
CRO |
Persuadable |
Deal velocity; pipeline |
Revenue protection |
Days saved in sales cycle; at-risk ARR recovered |
|
PE Sponsor |
Observer→ |
Enterprise value; exit readiness |
Valuation preservation |
Clean tech diligence; EBITDA multiple protection |
|
VP Engineering |
Persuadable |
Roadmap capacity; team morale |
Toil reduction |
Hours per sprint on security remediation vs. feature work |
|
Board / Audit Committee |
Supporter |
Fiduciary duty; regulatory risk |
Governance assurance |
Audit observations trending; regulatory exposure profile |
The CTO is a natural champion. She understands the technical debt and has already advocated for modernization. The CISO can strengthen her case with financial data. The CFO and CRO both have considerable influence but are currently neutral or skeptical. Each needs a different explanation: quantified risk reduction and ROI for the CFO, pipeline recovery and deal velocity for the CRO. The PE sponsor cares deeply about exit readiness but does not typically engage in operational decisions, placing them between observer and champion. The business case should give the CFO enough evidence to take it to the board through the established decision process.
The VP of Engineering also needs early attention because his team will carry the execution burden. If he sees the initiative as “security making us do extra work,” adoption will stall. If he sees it as investment in removing technical debt that has slowed his team, adoption is more likely to accelerate. The CISO needs to understand his objections, address capacity concerns, and explain how the initiative serves engineering priorities.
Stakeholder analysis continues throughout the program. Understanding who influences the outcome and what matters to them allows the CISO to explain the same business case in terms each decision-maker can evaluate.
Step 3: Quantify the Risk
In Post 3, we introduced Cyber Risk Quantification (CRQ) as a way to build credible business cases. Meridian’s CISO applies a FAIR-based approach, calibrated with industry loss data from platforms such as Kovrr and X-Analytics, to develop probability-weighted financial estimates for six risk scenarios:
|
Risk Scenario |
Frequency |
Avg. Loss |
ALE (Pre-Invest) |
ALE (Post-Invest) |
|
Data breach via unpatched CVE |
~1 in 4 years |
$4.8M |
$1,200,000 |
$240,000 |
|
Secrets exposure / credential theft |
~1 in 2 years |
$1.6M |
$800,000 |
$80,000 |
|
Supply chain compromise (3rd-party lib) |
~1 in 5 years |
$6.2M |
$1,240,000 |
$310,000 |
|
Lost enterprise deals (security objections) |
Ongoing |
- |
$4,200,000 |
$1,050,000 |
|
Operational downtime (EOL instability) |
12 hrs/month |
- |
$1,440,000 |
$360,000 |
|
M&A valuation discount |
At exit |
Variable (deal-specific) |
See note * |
$0 |
|
Total Annualized Exposure |
|
|
$8,880,000 + M&A (see note *) |
$2,040,000 |
* The M&A valuation discount reflects a real but non-recurring risk. Deal advisors and M&A practitioners consistently report material valuation adjustments for significant application security deficiencies, but no authoritative source publishes a standard percentage discount. The magnitude is deal-specific. This row makes the exit-valuation risk visible without asserting a precise figure. Readers should work with their deal advisors to estimate an appropriate range for their situation. The “Pre-Invest” column represents current annualized loss expectancy across the scenarios. The “Post-Invest” column represents projected exposure once the proposed application security program is fully implemented. The difference, $6.84M in annualized operational risk reduction excluding the M&A valuation component, represents the projected annual benefit before investment costs ($8.88M - $2.04M), rather than net ROI.
The M&A valuation discount requires separate consideration because it arises once, at exit, rather than as an annual recurring loss. It remains in the table because exit valuation is a central financial concern for a PE-backed company with an 18–24 month exit window. The “lost enterprise deals” estimate has a different basis: it comes from the CRO’s pipeline data. Its credibility with the CFO rests on the revenue team’s evidence of sales losses with security root causes.
The estimates need to be defensible and transparent about their assumptions, even where precision is limited. As discussed in Post 3, a quantified estimate can be challenged, refined, and stress-tested in ways that a subjective heat-map label cannot. CRQ gives stakeholders specific assumptions to debate and improve, rather than asking them simply to accept that a risk is real.
The Proposed Investment
To address $8.88M in annualized operational risk exposure, plus deal-specific M&A valuation risk, the CISO proposes the following phased investment:
|
Investment |
Year 1 |
Year 2 |
Ongoing |
|
Rails/Ruby stack modernization (Rails 7.x / Ruby 3.x migration) |
$320,000 |
$80,000 |
$40,000 |
|
SAST/SCA tooling + CI/CD integration |
$185,000 |
$120,000 |
$120,000 |
|
Secrets management platform (vault) |
$95,000 |
$60,000 |
$60,000 |
|
AppSec champion program + training |
$75,000 |
$50,000 |
$50,000 |
|
Senior AppSec engineer (headcount) |
$195,000 |
$200,000 |
$200,000 |
|
Total |
$870,000 |
$510,000 |
$470,000 |
The financial case compares an $870K Year 1 investment with $6.84M in annualized operational risk reduction, excluding the deal-specific M&A component, to produce a 7.86:1 benefit-cost ratio ($6.84M / $0.87M), equivalent to approximately 686% net ROI (($6.84M - $0.87M) / $0.87M). Preserving M&A value would increase that return, although the benefit is deal-specific and non-recurring. These ratios compare the fully implemented annual benefit with Year 1 cost; they are not realized Year 1 or 24-month program returns. At the full benefit rate, $870K / $6.84M x 12 implies a simple payback of about 1.5 months, before later costs. Actual payback depends on the phased benefit ramp and all program costs, including $510K in Year 2 and $470K annually thereafter; a sub-12-month payback from program start is not established by this table. Presenting those assumptions clearly allows the CFO to assess the case.
Step 4: Build the SCIPAB Narrative
The SCIPAB framework from Post 3 gives the CISO a structure for presenting the analysis. Each element draws on the value assessment, stakeholder mapping, and risk quantification completed in Steps 1–3:
|
S |
Situation |
Our platform processes $2.1B in mission-critical financial calculations for 200+ enterprise customers, including Fortune 500 companies with stringent security requirements. Our enterprise sales cycle averages 94 days, with 68% of prospects requesting detailed security documentation before signing. |
|
C |
Complication |
85% of our revenue-generating codebase runs on a Rails/Ruby stack that reached end-of-life. We have 47 unresolved high and critical CVEs across Rack, ActiveRecord, and bundled gems, no automated security scanning in our CI/CD pipeline, and hard-coded secrets in multiple repositories. Two enterprise deals totaling $1.8M ARR are currently paused pending evidence of remediation. Our last SOC 2 audit produced three observations directly tied to these gaps. |
|
I |
Implication |
Our CRQ analysis shows $8.88M in annualized operational risk exposure across five scenario categories, plus material M&A valuation risk at exit that is deal-specific in magnitude. We are losing approximately $4.2M in qualified pipeline annually to competitors who can satisfy security due diligence faster than we can. More critically, our PE sponsor’s exit timeline is 18–24 months away, and tech diligence will surface these findings. Deal advisors and practitioners consistently report material valuation adjustments, through remediation escrows and price renegotiation, for significant application security deficiencies discovered in tech diligence. |
|
P |
Position |
We propose a phased, 24-month Application Security Value Assurance program with a Year 1 investment of $870K. This program modernizes our Rails/Ruby stack, embeds automated security scanning into our development lifecycle, reduces secrets exposure, and builds an internal AppSec champion capability. The program is designed to reduce our annualized operational risk exposure from $8.88M to $2.04M once fully implemented, a $6.84M annualized reduction, while simultaneously accelerating engineering velocity and removing the #1 blocker to enterprise deal closure. |
|
A |
Action |
Approve the $870K Year 1 budget in the Q2 planning cycle. Assign a cross-functional steering committee with representation from Engineering, Product, Finance, and Legal. The CISO will provide monthly progress reports tied to the six business impact metrics outlined in the business case, with predefined tripwires for course correction. |
|
B |
Benefit |
Within 12 months, aim to recover approximately $3.2M in at-risk pipeline (timing to be validated against the phased rollout), reduce sales cycle by 12–15 days for security-sensitive deals, eliminate the three outstanding SOC 2 observations, and position the company for a clean tech diligence in the exit window. The projected $6.84M annualized reduction at full implementation already includes $3.15M in recovered enterprise deals ($4.2M - $1.05M, approximately $3.2M); this revenue benefit must not be counted again. Payback from program start depends on phased benefits and all program costs, while any M&A valuation preservation is separate and non-recurring. |
The same narrative addresses each stakeholder’s priorities. The CFO can assess quantified risk, ROI, and payback. The CRO can evaluate pipeline recovery and deal velocity, while the CTO sees the case for modernization and improved engineering velocity. The PE sponsor can judge the implications for diligence and valuation protection. This applies the principle introduced in Post 3: one business case, explained in terms that matter to each audience.
The sequence matters. Situation, Complication, and Implication establish a shared understanding of the problem and its consequences before the CISO proposes action. The closing Benefit section then describes outcomes the audience can measure: recovered pipeline, shorter sales cycles, resolved audit observations, and protected valuation. Technical improvements such as fewer CVEs and better CVSS scores support those outcomes, but the business case is expressed in dollars, days, and deals.
Step 5: Sustain the Change with Six Sources of Influence
Budget approval provides the resources, but the program also has to change the organizational behavior that created the problem. The Six Sources of Influence model from Post 2 helps the CISO plan that work.
Research from Crucial Learning shows that leaders who combine four or more sources of influence are ten times more likely to produce lasting change than those relying on a single source. Security programs often depend on structural motivation through mandates, policies, and compliance requirements. Meridian’s CISO uses all six sources to support implementation:
|
|
Motivation |
Ability |
|
Personal |
Reframe remediation as code quality investment. Show engineers that addressing the EOL stack eliminates the weekend firefighting and production incidents they hate. Connect secure coding to professional growth. |
Provide SAST/SCA tooling with IDE integration so developers see findings at the point of creation. Deliver secure coding workshops tailored to the specific vulnerability classes in your codebase. |
|
Social |
Launch an AppSec Champion program with peer recognition. Publish team-level security scorecards. Leverage the customer pressure (enterprise deal pauses) to create shared urgency across Sales and Engineering. |
Embed a security engineer within the platform team for pairing sessions on complex remediation. Create a shared Slack channel for rapid security consultation. Build a community of practice. |
|
Structural |
Link security posture metrics to business KPIs the board already tracks: deal velocity, customer retention, insurance premiums. Make the cost of inaction visible in quarterly business reviews. |
Automate scanning in CI/CD so the secure path requires zero additional effort. Set secure defaults. Make the insecure path require an explicit, documented exception. Remove friction from doing the right thing. |
These sources reinforce one another. An engineer who understands why secure coding matters, has tools that make it easier, sees peers recognized for it, and can get help with difficult problems has practical support for changing how they work. A deadline to “fix the vulnerabilities by Friday” provides none of that support on its own.
Prepare to Be Wrong: Tripwires and Course Correction
The WRAP process from Post 2 asks decision-makers to prepare for both success and failure. Meridian’s CISO defines the following tripwires in advance:
- If mean time to remediate critical CVEs does not decrease by 40% within six months, escalate to the steering committee and re-evaluate the tooling investment.
- If AppSec champion participation drops below 60% of target teams after the first quarter, engage engineering leadership and diagnose the adoption barrier before assuming the program design is wrong.
- If the Rails/Ruby stack migration falls more than 30 days behind schedule, review resource allocation. Dependence on engineering capacity is the highest-risk execution variable.
- If enterprise deal closures do not show measurable improvement in security-related cycle time within nine months, work with the CRO to validate the causal link between security posture and deal velocity.
- Identified the value at stake by connecting the technical condition to revenue, operating costs, capital efficiency, and treasury integrity, using the Defensible Security Budget framework from Post 1.
- Mapped stakeholders’ influence and priorities using the quadrant model and influence mapping from Post 3, then tailored the message to each audience.
- Quantified the risk in probability-weighted financial terms that the CFO could evaluate alongside other capital allocation decisions, applying CRQ and the reality-testing discipline from Posts 2 and 3.
- Built a SCIPAB narrative that established a shared understanding before proposing action and closed with benefits expressed in the listener’s terms, using the communication framework from Post 3.
- Planned for lasting behavioral change through all Six Sources of Influence from Post 2, so the investment would support more than a one-time remediation sprint.
- Defined tripwires for course correction using the WRAP process from Post 2, making clear when the assumptions or implementation would need to be reconsidered.
Predefined tripwires demonstrate the discipline a CFO and board need to see. They state the conditions under which the CISO will report that the program is not working, and what action will follow. That commitment gives stakeholders a basis for judging progress and holding the program accountable.
The Complete Arc: From Defects to Dollars
Meridian’s CISO began with a technical observation: the platform runs on an end-of-life Rails/Ruby stack with accumulating vulnerabilities. Without further analysis, that finding could have remained a risk register entry, a red cell on a heat map, or a quarterly update that was acknowledged and then deprioritized.
The CISO developed the finding into a business case through six connected activities:
This approach connects defects to dollars through evidence that the people allocating resources can assess. The frameworks give CISOs a practical way to lead as business executives with cybersecurity expertise, explaining how security decisions affect the organization’s financial outcomes.
The Thesis, Revisited
We began this series with an argument from The CISO Evolution: Business Knowledge for Cybersecurity Executives: success on the Internal Battlefield requires a command of both economics and psychology.
Economics connects security investments, risks, and programs to the financial outcomes the organization measures. Thinking like the money people gives the CISO a way to explain the value of technical priorities and secure the resources needed to address them. This does not require compromising technical principles.
Psychology explains how decisions are made within organizations and how to create conditions that make good decisions easier. The scientific method, the WRAP process, choice architecture, and the Six Sources of Influence help turn analysis into decisions and sustained action.
From Defects to Dollars describes the translation cybersecurity leaders need to make between engineering findings and the board’s financial concerns. A rigorous, honest, and persuasive narrative connects the two. The frameworks in this series make that work a repeatable discipline.
Addressing defects requires funding, and securing that funding depends on explaining why the investment is worth making.
The Complete Series
Post 1: From Defects to Dollars: A Practical Guide to Connecting Application Security to Value Assurance
Post 2: Business Decisions: Using Science, Frameworks, and Influence to Drive Better Outcomes
Post 3: Articulating the Business Case: From Stakeholder Analysis to Cyber Risk Quantification
Post 4: Application Security Value Assurance: A Case Study (this article)
References and Further Reading
The CISO Evolution: Business Knowledge for Cybersecurity Executives by Matthew K. Sharp and Kyriakos Lambros (Wiley, 2022)
Decisive: How to Make Better Choices in Life and Work by Chip Heath and Dan Heath (Crown Business, 2013)
Nudge: Improving Decisions About Health, Wealth, and Happiness by Richard H. Thaler and Cass R. Sunstein (Penguin, 2009)
Influencer: The New Science of Leading Change by Joseph Grenny, Kerry Patterson, David Maxfield, Ron McMillan, and Al Switzler (McGraw-Hill, 2013)
Measuring and Managing Information Risk: A FAIR Approach by Jack Freund and Jack Jones (Butterworth-Heinemann, 2014)
Veracode State of Software Security Report: veracode.com/state-of-software-security-report
Synopsys BSIMM Report: synopsys.com/software-integrity/bsimm
SCIPAB Communication Framework: mandel.com/blog/what-is-scipab
Cognitive bias resources: yourbias.is and yourlogicalfallacyis.com
To stay current with cybersecurity leadership insights, subscribe to Cyber Security Tribe.

