Secure upload

How it works

The sender proves identity or holds a scoped link. The bytes are ciphertext on the wire. The server may still store them in the clear. Say whether at-rest encryption is also on.

A claims form uploads 800 MB over HTTPS with a session cookie. A packet capture shows TLS. The object lands encrypted at rest. An old bookmark to the HTTP port is refused.

How it differs

Secure upload is the inbound leg. Secure download is the outbound leg. They are separate sessions.

A valid TLS session to the wrong host is still a failed upload.

Check the name on the certificate.

On the ticket

• The practical close is a log line: time, actor, byte count, result.
• Without that line the transfer is a story.
• With it, the next person can see whether this door did what the ticket claimed.
• If the path is shared, say so in the partner profile so a later change does not silently pick a different limit, key, or region.
• On a real ticket, write down the door, the byte count, and the clock.
• For secure upload, that means naming the host or bucket, the expected size, and the time the other side must have a complete file.
• A progress bar is not that record.
• A 200 response that arrives before the complete call is not that record.
• If a retry is allowed, say how many and whether it resumes.
• If a person must approve the send, name the person.
• Partners who receive secure upload files should match on hash or size before they import.
• A same-length corrupt file passes a size check and fails a hash.
• Keep the published hash off the only channel an attacker can edit, or treat it as a corruption check rather than a substitution check.
• When the path changes, new key, new region, new cap, update the profile the same day so the next run does not use a stale limit.