Flux 2.8 and Helm v4: The GitOps Upgrade Guide

What Flux v2.8 and Helm v4 change for GitOps users — server-side apply, kstatus health checks, CEL expressions, .status.inventory, Cosign v3, and the post-renderer breaking change.

Graph-Powered OSINT: From Data to Investigation with Agentic AI

Open-source intelligence (OSINT) was a graph problem before "graph" became fashionable. An investigation is nothing but entities and relationships with provenance: who talked to whom, which infrastructure belongs to which actor, which documents connect which events. What changed in 2026 is that generative and agentic AI have finally become capable of doing parts of the investigation itself — and the research community is now explicitly combining the two: graphs for structure and provenance, agents for collection and reasoning.

Why OSINT is a graph problem

Every OSINT task maps onto graph operations:

• Entity resolution is node deduplication across noisy sources ("X Corp" vs "X-Corp" vs "xcorp").
• Attribution is subgraph matching against known actor patterns.
• Threat intelligence is temporal graph analysis — the pattern of infrastructure, domains and personas over time.
• Provenance is edge metadata: every relationship needs its source, or the investigation collapses in court.

Generative AI adds a new entry to the list: the investigator itself becomes an agent that walks the graph, forms hypotheses and asks follow-up questions — which is exactly the agentic pattern the wider graph security research has been converging on.

The research is starting to codify it

The single most useful 2026 paper on this topic is the taxonomy work:

• Agentic and Generative AI for Open-Source Intelligence and Cyber Investigations: Taxonomy, Evaluation, and Challenges — finally names the field: a taxonomy of how generative and agentic AI are used in OSINT, how to evaluate those systems, and what the open challenges are. It is exactly the kind of consolidation that tells practitioners the pattern has arrived rather than being a scatter of demos.

Around the taxonomy, the corpus shows the building blocks:

• SENTINEL — a multi-modal early-detection framework for emerging cyber threats from Telegram streams, which is a graph problem in disguise: extracting entities (threat actors, malware, infrastructure) from unstructured multilingual social media and linking them into a knowledge graph.
• The graph-security literature is deep on fraud and anomaly detection with GNNs, and the recent additions increasingly fold those classic methods into agentic pipelines.

The pattern in practice

A modern graph-powered OSINT pipeline, synthesised from the research, looks like this:

1. Collect — agents scrape and monitor open sources (social media, forums, DNS/WHOIS, news, leaked-but-public datasets), producing noisy, multimodal evidence.
2. Extract and resolve — LLMs extract entities and relationships; graph-based entity resolution merges duplicates across languages and formats.
3. Link into a knowledge graph — every edge carries a provenance pointer and a timestamp (this is the non-negotiable graph discipline: OSINT evidence must be auditable).
4. Investigate with agents — the analyst's agent traverses the graph, runs queries, spots connected components that no one asked about, and drafts hypotheses with the underlying evidence attached.
5. Evaluate — the taxonomy from the 2026 survey applies: how do you measure whether the agent found the right thing, and whether its reasoning held up?

The hallucination trap — and why graphs are the antidote

This is the heart of the matter, and it is worth being blunt: generative AI in OSINT without a graph is a liability. An LLM asked to summarise "what do we know about X" will happily invent relationships. When the output is a graph of cited evidence, every claim trails an entity-relation structure that can be checked. The same robustness lesson from RAG applies: poisoned or hallucinated edges propagate through multi-hop reasoning — but with provenance on every edge, you can find, and revoke, the bad hop.

Practical rules:

1. Never let the agent author evidence. The agent proposes relationships; the graph only accepts them with a source pointer. Unverified edges are hypotheses, stored separately.
2. Version the graph. Investigations are temporal; your knowledge graph must be able to answer "what did we know in March?" — this is temporal-graph practice, not a nice-to-have.
3. Evaluate against ground truth. Precision of entity resolution and recall of attribution must be measured before you trust it.

Where this is heading

The convergence is the same one shaping the broader AI-security frontier: agents + knowledge graphs + foundation models, applied to a domain — security — where the cost of error is uniquely high. Expect the next wave to bring (a) formal evaluation benchmarks for AI in OSINT, (b) graph foundation models tuned on threat intelligence, and (c) provenance-aware agent memory so long investigations accumulate structured, auditable knowledge instead of chat logs.

The short version for security and DevOps teams: the tools now exist to let AI support the investigation — but the graph is what keeps that support honest. Build the provenance first, then let the agents walk the graph.

This article was researched from the graph-research corpus (16,979 papers, 100% taxonomy saturation). Sources: Agentic and Generative AI for OSINT and Cyber Investigations, SENTINEL.