A Test Equipment Manufacturer Gives Defense Firewall Teams a Files.com Domain and Fixed IPs They Can Allowlist

A display test equipment manufacturer builds the equipment that tests displays and the video components that drive them. It supplies display test-and-measurement systems to display makers and integrators worldwide, including avionics companies that rely on those systems for verification and acceptance testing.

The hardware is built to last. Many of its products stay in service for 15 to 20 years, and over that life the firmware, installers, configuration files, and manuals that keep them running have to keep reaching them, wherever they sit. Increasingly, they sit inside some of the most locked-down networks in industry: military programs, defense contractors, and now medical device makers.

A Portal Address Blocked as a Category

The manufacturer's payloads are exactly the kind of files security tooling exists to stop: .msi installers, executables, zipped applications. At defense sites, shared file-sharing domains are blocked as a category, and the generic address of the manufacturer's own hosted portal sat inside that category. Customers behind those firewalls could not reach the portal at all.

The manufacturer wanted one sanctioned path for every firmware release, configuration file, and application update, reachable from inside a locked-down customer's network. Across a customer base of hundreds of companies with hardware in service for decades, that path had to work again and again.

A Blocked Category, Not a Blocked Vendor

The problem could not be fixed from the manufacturer's side, because the blocking lives in its customers' security policies. A shared file-sharing URL, where thousands of unrelated organizations serve files from one domain, is precisely what a defense contractor's firewall team blocks. And the condition was spreading: access restrictions were tightening month over month and reaching beyond military contractors into the medical field, so the population of customers the manufacturer could not reach was growing, not shrinking.

What the fix had to do was clear. It had to give customer IT departments something they could specifically approve: an endpoint carrying the manufacturer's own name, resolving to fixed IP addresses a firewall team can allowlist. It had to leave the existing portal and its accounts untouched. And it had to be something the company's site administrator, who runs the website and the file server alongside the engineering work, could stand up without a web operations team.

The Portal Moved to the Manufacturer's Own Domain

The manufacturer already ran its product-support portal on Files.com, distributing firmware, configuration files, manuals, and applications through customer accounts with company-level permissions.

To reach the customers who were blocked, the manufacturer put that portal behind its own branded domain using the Files.com custom domain and dedicated IP features. The cutover was completed in one working session with Files.com support alongside the company's site administrator, with Files.com provisioning and managing the SSL certificate. Not one user account changed. Customers were simply issued the new address.

A Front Door a Defense Firewall Team Can Approve

With the branded domain live, the manufacturer gave the customers whose networks block shared domains an endpoint their security teams can sanction.

• Defense customers whose IT blocks shared file-sharing domains now log in and download directly, from a domain that carries the manufacturer's name and resolves to fixed IP addresses their firewall teams can allowlist.
• Every firmware release, configuration file, and application update for those customers now travels the same sanctioned path, from the manufacturer's portal to the engineer's desk.
• Nothing else moved. The same portal, the same accounts, the same group permissions; customers were simply issued the new address.
• The posture stands up to scrutiny: the branded domain rates A+ on SSL Labs, an answer the manufacturer can hand to any customer's security review.

The compounding result is the larger one. As the same restrictions spread into the medical field, onboarding the next locked-down customer is an allowlist request to that customer's IT department, not a new delivery method.

Distribution That Fits Inside the Customers' Security

The manufacturer did not ask any customer to loosen anything. The policies that block shared file-sharing domains all still stand. Files.com gave the manufacturer an endpoint that fits inside them. Today an engineer at a defense contractor gets a firmware update by logging in from their own desk, on a domain their own firewall team approved.