Story
Tenable
KrakenKraken Standardizes Access Control on Tenable
Kraken, a financials organization in the United States, uses Nessus from Tenable to support identity operations for IAM and helpdesk.
Teams at Kraken moved access control onto Tenable after local tools started to collide.
“Financials work at Kraken spans more than one site, even when headquarters sits in the United States.”
“IAM and helpdesk asked for a shared way to run identity operations without freezing local judgment.”
Independent write-up. Figures come from public sources or are illustrative.
Value results
| Category | Value result |
|---|---|
| Productivity | Fewer stalled items because access control has a clear owner |
| Risk and compliance | Nessus is the governed place IAM and helpdesk use for identity operations |
| Capability | New joiners can see how identity operations actually runs |
Story
Financials work at Kraken spans more than one site, even when headquarters sits in the United States. Access control was splitting across regional habits. IAM and helpdesk asked for a shared way to run identity operations without freezing local judgment.
Tenable (Nessus) is what they standardized on. Tenable provides exposure management software that helps organizations find and prioritize vulnerabilities across IT, cloud, and OT. Kraken uses it as the system of record for access control, with IAM and helpdesk as the primary operators and other groups coming in through the same queue.
Leaders get a picture they can actually walk. Teams get fewer mystery statuses. The story is about operating change, not an unpublished percentage.
