Hosted access and risk
Hosted Permafrost reads your cloud using access you grant. Review how we sign in, where data is stored and how you can cut off access.
Approve our app
With OAuth admin consent, an admin accepts once. Our app then exists in your tenant with read permissions. It can read at any time without anyone signed in.
We hold one secret for our app. That same secret is used for every customer who chose this option. If we were breached, an attacker with that secret could read directory data of every customer on this option until we replaced it.
Your app, your secret
You create the app in your tenant and give us its secret, which we store in our vault. If our vault were breached, an attacker could read your tenant until you replaced the secret. Other customers are not affected by yours.
Your app, no secret
With workload identity federation, you create the app and tell Microsoft to trust sign-in requests that come from Permafrost's production system.
Each time we need access, our hosting provider issues a short-lived proof of who we are. Microsoft exchanges it for a token that lasts about one hour. No secret is stored. An attacker would need control of our running production system or our hosting account.
What is true in all three
- We can read your identity data whenever the grant is active. The method changes how we prove who we are. What we can read stays the same.
- Your identity data, findings and reports are stored in our database in our hosting region. Review data residency.
- You also rely on our hosting and database providers. Review the sub-processor list.
- Access is read-only. Changes in your tenant happen only through a separate approval you give at that moment, which is not stored.
- Removing the app or its trust setting in your own tenant stops new sign-ins by us. A token we already hold can stay valid until it expires, usually about an hour.
Before choosing hosted
Data and region
May your identity data leave your network and be stored by a supplier, and which region must it stay in?Standing access
Is a third-party app with standing read access to your directory acceptable? If not, choose self-hosted.Sign-in method
Which of the three ways matches your policy on shared secrets? The no-secret way is the strongest.Suppliers and breach terms
Have you reviewed our supplier list and breach-notification terms?Cut off access
Do you know the exact step to cut off access and who can do it?Monitor sign-ins
Will you alert on sign-ins by our app from unexpected places?
Compare with self-hosted
With self-hosted Permafrost, your identity data, findings, reports and cloud credentials stay in your environment. You create your own app registration. There is no third-party app with standing access. You own backups, upgrades and the database. At activation and every six hours on schedule, the install sends its licence key, install ID and app version. Scheduled checks also send human and non-human identity counts. The licensing service sees the source IP and stores a salted hash for abuse control when IP hashing is configured.
Run it yourselfContinue with hosted
If hosted fits your policy, continue to sign-up after reviewing these risks.
Use hosted