Skip to main content
  1. Blog
  2. Article

Sarah Dickinson
on 20 November 2017


When building or deploying any IoT device either in remote locations or consumer’s homes, it is now essential for manufacturers to consider and review how their devices can be future-proofed once it leaves their warehouses – such as update mechanisms and deploying security patches quickly. This is particularly so in the consumer market where devices can be low cost with an emphasis on profitability and little consideration to how a device will fare once out in the wild.

Last week we covered the launch of the new Fingbox network security device which delivers new and innovative IoT security features to homes. Fing, the company behind Fingbox, have built a device that recognises the need for future proofing and have catered for an IoT device being sat in consumer’s homes for years to come. These considerations extend beyond providing security over the long run, but also how new functionality could enhance the product further down the line without requiring their customer base to buy new hardware.

To achieve this Fing has adopted Canonical’s brand store offering. The brand store essentially provides Fing with their own repository where they can manage the updates that they push to their customers. One example of this may be to push security patches if vulnerabilities become known.  Taking into account Ubuntu Core’s automatic update feature as well it creates a seamless experience for the customer. This is particularly important for such a device as recent Canonical research found that 69% of consumers do not update their connected devices.

The brand store option offers Fing the control required to select only the desired software they want to push to devices and equally ensures only authenticated devices access the store. Historically, software publishers have found it difficult to both target specific devices and also have control over what software is presented to a device. Adopting a brand store provides solutions to these issues without the need for timely and expensive custom-builds.

By adopting a brand store, Fing has also given themselves the opportunity to continually enhance the Fingbox and feature set that they offer their customers. This might only be their first hardware launch, but the team behind the Fingbox have shown a maturity and level of planning few companies have. Fing’s software choices from the outset mean they can evolve the functionality offered when needed and deploy to their customer base via a snap. This could be incremental updates to existing features or whole new feature sets. From Fing’s point of view, it opens the door to create new revenue streams beyond their initial hardware sales. For any manufacturer, building a business beyond hardware needs to become an increasing priority. When asking IoT professionals, Canonical found that 78% believed future monetisation of IoT devices would come via added services delivered as software.

When it comes to future-proofing, Fingbox have got their customers and themselves covered.   

Related posts


Miha Purg
15 May 2026

Finding the blind spot: How Canonical hunts logic flaws with AI

AI Article

AI is accelerating and improving how security engineers find and fix vulnerabilities. A new tool developed and used at Canonical, called Redhound, has already uncovered three critical logic vunerabilites, paving the way for a more secure software landscape. ...


Luci Stanescu
14 May 2026

Fragnesia Linux kernel local privilege escalation vulnerability mitigations

Ubuntu Article

A local privilege escalation (LPE) vulnerability affecting the Linux kernel has been publicly disclosed on May 13, 2026. The vulnerability does not have a CVE ID published, but is referred to as “Fragnesia.”  The vulnerability affects multiple Linux distributions, including all Ubuntu releases. The affected components are the Linux kernel ...


Luci Stanescu
8 May 2026

Dirty Frag Linux kernel local privilege escalation vulnerability mitigations

Ubuntu Article

Two local privilege escalation (LPE) vulnerabilities affecting the Linux kernel have been publicly disclosed on May 7, 2026. The vulnerabilities have been assigned the IDs CVE-2026-43284 and CVE-2026-43500 and are referred to as “Dirty Frag.” The affected components are Linux kernel modules. The first vulnerability impacts the modules tha ...