Comparison Overview
BeFrank

BeFrank
Spaklerweg 4, Amsterdam, Noord-Holland, 1096 BA, NL
Last Update: 01/04/2026
Het gemak van een modern pensioen Kiezen voor een pensioen en pensioenuitvoerder is al lastig genoeg. Processen hoeven dat gelukkig niet te zijn. Daarom maken we bij BeFrank praktische zaken zo eenvoudig mogelijk. BeFrank is een moderne online pensioenuitvoerder, ...

New York Life Insurance Company
51 Madison Avenue, New York, 10010, US
Last Update: 05/09/2026
For over 180 years, we’ve helped turn your biggest dreams into milestones that last a lifetime. As a mutual company we hold ourselves to the highest standards of transparency, objectivity, and integrity. We’re committed to improving local communities through a culture o...
Compliance Ranges Comparison

BeFrank







New York Life Insurance Company






Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for BeFrank in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for New York Life Insurance Company in 2026.
Incident History - BeFrank (X = Date, Y = Severity)
BeFrank cyber incidents detection timeline including parent company and subsidiaries.
Incident History - New York Life Insurance Company (X = Date, Y = Severity)
New York Life Insurance Company cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

BeFrank

New York Life Insurance Company
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)