Okta
Last updated: Nov 4, 2026
Rationale
Okta is the IAM platform that Fluid Attacks uses to manage access to hundreds of applications in the company. With it, Fluid Attacks gives access to applications but does not show the credentials. With it, Fluid Attacks can also keep a least privilege approach.
These are the primary reasons why Fluid Attacks selected it and not other alternatives:
- It is SaaS. Thus, Fluid Attacks does not maintain the infrastructure that it uses.
- Because it is an SSO platform, the talent must remember only their Okta password. After they sign in, they can get access to the applications that Fluid Attacks assigns to them.
- It gives a universal directory that keeps users, departments, applications, and permissions in one location.
- It supports Multi-factor authentication with OTPs that change every thirty seconds, and with push notifications through its Okta Verify app on IOS and Android.
- Because the Multi-factor authentication can occur on the phone of the user, Fluid Attacks does not have to manage independent security tokens.
- Its multi-factor authentication uses OOBA. This state-of-the-art authentication process uses two different communication channels: one for the application and a different one for the verification method. This process decreases the risk of identity theft, because an attacker would have to compromise the two channels.
- It requires Biometric MFA for face and fingerprint.
- It supports serverless automatic provisioning. Thus, Fluid Attacks keeps other directories of services, for example, Google Workspace and AWS IAM, automatically synchronized without more work.
- It supports SAML and OAuth. Thus, Fluid Attacks gives users access to applications without credential management.
- It supports thousands of preconfigured integrations.
- It gives detailed reports and logs about security and user activity.
- It gives a RADIUS agent for authentication on external infrastructure, for example, VPNs.
- It can apply strong password rules.
- Fluid Attacks can manage it with Terraform.
Alternatives
- OneLogin: Fluid Attacks used it for three years. It did not support as many integrations. Its automatic provisioning was not as flexible.
- Duo: It did not support as many integrations. Its automatic provisioning was not as flexible.
- Authentik: It did not support as many integrations. It did not support automatic user provisioning to Google Workspace. Thus, Fluid Attacks would have to keep its directory in sync with Google manually. It is not in the Cloudflare ZTNA IAM list. Thus, Fluid Attacks would have to use a generic approach to provision users.
Usage
Fluid Attacks uses Okta for these tasks: