Least privilege and multi-factor authentication
Customer sessions, administrative access, and provider consoles have different authorization boundaries. Role and record ownership checks limit application operations; privileged credentials stay on the server.
Multi-factor authentication is an additional control for privileged accounts and provider consoles. For an organizational review, request the current enforcement scope, account lifecycle process, and access-review evidence. Do not infer universal MFA enforcement from the availability of an identity provider’s MFA feature.
Authentication and ownership
Account features require authentication. A signed in session does not grant access to another customer's private records. Server checks and database policies restrict access by account, role, and the requested operation.
Administrative access
Administrative routes apply additional owner or role checks. Privileged service credentials are kept on the server. Access to operational information is limited according to role and business need.
Connected tools
API and connected assistant requests use their own authorization mechanisms. Credentials should be kept private and revoked when no longer needed. Public documentation and source pages remain separate from authenticated search histories and account records.