Week 14 · lesson
Privacy and Security Are Not Opposites
Privacy and security are related, but they are not the same goal.
Privacy concerns how information about people is collected, used, shared, retained, and controlled.
Security concerns protecting systems and information from unauthorized access, alteration, disruption, or misuse.
A system can be secure and still collect more personal information than users expect.
A system can respect privacy goals and still have weak technical protections.
Use the CIA Triad carefully
Confidentiality overlaps with privacy, but the terms are not interchangeable.
Suppose a school securely stores a large amount of student activity data and only authorized staff can access it.
Confidentiality may be strong.
Privacy questions can still remain:
- Should all that data be collected?
- How long should it be retained?
- Who should be allowed to use it and for what purpose?
- Were students and families informed?
- Can the data be reused for another purpose later?
Security asks whether the data is protected.
Privacy also asks whether the data practice itself is appropriate.
Trade-offs need stakeholders
A privacy-versus-security question often looks different depending on who is affected.
For a fictional encrypted messaging system, stakeholders might include:
- ordinary users
- victims of crime
- law-enforcement investigators
- technology companies
- cybersecurity professionals
- journalists
- government agencies
- people at risk of abuse or surveillance
Do not assume every stakeholder wants the same outcome or faces the same risk.
Build a stakeholder matrix
Use a teacher-provided fictional scenario:
Investigators possess a locked encrypted device believed to contain evidence relevant to a serious investigation. The device maker says weakening its security design could create risks for other users.
Create:
| Stakeholder | Goal | Security concern | Privacy concern | Evidence needed |
|---|
Complete at least five stakeholders.
Avoid false binaries
Weak framing:
Privacy or safety. Pick one.
Stronger framing:
- Which specific data is being requested?
- What authority or process governs access?
- Is the requested technical capability limited to one case or reusable?
- What new risk could the capability create?
- What alternatives exist?
- Who bears the cost if the design changes?
Real policy questions often involve competing risks, not one good side and one bad side.
Security controls can support privacy
Examples:
- encryption can reduce unauthorized disclosure
- access controls can limit who sees personal data
- logging can reveal inappropriate access
- data minimization can reduce what needs protection
- retention limits can reduce long-term exposure
Privacy-aware design can make security easier by reducing the amount of sensitive information the system stores.
Build a trade-off map
Choose one classroom scenario:
- school location-tracking app
- camera system
- encrypted messaging service
- student device monitoring
Map:
benefit → data required → security control → privacy cost → alternative design
Then propose one change that preserves the core benefit while reducing unnecessary data collection or access.
Evidence for Lesson 1
Submit:
- five-stakeholder matrix
- one trade-off map
- one privacy-preserving redesign
- one paragraph explaining why confidentiality and privacy are related but not identical
Finish with:
A privacy/security decision becomes stronger when we specify ________ instead of arguing about ________.
The goal is not to eliminate disagreement. It is to make the disagreement precise enough that evidence can matter.
decision flow
Monitoring, Alerts, and Baselines: Defensive Evidence Flow
Authorize
Confirm the classroom boundary and permitted evidence.
Observe
Inspect a provided artifact or isolated system state.
Assess
Connect evidence to risk, limitation, and control.
Defend
Document a safeguard and how it would be safely verified.
Read this concept flow as plain text
- Authorize. Confirm the classroom boundary and permitted evidence.
- Observe. Inspect a provided artifact or isolated system state.
- Assess. Connect evidence to risk, limitation, and control.
- Defend. Document a safeguard and how it would be safely verified.