This guide is for IT managers and first security hires at 50 to 500 employee companies who were just pitched an ISPM add-on, or asked by an auditor to prove identity hygiene.
Identity security posture management (ISPM) is the practice, and the category of tools that automate it, of continuously inventorying human and non-human identities, checking how they are authenticated and what they can reach, and flagging the gaps attackers use: dormant accounts, missing MFA, excess privilege and access that survived offboarding. ISPM measures posture, it does not repair it. In a mid-market company most findings trace back to an incomplete account inventory and a manual joiner, mover and leaver process, so the highest-return move is to close that loop first, then add a dedicated scanner where your identity provider's native checks stop.
Key takeaways
- Identity security posture management measures identity risk but does not fix it: findings only close when every account has an owner and a lifecycle process.
- CIS Controls v8.1 Safeguard 5.3, an Implementation Group 1 control, disables dormant accounts after 45 days, half the 90-day window Okta documents for ISPM.
- NIS2 never names ISPM, but Article 21(2)(f) requires procedures to assess whether risk-management measures work, and points (i) and (j) cover access control and MFA.
- At Satelia, a 70-person healthtech, Corma surfaced 160 applications where manual reports listed 30, the inventory its ISO 27001 and SOC 2 auditors asked for.
- At Infinox, the Head of IT Operations found long-tenured and senior leavers often carried a lot of shadow access, so their offboarding needs the closest review.
In this guide
- What is identity security posture management?
- ISPM vs ITDR, IGA, SSPM, CIEM and PAM
- What a posture check looks for at 50 to 500 employees
- Where identity posture actually breaks
- Native checks or a dedicated ISPM tool?
- What NIS2 and ISO 27001 auditors ask
- Six steps without a dedicated team
- How Corma fits, and where it does not
- Frequently asked questions
What is identity security posture management (ISPM)?
Identity security posture management is a security practice that continuously measures how well identities are controlled, and a category of software that automates the measurement. For every account, human or not, it asks four questions: should this account still exist, who owns it, how is it authenticated, and what can it reach.
In practice an ISPM tool connects to your identity stores and applications through their APIs and inspects five areas:
- Accounts: dormant accounts, orphaned accounts left behind by leavers, duplicates and local accounts that bypass single sign-on.
- Authentication: MFA coverage, especially on administrator roles and internet-facing applications, and weak or legacy sign-in methods.
- Privilege: admin sprawl, shadow admins and the gradual accumulation of rights as people change roles, which quietly erodes least privilege.
- Non-human identities: service accounts, API keys, OAuth integrations and AI agents, which the non-human identity entry in our glossary covers in more detail.
- Identity provider configuration: sign-in policies, conditional access rules and federation settings in the directory itself.
Is ISPM a product or a framework?
The vendors ranking for this term do not agree, and the disagreement matters for your budget. As of October 2026, One Identity describes ISPM as "not a single tool or product" but a framework made of IGA, PAM, ITDR and CIEM. Veza writes that ISPM is "gradually subsuming" IAM, IGA and PAM. Omada and Huntress take the opposite view: ISPM does not replace IAM or IGA, it checks whether they work. RSA lands in between and states that ISPM "builds on IGA", with IGA providing the foundation.
Our reading for a mid-market team: ISPM is the measurement layer, and the controls it measures live elsewhere. The identity provider enforces authentication, the identity governance process grants and removes access, and privileged access tooling protects admin sessions. A finding such as "14 leavers still active in the CRM" is closed by the lifecycle process, not by the scanner that found it. Buying the measurement before the controls exist produces a list nobody can act on.
ISPM vs ITDR, IGA, SSPM, CIEM and PAM: what each one covers
ISPM is preventive and inspects identities at rest: configuration, entitlements and hygiene. ITDR, identity threat detection and response, is detective and watches live sign-ins and sessions for an attack in progress. IGA decides who should have access and executes the change. The other three categories inspect neighbouring objects.
Six adjacent identity security categories
| Category | What it inspects | Question it answers | Usual owner at 50 to 500 employees |
|---|---|---|---|
| ISPM | Accounts, MFA coverage, privilege and non-human identities across the identity provider, SaaS and cloud | Which identities are weaker than our policy says? | IT or security lead, on a monthly cycle |
| ITDR | Sign-in events, token use and session anomalies on identity infrastructure | Is someone abusing an identity right now? | Security on-call, or an external SOC or MDR provider |
| IGA | Access requests, joiner, mover and leaver changes, reviews and certifications | Should this person have this access, and who approved it? | IT, with managers as reviewers |
| SSPM | Settings, sharing and third-party connections inside each SaaS application | Is this application configured safely? | Application owners, with IT |
| CIEM | Roles and permissions in AWS, Azure or Google Cloud | Which cloud identities can do more than they need? | Engineering or platform team |
| PAM | Vaulting, elevation and recording of administrator sessions | How is privileged access granted and monitored? | IT administrators |
The pair buyers confuse most is ISPM and ITDR, because several vendors now sell them side by side. They answer different questions on different timescales: posture work removes the dormant admin account before it is stolen, detection work notices when it is used. If your concern is application settings rather than identities, the SaaS security posture management guide covers that layer and how it relates to this one.
What does an identity posture check look for in a 50 to 500 employee company?
A posture check worth running at this size tests about ten controls, and seven of them come from Implementation Group 1 of the CIS Controls. CIS defines Implementation Group 1 as essential cyber hygiene and describes the typical IG1 enterprise as small to medium-sized, with limited IT and cybersecurity expertise. That is a more useful reference than the enterprise programmes described in vendor guides: measured by script on 12 October 2026, the word mid-market appears zero times on the nine editorial pages ranking in the top 20 for this query.
Ten identity posture checks mapped to CIS Controls v8.1 and NIS2
| Posture check | What failing looks like | CIS v8.1 safeguard (IG) | NIS2 Art. 21(2) |
|---|---|---|---|
| Complete account inventory | Accounts exist in SaaS apps that never went through single sign-on | 5.1, validated at least quarterly (IG1) | (i) asset management |
| Dormant accounts disabled | Accounts with no sign-in for months remain active | 5.3, after 45 days of inactivity where supported (IG1) | (i) access control policies |
| Dedicated admin accounts | Admins read email and browse from their privileged account | 5.4 (IG1) | (i) |
| Service account inventory | API keys and integration users with no owner or review date | 5.5, owner, review date and purpose, reviewed at least quarterly (IG2) | (i) |
| Access granting process | Access granted over chat and never recorded | 6.1 (IG1) | (i) |
| Access revoking process | Leavers keep access to apps outside the identity provider | 6.2, disable immediately upon termination (IG1) | (i) |
| MFA on internet-facing apps | SaaS apps reachable from anywhere with a password only | 6.3, can be enforced through the directory or SSO provider (IG1) | (j) |
| MFA on administrative access | Admin roles protected by a password alone | 6.5 (IG1) | (j) |
| Centralised access control | Apps still authenticated with local passwords | 6.7, through a directory or SSO provider (IG2) | (i) |
| Role-based access, reviewed | Privileges accumulate with every role change | 6.8, reviewed at least annually (IG3) | (i) and (f) |
Method: safeguard wording and Implementation Group levels read on the CIS Controls Assessment Specification for v8.1, Controls 5 and 6, and NIS2 points read in Directive (EU) 2022/2555 on EUR-Lex, both on 12 October 2026.
How long before an account counts as dormant?
It depends on whom you read, and this is where vendor guides contradict each other. Okta documents that its ISPM flags accounts "that have not been used for 90 days". Palo Alto Networks uses the same 90 days in its guide. Oleria suggests removing service accounts that have not authenticated in 180 days. The CIS Controls Assessment Specification for Control 5 is stricter: Safeguard 5.3 asks to "delete or disable any dormant accounts after a period of 45 days of inactivity, where supported". Germany's BSI, in its IT-Grundschutz module ORP.4, sets no number at all: accounts inactive for a longer period should be deactivated.
For a 50 to 500 employee company, take 45 days as the default. It is the only figure among these that comes from a control framework rather than a product setting, and it sits in the baseline CIS associates with organisations of your size. Then document the exceptions instead of loosening the rule. Infinox's IT operations team does exactly that: they leave notes on individual users, for example flagging "a rare auditor who only logs in once a quarter", so the account is not treated as unusual (Infinox interview, September 2026).
Where identity posture actually breaks: three patterns from Corma customers
In the three Corma customer cases below, the failing check was not MFA on the identity provider. It was the accounts nobody had listed, the access that tenure accumulates, and the tools that create no account at all.
The inventory is smaller than reality
Satelia is a 70-person healthtech based in Bordeaux that needed ISO 27001 and SOC 2 certification. Its external IT provider's reports did not show user permissions, roles or usage frequency, and auditors asked for proof of controlled access. Once connected, Corma revealed 160 applications, against the 30 identified in manual reports.
Eriel Cruz, Technical Project Manager at Satelia, puts the dependency plainly: "Without having those details, we couldn't move forward with the ISO 27001 and SOC2 certifications." (Satelia customer story, July 2026). A posture tool fed only by the systems Satelia already knew would have graded 30 applications and missed the other 130.
Tenure and seniority accumulate access
Infinox, a CFD brokerage that grew almost threefold in a year through expansion and acquisition, saw the problem at offboarding. Vadim, its Head of IT Operations, described it in September 2026:
"Anyone who'd been with the company for many years, or who held a senior managerial or C-level position, tended to have a lot of shadow access."
The same interview shows why posture coverage equals integration coverage. For the Infinox brands fully connected to Corma, offboarding the major access is a single action followed by a manual check. For the brands not yet integrated, in Vadim's words, "maybe a third of the access still has to be revoked manually". Any posture tool inherits that boundary: what is not connected is not measured.
Tools that create no account
APGAR, a 280-person consulting firm founded in Paris and running more than 80 SaaS tools, set out to increase its security posture by dealing with unauthorised applications and AI tools accessed through browsers, which evade traditional monitoring. Its compliance scope included ISO 27001 and ISO 42001. Jean-Marie Drucot, IT Manager and CISO, summarises the result: "Corma helps me enormously with all aspects of application detection and automatic management." (APGAR customer story, June 2026). An AI assistant connected through OAuth to a mailbox is an identity grant, even when no licence and no directory account exist, which is why shadow AI discovery belongs in the posture scope.
If one of these patterns describes your environment, a posture score will confirm it but will not resolve it. The fix is a complete access map and an automated leaver path: see your own access map in a Corma demo.
Do you need a dedicated ISPM tool, or does your identity provider already cover it?
Partly, and the boundary is predictable. Each identity platform now ships some posture checks, but each one's visibility stops at its own directory and the applications federated to it. A dedicated ISPM adds correlation across systems, which pays off once you run several identity stores, cloud infrastructure and many non-human identities.
Posture capabilities stated on public pages, read on 12 October 2026
| Product | Posture capability stated | Scope stated | Price shown on the page |
|---|---|---|---|
| Okta ISPM | Shadow admins, MFA gaps, local accounts, offboarded users with active access, non-human identities; dormant means unused for 90 days | Integrations listed: Azure AD and Microsoft 365, AWS, Salesforce | None, contact sales |
| Cisco Duo | Identity Security Posture Score with prioritised recommendations, dormant accounts, on-premises Active Directory monitoring | Employees, contractors and vendors, on premises or in the cloud, from one central place | The ISPM page's plan comparison lists Duo Advantage at $6 and Duo Premier at $9 per user per month (edition prices, not an ISPM price) |
| Microsoft Defender for Identity | Security posture assessments shown in Microsoft Secure Score, covering misconfigurations and legacy components such as NTLMv1 | On-premises Active Directory and hybrid identity infrastructure, through the Defender for Identity sensor | None on the documentation page |
| Google Workspace security health | Monitors the configuration of security-related Admin console settings | Supported editions listed: Enterprise, Frontline, Education Standard and Plus, Enterprise Essentials Plus | Edition-dependent; Business editions are not in the supported list |
| Veza | Access Graph, continuous risk scoring, automated remediation, strong focus on non-human identities | Active Directory, Okta, AWS IAM, GitHub and service accounts, "across the enterprise" | None |
| One Identity | Presents ISPM as a framework combining IGA, PAM, ITDR and CIEM | Educational page, not a single product | None |
| RSA | ISPM capabilities delivered through RSA Governance and Lifecycle, positioned to advance zero trust and continuous compliance | Government agencies, financial services and high-assurance organisations | None |
Method: each vendor's public product or documentation page, read on 12 October 2026. Vendors are named, not linked. Features and packaging change, so verify before buying.
Two readings matter for a mid-market buyer. First, the Google check: if your company runs Google Workspace on a Business edition, the security health page is not in the supported list, so do not count on it before checking your edition. Second, the vendor targeting: RSA names government, financial services and high-assurance organisations, Veza describes enterprise-wide scope, and Okta prices ISPM on request. These products are built for estates with several identity stores, not for one directory and 80 SaaS apps.
When a dedicated ISPM tool earns its place
- You run more than one identity store in production, for example Entra ID plus a second Okta tenant inherited through an acquisition, or an on-premises Active Directory that is still authoritative.
- Engineers create cloud IAM roles every week, and no one reviews them.
- Service accounts and API keys outnumber employees, and nobody can list them with an owner.
- Someone's job includes acting on posture findings every week. Without that person, findings become a second queue that nobody reads.
What ISPM will not fix
Practitioners say it bluntly in community threads: an ISPM finds the over-privileged account but does not fix the process that created it. Specifically:
- It does not assign owners. Every finding needs an addressee, and the tool cannot invent one.
- It does not provision or deprovision users, unless it also carries identity lifecycle features.
- It does not detect an attack in progress or a breach underway. That is ITDR, a different budget line.
- It cannot score applications it has no connector for, which is exactly where the Satelia and Infinox gaps were.
What NIS2 and ISO 27001 auditors actually ask about identity posture
Neither NIS2 nor ISO/IEC 27001 requires an ISPM product. Both ask for evidence that access controls exist, run on a schedule and are corrected when they fail.
Article 21(2) of Directive (EU) 2022/2555 (NIS2) lists the minimum cybersecurity risk-management measures. Four points land on identity posture:
- 21(2)(f): "policies and procedures to assess the effectiveness of cybersecurity risk-management measures".
- 21(2)(g): "basic cyber hygiene practices and cybersecurity training".
- 21(2)(i): "human resources security, access control policies and asset management".
- 21(2)(j): "the use of multi-factor authentication or continuous authentication solutions", among other secured communication measures.
Article 21(4) adds that an entity which finds it does not comply with these measures must take the necessary corrective measures "without undue delay". Read together, 21(2)(f) and 21(4) describe a measure-and-correct loop. That loop is what posture management automates, and the directive is indifferent to which tool runs it.
ISO 27001 auditors look for the same thing in a different vocabulary: a documented review cadence that was followed, and a record of what was removed. Corma applies that standard to itself. Its security teams page describes the exportable access evidence customers use, and its own security page states that administrative access to production is limited to a restricted number of people and that user access is evaluated quarterly and revoked upon termination.
One European point deserves a direct question during any evaluation. A posture tool needs privileged API access to your identity provider and applications, so it ends up holding a map of every employee's access. Under GDPR it is a processor of that data. Ask where it is stored and under which certification. Corma's web servers and databases run in data centres inside the European Union, under ISO/IEC 27001:2022 certification with annual independent audits.
How to run identity posture management in six steps, without a dedicated team
This sequence produces evidence fastest with the team a 50 to 500 employee company actually has.
- Build the account inventory from three sources. Combine the identity provider directory, application discovery and finance data such as card and invoice lines. Expect a gap of the Satelia kind, where 30 known applications became 160.
- Name an owner for every application and every non-human identity. CIS Safeguard 5.5 asks for a department owner, a review date and a purpose for each service account. Without owners, no later step has an addressee.
- Apply the IG1 baseline in risk order. MFA on administrative access and internet-facing apps first, dedicated admin accounts second, then the 45-day dormant rule with documented exceptions.
- Automate the leaver path. Disable access at termination, triggered by the HR system rather than an email. At Infinox, the HR termination date now reaches IT through a webhook, and a proper offboarding went from two to four hours across departments to about half an hour for an average user.
- Send a monthly inactive-user report to managers. Infinox sends automated monthly reports on inactive users to HR and managers, and managers come back with feedback. Decisions move to the people who know whether the access is still needed.
- Run access reviews on a schedule and keep the evidence. CIS asks for account inventories validated at least quarterly and role privileges reviewed at least annually. Automated access reviews produce the record of who reviewed what, when, and what was removed.
These six steps form a governance loop. A posture score becomes useful once the loop exists, because every finding then has an owner and a path to closure.
How Corma fits, and where it does not
Corma is a European SaaS management and identity governance platform built for mid-market IT teams. It is not a dedicated ISPM scanner and not an ITDR. It runs the loop that posture findings depend on: inventory, ownership, lifecycle and review, connecting discovery to policy-driven workflows for access requests, access reviews and joiner, mover and leaver changes.
Identity posture needs against Corma coverage
| Posture need | Corma | Detail |
|---|---|---|
| Inventory beyond single sign-on | Covered | Discovery of sanctioned and shadow applications, including tools adopted in the browser or installed on the machine; identities mapped to entitlements and owners |
| Dormant, unused and excess access | Covered | Alerts on risky provisions and accounts based on usage and your access policy, including admin privilege escalations and unused elevated rights |
| Joiner, mover and leaver | Covered | Zero-touch provisioning and deprovisioning; agents handle legacy tools without an API, a beta feature at Infinox in September 2026 |
| Access reviews and audit evidence | Covered | Audit-ready PDF and CSV reports of request logs, removals and existing permissions for ISO 27001 and SOC 2 |
| AI agents and non-human identities | Partial | Agents and NHIs are discovered and inventoried; API credential monitoring is not among the capabilities listed on Corma's platform pages |
| Identity provider configuration | Not covered | Conditional access and MFA policy settings: use the identity provider's native posture checks |
| Live attack detection (ITDR) | Not covered | A separate category, usually run by a SOC or MDR provider |
Corma publishes access management integration pages for Google Workspace, Microsoft Entra, Okta and JumpCloud. It was recognised in the Gartner Magic Quadrant for SaaS Management Platforms in 2025 and again in 2026. Related capabilities: identity and access management and automated identity governance. To see which accounts in your stack would fail the ten checks above, book a Corma demo.
Frequently asked questions
What is ISPM in cybersecurity?
ISPM, identity security posture management, is the continuous assessment of how identities are configured and what they can access, across the identity provider, SaaS applications and cloud. It flags dormant accounts, missing MFA, excess privilege and unowned non-human identities so they can be fixed before an attacker uses them.
What is the difference between ISPM and ITDR?
ISPM is preventive: it inspects identities at rest and reduces the attack surface. ITDR, identity threat detection and response, is detective: it watches sign-ins and sessions for attacks in progress. They complement each other, and many vendors now sell them side by side.
Do small and mid-size companies need ISPM?
They need identity posture control, which is not the same as buying a dedicated ISPM product. Below roughly 500 employees, the highest-return work is a complete account inventory, an owner per application, MFA on admin and internet-facing apps, and an automated leaver process. A dedicated tool pays off once you run several identity stores and many non-human identities.
Why do I need ISPM if I already use MFA?
MFA only protects the accounts it is enforced on. Posture work finds the accounts outside it: local logins that bypass single sign-on, leavers still active in unfederated apps, service accounts and API keys that never use MFA, and admin roles granted temporarily and never removed.
Does NIS2 require ISPM?
No. Directive (EU) 2022/2555 never names the category. Article 21(2) requires procedures to assess the effectiveness of security measures, basic cyber hygiene, access control policies and multi-factor authentication. A governance platform, a dedicated ISPM or a documented manual process can meet them, provided the evidence exists.
How often should identity posture be reviewed?
Continuously for automated checks, monthly for inactive-user reports to managers, at least quarterly for account inventories and service accounts, and at least annually for role privileges. The quarterly and annual cadences follow CIS Controls v8.1 Safeguards 5.1, 5.5 and 6.8.
.avif)






