New in Dradis Pro v5.5

Issue Library entries can have multiple translations, so the same finding can reach each client in their own language.

Two new calculators, STRIDE and AIVSS-SSVC, widen how you classify and score Issues.

And Dradis now tells you when a teammate is already editing the record you’ve opened.

Here’s what’s new!

Record Locking

Two testers editing the same finding at the same time is a reliable way to lose someone’s work. Dradis now tells you when a team member is already editing the record you’ve opened, and who it is. You can go back, or edit anyway.

This covers every record you edit: Issues, Evidence, Notes, Content Blocks, Cards, Issue Library entries, and Remediation Tracker tickets. To try it, open a record a teammate is currently editing.

IssueLibrary Translations

If you deliver reports in more than one language, you’ve probably kept a copy of each Issue Library entry per language and watched them drift apart. Now each entry holds a translation for every locale, and each project has its own Issue Library locale. Entries you import into a project, and Rules Engine matches against scanner output, use the translation for that project’s locale.

To try it, add a translation to an Issue Library entry, then set the Issue Library locale when you create or edit a project. Translations and locales are also available through the new v2 Issue Library API.

STRIDE and AIVSS-SSVC Calculators

Two new calculators are available from the Issue view. STRIDE records which of the six threat categories apply to an Issue: Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, and Elevation of Privilege. AIVSS-SSVC is built for findings in agentic AI systems: score the finding, then select a remediation outcome of Defer, Scheduled, Out-of-Cycle, or Immediate.

To try it, open an Issue and pick STRIDE or AIVSS-SSVC from its calculators.

Remediation Tracker Liquid and Links

Issues that use Liquid Dynamic Content used to reach Remediation Tracker with the raw tags in place of the text your report shows. Now the Liquid is rendered when you send the Issue, so the ticket shows the final text. Each ticket also gets Project, Issue, and Evidence fields with labeled links back to the source, plus a list of its Evidence.

To try it, send an Issue that uses Liquid to Remediation Tracker and open the ticket.


Release Notes

  • Dashboard: add issue grouping by report template List fields
  • Echo: Allow Roslin’s LanguageTool grammar and spell checking language to be changed
  • Editing: Warn user if another user is currently editing a record
  • Forms: show errors next to their fields instead of at the top of the form
  • Issue Library: Add translations for Entries
  • Nodes: Add a node from the node tree
  • Projects: set a project’s Issue Library locale on create and update
  • QA: show issue, evidence and content block states as colored badges in tables and tabs
  • Releases: notify users when a new Dradis release is available
  • Rules Engine: replace and match finding bodies with the Issue Library translation for the project’s locale
  • Webhooks:
    • add Board, List and Card CRUD events
    • add Content Block, Evidence, Node and Note CRUD events, Issue and Content Block state changes, inline thread lifecycle events, Comment and Echo Session creation, and Personal Access Token lifecycle events
    • add Evidence QA state change events
  • Upgraded gems:
    • addressable, crass, loofah, net-ssh, nokogiri, rack, rails, rails-html-sanitizer, sanitize
  • Bug fixes:
    • Avatars: display a local image while Gravatar loads
    • Combobox:
      • keep dropdown menus within the viewport and fit long option labels
      • show inline validation errors on dropdowns that fail validation
    • Dashboard: keep issue chart columns distinct when group labels match
    • Diffs: remove stray escape characters around highlighted changes
    • Editor: keep the cursor in place after uploading an image
    • Evidence:
      • publish a dedicated state change event for single and bulk QA updates
      • show the State column in the node evidence table
    • Kits: keep report template settings when re-uploading a downloaded kit
    • Sidebar tips: tone down the tips box in dark mode and keep its links readable
    • Word: use valid four-byte identifiers for generated list definitions
  • New integrations:
    • Calculators:
      • AIVSS-SSVC
      • STRIDE
  • Integration enhancements:
    • Remediation Tracker:
      • Render Liquid when sending an Issue to Remediation Tracker
      • Split source links into Project, Issue, and Evidence fields with labeled links and an evidence list
      • Warn user if another user is currently editing a ticket
    • Scheduler: reuse the team color palette in darker shades when there are more than 20 teams
  • Reporting enhancements:
    • Word: reduce repeated field parsing and text conversion when generating large reports
  • REST/JSON API enhancements:
    • Boards: add support for repositioning lists and moving cards within and between lists
    • Evidence: add state selection on API v3 create/update and include state in responses
    • Issue Library:
      • add v2 with entry translations, reading an entry in a locale, and locales
    • Personal Access Tokens (PAT):
      • add card and list positioning support through their update scopes
      • add IssueLibrary API scopes
  • Security Fixes:
    • Medium: Authenticated (author) persistent cross-site scripting around issue imports

Not using Dradis Pro?

Leave a Reply

Your email address will not be published. Required fields are marked *