• Home
  • Education
  • News and Resources
  • Advocacy
  • Associate Members
  • Contact
  • My Profile
  • Click to open the search input field Click to open the search input field Search
  • Menu Menu
News
Resources

When the Bank Grows, the Network Gets Harder to Manage

By Anne Tarantino, account executive, Locknet Managed IT.

Anne Tarantino

Growth plans for community banks usually focus on markets, deposits, and lending. The network tends to come up later, often after something breaks.

That’s understandable. But every new branch, acquisition, and vendor connection adds work for an IT team that is usually small to begin with, and that work compounds faster than headcount does.

Here are seven places where growth tends to strain a bank’s network, with one practical step for each.

1. Branches drift apart

A new branch is one line in a growth plan. On the network, it’s a circuit, a firewall, switches, wireless, ATMs or ITMs, cameras, and a connection back to the core. Each piece has to be configured, patched, and monitored to the same standard as every other location.

Over time, small exceptions add up like a firewall rule added for a vendor and never removed, a switch left on older firmware, or a backup circuit that was never tested. These rarely show up until an exam or an incident.

Practical step: Write down a standard branch configuration and check every location against it at least once a year, including branches that came through an acquisition.

2. Acquisitions arrive with someone else’s decisions

An acquired institution brings its own IP addressing, security tools, carrier contracts, and years of choices nobody wrote down. Integration means deciding what to keep and what to replace, then timing that work around a core conversion, so customers don’t feel it.

That is a project on top of daily operations, and it usually lands on the same people running them.

Practical step: Add a network review to due diligence, before the deal is approved. Ask for current diagrams, firewall rules, and carrier and vendor contracts, and note what’s missing.

3. Every new partner is another way in

Digital banking platforms, card processors, fintech integrations, cloud applications, and vendor remote access each open a path into the network. Each one needs to be segmented, monitored, and reviewed.

As partners are added, a basic question gets harder to answer with confidence: who can reach what, and why?

Practical step: Keep one list of every third-party connection, what it can access, and who approved it. Review it as part of your vendor management program and remove access that’s no longer needed.

4. Documentation falls behind the network

Examiners and auditors expect current network diagrams, data flow documentation, evidence of segmentation, and a record of how changes are approved. Across three locations, that’s manageable. Across ten, with an acquisition underway, it becomes ongoing work.

When documentation lags the actual network, exam prep turns into a scramble.

Practical step: Update diagrams and change records as part of each change, not the week before an exam. If a change isn’t documented, treat it as unfinished.

5. Alerts outgrow the hours to review them

More users, locations, and connections produce more traffic, logs, and alerts. A small IT team may not have the hours to review them all, and outages and threats don’t keep business hours.

The time between when something goes wrong and when someone notices can widen quietly as the bank grows.

Practical step: Decide who reviews alerts on nights and weekends, and how quickly. If the honest answer is “no one until Monday,” raise that gap with leadership now rather than after an incident.

6. Too much knowledge sits with too few people

In many banks, one or two people know how the network really works: which firewall rules matter, which circuit is on which contract, why one branch is set up differently.

That knowledge is valuable, and it’s also a risk. When those people are pulled into a conversion, take vacation, or leave, the bank loses the context it needs to troubleshoot and make changes safely.

Practical step: Have them walk a colleague through the network and write down what they cover. Start with whatever would be hardest to figure out in the middle of an outage.

A quick self-check for your bank

If your team can answer yes to each of these, your network is likely keeping pace with your growth. Any “no” or “not sure” is a good place to start.

  1. Does every branch, including acquired ones, match a written standard configuration?
  2. Was IT part of our last acquisition or expansion before it was approved?
  3. Do we have a current list of every third-party connection and what it can reach?
  4. Could we hand an examiner an accurate network diagram today?
  5. Is someone reviewing alerts on nights and weekends?
  6. If our network lead were out for two weeks, could someone else handle an outage?

Bringing the network into the growth conversation

None of this requires the largest IT team or the newest tools. It requires knowing where the network stands today and bringing it into the conversation earlier, while growth decisions are being made rather than after.

Banks that do this tend to absorb new branches and acquisitions with fewer surprises, at exam time and everywhere else.

Print 🖨
November 18, 2026/by Jaclyn Lindquist
Tags: IT
Share this entry
  • Share on Facebook
  • Share on X
  • Share on WhatsApp
  • Share on Pinterest
  • Share on LinkedIn
  • Share on Tumblr
  • Share on Vk
  • Share on Reddit
  • Share by Mail
