Bookmarks

    Nothing saved yet. Use the bookmark on any article. Bookmarks are kept on this device only: they stay private and work without an account.

    Settings

    Appearance

    Reading mode

    Font size

    Content width

    Line spacing

    Keyboard shortcuts

    /
    Search
    j k
    Next / previous story
    ← →
    Previous / next section (columns)
    b
    Bookmarks
    s
    Settings
    r
    Columns / scroll
    t
    Light / dark

    Saved in this browser only.

    Ping2Prompt
    Subscribe to the Weekly Brief Sign in
    A glowing backlit panel showing a printed circuit board schematic with chips and traces in white lines on a dark background.
    Photo by Adi Goldstein on Unsplash

    DefectDojo 3.5.200 adds Trivy, Grype and Syft package data and fixes

    DefectDojo

    What changed

    DefectDojo 3.5.200 lists all changes merged since 3.5.103. Trivy, Grype and Syft imports now record the package URL and CPEs on dependency locations. The risk acceptance expiration run now bounds the number of messages it sends.

    Notable fixes:

    • Reimport by test title now goes into the test of the report's tool.
    • A finding is closed as mitigated when the close body omits is_mitigated.
    • Reinstating a risk acceptance leaves out findings closed since the expiry.
    • The UI refuses marking a finding as a duplicate of itself or of a cluster root.
    • delete_preview in the API is served only to a caller the DELETE would admit.

    Who needs to act

    Self-hosters should read the upgrade notes in the DefectDojo documentation before upgrading, as they hold release-specific and general instructions. The sources give no explicit list of breaking changes, only that pointer.

    What the sources don't cover

    The release page gives no release date, container image locations or hardware requirements.

    Sources

    Image: Photo by Adi Goldstein on Unsplash


    This story was produced with AI assistance from the sources listed above and fact-checked against them before publication. Read our editorial methodology and the corrections log. Spotted an error? Email [email protected].

    Continue

    Share on Bluesky · Mastodon · Email ·

    Discussion