Identity Access Management

Access Governance for Mid-Market: Model, Controls and Tooling

Corma Founder & COO Nikolai Fomm
Nikolai Fomm
COO and co-founder
November 17, 2026
1
minute of reading
Access Governance for Mid-Market: Model, Controls and Tooling

This access governance guide is for IT and security leads at 50 to 500 employee companies that already run an identity provider and must now prove who has access to what for ISO 27001, SOC 2 or NIS2.

Access governance for a mid-market company comes down to a light operating model, eight controls and one tooling decision. The model names who decides on access (application owners and line managers), who executes changes (IT) and who stays accountable (management). The eight controls map directly to NIS2, DORA and ISO 27001. The tooling decision depends on one figure: the share of your applications that your identity provider actually controls.

Key takeaways

  • Access governance is the discipline of deciding, reviewing and proving who holds which access, while user access management executes the grants and revocations it approves.
  • NIS2 applies to companies with 50 or more employees in the sectors it covers, and its Article 21(2)(i) lists access control policies among the required measures.
  • Among NIS2, DORA and ISO 27001, only DORA's ICT risk standards set a frequency for updating access rights: every 6 months for critical-function systems, yearly otherwise.
  • At Satelia, a 70-person healthtech company, discovery found 160 applications where the previous manual report counted about 30, a gap that had blocked its ISO 27001 and SOC 2 certifications.
  • In a 50 to 500 person company, application owners and managers decide on access, IT executes the changes, and the management body stays accountable under NIS2 Article 20.

What is access governance, and how is it different from user access management?

Access governance is the discipline of defining, reviewing and proving who holds access to which systems, and why. User access management is the operational side: it creates accounts, grants and removes permissions, and enforces login policies. Governance checks that the result of that work is correct, and keeps the evidence.

The EU rules that implement NIS2 describe the governance output in concrete terms. In-scope digital providers must "maintain a register of access rights granted", apply logging to the management of those rights, and document the results of each review, under points 11.2.2 and 11.2.3 of the Annex to Commission Implementing Regulation (EU) 2024/2690. That register of access rights, and the decisions attached to it, is what an auditor actually reads.

Access governance vs user access management

DimensionAccess governanceUser access management
Core questionShould this person still have this access, and can we prove it?Can this person get the access they need, quickly and safely?
Main activitiesPolicy, access reviews, certification, separation of duties checks, evidenceProvisioning, deprovisioning, SSO, MFA, policy enforcement at login, fulfilling access requests
Typical owner (50 to 500 employees)Security or compliance lead, with application ownersIT operations
OutputRegister of access rights, review records, remediation logWorking accounts and permissions in each application
Failure modeAudit finding, privilege creep, excessive permissions, orphaned accountsSlow onboarding, a leaver who can still log in

In a company of this size, user access management usually lives in the identity provider and in a ticket queue: someone requests an application, a manager agrees in a chat message, IT creates the account. Each step works, but nothing connects them. Access governance adds the missing thread: a policy that says who may approve what, a record of every decision, and a regular check that the access still matches the person's role.

The two depend on each other: governance without management produces review decisions nobody applies, and management without governance produces access nobody can justify. For the full comparison of the identity layers, see our guide on identity governance vs identity management. For a one-paragraph definition, use our IT glossary entry on access governance.

Why does access governance become urgent between 50 and 500 employees?

Because the regulatory threshold and the application sprawl arrive at the same time. NIS2 starts at 50 employees in the sectors it covers, and at that size the application estate often outgrows the IT team's list, as the Satelia case below shows.

What NIS2 changes at 50 employees

Article 2(1) of the NIS2 Directive (EU) 2022/2555 applies to entities of the sectors listed in its Annexes I and II that qualify as medium-sized enterprises or larger. Under the EU definition of SMEs (Recommendation 2003/361/EC), a company with 50 or more employees is no longer a small enterprise. Some entities are covered whatever their size.

  • Article 21(2)(i) requires "human resources security, access control policies and asset management".
  • Article 21(2)(j) adds multi-factor or continuous authentication "where appropriate".
  • Article 20(1) makes the management body approve these measures, oversee their implementation and answer for infringements.

For in-scope companies, access governance therefore stops being an IT preference and becomes a board-level obligation. Our NIS2 compliance checklist for IT teams covers the other measures of Article 21.

You already have access debt

The second force is the stock of access already granted. Access governance in a growing company never starts from a clean slate: it starts from years of accounts created by different people, in tools nobody fully listed. The work is less about designing a process than about finding out what exists, because every unlisted account is attack surface that no review will ever cover.

Satelia, a 70-employee healthtech company based in Bordeaux, is a clear case. In a video published in June 2026, its technical project manager Eriel Cruz explains that Corma surfaced 160 applications, where "the manual report we used to have only counted like 30". On the Satelia customer story, he adds: "Without having those details, we couldn't move forward with the ISO 27001 and SOC2 certifications."

Héloïse Rozès, co-founder and CEO of Corma, described the same drift when the company announced its seed round in December 2025: "the risks of data leaks and access abuse increases every day with the rise of Shadow AI and the overall permission sprawl."

This guide is not written for enterprises with a dedicated IAM team and ERP separation of duties projects, for data teams governing access to warehouses (data access governance), or for developers building customer login (CIAM). It is written for the IT lead who has to make access provable with the team they already have.

Which operating model works for a mid-market company?

A simple split works: owners decide, IT executes, security oversees, and the management body stays accountable. Mid-market companies rarely have an IAM team, so the operating model has to fit inside roles that already exist.

DORA's ICT risk standards make the split explicit for financial entities. The access control policy must cover the "assignment of roles and responsibilities for granting, reviewing, and revoking access rights", under Article 21, point (e)(i), of Commission Delegated Regulation (EU) 2024/1774. Outside finance, it is, in our reading, the clearest written version of what an ISO 27001 or NIS2 auditor will ask you to show.

Access governance RACI for a 50 to 500 employee company

ActivityManagement bodySecurity or compliance leadApplication ownerLine managerIT teamHR
Approve the access control policyARCICI
Keep the application and account inventoryIACR
Approve access requestsIARC
Create, change and remove accounts (joiner, mover, leaver)IICA, RR (triggers the event)
Run periodic access reviewsIAR (permission levels)R (who needs the app)C (prepares campaigns)
Review privileged and admin accountsIACR
Keep evidence and answer auditorsIACR

R: responsible, A: accountable, C: consulted, I: informed. Model built by Corma from Article 20 of NIS2 and Article 21 of Delegated Regulation (EU) 2024/1774, read in October 2026.

How does the model change between 50 and 500 employees?

The roles stay the same, but the people who hold them change with size.

  • Around 50 to 150 employees, the IT lead often doubles as security lead, and application owners are simply department heads (finance owns the accounting tool, sales owns the CRM). One person can run the whole cycle if the inventory and the evidence are automated.
  • Around 150 to 500 employees, a dedicated security or compliance role appears, each critical application gets a named owner, and a short quarterly meeting reviews exceptions, open findings and leavers still active.
  • With subsidiaries or several countries, owners are named per entity. CITEL Guichard, a 400-employee manufacturer, came to Corma needing better onboarding and offboarding, fine-grained access controls, and IT processes adapted to its subsidiaries, including outside Europe.

Who should own access reviews: IT, managers or application owners?

Split the review in two. Line managers confirm that each person still needs each application; application owners confirm which permission level inside the application is justified. IT prepares the campaign and applies the revocations, but should not decide on behalf of the business.

The failure mode is well known in IT communities. An r/sysadmin thread on access reviews sums it up: "Line managers approve everything to make the review go away." Three counter-measures work in companies without an IAM team:

  • Keep campaigns short: one application or one team at a time, never the whole estate in one spreadsheet.
  • Make "revoke if unsure" the default, with a fast restore path so a wrong revocation costs minutes, not days.
  • Show usage next to every account, such as the last login date, so the reviewer decides on facts.

Corma applies this to itself: its security page states that user access "is evaluated on a quarterly basis and revoked upon termination". Security teams can see how this runs in practice on our page on how Corma helps security teams stay compliant.

Which access governance controls do auditors and regulators expect?

Eight controls cover what NIS2, DORA and ISO 27001 ask about access. None of them requires an enterprise IAM program. Each one requires an owner, a frequency and a piece of evidence.

