Metabase CVE-2026-72898: how to organise your response
A critical flaw in the Metabase password reset endpoint, CVE-2026-72898, is listed by CISA as exploited. This article explains who is affected and how to organise the response.
PiLabs
PiLabs follows the CISA catalogue and the NVD and publishes summaries.
Latest vulnerabilitiesNews
A firewall that is too small slows the branch down, and one that is too large wastes budget. This guide explains what to measure and what to ask before you choose.
This article was written automatically on 18 November 2026 from the information on this site and checked by automated rules; it was not reviewed by a person. Tell us if something is wrong
A branch office is small, but it still needs a firewall that fits. If the device is too small, pages load slowly, video calls break up and staff look for ways around it. If it is far too large, you pay for capacity and licences you never use. This guide shows how to find the right size with a few simple measurements.
Size follows use, not the number of desks. Before you look at any product sheet, write down the following:
If you have a firewall today, its reports are the best starting point. Look at the busiest hours of a normal week, not the average of the whole month. That is when the device has to cope.
Every firewall datasheet lists a top speed. Read it with care. That figure is usually measured with the simplest traffic and with most security features switched off. Once you turn on the features you actually need, the speed that remains is lower.
Ask the supplier for the speed with the features you plan to use. These often include:
Also check the number of simultaneous connections and the number of new connections per second. A branch with many small devices or busy web applications can reach these limits before it reaches the speed limit.
A firewall is usually kept for several years, so do not size it only for today. Think about how the branch may change over that time: more staff, a faster internet line, more cloud applications, more video. A sensible margin is better than a device that is already full on the first day. Your own plan matters more than a general rule, so ask the branch manager what is expected.
Then think about failure. If the branch cannot work without the internet, consider these options:
Not every branch needs all of these. Decide how long the branch can be offline, and choose from there.
The price of the box is only part of the cost. Many firewall features work only with a paid subscription, and those subscriptions are often renewed every year or every few years. Ask what is included in the first licence, what must be bought separately, and what happens to protection when a subscription ends.
Think about management as well. A branch rarely has its own network engineer. Check whether the device can be managed from a central place, whether changes can be made remotely, and who is responsible for updates. A firewall that is never updated or reviewed protects less each year, however large it is.
Write the answers down and compare them across suppliers in the same way. A clear, honest answer to these questions is a better sign than the lowest price.
Pinet supplies Palo Alto Networks firewalls and subscriptions sized for your traffic and growth, and also handles deployment, policy design and support. You can read more on the Palo Alto Networks page. To discuss your branch, use the Pinet contact page.
More
A critical flaw in the Metabase password reset endpoint, CVE-2026-72898, is listed by CISA as exploited. This article explains who is affected and how to organise the response.
A critical flaw in Kestra OSS lets an unauthenticated attacker run code, and CISA lists it as exploited. This article explains who is affected and how to organise the response.
A penetration test answers one narrow question well. This article explains what it covers, what it leaves out and what to agree in writing before the work starts.
Write to us. A consultant will answer.