Comparison Overview
Allianz Asset Management
Allianz Asset Management
Seidlstr. 24-24a, None, München, None, DE, 80335
Last Update: 26/03/2026
Allianz Asset Management (AllianzAM) is the financial and governance holding company for the asset management business of Allianz SE, with approx. EUR 2,000 bn of assets under management and approx. 5,000 employees worldwide. AllianzAM is comprised of two separate inv...
Standard Bank Group
30 Baker St, Rosebank,, Johannesburg , Gauteng, ZA, 2196
Last Update: 02/04/2026
As a brand with a legacy of over 160 years in Africa, we have a deep understanding and belief in the boundless opportunities that this continent presents. Our vision extends beyond mere geography; it encompasses a profound recognition of the potential for growth that re...
Compliance Ranges Comparison
Allianz Asset Management
Standard Bank Group
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Allianz Asset Management in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Standard Bank Group in 2026.
Incident History - Allianz Asset Management (X = Date, Y = Severity)
Allianz Asset Management cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Standard Bank Group (X = Date, Y = Severity)
Standard Bank Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Allianz Asset Management
Standard Bank Group
FAQ
Latest Global CVEs
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead to denial of service via Excessive Allocation (CAPEC-130). A low-privileged authenticated user can send a specially crafted request to a Kibana machine learning feature, causing the server to exhaust available memory and become unavailable to all users.
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead to denial of service via Excessive Allocation (CAPEC-130). An authenticated attacker with low-privilege access can trigger a denial of service condition in Kibana by sending a specially crafted, oversized request payload. Processing this user-supplied input requires resource-intensive memory allocation that can exhaust the available heap memory in the Kibana process, causing it to crash and become unavailable to all users.
Authorization Bypass Through User-Controlled Key (CWE-639) in Kibana can lead to information disclosure via user-supplied identifiers that reference scheduled query result data from Kibana Spaces the requester is not authorized to access.
Incorrect Authorization (CWE-863) in Kibana can lead to integrity compromise of Machine Learning audit and notification records via Accessing Functionality Not Properly Constrained by ACLs (CAPEC-1). A vulnerability exists in Kibana's Machine Learning functionality where a Machine Learning management endpoint performs an insufficient authorization check. The endpoint validates only a coarse privilege level but does not verify that the requesting user has access to the specific Machine Learning job or notification resources provided in the request. As a result, a low-privileged user with Machine Learning access in any Kibana space can manipulate Machine Learning audit and notification records for arbitrary jobs—including jobs in other spaces or belonging to other users—by leveraging Kibana's internally elevated credentials to write to restricted Machine Learning system indices that the user cannot access directly.
Uncontrolled Recursion (CWE-674) in Elasticsearch can lead to denial of service via a specially crafted search request submitted by a low-privileged authenticated user. A user with read-level index access can submit a request that triggers unbounded recursive processing within the Elasticsearch query evaluation component, causing a fatal error that terminates the affected node. In single-node deployments, this results in complete service outage; in multi-node clusters, it causes repeated node restarts and sustained availability degradation.