Posts

#4267 Structural RAG

Image
#4267 Structural RAG PageIndex: Reasoning-Based Vectorless RAG Framework https://youtu.be/H5jHCh588o4 #4267  Describe an alternative to embedding and indexing for RAG. Consider a plain text toc for topics within a document. While vector embeddings are the "gold standard" for RAG right now, they often feel like using a sledgehammer to crack a nut—especially for single, long documents where semantic search can lose the forest for the trees. An excellent alternative is Structural Metadata Navigation (or "Map-Guided Retrieval"). Instead of turning text into high-dimensional math, you treat the document like a library with a highly efficient librarian. The Concept: Structural Metadata Navigation In this approach, you use a Plain Text Table of Contents (TOC) as a high-level "map" for the LLM. Instead of searching for similar meaning , you search for relevant locations . How it Works The Mapmaker: You (or a lightweight LLM pass) extract a detailed TOC with hea...

#4266 Knowledge Graph: Cyber Attacks

Image
#4266 Knowledge Graph: Cyber Attacks #4266  I want to develop a knowledge graph to find patterns in cyber attacks for data like: attacker, type of attack, target of attack. What would be other good information to include? Building a knowledge graph for cyber attacks is a powerful way to move from "detecting incidents" to "understanding adversaries." While Attacker , Type , and Target are the core, they only tell you what happened. To find deep patterns, you need the how , where , and so what . Using the STIX 2.1 and MITRE ATT&CK frameworks as your "vocabulary," here is the additional information you should include to make your graph truly analytical. 1. The "How": Tactics, Techniques, & Procedures (TTPs) This is the most critical layer for pattern recognition. Attackers often change their tools or IP addresses, but they rarely change their habits (TTPs). Tactics: The attacker's goal (e.g., Persistence, Privilege Escalation, Exfil...