Comparison Overview
NAME IT

NAME IT
Fredskovvej 1, Brande, Central Denmark Region 7330, DK
Last Update: 17/05/2026
NAME IT is a part of BESTSELLER and started out as EXIT in 1986. In 1996 NAME IT was introduced as a sub brand and in 2008 EXIT was rebranded as NAME IT. Today NAME IT is represented in more than 20 markets across Europe, Asia, North America, South America and Austr...

Levi Strauss & Co.
1155 Battery St, San Francisco, US
Last Update: 05/09/2026
You’re an original. So are we. We’re a company of people who like to forge our own path. We invented the blue jean in 1873, and we reinvented khaki pants in 1986. We pioneered labor and environmental guidelines in manufacturing. And we work to build sustainability int...
Compliance Ranges Comparison

NAME IT







Levi Strauss & Co.






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Apparel and Fashion Industry Avg (This Year)
No incidents recorded for NAME IT in 2026.
Incidents vs Retail Apparel and Fashion Industry Avg (This Year)
Levi Strauss & Co. has 0.99% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - NAME IT (X = Date, Y = Severity)
NAME IT cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Levi Strauss & Co. (X = Date, Y = Severity)
Levi Strauss & Co. cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

NAME IT

Levi Strauss & Co.
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.