-
Notifications
You must be signed in to change notification settings - Fork 4
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
Use/Misuse Case 5 (RBAC) #15
Comments
I think this is pretty good. You have a nice progression. I would be more specific with actors names, like nurse, or ransomware attacker etc. like our professor mention in our check in. Im sure he will be looking to take points off for being too generic. IN our lectures, it also noted that is shouldn't be too technical. I had to google what RBAC meant. I always take the 'Would a 5-year-old understand this' approach. Other than some labels, I think you may be done! |
This works well. You progress through the steps showing how it is able to perform the needed steps to create more security for the product. |
https://forum.itflow.org/d/345-allow-technicians-to-add-clients This is where I got the idea for the IDOR vulnerability. |
Would phishing campaigns, password spraying, or man-in-the-middle attacks be additional attack methods that made be used to exploit the Identity Management Platform? |
Reasoning for SQL injection in Use case |
A Security Researcher discovered that the code is vulnerable with a SQL injection on the client page, this got fixed. There was also a IDOR vulnerability with the fact that people could visit vital site pages if they had a valid URL, This got put in the release milestone 1.0. |
No description provided.
The text was updated successfully, but these errors were encountered: