-
-
Notifications
You must be signed in to change notification settings - Fork 666
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
3.6.1 "Subscriber" is not defined #1053
Comments
Thanks for joining us! I think the "subscriber" is the end user here. New language would be helpful, go for it! |
Its merged! :) |
elarlang
pushed a commit
to elarlang/ASVS
that referenced
this issue
Oct 25, 2021
elarlang
pushed a commit
to elarlang/ASVS
that referenced
this issue
Oct 25, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi there! This is my first issue, and I am new to application security as well as standards development in general. I have been a software developer for over ten years, mostly in web development. I have always had an interest in secure coding, but six months ago I started working as an AppSec Champion in my organization. I appreciate the work here tremendously! I have already used the ASVS to create checklists for our organization.
I would appreciate any critical feedback on how to be useful to the work here
I think that 3.6.1 could be updated to more clearly state the requirement. Does "subscriber" refer to the end user, or the RP? I realize that since I don't work on Federated CSPs this may be standard language that I am just unfamiliar with.
I would be happy to submit a PR with some updated language if that's helpful.
Thanks,
Isaac Lewis
The text was updated successfully, but these errors were encountered: