Aqua does not currently offer SCIM-based user provisioning. Stepwork automates Aqua provisioning with 98% accuracy — no API required.
No native SCIM endpoint Complexity Vector: Admin roles and policy scopes are enforced via console/UI and don’t map cleanly to identity provisioning flows
Aqua supports SSO, but without a clearly app-owned SCIM endpoint, security-admin lifecycle and role enforcement still becomes manual and audit-sensitive. Stepwork enforces and records the UI-level changes needed for defensible control…which is why teams use Stepwork to automate Aqua flows with 98% accuracy without needing an API.
Aqua supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
No. Aqua does not currently offer SCIM-based user provisioning, leaving IT teams to manage user lifecycle changes manually.
Stepwork automates Aqua provisioning through interface automation — the same way a human would, but with 98% accuracy and no API required. Record the flow once, and Stepwork runs it on demand or on a schedule.
Yes. Stepwork authenticates to Aqua through your existing identity provider (Okta, Microsoft Entra ID, 1Password, etc.) and completes MFA natively — including OTP, passkeys, and push notifications. No separate credentials or service accounts are needed.
The primary risk is manual lifecycle control for security-admin access. Additional risks include over-privileged roles;, audit evidence gaps;, policy drift. Stepwork eliminates these risks by automating the entire provisioning workflow.
No. Stepwork completes MFA exactly like a human user — supporting OTP, passkeys, push notifications, and other methods. It signs in through your existing identity provider via SAML, mirroring your organization's security posture.
See how Stepwork provisions users in Aqua with 98% accuracy — in a 15-minute demo.
Book a Demo