Skip to content
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

Closed
DoomDragoon opened this issue Sep 19, 2023 · 11 comments
Closed

Use/Misuse Case 5 (RBAC) #15

DoomDragoon opened this issue Sep 19, 2023 · 11 comments
Assignees

Comments

@DoomDragoon
Copy link
Collaborator

No description provided.

@Deeds101 Deeds101 changed the title Use/Misuse Case 5 Use/Misuse Case 5 (Ticket Form) Sep 20, 2023
@Deeds101 Deeds101 changed the title Use/Misuse Case 5 (Ticket Form) Use/Misuse Case 5 (RBAC) Sep 23, 2023
@Deeds101
Copy link
Owner

Iteration 1

Image

@Deeds101
Copy link
Owner

Iteration 2

Image

@Deeds101
Copy link
Owner

Iteration 3

Image

@DoomDragoon
Copy link
Collaborator Author

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!

@kdherrm88
Copy link
Collaborator

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.

@Deeds101
Copy link
Owner

Final Itteration

Image

Thank you guys, I was having a brain freeze on how to label the threat actors as well as the clients.

@Deeds101
Copy link
Owner

https://forum.itflow.org/d/345-allow-technicians-to-add-clients
itflow-org/itflow#530

This is where I got the idea for the IDOR vulnerability.

@Atmcalpine
Copy link
Collaborator

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?

@Deeds101
Copy link
Owner

Final with Revisions

Image

@Deeds101
Copy link
Owner

itflow-org/itflow#673

Reasoning for SQL injection in Use case

@Deeds101
Copy link
Owner

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

4 participants