Skip to content

Improve security best practices in documentation#1501

Open
QuentinN42 wants to merge 7 commits intographql-python:masterfrom
QuentinN42:feat/security
Open

Improve security best practices in documentation#1501
QuentinN42 wants to merge 7 commits intographql-python:masterfrom
QuentinN42:feat/security

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.

1 participant