Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

PING Comments On Mitigation Strategies #44

Merged
merged 49 commits into from
Dec 3, 2018
Merged

PING Comments On Mitigation Strategies #44

Changes from 1 commit
Commits
Show all changes
49 commits
Select commit Hold shift + click to select a range
643fa2c
make mitigations section have 80 character line breaks
jasonanovak Oct 14, 2018
6b621a3
remove the duplicative how to use section at the end of the document
jasonanovak Oct 14, 2018
b12b60a
add mitigations section introduction
jasonanovak Oct 14, 2018
db552fc
reorder mitigations and add placeholders for new mitigations
jasonanovak Oct 14, 2018
6c636d4
add data minimization section
jasonanovak Oct 14, 2018
fc3c4a1
add Privacy Friendly Defaults
jasonanovak Oct 14, 2018
cc0ed22
explicit user mediation
jasonanovak Oct 14, 2018
5bba804
drop-feature
jasonanovak Oct 14, 2018
1f4caef
remove sanitize the data and move examples up to minimize the data
jasonanovak Oct 14, 2018
b007588
add restrict-to-first-party mitigation
jasonanovak Oct 14, 2018
fa9e943
fix spacing of drop-feature and privacy-impact-assessment
jasonanovak Oct 14, 2018
ecb8ce5
fix spacing of drop-feature and privacy-impact-assessment
jasonanovak Oct 14, 2018
58180c8
update secure origins
jasonanovak Oct 14, 2018
c1ea566
update privacy-impact-assessments
jasonanovak Oct 14, 2018
444a3f0
Address @eseltzer comments
Oct 18, 2018
cb291f8
address Nick's feedback
jasonanovak Oct 22, 2018
540e585
bikeshed w3ctag variant through PR41 including edits so links work; u…
jasonanovak Nov 9, 2018
c882fcb
make mitigations section have 80 character line breaks
jasonanovak Oct 14, 2018
8db94fb
remove the duplicative how to use section at the end of the document
jasonanovak Oct 14, 2018
3f9a72a
add mitigations section introduction
jasonanovak Oct 14, 2018
03fcf09
reorder mitigations and add placeholders for new mitigations
jasonanovak Oct 14, 2018
3905166
add data minimization section
jasonanovak Oct 14, 2018
765aef5
add Privacy Friendly Defaults
jasonanovak Oct 14, 2018
e03fd80
explicit user mediation
jasonanovak Oct 14, 2018
a153e82
drop-feature
jasonanovak Oct 14, 2018
6254dac
remove sanitize the data and move examples up to minimize the data
jasonanovak Oct 14, 2018
c56bac6
add restrict-to-first-party mitigation
jasonanovak Oct 14, 2018
7635529
fix spacing of drop-feature and privacy-impact-assessment
jasonanovak Oct 14, 2018
f3e4dbf
fix spacing of drop-feature and privacy-impact-assessment
jasonanovak Oct 14, 2018
095ce02
update secure origins
jasonanovak Oct 14, 2018
e86f99a
update privacy-impact-assessments
jasonanovak Oct 14, 2018
de021d3
Address @eseltzer comments
Oct 18, 2018
9c4ffef
address Nick's feedback
jasonanovak Oct 22, 2018
77babb8
continue rebasing week 4 against week 3
jasonanovak Nov 9, 2018
0c7f047
fixes for eventual bikeshed
jasonanovak Nov 9, 2018
a15d381
bikeshed index.src.html and edits to support it to prevent a regressi…
jasonanovak Nov 9, 2018
866f212
Simplification
lknik Nov 23, 2018
3033fd4
Not sure if we need 'friendly'
lknik Nov 23, 2018
062d592
address https://github.com/w3ctag/security-questionnaire/pull/44/file…
jasonanovak Dec 3, 2018
55de114
Merge branch 'week-04-mitigation-strategies' of github.com:jasonanova…
jasonanovak Dec 3, 2018
b81de7d
address https://github.com/w3ctag/security-questionnaire/pull/44/file…
jasonanovak Dec 3, 2018
6420040
address https://github.com/w3ctag/security-questionnaire/pull/44/file…
jasonanovak Dec 3, 2018
db29182
address https://github.com/w3ctag/security-questionnaire/pull/44/file…
jasonanovak Dec 3, 2018
ea8d5ac
https://github.com/w3ctag/security-questionnaire/pull/44#discussion_r…
jasonanovak Dec 3, 2018
91c1f14
Making it consistent with Jason's contact details
lknik Dec 3, 2018
4707eac
addressing https://github.com/w3ctag/security-questionnaire/pull/44#d…
jasonanovak Dec 3, 2018
38566f5
Merge branch 'week-04-mitigation-strategies' of github.com:jasonanova…
jasonanovak Dec 3, 2018
d0a69d9
Preserving -> friendlt
lknik Dec 3, 2018
1621032
Added potentially
lknik Dec 3, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion index.src.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -783,8 +783,14 @@ <h3 id="privacy-impact-assessment">
the end-developer, system owners, or managers responsibility to realize
this and act accordingly in the design of his/her system. Some use may
warrant conducting as privacy impact assessment, especially when data
relating to individuals may be processed. Examples.
relating to individuals may be processed.

Specifications that expose such sensitive data should include a
recommendation that websites and applications adopting the API — but not
necessarily the implementing user agent — conduct a privacy impact assessment
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do we mean by "not necessarily the implementing UA"? Why are we adding this?

of the data that they collect.

A features that recommends such is:
* [GENERIC-SENSORS] advices to consider performing of a privacy impact
assessment

Expand Down