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.
Hi all. The latest license mappings from 2024-07-30 are here:
license_threat_groups_07302024.csv (78.2 KB)
Hello! The latest license mappings from 2024-08-29 are here:
license_threat_groups_08292024.csv (79.3 KB)
Hello! The latest license mappings from 2024-09-26 can be found here:
license_threat_groups_09262024.csv (80.5 KB)
Hello everyone, the latest license information for Oct, 2024 can be found here:
license_threat_groups_10312024.csv (81.5 KB)
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?
Hello everyone, the latest license information for Nov, 2024 can be found here:
license_threat_groups_11282024.csv (83.2 KB)
Hello everyone, the latest license information for December, 2024 can be found here:
license_threat_groups_01062025.csv (85.2 KB)
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?
Thanks.
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.
Thanks Jonathan.
Is it possible to make the current LTG listing available via CLI? Or another option?
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"
},
]
}
]
}
]
}
Hello everyone, the latest license information for January, 2025 can be found here:
license_threat_groups-01312025.csv (86.2 KB)
Hello everyone, the latest license information for February, 2025 can be found here:
license_threat_groups_02282025.csv (87.1 KB)
Hello everyone, the latest license information for March, 2025 can be found here:
license_threat_groups_04042025.csv (88.5 KB)