A Hotel Company Makes Files.com the Control Point for Data Leaving Its Multi-Brand Hotel Business

A US hotel company runs a multi-brand portfolio of more than a thousand properties. Most of those properties are franchised, with the remainder managed directly by the company.

An operation like that is a data-exchange business as much as a lodging business. Managed properties generate financial files from their Oracle systems every day. Corporate systems in Azure produce data feeds for revenue-management vendors and other partners. Dozens of outside vendors send files in and retrieve files out. Data leaves the company constantly, in many directions, and it is the information security team's job to know how and where.

Outbound Data Ran Channel by Channel, Vendor by Vendor

Outbound data at the company had no single shape. Each vendor relationship carried its own connection. Cloud systems fed data directly to the partners that consumed it. The channels worked, one at a time, and each carried its own copy of the controls. The security team wanted one place to stand: a single point where access controls, logging, and classification attach to every outbound path at once. Every new vendor relationship would land on that point instead of adding a channel of its own.

Hotel data movement converges nowhere on its own. Managed properties produce files locally, on site. Corporate data lives in Azure. Vendors both push files in and pull files out, each on its own arrangement. Securing that channel by channel would mean replicating controls across every counterparty, and then doing it again for every vendor the company added.

That point of convergence had to carry corporate Azure output, vendor exchange, and property financials alike. It had to speak the SFTP the vendors already used, keep each counterparty walled into its own directories, carry heavy machine-to-machine traffic, and open itself to the security tooling the company already ran. The company selected Files.com to be that point.

Azure Ships Data In, Vendors Take It Out Over SFTP

The company's Azure databases, blob storage, and Azure Functions now ship outbound data into Files.com, and Files.com serves it to external vendors and customers from there. The majority of movement on the platform is outbound: it is the step where data crosses from the company's environment to the outside world.

Vendors connect over SFTP with SSH key authentication. Per-user and per-folder permissions in Files.com scope each vendor to its own directories, so a counterparty sees only its own exchange and nothing else on the platform. Revenue-management platforms including IDeaS and OTA Insights reach their files the same way. Machine-to-machine traffic runs on programmatic service accounts over the Files.com REST API, tens of thousands of API transactions a day, and each vendor's account carries a named internal business owner, so every automated path out of the company has a person accountable for it.

The same platform carries the inbound spoke. Dozens of managed properties generate Oracle deposit files on local servers, scripts push those files to Files.com, and the corporate accounting team downloads them from one place. Collection from dozens of physical sites into a central finance function runs on the same governed platform that handles vendor egress.

Security Effort Now Aims at One Platform

With the hub in production, the company replaced a census of outbound channels with one platform where controls attach.

• Vendor EDI is consolidated: anyone at the company doing EDI with a vendor uses Files.com as the primary method. Onboarding the next vendor means a scoped account, an SSH key, and a named owner.
• Outbound data is observable at one point. What leaves the company passes through a platform that records it.
• Existing security tooling reached the transfer layer without adding another tool. A data-classification tool built for SharePoint and OneDrive inspects everything held on Files.com through a read-only API key, extending the company's classification coverage to the platform where data actually departs.
• Property financial collection carries the same governance as vendor exchange, because both run through the same platform.

The compounding result is that security effort no longer scales with the number of counterparties. A new vendor lands on the existing pattern, and the controls, the logging, and the classification coverage apply to it on arrival.

One Place to Stand

The company did not make its data egress governable by locking down every channel one at a time. It gave data one deliberate way out of the company, and it concentrated its security effort there. Files.com is that way out, which is why the team that guards a hotel business of more than a thousand properties calls it some of the most critical infrastructure it runs.