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

Granular Permission system to split MISP admin and System Admin #6162

Open
digihash opened this issue Jul 30, 2020 · 4 comments
Open

Granular Permission system to split MISP admin and System Admin #6162

digihash opened this issue Jul 30, 2020 · 4 comments
Labels
T: feature request Type: feature request. This issue is requesting a new feature topic: admin This issue involves the organization administration feature

Comments

@digihash
Copy link

Is your feature request related to a problem? Please describe.

Image that you have an SLA contract with a hosting company that will host the MISP instance you want to use on their servers. In the SLA, you expect a high availability of the system and a high security standard. Because of this, the hoster won't allow you, as the client, to fiddle with the operating system, web server, database, or MISP system settings which could lead to downtime of the server.

The problem here is that the current permission system only has the option to be a site admin or an Org admin, but nothing in between.

Describe the solution you'd like

I would like a solution in this case where the Site admin is further divided in a system admin that can change system settings and a site admin that can't change any MISP server specific settings, but can do the following.

System administrator can:

  • manage Server settings & maintenance
  • manage jobs
  • update the system and all extras
  • Add/manage modules, warning lists, taxonomies, etc...

Site administrator can:

  • Manage all users
  • See all audit logs
  • Manage organisations
  • Blacklist events & organisations
  • Manage registrations

Things I'm not sure where to put it, maybe make it possible to choose and let it be added separately in a certain role

  • Sync Actions:
    • manage servers/feeds
    • manage SightingDB connections
@digihash digihash added T: feature request Type: feature request. This issue is requesting a new feature needs triage This issue has been automatically labelled and needs further triage labels Jul 30, 2020
@iglocska
Copy link
Member

As discussed before - definitely something that would be useful and it would eliminate some of the issues we have today, but it's a rather large task.

@digihash
Copy link
Author

I know @iglocska, I just wanted to log it down here so we can follow it up 👍

@iglocska
Copy link
Member

Oh no, don't get me wrong just left it as a note internally so we know that we want this but it's a larger task - thanks for creating the issue ;)

@adulau adulau removed the needs triage This issue has been automatically labelled and needs further triage label Jul 31, 2020
@enjeck enjeck added the topic: admin This issue involves the organization administration feature label Nov 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T: feature request Type: feature request. This issue is requesting a new feature topic: admin This issue involves the organization administration feature
Projects
None yet
Development

No branches or pull requests

5 participants