You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
The text was updated successfully, but these errors were encountered:
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
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.
The text was updated successfully, but these errors were encountered: