Cybersecurity Breach Impact Analysis

Use This Skill When

• A company, customer, supplier, or critical vendor has suffered a cyber incident with possible financial consequences.
• The user wants an investment view on revenue impact, remediation cost, customer trust damage, or competitive spillovers.
• The analysis must go beyond bad headline and map transmission into bookings, churn, margins, litigation, and regulation.
• The task includes identifying second-order winners and losers across the ecosystem.

Required Inputs

• Incident date, affected systems, customer scope, and breach type if known.
• The exposed company or ecosystem role of the affected entity.
• Company size, revenue mix, customer profile, and concentration if available.
• Regulatory context such as healthcare, financial services, government, or data privacy exposure.
• The user's objective: immediate event analysis, thesis update, or sector read-through.

Workflow

1. Define the incident scope: data theft, outage, ransomware, service degradation, internal control breach, or supply-chain compromise.
2. Map the primary impact channels:
   • Revenue interruption or delayed sales cycles
   • Customer churn, expansion slowdown, or trust erosion
   • Remediation, legal, insurance, and compliance cost
   • Management distraction and product roadmap delay
   • Regulatory or contractual penalties
3. Distinguish between operational outage risk, data trust risk, and governance / control risk; they affect valuation differently.
4. Identify exposed counterparties and likely beneficiaries such as alternative vendors, managed security providers, or incident-response firms.
5. Separate immediate quarter noise from longer-duration damage such as impaired win rates or a higher discount rate.
6. Summarize the investment implication, key unknowns, and the next disclosures that matter most.

Output Requirements

• Use an event-driven investment tone that connects the incident to financial transmission mechanisms.
• Structure the answer from direct impact to second-order impact to thesis implication.
• Be specific about which line items are at risk: bookings, renewal rates, gross margin, opex, litigation reserves, or sales efficiency.
• Make uncertainty explicit when facts are still developing.
• Avoid security jargon unless it materially changes the business consequence.

Output Template

Quality Checks

• Confirm the incident type is defined clearly enough to map the right business consequences.
• Check that direct financial channels are distinguished from reputational or governance channels.
• Verify the analysis includes both downside costs and possible competitive spillovers.
• Make sure long-term impairment is not assumed without evidence on customer behavior or regulatory fallout.
• Ensure unknowns are listed explicitly when the event is still unfolding.

Guardrails

• Do not equate every breach with permanent customer loss; context matters.
• Do not ignore industry-specific regulation, especially in healthcare, finance, and public sector markets.
• Do not analyze only the victim; include vendors, substitutes, and affected customers when relevant.
• Do not overfit to initial headlines before severity and scope are better understood.
• Do not confuse temporary remediation spend with structural margin impairment unless there is evidence.

Example Prompts

• Analyze the likely revenue and trust impact of a breach at a payroll software provider.
• A hospital IT vendor was hit by ransomware. Map the primary losers, beneficiaries, and duration of impact.
• Give me the investment impact framework for a cloud platform outage that exposed customer data.