K
96–181 k $US par an · Brooklyn, Ohio, US
KeyBank
KeyBank's security teams operate under the threat model you'd expect from one of the nation's largest bank-based financial services companies: protecting the full stack of banking, investment, and capital markets infrastructure across a sprawling, multi-state footprint. The attack surface is wide - consumer and commercial banking portals, trading systems, financial wellness platforms, and the interconnections tying them together. Founded in 1832 and headquartered in Cleveland, Ohio, the institution carries nearly two centuries of operational history, which means legacy systems and modern fintech integrations coexist in ways that demand serious architectural discipline from any security function. Defending that estate means confronting the usual suspects - credential stuffing, business email compromise, API abuse, ransomware - plus the regulatory complexity that comes with being a systemically important financial institution. The work spans identity and access management, network segmentation, threat detection and response, vulnerability management, and secure software development across internal teams and third-party vendors. Compliance isn't optional; it's foundational, and security engineering sits at the intersection of federal banking regulation and real-time threat intelligence. The company's core values center on accountability, integrity, and teamwork - language that, in practice, translates to cross-functional security collaboration with risk, fraud, and technology teams. KeyBank's commitment to community investment and financial wellness extends into how the organization thinks about data stewardship and customer trust. For security professionals, the draw is straightforward: high-stakes infrastructure, regulated complexity, and the mandate to protect assets that matter to millions of Americans.
KeyBank's security teams operate under the threat model you'd expect from one of the nation's largest bank-based financial services companies: protecting the full stack of banking, investment, and capital markets infrastructure across a sprawling, multi-state footprint. The attack surface is wide - consumer and commercial banking portals, trading systems, financial wellness platforms, and the interconnections tying them together. Founded in 1832 and headquartered in Cleveland, Ohio, the institution carries nearly two centuries of operational history, which means legacy systems and modern fintech integrations coexist in ways that demand serious architectural discipline from any security function.
Defending that estate means confronting the usual suspects - credential stuffing, business email compromise, API abuse, ransomware - plus the regulatory complexity that comes with being a systemically important financial institution. The work spans identity and access management, network segmentation, threat detection and response, vulnerability management, and secure software development across internal teams and third-party vendors. Compliance isn't optional; it's foundational, and security engineering sits at the intersection of federal banking regulation and real-time threat intelligence.
The company's core values center on accountability, integrity, and teamwork - language that, in practice, translates to cross-functional security collaboration with risk, fraud, and technology teams. KeyBank's commitment to community investment and financial wellness extends into how the organization thinks about data stewardship and customer trust. For security professionals, the draw is straightforward: high-stakes infrastructure, regulated complexity, and the mandate to protect assets that matter to millions of Americans.