OneNym.idDiscuss deployment
English

THE HUMAN FIREWALL / Chapter 8

Sharing Documents and Email Without Mishaps

The most common data leaks are not break-ins but the right file sent to the wrong person, or the wrong file sent to the right one. This chapter turns safe sharing into a few quick glances you can make before anything leaves your outbox.

This page summarises the chapter. The full text is in the book.

The wrong-recipient email and the autocomplete trap

Rosa types "Pat" to email a payment summary to her supplier contact Patricia Nwosu, and autocomplete fills in Patrick Newman, a customer she emailed once months ago. Nobody tricked her; the program guessed from her whole history and she trusted it. Autocomplete offers the wrong match with the same confidence as the right one, and only you know which is which.

The fix is to read the actual addresses, not just display names, in the two seconds before you send, because a sent email cannot be pulled back. Clear out one-off contact suggestions, add the recipient last for sensitive messages, and type addresses in full when stakes are high. When forwarding, scroll down and check the earlier messages travelling with it, since a forward carries its whole history.

Reply-all, cc and bcc

Reply-all sends a comment meant for one person to everyone on the thread, so glance at the recipients before writing and treat reply-all as a deliberate choice. The difference between cc and bcc matters even more: everyone in cc can see everyone else's address, which is a leak when the recipients are strangers such as customers, event attendees or job applicants.

The rule is to use bcc, or better a proper mailing tool, whenever recipients do not already know each other. Nadia in HR handles this often, and she sets up bcc before adding a single name, putting only her own address in the To line, rather than trusting herself to remember halfway through.

The wrong attachment

Files named "final", "final_v2" and "FINAL_real" make it easy to attach last month's figures, an internal draft with private notes, or another client's report. A quieter danger is that hiding rows or columns or filtering a spreadsheet does not remove the data; it travels with the file, as do tracked changes and comments.

Open the file and check its real contents before attaching and again before sending, name files clearly, and copy just the part someone needs into a fresh document. Mia nearly sent a training budget that also carried a salaries tab and a notes tab with a manager's blunt comments. She caught it by opening the attached copy, sent a clean spreadsheet instead, and warned the manager about the original file.

Secure links instead of sensitive attachments

An attachment is a copy you hand out that can be forwarded without your knowledge. A secure link keeps the file in one controlled place and grants access that can be limited to named people, set to expire, made view-only and switched off. For sensitive material such as staff lists, invoices, customer records or contracts, prefer the link.

The book warns that revoking a link only stops future access; it cannot undo downloads, copies, screenshots or forwards already made. So if a link goes to the wrong person, revoke it and also report the disclosure promptly to security or IT. Turn off links when a project ends, so old shares do not stay open behind you.

External sharing, the final check and encryption

Data shared outside the company crosses a line you cannot see across, so read external-recipient warnings, check whether you are sharing one file or a whole folder, and be wary of requests to send work data to personal email addresses. An unusual request to share with an outside address, especially an urgent one, should be confirmed through a channel you already trust. Before any send, a short pause to check addresses, file contents, cc or bcc, link or attachment, and external recipients catches most mistakes.

Encryption simply means scrambling information so only the intended reader can read it, and the approved company tools often do this behind the scenes. If you are asked to password-protect a file, never send the password in the same email; share it another way, such as a phone call or a different app.

KEY POINTS

Key points

  • Read the real email addresses, not the display names, before sending anything sensitive.
  • Check who will receive your reply before choosing reply-all.
  • Use bcc, set up before adding names, for any group of people who should not see each other's addresses.
  • Open every attachment before sending and check the version, hidden tabs, tracked changes and comments.
  • Share sensitive files through a secure link limited to named people with an expiry date.
  • Read external-recipient warnings and never send work data to a personal email address.

QUESTIONS

Common questions

How can I avoid sending an email to the wrong person?
Before sending, read the actual email addresses rather than the display names autocomplete shows. For sensitive messages, add the recipient last and type the address in full when the stakes are high. Clearing old one-off contact suggestions also removes look-alike names that cause mistakes.
When should I use bcc instead of cc?
Use bcc whenever the recipients do not already know each other, such as customers, event attendees or job applicants. Everyone in cc can see every other address, which can reveal personal data, for example who else applied for a role. For larger groups a proper mailing tool is better still.
Does hiding rows or columns in a spreadsheet remove the data?
No. Hidden rows, hidden columns and filtered views only tuck data out of sight, and it travels with the file. Other tabs, tracked changes and comments can also reveal more than you intend. Open the file before sending and, if someone needs only part of it, copy that part into a fresh document.
Is it safer to share a link than to attach a file?
For sensitive files, usually yes. A secure link keeps one controlled copy and lets you limit access to named people, set an expiry and switch it off. Revoking it only prevents future access and cannot undo copies already downloaded or forwarded, so report any accidental disclosure promptly.
What should I do if I shared a link or file with the wrong person?
If it was a link, revoke access straight away, and in every case report the disclosure promptly to your security or IT team, saying what went out and to whom. The sooner they know, the more they can do. The book describes early reporting as the professional response, not an admission of carelessness.
Can I send the password for a protected file in the same email?
No. Sending the password with the file is like taping the key to a locked box. Send the file one way and the password another, such as by phone or in a different messaging app, so intercepting one does not reveal both.