① Logs cannot be stored for a long period of time

• Okta's standard log storage period is 90 days (*).
  *Documentation: https://help.okta.com/ja-jp/content/topics/reports/syslog-filters.htm
  *As of August 2, 2024
• If logs need to be stored on an annual basis due to corporate security policies or audit compliance, additional operational efforts such as manually downloading the logs will be required.

② It is unclear whether the partner's SaaS license is being used appropriately

• The number of consumed licenses / active users on the SaaS side that is connected to Okta is not explicitly visualized, and in order to check, it is necessary to look at Okta logs and reports, which takes time and effort.

The service called "MUCV for Okta" will solve these issues!

① Logs can be stored for a long period of time

• Logs can be stored for one year. If you wish, we can store logs for more than one year!
• Logs are automatically collected by MUCV for Okta. Administrators do not need to collect them manually, so no additional operational effort is required!
  
  <Log storage mechanism>
  
  
  
• Log collection also brings the following benefits! It allows you to visualize user authentication status. You can immediately check when, who, and where someone accessed something!
  
  <Visualization image>
  

② Visualization of SaaS license usage status linked to Okta

• It is possible to pick out and display SaaS with a large discrepancy between the number of users and the number of purchased SaaS licenses (i.e. the actual number of users is small). This is useful for proper management of license numbers!
• You can also identify users who use the service infrequently. Use this to reconsider license allocation!
  
  <Visualization image>