Access governance control catalogue mapped to EU texts and ISO 27001

ControlWhat it means in practiceEvidence an auditor asks forNIS2 and IR 2024/2690DORA RTS 2024/1774ISO/IEC 27001:2022 Annex A
1. Application and account inventoryEvery application, account and owner listed, including apps outside SSORegister of access rights with named ownersArt. 21(2)(i); IR 11.2.2(e)Art. 20(2), records of identity assignments5.9, 5.18
2. Access policy and role baselinesNeed-to-know, least privilege and separation of duties defined per roleApproved policy and a role-to-application matrixArt. 21(2)(i); IR 11.2.2(a)Art. 21(a) and (b)5.3, 5.15
3. Joiner, mover, leaverAccounts created, changed and removed from HR eventsLeaver dates matched with account deactivation datesIR 11.2.2(b)Art. 20(2)(b); Art. 21(e)(iii)5.16, 5.18
4. Access requests and approvalsAny extra access requested and approved by the right personRequest log with approver and dateIR 11.2.2(c)Art. 21(e)(i)5.18
5. Periodic access reviewsOwners confirm or revoke entitlements on a set cadenceReview records with decisions and the changes appliedIR 11.2.3Art. 21(e)(iv)5.18
6. Privileged and admin accountsSeparate admin accounts, strong authentication, tighter reviewsAdmin account list, MFA status, review recordsArt. 21(2)(j); IR 11.3Art. 21(e)(ii) and (f)(ii)8.2, 8.5
7. Third-party, shared and non-human accountsContractors, shared accounts, service accounts and AI agents limited in scope and duration, each with a named sponsorList of external, shared and non-human accounts with owners and end datesIR 11.2.2(d)Art. 20(2)(a); Art. 21(c)5.16
8. Logging and evidence trailEvery grant, change and revocation recordedExportable audit trailIR 11.2.2(f)Art. 20(2), records kept after departures8.15

Method note: catalogue built by Corma from the NIS2 Directive (EU) 2022/2555, the Annex to Implementing Regulation (EU) 2024/2690, Delegated Regulation (EU) 2024/1774 and the ISO/IEC 27001:2022 Annex A control titles, read in October 2026. Regulation 2024/2690 binds the digital providers listed in Article 21(5) of NIS2, such as cloud, data centre and managed service providers. For other NIS2 entities, we use it as a benchmark of what "access control policies" means in practice.

Read the first row again: it is where Satelia's certification stalled, because the inventory stopped at a manual report. That is the gap an IGA layer closes first. Corma's identity governance and administration platform maps every identity to its entitlements and owners across federated, unfederated and shadow applications, then runs requests, reviews and joiner, mover, leaver changes from that single record.

The second weak point is the end of the review. A revocation decided in a spreadsheet is not a control until it has been applied in the target application and checked. An auditor who samples a few revocations will look for exactly that proof, so the evidence trail should link each "revoke" decision to the date the account was actually removed or downgraded.

How often must access rights be reviewed? What the texts actually say

No EU text imposes quarterly reviews. DORA's standards set the only figures, and the NIS2 implementing rules require reviews "at planned intervals" that you define and document. Quarterly is a sound practice, not a legal minimum.

Review frequency in the texts

SourceWho it bindsWhat it says about review frequency
Delegated Regulation (EU) 2024/1774, Art. 21(e)(iv)Financial entities under DORAAccess rights updated at least every 6 months for ICT systems supporting critical or important functions, and at least once a year for all other ICT systems
Implementing Regulation (EU) 2024/2690, Annex 11.2.3 and 11.3.3Cloud, data centre, managed service and other digital providers under NIS2Reviews "at planned intervals", results and changes documented, privileged accounts included
NIS2 Directive, Art. 21(2)(i)Essential and important entitiesNo frequency: requires access control policies
ISO/IEC 27001:2022, Annex A 5.18Certified organizationsNo frequency: access rights provisioned, reviewed, modified and removed according to your own access control policy

Some vendors now argue that continuous monitoring makes periodic reviews obsolete. Continuous monitoring of usage and risky grants is useful, but it does not replace a dated, attributed review decision: that record is precisely what the DORA and NIS2 texts above ask you to document.

