Comparison Overview
FuturePlan by Ascensus

FuturePlan by Ascensus
undefined, Dresher, Pennsylvania, 19025, US
Last Update: 19/12/2025
We stand as a Category of One partner in the TPA space. As a leading third party administrator for America’s leading recordkeepers and advisors, we are the only TPA offering a full spectrum of creative plan design, strategic consulting, IRS and DOL regulatory compliance...

Ally
500 Woodward Ave, Detroit, 48226, US
Last Update: 13/09/2026
Ally Financial Inc. (NYSE: ALLY) is a leading digital financial services company and a top 25 U.S. financial holding company offering financial products for consumers, businesses, automotive dealers and corporate clients. NMLS #3015 | #181005 | https://www.nmlsconsume...
Compliance Ranges Comparison

FuturePlan by Ascensus







Ally






Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for FuturePlan by Ascensus in 2026.
Incidents vs Financial Services Industry Avg (This Year)
Ally has 0.99% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - FuturePlan by Ascensus (X = Date, Y = Severity)
FuturePlan by Ascensus cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Ally (X = Date, Y = Severity)
Ally cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

FuturePlan by Ascensus

Ally
FAQ
Latest Global CVEs
HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server.
Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory amplification vector as a result.
A trusted template author may have previously written a valid template wherein the use of the 'yield' keyword would not be correctly escaped. We now ensure that valid keyword uses are escaped and non-keyword uses are not escaped.
Improper certificate validation in Microsoft Partner Center allows an unauthorized attacker to elevate privileges over a network.
Authorization bypass through user-controlled key in Microsoft Bookings allows an unauthorized attacker to elevate privileges over a network.