Geospace Technologies Shut Down Its DMZ by Moving Seismic Data Exchange to Files.com

Geospace Technologies is a Houston-based, Nasdaq-listed manufacturer of seismic instrumentation and ruggedized sensing equipment. Its products serve energy exploration companies, water utilities, and U.S. government agencies worldwide, and the engineering behind them is genuinely hard: the company's OBX ocean-bottom nodes are autonomous recorders that sit on the seabed at depths beyond 3,400 meters, capturing seismic data continuously for up to 100 days.

Instruments like that exist to produce data. A seismic operation generates field recordings at multi-terabyte scale, and delivering the work means moving that data — along with project files, instruction books, and manuals — between field crews, Geospace engineers, and customers. For years, that exchange ran through an FTP server Geospace hosted itself, inside a DMZ on its own corporate network.

A Security Decision With a File Server in the Way

Geospace's security team decided to shut the DMZ down entirely. A DMZ exists to expose services to the internet, and that exposure was exactly the liability the company wanted gone.

But the FTP server in that DMZ was the external file-exchange mechanism for the company's engineers. Shutting the perimeter down meant there was no internal path left to run an external-facing FTP service at all. The bind was direct: keep a perimeter segment alive solely to host one file server — preserving the exposure the shutdown was meant to eliminate — or take away the mechanism that moved seismic field data and project deliverables to customers.

The problem was never really the FTP server. It was that external file exchange required Geospace to operate exposed infrastructure on its own network. And the workload was too large to route around: terabytes of field data, far past what email or ad hoc sharing could carry, while self-hosting the server anywhere else inside the network would simply have recreated the exposure in a new location.

The replacement had to run entirely outside Geospace's network, so nothing external-facing remained on their infrastructure. It had to speak SFTP, so existing transfer workflows kept working. It had to give recipients outside the company a way to receive files through a browser, with nothing to install. And it had to absorb seismic data at terabyte scale, indefinitely.

Geospace selected Files.com as that externally hosted exchange. Its SFTP support let existing transfer workflows continue, while browser-based sharing gave external recipients a way to receive files and cloud storage kept the exchange outside Geospace's infrastructure.

File Exchange With No Footprint on the Network

Files.com became the external edge of Geospace's file exchange, hosted entirely off their network. Engineers upload data over SFTP or through the web interface and share it with named recipients outside the company — customers and field crews. What moves is everything tied to the seismic work: recordings collected in the field, project files tied to delivery and completion, instruction books, and manuals.

The external-facing endpoint belongs to Files.com, not Geospace. There is no port to open on their network, no server sitting in a perimeter segment, no storage array for IT to grow when engineers need more room. Capacity comes from the platform.

Seventeen Terabytes Later, No Perimeter to Maintain

With Files.com carrying the exchange, Geospace replaced self-hosted perimeter infrastructure with a service its network never has to expose anything for.

• Geospace runs with no DMZ at all. The security posture the shutdown was meant to achieve holds, because the file exchange that depended on the DMZ left the network rather than relocating inside it.
• Engineer-to-customer exchange kept going and grew: stored volume rose from roughly 10 TB to nearly 17 TB on Files.com.
• That growth — about half a terabyte a month of new seismic work product — is absorbed on the platform side. Adding capacity stopped being an infrastructure project.

The Exchange Left the Network, So the Perimeter Could Go

Plenty of companies keep a DMZ alive for one reason — the file server lives there. Geospace showed the dependency runs the other way: move the exchange itself onto Files.com, and there is nothing left for the perimeter to host. Security posture and file exchange stopped being a trade-off, and both have held while the data kept growing.