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

Feedback on section 3.2 Threat Model #235

Open
simoneonofri opened this issue Mar 7, 2024 · 2 comments
Open

Feedback on section 3.2 Threat Model #235

simoneonofri opened this issue Mar 7, 2024 · 2 comments

Comments

@simoneonofri
Copy link

During a discussion on Threat Modelling, where it was appreciated that we had public Threat Models, I received this feedback from Loren Kohnfelder.

I am just quoting it here, hoping that it will be useful:

3.2.1 WoT Primary Stakeholders: System User should include excessive bandwidth consumption, as well as device being bricked by OEM such as a bad update Denial of Service threats.
3.2.2 Assets: System Provider Data says Others: no access, but I would think System User needs readonly access to configuration data.
3.2.3 Adversaries: Disappointed to see the Careless OEM threat out of scope because today I think this is the biggest problem with connected devices. Also Careless System Provider. It seems that more transparent devices (see 3.2.2 comment) could help System Users see what's going on.

@mmccool
Copy link
Contributor

mmccool commented Apr 22, 2024

Thanks, that is useful feedback! Regarding "Careless OEM" - there's also the "Malicious OEM"... we will have to think about what we can do here. But you're right, more transparency would help.

@mmccool
Copy link
Contributor

mmccool commented Apr 22, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants