mirror of
https://github.com/graphql-python/graphene.git
synced 2025-02-02 20:54:16 +03:00
docs: start secu
Signed-off-by: QuentinN42 <quentin@lieumont.fr>
This commit is contained in:
parent
57cbef6666
commit
c432022582
|
@ -10,6 +10,7 @@ Contents:
|
||||||
types/index
|
types/index
|
||||||
execution/index
|
execution/index
|
||||||
relay/index
|
relay/index
|
||||||
|
security/index
|
||||||
testing/index
|
testing/index
|
||||||
api/index
|
api/index
|
||||||
|
|
||||||
|
|
10
docs/security/index.rst
Normal file
10
docs/security/index.rst
Normal file
|
@ -0,0 +1,10 @@
|
||||||
|
======================
|
||||||
|
Security consideration
|
||||||
|
======================
|
||||||
|
|
||||||
|
It is crucial to follow security best practices while deploying a GraphQL application to production.
|
||||||
|
GraphQL APIs are inherently prone to various security risks, but they can be reduced by taking appropriate precautions.
|
||||||
|
Neglecting to do so can expose the API to vulnerabilities like credential leakage or denial of service attacks.
|
||||||
|
|
||||||
|
|
||||||
|
In this section, we will discuss the most common security risks and how to mitigate them.
|
Loading…
Reference in New Issue
Block a user