Skip to content

v7.9.0 - AI Navigator, Tradecraft 2.0, tenant-filter fixes

Latest

Choose a tag to compare

@samugit83 samugit83 released this 19 Nov 19:03

Highlights

Added: AI Navigator, a chat that answers questions about RedAmon and about your project. A chat button sits on every page. You can drag it anywhere and resize its panel by the edges. It answers two kinds of question:

  • How RedAmon works. Answers come from the documentation and link to the exact section on redamon.org and the GitHub wiki.
  • The selected project's data. It covers the graph, findings, scans and versions, settings, triage, remediations, reports and workspace files.

Navigator only reads. If you ask it to do something, it hands the request to the AI Agent ("Open the AI Agent").

  • It runs on each person's own model. Pick it in Global Settings → Models by feature → AI Navigator; the first message asks if none is set.
  • It reads only what that person may read, and checks this on every call.
  • Each person's conversations stay private, per project.

A new permission, navigator:use, is in every built-in member set except Automation. Owners choose in the share dialog whether collaborators can use Navigator on their project. This is off by default, because the project's data would go to each collaborator's own AI provider. Root turns Navigator on or off for everyone in IAM → Instance.

Added: Tradecraft 2.0, each account's knowledge library. Global Settings → Tradecraft keeps a library of trusted hacking-knowledge sites. The agent searches and reads this library during an engagement.

  • Background ingestion. Adding, editing or refreshing a resource starts a job. The card shows its stage, and Cancel stops it. The previous version stays in use until the new one is ready. Nothing runs on a timer.
  • Live or Stored. A Live resource (the default) keeps the site map and the page cards, and reads each page from its site. A Stored resource also keeps a cleaned copy of every page in your database. Stored pages count against a quota of 1 GB per account (by default) and 20 GB per install.
  • Every page gets a card: its title, its place in the site, headings, a one-line description, and tags for topic, content kind and technology.
  • Three agent tools:
    • tradecraft_search searches the library with no model call.
    • tradecraft_lookup reads one section of one page by its page ID, such as patt:412.
    • tradecraft_ask, the librarian, takes a vague need ("the WAF blocks SLEEP") and answers with up to three checked pages and exact excerpts.
  • Library now. When a page fits the step the agent is working on, its think step sees up to 3 of the library's best pages. The agent reads them before falling back on its own knowledge or a web search.
  • More site types and controls:
    • With a GitHub token, CVE archives are indexed (up to the 20,000 largest CVE files, with no text stored).
    • Docs sites are mapped from their search index or their sitemaps.
    • Website crawls can be rule-based, LLM-guided, or Auto.
    • An ingestion focus keeps everything, keeps only chosen topics (Focused), or keeps everything and tags it (Tag only).
    • Private sites can use a site login.
    • A Map view lets you search, read, pin, block and restore pages.
  • Per project: each resource has its own switch in the Agent Skills & Tradecraft tab.

See the wiki page Tradecraft Lookup and README.TRADECRAFT.md.

