Comparison Overview
Tangem
Tangem
Baarerstrasse 10, Zug, 6300, CH
Last Update: 12/03/2026
Tap into crypto freedom. Security. Utility. Mobility. 6M+ wallets and counting. Posts are not directed towards UK users.
Globant
875 Howard St, San Francisco, 94103, US
Last Update: 02/04/2026
At Globant, we create the digitally-native products that people love. We bridge the gap between businesses and consumers through technology and creativity, leveraging our experience as an AI powerhouse. We dare to digitally transform organizations and strive to delight ...
Compliance Ranges Comparison
Tangem
Globant
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
Tangem has 34.21% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Globant in 2026.
Incident History - Tangem (X = Date, Y = Severity)
Tangem cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Globant (X = Date, Y = Severity)
Globant cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Tangem
Globant
FAQ
Latest Global CVEs
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an inadequate encryption strength vulnerability which could allow an attacker to steal admin credentials via weak hash or a pass-the-hash attack.
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an exposure of sensitive system information to an unauthorized control sphere vulnerability which could allow for asset discovery by unauthenticated users.
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an unintended proxy or intermediary vulnerability which could allow an attacker to use an active proxy, which would bypass OT segmentation.
Pronetiqs IntraVUE Versions 3.2.1a14 and prior have a plaintext storage of a password vulnerability that could expose cleartext credentials through the API.
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an exposure of sensitive system information to an unauthorized control sphere vulnerability which could expose the underlying host/share filesystem.