We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Penetration testing on a pygeoapi instance would be a valuable testing mechanism in a DevSecOps context.
Zed Attack Proxy (ZAP) could be a viable option, given it provides this functionality as GitHub Actions:
We should also consider the OWASP API Security Top 10.
The result would be a GitHub Action (.github/workflows/security.yml) that would run some/all of the above.
.github/workflows/security.yml
The text was updated successfully, but these errors were encountered:
For OWASP API Security Top 10: I would replicate what has been implemented for fastgeoapi
Sorry, something went wrong.
francbartoli
No branches or pull requests
Penetration testing on a pygeoapi instance would be a valuable testing mechanism in a DevSecOps context.
Zed Attack Proxy (ZAP) could be a viable option, given it provides this functionality as GitHub Actions:
We should also consider the OWASP API Security Top 10.
The result would be a GitHub Action (
.github/workflows/security.yml
) that would run some/all of the above.The text was updated successfully, but these errors were encountered: