Access model
Read-only by design
Connections to your environment are read-only. Scans collect configuration state from Microsoft 365, Entra ID, and Azure and make no changes. The platform cannot modify settings, create or delete users, alter policies, or write anything into your tenant, because it is never granted the permission to.
Access to Microsoft environments uses Microsoft Entra app registrations with certificate-based authentication and least-privilege read scopes. That means the scopes requested are the minimum needed to read the configuration controls carriers ask about on a cyber insurance questionnaire: things like MFA policy state, privileged role assignments, and email authentication settings.
You stay in control at every point:
- You grant consent. The connection is authorized in your own Microsoft tenant by your own administrators. Nothing is connected without that consent.
- You can revoke it at any time. Revocation happens in your tenant, on your schedule, without needing to contact SecValley. Once revoked, scans stop.
- You can see exactly what was granted. The app registration and its read scopes are visible in your tenant like any other enterprise application.
This is the same standard we hold the environments we scan to. A product that checks whether your controls match what you told your carrier should itself be the easiest connection on your books to explain.