Comparison Overview
Procter & Gamble India
Procter & Gamble India
Procter & Gamble Plaza, Mumbai, 400099, IN
Last Update: 01/04/2026
P&G was founded over 180 years ago as a soap and candle company. In India, P&G’s history started in 1985 with the acquisition of Richardson Hindustan Limited (RHL). Today we touch the lives of hundreds of millions of consumers in India with our portfolio of 13 leading a...
Vedanta Group
Vedanta Resources, London, GB
Last Update: 08/09/2026
We operate on the belief that our people are our core assets and we consistently endeavour towards developing their potential to be our future leaders and key employees. We currently operate in India, South Africa, Liberia and Namibia, through our various subsidiaries. ...
Compliance Ranges Comparison
Procter & Gamble India
Vedanta Group
Benchmark & Cyber Underwriting Signals
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Procter & Gamble India in 2026.
Incidents vs Manufacturing Industry Avg (This Year)
Vedanta Group has 0.99% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Procter & Gamble India (X = Date, Y = Severity)
Procter & Gamble India cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Vedanta Group (X = Date, Y = Severity)
Vedanta Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Procter & Gamble India
Vedanta Group
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.