Old National Bank has been in the financial services game since 1834 - that's 190 years of accumulating attack surface across deposit accounts, mortgage origination, commercial lending, credit card processing, and wealth management platforms. With $73 billion in total assets and a top-25 U.S. bank ranking, the institution operates across seven Midwest states (Illinois, Indiana, Kentucky, Michigan, Minnesota, North Dakota, Wisconsin) with 2,769 team members. The threat model is straightforward: a regional bank of this scale handles high-volume personally identifiable information, transaction data, and financial account credentials across both digital and traditional banking channels - online and mobile banking platforms, home equity and mortgage pipelines, and commercial banking operations all present distinct risk domains.
The security challenge at a bank like this isn't abstract. It's protecting customer financial data across checking, savings, mortgage, and credit card product lines while maintaining uptime on digital banking platforms that serve consumers and businesses simultaneously. The Midwest footprint means regulatory compliance obligations spanning multiple state jurisdictions alongside federal banking regulations. The institution describes itself as maintaining the culture of a smaller community bank despite its scale - a tension that often surfaces in security orgs balancing legacy infrastructure with modernization demands.
Founded in Evansville, Indiana, Old National has been recognized through The Civic 50 as one of the most community-minded companies in the U.S. The bank's seven-state presence and broad product portfolio - from personal deposit accounts to wealth management services - means the security team operates across a wide surface area with real financial and reputational stakes. For cybersecurity professionals, the draw is scale without the bureaucratic bloat of a megabank, with enough complexity across banking verticals to keep the work technically demanding.
