Currently taking clients

Week 6 — Security & breach

Part
7 of 10
Course
A six-week GDPR curriculum for small companies

Week 6

Final stretch!

Documenting TOMs

You've added them to your list, now it's time to document them properly. Add a section Technical and Organizational Measures to your GDPR documentation, and list the TOMs you already have in place. You can pretty much copy them over and add some detail. But if you want some inspiration on how to phrase things, just take a look at my DPA.

Let's take TOM: We make regular backups and upload them to encrypted online storage as an example:

GDPR Documentation
[...everything you previously documented...]
Technical and Organizational Measures
Backup and recovery concept
All business data is backed up, encrypted, and uploaded to secure online storage. Recovery under worst conditions is tested twice a year, or when the process changes.

That one was easy, wasn't it? And the best part is: If you need to provide your own DPA at some point, you'll be able just copy things over from your existing documentation.

Implementing New TOMs

The next step is, for each scenario, to come up with possible TOMs you could implement to mitigate or prevent any damage. You don't have to implement them immediately - this is just about you thinking about coming up with ways to solve those scenarios.

Let's say you're concerned about someone breaking into your office and stealing your contract data. Here's a few ways to prevent that:

  • You could lock the doors
  • You could look the cabinet the contracts are in
  • You could add an alarm system
  • You could hire a security guard
  • You could hide the cabinet behind a fake wall
  • You could store your contract data in a bank vault
  • You could store your contract data digitally, in an encrypted format

All of those either reduce the chance that this scenario comes to pass or reduce the amount of damage that can be caused by it.

The good news is: As a small business you aren't required to have enterprise level security. But you are required to put in an appropriate amount of effort, and what's appropriate depends on the level of impact a scenario would have: Having IP addresses leaked isn't even remotely as bad as accidentally making someone's medical history public.

That means you don't have to implement every measure you can come up with. You can pick and choose depending on the likelihood of the scenario, the importance of the data, and the effort it'd take to implement the measure.

And a lot of measures cover several scenarios at once! For example, having your contract data in an encrypted digital form and backed up somewhere online means that it doesn't matter if it's someone breaking into your shop or if the shop burns down. In either case nothing bad happens to the data. But it does open up the concern about being hacked! That then is another scenario that needs to be thought about.

Once you've decided what measures you want to implement you can add them to your List of Improvements:

List of Improvements
[...]
Implement TOM: Buy a lockable and fire proof cabinet for the contracts

You can then implement them when you have the time. But remember to add them to your documentation when you do so!