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

Feature request: Centralized way to lock out organizations syncing from/to MISP and Cerebrate instances that can't guarantee security of the synced data #199

Open
Wachizungu opened this issue Dec 18, 2024 · 0 comments

Comments

@Wachizungu
Copy link
Contributor

Wachizungu commented Dec 18, 2024

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

If one of my MISP or Cerebrate instances sees a remote connecting from an instance that indicates it's running a version I know can't keep crucial data safe, I'd like to be able to lock it (and potentially the associated organization) out without jumping through a lot of hoops.

Describe the solution you'd like

Someplace I can set "unacceptable versions" or "minimum version that can be used for syncing".

I'm putting this under cerebrate because I'm hoping it can then orchestrate that on all connected MISP and Cerebrate instances.

Additional context

I understand this wouldn't be a full safeguard, but I think it might still make life easier for admins in the future.

@Wachizungu Wachizungu changed the title Feature request: Centralized way to lock out organizations syncing from/to MISP instances that can't guarantee security of the synced data Feature request: Centralized way to lock out organizations syncing from/to MISP and Cerebrate instances that can't guarantee security of the synced data Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant