SFTP and secure file delivery

Despite APIs and streams, file delivery remains the workhorse of enterprise data exchange. This guide covers SFTP and secure file delivery done well.

Why files still matter

File-based delivery is simple, universal and well-suited to batch data, which is why it remains widespread in enterprise. The question is doing it securely and reliably.

Secure file transfer

SFTP and equivalent secure protocols encrypt transfer and authenticate parties. Encryption at rest and key management protect files beyond transit.

Automation and reliability

Scheduled, automated transfers with integrity checks, retries and notifications make file delivery dependable. Manual file handling is where errors creep in.

Structure and naming

Consistent file formats, schemas and naming conventions let consumers automate ingestion. A clear manifest aids validation.

Sourcing considerations

For batch data, file delivery is often the simplest fit; for live data, APIs or streams suit better. Personal data in files needs encryption and access control.

In a managed model

A managed partner can deliver data via secure, automated file transfer with integrity checks and clear conventions.

Why files still win for batch

Despite APIs and streams, secure file delivery remains the workhorse for batch data because it is simple, universal and well-suited to scheduled bulk transfer. SFTP and equivalents encrypt transfer and authenticate parties; encryption at rest and key management protect files beyond transit.

Automation and conventions

Reliability comes from automation: scheduled transfers with integrity checks, retries and notifications, plus consistent formats, schemas and naming so consumers can ingest without manual handling. A clear manifest aids validation, and personal data in files needs encryption and access control.

Sources & further reading

• SFTP/SSH and secure-transfer standards.
• ISO/IEC 27001: security controls.
• DAMA-DMBOK: data delivery.
• Internal practice: DataSupplier file delivery.