Comparison Overview
Direction interministérielle du numérique (DINUM)

Direction interministérielle du numérique (DINUM)
20, Avenue de Ségur, Paris, 75007, FR
Last Update: 12/06/2026
Informations pratiques, projets, initiatives, chiffres et résultats, mais aussi portraits des acteurs qui transforment le numérique dans l’État : suivez sur cette page l’actualité gouvernementale du numérique au service de l'efficacité de l'action publique, en temps rée...

Belastingdienst
Korte Voorhout 7, Den Haag, NL, 2500 EE
Last Update: 13/09/2026
De organisatie bestaat uit diverse onderdelen, waaronder de Belastingdienst, Douane, Toeslagen, FIOD en enkele facilitaire organisaties. Met ruim 30.000 medewerkers werken we in kantoren die verspreid zijn over het hele land. Gezamenlijk heffen, innen en controleren we ...
Compliance Ranges Comparison

Direction interministérielle du numérique (DINUM)







Belastingdienst






Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
Direction interministérielle du numérique (DINUM) has 102.7% more incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Belastingdienst in 2026.
Incident History - Direction interministérielle du numérique (DINUM) (X = Date, Y = Severity)
Direction interministérielle du numérique (DINUM) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Belastingdienst (X = Date, Y = Severity)
Belastingdienst cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Direction interministérielle du numérique (DINUM)

Belastingdienst
FAQ
Latest Global CVEs
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to exposure of session tokens in the HTML response.
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to an XML external entity (XXE) injection flaw.
IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 could allow a local attacker to obtain sensitive information due to cleartext transmission of sensitive information.
IBM Planning Analytics 2.0, and 2.1 could allow a remote authenticated attacker to execute arbitrary code due to a stack-based buffer overflow.
IBM DataStage on Cloud Pak for Data 5.4.0.0 can allow a man-in-the-middle attacker to present a forged TLS certificate, intercept the connection, and capture the IAM bearer Authorization header automatically attached by the session adapter. The captured token grants full platform-scope tenant API access, enabling the attacker to read and manipulate the victim's DataStage projects, flows, assets, and pipeline definitions. This is client-side SDK code running on the user's own machine, so exploitation requires an external network interceptor rather than a co-tenant in the shared cluster.