Edit

Share via

Secure Generative AI with Microsoft Entra

  • Article

As the digital landscape rapidly evolves, businesses across various industries increasingly adopt Generative Artificial Intelligence (Gen AI) to drive innovation and enhance productivity. A recent research study indicates that 93% of businesses are implementing or developing an AI strategy. Approximately the same percentage of risk leaders report feeling under-prepared or only somewhat prepared to address the associated risks. As you integrate Gen AI into your operations, you must mitigate significant security and governance risks.

Microsoft Entra offers a comprehensive suite of capabilities to securely manage AI applications, appropriately control access, and protect sensitive data:

This article delves into the specific security challenges that Gen AI poses and how you can address them with Microsoft Entra.

Discover overprivileged identities

Ensure that users have the appropriate permissions to comply with the principle of least privilege. Based on our telemetry, over 90% of identities use less than 5% of permissions granted. Over 50% of those permissions are high risk. Compromised accounts can cause catastrophic damage.

Multicloud environment management is difficult as Identity and Access Management (IAM) and security teams often need to collaborate cross-functionally. Multicloud environments can limit comprehensive view into identities, permissions, and resources. This limited view increases the attack surface on identities that have overly privileged roles and over permissioned accounts. Risk of compromised unused accounts with high permissions increases as organizations adopt multicloud.

Identify nonhuman accounts

Nonhuman accounts have repeatable patterns and are less likely to change over time. When you identify these accounts, consider using workload or managed identities and Microsoft Entra Permissions Management. Permissions Management is a Cloud Infrastructure Entitlement Management (CIEM) tool. It provides comprehensive visibility into permissions that you assign to all identities across Azure, Amazon Web Services (AWS), and Google Cloud Platform (GCP).

Trim roles down to the Zero Trust least privilege access security principle. Pay close attention to super identities (such as serverless functions and apps). Factor in use cases for Gen AI applications.

Enforce just-in-time access for Microsoft Entra roles

