You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: strategy.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -53,7 +53,7 @@ With all your essential data inventoried, you can now continue to select an appr
53
53
54
54
In addition to the backup method, we will also record the frequency and destination. For automated backup processes, it's common to do them whenever data is changed, daily or hourly. For manual data exports, you will probably do it monthly or every quarter.
@@ -91,7 +91,7 @@ Users often assume that a file sync (Dropbox, Nextcloud) is the same as having a
91
91
92
92
93
93
### Backup Frequency Mismatch
94
-
You probably noticed this while writing up your inventory. In some cases the velocity of the data (how often it changes) will not match your current backup frequency. That means you can expect to lose more data than specified in the RPO. So for each row make sure that the backup frequency is higher or the same as the specified RPO. If it's not, either find a way to increase it or change your RPO. Here an example:
94
+
You probably noticed this while writing up your inventory. In some cases the velocity of the data (how often it changes) will not match your current backup frequency. That means you can expect to lose more data than specified in the RPO. So for each row make sure that the backup frequency is higher or the same as the specified RPO. If it's not, either find a way to increase it or change your RPO. Here's an example:
95
95
96
96
An employee works on a file the whole day, but backups only happen once a day at night. If the file is damaged in the afternoon you lose one day's work. In this case you may need to consider local snapshots or do more frequent backups.
97
97
@@ -106,7 +106,7 @@ The next concept to be aware of is Recovery Time Objective (RTO). It describes t
106
106
107
107
108
108
### Security Issues
109
-
The data you handle will have value to other people. A competitior could be interested in documents and client lists. An employee could be interested in salary data. At the same time the fines for data breaches have been increasing. So it should be in your interest to keep *all* data locations save. This includes backup locations.
109
+
The data you handle will have value to other people. A competitior could be interested in documents and client lists. An employee could be interested in salary data. At the same time the fines for data breaches have been increasing. So it should be in your interest to keep *all* data locations safe. This includes backup locations.
110
110
111
111
For a full security review, one would also record the confidentiality and integrity requirements for each data asset. This is outside our scope. We will do a more general check for each asset to see if the locations are secure enough. For each inventory row consider the following:
0 commit comments