Financial institutions are a storehouse of attractive data for attackers. Although most attacks against financial organizations don’t necessarily succeed in emptying coffers outright, other information—such as PII (Personally identifiable information) related to customers and employees—is just as valuable. In addition, attackers have stolen money directly from banks in the past (see the 2016 SWIFT attacks), so this isn’t a threat that banks can discount.
Attacks against banks have dramatically increased in scale and multiplied in complexity. In 2020, attacks against banks rose 238% in an increase tied to the COVID-19 pandemic, but even a decrease in 2021 would still leave threat levels well above normal. Attackers aren’t just trying to steal information—data breaches now include:
Lastly, even if an attacker can’t steal information directly from a bank or paralyze it with ransomware, they can still disrupt its operations with nuisances such as DDoS attacks. Imperva recorded a 30% increase in DDoS attacks versus banks in 2020, with many attacks including a ransom component—e.g., “we’ll stop disrupting your network if you pay us in Bitcoin.” DDoS attacks often prevent customers from making deposits or withdrawals online, causing severe reputational damage in just a short time. The temptation to pay the ransom is strong.
No matter whether you pay a ransom or not, your bank will pay a high price in the event of a successful cyberattack. The IBM 2020 Cost of a Data Breach Report suggests that banks will incur a total cost of $5.85 million in the event of a data breach. This includes the cost of stolen data, downtime, fines, reputational damage, and more. What defenses should you invest in to defray this ongoing risk?
Let’s assume that you’re already doing the commonsense things designed to protect your company.
Despite all this, attackers still have a decent chance of getting through your defenses—so what extra steps should you be taking?
One vulnerability to consider is that many (perhaps most) banking employees are still working from home—even vaccinated workers still enjoy remote work. This widens your attack surface and keeps the IT department working overtime. As you struggle to keep the WAN and VPN free of performance issues, hackers can take advantage of your blind spots.
What’s more, other system pressures are making you more vulnerable. The drive towards open banking—in which banks make their data available using APIs—is great for functionality, agility, and mobility, but it can also make banks more exposed to supply chain attacks. Mobile banking, cloud adoption, microservices architecture, and other advancements all represent security tradeoffs.
In response, banks need to adopt modernized network monitoring and security solutions, as traditional monitoring and security solutions typically inspect traffic that goes across the network—what we’ll call north-south traffic. With the movement towards cloud implementations and SaaS applications—only 17% of organizations are reporting visibility into this east-west traffic, according to the 2020 SANS Network Visibility and Threat Detection report.
The same SANS report indicates a large gap in visibility across all industries. Less than 40% of respondents were able to report confidence in their ability to discover every endpoint connected to their network. Meanwhile, almost 60% of respondents reported feeling a high or very high level of risk related to their lack of visibility.
The truth is that traditional monitoring tools and architectures don’t do a great job of securing the enterprise. The perimeter is in tatters. The best way to monitor traffic is instead to capture the data flows between applications and clients. Companies can augment this understanding by using corporate interception proxies to decrypt traffic that might be disguising malicious communications, and by sharing network flow data with security teams to identify large traffic sources.
Right now, finance, banking, and insurance companies are vulnerable to more aggressive cyberattacks because their traditional security tools don’t protect against attackers that move laterally and attack the supply chain. In addition, they can be hobbled or taken offline by DDoS attacks, which hurt their customers and cause reputational damage.
For the first problem, Garland provides packet visibility through network TAPs and packet brokers. These allow network architects to capture more information in more places, which in turn lets them direct previously unmonitored east-west traffic to their security solutions. By detecting threats that move within the network rather than through it, administrators can mitigate intrusions that might otherwise have been invisible.
Addressing the issue of network downtime, Garland also provides inline bypass TAPs to provide added resiliency and redundancy to inline security tools to ensure network uptime. This means that when attackers try to bring your network down, your active cybersecurity tools are always protecting, and you’ll be able to ensure the continuity of your 24/7 services and continue serving your customers.
Some of the biggest financial institutions in the world trust Garland to provide enhanced network security and monitoring tools.
Looking to add an Inline Bypass or TAP Visibility to your security deployment, but not sure where to start? Join us for a brief network Design-IT consultation or demo. No obligation - it’s what we love to do.
If the inline security tool goes off-line, the TAP will bypass the tool and automatically keep the link flowing. The Bypass TAP does this by sending heartbeat packets to the inline security tool. As long as the inline security tool is on-line, the heartbeat packets will be returned to the TAP, and the link traffic will continue to flow through the inline security tool.
If the heartbeat packets are not returned to the TAP (indicating that the inline security tool has gone off-line), the TAP will automatically 'bypass' the inline security tool and keep the link traffic flowing. The TAP also removes the heartbeat packets before sending the network traffic back onto the critical link.
While the TAP is in bypass mode, it continues to send heartbeat packets out to the inline security tool so that once the tool is back on-line, it will begin returning the heartbeat packets back to the TAP indicating that the tool is ready to go back to work. The TAP will then direct the network traffic back through the inline security tool along with the heartbeat packets placing the tool back inline.
Some of you may have noticed a flaw in the logic behind this solution! You say, “What if the TAP should fail because it is also in-line? Then the link will also fail!” The TAP would now be considered a point of failure. That is a good catch – but in our blog on Bypass vs. Failsafe, I explained that if a TAP were to fail or lose power, it must provide failsafe protection to the link it is attached to. So our network TAP will go into Failsafe mode keeping the link flowing.
Single point of failure: a risk to an IT network if one part of the system brings down a larger part of the entire system.
Heartbeat packet: a soft detection technology that monitors the health of inline appliances. Read the heartbeat packet blog here.
Critical link: the connection between two or more network devices or appliances that if the connection fails then the network is disrupted.