Update Your IQ Server License Threat Groups - Sonatype Labs - Sonatype Community

post by twinter on May 16, 2024

Hello everyone!

We have a new release of the License LTG Updater that contains support for the new AI-ML LTG and associated licenses:

ltg-updater-1.0.3.jar (8.4 MB)

Additionally, here are the latest license mappings:

license_threat_groups_04302024.csv (74.1 KB)


post by ovoronin on Jun 18, 2024

Hi all. The latest license mappings from 2024-05-28 are here:

license_threat_groups_05282024.csv (76.2 KB)


post by jplevac on Jul 19, 2024

Hi all. The latest license mappings from 2024-06-28 are here:

license_threat_groups_06282024.csv (77.3 KB)


post by djb on Jul 26, 2024

I have to agree with @u.maurer, this seems like the wrong channel for a versioned official .jar. Why not a separate page like how the Reference Policy files are provided? Feels like a similar use case.


post by jplevac on Aug 6, 2024

We realize this process is painful and are looking at ways of automating some of these steps. I’ll forward your message to appropriate internal stakeholders.


post by jplevac on Aug 6, 2024

Hi all. The latest license mappings from 2024-07-30 are here:

license_threat_groups_07302024.csv (78.2 KB)


post by twinter on Sep 17, 2024

Hello! The latest license mappings from 2024-08-29 are here:

license_threat_groups_08292024.csv (79.3 KB)


post by twinter on Oct 7, 2024

Hello! The latest license mappings from 2024-09-26 can be found here:

license_threat_groups_09262024.csv (80.5 KB)


post by twinter on Nov 1, 2024

Hello everyone, the latest license information for Oct, 2024 can be found here:

license_threat_groups_10312024.csv (81.5 KB)


post by tiam-shin.yong on Nov 11, 2024

Hello. I agree with the comments here. As an admin of IQ, this update process is challenging due to the number of licenses in the LTG. While the version updates and the tool are useful, they do not apply to our use case, where we customize our LTG based on IT Law guidance. Currently, there is no efficient way to compare the list of licenses in the updated LTG with those configured in IQ (other than manually) to identify discrepancies and decide whether to update the policies.

It would be great if you could automate this process or provide a UI feature to identify the differences between the updated list and the customer’s IQ list. If this update tool is intended to automate updates, why not integrate it into the IQ release so that policies are updated automatically when the IQ version is upgraded?


post by twinter on Dec 13, 2024

Hello everyone, the latest license information for Nov, 2024 can be found here:

license_threat_groups_11282024.csv (83.2 KB)


post by jplevac on Jan 14, 2025

Hello everyone, the latest license information for December, 2024 can be found here:

license_threat_groups_01062025.csv (85.2 KB)


post by jonathan.solan on Feb 7, 2025

Hi,

I have a quick question.

Are these group updates not included with the IQ Server releases? Do the group updates have to be performed manually?


post by jzora on Feb 7, 2025

That’s correct, Jonathan. New license data is added to the platform all the time, but threat groups need to be updated manually. We do this so as not to overwrite any modifications your organization’s legal teams may have made.

For more details, check our documentation on the topic.


post by jonathan.solan on Feb 11, 2025

Thanks Jonathan.

Is it possible to make the current LTG listing available via CLI? Or another option?


post by djb on Feb 13, 2025

You can GET this undocumented endpoint for a list of LTGs: https://{{iq_url}}/rest/licenseThreatGroup/organization/{{organization_id}}.

But, add /applicable on the end of the above to return the individual licenses within each of those returned LTGs.

{
  "licenseThreatGroupsByOwner": [
    {
      "ownerId": "example_org_id",
      "ownerName": "Example Org",
      "ownerType": "organization",
      "licenseThreatGroups": [
        {
          "id": "xb3q7cvt27d5323aa677899398a4c74d",
          "name": "Banned",
          "threatLevel": 10,
          "licenses": [
            {
              "id": "h9d3c52fgtyu4b956p3f5935y309u973",
              "ownerId": "example_org_id",
              "licenseThreatGroupId": "vd3f7fbd27d5423aa698765098a4c67d",
              "licenseId": "GPL-3.0"
            }
          ]
        }
      ]
    }
  ]
}

post by jplevac on Feb 18, 2025

Hello everyone, the latest license information for January, 2025 can be found here:

license_threat_groups-01312025.csv (86.2 KB)


post by jplevac on Mar 17, 2025