Microsoft Entra Privileged Identity Management (PIM) helps you manage, control, and monitor access to resources in Microsoft Entra ID, Azure, and other Microsoft Online Services (such as Microsoft 365 or Microsoft Intune). Non-PIM enabled privileged users have standing access (always in their assigned roles even when they don't need their privileges). The PIM discovery and insights page shows permanent global administrator assignments, accounts with highly privileged roles, and service principals with privileged role assignments. When you see these permissions, make note of what should be normal for your environment. Consider trimming down these roles or reducing them to just-in-time (JIT) access with PIM eligible assignments.

Directly within the discovery and insights page, you can make privileged roles PIM-eligible to reduce standing access. You can remove the assignment altogether if they don't need privileged access. You can create an access review for Global Administrators that prompts them to regularly review their own access.

Enable access controls

Permission creep creates a risk of unauthorized access and restricted company data manipulation. Secure AI applications with the same governance rules that you apply to all corporate resources. To achieve this goal, define and roll out granular access policies for all users and company resources (including Gen AI apps) with ID Governance and Microsoft Entra Conditional Access.

Ensure that only the right people have the right access level for the right resources. Automate access lifecycles at scale through controls with Entitlement Management, Lifecycle Workflows, access requests, reviews, and expirations.

Govern your Joiner, Mover, and Leaver (JML) user processes with Lifecycle Workflows and control access in ID Governance.

Configure policies and controls to govern user access

Use Entitlement Management in ID Governance to control who can access applications, groups, Teams, and SharePoint sites with multi-stage approval policies.

Configure automatic assignment policies in Entitlement Management to automatically give users access to resources based on user properties such as department or cost center. Remove user access when those properties change.

To right size access, we recommend that you apply an expiration date and/or periodic access review to entitlement management policies. These requirements ensure users don't indefinitely retain access through time-limited assignments and recurring application access reviews.

Enforce organizational policies with Microsoft Entra Conditional Access

Conditional Access brings signals together to make decisions and enforce organizational policies. Conditional Access is Microsoft's Zero Trust policy engine that takes into account signals from various sources to enforce policy decisions.

Enforce least privilege principles and apply the right access controls to keep your organization secure with Conditional Access policies. Think of Conditional Access policies as if-then statements where identities that meet certain criteria can only access resources if they meet specific requirements such as MFA or device compliance status.

Restrict access to Gen AI apps based on signals like users, groups, roles, location, or risk to enhance policy decisions.

After you deploy Conditional Access policies, use the Conditional Access gap analyzer workbook to identify sign-ins and applications where you aren't enforcing these policies. We recommend deploying at least one Conditional Access policy that targets all resources to ensure baseline access control.

Enable automation to manage employee identity lifecycle at scale

Give users access to information and resources only if they have a genuine need for them to perform their tasks. This approach prevents unauthorized access to sensitive data and minimizes potential security breach impact. Use automated user provisioning to reduce unnecessary granting of access rights.

Automate lifecycle processes for Microsoft Entra users at scale with Lifecycle Workflows in ID Governance. Automate workflow tasks to right size user access when key events occur. Example events include before a new employee is scheduled to start work at the organization, as employees change status, and as employees leave the organization.

Govern highly privileged administrative role access

There might be cases where identities require higher privilege access due to business/operational requirements such as break glass accounts.

Privileged accounts should have the highest protection level. Compromised privileged accounts can cause potentially significant or material impact on organizational operations.

Only assign authorized users to administrative roles in Microsoft Azure and Microsoft Entra. Microsoft recommends you require phishing-resistant MFA on the following roles at a minimum:

  • Global Administrator
  • Application Administrator
  • Authentication Administrator
  • Billing Administrator
  • Cloud Application Administrator
  • Conditional Access Administrator
  • Exchange Administrator
  • Helpdesk Administrator
  • Password Administrator
  • Privileged Authentication Administrator
  • Privileged Role Administrator
  • Security Administrator
  • SharePoint Administrator
  • User Administrator

Your organization might choose to include or exclude roles based on requirements. To review role memberships, configure and use directory role access reviews.

Apply role-based access control using Privileged Identity Management (PIM) and just-in-time (JIT) access. PIM provides JIT access to resources by assigning time-bound access. Eliminate standing access to lower risk of excessive or misused access. PIM allows for approval and justification requirements, MFA enforcement for role activation, and audit history.

Manage external guest identity lifecycle and access

In most organizations, end-users invite business partners (B2B) and vendors for collaboration and provide access to applications. Typically, collaboration partners receive application access during the onboarding process. When collaborations don't have a clear end date, it isn't clear when a user no longer needs access.

Entitlement Management features enable automated lifecycle of external identities with access to resources. Establish processes and procedures to manage access through Entitlement Management. Publish resources through access packages. This approach helps you to track external user access to resources and reduce the problem's complexity.

When you authorize employees to collaborate with external users, they can invite any number of users from outside your organization. If external identities use applications, Microsoft Entra access reviews help you to review access. You can let the resource owner, external identities themselves, or another delegated person you trust attest to whether they require continued access.

Use Microsoft Entra access reviews to block external identities from signing in to your tenant and deleting external identities from your tenant after 30 days.

Enforce data security and compliance protections with Microsoft Purview

Use Microsoft Purview to mitigate and manage the risks associated with AI usage. Implement corresponding protection and governance controls. Microsoft Purview AI Hub is currently in preview. It provides easy-to-use graphical tools and reports to quickly gain insights into AI use within your organization. One-click policies help you protect your data and comply with regulatory requirements.

Within Conditional Access, you can enable Microsoft Purview Adaptive Protection to flag behavior that's indicative of insider risk. Apply Adaptive Protection as you apply other Conditional Access controls to prompt the user for MFA or provide other actions based on your use cases.

Monitor access

Monitoring is crucial to detect potential threats and vulnerabilities early. Watch for unusual activities and configuration changes to prevent security breaches and maintain data integrity.

Continually review and monitor access to your environment to discover suspicious activity. Avoid permissions creep and get alerts when things unintentionally change.

In some scenarios, you might only use AI applications seasonally. For example, financial apps might have low usage outside of tax and audit season while retail apps might have usage spikes during the holiday season. Disable accounts that go unused for a significant period, especially external partner accounts, with Lifecycle Workflows. Consider seasonality if JIT or temporary account deactivation is more appropriate.

Ideally, all users follow access policies to secure access to organizational resources. When you need to use Conditional Access policies with exclusions for individual users or guests, you can avoid policy exception oversight. Use Microsoft Entra access reviews to provide auditors with proof of regular exception review.

Continually review Permissions Management. As identities stay with an organization, they tend to gather permissions while they work on new projects or move teams. Monitor the Permissions Creep Index (PCI) score within Permissions Management and set up monitoring and alerting capabilities. This approach reduces gradual permissions creep and decreases the blast radius around compromised user accounts.

  • Configure reports to regularly run. Configure custom reports for specific use cases, especially for identities that need to access Gen AI apps.
  • To monitor permissions creep across Azure, AWS, and GCP, use Permissions Management. Apply recommendations to workload identities to ensure that your Gen AI apps don't have excessive permissions or have more permissions added over time than necessary.

Related content