Study guide: Distinguish Security and Privacy Boundaries
A private service sends detailed answers to an external provider and supplies a signed report. Explain the data-flow/privacy question and what a valid signature does not establish.
Ideas to explain in your own words
- A cryptographic hash maps input data to a digest. It is not reversible encryption and does not by itself prove who created the input. Comparing a digest with a trusted expected digest can support integrity checking under its assumptions. Use vetted cryptographic tools rather than an invented classroom substitution as real protection.
- A digital signature supports integrity and signer authentication under a public-key scheme and its trust assumptions. Verification requires the appropriate public key and trusted association with a signer. It does not encrypt the message or prove every claim in the message is true. This lesson uses role descriptions, not real key handling.
- Security protections can prevent unauthorized access while a permitted use still creates privacy risk. Collecting unnecessary sensitive data, keeping it too long or using it for an unrelated purpose affects people even when storage is protected. A privacy review examines purpose, scope and effects, not only passwords.
- A data-flow map shows where information moves and which systems or people receive it. Crossing a trust boundary can change exposure or control. A diagram should include local storage, server storage and external recipients, not only the visible screen. The lesson’s systems are fictional and no actual data is transmitted.
Useful vocabulary
- digest
- A cryptographic hash result.
- signature
- A cryptographic integrity/authentication mechanism under a key scheme.
- trust boundary
- A transition between different control or trust contexts.
Watch your reasoning
- Matching an untrusted digest supplied by an attacker does not establish trusted origin.
- A valid signature authenticates its cryptographic relationship, not the truth of every statement.
- Encryption does not automatically make every collection purpose appropriate.
- A public-looking interface does not reveal every downstream recipient.
A worked review example
Data is mapped to a fixed-length digest. Which mechanism or evidence is stated? The supported answer is Hash digest. Distinguish digest comparison, reversible confidentiality protection and source authentication. Matching an untrusted digest supplied by an attacker does not establish trusted origin. A cryptographic hash maps input data to a digest. Answers remain only in the described browser. Which destination or boundary is described? The supported answer is Local device storage. Identify the receiver and applicable protection at each stated data-flow step. A public-looking interface does not reveal every downstream recipient. A data-flow map shows where information moves and which systems or people receive it.
Make a practice plan
- Make a four-row summary, one row for each lesson, with its computing idea and one worked decision.
- Explain one tempting mistake using the actual supplied example.
- Complete the new unit review before consulting its explanations.
- Try the transfer task on paper and compare your evidence against the model response.