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

Spam Transactions / DoS Potential #21

Open
Abstrct opened this issue Nov 7, 2015 · 0 comments
Open

Spam Transactions / DoS Potential #21

Abstrct opened this issue Nov 7, 2015 · 0 comments

Comments

@Abstrct
Copy link
Contributor

Abstrct commented Nov 7, 2015

The CCSS doesn't currently mention spam transactions at all, but depending how you deal with them there is certainly a DoS component to consider. I'm working on a project right now that could be susceptible to such an attack and I'm looking for some guidance on how best to deal with them.

My concern is that if I simply ignore transactions under a certain amount it may lead to added support requests (i.e. agitated customers), or even audit anomalies (i.e. agitated revenue agencies). If I deal with them by logging, or if I just process it like any other transaction, then my database fills up with data that isn't profitable and potentially slows down the system for everyone else.

This issue is just on the cusp of security, so an answer of out of scope is acceptable, but I would love to hear other opinions/suggestions on it.

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