Our recommendation for a 50 to 500 person company: quarterly for privileged accounts and applications holding financial, health or customer data, twice a year for the rest, and an immediate check at every role change or departure. It meets the DORA minimum with margin and gives an ISO 27001 auditor a cadence you can actually hold. Corma runs automated and compliant access reviews with campaigns, reminders and an exportable audit trail.

Which tooling fits: identity provider, review tool or SaaS management with IGA?

Start from coverage, not features. If most of your critical applications are federated to your identity provider, its governance module may be enough. If a large share is not, an IdP-native review only certifies part of the estate, and you need a layer that sees the rest.

Corma splits an application estate into three groups: federated apps (connected to the identity provider through SSO or SCIM), unfederated apps (known and in use, but outside the identity provider) and shadow IT (in use, but unknown to IT). Governance tools differ mainly by how far they reach into the second and third groups.

Access governance tooling: four architectures compared

ApproachExamplesReaches unfederated and shadow appsJoiner, mover, leaverEvidence for auditsBest fit
Identity provider governance moduleMicrosoft Entra ID Governance, Okta Identity GovernanceOnly apps connected to the IdPStrong for connected appsReviews and logs for connected appsMost critical apps already behind SSO and SCIM
Standalone access review toolReview-only tools fed by exportsOnly what you importNoGood review records, revocations applied elsewhereAudit-driven need, few applications
SaaS management platform with IGACormaYes, through IdP, finance and browser discoveryYes, through SCIM, APIs and agentsReviews, logs and license data in one record50 to 500 employees, lean IT, many SaaS apps
Enterprise IGA suiteSailPoint, SaviyntYes, with connectors built in a projectYesExtensive, including ERP separation of duties1,000+ employees with a dedicated IAM team

Licensing matters as much as features when choosing user access management tools. Okta includes Identity Governance, which covers access requests and access reviews, only from its Essentials suite at $17 per user per month, according to Corma's Okta pricing analysis (prices checked on 28 September 2026).

Before buying any user access management software, five questions separate tools that fit a mid-market estate from those that do not:

  • Coverage: what share of your applications will the tool see on day one, including those with no SSO or SCIM?
  • Execution: when a reviewer revokes access in an application without SCIM, who removes the account, and how is it confirmed?
  • Evidence: can you export review decisions, approval workflows and revocation dates in a format your auditor accepts?
  • Hosting: where is identity data stored, and does the vendor hold ISO/IEC 27001 certification?
  • Licensing: does governance depend on a higher tier of your identity provider, and is the price per user or per application?

Is Microsoft Entra ID Governance included in Microsoft 365 E5?

Not in full. According to Microsoft's Entra licensing documentation, checked in October 2026, Microsoft 365 E5 includes Microsoft Entra ID P2, which covers standard access reviews, entitlement management and Privileged Identity Management. Lifecycle Workflows, which automate joiner, mover and leaver tasks, and several advanced review features require a separate Microsoft Entra ID Governance license or the Microsoft Entra Suite.

Is a dedicated IGA tool worth it if only part of your apps is connected to the IdP?

Yes, when the unconnected part holds sensitive data or falls inside your audit scope. The question comes up often on IAM forums, phrased as whether a dedicated IGA system is worth it when only 20 to 30% of the application landscape sits behind the identity provider. A review of the federated part alone leaves the riskiest accounts out of the evidence.

APGAR, a 280-employee consulting firm running more than 80 SaaS tools, faced exactly this when it set out to strengthen its security posture: applications and AI tools used through the browser escaped monitoring, while access reviews for ISO 27001 relied on manual checks. Its IT Manager and CISO, Jean-Marie Drucot, sums up the result: "Corma helps me enormously with all aspects of application detection and automatic management."

For a vendor-by-vendor shortlist, see our comparison of the best IGA solutions for mid-market companies.

Where should you start? A first-quarter sequence

