Story
How Kubota Runs Security Operations on Okta Customer Identity
Kubota, an industrials organization in Japan, uses Okta Customer Identity from Okta to support security operations for SOC analysts.
Value results
| Category | Value result |
|---|---|
| Productivity | Fewer stalled items because endpoint detection has a clear owner |
| Risk and compliance | New joiners can see how security operations actually runs |
| Risk and compliance | Handoffs in security operations sit in a shared queue instead of a mailbox trail |
Story
Kubota is based in Japan and runs industrials operations at a scale where endpoint detection cannot live in side channels. SOC analysts were reconciling competing copies of the same work, which slowed security operations and hid who owned the next step.
The company runs security operations on Okta, with Okta Customer Identity as the product SOC analysts actually open. Okta is an identity platform for workforce and customer authentication, single sign-on, and lifecycle management. For Kubota, that means SOC analysts can open one workflow, see endpoint detection, and let neighboring teams join without inventing a parallel stack.
Public materials confirm the companies and products. They do not always publish a single verified KPI for this pairing, so the outcome here is operational: clearer ownership, fewer stalled handoffs, and a shared record for endpoint detection.