Skip to content
This repository was archived by the owner on Nov 14, 2023. It is now read-only.

Commit 929835f

Browse files
authored
Merge pull request #1615 from ihanke/patch-21
Update The-future-of-privacy.md
2 parents 8cbf83e + f147a4d commit 929835f

File tree

1 file changed

+41
-4
lines changed

1 file changed

+41
-4
lines changed

Outcomes/CISO/The-future-of-privacy.md

+41-4
Original file line numberDiff line numberDiff line change
@@ -3,10 +3,47 @@ layout : blocks/outcome
33
title : The Future of Privacy
44
---
55

6-
### Outcomes
7-
8-
- OWASP Privacy statements
9-
- Concept of a campaign and compliance of OWASP community and foundation, road map
6+
### Outcomes / Statements
7+
1. Data minimazation is a best practice, but
8+
> its difficult to control
9+
> it's difficult to enforce, because there is no general exact
10+
definition, what "minimization" means
11+
> it can be bypassed using a broad formulated user consent
12+
> we may loose this fight ...
13+
14+
2. Instead of enforce data minimazation we could invent a
15+
misuse-based model:
16+
> collecting and selling personal data is a successful business
17+
model - therefore data minimazation is hard to enforce
18+
> so: collecting data is NOT a misuse
19+
> using data without a specific user-consent IS a misuse
20+
> Correlation and / or merging of different data sources IS
21+
a misuse
22+
> future challenge: misuse cases of specific data may change
23+
in future
24+
25+
3. data anonymization is a best practice, but
26+
> big data analysis of combined data-sets may enable a
27+
re-personalization of previously anonymized data
28+
> in case of a secure, effective (randomized) data anonymization
29+
there should be no restrictions for data collection
30+
31+
4. Enforcing a consent-by-usage / consent-by-purpose model may be a part
32+
of a solution
33+
> so: organizations are allowed to store the data, but they
34+
HAVE TO aks for a usage consent for any type of content at any
35+
time they want to use those data for a new purpose
36+
> this consent has to have an defined expiration date
37+
38+
5. All data have to contain an individual time-of-expiration, were they
39+
have to be deleted automatically (auto-destroy mechanism)
40+
(except regulatory requirements force a later date of deletion)
41+
42+
6. How can we achieve that respecting privacy issues is seen as a business
43+
advantage and not a penalty? Which respect-privacy-incentives
44+
are possible?
45+
46+
7. People are adviced to use fake-identities where ever possible!
1047

1148
### Synopsis and Takeaways
1249

0 commit comments

Comments
 (0)