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

Elaborate on security practices against DoS and Brute Force #134

Closed
aeneasr opened this issue Dec 9, 2019 · 1 comment
Closed

Elaborate on security practices against DoS and Brute Force #134

aeneasr opened this issue Dec 9, 2019 · 1 comment
Assignees
Labels
corp/m4 Up for M4 at Ory Corp.

Comments

@aeneasr
Copy link
Member

aeneasr commented Dec 9, 2019

Is your feature request related to a problem? Please describe.

Aside from built-in security features, we probably want:

  1. Protection against (D)DoS attacks
  2. Protection against Brute Force attacks
  3. Protection against Spam

Describe the solution you'd like

We do not want to build in all of these protections in Kratos.� Many protection mechanisms need to be fine-tuned to fit in the environment they're used in. For example, what a small website might see as "DDoS" is just traffic on a normal day on another site.

We should therefore elaborate on security patterns required when running ORY Kratos anywhere.

Describe alternatives you've considered

Build in these security patterns in ORY Kratos.

Additional context

The cloud service will have best-practices for brute-force and similar attacks in place.

@aeneasr aeneasr changed the title Elaborate on security practices Elaborate on security practices against DoS and Brute Force Dec 9, 2019
@aeneasr aeneasr added this to the v0.0.2 milestone Dec 9, 2019
@aeneasr aeneasr modified the milestones: v0.4.0-alpha.1, v0.5.0-alpha.1 Jun 8, 2020
@aeneasr aeneasr removed the security label Aug 20, 2020
@aeneasr
Copy link
Member Author

aeneasr commented Dec 8, 2020

I think this does not really belong in ORY Kratos but in the reverse proxy. It just adds feature bloat!

@aeneasr aeneasr closed this as completed Dec 8, 2020
@aeneasr aeneasr self-assigned this Dec 8, 2020
@aeneasr aeneasr added the corp/m4 Up for M4 at Ory Corp. label Dec 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
corp/m4 Up for M4 at Ory Corp.
Projects
None yet
Development

No branches or pull requests

1 participant