Okta administrators need best practices for creating custom authentication policies that address different connection types and risk behaviors. Implementing an assurance-level model categorizes applications by sensitivity to determine the exact authenticator, location, and behavior requirements. Administrators must efficiently implement these policies across multiple applications to secure network zones, such as Virtual Private Networks (VPNs).

• Okta Identity Engine (OIE)
• Custom Authentication Policies
• Application Deployment
• Risk Management
• Assurance Level Model

Administrators need to understand how to implement custom authentication policies effectively and efficiently across different applications. These implementations must account for the variability in risk behaviors and connection types.

How are custom authentication policies optimized?

Follow these best practices to optimize custom authentication policies for application deployment:

• Assurance Level Model: Define policies around an assurance level model. Categorize applications as High Assurance, Medium Assurance, or Low Assurance. Set authenticator requirements, location criteria, and behavior criteria for each category.
• Association of Applications: Associate the appropriate policies with the corresponding applications based on their sensitivity and requirements, after defining the assurance levels.
• Continuous Review: Review and update policies regularly to adapt to changes in risk levels or application functionality.
• Educational Resources: Review the Okta Password-less webinar for additional insights and practical demonstrations.