Improve security best practices in documentation #1501
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: QuentinN42 <[email protected]>
Signed-off-by: QuentinN42 <[email protected]>
Signed-off-by: QuentinN42 <[email protected]>
Signed-off-by: QuentinN42 <[email protected]>
Signed-off-by: QuentinN42 <[email protected]>
Signed-off-by: QuentinN42 <[email protected]>
Signed-off-by: QuentinN42 <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Greetings!
I work as a DevSecOps at Escape, where we operate a tool for testing the security of GraphQL. Securing web applications is crucial, and our objective is to simplify the process of adopting security best practices.
Our team has been looking at the Graphene engine for quite some time, and we have contributed to its documentation by incorporating our expertise in GraphQL security measures.
Specifically, I have improved the existing documentation by improving @aryaniyaps' documentation about custom validators presenting the vulnerabilities, potential exploits, and examples of mitigation code samples with the Graphene engine. My primary focus has been enhancing vulnerability comprehension by providing relevant examples.
Furthermore, we learned a problem with GraphQL in the underlying server itself (CORS, Headers ...). So I have added a paragraph to lead them to the other docs.
Thanks for this engine, and have a great day!