LLMs Change - Where Should Knowledge Live? (Lessons From SBOM)
Provides LLMs Change - Where Should Knowledge Live? (Lessons From SBOM) and evaluates key implications for security practitioners.
Summary
Overview: Large Language Models (LLMs) are widely used to search, summarize, and generate answers. They are powerful, but results are not always stable and can be difficult to verify. Many systems use Retrieval-Augmented Generation (RAG) to connect LLMs with external data. This helps, but does not fully solve the problem. The same question can produce different answers depending on the model or context, making knowledge hard to manage. This raises a simple question: where should knowledge be managed? A si
Key Topics: milar issue exists in software supply chains. SBOM (Software Bill of Materials) makes components and relationships visible, but is often treated as static data. Based on hands-on experience designing graph-based knowledge systems, this session introduces a design approach: managing knowledge outside LLMs as structured, persistent data.
Related talks
The Linux Foundation·37 min
Yongjae Chung · Justin Cappos
Evaluates SBOMs Arent Enough. Secure Your Software Supply Chain End-To-End and evaluates key implications for security practitioners.
The Linux Foundation·44 min
Joshua Watt
Demonstrates complying With Regulatory SBOM Requirements Using the Yocto Project and evaluates key implications for security practitioners.
The Linux Foundation·33 min
Takashi Ninjouji · Hiroyuki Ishii
Details automation of SBOM Assessment in AGL Development Process and evaluates key implications for security practitioners.


