S3C2 SICP Summit 2025-06: Vulnerability Response Summit

Anna Lena Rotthaler, Simon Oberthür, Juraj Somorovsky, Kirsten Thommes, Simon Trang, Yasemin Acar, Michel Cukier, William Enck, Alexandros Kapravelos, Christian Kästner, Dominik Wermke, Laurie A. WilliamsarXiv 2025 · DOI · arXiv

TL;DR

This paper summarizes a summit where industry practitioners and researchers discussed the challenges and best practices in software supply chain vulnerability response. Key takeaways highlight the evolving landscape of vulnerability reporting, the complexities of assessment and remediation, the need for better tooling and standardization, and the impact of upcoming regulations like the Cyber Resilience Act.

What Problem Does This Paper Address?

The increasing frequency and impact of cyberattacks targeting the software supply chain have made vulnerability response a critical concern for businesses and governments. Despite this, there's a gap in understanding the practical challenges faced by industry professionals in managing and responding to these vulnerabilities. This paper addresses this by bringing together practitioners and researchers to share experiences, identify common pain points, and explore potential solutions and research opportunities in the realm of software supply chain security and vulnerability response.

Methods

The paper details a one-day summit organized by the NSF-supported Secure Software Supply Chain Center (S3C2) and the Software Innovation Campus Paderborn (SICP). The summit involved nine practitioners from nine different companies, operating under Chatham House Rules to encourage open discussion. The methodology included:

  • Pre-Summit Survey: Participants voted on topics for panel discussions, ensuring the agenda reflected current industry challenges.
  • Keynote Presentation: Setting the stage for the day's discussions.
  • Five Panel Discussions: Each panel focused on a specific aspect of vulnerability response, with initial statements from selected participants followed by open discussion. Topics included experiences with vulnerability reporting, assessing and fixing vulnerabilities, tools for vulnerability management, organization of vulnerability reporting, and the impact of regulations like the Cyber Resilience Act (CRA) and NIS2.
  • Note-Taking and Synthesis: Researchers (professors, scientific employees, and PhD students) took detailed notes during the discussions. A draft summary was then jointly created and reviewed by all attendees and authors to ensure accuracy and completeness.

Datasets

Not discussed in the paper.

Key Insights and Ideas

  • Shift Towards Transparency: Companies are moving away from hiding vulnerabilities due to fear of appearing low-quality, embracing transparency to build customer trust.
  • Vulnerability Reporting is Evolving: While a single, easily discoverable email address is preferred for reporting, many vulnerabilities are still reported by customers rather than dedicated security researchers.
  • Assessment is Human-Centric: Automating vulnerability assessment is difficult due to the need for deep product and context knowledge. Criticality decisions often rely on human expertise, leading to potential biases (e.g., overestimating severity).
  • Fixing Timelines are Pressured: The typical 90-day window for fixing vulnerabilities is being challenged by new regulations, and the volume of reports is expected to increase significantly.
  • Tooling Challenges Persist: While tools exist for known vulnerabilities, there's a lack of comprehensive solutions for novel threats. Usability, false positives, and integration issues remain significant problems. The desire for a "single source of truth" for vulnerability data is strong.
  • Regulatory Impact is Significant: The Cyber Resilience Act (CRA) and NIS2 are driving substantial changes in how companies approach security, requiring new processes, expertise, and potentially increasing costs, especially for smaller businesses.
  • Bug Bounties are Niche: Bug bounty programs are seen as a sign of high maturity, but their value is not universally apparent, particularly in B2B contexts, and they are often viewed as a commercialization of vulnerability research.

Key Results

The paper doesn't present quantitative results in the traditional sense but rather synthesizes qualitative findings from the summit discussions. Key qualitative findings include:

  • Common Challenges: Difficulty in assessing vulnerability criticality, the need for specialized human expertise, the complexity of integrating security tools, and the significant impact of upcoming regulations (CRA, NIS2) were recurring themes.
  • Practitioner Preparedness: Attendees feel generally prepared for NIS2, but express uncertainty and concern regarding the implementation and cost of compliance with the CRA.
  • Tooling Gaps: A significant gap exists in tools that can provide a unified view of vulnerabilities and handle the output of various scanners effectively. The need for standardization (e.g., SPDX, CycloneDX, VEX) to enable better data exchange between tools was emphasized.
  • Organizational Structures: Dedicated structures for vulnerability reporting are common, often built around ISO 27001, with clear escalation paths.

Limitations and Future Work

Limitations:

  • Small Sample Size: The summit involved only nine practitioners from nine companies, limiting the generalizability of the findings to the broader industry.
  • Chatham House Rules: While encouraging open discussion, these rules prevent the identification of specific companies or their practices, making it harder to draw concrete examples.
  • Focus on Specific Regions/Regulations: The discussions were heavily influenced by European regulations (CRA, NIS2), which might not fully reflect global challenges.

Future Work:

The paper implicitly suggests several areas for future research and development:

  • Improved Vulnerability Assessment Tools: Developing tools that can better incorporate context and reduce reliance on manual assessment.
  • Standardization Efforts: Continued work on and adoption of standards like SPDX, CycloneDX, and VEX to facilitate tool interoperability and data exchange.
  • Regulatory Compliance Strategies: Research into cost-effective ways for companies, especially SMEs, to comply with new regulations like the CRA.
  • Understanding B2B Bug Bounties: Further exploration of how bug bounty programs can be effectively implemented and valued in business-to-business contexts.
  • AI in Vulnerability Management: While not currently perceived as helpful, future research could explore how AI might assist in vulnerability assessment and prioritization.

Summary updated

BibTeX
@misc{rotthaler2025s,
  author = {Anna Lena Rotthaler and Simon Oberthür and Juraj Somorovsky and Kirsten Thommes and Simon Trang and Yasemin Acar and Michel Cukier and William Enck and Alexandros Kapravelos and Christian Kästner and Dominik Wermke and Laurie A. Williams},
  title = {{S3C2 SICP Summit 2025-06: Vulnerability Response Summit}},
  year = {2025},
  eprint = {2512.02600},
  archivePrefix = {arXiv},
  url = {https://arxiv.org/abs/2512.02600},
}
Figure