Skip to content

Portals

Client reporting portals (their own vuln tracker, a shared GRC tool, a custom finding form) rarely match Raven's finding shape. Portals turns any Raven finding into paste-ready text for whatever form the client makes you fill in. You copy, paste, review, and submit, instead of re-typing every field by hand.

You drive it from the Portals section of the web dashboard, and from the Copy for portal ▾ dropdown on any finding.

Only the learn step draws AI credits

Copying a finding for a portal, saving a field map, and filling portals from a saved template are all deterministic and work with no credits. Only learning a field map from a pasted form uses AI. Without credits you can still build a template by hand and use it normally.

Two ways to fill a portal

Templates: learn once, fill deterministically. Paste a portal's finding form into Portals once. Raven makes a single AI pass to learn the form's fields and you confirm the map. After that, every finding fills that portal's exact field names deterministically (no AI, no network, no re-paste). This is the path to use for a portal you'll submit to more than once.

Generic browser-AI prompt: the no-template quick path. For a one-off portal you don't want to template, Raven builds a paste-ready prompt. You paste it into a browser AI alongside the open form, and the AI field-matches Raven's finding onto whatever fields the form has. No setup, but it leans on an external AI rather than a saved map.

Either way, you stay in the loop and submit manually. Raven produces text only. It never talks to the portal and never automates the browser. Fields it can't fill are flagged [you fill].

How it works

  1. Add a portal once (optional): paste its finding form under Templates. Raven learns the fields in one AI pass; you confirm the map.
  2. On any finding, use Copy for portal ▾ and either pick your saved template (deterministic fill with the portal's real field names) or pick Generic prompt (browser-AI field-matching).
  3. Paste into the portal. The client's real names, hosts, and domains are kept intact; the portal is their actual deliverable.
  4. Review and submit it yourself. Raven never auto-submits. Anything it couldn't fill is flagged [you fill].

Use Copy all findings to build one block per finding, divider-separated, so you can grab them one at a time as you work down the form.

Secret redaction

Portals output is safe to paste into a client-facing form: cracked cleartext passwords and NTLM / NetNTLM password hashes are redacted from the generated text. Client identity (real hostnames, domains, and names) is deliberately preserved, because the portal is the client's own deliverable and needs their real assets named.

Learning a template is the one place Portals uses AI (a single pass over the form you paste). Filling findings from a saved template is fully deterministic (no AI, no network), so the redaction rail is the only thing that ever leaves your machine, and only when you use the generic browser-AI prompt.