V4 Access Control Additions #2064
Closed
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
Add 4 verification requirements to chapter 4 section 1
Add 3 verification requirements to chapter 4 section 2
Add 5 verification requirements to chapter 4 section 3
Marking "Added"
|
hey, to save you time - it does not make sense to create a PR before there is agreement on the related issue:
My recommendation is to create a PR for related issue when there is agreement in the issue - then we can merge it fast and it is clear for everyone, what is done and what is not. |
randomstuff
reviewed
Sep 5, 2024
|
|
||
| ## V4.2 Operation Level Access Control | ||
|
|
||
| | # | Description | L1 | L2 | L3 | CWE | | ||
| | :---: | :--- | :---: | :---: | :---: | :---: | | ||
| | **4.2.1** | Verify that sensitive data and APIs are protected against Insecure Direct Object Reference (IDOR) attacks targeting creation, reading, updating and deletion of records, such as creating or updating someone else's record, viewing everyone's records, or deleting all records. | ✓ | ✓ | ✓ | 639 | | ||
| | **4.2.2** | [MOVED TO 50.3.1] | | | | | | ||
| | **4.2.3** | [ADDED] Verify that multi-tenant applications use cross-tenant controls to ensure user operations will never affect tenants with which they do not have permissions to interact. | ✓ | ✓ | ✓ | 284 | | ||
| | **4.2.4** | Verify that access to an object is based on the originating sybject's (e.g. user's) permissions, not on the permissions of any intermediary or service acting on their behalf. | | | ✓ | 441 | |
|
Thanks @elarlang - I will close this PR and re-submit individually once we've come to a consensus on each issue. |
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.
This Pull Request relates to issues #2058 #2059 #2060 #2061 #2062 #2063