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

Idea for a third threat model example #527

Open
hirasso opened this issue Aug 2, 2024 · 0 comments
Open

Idea for a third threat model example #527

hirasso opened this issue Aug 2, 2024 · 0 comments

Comments

@hirasso
Copy link

hirasso commented Aug 2, 2024

As I was reading through the two scenarios described in the Tutorial, I had a strong feeling that one important threat model was not covered: Myself as a developer! The threat model goes like this:

  • I build a website that contains a contact form where submitters can leave their contact information
  • I store the submitted contact form data in my database
  • At some point in the future, I do a mysqldump and forget about the resulting *.sql file in a public folder on the server
  • I also don't have a .htaccess directive to prevent direct access to *.sql files

This is the scenario I find the most likely for many simpler websites. Data theft. Maybe you find this a useful addition to the scenarios? It's not so much about implementation but more about realizing a threat even exists.

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

1 participant