You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: index.html
+16-16Lines changed: 16 additions & 16 deletions
Original file line number
Diff line number
Diff line change
@@ -1102,52 +1102,52 @@ <h3 property="schema:name">Security and Privacy Review</h3>
1102
1102
<dtabout="#security-privacy-review-purpose" id="security-privacy-review-purpose"><ahref="https://www.w3.org/TR/security-privacy-questionnaire/#purpose" rel="cito:repliesTo">What information might this feature expose to Web sites or other parties, and for what purposes is that exposure necessary?</a></dt>
1103
1103
<ddabout="#security-privacy-review-purpose"><spandatatype="rdf:HTML" property="schema:description">There are no known security impacts of the features in this specification.</span></dd>
1104
1104
1105
-
<dtabout="#security-privacy-review-minimum-data" id="security-privacy-review-minimum-data"><ahref="https://www.w3.org/TR/security-privacy-questionnaire/#minimum-data">Do features in your specification expose the minimum amount of information necessary to enable their intended uses?</a></dt>
1105
+
<dtabout="#security-privacy-review-minimum-data" id="security-privacy-review-minimum-data"><ahref="https://www.w3.org/TR/security-privacy-questionnaire/#minimum-data"rel="cito:repliesTo">Do features in your specification expose the minimum amount of information necessary to enable their intended uses?</a></dt>
<dtabout="#security-privacy-review-personal-data" id="security-privacy-review-personal-data"><ahref="https://www.w3.org/TR/security-privacy-questionnaire/#personal-data">How do the features in your specification deal with personal information, personally-identifiable information (PII), or information derived from them?</a></dt>
1108
+
<dtabout="#security-privacy-review-personal-data" id="security-privacy-review-personal-data"><ahref="https://www.w3.org/TR/security-privacy-questionnaire/#personal-data"rel="cito:repliesTo">How do the features in your specification deal with personal information, personally-identifiable information (PII), or information derived from them?</a></dt>
1109
1109
<ddabout="#security-privacy-review-personal-data"><spandatatype="rdf:HTML" property="schema:description">ACL resources can contain any data including that which identifies or refers to <cite><ahref="#agent">agents</a></cite> and <cite><ahref="#agent-group">agent groups</a></cite>. Access to ACL resources is only granted to <cite><ahref="#access-subjects">Access Subjects</a></cite> with the <cite><ahref="#acl-mode-control" rel="rdfs:seeAlso"><code>acl:Control</code></a></cite> access mode, and thus by definition, <ahref="https://w3ctag.github.io/design-principles/#consent">meaningful consent</a> to any personal data that agents include about themselves is extended to other agents with control access on the ACL resource. Group resources are subject to the same Authorization conditions as any resource (that is not an ACL resource), and thus information could be exposed.</span></dd>
1110
1110
1111
-
<dtabout="#security-privacy-review-sensitive-data" id="security-privacy-review-sensitive-data"><ahref="https://www.w3.org/TR/security-privacy-questionnaire/#sensitive-data">How do the features in your specification deal with sensitive information?</a></dt>
1111
+
<dtabout="#security-privacy-review-sensitive-data" id="security-privacy-review-sensitive-data"><ahref="https://www.w3.org/TR/security-privacy-questionnaire/#sensitive-data"rel="cito:repliesTo">How do the features in your specification deal with sensitive information?</a></dt>
1112
1112
<ddabout="#security-privacy-review-sensitive-data"><spandatatype="rdf:HTML" property="schema:description">Same implications as <cite><ahref="#security-privacy-review-personal-data" rel="rdfs:seeAlso">personal information and personally-identifiable information</a></cite> in ACL resources and group resources. When including sensitive information, the sender can be aware that changes to a group resource’s Authorization can allow non-members or new members to view membership details.</span></dd>
1113
1113
1114
-
<dtabout="#security-privacy-review-persistent-origin-specific-state" id="security-privacy-review-persistent-origin-specific-state"><ahref="https://www.w3.org/TR/security-privacy-questionnaire/#persistent-origin-specific-state">Do the features in your specification introduce new state for an origin that persists across browsing sessions?</a></dt>
1114
+
<dtabout="#security-privacy-review-persistent-origin-specific-state" id="security-privacy-review-persistent-origin-specific-state"><ahref="https://www.w3.org/TR/security-privacy-questionnaire/#persistent-origin-specific-state"rel="cito:repliesTo">Do the features in your specification introduce new state for an origin that persists across browsing sessions?</a></dt>
<dtabout="#security-privacy-review-underlying-platform-data" id="security-privacy-review-underlying-platform-data"><ahref="https://www.w3.org/TR/security-privacy-questionnaire/#underlying-platform-data">Do the features in your specification expose information about the underlying platform to origins?</a></dt>
1117
+
<dtabout="#security-privacy-review-underlying-platform-data" id="security-privacy-review-underlying-platform-data"><ahref="https://www.w3.org/TR/security-privacy-questionnaire/#underlying-platform-data"rel="cito:repliesTo">Do the features in your specification expose information about the underlying platform to origins?</a></dt>
<dtabout="#security-privacy-review-send-to-platform" id="security-privacy-review-send-to-platform"><ahref="https://www.w3.org/TR/security-privacy-questionnaire/#send-to-platform">Does this specification allow an origin to send data to the underlying platform?</a></dt>
1120
+
<dtabout="#security-privacy-review-send-to-platform" id="security-privacy-review-send-to-platform"><ahref="https://www.w3.org/TR/security-privacy-questionnaire/#send-to-platform"rel="cito:repliesTo">Does this specification allow an origin to send data to the underlying platform?</a></dt>
1121
1121
<ddabout="#security-privacy-review-send-to-platform"><spandatatype="rdf:HTML" property="schema:description">No. <cite><ahref="#acl-resource" rel="cito:discusses">ACL resources</a></cite> are described within the framework of HTTP as RDF documents <cite><ahref="#acl-resource-representation" rel="cito:discusses">represented with the Turtle syntax</a></cite>. Servers might be able to redirect ACL resources, (e.g., the <code>https:</code> URLs to <code>file:</code>, <code>data:</code>, or <code>blob:</code> URLs), but no behaviour is defined by this specification.</span></dd>
1122
1122
1123
-
<dtabout="#security-privacy-review-sensor-data" id="security-privacy-review-sensor-data"><ahref="https://www.w3.org/TR/security-privacy-questionnaire/#sensor-data">Do features in this specification allow an origin access to sensors on a user’s device</a></dt>
1123
+
<dtabout="#security-privacy-review-sensor-data" id="security-privacy-review-sensor-data"><ahref="https://www.w3.org/TR/security-privacy-questionnaire/#sensor-data"rel="cito:repliesTo">Do features in this specification allow an origin access to sensors on a user’s device</a></dt>
<dtabout="#security-privacy-review-other-data" id="security-privacy-review-other-data"><ahref="https://www.w3.org/TR/security-privacy-questionnaire/#other-data">What data do the features in this specification expose to an origin? Please also document what data is identical to data exposed by other features, in the same or different contexts.</a></dt>
1126
+
<dtabout="#security-privacy-review-other-data" id="security-privacy-review-other-data"><ahref="https://www.w3.org/TR/security-privacy-questionnaire/#other-data"rel="cito:repliesTo">What data do the features in this specification expose to an origin? Please also document what data is identical to data exposed by other features, in the same or different contexts.</a></dt>
1127
1127
<ddabout="#security-privacy-review-other-data"><spandatatype="rdf:HTML" property="schema:description">No detail about another origin’s state is exposed. As the association between a resource and its ACL resource is at the discretion of the resource server, they can be on different origins (<cite><ahref="#uri-origin" rel="cito:discusses">URI Origin</a></cite>). Similarly, when a server participates in the <cite><ahref="https://fetch.spec.whatwg.org/#cors-protocol" rel="cito:citesAsAuthority">CORS protocol</a></cite> [<cite><aclass="bibref" href="#bib-fetch">FETCH</a></cite>], HTTP requests from different origins my be allowed. This feature does not add any new attack surface above and beyond normal <cite><ahref="https://fetch.spec.whatwg.org/#cors-request" rel="cito:citesAsAuthority">CORS requests</a></cite>, so no extra mitigation is deemed necessary.</span></dd>
1128
1128
1129
-
<dtabout="#security-privacy-review-string-to-script" id="security-privacy-review-string-to-script"><ahref="https://www.w3.org/TR/security-privacy-questionnaire/#string-to-script">Do features in this specification enable new script execution/loading mechanisms?</a></dt>
1129
+
<dtabout="#security-privacy-review-string-to-script" id="security-privacy-review-string-to-script"><ahref="https://www.w3.org/TR/security-privacy-questionnaire/#string-to-script"rel="cito:repliesTo">Do features in this specification enable new script execution/loading mechanisms?</a></dt>
<dtabout="#security-privacy-review-remote-device" id="security-privacy-review-remote-device"><ahref="https://www.w3.org/TR/security-privacy-questionnaire/#remote-device">Do features in this specification allow an origin to access other devices?</a></dt>
1132
+
<dtabout="#security-privacy-review-remote-device" id="security-privacy-review-remote-device"><ahref="https://www.w3.org/TR/security-privacy-questionnaire/#remote-device"rel="cito:repliesTo">Do features in this specification allow an origin to access other devices?</a></dt>
<dtabout="#security-privacy-review-native-ui" id="security-privacy-review-native-ui"><ahref="https://www.w3.org/TR/security-privacy-questionnaire/#native-ui">Do features in this specification allow an origin some measure of control over a user agent’s native UI?</a></dt>
1135
+
<dtabout="#security-privacy-review-native-ui" id="security-privacy-review-native-ui"><ahref="https://www.w3.org/TR/security-privacy-questionnaire/#native-ui"rel="cito:repliesTo">Do features in this specification allow an origin some measure of control over a user agent’s native UI?</a></dt>
<dtabout="#security-privacy-review-temporary-id" id="security-privacy-review-temporary-id"><ahref="https://www.w3.org/TR/security-privacy-questionnaire/#temporary-id">What temporary identifiers do the features in this specification create or expose to the web?</a></dt>
1138
+
<dtabout="#security-privacy-review-temporary-id" id="security-privacy-review-temporary-id"><ahref="https://www.w3.org/TR/security-privacy-questionnaire/#temporary-id"rel="cito:repliesTo">What temporary identifiers do the features in this specification create or expose to the web?</a></dt>
<dtabout="#security-privacy-review-first-third-party" id="security-privacy-review-first-third-party"><ahref="https://www.w3.org/TR/security-privacy-questionnaire/#first-third-party">How does this specification distinguish between behaviour in first-party and third-party contexts?</a></dt>
1141
+
<dtabout="#security-privacy-review-first-third-party" id="security-privacy-review-first-third-party"><ahref="https://www.w3.org/TR/security-privacy-questionnaire/#first-third-party"rel="cito:repliesTo">How does this specification distinguish between behaviour in first-party and third-party contexts?</a></dt>
1142
1142
<ddabout="#security-privacy-review-first-third-party"><spandatatype="rdf:HTML" property="schema:description">When an HTTP request includes the <code>Origin</code> header (typical Web browsers use <ahref="#origin-considerations" rel="cito:discusses">origin based security</a> to warn servers), <ahref="#web-origin-authorization" rel="cito:discusses">Authorizations are matched</a> in context of the origin of the HTTP request in addition to requiring agent identification and allowed access modes. While the use of <code>Origin</code> is not intended as client identification, the implication is that unless servers have separate mechanisms to verify the original request made by an application, the <code>Origin</code> header’s field-value can differ. In order to distinguish social entities and clients supported by authentication protocols, an issue on <cite><ahref="#client-identification" rel="cito:discusses">client identification</a></cite> is filed.</span></dd>
1143
1143
1144
-
<dtabout="#security-privacy-review-private-browsing" id="security-privacy-review-private-browsing"><ahref="https://www.w3.org/TR/security-privacy-questionnaire/#private-browsing">How do the features in this specification work in the context of a browser’s Private Browsing or Incognito mode?</a></dt>
1144
+
<dtabout="#security-privacy-review-private-browsing" id="security-privacy-review-private-browsing"><ahref="https://www.w3.org/TR/security-privacy-questionnaire/#private-browsing"rel="cito:repliesTo">How do the features in this specification work in the context of a browser’s Private Browsing or Incognito mode?</a></dt>
1145
1145
<ddabout="#security-privacy-review-private-browsing"><spandatatype="rdf:HTML" property="schema:description">No different than <q>browser’s 'normal' state</q>.</span></dd>
1146
1146
1147
-
<dtabout="#security-privacy-review-considerations" id="security-privacy-review-considerations"><ahref="https://www.w3.org/TR/security-privacy-questionnaire/#considerations">Does this specification have both "Security Considerations" and "Privacy Considerations" sections?</a></dt>
1147
+
<dtabout="#security-privacy-review-considerations" id="security-privacy-review-considerations"><ahref="https://www.w3.org/TR/security-privacy-questionnaire/#considerations"rel="cito:repliesTo">Does this specification have both "Security Considerations" and "Privacy Considerations" sections?</a></dt>
1148
1148
<ddabout="#security-privacy-review-considerations"><spandatatype="rdf:HTML" property="schema:description">Yes, in <cite><ahref="#security-considerations" rel="rdfs:seeAlso">Security Considerations</a></cite> and <cite><ahref="#privacy-considerations" rel="rdfs:seeAlso">Privacy Considerations</a></cite>.</span></dd>
1149
1149
1150
-
<dtabout="#security-privacy-review-relaxed-sop" id="security-privacy-review-relaxed-sop"><ahref="https://www.w3.org/TR/security-privacy-questionnaire/#relaxed-sop">Do features in your specification enable origins to downgrade default security protections?</a></dt>
1150
+
<dtabout="#security-privacy-review-relaxed-sop" id="security-privacy-review-relaxed-sop"><ahref="https://www.w3.org/TR/security-privacy-questionnaire/#relaxed-sop"rel="cito:repliesTo">Do features in your specification enable origins to downgrade default security protections?</a></dt>
0 commit comments