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

Improve security best practices in documentation #1501

Open
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

QuentinN42
Copy link
Contributor

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!

Signed-off-by: QuentinN42 <quentin@lieumont.fr>
Signed-off-by: QuentinN42 <quentin@lieumont.fr>
Signed-off-by: QuentinN42 <quentin@lieumont.fr>
Signed-off-by: QuentinN42 <quentin@lieumont.fr>
Signed-off-by: QuentinN42 <quentin@lieumont.fr>
Signed-off-by: QuentinN42 <quentin@lieumont.fr>
Signed-off-by: QuentinN42 <quentin@lieumont.fr>
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

Successfully merging this pull request may close these issues.

None yet

1 participant