Read a sample: 1. Thinking Through Data Protection Decisions
Mara, an IT analyst at a regional equipment supplier, receives a straightforward request: give the service team access to a spreadsheet of customer repairs. The team wants to spot recurring failures before its next planning meeting.
The spreadsheet contains product identifiers, repair dates, technician notes, customer names, and contact details. It lives in a shared folder, and the easiest response would be to copy it into the team’s workspace.
That response might also create a second, loosely managed collection of customer information. The service team may need repair histories but not customer phone numbers. Some notes may contain details entered in free text. If the copied file is altered, the team could make decisions from inaccurate records. If access is blocked entirely, the business loses a useful opportunity to improve service.
Mara’s decision is not simply whether to protect the spreadsheet. It is how to make the needed information useful while managing the risks created by access, copying, modification, and retention.
That is the central skill in this book. Data protection controls are most useful when they are selected for a specific purpose, applied to a defined asset, and evaluated against the way people actually work.
An information asset is information that has value to an organization, along with the context needed to use and protect it. The asset might be a customer database, a design document, an employee roster, a set of application logs, or a backup. A single file can contain several kinds of information with different sensitivities.
The word asset matters because it shifts attention from a particular device to what the information does for the organization. A laptop may be replaceable, but the unpublished plans stored on it may not be. Conversely, a database server may be expensive, but the more significant concern may be the accuracy and availability of the records it holds.
To identify the asset, ask practical questions:
- What information is involved, and what does it contain?
- What business activity depends on it?
- Where is it created, stored, processed, shared, and copied?
- Who uses it, manages it, and makes decisions about it?
- What could happen if it were exposed, altered, unavailable, or kept too long?
These questions often reveal a broader scope than the original request suggests. Mara’s spreadsheet is not necessarily the only copy of the repair information. The source may be a service application; the spreadsheet may be an export; an email attachment or backup may contain another copy. Protecting the shared folder alone would leave those other locations outside the decision.
It is equally important not to make the scope so broad that no one can act. Mara does not need to map every system in the company before addressing the service team’s request. She does need enough context to understand the proposed export, its contents, its intended users, and where it is likely to go.
Information moves through a lifecycle. The stages are not always linear, and an organization may use different names for them, but the following model is useful for making protection decisions:
1. Creation or collection: Information is generated or obtained.
2. Use and processing: People or systems view, analyze, update, or transform it.
3. Storage: Information is held in active systems, files, databases, or other repositories.
4. Sharing and transfer: Information moves between users, systems, organizations, or locations.
5. Retention and archival: Information is kept for operational, contractual, legal, or other approved purposes.
6. Disposal: Information and media are deleted or sanitized when they are no longer required to be kept.
A record may pass through several stages at once. An archived file is stored, for example, and it may later be retrieved and shared. A backup is created and retained while the production data continues to be used. The model is a way to ask where controls are needed, not a claim that every piece of data follows an identical path.
At collection, the most effective protection may be to avoid collecting a field that has no legitimate purpose. During use, access controls can limit who can see or change the data. During transfer, encryption can protect information on the network path it covers. During retention, a schedule can prevent records from being kept indefinitely without reason. At disposal, the appropriate method depends on the information, the medium, and the organization’s control over it.
No one control follows information perfectly through every stage. Encrypting a laptop’s storage, for instance, can reduce exposure if the device is lost while its data is protected at rest. It does not prevent an authorized user from opening a file and sending its contents elsewhere. Likewise, deleting a file from a working folder does not by itself establish what happened to its backups or other copies.
Lifecycle thinking makes those boundaries visible. It encourages a candidate to ask not only, “Which control fits this situation?” but also, “What happens before and after this control is applied?”
Data protection decisions involve different forms of authority and expertise. A useful distinction is between the person accountable for the information and the people who operate the systems that hold it.
A data owner is typically a business role responsible for decisions about a defined set of information, including its appropriate use and protection. A custodian or system administrator implements and maintains technical controls on the owner’s behalf. Users need access to perform legitimate work. Security and privacy…