January 20, 2026

Per-tenant security profiles: governance that matches how teams actually operate

One-size-fits-all security policies create friction for developers and gaps for high-risk environments. Per-tenant profiles let each team configure their own risk appetite.

Different teams have fundamentally different risk appetites. A finance team handling sensitive transactions needs maximum scrutiny on every access attempt. A development team working with non-production data needs the freedom to work from coffee shops on personal devices without constant MFA challenges. Forcing both into the same security posture satisfies neither.

Identity Armour introduces named security profiles—high-security, developer-friendly, and compliance-strict—that configure how the five evaluation vectors contribute to each tenant's confidence score. High-security profiles maximize device posture and behavioral analytics weights. Developer-friendly profiles relax geographic and device constraints while maintaining session integrity monitoring. Compliance-strict profiles balance all vectors equally for regulated environments.

Beyond named profiles, tenants can define custom vector weights via API, adjusting the contribution of each evaluation dimension to match their specific risk model. This means governance is not something imposed uniformly from above—it is something each team configures to match how they actually operate.

The result is less friction for legitimate users, stronger controls where they matter most, and a governance model that scales across diverse organizational units without creating policy exceptions that undermine the overall security posture.

← All posts