w3c/trace-context

Self-Review Questionnaire for Trace Context Level 2: Security and Privacy

kalyanaj opened this issue · 1 comments

kalyanaj commented

Filing a placeholder for filling in the self-review questionnaire for Security and Privacy.

[Self-Review Questionnaire: Security and Privacy] (https://w3ctag.github.io/security-questionnaire/)

Trace-Context Level 1 is already in recommendation status. This questionnaire is specifically for the diff/delta between it and the FPWD of Level 2.

  1. What information might this feature expose to Web sites or other parties, and for what purposes is that exposure necessary?
    There is no change to this as part of this change.
  1. Do features in your specification expose the minimum amount of information necessary to enable their intended uses?
    Yes. The newly added flag conveys that if it is set, at least the right-most 7 bytes of the trace-id MUST be randomly (or pseudo-randomly) generated.
  1. How do the features in your specification deal with personal information, personally-identifiable information (PII), or information derived from them?
    No change to the behavior as compared to Level 1 of the spec.
  1. How do the features in your specification deal with sensitive information?
    No change to the behavior as compared to Level 1 of the spec.
  1. Do the features in your specification introduce new state for an origin that persists across browsing sessions?
    No.
  1. Do the features in your specification expose information about the underlying platform to origins?
    No.
  1. Does this specification allow an origin to send data to the underlying platform?
    No.
  1. Do features in this specification enable access to device sensors?
    No.
  1. Do features in this specification enable new script execution/loading mechanisms?
    No.
  1. Do features in this specification allow an origin to access other devices?
    No.
  1. Do features in this specification allow an origin some measure of control over a user agent's native UI?
    No.
  1. What temporary identifiers do the features in this specification create or expose to the web?
    N/A
  1. How does this specification distinguish between behavior in first-party and third-party contexts?
    No change to this since Level 1.
  1. How do the features in this specification work in the context of a browser’s
    Private Browsing or Incognito mode?
    No change to this since Level 1.
  1. Does this specification have both "Security Considerations" and "Privacy
    Considerations" sections?
    Yes.
  1. Do features in your specification enable origins to downgrade default
    security protections?
    No.
  1. How does your feature handle non-"fully active" documents?
    N/A. At the moment there are no plans to implement trace context as part of the user-agent.
  1. What should this questionnaire have asked?
    The above questions cover the relevant aspects from a security and privacy perspective.
kalyanaj commented

Closing this issue as the privacy review has been completed for Level 2.