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

Have I been pwned #367

Open
jamesgeddes opened this issue Aug 18, 2021 · 2 comments
Open

Have I been pwned #367

jamesgeddes opened this issue Aug 18, 2021 · 2 comments
Labels
epic Issues which contain a body of work that should be broken down into specific tasks P4 Issues that are low impact and not urgent. Probably won't get much attention tbh.

Comments

@jamesgeddes
Copy link
Contributor

jamesgeddes commented Aug 18, 2021

As part of our duty of care toward our members, check if their email address or telephone number has been involved in any data breaches.

We also want to collect stats on the number of members who are and are not involved in breaches - because data is fun.

Actions

At 0700 UTC every day,

  • set not_external_breached_total and external_breached_total to 0
  • Use the Have I Been Pwned API to check all accounts
  • If the member has not been involved in a breach, add 1 to not_breached_total.
  • If the member has been involved in a breach:
    • contact the member
    • show a banner on login
    • add 1 to external_breached_total
    • require the member to set up 2FA (requires 2FA #44)
  • Graph uknown, breached & not breached as a percentage with grafana

Constraints

  • Member must opt-in to having their email address sent to haveibeenpwned.com in member settings.
  • Output datetime, external_breached_total, not_external_breached_total to the database so that they can be picked up by grafana.
  • if the member has provided SMS System Messages GDPR permissions, contact via SMS
  • if the member has not provided SMS system messages GDPR permissions but has provided email system messages permissions, contact via email
  • If no system messages GDPR permission have been provided, only show a banner on login.
  • Contact must advise that 2FA is now required on next login
  • Banner should:
    • be shown at the top of every page while member is logged in
    • explain which of their other accounts have been involved in a breach
    • explain that these accounts are not affiliated with Geek.Zone
    • be dismissed with a tickbox and button double confirmation - "I understand and will address this with those organisations"
  • Should be able to distinguish between threats that we have already notified the member about and new threats.

Impact

Low

Urgency

Later

@jamesgeddes jamesgeddes added the epic Issues which contain a body of work that should be broken down into specific tasks label Dec 8, 2021
@OMGtechy
Copy link

This shouldn't be auto-opt in / opt-out - sending someone's password without their knowing is ... eek. Just make it such that someone has to choose explicitly. Disabled until they do.

@jamesgeddes jamesgeddes added the P? Awaiting priority assignment label Apr 13, 2022
@jamesgeddes
Copy link
Contributor Author

jamesgeddes commented Apr 13, 2022

@OMGtechy With regard to,

  • opt-in/opt-out
    on reflection I do agree with you; any time that we are sharing PII with another party we need to explicitly seek permission from the user. I have updated the description accordingly.
  • what data is provided to haveibeenpwned.com
    only email addresses are shared with haveibeenpwned.com, nothing else - particularly no passwords. This would be clearly explained in the UI.

@geekzonebotold geekzonebotold added P4 Issues that are low impact and not urgent. Probably won't get much attention tbh. and removed P? Awaiting priority assignment labels Nov 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic Issues which contain a body of work that should be broken down into specific tasks P4 Issues that are low impact and not urgent. Probably won't get much attention tbh.
Projects
None yet
Development

No branches or pull requests

3 participants