Hello everyone, the latest license information for February, 2025 can be found here:

license_threat_groups_02282025.csv (87.1 KB)


post by nsai on Apr 4, 2025

Hello everyone, the latest license information for March, 2025 can be found here:

license_threat_groups_04042025.csv (88.5 KB)


post by nsai on Apr 28, 2025

Hello everyone, the latest license information for April, 2025 can be found here:

license_threat_groups_04282025.csv (89.6 KB)


post by nsai on May 27, 2025

Hello everyone, the latest license information for May, 2025 can be found here:

license_threat_groups_05272025.csv (90.7 KB)


post by nsai on Jun 26, 2025

Hello everyone, the latest license information for June, 2025 can be found here:

license_threat_groups_06262025.csv (92.0 KB)


post by nsai on Aug 1, 2025

Hello everyone, the latest license information for July, 2025 can be found here:

license_threat_groups_07312025.csv (93.0 KB)


post by nsai on Aug 28, 2025

Hello everyone, the latest license information for August, 2025 can be found here:

license_threat_groups_08282025.csv (94.3 KB)


post by nsai on Sep 29, 2025

Hello everyone, the latest license information for September, 2025 can be found here:

license_threat_groups_09292025.csv (95.6 KB)

Hello everyone, the latest license information for October, 2025 can be found here:

license_threat_groups_11012025.csv (97.6 KB)


post by nsai on Dec 1, 2025

Hello everyone, the latest license information for November, 2025 can be found here:

license_threat_groups_11302025.csv (99.9 KB)


post by nsai on Dec 3, 2025

Hello everyone, the latest license information after a priority release for December, 2025 can be found here:

license_threat_groups_12032025.csv (100.3 KB)

Updated version of file:

license_threat_groups_12042025.csv (100.3 KB)


post by nsai on Dec 31, 2025

Hello everyone, the latest license information for December, 2025 month end can be found here:

license_threat_groups_12312025.csv (101.3 KB)


post by mlthien on Jan 6

Is there any discussion/plans around improving this process?

a) finding the new threat groups .csv

b) updating to the new threat groups


post by jzora on Jan 6

Hi, Michael,

Good question. We’re aware of the inefficiency here and are exploring some options to make the process feel a little less like hunting buried treasure. Stay tuned.


post by nsai on Jan 31

Hello everyone, the latest license information for January, 2026 month end can be found here:

license_threat_groups_01312026.csv (102.3 KB)


post by nsai on Feb 27

Hello everyone, the latest license information for February, 2026 month end can be found here:

license_threat_groups_02272026.csv (103.5 KB)


post by Saurabh_Jha on Mar 30

Hello everyone, the latest license information for March, 2026 month end can be found here:

license_threat_groups_03302026.csv (104.8 KB)


post by Saurabh_Jha on Apr 30

Hello everyone, the latest license information for April, 2026 month end can be found here:

license_threat_groups_04302026.csv (106.3 KB)


post by ralf_a on Jun 1

Hello @dgriffin ,

Two weeks ago, we attempted to update the License Threat Groups in our test system. We used version 1.0.3 of the updater tool and the import file dated April 30, 2026. The tool was executed using the recommended parameters: “-d -f”.

However, during the update process, we did not receive any prompts, aside from the final “Approve LTG updates? [Y/n]”. Specifically, there was no prompt of the form _“Keep the existing assignment for ‘X’, assigned to ‘Y’, in organization ‘Z’? [Y/n]”`_. While all standard LTGs appeared to have been successfully updated, all licenses within our two custom LTGs had been deleted.

We observed a similar behavior last year, which is why we have not updated the LTGs on our production system for some time. Unfortunately, this has now resulted in a significant number of licenses not being assigned to any LTG.

Do you have any idea what could be causing this problem?


post by Saurabh_Jha on Jun 1

Hello everyone, the latest license information for May, 2026 month end can be found here:

license_threat_groups_05312026.csv (107.4 KB)


post by jzora on Jun 1

Hi, Ralf,

Since you’re a customer, I’d recommend opening a ticket with our Support team for this issue. They’ll be able to help you troubleshoot. I’ll follow up on my side, as well.


post by jzora on Jun 18

Hi, all,

Moving forward, for the LTG Updater tool and the associated monthly CSV files, please visit our Knowledge Base article about the topic.

https://support.sonatype.com/hc/en-us/articles/4418674692883-How-to-Update-Sonatype-Lifecycle-IQ-Server-License-Threat-Groups