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

Augment RiskyPermissions.json to cover additional service principal API permissions #1471

Open
2 tasks
tkol2022 opened this issue Dec 13, 2024 · 1 comment
Open
2 tasks
Labels
enhancement This issue or pull request will add new or improve existing functionality
Milestone

Comments

@tkol2022
Copy link
Collaborator

💡 Summary

Go through the permissions listed in the Graph reference and determine if we need to augment \PowerShell\ScubaGear\Modules\Permissions\RiskyPermissions.json with any additional permissions to cover more risks. We can also see if there are any other permissions for EXO, Teams, Sharepoint that could be covered.

Motivation and context

Continuous improvement by increasing the risk surface area covered by ScubaGear

Implementation notes

  • Examine the MS Graph permissions list linked above and compare it to the RiskyPermissions.json file. Modify the json file if necessary.
  • For EXO, Teams, Sharepoint, use the Entra Id > App Registrations > app > Manage > API Permissions page and click to add a permission in order to reference the available permissions for those services. Modify the json if necessary.
@tkol2022 tkol2022 added the enhancement This issue or pull request will add new or improve existing functionality label Dec 13, 2024
@tkol2022
Copy link
Collaborator Author

In the future we might want to look at permissions prefixed with DeviceManagement*. There could be some risks that we want to flag there related to exposing user devices.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement This issue or pull request will add new or improve existing functionality
Projects
None yet
Development

No branches or pull requests

2 participants