Unique Keys per Organization | Voters

Unique Keys per Organization

in progress

Cameron Granger

Ability to have unique keys per organization (similar in length/uniqueness to account keys) that can then be disabled in the event that a customer departs and the Huntress Account holder needs to disable the account.

If you give this an upvote, do us a favor and submit your use case! This will help us get things moving.

April 30, 2021

Autopilot

Merged in a post:

Org Specific / Individual Account Keys for Agent Installation

Michael Kajewski

Currently to deploy an agent we need to use a global account wide "Account Key" along with an organisation key. The Org key doesn't matter as one is automatically created if the Account Key is correct, however should the account key gets exposed or left somewhere it shouldn't we would then need to rotate the account key and re-deploy our automations across ALL clients instead of just rotating the one that was exposed.

Can we please get a key per org or just individual keys for installation

6 days ago

Gregory Marchand

Concur - We have several co-managed IT teams and have to give out our master key to do the install

Gary Herbstman

I agree with this and had recently been thinking about the same issue.

Alexander Trout

Concur with this - we routinely need to give out both keys in co-managed scenarios. I'd prefer to have both the option to revoke org keys and the option to generate a unique keyset that can

only

be used by a specific org. I'd very much prefer to have the option to

not

hand out an account key to co-managed customers.

Matthiew Morin (Huntress)

updated the status to

in progress

Hi all, thanks for the feedback on this!
We're starting work on the ability to "revoke" or "invalidate" Organization Keys so that if an Agent attempts to register with the key, it will be denied.
This will prevent unexpected agent re-registrations and organization re-creations.

Orel Einy

This is a must-have as an MSSP to offboard customers or avoid abuse of a given organization key. Kindly promote this if possible.

Brian Saia

As an MSSP with huntress of clients, we

have

to give out installers with our Account ID in it and currently it is impossible to stop a former client from re-registering agents to our account. The ability to block registrations from an unauthorized entity is a necessary prerequisite for a platform selling to a MSSP.

Sibe Pronounced Ceebeh Klomp

This is a must have for us as an MSSP.

Hunter Mays

This is very important. Having to reset the account key to prevent old clients from being able to reinstall is more work since it impacts all current clients. In my experience, the organization key can just be made up during the installation and Huntress will then create a new organization for that key. This has created a bit of a headache for us even during normal installation since some mistypes have created random organizations that are difficult to track down the device's owner.

Eric Henry

updated the status to

under review

→