https://www.wisbank.com/wp-content/uploads/2021/09/Untitled-3_Yellow.jpg 972 1920 Jaclyn Lindquist https://www.wisbank.com/wp-content/uploads/2021/09/Wisconsin-Bankers-Association-logo.svg Jaclyn Lindquist2026-11-18 13:54:452026-11-18 13:54:45When the Bank Grows, the Network Gets Harder to Manage
You might also like
Illuminating the Invisible: Why Dark Data Matters for Community Banks
The Tabletop Exercise Your Bank Keeps Meaning to Schedule
Search Search

Categories

  • Advocacy
  • Community
  • Compliance
  • Credit Unions
  • Education
  • Member News
  • News
  • Products
  • Resources
  • Uncategorized

Recent Posts

  • Executive Letter: Registration Now Open for 2027 WBA Bank Executives Conference
  • Horicon Bank Promotes John Shabaz to Branch Manager in Neosho
  • Prevail Bank Supports Beyond Blessed Pantry with a $5,000 Donation
  • Bay Bank Hosting Food & Toy Drive to Support Families in Need
  • When the Bank Grows, the Network Gets Harder to Manage

Archives

  • November 2026
  • October 2026
  • September 2026
  • August 2026
  • July 2026
  • June 2026
  • May 2026
  • April 2026
  • March 2026
  • February 2026
  • January 2026
  • December 2025
  • November 2025
  • October 2025
  • September 2025
  • August 2025
  • July 2025
  • June 2025
  • May 2025
  • April 2025
  • March 2025
  • February 2025
  • January 2025
  • December 2024
  • November 2024
  • October 2024
  • September 2024
  • August 2024
  • July 2024
  • June 2024
  • May 2024
  • April 2024
  • March 2024
  • February 2024
  • January 2024
  • December 2023
  • November 2023
  • October 2023
  • September 2023
  • August 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2016
Wisconsin Bankers Association logo
  • About
  • Community
  • Subsidiaries
  • Staff

questions@wisbank.com

608-441-1200

4721 S Biltmore Ln.
Madison, WI 53718

Get our Newsletter!
Subscribe

© 2025 Wisconsin Bankers Association. All rights reserved. | Website Design by Bizzy Bizzy
Link to: North Shore Bank Opens New Green Bay West Branch Link to: North Shore Bank Opens New Green Bay West Branch North Shore Bank Opens New Green Bay West Branch Link to: Bay Bank Hosting Food & Toy Drive to Support Families in Need Link to: Bay Bank Hosting Food & Toy Drive to Support Families in Need Bay Bank Hosting Food & Toy Drive to Support Families in Need
Scroll to top Scroll to top Scroll to top

This site uses cookies. By continuing to browse the site, you are agreeing to our use of cookies.

OKLearn more×

Cookie and Privacy Settings



How we use cookies

We may request cookies to be set on your device. We use cookies to let us know when you visit our websites, how you interact with us, to enrich your user experience, and to customize your relationship with our website.

Click on the different category headings to find out more. You can also change some of your preferences. Note that blocking some types of cookies may impact your experience on our websites and the services we are able to offer.

Essential Website Cookies

These cookies are strictly necessary to provide you with services available through our website and to use some of its features.

Because these cookies are strictly necessary to deliver the website, refusing them will have impact how our site functions. You always can block or delete cookies by changing your browser settings and force blocking all cookies on this website. But this will always prompt you to accept/refuse cookies when revisiting our site.

We fully respect if you want to refuse cookies but to avoid asking you again and again kindly allow us to store a cookie for that. You are free to opt out any time or opt in for other cookies to get a better experience. If you refuse cookies we will remove all set cookies in our domain.

We provide you with a list of stored cookies on your computer in our domain so you can check what we stored. Due to security reasons we are not able to show or modify cookies from other domains. You can check these in your browser security settings.

Other external services

We also use different external services like Google Webfonts, Google Maps, and external Video providers. Since these providers may collect personal data like your IP address we allow you to block them here. Please be aware that this might heavily reduce the functionality and appearance of our site. Changes will take effect once you reload the page.

Google Webfont Settings:

Google Map Settings:

Google reCaptcha Settings:

Vimeo and Youtube video embeds:

Privacy Policy

You can read about our cookies and privacy settings in detail on our Privacy Policy Page.

Terms of Use
Accept settingsHide notification only

Subscribe

* indicates required








Membership