Integrations
Azure Key Vault Data Source
See which accounts and groups can reach each vault, secret and key in Azure.
All product updates
Integrations
Azure Government Data Source
Hydden now collects from Azure Government, so agencies and contractors get the same identity view as teams on commercial Azure.
Use case
Teams that work with government data often run on Azure Government, a separate cloud from commercial Azure. Hydden collects from it the same way it does from commercial Azure. You pick the national cloud when you add the source.
Why it matters
Regulated environments need the closest watch on access. They should not be the ones left out of it.
How it works
1. Pick your cloud
Choose Azure Government when you add the Azure source.
2. Join the identity record
Each Azure Government identity is matched to the same person's other accounts.
3. Spot the risk
Privileged and ownerless accounts stand out, as in any other source.
Screens and documentation
Azure Government is available to all customers. Add an Azure source and choose the national cloud.
Need configuration detail? Technical documentation is available to customers after sign-in.
Key benefits
Let's say John, a security lead at a government contractor, runs one workload on commercial Azure and another on Azure Government. He needs one list of who has admin rights in both. Here is what Hydden does.
- Collects from both clouds.
- Matches the accounts in each to the people who own them.
- Gives John one list of admins across both clouds.
Related updates
All updatesIntegrations
Microsoft Entra ID Connector For Hydden
Entra ID identities and access in Hydden, ready for reviews and provisioning.
Integrations
GitLab Data Source
See who can reach your source code in GitLab, and who they really are.
Bring Azure Government into view
Request a trial and connect Azure Government to Hydden.