refactor: rewording

Signed-off-by: QuentinN42 <quentin@lieumont.fr>
This commit is contained in:
QuentinN42 2023-03-15 15:40:28 -07:00
parent c432022582
commit 65af30194c
No known key found for this signature in database
GPG Key ID: 2CD7D563712B3A50

View File

@ -2,9 +2,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.
As GraphQL is a query language, it allows users to use a wider pannel of inputs than traditional REST APIs.
Due to this feature, GraphQL APIs are inherently prone to various security risks, but they can be reduced by taking
appropriate precautions. Neglecting them 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.