-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
docs: add "OWASP API Security Top 10 2023" to Security Guidelines #8669
Conversation
👋 Hi, @kenjis! |
fb5d619
to
6205a66
Compare
6205a66
to
24089a3
Compare
This is the last PR for v4.4.8. |
OWASP recommendations | ||
--------------------- | ||
|
||
- Implement a proper authorization mechanism that relies on the user policies and |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In this case a good job is done by lonnieezell:
https://github.com/lonnieezell/forum-example/blob/develop/_docs/policies.md
|
||
- When exposing an object using an API endpoint, always make sure that the user | ||
should have access to the object's properties you expose. | ||
- Avoid using generic methods such as to_json() and to_string(). Instead, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are (to_json()
and to_string()
)codes, it is better to specify them as codes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since CI does not provide such methods, why not just leave it as it is?
Needs #8652Description
Frankly, CI4 offers very few features for API Security.
Checklist: