Okta Professional Services

1. Okta IAM Strategy

We will work jointly to provide an Okta Deployment strategy. We will incorporate the use of best practices for building a secure and agile enterprise with identity as management, cybersecurity, and cloud services for your business.

Strategy questions to ask yourself around your Okta IAM.

1. Do you want to centralize your accounts and access with to single sign-on?
2. Have you considered eliminating passwords where possible?
3. Would you want to authenticate users based on user location?
4. Do you want to enable strong, unique passwords everywhere else. Prevent credential stuffing and password spraying ?

2. Strategic Advisory

We will jointly advise you to achieve a repeatable and affordable process. We will effectively develop a custom, robust Okta platform related to your Identity Management, Cybersecurity, and Cloud Services to meet your business objectives.

1. Automate provisioning and de-provisioning with Okta WorkFlow Console.
2. Enable reporting so you can see who and what groups have access to which applications.
3. Periodically review user group access to applications.

3. Cybersecurity

We will help with the implementation of the overall corporate program for solution deployment and management of identity management, cybersecurity, and cloud platforms.

For Example:

1. We can help Architect your Cloud Security posture.
2. We can help implement Multi-Factor Authentication (MFA) across all applications.
3. We can ensure and enable an MFA solution with adaptive capability.

We will work to harden your authentication everywhere you can.

4. Cloud Licensing Consolidation

1. One Bill for Cloud Services
2. One place to Order.
3. One Place to Submit.

Cloud Licensing Providers we handle.

  Microsoft Office 365

  GSuite WorkSpace

  ProofPoint

  Netskope

  Okta

• How many Active Directory domains will be provisioned?
• Get a detailed description of the existing onboard process for IT?
• When is "email" generated for the new hire?
• Is there a separate OU structure for FTE and contractors in an AD?
• What is the format of the AD UPN?
• Are there development instances of AD, HR, and Okta to be used for change management?
• How clean is the existing HR data?
• How many in-scope HR users compared to AD users?
• What are the attributes to be synced between the HR system, Okta, and target applications?
• Is there HR data to determine birthright access?
• Is there HR data to distinguish in scope user communities (i.e., FTE vs. Contractor)?
• What is the current username format in HR?
• What are the user expected username formats for target applications?

How can SSO work with our active directory?

• Is the customer in a Hybrid Deployment?
• Does the customer meet Office 365 prerequisite set by Microsoft?
• Is the customer using Azure AD Connect to migrate users to O365?
• Is MFA in scope for access to O365?

Use AD and Azure AD as Single Source of Truth SSOT for your Okta instance.

For many Microsoft Office 365 customers, Microsoft Active Directory (AD) and Azure Active Directory is your core piece of the identity management infrastructure. With AD serving as the enterprise directory, user authentication and application access policies around on-premises applications are often tied to users and security groups in AD. Similarly, the ideal Microsoft Office 365 deployment should be able to tightly integrate with AD. Office 365 accounts should be created based on AD user-profiles and security groups. And users should be able to leverage their AD credentials when accessing Office 365.

When the user needs to change a password, it can all be done without a call into IT.

Everyone is happy!