Back to Feed
ComplianceJun 3, 2026

What 345 Days of Untested Exposure Looks Like at a Bank

Annual penetration tests leave 345 days of banking exposure unvalidated amid constant infrastructure changes.

A two-week annual penetration test leaves roughly 345 days of real-world exposure unvalidated, creating significant risk in modern banking environments where infrastructure changes continuously. Regulators (PCI DSS, FFIEC, NYDFS) already expect testing to occur in response to changes—cloud migrations, fintech integrations, M&A work—not just annual assessments. A recent engagement at a regional bank uncovered an unauthenticated API endpoint on a third-party mortgage platform that exposed staff records and internal codes for every financial institution using the shared infrastructure.

AI summary of the linked source. Not reviewed by an editor. How this works

Vendor Watch

Run CrowdStrike?

Get an email when a new story names CrowdStrike, usually within the hour.

Free. Your list stays private and never appears in a subject line. One click stops it. How Vendor Watch worksPrivacy

The lesson from this incident

Full lesson

A regional bank's reliance on annual penetration testing left 345 days of exposure unvalidated, during which an unauthenticated API endpoint on a third-party mortgage platform exposed sensitive staff records. Modern banking environments change continuously through cloud migrations, fintech integrations, and M&A activities, making annual security assessments insufficient. Regulators like PCI DSS, FFIEC, and NYDFS already require testing in response to infrastructure changes, not just scheduled annual reviews. This incident demonstrates how shared third-party platforms can amplify security vulnerabilities across multiple financial institutions simultaneously.

What helps against this

How we list vendors

Entities

Marquis Software (vendor)Sprocket Security (vendor)CrowdStrike (vendor)Mandiant (vendor)