Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
SCIM is the standard REST API for creating, updating, and deactivating user accounts in another system, so that leavers are removed automatically rather than by ticket.

What Is SCIM?
Single sign-on handles authentication. It does not create the account in the first place, update it when someone changes team, or disable it when they leave. Those are provisioning problems, and before SCIM every application solved them differently—a CSV import here, a proprietary API there, a nightly script somebody wrote in 2019 and nobody has touched since.
SCIM, the System for Cross-domain Identity Management, standardises that. Version 2.0 is defined by RFC 7643 for the schema and RFC 7644 for the protocol, and it is now supported by most serious SaaS vendors.
SCIM defines two core resource types, User and Group, with a fixed set of attributes and an extension schema for enterprise fields such as employee number, department, cost centre, and manager. It then defines the endpoints to act on them:
POST /scim/v2/Users create
GET /scim/v2/Users/{id} read
PUT /scim/v2/Users/{id} replace
PATCH /scim/v2/Users/{id} partial update
DELETE /scim/v2/Users/{id} remove
GET /scim/v2/Users?filter=userName eq "[email protected]"
Because the schema and the endpoints are agreed in advance, an identity provider such as Microsoft Entra ID, Okta, or a dedicated governance platform can provision into any compliant application without a bespoke connector. That is the whole value proposition, and it is a large one when the estate contains two hundred SaaS applications.
One schema detail carries disproportionate weight. The active boolean on a user resource is how SCIM expresses deactivation, and almost all provisioning flows should set active to false rather than issuing a DELETE.
The reason is practical. A deleted account takes its audit history, file ownership, and in some applications its content with it. A deactivated account stops working immediately while remaining available for investigation, data retrieval, and the handover that nobody planned. Under UK GDPR you also need to be able to produce records of processing activity, and deleting the account that performed them does not help.
Where applications implement DELETE as a soft delete this distinction blurs, which is exactly why it must be tested per application rather than assumed.
SCIM makes deprovisioning possible. It does not make it happen, and three gaps account for most failures.
active to false prevents new sign-ins; it does not necessarily terminate an existing session or invalidate an issued token. The account is disabled and the person is still working. Combine SCIM deactivation with explicit session revocation, as covered in token introspection and revocation.A SCIM endpoint is an administrative API for your user directory in that application. Whoever holds its credential can create accounts, change group membership, and disable people.
Most implementations authenticate with a long-lived bearer token, which is the weakest common pattern: a static secret, often stored in the identity provider’s configuration and sometimes in a deployment script or a ticket. Prefer OAuth 2.0 client credentials with short-lived tokens where the vendor supports it, store whatever credential exists in a secrets manager, rotate it on a schedule, and restrict the endpoint by source address if the application allows it.
On the receiving side, log every SCIM operation. Account creation and group membership changes arriving through an API are exactly the events an attacker would use to create persistence, and they are frequently absent from application audit logs because they were implemented as an integration feature rather than an administrative one.
SCIM is the execution layer for identity lifecycle management: the HR system or governance platform decides what should happen, SCIM makes it happen in each application, and SAML or OpenID Connect handles the sign-in afterwards. Treat them as three layers of one design rather than separate projects.
When procuring SaaS, ask for SCIM 2.0 support specifically, and ask what the vendor does on deactivation—whether group membership is removed, whether existing sessions are terminated, and whether data ownership transfers. The answers vary widely, and finding out during an incident is expensive.
At Privia Security, we review provisioning coverage and deprovisioning effectiveness in our infrastructure and architecture review services.
No, they do different jobs and most deployments need both. SAML or OpenID Connect authenticates a user at sign-in; SCIM creates, updates, and deactivates the account that sign-in maps to. Without provisioning, leavers keep working accounts in applications that nobody disabled, which single sign-on alone will not prevent.
Deactivate in almost every case, by setting the active attribute to false. Deletion can remove audit history, file ownership, and content that the organisation still needs for investigation, handover, or data protection record-keeping. Delete only after a defined retention period and a deliberate decision, and test what each application actually does with a DELETE request.
Because deactivation usually prevents new sign-ins without terminating existing sessions or invalidating tokens already issued. Depending on the application, someone can continue working for hours. Pair SCIM deactivation with explicit session revocation at the identity provider, and verify per application how quickly access genuinely stops rather than assuming it is immediate.
Prefer OAuth 2.0 client credentials with short-lived tokens where the vendor supports it. Many implementations still use a long-lived bearer token, which is a static secret with full administrative control over that application’s user directory. Store it in a secrets manager, rotate it on a schedule, restrict by source address where possible, and log every operation.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.