Site Search

Okta

Octa

Okta Workforce Identity

The global standard for IDaaS, with over 18,000 companies using the service worldwide

The Okta Workforce Identity Big Picture

By utilizing Okta, you can improve security when using SaaS, streamline ID management operations, and strengthen governance.

The Okta Workforce Identity Big Picture

Why "IDaaS = Okta"? 4 reasons to choose it

1. Overwhelming number of supported applications

It can be linked to over 7,600 SaaS, accelerating the cloud utilization of companies.

2. Easily integrate multiple directories

Multi-domain AD and ID directories can be easily integrated, enabling a common authentication infrastructure in large-scale environments.

3. Latest security measures

We provide a secure SaaS usage environment with more than 14 types of MFA, including passwordless, and access control based on user behavior.

4. Best of Breed Zero Trust

You can build a zero trust environment with device access control through EDR/MDM integration and secure app access through integration with SASE/SSE products.

overwhelming
Number of supported applications
圧倒的なアプリケーション対応数
Multi-directory
Easy integration
マルチディレクトリを容易に統合
Latest
Security measures
最新のセキュリティ対策
Best of breed
Zero Trust
ベストオブブリードなゼロトラスト

real use case

1. Cases where SSO (single sign-on)/provisioning is supported due to the expansion of cloud adoption

  • Before
    • Even though the number of SaaS services has increased, SSO is only available for some SaaS services
    • Accounts are operated manually, which places a high operational burden
  • After
    • Okta template enables SSO for multiple SaaS
    • Provisioning function automates SaaS account operations
Before
After

2. A large-scale authentication infrastructure case that integrated multiple domain ADs

  • Before
    • AD integration is difficult, making it impossible to create a common authentication infrastructure
    • There is a risk that the operating policy of overseas SaaS is unclear
  • After
    • Easily integrate with AD to achieve a common authentication platform
    • Strengthening governance by integrating certification with common/overseas SaaS
Before
After

3. Authentication infrastructure for SaaS used exclusively by specific departments such as development and digital transformation

  • Before
    • Division-specific apps are authenticated with ID/Password only
    • Cannot be linked to the internal authentication infrastructure due to external user restrictions
  • After
    • Realizing individual authentication infrastructure for each business division
    • Strengthen security by using MFA etc. during authentication
Before
After

Inquiry/Document request

In charge of Macnica Okta Co., Ltd.

Weekdays: 9:00-17:00