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

More Specificity on Threat Notification #155

Open
stonevc opened this issue Jul 1, 2020 · 0 comments
Open

More Specificity on Threat Notification #155

stonevc opened this issue Jul 1, 2020 · 0 comments
Assignees
Labels
out of scope An issue that is not within the purview of the standard at present

Comments

@stonevc
Copy link

stonevc commented Jul 1, 2020

All of the current steps make sense, however, companies could go a bit further when notifying consumers of data breaches. They could, to the best of their knowledge, include who they believe caused the breach, what the breached data could be used for, and how that breached data could negatively affect a user. Consumers often don't even know what data is being collected, let alone how that data could be used maliciously. It is up to the companies to explain the full severity of the breach thoroughly to any affected users.

@billfitzgerald billfitzgerald added the out of scope An issue that is not within the purview of the standard at present label Oct 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
out of scope An issue that is not within the purview of the standard at present
Projects
None yet
Development

No branches or pull requests

3 participants