Start with the stock you already have, not with a policy document. The sequence below is the order we recommend for an IT team of one to five people, and each step produces evidence you can show.

  1. Build the inventory (weeks 1 to 3). Pull applications from the identity provider, expense data and browser discovery, then assign one owner per application. Without this step, every later review certifies an incomplete list. Corma's SaaS visibility and shadow IT detection builds this list automatically.
  2. Close the leaver gap (weeks 2 to 4). Compare the last twelve months of HR departures with accounts that are still active, and disable orphaned accounts. Then automate the flow: Skello, a 340-employee HR software company, has onboarded and offboarded more than 140 employees automatically with Corma's automated provisioning and onboarding.
  3. Review privileged access first (month 2). List admin accounts on the identity provider, cloud consoles, finance and HR tools, and enforce MFA on all of them, as NIS2 Article 21(2)(j) expects where appropriate.
  4. Run the first owner-led review on critical applications (months 2 to 3). One application at a time, with "revoke if unsure" as the default and every decision logged.
  5. Write down the cadence and the evidence (month 3). Set review frequencies per application tier and store the records. Your access control policy now describes what you actually do.

How Corma supports access governance for mid-market teams

Corma combines SaaS management, identity and access management and identity governance in one European platform built for mid-market companies. It sits on top of your identity provider rather than replacing it.

  • One record for every app, account and owner, federated, unfederated and shadow, built from native connectors to Google Workspace, Microsoft Entra ID, Okta and JumpCloud, from finance data and from the browser.
  • Action where no API exists. When announcing Corma's second consecutive inclusion in the Gartner Magic Quadrant for SaaS Management Platforms in June 2026, Héloïse Rozès explained that Corma's browser-based agents can act in applications that offer no API, and that IT Security and Compliance was Corma's highest-scored use case in the 2026 report.
  • Requests, reviews and joiner, mover, leaver changes in the same platform, with exportable evidence for ISO 27001, SOC 2 and NIS2 audits.
  • EU hosting and ISO/IEC 27001:2022 certification. Corma's servers and databases run in data centers inside the European Union, so identity data stays hosted in the EU.

See your own access governance gaps in one view. Book a Corma demo and we will map your federated, unfederated and shadow applications against the eight controls above.

FAQ

What is the difference between access governance and IGA?

Access governance is the discipline of deciding, reviewing and proving who should hold which access. Identity governance and administration (IGA) is the software category that implements it, adding provisioning and lifecycle automation to policy and access reviews.

Does access governance replace my identity provider?

No. The identity provider authenticates users and provisions the applications connected to it. Access governance sits on top of it: it checks that the resulting access is justified, covers applications the identity provider does not control, and keeps the evidence.

What are the main steps of user access management?

User access management follows five steps: request, approval, provisioning, periodic review and revocation. Access governance adds the policy that says who approves each step, and the records that prove each step happened.

Does NIS2 apply to a company with 50 employees?

It can. NIS2 applies to entities in the sectors of its Annexes I and II that qualify as medium-sized enterprises or larger, and a company with 50 or more employees is no longer a small enterprise under the EU definition. Some entities are covered regardless of size, so check your sector and your national transposition law.

Are spreadsheets enough for access reviews?

For a handful of applications, yes, if every decision is dated, attributed and applied in the target system. Spreadsheets break as the application count grows, because exports go stale and nobody can prove that a revoked access was actually removed.

What evidence does an auditor expect for access governance?

A dated register of access rights, records showing who reviewed which entitlement and what they decided, and proof that revocations were applied. For leavers, auditors usually compare HR exit dates with account deactivation dates.

Zluri Acquired by Infotech: What It Means and How to Switch
Company Updates
October 27, 2026

Zluri Acquired by Infotech: What It Means and How to Switch

Read Article
Joiner Mover Leaver: Automating the JML Process Across SaaS
Identity Access Management
November 17, 2026

Joiner Mover Leaver: Automating the JML Process Across SaaS

Read Article
Access Governance for Mid-Market: Model, Controls and Tooling
Identity Access Management
November 17, 2026

Access Governance for Mid-Market: Model, Controls and Tooling

Read Article

The new standard in license management

Ready to revolutionize your IT governance?

Isometric illustration of a calculator with black number keys and orange operation buttons on screen
Black circular icon with two white rounded rectangles resembling a simple ghost or face designOrange circular icon with two white vertical bars on the left sideDark circular icon with white pause symbol and dotted pattern