Comparison Overview
Ferrara
Ferrara
404 W Harrison St, Suite 650, Chicago, Illinois, US, 60607
Last Update: 04/04/2026
We are Ferrara, an undisputed leader in sugar confections. Ferrara is #1 in the category in the US with ambitions of being the global leader by leveraging our focus, capabilities, and brand portfolio to drive category development for our community, customer, and consume...
JSW
Bandra Kurla Complex, Mumbai, 400051, IN
Last Update: 20/09/2026
At JSW, we believe innovation has the power to make the world #BetterEveryday. As a US$ 23 billion group, ranked among India’s leading business houses, we drive economic growth across sectors like Steel, Energy, Infrastructure, Cement, Paints, Green Mobility, Defence, S...
Compliance Ranges Comparison
Ferrara
JSW
Benchmark & Cyber Underwriting Signals
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Ferrara in 2026.
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for JSW in 2026.
Incident History - Ferrara (X = Date, Y = Severity)
Ferrara cyber incidents detection timeline including parent company and subsidiaries.
Incident History - JSW (X = Date, Y = Severity)
JSW cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Ferrara
JSW
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.