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.

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

Add in-line privacy and security considerations to VISS transport #465

Open
samuelweiler opened this issue Dec 1, 2022 · 2 comments
Open
Labels
privacy-needs-resolution Issue the Privacy Group has raised and looks for a response on. security-needs-resolution Issue the security Group has raised and looks for a response on.

Comments

@samuelweiler
Copy link
Member

https://www.w3.org/TR/viss2-transport/ has no in-line Privacy nor Security writeup. I suggest the WG to prioritize the architectural stuff in #464 over this issue.

@samuelweiler samuelweiler added privacy-needs-resolution Issue the Privacy Group has raised and looks for a response on. security-needs-resolution Issue the security Group has raised and looks for a response on. labels Dec 1, 2022
@tguild
Copy link
Member

tguild commented Apr 4, 2023

Transport cannot be used without Core, inclined to refer to its privacy and security considerations. Additional security considers exist for each underlying protocol, what to reference or direct implementers to, OWASP as WoT did?

https://www.w3.org/TR/2023/CR-wot-discovery-20230119/#security-considerations

provide link to COVESA Mira board of some potential architectures - there is no one defined one - including some where VISS may be used.

W3C Automotive Best Practices is stalled but still desirable, intent to do with COVESA Data Expert Group.

https://www.w3.org/TR/2019/NOTE-wot-security-20191106/

@UlfBj
Copy link
Contributor

UlfBj commented Oct 3, 2023

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
privacy-needs-resolution Issue the Privacy Group has raised and looks for a response on. security-needs-resolution Issue the security Group has raised and looks for a response on.
Projects
None yet
Development

No branches or pull requests

3 participants