Skip to main content

Identity and Access Management

Public Oath

Fluid Attacks will look for an Identity and Access Management (IAM) architecture that properly balances security and user comfort.

We will constantly look for better ways of centralizing credentials and access to all of our stack.


  1. We use Okta as our main IAM provider.
  2. It is accessible via
  3. It is managed as code using Terraform. Below is a comprehensive list:
    • Applications
    • Groups
    • Users
    • SAML integration with AWS
    • Organization settings
    • Passphrases and MFA policies
  4. Applications, groups and users are stored in encrypted YAML files using Mozilla SOPS as they contain sensitive data like application passphrases and staff personal information.
  5. Applications are third party solutions used by Fluid Attacks.
  6. Groups are Fluid Attacks' departments.
  7. Users are Fluid Attacks' staff.
  8. Users and applications belong to groups. Meaning that when a user belongs to a group, she can access all applications that belong to that same group.
  9. Policies are enforced for all staff.
  10. Developers can assume AWS roles by authenticating to Okta via aws-okta-processor.


Please read the contributing page first.