Saturday, November 8, 2025

Making Cyber Risk a Company-Wide Priority

SINC Fireside Chat: Security Is Everyone's Job: Aligning Cybersecurity and Business Through Leadership and Trust. Aligning Cybersecurity and Business Through Leadership and Trust. Cybersecurity isn't just about protection but instead about performance. When security is embedded into the organization's fabric, aligned with business objectives, and championed by leadership, it becomes a catalyst for growth, resilience, and mission success.


Cybersecurity is a Business Imperative

Boards and executive leadership increasingly recognize cybersecurity as a core business risk. Awareness is high, but execution gaps remain. Regulators and investors expect demonstrable governance, transparency, and effective cyber programs that protect revenue, enable strategic initiatives, and preserve brand trust.

The most mature organizations treat cyber risk as enterprise risk. Risks are measured, prioritized, funded, and owners are held accountable to the  business. Frameworks such as NIST CSF and CIS Controls offer practical structures to operationalize these principles.


Governance turns to Execution

Cybersecurity governance must extend from the board to the CEO, CISO, CIO, and business leaders. Integration starts with:

  1. Incoporating security into workflows — embedding controls into product development, procurement, onboarding, and vendor intake.
  2. Ensuring security habitual — through frictionless solutions such as single sign-on, passwordless access, automated patching, and secure defaults.
  3. Defining role-based responsibilities — integrated into job descriptions and performance reviews.
  4. Delivering contextual learning — just-in-time nudges within email and collaboration tools.
  5. Embedding security champions — within business functions like engineering, HR, and sales to act as internal service partners.


Risk Translated into Business Terms

Start with a value map connecting critical business assets revenue streams, intellectual property, and customer data to that of cyber controls. Define risk appetite and thresholds to clarify acceptable downtime or data loss. Translate these into measurable KPIs such as:

  • Percentage of revenue-impacting systems patched within SLA
  • Mean time to detect and remediate incidents
  • Frequency of resilience and recovery tests passed
  • Risk exposure and ROI of cyber investments
  • Third-party assurance levels for critical vendors

Measurements that show business impact and risk trend lines help leadership make informed, strategic decisions.


Quantifying and Communicating Risk

Adopting Cyber Risk Quantification (CRQ) enables leaders to evaluate potential financial impacts: lost revenue, remediation costs, fines, and compare them with other enterprise risks in a shared business language.

Run tabletop exercises that use these quantified scenarios to prepare the board for tradeoffs, investment decisions, and communication strategies. Brief leadership concisely — focus on scenario impacts, not technical detail.

Embed cyber oversight into board committee charters (audit, risk, or dedicated cyber committees) and establish standing agenda items for top risks, readiness, and compliance updates. Use leadership pipelines to influence vendors, reinforce supply chain security, and restore customer trust after incidents.


Build a Culture of Security

Technology without culture is brittle. Sustainable resilience depends on the synergy of People, Process, and Technology. An emphasis my co-presenter established which each reinforcing the other.

  • People are the first line of defense and most vital element to maturity and success. Leadership must model secure behavior and psychological saftegy, reward good security habits, and foster psychological safety where employees report issues without fear of blame. 
  • Process provides structure and balance between the other pillars. Embed security governance into workflows, performance measures, and decision-making routines across business functions.
  • Technology amplifies capability and supports the structure built. Invest in frictionless, adaptive solutions that enable security by design and reduce complexity for users.

Together, these pillars create a resilient ecosystem where security becomes second nature not a separate discipline.


Measuring Readiness

Run annual board-led tabletop exercises to test decision-making and communication readiness. Track key indicators such as time-to-decision, time-to-public communication, and exercise frequency. Maintain pre-approved playbooks for communications, legal response, and escalation paths.

Leadership should:

  • Approve the top 5-10 enterprise cyber risks and risk appetite definitions.
  • Endorse funding for a CRQ pilot and prioritized CIS Controls implementation.
  • Commit to an annual tabletop exercise and a monthly top-risk dashboard.


Conclusion

It's an honor to help empower cybersecurity and business leaders with strategies that transform technical risk into business urgency and position cybersecurity as a true business driver.

A modern take on the Security "CIA Triad" extends beyond confidentiality, integrity, and availability to include:

  • Communication — telling the "why" story that resonates across the enterprise.
  • Integration — fostering genuine, enterprise-wide partnership.
  • Adaptation — driving innovation to advance the organization's mission.

This discussion extends and deepens the conversation around cybersecurity as a business imperative. A leadership discipline that drives trust, resilience, and competitive advantage.





Wednesday, November 5, 2025

Software Supply Chain in Crisis

CISO panel discussion at Cyber Defense Conferences on evolving third-party and AI supply chain risks

Third-party and software supply chain threats are escalating in complexity and frequency, driven by trusted access, automation, and the rapid adoption of AI. Traditional governance models reliant on static assessments and siloed controls are no longer sufficient. A shift toward continuous, integrated, and behavior-based security is imperative.


Key Insights

  • Fundamentals still matter
    Core security principles including strong credentials, least privilege, layered defenses, and Zero Trust Architecture (ZTA) remain foundational. These principles must extend across third-party ecosystems.
  • Third-Party risk is a growing threat vector
    Attackers exploit trusted relationships, leveraging vendor access, CI/CD credentials, and automated update pipelines to bypass controls. The software supply chain remains fragile due to fragmented ownership across AppSec, CloudSec, and Vendor Risk.
  • AI-Native Dependencies Expand the Attack Surface
    AI vendors introduce opaque models, broad API integrations, and sensitive data flows. This creates new risks: model tampering, data leakage, and abuse of delegated access.
  • Velocity Outpaces Governance
    The scale and speed of modern development particularly with GenAI have outstripped traditional security and compliance models. Manual vetting can no longer keep pace.
  • Nation-state and ransomware threats converge
    Adversaries increasingly target SaaS and developer ecosystems for espionage, disruption, and extortion. Supply-chain compromise offers persistent access and high-leverage impact.


Strategic Actions

  1. Modernize vendor governance
    Transition from static questionnaires to continuous trust models. Require SBOMs, runtime attestations, CI/CD hygiene evidence, and enforce phishing-resistant MFA and rapid credential revocation.
  2. Institutionalize continuous validation
    Adopt CTEM-like models for third-party and supply chain risk. Automate dependency scanning, runtime enforcement, and least-privilege enforcement for connectors and APIs.
  3. Govern AI-generated code
    Implement CI policies requiring AI-generated code to be flagged, scanned, and reviewed especially for critical modules. Make this process auditable and enforceable.
  4. Prepare for supply chain campaigns
    Develop cross-functional incident playbooks. Simulate package compromise scenarios, enforce CI runner isolation, and ensure rapid token rotation and rollback capabilities.
  5. Unify ownership across domains
    Assign a supply-chain risk owner e.g., CISO, Legal, and IT lead) with authority to enforce cross-team controls. Align SLAs and runbooks across AppSec, DevOps, CloudOps, and Vendor Risk.


Securing today's dynamic and delicate supply chain eco-system demands more than tools but a strong third-party risk management program rooted in risk-based tolerance approach through execution of  enterprise-wide partnership, trusted vendor relationships, and continuous validation. Next up, 4th-parties...