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

Re-evaluate GWS.COMMONCONTROLS.6.1v0.3 #491

Open
2 tasks
adhilto opened this issue Nov 4, 2024 · 0 comments
Open
2 tasks

Re-evaluate GWS.COMMONCONTROLS.6.1v0.3 #491

adhilto opened this issue Nov 4, 2024 · 0 comments
Milestone

Comments

@adhilto
Copy link
Collaborator

adhilto commented Nov 4, 2024

💡 Summary

Consider removing or updating 6.1, given the information here under "Motivation and context."

Motivation and context

The current policy:

All highly privileged accounts SHALL leverage Google Account authentication with phishing-resistant MFA and not the agency's authoritative on-premises or federated identity system.

The roles considered "highly privileged" are defined here.

Of those roles, the most important is super admin. However, Google Workspace does not allow you to create a super admin that uses a third-party identity provider. The question is, are the other roles important enough to keep this policy in?

Additionally, a role-based definition of highly privileged accounts has the potential to miss quite a few privileged accounts, given that you can create custom roles. A privilege-based definition might be more appropriate.

For example, a list of highly-privileged privileges probably should include the User Security Management privilege, which among other things, allows you to disable MFA org-wide.

Implementation notes

N/A

Acceptance criteria

  • Decide if we want to keep this policy
  • Decide if we want to update it from a role-based definition to a privilege-based definition
@adhilto adhilto added this to the Eel milestone Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant