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)
Hello everyone, the latest license information for November, 2025 can be found here:
license_threat_groups_11302025.csv (99.9 KB)
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)
Hello everyone, the latest license information for December, 2025 month end can be found here:
license_threat_groups_12312025.csv (101.3 KB)
Is there any discussion/plans around improving this process?
a) finding the new threat groups .csv
b) updating to the new threat groups
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.
Hello everyone, the latest license information for January, 2026 month end can be found here:
license_threat_groups_01312026.csv (102.3 KB)
Hello everyone, the latest license information for February, 2026 month end can be found here:
license_threat_groups_02272026.csv (103.5 KB)
Hello everyone, the latest license information for March, 2026 month end can be found here:
license_threat_groups_03302026.csv (104.8 KB)
Hello everyone, the latest license information for April, 2026 month end can be found here:
license_threat_groups_04302026.csv (106.3 KB)
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?
Hello everyone, the latest license information for May, 2026 month end can be found here:
license_threat_groups_05312026.csv (107.4 KB)
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.