Skip to content

Latest commit

 

History

History
56 lines (55 loc) · 3.99 KB

security-privacy-questionnaire.md

File metadata and controls

56 lines (55 loc) · 3.99 KB
Raw

Self-Review Questionnaire: Security and Privacy

  1. What information does this feature expose, and for what purposes?
  2. Do features in your specification expose the minimum amount of information necessary to implement the intended functionality?
    • A: The proposed design puts the User Agent in control of peer management. This approach was designed specifically to limit exposing information as much as possible.
  3. Do the features in your specification expose personal information, personally-identifiable information (PII), or information derived from either?
  4. How do the features in your specification deal with sensitive information?
  5. Do the features in your specification introduce state that persists across browsing sessions?
  6. Do the features in your specification expose information about the underlying platform to origins?
    • A: By design no such information should be exposed.
  7. Does this specification allow an origin to send data to the underlying platform?
    • A: The specification is meant to be implementable using the Open Screen Protocol, a cross platform protocol.
  8. Do features in this specification enable access to device sensors?
    • A: The specification doesn't allow direct access to device sensors.
  9. Do features in this specification enable new script execution/loading mechanisms?
    • A: No
  10. Do features in this specification allow an origin to access other devices?
  11. Do features in this specification allow an origin some measure of control over a user agent's native UI?
  12. What temporary identifiers do the features in this specification create or expose to the web?
  13. How does this specification distinguish between behavior in first-party and third-party contexts?
  14. How do the features in this specification work in the context of a browser’s Private Browsing or Incognito mode?
    • A: The specification of the OpenScreen protocol are to be followed in this area.
  15. Does this specification have both "Security Considerations" and "Privacy Considerations" sections?
    • A: Both Security and Privacy concerns have been considered.
  16. Do features in your specification enable origins to downgrade default security protections?
  17. What happens when a document that uses your feature is kept alive in BFCache (instead of getting destroyed) after navigation, and potentially gets reused on future navigations back to the document?
    • A: This is an open point. It will be addressed by studying president set by specs such as WebRTC and WebTransport.
  18. What happens when a document that uses your feature gets disconnected?
    • A: This is handled by the appropriate teardown logic & events.
  19. What should this questionnaire have asked?
    • A: No further comments. This specification purposefully makes an effort to stay within established security concepts. It exposes less information, such as IP information, about the peers involved than WebRTC.