Summary and recommendation
Lacework, the cloud security platform trusted by enterprises for workload protection and compliance monitoring, does not offer SCIM provisioning on any plan. While Lacework supports SAML SSO integration with identity providers like Okta and Entra ID for authentication, user accounts must still be manually created and managed within the Lacework console. This creates a significant operational burden for IT teams managing security access across cloud environments, especially given Lacework's role in compliance-critical security operations.
The lack of automated provisioning creates a dangerous gap between identity governance and security tool access. Without SCIM, IT teams cannot ensure consistent user lifecycle management for a platform that monitors their most sensitive cloud workloads. Manual user management delays onboarding for security analysts, complicates offboarding procedures, and creates audit trail gaps that compliance frameworks specifically flag as high-risk violations.
The strategic alternative
Lacework has no native SCIM. Automate offboarding, user access reviews, and license workflows across every app, including the ones without APIs. We maintain the integration layer underneath. You focus on judgment, not plumbing.
Quick SCIM facts
| SCIM available? | No |
| SCIM tier required | N/A |
| SSO required first? | No |
| SSO available? | Yes |
| SSO protocol | SAML 2.0 |
| Documentation | Not available |
Supported identity providers
| IdP | SSO | SCIM | Notes |
|---|---|---|---|
| Okta | ✓ | ❌ | SSO only, no provisioning |
| Microsoft Entra ID | ✓ | ❌ | SSO via SAML only |
| Google Workspace | Via third-party | ❌ | No native support |
| OneLogin | Via third-party | ❌ | No native support |
The cost of not automating
Without SCIM (or an alternative like Stitchflow), your IT team manages Lacework accounts manually. Here's what that costs:
The Lacework pricing problem
Lacework gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Tier comparison
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Pro | Custom quote | ||
| Business | Custom quote | ||
| Enterprise | Custom quote |
Pricing and provisioning matrix
| Plan | Pricing | SSO | SCIM Provisioning |
|---|---|---|---|
| Pro | Custom quote | ❌ Not available | ❌ Not available |
| Business | Custom quote | ❌ Not available | ❌ Not available |
| Enterprise | Custom quote | ✓ SAML SSO | ❌ Not available |
What this means in practice
Manual provisioning workflow
1. IT admin receives access request for Lacework 2. Admin logs into Lacework console separately 3. Manually creates user account with appropriate role assignments 4. User can then authenticate via SSO (Enterprise only) 5. Repeat for every new hire, role change, or departure
No deprovisioning automation
Additional constraints
Summary of challenges
- Lacework does not provide native SCIM at any price tier
- Organizations must rely on third-party tools or manual provisioning
- Our research shows teams manually provisioning this app spend significant hidden costs annually
What Lacework actually offers for identity
SAML SSO only
Lacework provides basic SAML 2.0 integration for authentication:
| Feature | Support |
|---|---|
| SAML SSO | ✓ Available |
| User provisioning | ❌ None |
| User deprovisioning | ❌ None |
| Group management | ❌ None |
| Automated role assignment | ❌ None |
The reality: You get federated login but zero automation for user lifecycle management.
Okta Integration (SSO only)
The Okta Integration Network listing confirms limited functionality:
| Capability | Supported? |
|---|---|
| SAML SSO | ✓ Yes |
| Create users | ❌ No |
| Update users | ❌ No |
| Deactivate users | ❌ No |
| Group sync | ❌ No |
| Role provisioning | ❌ No |
Microsoft Entra Integration
Entra documentation shows the same limitations:
What this means: Every user onboarding, role change, and offboarding requires manual work in Lacework's console. For security platforms where access control is critical, this creates both operational overhead and compliance gaps.
What IT admins are saying
Lacework's lack of automated provisioning creates operational overhead for security teams:
- Manual user onboarding slows down access to critical security monitoring
- No way to automatically sync team changes from identity providers
- User lifecycle management requires separate processes outside of normal IT workflows
- SSO helps with authentication but doesn't solve the provisioning gap
Even with SSO configured, we still have to manually create each user account in Lacework before they can access the platform. It's an extra step that shouldn't be necessary.
The lack of SCIM support means we can't automate user provisioning like we do with our other security tools. Everything has to be done manually.
The recurring theme
While Lacework offers SSO for authentication, the absence of SCIM provisioning means IT teams must manually manage user accounts, creating friction in security team onboarding and offboarding processes.
The decision
| Your Situation | Recommendation |
|---|---|
| Small security team (<10 users) with low turnover | Manual management is workable with SSO |
| Growing security operations with regular team changes | Use Stitchflow: manual provisioning creates security gaps |
| Enterprise with compliance requirements (SOX, PCI, SOC) | Use Stitchflow: automated audit trail essential |
| Multi-cloud deployments with distributed security teams | Use Stitchflow: centralized identity management critical |
| Organizations prioritizing zero-trust architecture | Use Stitchflow: immediate deprovisioning prevents access drift |
The bottom line
Lacework delivers enterprise-grade cloud security monitoring, but forces you back to manual user management—a security anti-pattern for the very teams that need automated controls most. For security operations that demand the same rigor in identity management as threat detection, Stitchflow provides the automation Lacework should have built natively.
Make Lacework workflows AI-native
Lacework has no native SCIM. We build complete offboarding, user access reviews, and license workflows across every app, including the ones without APIs.
Technical specifications
SCIM Version
Not specifiedSupported Operations
Not specifiedSupported Attributes
Plan requirement
Not specifiedPrerequisites
Not specifiedKey limitations
- No SCIM support available
- Manual user management only
- SSO available for authentication
Documentation not available.
Configuration for Okta
Integration type
Okta Integration Network (OIN) app
Where to enable
Docs
SSO only, no provisioning
Use Stitchflow for automated provisioning.
Configuration for Entra ID
Integration type
Microsoft Entra Gallery app
Where to enable
SSO via SAML only
Use Stitchflow for automated provisioning.
Unlock SCIM for
Lacework
Lacework has no native SCIM. We still automate end-to-end workflows across every app, including the ones without APIs.
See how it works