Security

  • A \uXXXX escape could hide Cypher from the tenant filters. Neo4j decodes the escape before it reads the query. A crafted string could therefore end for Neo4j but not for the filter, and a UNION branch or a procedure call after it ran with no tenant filter. That allowed reading another project's graph, or making the database fetch a URL. These paths now refuse any \uXXXX escape: the agent's query_graph, /graph/exec, raw Cypher in MCP query_graph, the sandbox's redagraph, and saved graph views.
  • Neo4j loads only the APOC procedures RedAmon calls. It used to load every apoc.* procedure, and apoc.load.* and apoc.cypher.* are no longer available.
  • A failed graph query no longer writes the query or a value to the logs. Only the error code and class are logged.
  • tradecraft_lookup could read any public URL, and could send the project owner's GitHub token to any GitHub address. 7.8.0 was also affected. Now:
    • A forced path reads only a page of the resource.
    • The token goes only to the resource's own repository.
    • Only the owner's own run reads with a token.
  • A wiki's mkdocs.yml could exhaust the agent's memory through YAML aliases. The file is now read up to 10 MB, and its navigation is walked within the map limit.
  • Site logins stay with their owner and their host.
    • A login is sent only to the resource's own host, checked again at every redirect.
    • It never goes through the browser, and it is used only in the owner's own runs.
    • Moving a resource to another host requires typing the login again.
    • Every change to a login is audited, without its value.
  • Tradecraft no longer shares a page cache between accounts. Refresh and Verify no longer return the resource's GitHub token, and the internal route that listed resources with unmasked tokens is gone.
  • The browser fallback blocks WebSockets, popups and peer connections to internal addresses.
  • Library text is treated as untrusted everywhere. Every Tradecraft result, and all page text a model reads, sits inside the untrusted envelope. The librarian's answers are checked in code.
  • A Rules of Engagement ban on query_graph or tradecraft_lookup also covers their companion tools. Those are graph_schema and graph_summary for the first, and tradecraft_search and tradecraft_ask for the second. The ban applies in single tools, parallel plans and fireteams.

Fixed

  • A chat that closed during its run no longer keeps its session slot. Enough of these slots used to reach MAX_AGENT_SESSIONS, and then new chats were refused.
  • Allow on a tool or wave card takes effect at the click, so a second click no longer sends a second answer.
  • Update Settings in a node's settings modal (workflow view) no longer waits on a prompt hidden under the modal.
  • The project Activity link is now a button in the Project Settings header. It asks before you leave with unsaved changes.
  • Clearing a number in the project form falls back to its default. A typed 0 stays 0 where 0 means no limit.
  • AI Navigator's citation chips are easy to read in light mode.

Before you update

  • Tradecraft 2.0 replaces Tradecraft 1.x for every account, with no switch to keep 1.x.
    • At the agent's first start after the update, your resources are converted from the maps they already have. Nothing is downloaded, no model is called, and the resources show Ingested before 2.0.
    • Global Settings → Tradecraft then offers Save & refresh all once. It gives the resources headings, descriptions and search inside their pages. A refresh calls each resource's model.
  • Adding or turning on a Tradecraft resource asks for a librarian model while Librarian use is set to Agent decides (the default). Choose one in Models by feature → Tradecraft librarian, or set Librarian use to Search only, which needs no model.
  • Admins with custom permission sets: custom sets show navigator:use as available, not granted. Add it to the sets that should use AI Navigator.
  • The old Tradecraft page-cache volume (redamon_tradecraft_cache) is deleted once. Its content was disposable. To keep it, run touch .tradecraft-cache-removed at the repository root before updating.
  • Some projects get new Tradecraft phases, once. Where tradecraft_lookup was allowed in exactly exploitation and post-exploitation, it becomes allowed in all three phases. The audit log's system.tradecraft_phases_backfill row lists the projects that changed.
  • Scripts that call other APOC procedures stop working. If you run your own script against the stack and it calls an APOC procedure RedAmon does not use, it now gets "no procedure registered".
  • New projects start with the CVE (MSF) skill off. Existing projects keep their choice.

Upgrade

./redamon.sh update
  • The update fetches the documentation submodule (redamon.wiki) that AI Navigator answers from.
  • It also changes docker-compose.yml so the agent mounts the wiki read-only, which makes it rebuild every core image once.
  • The agent and the webapp must be updated together.
  • No environment variable is added.
  • All data changes are additive: eight Tradecraft tables, 18 columns and the pg_trgm extension. Databases, scan results and reports are kept.

Rolling back to 7.8.0 deletes data. It drops every AI Navigator conversation, every owner's collaborator choice, and the Tradecraft 2.0 tables and columns with their data. Back up the database first. Your Tradecraft resources still work on 7.8.0.

Full details in CHANGELOG.md.