-
-
Notifications
You must be signed in to change notification settings - Fork 679
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
Move 3.5.2 to 3.1.3 and modify to resolve #1522 #1743
Conversation
5.0/en/0x12-V3-Session-management.md
Outdated
@@ -17,6 +17,7 @@ As previously noted, these requirements have been adapted to be a compliant subs | |||
| :---: | :--- | :---: | :---: | :---: | :---: | :---: | | |||
| **3.1.1** | [DELETED, MERGED TO 8.3.1] | | | | | | | |||
| **3.1.2** | [ADDED] Verify that the application performs all session token verification using a trusted, back-end service. | ✓ | ✓ | ✓ | 603 | | | |||
| **3.1.3** | [MOVED FROM 3.5.2, MODIFIED] Verify that the application uses either **cryptographically signed or opaque tokens** for session management. Static API secrets and keys should be avoided. | ✓ | ✓ | ✓ | 798 | 7.1 | |
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.
**cryptographically signed or opaque tokens**
I don't think it is a good idea to use markdown in the table. It messes with CSV export, for example. Also, I don't think the emphasis adds anything here.
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.
Great point @Sjord! I have removed that
3.5.2 was level 2 is the change intended? |
Yes since this is now a more general/basic requirement it should be level 1 @elarlang |
This Pull Request relates to issue #1522