l3montree-dev / l3montree-dev/devguard
Discussion: Add safety checks against DOS attacks
Open
Nobody has claimed this yet.
feature-request
- Dominant language
- Go
- Stars
- 161
- Forks
- 43
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 37
Description
We discussed possibly attack vectors for a DOS attack on DevGuard and cam up with some ideas to make it harder for attackers to execute such an attack:
- Rate Limit on ingoing requests
- Add human check to sign up process, to avoid mass creation of accounts with bots
- Add a size limit on the data which an organization can hold to avoid DOS on the database
- Monitor data growth and act on suspiciously high daily growth
Another approach would be a database which can easily be recovered after such an DOS attack on the hard drive space.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified. Start by turning the listed attack vectors into a defined scope and selecting which mitigations DevGuard should pursue; done requires an agreed approach for request limits, signup checks, organization data limits, growth monitoring, or database recovery.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, databases, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100