<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Evolveum | Open Source Identity Management &amp; Governance</title>
	<atom:link href="https://evolveum.com/feed/" rel="self" type="application/rss+xml" />
	<link>https://evolveum.com</link>
	<description>Face your security challenges with OSS state-of-the-art platform midPoint, a matchless combination of IdM and Identity Governance.</description>
	<lastBuildDate>Thu, 19 Nov 2026 16:03:10 +0000</lastBuildDate>
	<language>en-GB</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>MidPoint and Java4Shell: Action Needed</title>
		<link>https://evolveum.com/midpoint-and-java4shell-action-needed/</link>
					<comments>https://evolveum.com/midpoint-and-java4shell-action-needed/#comments</comments>
		
		<dc:creator><![CDATA[Evolveum]]></dc:creator>
		<pubDate>Thu, 19 Nov 2026 16:03:10 +0000</pubDate>
				<category><![CDATA[Other]]></category>
		<guid isPermaLink="false">https://evolveum.com/?p=16697</guid>

					<description><![CDATA[<p>Java4Shell (CVE-2026-114938) is a severe cybersecurity vulnerability in Java platform. As midPoint runs on Java platform, Java2Shell poses a major risk for midPoint deployments. Administrators of midPoint deployments are advised to update Java platform immediately. Java4Shell is a memory corruption flaw in Base64 decoder of Java platform. The flaw may allow attacker to remotely execute <a href="https://evolveum.com/midpoint-and-java4shell-action-needed/" rel="nofollow"><span class="sr-only">Read more about MidPoint and Java4Shell: Action Needed</span>[&#8230;]</a></p>
<p>The post <a rel="nofollow" href="https://evolveum.com/midpoint-and-java4shell-action-needed/">MidPoint and Java4Shell: Action Needed</a> appeared first on <a rel="nofollow" href="https://evolveum.com">Evolveum | Open Source Identity Management &amp; Governance</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><a href="https://calif.io/java4shell">Java4Shell</a> (<a href="https://nvd.nist.gov/vuln/detail/cve-2026-114938">CVE-2026-114938</a>) is a severe cybersecurity vulnerability in Java platform. As midPoint runs on Java platform, Java2Shell poses a major risk for midPoint deployments. Administrators of midPoint deployments are advised to update Java platform immediately. <!-- READMORE --></p>
<p><a href="https://calif.io/java4shell">Java4Shell</a> is a memory corruption flaw in Base64 decoder of Java platform. The flaw may allow attacker to remotely execute code or reveal data from memory under some circumstances. It is much more likely that the attacker can use the vulnerability to crash the application. This is not a vulnerability in midPoint code. However, midPoint deployments are affected. <b>All midPoint deployments running on vulnerable versions of Java platform are in severe risk.</b></p>
<p>The vulnerability is not easy to exploit, as exploit needs to be adapted for every application individually. Yet the exploit is far from being impossible or even unlikely. We are not aware of any exploits that would work for midPoint so far. However, it is just a question of time. Let us not risk anything and <b>update the Java platform immediately!</b></p>
<p>In case that you have installed Java platform (JDK or JRE) manually or in case that it comes from your OS distribution, have a look at security advisories of your java platform or operating system. If you have installed midPoint from Evolveum container images, update the images. If you are using images for midPoint 4.11.x or later, using floating tags such as <code>4.11.0</code> or <code>4.11-alpine-latest</code>, the images will be updated those containing patched Java platform when you _pull_ the images. Alpine and Ubuntu images are updated. Unfortunately, Rocky Linux images are not updated yet. Rocky Linux have not released patched images yet, and we decided not to wait any longer with this announcement. We will update Rocky Linux images as soon as the upstream incorporates the patches.</p>
<p>Users of midPoint 4.8 and 4.10 should explicitly update to the latest maintenance release (<code>4.8.14</code> and <code>4.10.5</code>), as for these versions the tags are not automatically updated to latest maintenance release. If you are using different tags, please refer to the <a href="https://docs.evolveum.com/midpoint/get-started/install/containers/container-image-naming/">container image naming conventions</a> for details. If you are not able to update your Java platform for any reason, you may use <code>XX:-UseBASE64Intrinsics</code> Java option as workaround. However, updating your Java platform immediately is the best course of action. Also bear in mind that continuously updating midPoint to the latest maintenance release is strongly recommended best practice.</p>
<p>Java4Shell is yet another hit in the cybersecurity storm that we are living through. The storm is unlikely to end anytime soon. Therefore, keep in mind that <i>any software which cannot be readily updated on a very short notice is an unacceptable security risk.</i> Make sure all your software is running on supported version, that you have process in place to quickly update it, and that the process works.</p>
<p>Brace yourself, the storm is raging. Update your software, and stay safe.</p>
<p>The post <a rel="nofollow" href="https://evolveum.com/midpoint-and-java4shell-action-needed/">MidPoint and Java4Shell: Action Needed</a> appeared first on <a rel="nofollow" href="https://evolveum.com">Evolveum | Open Source Identity Management &amp; Governance</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://evolveum.com/midpoint-and-java4shell-action-needed/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
		<item>
		<title>How MidPoint Simulations Helped Ensure a Smooth Go-Live For Belgium’s Pension Services</title>
		<link>https://evolveum.com/how-midpoint-simulations-helped-ensure-a-smooth-go-live/</link>
					<comments>https://evolveum.com/how-midpoint-simulations-helped-ensure-a-smooth-go-live/#respond</comments>
		
		<dc:creator><![CDATA[ACEN]]></dc:creator>
		<pubDate>Wed, 18 Nov 2026 08:25:39 +0000</pubDate>
				<category><![CDATA[Community]]></category>
		<guid isPermaLink="false">https://evolveum.com/?p=16614</guid>

					<description><![CDATA[<p>This article was written by our implementation partner, ACEN, as part of our MidPoint in Practice series, where partners share real-world implementation stories highlighting how they solve identity governance challenges with midPoint. About ACEN: ACEN is a top-notch provider of complete cyber security solutions in Belgium that ensures companies from various fields are protected against <a href="https://evolveum.com/how-midpoint-simulations-helped-ensure-a-smooth-go-live/" rel="nofollow"><span class="sr-only">Read more about How MidPoint Simulations Helped Ensure a Smooth Go-Live For Belgium’s Pension Services</span>[&#8230;]</a></p>
<p>The post <a rel="nofollow" href="https://evolveum.com/how-midpoint-simulations-helped-ensure-a-smooth-go-live/">How MidPoint Simulations Helped Ensure a Smooth Go-Live For Belgium’s Pension Services</a> appeared first on <a rel="nofollow" href="https://evolveum.com">Evolveum | Open Source Identity Management &amp; Governance</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><em>This article was written by our implementation partner, <a href="https://evolveum.com/partners/acen/">ACEN</a>, as part of our MidPoint in Practice series, where partners share real-world implementation stories highlighting how they solve identity governance challenges with <a href="https://evolveum.com/midpoint/" target="_blank" rel="noopener">midPoint</a>.</em></p>
<div style="background-color: #9dc2e6; padding: 20px 24px; border-radius: 8px; border: none; outline: none; box-shadow: none; width: 100%; font-family: 'Roboto', sans-serif, Arial; color: #ffffff; display: flex; align-items: center; gap: 20px; box-sizing: border-box; margin: 25px 0;">
<div style="display: flex; align-items: center; flex-shrink: 0;"><img style="width: 65px; height: 65px; border-radius: 50%; object-fit: contain; background: #ffffff; padding: 5px; box-sizing: border-box; border: none;" src="https://evolveum.com/wp-content/uploads/acen-logo.png" alt="ACEN logo" /></div>
<div style="width: 2px; background-color: #ffffff; opacity: 0.8; align-self: stretch; flex-shrink: 0;"></div>
<div style="text-align: left; display: flex; flex-direction: column; justify-content: center; gap: 8px; flex-grow: 1;">
<p style="margin: 0 !important; font-size: 16px !important; line-height: 1.4 !important; color: #ffffff !important;"><strong>About ACEN:</strong></p>
<p style="margin: 0 !important; font-size: 16px !important; line-height: 1.6 !important; color: #ffffff !important;"><a href="https://evolveum.com/partners/acen/">ACEN</a> is a top-notch provider of complete cyber security solutions in Belgium that ensures companies from various fields are protected against any possible threats coming from the Internet. Its group of professionals has gained vast experience and knowledge over time and therefore always provides individualized answers to the challenges faced by each customer. ACEN continuously keeps itself aligned with all emerging dangers and technologies so it can prepare customers for potential security breaches. ACEN prides itself on being easily approachable. The company listens attentively and responds promptly, all in addition to offering unprecedented support services. All of this is what ACEN refers to as its personalized cybersecurity approach.</p>
</div>
</div>
<p>As the years pass, digital landscapes continue to grow through a mix of manual account management and homegrown scripted automation. Over time, these environments can reach a point where nobody is entirely sure what&#8217;s still active, what&#8217;s leftover, and what quietly stopped working two reorganizations ago.</p>
<p>That was exactly the situation one of ACEN&#8217;s customers faced: <a href="https://www.sfpd.fgov.be/en" target="_blank" rel="noopener">SFPD</a> (Belgium’s Federal Pension Service), a mid-sized organization on the verge of migration. Their objective was to migrate identity lifecycle management and provisioning onto midPoint, with AD (Active Directory) as one of the primary connected systems. But they lacked the insight and visibility needed to move forward with confidence.</p>
<p>As with almost every IGA project, their lower development, test, and acceptance environments ran on anonymized copies of production data. When it comes to privacy and compliance, this is good practice. But it comes with a well-known downside: anonymization tends to normalize the data. The mess that exists in real production tends to be misrepresented in test environments. Names get replaced, attributes get scrubbed or regenerated, and you end up with a set of data that&#8217;s &#8220;too clean&#8221;. Stale accounts, inconsistent attribute values, orphaned objects, and half-finished migrations don&#8217;t exist&#8230; except they do.</p>
<h2>The challenge: Catching what anonymized test data hides</h2>
<p>How could the team validate a go-live with issues that were anonymized away? The only available test data couldn&#8217;t test production-scale, production-quality data issues in a realistic way.</p>
<p>Going live without testing wasn&#8217;t a risk anyone was willing to take. ACEN couldn&#8217;t trust that what worked in acceptance would work identically in production.</p>
<p>Provisioning and synchronization logic may look correct against clean test data. That&#8217;s in no way a guarantee it won&#8217;t behave completely differently once meeting real-world entropy:</p>
<ol>
<li>Attributes are assumed to be unique when they aren&#8217;t.</li>
<li>Accounts exist in AD but were never properly linked to an HR source.</li>
<li>Correlation rules match either too eagerly or not at all.</li>
<li>&#8230;</li>
</ol>
<p>These are the typical kinds of problems you run into in an IGA rollout. Insufficient testing can therefore turn a go-live into an incident.</p>
<h2>How midPoint simulations helped the project’s go-live</h2>
<p>Luckily, there was an alternative to unleashing the synchronization and provisioning tasks in live production. ACEN was able to run them in midPoint&#8217;s simulation mode. MidPoint processed the real, unmodified production data without them needing to touch it and without needing to alter anonymization safeguards in the lower environments.</p>
<p>ACEN ran <a href="https://docs.evolveum.com/midpoint/architecture/concepts/simulation/">simulations</a> across the full scope of accounts in AD, HR data, and the target midPoint repository. This allowed them to preview computed correlations, evaluate role assignments, and see exactly what impact these changes would have. All without ever writing anything back to the connected systems in production. Before pushing anything, ACEN evaluated the resulting data reports with the customer. Together they made a well-informed decision on when the rollout was ready to go.</p>
<p>The simulation surfaced two categories of findings that no amount of testing in acceptance could have caught:</p>
<p><strong>Data quality issues that only existed in production.</strong> The team quickly came across inconsistent attribute formatting and a handful of accounts with correlation-relevant attributes that collided. These kinds of relational issues would never have been produced by anonymized test data. The same was true for certain edge cases in name and organizational data that the mapping logic had not accounted for.</p>
<p><strong>In-scope AD accounts that should have been automatically deprovisioned.</strong> The customer had built scripting years earlier, specifically to deprovision leavers. Quietly in the background, the scripts had been failing, skipping edge cases. This had been going on for some time and resulted in the accumulation of a reasonable set of outdated accounts, undetected. Nobody noticed because there weren&#8217;t any tools in place to monitor expected changes. The scripts ran, no errors came up, and nobody looked closer.</p>
<p>ACEN approached every finding as a decision point, not as something to fix reflexively in code. For genuine data issues, the source data was cleaned up before go-live. For the AD leftovers, a review and cleanup process was initiated. This closed the gap that had existed in silence for all that time.</p>
<p>Then came the edge cases. Not everything that surfaced was a data quality problem. And also, not everything called for a permanent fix. Some issues were temporary, and certain accounts were held back until resolved. Others needed to stay untouched indefinitely because of their nature &#8211; think of VIP accounts or system-critical logins.</p>
<p>Luckily, midPoint&#8217;s marking feature allowed the team to flag them directly. A &#8220;whatever you do, don&#8217;t touch this&#8221; label attached to the object, which midPoint respects during processing. This feature meant ACEN didn&#8217;t need to special-case their synchronization and correlation logic around these edge cases. Marks came off once a data issue was cleared and stayed on the ones that needed permanent protection. That kept the underlying automation configuration untouched.</p>
<h2>The result: A seamless go-live</h2>
<p>When the time came to go live, the event was uneventful, as designed.</p>
<p>A number of small issues came up, but only the kind you expect and can resolve within hours. Nothing of scale or severity that would break anything critical — what could have occurred had the team deployed directly to production.</p>
<p>Simulations caught all of that: the data issues, stale AD accounts, and edge cases had all been addressed beforehand. MidPoint&#8217;s Simulations gave the team visibility into them ahead of time, rather than having to solve them post-go-live as production incidents.</p>
<p>The value of Simulations wasn&#8217;t that it eliminated every possible issue. It changed when those issues were discovered: before go-live rather than during it.</p>
<h2>Key lessons learned</h2>
<p>This project reinforced ACEN&#8217;s belief that anonymized test data only provides half the story and insight. While it protects privacy, it also hides real problems until the day of go-live – unless a step is built in that provides a safe look into production before anything is deployed.</p>
<p>Secondly, the team learned the difference between automations running without errors and scripts that actually work. Metrics don&#8217;t always give the full picture. The AD deprovisioning had &#8220;run fine&#8221; for years until Simulations gave everyone a lens they&#8217;d never had before.</p>
<p>ACEN&#8217;s advice to customers is simple: a successful IGA go-live is one where nobody noticed it happened. The absence of drama on launch isn&#8217;t luck. It&#8217;s the payoff of everything that was de-risked beforehand.</p>
<p>In this project, midPoint&#8217;s Simulations feature was the single biggest contributor to making that quiet, uneventful go-live possible.</p>
<h2>Frequently Asked Questions</h2>
<details style="border-bottom: 1px solid #e0e0e0; padding: 16px 0; cursor: pointer;">
<summary style="font-size: 18px; font-weight: bold; color: #1b365d; list-style: none; display: flex; align-items: baseline; gap: 10px;"><span style="color: #9dc2e6; font-size: 20px; font-weight: bold; line-height: 1; display: inline-block;">+</span> What is Simulations in midPoint?</summary>
<div style="margin-top: 12px; padding-left: 24px; font-size: 16px; line-height: 1.6; color: #4a4a4a;">
<p style="margin: 0;">MidPoint&#8217;s Simulations is a feature that allows you to preview the outcome of identity management changes before they are applied. It allows teams to evaluate how midPoint would process objects, assignments, correlations, and other changes without committing those changes to the affected systems. Simulations are useful for validating configuration and understanding its potential impact before execution.</p>
</div>
</details>
<details style="border-bottom: 1px solid #e0e0e0; padding: 16px 0; cursor: pointer;">
<summary style="font-size: 18px; font-weight: bold; color: #1b365d; list-style: none; display: flex; align-items: baseline; gap: 10px;"><span style="color: #9dc2e6; font-size: 20px; font-weight: bold; line-height: 1; display: inline-block;">+</span> How does Simulations work in midPoint?</summary>
<div style="margin-top: 12px; padding-left: 24px; font-size: 16px; line-height: 1.6; color: #4a4a4a;">
<p style="margin: 0;">The Simulations feature processes identity data using midPoint&#8217;s normal processing logic, but records the resulting operations as simulation results instead of executing them as persistent changes. Teams can then inspect the results to understand what midPoint would change, which makes simulations useful for testing proposed changes and configurations in a controlled way.</p>
</div>
</details>
<details style="border-bottom: 1px solid #e0e0e0; padding: 16px 0; cursor: pointer;">
<summary style="font-size: 18px; font-weight: bold; color: #1b365d; list-style: none; display: flex; align-items: baseline; gap: 10px;"><span style="color: #9dc2e6; font-size: 20px; font-weight: bold; line-height: 1; display: inline-block;">+</span> What activities can be run in midPoint&#8217;s simulation mode?</summary>
<div style="margin-top: 12px; padding-left: 24px; font-size: 16px; line-height: 1.6; color: #4a4a4a;">
<p style="margin: 0;">MidPoint&#8217;s Simulations feature currently supports synchronization activities such as <strong>import, reconciliation, and live synchronization</strong>, as well as <strong>recomputation, iterative and non-iterative scripting, and change execution</strong>. These activities can calculate the changes that would normally be made and record them as simulation results instead of applying persistent changes.</p>
</div>
</details>
<p>.</p>
<div style="background-color: #9dc2e6; padding: 24px 30px; border-radius: 8px; border: none; outline: none; box-shadow: none; width: 100%; font-family: 'Roboto', sans-serif, Arial; color: #ffffff; text-align: center; box-sizing: border-box; margin: 35px 0 25px;">
<p style="margin: 0 0 8px 0 !important; font-size: 20px !important; line-height: 1.4 !important; color: #ffffff !important;"><strong>Interested in working with ACEN?</strong></p>
<p style="margin: 0 0 18px 0 !important; font-size: 16px !important; line-height: 1.6 !important; color: #ffffff !important;">Get in touch with ACEN to discuss your identity management needs.</p>
<p><a style="display: inline-block; background-color: #ffffff; color: #1b365d; padding: 10px 20px; border-radius: 5px; text-decoration: none; font-weight: bold; font-size: 16px;" href="https://evolveum.com/partners/acen/" target="_blank" rel="noopener">Contact ACEN</a></p>
</div>
<p>The post <a rel="nofollow" href="https://evolveum.com/how-midpoint-simulations-helped-ensure-a-smooth-go-live/">How MidPoint Simulations Helped Ensure a Smooth Go-Live For Belgium’s Pension Services</a> appeared first on <a rel="nofollow" href="https://evolveum.com">Evolveum | Open Source Identity Management &amp; Governance</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://evolveum.com/how-midpoint-simulations-helped-ensure-a-smooth-go-live/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>MidPoint 4.11: Verified by Penetration Testing</title>
		<link>https://evolveum.com/cra-midpoint-pentest/</link>
					<comments>https://evolveum.com/cra-midpoint-pentest/#respond</comments>
		
		<dc:creator><![CDATA[Martin Spanik]]></dc:creator>
		<pubDate>Fri, 30 Oct 2026 15:24:06 +0000</pubDate>
				<category><![CDATA[Evolveum's Identity Management and Governance Blog]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>
		<guid isPermaLink="false">https://evolveum.com/?p=16464</guid>

					<description><![CDATA[<p>Security is an ongoing part of midPoint development. As part of our work to strengthen midPoint and prepare for the EU Cyber Resilience Act (CRA), we commissioned an independent penetration test of midPoint 4.11. The work was supported by the European Union and Slovakia&#8217;s National Security Authority (NBÚ) under the TestCert-SK MidPoint &#8211; CRA compliance <a href="https://evolveum.com/cra-midpoint-pentest/" rel="nofollow"><span class="sr-only">Read more about MidPoint 4.11: Verified by Penetration Testing</span>[&#8230;]</a></p>
<p>The post <a rel="nofollow" href="https://evolveum.com/cra-midpoint-pentest/">MidPoint 4.11: Verified by Penetration Testing</a> appeared first on <a rel="nofollow" href="https://evolveum.com">Evolveum | Open Source Identity Management &amp; Governance</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Security is an ongoing part of midPoint development. As part of our work to <a href="https://evolveum.com/midpoint-and-cra/"><strong>strengthen midPoint</strong></a> and prepare for the EU Cyber Resilience Act (CRA), we commissioned an independent penetration test of midPoint 4.11.</p>
<p>The work was supported by the European Union and <a href="https://www.nbu.gov.sk/">Slovakia&#8217;s National Security Authority (NBÚ)</a> under the TestCert-SK MidPoint &#8211; CRA compliance enhancements project (101127837). The project was recently completed, and here are the the highlights of what we found.</p>
<h2>Improving midPoint&#8217;s security</h2>
<p>MidPoint is highly customizable, so its security depends, in part, on how it is configured. We want organizations to be able to build a secure environment using the configurations described in our documentation, even when they are just getting started with midPoint itself.</p>
<p>The penetration test examined the potential impact of access by an unauthenticated user, including deployments that allow self-registration. It focused on configurations documented by Evolveum and covered both midPoint&#8217;s flexible authentication and authentication through Keycloak. The tester also assessed the application against common web and API security risks, as well as business logic, identity fraud, and data leakage scenarios.</p>
<h2>What did the test find?</h2>
<p>An external pentester performed the manual penetration test during August and September 2026, in a test environment.</p>
<p>The assessment began during the final stages of midPoint 4.11 development, and the results were verified against midPoint 4.11-RC2 shortly before the 4.11.0 release.</p>
<p>Although no major vulnerabilities were found, we resolved minor findings and improved documentation to deliver software preconfigured for safer defaults and documentation better suited for your use cases. One example of documentation updates is the option to <a href="https://docs.evolveum.com/midpoint/reference/support-4.11/security/credentials/password-policy/disallow-specific-passwords/"><strong>disallow specific values in passwords</strong></a>.</p>
<p>The report described midPoint&#8217;s overall security posture as robust and found no further vulnerabilities that could immediately be used to jeopardize the application&#8217;s security. We addressed the findings and used the assessment to improve documentation and examples. We also refined details and parameters of the new <a href="https://docs.evolveum.com/midpoint/reference/support-4.11/security/authentication/flexible-authentication/modules/totp/"><strong>TOTP authentication module</strong></a>, introduced in midPoint 4.11.</p>
<h2>Security work continues</h2>
<p>The penetration testing of midPoint is one part of our broader effort to make midPoint more secure and easier to configure and use. From midPoint 4.11 onward, penetration testing will be a standard part of the product development cycle. The documentation and examples are being improved continually.</p>
<p>MidPoint 4.11.0 has now been released and the development of 4.12 has started. It will bring further improvements, including work aligned with the CRA&#8217;s requirements, to help our customers configure, deploy, and use midPoint securely.</p>
<div style="display: flex; justify-content: center; align-items: center; flex-wrap: wrap; gap: 40px; margin-bottom: 20px;">
<div style="display: flex; align-items: center;"><a style="display: flex; align-items: center;" href="https://ec.europa.eu/" target="_blank" rel="noopener"><br />
<img style="height: 60px; width: auto; object-fit: contain; display: block;" src="https://evolveum.com/wp-content/uploads/funded-by-the-eu-logo.jpg" alt="Funded by the European Union" /><br />
</a></div>
<div class="vertical-separator" style="width: 1px; height: 100px; background-color: #2a2768;"></div>
<div style="display: flex; align-items: center;"><a style="display: flex; align-items: center;" href="https://www.nbu.gov.sk/" target="_blank" rel="noopener"><br />
<img style="height: 60px; width: auto; object-fit: contain; display: block;" src="https://evolveum.com/wp-content/uploads/nbu-sk-logo.png" alt="Národný bezpečnostný úrad" /><br />
</a></div>
<div class="vertical-separator" style="width: 1px; height: 100px; background-color: #2a2768;"></div>
<div style="display: flex; align-items: center;"><a style="display: flex; align-items: center;" href="https://cybersecurity-centre.europa.eu/" target="_blank" rel="noopener"><br />
<img style="height: 60px; width: auto; object-fit: contain; display: block;" src="https://evolveum.com/wp-content/uploads/eccc-logo.png" alt="European Cybersecurity Competence Centre and Network" /> </a></div>
</div>
<hr style="height: 1px; background-color: #333333; border: none; margin: 40px 0;" />
<p>Bezpečnosť je neoddeliteľnou súčasťou priebežného vývoja midPointu. V rámci našej snahy posilňovať bezpečnosť midPointu a pripraviť ho na európsky Akt o kybernetickej odolnosti (Cyber Resilience Act, CRA) sme zadali nezávislý penetračný test midPointu 4.11.</p>
<p>Prácu podporili Európska únia a Národný bezpečnostný úrad Slovenskej republiky (NBÚ) v rámci projektu TestCert-SK – <b>MidPoint – CRA compliance enhancements project</b> (101127837). Projekt sa práve v týchto dňoch skončil.</p>
<h2>Zvyšovanie bezpečnosti midPointu</h2>
<p>MidPoint ponúka rozsiahle možnosti prispôsobenia, preto jeho bezpečnosť čiastočne závisí od spôsobu konfigurácie. Chceme, aby organizácie dokázali vytvoriť bezpečné prostredie pomocou konfigurácií opísaných v našej dokumentácii, aj keď s midPointom ešte len začínajú.</p>
<p>Penetračný test skúmal možný vplyv prístupu neovereného používateľa vrátane nasadení, ktoré umožňujú samoobslužnú registráciu. Zameral sa na konfigurácie zdokumentované spoločnosťou Evolveum a zahŕňal flexibilnú autentifikáciu midPointu aj autentifikáciu prostredníctvom Keycloaku. Tester posudzoval aplikáciu aj z pohľadu bežných rizík webovej a API bezpečnosti, obchodnej logiky, podvodného zneužitia identity a úniku údajov.</p>
<h2>Čo test odhalil?</h2>
<p>Externý penetračný tester vykonal manuálny penetračný test v testovacom prostredí počas augusta a septembra 2026.</p>
<p>Posudzovanie sa začalo v záverečnej fáze vývoja midPointu 4.11. Výsledky sa overili vo verzii midPoint 4.11-RC2 krátko pred vydaním verzie 4.11.0.</p>
<p>Test neodhalil žiadne závažné zraniteľnosti. Zistené nedostatky s nižšou závažnosťou sme odstránili a vylepšili sme dokumentáciu, aby softvér používal bezpečnejšie predvolené nastavenia a dokumentácia lepšie zodpovedala vašim prípadom použitia. Jedným z príkladov aktualizácie dokumentácie je možnosť zakázať konkrétne hodnoty v heslách.</p>
<p>V správe sa celkový stav bezpečnosti midPointu hodnotí ako robustný. Neboli zistené ďalšie zraniteľnosti, ktoré by bolo možné okamžite zneužiť na ohrozenie bezpečnosti aplikácie. Zistenia sme vyriešili a výsledky testu využili na vylepšenie dokumentácie a príkladov. Spresnili sme aj podrobnosti a parametre nového autentifikačného modulu TOTP, ktorý bol predstavený v midPointe 4.11.</p>
<h2>Práca na bezpečnosti pokračuje</h2>
<p>Penetračný test midPointu je jednou zo súčastí našej širšej snahy zvýšiť jeho bezpečnosť a zjednodušiť jeho konfiguráciu a používanie. Od verzie midPoint 4.11 je penetračné testovanie štandardnou súčasťou vývojového cyklu produktu. Dokumentáciu a príklady priebežne vylepšujeme.</p>
<p>MidPoint 4.11.0 je už vydaný a vývoj verzie 4.12 sa začal. Prinesie ďalšie vylepšenia vrátane práce zameranej na požiadavky CRA, aby sme zákazníkom pomohli midPoint bezpečne konfigurovať, nasadzovať a používať.</p>
<p>The post <a rel="nofollow" href="https://evolveum.com/cra-midpoint-pentest/">MidPoint 4.11: Verified by Penetration Testing</a> appeared first on <a rel="nofollow" href="https://evolveum.com">Evolveum | Open Source Identity Management &amp; Governance</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://evolveum.com/cra-midpoint-pentest/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>MidPoint is Not Vulnerable to PHP2Shell</title>
		<link>https://evolveum.com/midpoint-is-not-vulnerable-to-php2shell/</link>
					<comments>https://evolveum.com/midpoint-is-not-vulnerable-to-php2shell/#respond</comments>
		
		<dc:creator><![CDATA[Radovan Semancik]]></dc:creator>
		<pubDate>Thu, 22 Oct 2026 16:10:11 +0000</pubDate>
				<category><![CDATA[Evolveum's Identity Management and Governance Blog]]></category>
		<category><![CDATA[News]]></category>
		<guid isPermaLink="false">https://evolveum.com/?p=16375</guid>

					<description><![CDATA[<p>PHP2Shell is a critical cybersecurity problem for PHP applications. As midPoint is implemented in Java and not PHP, midPoint is not vulnerable to PHP2Shell. However, impact of PHP2Shell is so severe that it is worth discussing. Once a vulnerability gets its own name, it is very obvious that the impact is serious. However, this is <a href="https://evolveum.com/midpoint-is-not-vulnerable-to-php2shell/" rel="nofollow"><span class="sr-only">Read more about MidPoint is Not Vulnerable to PHP2Shell</span>[&#8230;]</a></p>
<p>The post <a rel="nofollow" href="https://evolveum.com/midpoint-is-not-vulnerable-to-php2shell/">MidPoint is Not Vulnerable to PHP2Shell</a> appeared first on <a rel="nofollow" href="https://evolveum.com">Evolveum | Open Source Identity Management &amp; Governance</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>PHP2Shell is a critical cybersecurity problem for PHP applications. As midPoint is implemented in Java and not PHP, midPoint is not vulnerable to PHP2Shell. However, impact of PHP2Shell is so severe that it is worth discussing.</p>
<p>Once a vulnerability gets its own name, it is very obvious that the impact is serious. However, this is perhaps quite an understatement in case of PHP2Shell. PHP2Shell is a set of two vulnerabilities (CVE-2026-109618 and CVE-2026-109619) allowing unauthenticated attackers to remotely execute arbitrary code on servers that use PHP for serving web pages. This is pretty much as bad as it gets. However, it is still not the whole picture of PHP2Shell. As this vulnerability was hidden in PHP codebase for years, pretty much every PHP version currently in use is vulnerable. PHP is an old language, it was proclaimed to be dead several times already. However, it is still very popular. This means that <i>almost every organization</i> connected to the Internet is affected by PHP2Shell in one way or another.</p>
<p>Naturally, Evolveum is affected too. Our company web page is running on PHP as well as several other applications. However, <b>midPoint itself is not affected</b> at all. MidPoint is written primarily in Java, using JavaScript in user interface, and Python which is used for supporting services. There is no PHP in midPoint. Even our PHP applications are not directly involved in midPoint, its development, build and testing. <b>We are sure that midPoint is safe from PHP2Shell</b>.</p>
<p>We have been very busy since the very moment we have learned about PHP2Shell, patching and updating, testing, checking and re-checking. PHP2Shell is such a serious threat that some follow-up work is still ongoing, and will be ongoing for some time. The echoes of PHP2Shell will be reverberating through the Internet for a long time.</p>
<p>This is a painful lesson to all of us, even though it teaches us what we all were supposed to know already: <i>Any software which cannot be readily updated on a very short notice is an unacceptable security risk.</i> It always was, but it just got a lot worse. Make sure all your software is running on supported version, that you have process in place to quickly update it, and that the process works. This is still important if you are using software as a service (SaaS) &#8211; perhaps even doubly so in such situation as SaaS providers are prime targets for attackers. Make sure your provider have appropriate mechanisms in place.</p>
<p>PHP2Shell is not an isolated problem. Contemporary software is a huge cauldron of code, libraries, platforms, dependencies, tools, and devices. More severe problems are hiding in the dark corners of the software labyrinth, waiting to be exploited. Brace yourself, and have your incident response process ready. It will be needed. Again and again.</p>
<p>The post <a rel="nofollow" href="https://evolveum.com/midpoint-is-not-vulnerable-to-php2shell/">MidPoint is Not Vulnerable to PHP2Shell</a> appeared first on <a rel="nofollow" href="https://evolveum.com">Evolveum | Open Source Identity Management &amp; Governance</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://evolveum.com/midpoint-is-not-vulnerable-to-php2shell/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Introducing MidPoint 4.11: AI-Assisted Onboarding, Stronger Security, and More</title>
		<link>https://evolveum.com/introducing-midpoint-4-11/</link>
					<comments>https://evolveum.com/introducing-midpoint-4-11/#respond</comments>
		
		<dc:creator><![CDATA[Evolveum]]></dc:creator>
		<pubDate>Thu, 22 Oct 2026 08:48:35 +0000</pubDate>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[News]]></category>
		<guid isPermaLink="false">https://evolveum.com/?p=16294</guid>

					<description><![CDATA[<p>Application onboarding is a core part of identity management, but it can also be one of the most time consuming. With midPoint 4.11, we’re making it easier with midPilot, an AI onboarding assistant, stronger security capabilities, built-in support for ITSM integrations, and a new community-driven MidPoint Integration Catalog to help you connect applications faster. And <a href="https://evolveum.com/introducing-midpoint-4-11/" rel="nofollow"><span class="sr-only">Read more about Introducing MidPoint 4.11: AI-Assisted Onboarding, Stronger Security, and More</span>[&#8230;]</a></p>
<p>The post <a rel="nofollow" href="https://evolveum.com/introducing-midpoint-4-11/">Introducing MidPoint 4.11: AI-Assisted Onboarding, Stronger Security, and More</a> appeared first on <a rel="nofollow" href="https://evolveum.com">Evolveum | Open Source Identity Management &amp; Governance</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Application onboarding is a core part of identity management, but it can also be one of the most time consuming. With midPoint 4.11, we’re making it easier with <a href="https://evolveum.com/ai-powered-iga/">midPilot</a>, an AI onboarding assistant, stronger security capabilities, built-in support for ITSM integrations, and a new community-driven MidPoint Integration Catalog to help you connect applications faster.</p>
<p>And that’s just the beginning. Let’s take a closer look at what’s new in midPoint 4.11.</p>
<h2>Rapid Application Onboarding with MidPilot</h2>
<p>MidPoint 4.11 introduces new AI-assisted features that help accelerate application onboarding, from developing a connector to configuring the resource.</p>
<h3>MidPilot Connector Generator</h3>
<p>Every integration starts with a way to connect the application. If you don’t find a suitable connector in our new MidPoint Integration Catalog, you can develop it directly in midPoint using our low-code framework with midPilot’s AI assistance and step-by-step guidance through the user interface. Each step is easy to understand, and midPoint even lets you test the functionality simply by clicking a button.</p>
<p style="text-align: center;"><iframe loading="lazy" title="MidPilot Connector Generator" src="https://www.youtube.com/embed/Te22v6YlzDA" width="660" height="365" frameborder="0" allowfullscreen="allowfullscreen"><span data-mce-type="bookmark" style="display: inline-block; width: 0px; overflow: hidden; line-height: 0;" class="mce_SELRES_start">﻿</span><span data-mce-type="bookmark" style="display: inline-block; width: 0px; overflow: hidden; line-height: 0;" class="mce_SELRES_start">﻿</span></iframe></p>
<h3>MidPilot Smart Recommendations</h3>
<p>It doesn’t end with the connector. Once you have it installed, you need to configure the resource’s mappings, correlations, and associations. This can be quite time-consuming for users new to midPoint, and we address this concern with midPilot – with a click of a button you can generate suggestions for all those settings.</p>
<p>You remain in control of what information is shared with the LLM. For each suggestion, you can choose which data to provide, including real schemas and portions of actual data when you want more relevant results. You can also connect midPilot to your own in-house LLM. MidPilot provides guidance, but it never changes your configuration without your explicit confirmation.</p>
<p style="text-align: center;"><iframe loading="lazy" title="Smart Recommendations with MidPilot" src="https://www.youtube.com/embed/WID8BVwmdJ8" width="660" height="365" frameborder="0" allowfullscreen="allowfullscreen"><span data-mce-type="bookmark" style="display: inline-block; width: 0px; overflow: hidden; line-height: 0;" class="mce_SELRES_start">﻿</span></iframe></p>
<h2>ITSM Ticketing for Manual Resources</h2>
<p>Manual resources rely on tickets to track the progress of provisioning operations that are executed manually by human operators. By default, these were managed internally by midPoint, and system administrators handled them in the midPoint GUI. With midPoint 4.11, we introduce “manual connectors”, allowing the provisioning tickets to be created in your favorite ITSM system and handled there.</p>
<p style="text-align: center;"><iframe loading="lazy" title="ITSM ticketing for manual resources" src="https://www.youtube.com/embed/ZCu2ouTMOlo" width="660" height="365" frameborder="0" allowfullscreen="allowfullscreen"></iframe></p>
<h2>MidPoint Integration Catalog</h2>
<p>The MidPoint Integration Catalog is the one place where you can find all the information needed to onboard a new application to midPoint. It was designed to be a community-driven hub where you can discover connectors, how-to guides, sample files, configuration snippets, tutorials, and other resources that help you connect applications and configure them in midPoint.</p>
<p style="text-align: center;"><iframe loading="lazy" title="Integration Catalog" src="https://www.youtube.com/embed/iBmSrBbN-oQ" width="660" height="365" frameborder="0" allowfullscreen="allowfullscreen"></iframe></p>
<h2>Security Improvements</h2>
<h3>Safe Scripting Language – MidPoint Expression Language (MEL)</h3>
<p>The introduction of the MidPoint Expression Language (MEL) is a major step towards securing midPoint by design. Our vision is to provide a strictly controlled, safe alternative to existing scripting languages. This allows administrators to write necessary expressions while keeping the core system completely isolated from malicious or accidental exploits, significantly minimizing security risks.</p>
<h3>TOTP: Two-Factor Authentication for MidPoint Itself</h3>
<p>We added a new module for multifactor authentication (MFA) in midPoint 4.11, specifically the Time-based One-Time Password (TOTP) module. This allows administrators to strengthen the protection of midPoint user accounts by requiring an additional authentication factor. As MFA becomes an increasingly important security measure for critical systems, this provides another way to protect access to midPoint itself, even in deployments where MFA is not implemented on the access management level.</p>
<p style="text-align: center;"><iframe loading="lazy" title="TOTP verification" src="https://www.youtube.com/embed/bkzwwVSPv2o" width="660" height="365" frameborder="0" allowfullscreen="allowfullscreen"><span data-mce-type="bookmark" style="display: inline-block; width: 0px; overflow: hidden; line-height: 0;" class="mce_SELRES_start">﻿</span><span data-mce-type="bookmark" style="display: inline-block; width: 0px; overflow: hidden; line-height: 0;" class="mce_SELRES_start">﻿</span></iframe></p>
<h2>MidPoint Studio</h2>
<p>With the midPoint 4.11 release, we’re introducing an updated MidPoint Studio plugin for IntelliJ IDEA with AI-assisted workflows. The plugin contains specific actions for object type suggestions, correlation rule suggestions, mapping suggestions, and association suggestions, together with shared infrastructure for launching these workflows through dialogs, wizards, and a dedicated smart-suggestion tool window.</p>
<p style="text-align: center; margin: 25px 0;"><img style="display: block; width: 100%; max-width: 660px; height: auto; margin: 0 auto;" src="https://evolveum.com/wp-content/uploads/connector-generator-creation.gif" alt="MidPoint Studio AI-assisted workflows" /></p>
<p><!-- Try midPoint 4.11 CTA --></p>
<div style="background-color: #9dc2e6; padding: 20px 24px; border-radius: 8px; border: none; outline: none; box-shadow: none; width: 100%; font-family: 'Roboto', sans-serif, Arial; color: #ffffff; display: flex; align-items: center; gap: 20px; box-sizing: border-box; margin: 25px 0;">
<div style="display: flex; align-items: center; flex-shrink: 0;"><img style="width: 65px; height: 65px; border-radius: 50%; object-fit: cover; background: #ffffff; padding: 5px; box-sizing: border-box; border: none;" src="https://evolveum.com/wp-content/uploads/midpoint-circle-logo.png" alt="midPoint logo" /></div>
<div style="width: 2px; background-color: #ffffff; opacity: 0.8; align-self: stretch; flex-shrink: 0;"></div>
<div style="text-align: left; display: flex; flex-direction: column; justify-content: center; gap: 8px; flex-grow: 1;">
<p style="margin: 0 !important; font-size: 20px !important; line-height: 1.4 !important; color: #ffffff !important; font-weight: bold;">Try MidPoint 4.11 Today</p>
<p style="margin: 0 !important; font-size: 16px !important; line-height: 1.5 !important; color: #ffffff !important;">MidPoint 4.11 is available now! Alongside the new features and improvements, the release includes bug fixes, so we recommend upgrading to the latest version.</p>
<p style="margin: 8px 0 0 0 !important;"><a style="display: inline-block; background-color: #dceaf7; color: #24527a; text-decoration: none; padding: 10px 22px; border-radius: 6px; font-size: 16px; font-weight: 600;" href="https://evolveum.com/midpoint/" target="_blank" rel="noopener">Try midPoint</a></p>
</div>
</div>
<h2>And More</h2>
<p>MidPoint 4.11 also brings a host of smaller improvements, including:</p>
<ul>
<li style="list-style-type: none;">
<ul>
<li><strong>Accessibility improvements</strong> – MidPoint is easier to use for everyone, and we are proud to announce our ongoing <a href="https://docs.evolveum.com/midpoint/compliance/wcag/" target="_blank" rel="noopener">full compliance</a> with the WCAG 2.2 Level AA.</li>
<li><strong>Focus-based policies for task activity</strong> – Focus-based policies can now be configured and evaluated per activity. Read more <a href="https://docs.evolveum.com/midpoint/reference/master/tasks/focus-policies-in-activities/" target="_blank" rel="noopener">here</a>.</li>
<li><strong>Multi-tab browser support</strong> – Improves the use of multiple tabs or windows in the web browser while maintaining a consistent experience across all of them.</li>
</ul>
</li>
</ul>
<h2>Ready to explore what’s new?</h2>
<ul>
<li>Read the full <a href="https://docs.evolveum.com/midpoint/release/" target="_blank" rel="noopener">release notes</a>.</li>
<li>Have questions or need help with an advanced use case? <a href="https://evolveum.com/about-us/contact-us/" target="_blank" rel="noopener">Contact us</a> — we’d love to hear from you.</li>
</ul>
<p>The post <a rel="nofollow" href="https://evolveum.com/introducing-midpoint-4-11/">Introducing MidPoint 4.11: AI-Assisted Onboarding, Stronger Security, and More</a> appeared first on <a rel="nofollow" href="https://evolveum.com">Evolveum | Open Source Identity Management &amp; Governance</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://evolveum.com/introducing-midpoint-4-11/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Taming the Chaos: Managing Multiple Source Systems and Identity Correlation in Higher Education</title>
		<link>https://evolveum.com/managing-multiple-source-systems-and-identity-correlation-in-he/</link>
					<comments>https://evolveum.com/managing-multiple-source-systems-and-identity-correlation-in-he/#respond</comments>
		
		<dc:creator><![CDATA[Unicon]]></dc:creator>
		<pubDate>Wed, 21 Oct 2026 06:18:38 +0000</pubDate>
				<category><![CDATA[Community]]></category>
		<guid isPermaLink="false">https://evolveum.com/?p=16276</guid>

					<description><![CDATA[<p>This article was written by our Gold implementation partner, Unicon Inc., as part of our MidPoint in Practice series, where partners share real-world implementation stories highlighting how they solve identity governance challenges with midPoint. About Unicon, Inc.: Unicon, Inc. is a leading provider of IT consulting, services, and support for education technology and works with <a href="https://evolveum.com/managing-multiple-source-systems-and-identity-correlation-in-he/" rel="nofollow"><span class="sr-only">Read more about Taming the Chaos: Managing Multiple Source Systems and Identity Correlation in Higher Education</span>[&#8230;]</a></p>
<p>The post <a rel="nofollow" href="https://evolveum.com/managing-multiple-source-systems-and-identity-correlation-in-he/">Taming the Chaos: Managing Multiple Source Systems and Identity Correlation in Higher Education</a> appeared first on <a rel="nofollow" href="https://evolveum.com">Evolveum | Open Source Identity Management &amp; Governance</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><em>This article was written by our Gold implementation partner, <a href="https://evolveum.com/partners/unicon/">Unicon Inc.</a>, as part of our MidPoint in Practice series, where partners share real-world implementation stories highlighting how they solve identity governance challenges with <a href="https://evolveum.com/midpoint/" target="_blank" rel="noopener">midPoint</a>.</em></p>
<div style="background-color: #9dc2e6; padding: 20px 24px; border-radius: 8px; border: none; outline: none; box-shadow: none; width: 100%; font-family: 'Roboto', sans-serif, Arial; color: #ffffff; display: flex; align-items: center; gap: 20px; box-sizing: border-box; margin: 25px 0;">
<div style="display: flex; align-items: center; flex-shrink: 0;"><img style="width: 65px; height: 65px; border-radius: 50%; object-fit: contain; background: #ffffff; padding: 5px; box-sizing: border-box; border: none;" src="https://evolveum.com/wp-content/uploads/unicon-new-logo.png" alt="Unicon logo" /></div>
<div style="width: 2px; background-color: #ffffff; opacity: 0.8; align-self: stretch; flex-shrink: 0;"></div>
<div style="text-align: left; display: flex; flex-direction: column; justify-content: center; gap: 8px; flex-grow: 1;">
<p style="margin: 0 !important; font-size: 16px !important; line-height: 1.4 !important; color: #ffffff !important;"><strong>About Unicon, Inc.:</strong></p>
<p style="margin: 0 !important; font-size: 16px !important; line-height: 1.6 !important; color: #ffffff !important;"><a href="https://evolveum.com/partners/unicon/">Unicon, Inc.</a> is a leading provider of IT consulting, services, and support for education technology and works with institutions and organizations to find solutions to meet business challenges. Unicon specializes in using open source technologies to deliver flexible and cost-effective systems for identity and access management (IAM). The company provides services for open source projects including midPoint, Central Authentication Service (CAS), Shibboleth, Grouper, and SimpleSAMLphp on-prem or in the cloud.</p>
</div>
</div>
<p>Higher education environments are notoriously complex when it comes to identity governance. The IT landscape must seamlessly accommodate multi-affiliation, <a href="https://docs.evolveum.com/midpoint/methodology/first-steps-training/bonus-points/multiple-sources/">multiple source systems</a>, <a href="https://docs.evolveum.com/midpoint/reference/support-4.10/security/authentication/flexible-authentication/">flexible authentication</a>, access grace periods, and immense scalability. In this implementation story written by our partner Unicon Inc., we examine a large public university serving over 80,000 active students, 20,000 staff members, and hundreds of thousands of alumni. The university managed identities across a highly fragmented ecosystem: a primary HR system for faculty and staff, a separate Student Information System (SIS) for enrolled learners, an applicant system, and an independent CRM platform for alumni and continuing education. This is a simpler example as many institutions contain more source-of-truth systems, but the methodology scales.</p>
<h2>Challenge: Managing Identity Data Across Multiple Source Systems</h2>
<p>The core operational challenge centered on aggregating and harmonizing multiple source systems. While connecting APIs and external systems is straightforward, the business logic required to unify distinct identity silos introduces complications. Several distinct hurdles emerged:</p>
<ul>
<li><strong>Attribute duplication and determining the “winner”:</strong> A user might exist simultaneously in the HR system (as a researcher) and the SIS (as a graduate student). The university needed a robust strategy to organize attributes for downstream use and determine which system&#8217;s data (such as preferred name or contact information) should “win” in the event of a conflict.</li>
<li><strong><a href="https://docs.evolveum.com/midpoint/reference/support-4.10/correlation/">Correlation</a> and deduplication:</strong> When a former undergraduate returns years later as an employee or a continuous learner, their records must seamlessly merge. Failing to correlate identities reliably results in duplicate active accounts, fragmented access histories, and licensing bloat in downstream applications.</li>
<li><strong>Marrying logical identifiers with rules:</strong> Many universities historically utilized various scripts, manual processes and other rules to set identifiers and other information. Preserving these rules while planning for inevitable future expansion without breaking existing downstream dependencies is always critical.</li>
<li><strong>Record consistency and availability:</strong> With multiple systems pushing updates at different intervals (nightly HR batches versus real-time SIS event triggers), ensuring record consistency and high availability of the most current identity state is paramount. Underlying this is the need to thoroughly understand the data within the source-of-truth systems themselves. When does it change? Is it possible to have duplicates per physical person or record? What pieces might be missing or unreliable? Essentially, implementers must validate their assumptions about any inbound data, and often it takes time (e.g., semester boundaries).</li>
</ul>
<h2>Building a Unified Identity Hub</h2>
<p>To resolve these issues, midPoint was deployed as the authoritative identity hub, leveraging its advanced correlation rules, inbound mappings, and unified schema modeling. The approach required defining clear rules of engagement for how data flowed into the central vault.</p>
<h3>Authoritative Sources and Attribute Mappings</h3>
<p>Working with business stakeholders, the Unicon team established a strict matrix of authoritative sources and rules based on existing practices. By utilizing midPoint&#8217;s inbound mapping parameters, we categorized data feeds by strength (e.g., strong vs. weak mappings) to systematically pick the “winning” attributes.</p>
<div style="overflow-x: auto; margin: 20px 0;">
<table style="width: 100%; border-collapse: collapse; font-size: 16px; line-height: 1.5;">
<thead>
<tr>
<th>Source System</th>
<th>Primary Identity Audience</th>
<th>Authoritative Attributes (Winners)</th>
</tr>
</thead>
<tbody>
<tr>
<td>Workday (HR)</td>
<td>Faculty, Staff, Contractors</td>
<td>Legal Name, Job Title, Department, Payroll ID</td>
</tr>
<tr>
<td>Banner (SIS)</td>
<td>Students, Applicants</td>
<td>Major, Enrollment Status, Student ID, GPA</td>
</tr>
<tr>
<td>Salesforce (CRM)</td>
<td>Alumni, Donors, Guests</td>
<td>Personal Email, Forwarding Address, Donation Status</td>
</tr>
</tbody>
</table>
</div>
<p>Note that in many cases in higher education, you cannot always pick a winner solely by the source-of-truth system, although it is a good starting point. MidPoint supports this by easily allowing deployers to bring in all critical attributes via extension attributes (including simplifying via multi-value attributes) on identities. This enables the deployer to choose which attribute “wins” based on their specific logic, circumstances, or even the requirements of the downstream system.</p>
<h3>Advanced Correlation Matrix</h3>
<p>Most universities have scripts, legacy customizations or even high-effort manual processes to deduplicate identities. With midPoint and its Correlation functionality, we were able to replace rudimentary matching scripts with midPoint&#8217;s multi-tiered correlation strategies. The system evaluates incoming records sequentially:</p>
<ol>
<li><strong>Deterministic match:</strong> First, midPoint searches for an exact match on a globally unique identifier, such as a National ID or a previously stamped University ID.</li>
<li><strong>High-confidence composite match:</strong> If a unique ID is absent, midPoint evaluates a composite key (e.g., Legal Name + Date of Birth + Email).</li>
<li><strong>Fuzzy match and duplicate handling:</strong> If only a partial match is detected, midPoint marks the record, suspends automatic provisioning, and generates a workflow task for manual Identity Management review. This prevents the system from incorrectly merging distinct individuals (e.g., twins with similar names).</li>
</ol>
<p>Note that this isn’t the only possibility; Unicon has assisted deployers with even more complex needs.</p>
<h2>Implementing Identity Correlation and Lifecycle Automation</h2>
<p>The technical implementation of marrying rule-based identifiers with midPoint&#8217;s native capabilities was challenging but rewarding. The university&#8217;s legacy system relied on procedural code to generate usernames (e.g., avoiding collisions by appending sequential numbers). This logic was successfully migrated into midPoint using native Groovy scripting within the user template. MidPoint now evaluates the identity vault dynamically, applies the legacy naming convention, checks for collisions in real time, and assigns the logical identifier without relying on external scripts.</p>
<p>Unicon also tackled record consistency by implementing delta synchronizations and LiveSync where supported. For the legacy HR system that could only export flat files, we scheduled frequent reconciliation tasks. midPoint&#8217;s robust caching and unified schema ensured that downstream applications (like Active Directory and Microsoft Entra ID) received highly organized, cleanly formatted attributes regardless of the sync intervals of the disparate upstream sources.</p>
<p>Overall, midPoint allowed them to manage identity data faster than their legacy systems and frameworks, reducing the time from account creation to actual downstream provisioning by days, and in some use cases, weeks.</p>
<h2>The Result: Unified Identities and Fewer Duplicate Accounts</h2>
<p>By centralizing their identity architecture with midPoint, the university achieved profound operational benefits:</p>
<ul>
<li><strong>Unified identity profiles:</strong> The help desk now utilizes midPoint as a single pane of glass, viewing a unified focal identity that accurately represents a user&#8217;s combined HR, SIS, and CRM personas.</li>
<li><strong>Massive reduction in duplicate accounts:</strong> During the initial reconciliation, midPoint successfully deduplicated 15,000+ legacy records. Downstream systems were cleansed of bloat, significantly reducing licensing costs.</li>
<li><strong>Automated multi-affiliation lifecycle:</strong> When an active student gets hired as an employee, midPoint instantly correlates the new HR record to their existing student profile. It seamlessly updates their primary affiliation, preserving their email inbox while safely layering on new staff entitlements.</li>
</ul>
<h2>Lessons Learned</h2>
<p>The most critical lesson from this deployment is that technical correlation rules and attribute rules are only as reliable as the underlying data quality and assumptions made about the source-of-truth systems. During testing, it was discovered that SIS allowed placeholder dates of birth (e.g., 01/01/1900), which severely disrupted correlation logic until remedied. MidPoint allows deployers to handle this in the inbound mapping or condition and to sanitize and ignore these placeholder values before correlation occurs. This is only one of the many “gotchas” that source systems can throw at IAM administrators. We recommend validating data and source system assumptions as early as possible.</p>
<p>Additionally, defining a “winning” attribute is fundamentally a business decision, not an IT/IAM decision. We highly recommend conducting IAM policy and data governance workshops early in the project (including as many relevant stakeholders as possible) to secure official sign-off on the attribute flow matrix and to surface non-documented “tribal” knowledge. The IAM policies, as well as the attribute and identity flows and rules, should be thoroughly documented. These will inevitably change over time, and having a clear picture is essential when making modifications to reduce ramifications. midPoint offers the flexibility to map anything anywhere, but establishing clear business ownership ensures the identity infrastructure remains scalable and maintainable over the long term.</p>
<h2>Frequently Asked Questions</h2>
<details style="border-bottom: 1px solid #e0e0e0; padding: 16px 0; cursor: pointer;">
<summary style="font-size: 18px; font-weight: bold; color: #1b365d; list-style: none; display: flex; align-items: baseline; gap: 10px;"><span style="color: #9dc2e6; font-size: 20px; font-weight: bold; line-height: 1; display: inline-block;">+</span> What is identity correlation in midPoint?</summary>
<div style="margin-top: 12px; padding-left: 24px; font-size: 16px; line-height: 1.6; color: #4a4a4a;">
<p style="margin: 0;">Correlation is the automated process by which midPoint evaluates incoming accounts from connected resources (like an HR database) to determine if they belong to an existing user (or other object) in the midPoint IAM system or if a new identity should be provisioned. This is essential for integrating multiple source-of-truth systems and preventing downstream duplicates.</p>
</div>
</details>
<details style="border-bottom: 1px solid #e0e0e0; padding: 16px 0; cursor: pointer;">
<summary style="font-size: 18px; font-weight: bold; color: #1b365d; list-style: none; display: flex; align-items: baseline; gap: 10px;"><span style="color: #9dc2e6; font-size: 20px; font-weight: bold; line-height: 1; display: inline-block;">+</span> How does midPoint assist implementers in handling conflicting attributes from multiple source systems?</summary>
<div style="margin-top: 12px; padding-left: 24px; font-size: 16px; line-height: 1.6; color: #4a4a4a;">
<p style="margin: 0;">MidPoint assists deployers in resolving conflicts using inbound mapping rules and strengths primarily configured within the source of truth resource schema in midPoint. Usually, inbound mappings alone are not sufficient. Instead, additional critical attributes can be brought in; then, within a template or via outbound mappings per external resource, deployers can prioritize sources or select an attribute based on current rules and conditions. One of midPoint&#8217;s main strengths is its flexibility, allowing deployers to adapt to the complex scenarios and needs that are part and parcel of higher education.</p>
</div>
</details>
<div style="background-color: #9dc2e6; padding: 24px 30px; border-radius: 8px; border: none; outline: none; box-shadow: none; width: 100%; font-family: 'Roboto', sans-serif, Arial; color: #ffffff; text-align: center; box-sizing: border-box; margin: 35px 0 25px;">
<p style="margin: 0 0 8px 0 !important; font-size: 20px !important; line-height: 1.4 !important; color: #ffffff !important;"><strong>Interested in working with Unicon?</strong></p>
<p style="margin: 0 0 18px 0 !important; font-size: 16px !important; line-height: 1.6 !important; color: #ffffff !important;">Get in touch with Unicon to discuss your identity management needs.</p>
<p><a style="display: inline-block; background-color: #ffffff; color: #1b365d; padding: 10px 20px; border-radius: 5px; text-decoration: none; font-weight: bold; font-size: 16px;" href="https://evolveum.com/partners/unicon/" target="_blank" rel="noopener">Contact Unicon</a></p>
</div>
<p>The post <a rel="nofollow" href="https://evolveum.com/managing-multiple-source-systems-and-identity-correlation-in-he/">Taming the Chaos: Managing Multiple Source Systems and Identity Correlation in Higher Education</a> appeared first on <a rel="nofollow" href="https://evolveum.com">Evolveum | Open Source Identity Management &amp; Governance</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://evolveum.com/managing-multiple-source-systems-and-identity-correlation-in-he/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Strengthening midPoint security and preparing for the EU Cyber Resilience Act</title>
		<link>https://evolveum.com/midpoint-and-cra/</link>
					<comments>https://evolveum.com/midpoint-and-cra/#respond</comments>
		
		<dc:creator><![CDATA[Mita Chu]]></dc:creator>
		<pubDate>Thu, 24 Sep 2026 12:42:03 +0000</pubDate>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[Latest news]]></category>
		<guid isPermaLink="false">https://evolveum.com/?p=16142</guid>

					<description><![CDATA[<p>The EU Cyber Resilience Act (CRA) is now in force, establishing cybersecurity requirements for products with digital elements. While the main CRA obligations will apply from December 2027, organizations developing and maintaining software products need to start preparing well in advance. As part of our ongoing commitment to the security and long-term development of midPoint, <a href="https://evolveum.com/midpoint-and-cra/" rel="nofollow"><span class="sr-only">Read more about Strengthening midPoint security and preparing for the EU Cyber Resilience Act</span>[&#8230;]</a></p>
<p>The post <a rel="nofollow" href="https://evolveum.com/midpoint-and-cra/">Strengthening midPoint security and preparing for the EU Cyber Resilience Act</a> appeared first on <a rel="nofollow" href="https://evolveum.com">Evolveum | Open Source Identity Management &amp; Governance</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>The <strong><a href="https://digital-strategy.ec.europa.eu/en/policies/cyber-resilience-act" rel="noopener" target="_blank">EU Cyber Resilience Act</a></strong> (CRA) is now in force, establishing cybersecurity requirements for products with digital elements. While the main CRA obligations will apply from December 2027, organizations developing and maintaining software products need to start preparing well in advance.</p>
<p>As part of our ongoing commitment to the security and long-term development of midPoint, Evolveum has received funding from the EU to assess the current state of the product and our development processes against the CRA requirements. The project MidPoint – CRA compliance enhancements will help us identify areas for improvement and define concrete steps towards meeting the regulation’s requirements.</p>
<h2>Assessing our readiness for the CRA</h2>
<p>The project will begin with a detailed analysis of the CRA requirements and a gap analysis of midPoint and Evolveum&#8217;s existing processes. This will help us understand where our current practices already meet the requirements and where further measures may be needed.</p>
<p>We will also perform a cybersecurity risk assessment and identify specific features and process improvements to be considered for implementation in the midPoint 4.12 release. The findings will be brought together in a dedicated CRA action plan, providing a practical roadmap for addressing the identified gaps and preparing for the regulation&#8217;s requirements.</p>
<h2>Putting midPoint under pressure</h2>
<p>Part of our action plan is to conduct a penetration testing of the upcoming midPoint 4.11, including a testing performed by an independent third-party contractor. This will not be a one-and-done exercise – as we have done previously, we are committed to penetration testing subsequent major product versions every year before their release. </p>
<p>The goal is to simulate a cyberattack to identify vulnerabilities and uncover gaps that may not be apparent during the usual testing and development process. The results of the penetration testing will be made publicly available, reflecting our commitment to open standards and transparency. The findings will also feed directly into our ongoing security improvements and help us make each new version of midPoint more resiliant.</p>
<h2>Building security into the product lifecycle</h2>
<p>The CRA places greater emphasis on cybersecurity throughout the lifecycle of products with digital elements, including secure design and development, vulnerability handling, and ongoing security.</p>
<p>For Evolveum, this project is an opportunity to approach these requirements systematically: understand what the regulation requires, assess our current position, identify risks and gaps, and turn those findings into concrete improvements.<br />
The project is supported through the TestCert-SK project (101127837), funded by the European Commission and Slovakia’s National Security Authority (NBÚ). </p>
<p>Security is not a one-time milestone, it is an ongoing part of developing and maintaining trusted identity governance software. This project is one step in the continuous process of strengthening the security and resilience of midPoint.</p>
<style>
  @media (max-width: 600px) {<br />
    .vertical-separator {<br />
      display: none;<br />
    }<br />
  }<br />
</style>
<div style="margin-top: 40px;">
<hr style="border: none; border-top: 1px solid #2a2768; width: 100%; margin: 0 0 20px 0;" />
<div style="height: 20px;"></div>
<h2>Posilňovanie bezpečnosti midPointu a príprava na Akt o kybernetickej odolnosti EÚ (CRA)</h2>
<p>Akt o kybernetickej odolnosti EÚ (Cyber Resilience Act – CRA) už nadobudol účinnosť a stanovuje požiadavky na kybernetickú bezpečnosť produktov s digitálnymi prvkami. Hoci sa hlavné povinnosti vyplývajúce z CRA začnú uplatňovať od decembra 2027, organizácie, ktoré vyvíjajú a udržiavajú softvérové produkty, by sa na ne mali začať pripravovať s dostatočným predstihom.</p>
<p>V rámci nášho dlhodobého záväzku k bezpečnosti a ďalšiemu rozvoju midPointu získala spoločnosť Evolveum finančnú podporu od EÚ na posúdenie súčasného stavu produktu a našich vývojových procesov z hľadiska požiadaviek CRA. Projekt MidPoint – CRA compliance enhancements nám pomôže identifikovať oblasti, v ktorých je priestor na zlepšenie a stanoviť konkrétne kroky smerujúce k splneniu požiadaviek tejto regulácie.</p>
<h2>Posúdenie našej pripravenosti na CRA</h2>
<p>Projekt sa začne podrobnou analýzou požiadaviek CRA a analýzou rozdielov medzi týmito požiadavkami a existujúcim stavom midPointu a procesov v spoločnosti Evolveum. To nám pomôže zistiť, v ktorých oblastiach naše súčasné postupy požiadavky už spĺňajú a kde bude potrebné prijať ďalšie opatrenia.</p>
<p>Zároveň vykonáme hodnotenie kybernetických rizík a identifikujeme konkrétne funkcie a možnosti zlepšenia procesov, ktoré by bolo vhodné zvážiť na implementáciu v rámci vydania midPointu 4.12. Výsledky spojíme do samostatného akčného plánu pre CRA, ktorý poskytne praktický návrh ďalšieho postupu pri riešení identifikovaných nedostatkov a príprave na požiadavky tejto regulácie.</p>
<h2>Bezpečnosť ako súčasť životného cyklu produktu</h2>
<p>CRA kladie väčší dôraz na kybernetickú bezpečnosť počas celého životného cyklu produktov s digitálnymi prvkami vrátane bezpečného návrhu a vývoja, riešenia zraniteľností a priebežného zabezpečovania produktu.</p>
<p>Pre spoločnosť Evolveum je tento projekt príležitosťou pristúpiť k týmto požiadavkám systematicky: pochopiť, čo regulácia vyžaduje, posúdiť našu súčasnú situáciu, identifikovať riziká a nedostatky, a následne premeniť tieto zistenia na konkrétne zlepšenia.</p>
<p>Projekt* je podporený v rámci TestCert-SK (101127837), ktorý je financovaný Európskou komisiou a Národným bezpečnostným úradom Slovenskej republiky (NBÚ).</p>
<p>Bezpečnosť nie je jednorazovým míľnikom, ale neoddeliteľnou súčasťou neustáleho vývoja a údržby dôveryhodného softvéru na správu identít. Tento projekt predstavuje ďalší krok v kontinuálnom procese posilňovania bezpečnosti a odolnosti midPointu.</p>
<p></br><br />
*Projekt financovaný na základe zmluvy o poskytnutí NFP č. 25094/2026 podporuje Národný bezpečnostný úrad. Financované Európskou úniou. Vyjadrené názory a postoje sú názormi a vyhláseniami autora(-ov) a nemusia nevyhnutne odrážať názory a stanoviská Európskej únie alebo Európskeho kompetenčného centra pre kybernetickú bezpečnosť. Európska únia ani Európske kompetenčné centrum pre kybernetickú bezpečnosť za ne nepreberá žiadnu zodpovednosť“.</p>
<p>Výška poskytnutého NFP: 39201,59- EUR</p>
<hr style="border: none; border-top: 1px solid #2a2768; width: 100%; margin: 0 0 20px 0;" />
<div style="display: flex; justify-content: center; align-items: center; flex-wrap: wrap; gap: 40px; margin-bottom: 20px;">
<div style="display: flex; align-items: center;"><a style="display: flex; align-items: center;" href="https://ec.europa.eu/" target="_blank" rel="noopener"><br />
<img style="height: 60px; width: auto; object-fit: contain; display: block;" src="https://evolveum.com/wp-content/uploads/funded-by-the-eu-logo.jpg" alt="Funded by the European Union" /><br />
</a></div>
<div class="vertical-separator" style="width: 1px; height: 100px; background-color: #2a2768;"></div>
<div style="display: flex; align-items: center;"><a style="display: flex; align-items: center;" href="https://www.nbu.gov.sk/" target="_blank" rel="noopener"><br />
<img style="height: 60px; width: auto; object-fit: contain; display: block;" src="https://evolveum.com/wp-content/uploads/nbu-sk-logo.png" alt="Národný bezpečnostný úrad" /><br />
</a></div>
<div class="vertical-separator" style="width: 1px; height: 100px; background-color: #2a2768;"></div>
<div style="display: flex; align-items: center;"><a style="display: flex; align-items: center;" href="https://cybersecurity-centre.europa.eu/" target="_blank" rel="noopener"><br />
<img style="height: 60px; width: auto; object-fit: contain; display: block;" src="https://evolveum.com/wp-content/uploads/eccc-logo.png" alt="European Cybersecurity Competence Centre and Network" />
</div>
</div>
<p></br></p>
<h2>Frequently Asked Questions</h2>
<details style="border-bottom: 1px solid #e0e0e0; padding: 16px 0; cursor: pointer;">
<summary style="font-size: 18px; font-weight: bold; color: #1b365d; list-style: none; display: flex; align-items: baseline; gap: 10px;"><span style="color: #9dc2e6; font-size: 20px; font-weight: bold; line-height: 1; display: inline-block;">+</span> What is the CRA?</summary>
<div style="margin-top: 12px; padding-left: 24px; font-size: 16px; line-height: 1.6; color: #4a4a4a;">
<p style="margin: 0;">The Cyber Resilience Act is an EU regulation that establishes cybersecurity requirements for products with digital elements, including both hardware and software products placed on the EU market.<br />
<br />
Its goal is to make products more secure throughout their lifecycle. The regulation puts greater responsibility on manufacturers to address cybersecurity from the design and development stages through to maintenance, vulnerability handling, and support.</p>
</div>
</details>
<details style="border-bottom: 1px solid #e0e0e0; padding: 16px 0; cursor: pointer;">
<summary style="font-size: 18px; font-weight: bold; color: #1b365d; list-style: none; display: flex; align-items: baseline; gap: 10px;"><span style="color: #9dc2e6; font-size: 20px; font-weight: bold; line-height: 1; display: inline-block;">+</span> What are the requirements of the CRA?</summary>
<div style="margin-top: 12px; padding-left: 24px; font-size: 16px; line-height: 1.6; color: #4a4a4a;">
<p style="margin: 0;">The CRA introduces cybersecurity requirements covering the design, development, delivery, and maintenance of products with digital elements.<br />
<br />
Among other things, manufacturers need to:<br />
</p>
<ul>
<li>design and develop products with appropriate cybersecurity in mind</li>
<li>carry out a cybersecurity risk assessment</li>
<li>address identified vulnerabilities and security risks</li>
<li>provide security updates and handle vulnerabilities throughout the required support period</li>
<li>provide appropriate security information and technical documentation</li>
<li>carry out the applicable conformity assessment procedure</li>
<li>report certain actively exploited vulnerabilities and severe security incidents</li>
<li>provide information about the product&#8217;s security and support period</li>
</ul>
<p>The specific requirements and conformity-assessment procedure depend on the product and its classification under the CRA.</p>
</div>
</details>
<details style="border-bottom: 1px solid #e0e0e0; padding: 16px 0; cursor: pointer;">
<summary style="font-size: 18px; font-weight: bold; color: #1b365d; list-style: none; display: flex; align-items: baseline; gap: 10px;"><span style="color: #9dc2e6; font-size: 20px; font-weight: bold; line-height: 1; display: inline-block;">+</span> What is the CRA timeline?</summary>
<div style="margin-top: 12px; padding-left: 24px; font-size: 16px; line-height: 1.6; color: #4a4a4a;">
<p style="margin: 0;">The CRA is already in force, but its requirements are being introduced in stages:</p>
<ul>
<li>10 December 2024: The Cyber Resilience Act entered into force</li>
<li>11 June 2026: Provisions concerning the notification of conformity assessment bodies come into effect</li>
<li>11 September 2026: The CRA vulnerability and severe-incident reporting obligations come into effect</li>
<li>11 December 2027: The main provisions of the CRA come into effect, including the core cybersecurity requirements for products covered by the regulation</li>
</ul>
</div>
<p>The post <a rel="nofollow" href="https://evolveum.com/midpoint-and-cra/">Strengthening midPoint security and preparing for the EU Cyber Resilience Act</a> appeared first on <a rel="nofollow" href="https://evolveum.com">Evolveum | Open Source Identity Management &amp; Governance</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://evolveum.com/midpoint-and-cra/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Toxic Combinations, Handled: Enforcing Segregation of Duties Across Systems with MidPoint</title>
		<link>https://evolveum.com/toxic-combinations-handled-enforcing-sod-with-midpoint/</link>
					<comments>https://evolveum.com/toxic-combinations-handled-enforcing-sod-with-midpoint/#respond</comments>
		
		<dc:creator><![CDATA[AMI Praha]]></dc:creator>
		<pubDate>Wed, 23 Sep 2026 06:30:41 +0000</pubDate>
				<category><![CDATA[Community]]></category>
		<guid isPermaLink="false">https://evolveum.com/?p=16088</guid>

					<description><![CDATA[<p>This article was written by our Gold implementation partner, AMI Praha, as part of our MidPoint in Practice series, where partners share real-world implementation stories highlighting how they solve identity governance challenges with midPoint. About AMI Praha: AMI Praha is a system integrator operating in the ICT security segment that specializes in authentication / authorization <a href="https://evolveum.com/toxic-combinations-handled-enforcing-sod-with-midpoint/" rel="nofollow"><span class="sr-only">Read more about Toxic Combinations, Handled: Enforcing Segregation of Duties Across Systems with MidPoint</span>[&#8230;]</a></p>
<p>The post <a rel="nofollow" href="https://evolveum.com/toxic-combinations-handled-enforcing-sod-with-midpoint/">Toxic Combinations, Handled: Enforcing Segregation of Duties Across Systems with MidPoint</a> appeared first on <a rel="nofollow" href="https://evolveum.com">Evolveum | Open Source Identity Management &amp; Governance</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><em>This article was written by our Gold implementation partner, <a href="https://evolveum.com/partners/ami-praha/">AMI Praha</a>, as part of our MidPoint in Practice series, where partners share real-world implementation stories highlighting how they solve identity governance challenges with </em><a href="https://evolveum.com/midpoint/" target="_blank" rel="noopener"><em>midPoint</em></a><em>.</em></p>
<div style="background-color: #9dc2e6; padding: 20px 24px; border-radius: 8px; border: none; outline: none; box-shadow: none; width: 100%; font-family: 'Roboto', sans-serif, Arial; color: #ffffff; display: flex; align-items: center; gap: 20px; box-sizing: border-box; margin: 25px 0;">
<div style="display: flex; align-items: center; flex-shrink: 0;"><img style="width: 65px; height: 65px; border-radius: 50%; object-fit: contain; background: #ffffff; padding: 5px; box-sizing: border-box; border: none;" src="https://evolveum.com/wp-content/uploads/ami-praha-logo.jpg" alt="AMI Praha logo" /></div>
<div style="width: 2px; background-color: #ffffff; opacity: 0.8; align-self: stretch; flex-shrink: 0;"></div>
<div style="text-align: left; display: flex; flex-direction: column; justify-content: center; gap: 8px; flex-grow: 1;">
<p style="margin: 0 !important; font-size: 16px !important; line-height: 1.4 !important; color: #ffffff !important;"><strong>About AMI Praha:</strong></p>
<p style="margin: 0 !important; font-size: 16px !important; line-height: 1.6 !important; color: #ffffff !important;"><a style="color: #ffffff !important; text-decoration: underline;" href="https://evolveum.com/partners/ami-praha/">AMI Praha</a> is a system integrator operating in the ICT security segment that specializes in authentication / authorization processes and access control to information, regardless of the place of storage. AMI Praha has been integrating midPoint into their customers’ IAM infrastructures since 2015.</p>
</div>
</div>
<h2>What Is Segregation of Duties (SoD)?</h2>
<p><a href="https://docs.evolveum.com/midpoint/reference/support-4.10/roles-policies/policies/segregation-of-duties/" target="_blank" rel="noopener"><strong>Segregation of Duties (SoD)</strong></a> is one of the most important controls in identity governance and administration (IGA). It prevents users from accumulating combinations of permissions that could enable fraud or abuse of power, and it&#8217;s a core component of any effective risk management strategy.</p>
<p>Certain powerful capabilities must never rest in the same pair of hands – being able to create a vendor and approve a payment, or to post a journal entry and approve it – these two examples are classic fraud risks. These &#8220;toxic combinations&#8221; are common audit findings and are addressed directly by compliance frameworks such as ISO/IEC 27001 (Control 5.3).</p>
<p>Many enterprise applications can enforce SoD within their own environment. But today&#8217;s organizations run on multiple interconnected systems, and a user may pick up one sensitive entitlement in one application and another in a line-of-business system, creating a risky combination that no single application can detect on its own.</p>
<p>This is where identity governance becomes essential. Because midPoint serves as a central identity governance and administration platform, it has a complete view of a user&#8217;s assignments and can enforce cross-system SoD policies before risky access is granted.</p>
<p>In this implementation story, AMI Praha explains how a regulated financial institution in Central Europe used <a href="https://evolveum.com/midpoint/" target="_blank" rel="noopener">midPoint</a> to move from manual, detective controls to automated, preventive access governance.</p>
<h2>The Challenge: Enforcing Segregation of Duties Across Multiple Systems</h2>
<p>The organization uses <a href="https://evolveum.com/midpoint/" target="_blank" rel="noopener">midPoint</a> as its central IGA platform, granting access through a role model (a structure where access rights are bundled into named roles, then assigned to users, rather than granted permission-by-permission) that spans several connected systems – an SAP ABAP back end, Active Directory, an LDAP directory, and a core line-of-business application – all fed from an authoritative HR source.</p>
<p>Although SoD was already being checked within individual systems, most notably inside SAP, the organization faced a common identity governance challenge: no single application had visibility into a user&#8217;s complete access profile. As a result, toxic combinations spanning multiple systems could slip through undetected.</p>
<p>At the same time, enforcement relied heavily on manual spreadsheets and periodic audits. Violations were discovered only after access had already been granted, rather than prevented at the point of request – creating real exposure windows, repetitive analyst effort, and audit findings that were expensive to remediate after the fact.</p>
<p>To complicate matters further, years of accumulated role assignments meant SoD conflicts already existed throughout the environment. A &#8220;just turn it on&#8221; approach wasn&#8217;t an option: enabling strict enforcement overnight would have disrupted business operations and generated a flood of errors. The organization needed a solution that strengthened governance and compliance without interrupting day-to-day work.</p>
<h2>How MidPoint Enforced Cross-System Segregation of Duties</h2>
<p><a href="https://evolveum.com/partners/ami-praha/">AMI Praha</a> implemented <a href="https://docs.evolveum.com/midpoint/reference/support-4.10/roles-policies/policies/segregation-of-duties/" target="_blank" rel="noopener">SoD</a> natively in midPoint using policy rules with exclusion constraints, and, critically, rolled it out gradually. A few properties of midPoint&#8217;s model made this approach clean to implement:</p>
<ul>
<li><strong>Exclusion is declarative and bi-directional.</strong> Administrators state, on one role, that it excludes another via a targetRef. MidPoint treats the exclusion as mutual regardless of which role is assigned first or second, so each conflicting pair is defined once, not twice, which keeps the policy set simpler to maintain long-term.</li>
</ul>
<ul>
<li><strong>The enforcement action is separate from the constraint.</strong> The same exclusion can be attached to different policy actions depending on how strict the situation calls for:
<ul>
<li><em>enforcement</em> &#8211; a hard block; the conflicting assignment is rejected with an error.</li>
<li><em>approval</em> &#8211; the request is routed to a designated approver, who can grant a documented, auditable exception.</li>
<li><em>record</em> &#8211; the conflict is marked but not blocked, so it can be reported without disrupting anyone.</li>
</ul>
</li>
</ul>
<ul>
<li><strong>Metaroles let SoD scale.</strong> Instead of wiring together hundreds of individual role pairs, the team expressed &#8220;exclusion classes&#8221;, for example, all executive roles versus all controlling roles through metaroles (roles that apply their rules to a whole category of other roles at once), so newly added roles inherit the correct exclusions automatically.</li>
<li><strong>It&#8217;s a cross-system by construction.</strong> Because midPoint evaluates a user&#8217;s complete assignment set, a violation split across SAP and another application is caught just as reliably as one contained entirely inside SAP – something a single-system control cannot do.</li>
</ul>
<h2>A Gradual Rollout That Minimized Risk</h2>
<p>The rollout followed midPoint&#8217;s gradual-enforcement pattern, which turned out to be the single most important decision in the project:</p>
<ol>
<li><strong>Model the conflicts.</strong> Working with business and compliance owners, AMI Praha translated the organization&#8217;s SoD matrix into exclusion constraints on the relevant roles, using metaroles for the broad &#8220;class versus class&#8221; rules.</li>
<li><strong>Start in record mode.</strong> Every rule went live initially with the record action. Nothing was blocked; conflicts were simply marked.</li>
<li><strong>Report and remediate.</strong> The team produced a violation report from those marks, surfacing the true state of pre-existing conflicts. The business then worked through the backlog – removing access, splitting duties, or formally accepting a documented exception – until it was clean.</li>
<li><strong>Switch to prevention.</strong> Only then did the actions change to enforcement for the strict rules and approval for the cases where legitimate, controlled exceptions are a business reality. From that point on, midPoint prevents new violations at the moment of request.</li>
</ol>
<p>Pairing enforcement and approval per rule was key to making this work: the truly forbidden combinations became simply impossible, while the &#8220;normally not allowed, but sometimes justified&#8221; combinations generate an approval request that leaves a full audit trail of who requested, who approved, and why.</p>
<h2>From Detective Controls to Preventive Identity Governance</h2>
<p>The most significant shift was in timing: SoD moved from detective to preventive. Conflicting access is now stopped at the moment of request, closing the exposure window that periodic reviews used to leave open. Instead of discovering a violation weeks or months after the fact, the system simply refuses to create it.</p>
<p>Coverage also became cross-system. Because midPoint evaluates a user&#8217;s complete assignment set, it catches combinations that no individual application (SAP included) could have seen on its own, closing the blind spot that motivated the project in the first place.</p>
<p>That shift changed what audit preparation looks like day to day. Rather than assembling evidence after the fact, the organization can now present it directly: the policy rules serve as the documented control, the marks left by earlier record-mode runs serve as historical evidence, and every approved exception carries its own audit trail of who requested it, who approved it, and why. Analyst time that used to go into manually hunting for violations has been redirected toward remediation and ongoing policy refinement instead.</p>
<h2>Key Lessons for Implementing Segregation of Duties</h2>
<p><strong>Gradual enforcement isn&#8217;t optional at scale.</strong> Going straight to hard blocking in an established role model breaks legitimate work. The record → report → remediate → enforce sequence is what actually makes SoD deployable in a live environment rather than a theoretical policy that never gets switched on.</p>
<p>It&#8217;s also worth <strong>defining each conflicting pair only once</strong>. Because exclusion in midPoint is bi-directional, mirroring a rule on both roles creates maintenance noise down the line. For the same reason, metaroles are worth adopting early rather than late: pair-by-pair modeling doesn&#8217;t scale and tends to rot as new roles are added, while class-level rules keep the policy maintainable over time.</p>
<p><strong>Enforcement and approval should be combined deliberately</strong> rather than applied uniformly. Not every conflict is absolute, therefore reserving hard enforcement for the genuinely forbidden combinations, and routing the rest through an approval workflow, keeps the control both strict where it needs to be and workable where legitimate exceptions exist.</p>
<p>Finally, it&#8217;s worth remembering that <strong>SoD is a business artifact, not a technical one</strong>. The exclusion matrix has to be owned and signed off by compliance and the business. MidPoint enforces the policy faithfully, but only the business can decide what the policy actually is.</p>
<h2>Frequently Asked Questions</h2>
<details style="border-bottom: 1px solid #e0e0e0; padding: 16px 0; cursor: pointer;">
<summary style="font-size: 18px; font-weight: bold; color: #1b365d; list-style: none; display: flex; align-items: baseline; gap: 10px;"><span style="color: #9dc2e6; font-size: 20px; font-weight: bold; line-height: 1; display: inline-block;">+</span> What are the benefits of Segregation of Duties?</summary>
<div style="margin-top: 12px; padding-left: 24px; font-size: 16px; line-height: 1.6; color: #4a4a4a;">
<p style="margin: 0;">SoD minimizes operational risk by preventing any single individual from executing high-risk processes unchecked. It dramatically reduces exposure to internal fraud, errors, and privilege abuse across the organization. Additionally, SoD simplifies alignment with major compliance frameworks like ISO/IEC 27001 and SOX.</p>
</div>
</details>
<details style="border-bottom: 1px solid #e0e0e0; padding: 16px 0; cursor: pointer;">
<summary style="font-size: 18px; font-weight: bold; color: #1b365d; list-style: none; display: flex; align-items: baseline; gap: 10px;"><span style="color: #9dc2e6; font-size: 20px; font-weight: bold; line-height: 1; display: inline-block;">+</span> How does midPoint enforce Segregation of Duties?</summary>
<div style="margin-top: 12px; padding-left: 24px; font-size: 16px; line-height: 1.6; color: #4a4a4a;">
<p style="margin: 0;">MidPoint enforces SoD using policy rules defined within role configurations, specifically through role exclusions. A role can declare via a policy constraint that it cannot be assigned alongside another specific role or category. Administrators can utilize metaroles to apply these bidirectional exclusion rules across entire classes of roles simultaneously. Because midPoint evaluates a user’s global assignment set across all connected target systems, it effectively catches cross-system conflicts.</p>
</div>
</details>
<details style="border-bottom: 1px solid #e0e0e0; padding: 16px 0; cursor: pointer;">
<summary style="font-size: 18px; font-weight: bold; color: #1b365d; list-style: none; display: flex; align-items: baseline; gap: 10px;"><span style="color: #9dc2e6; font-size: 20px; font-weight: bold; line-height: 1; display: inline-block;">+</span> What happens when a Segregation of Duties conflict is detected?</summary>
<div style="margin-top: 12px; padding-left: 24px; font-size: 16px; line-height: 1.6; color: #4a4a4a;">
<p style="margin: 0;">When a SoD conflict is detected, midPoint’s response depends entirely on the policy action attached to the exclusion rule. With strict enforcement, the system hard-blocks the request and rejects any conflicting assignment outright. Alternatively, with an approval workflow, the request is automatically routed to a designated authority who can review the context and grant a documented exception. The system can also be configured to simply record or log the conflict for visibility without blocking, which is ideal during initial policy rollouts.</p>
</div>
</details>
<div style="background-color: #9dc2e6; padding: 24px 30px; border-radius: 8px; border: none; outline: none; box-shadow: none; width: 100%; font-family: 'Roboto', sans-serif, Arial; color: #ffffff; text-align: center; box-sizing: border-box; margin: 35px 0 25px;">
<p style="margin: 0 0 8px 0 !important; font-size: 20px !important; line-height: 1.4 !important; color: #ffffff !important;"><strong>Interested in working with AMI Praha?</strong></p>
<p style="margin: 0 0 18px 0 !important; font-size: 16px !important; line-height: 1.6 !important; color: #ffffff !important;">Get in touch with AMI Praha to discuss your identity management needs.</p>
<p><a style="display: inline-block; background-color: #ffffff; color: #1b365d; padding: 10px 20px; border-radius: 5px; text-decoration: none; font-weight: bold; font-size: 16px;" href="https://evolveum.com/partners/ami-praha/" target="_blank" rel="noopener">Contact AMI Praha</a></p>
</div>
<p>The post <a rel="nofollow" href="https://evolveum.com/toxic-combinations-handled-enforcing-sod-with-midpoint/">Toxic Combinations, Handled: Enforcing Segregation of Duties Across Systems with MidPoint</a> appeared first on <a rel="nofollow" href="https://evolveum.com">Evolveum | Open Source Identity Management &amp; Governance</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://evolveum.com/toxic-combinations-handled-enforcing-sod-with-midpoint/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>AI Agent Governance: How to Safely Deploy and Manage AI Identities</title>
		<link>https://evolveum.com/ai-agent-governance-how-to-safely-deploy-and-manage-ai-identities/</link>
					<comments>https://evolveum.com/ai-agent-governance-how-to-safely-deploy-and-manage-ai-identities/#respond</comments>
		
		<dc:creator><![CDATA[Mita Chu]]></dc:creator>
		<pubDate>Fri, 11 Sep 2026 08:04:52 +0000</pubDate>
				<category><![CDATA[Deployment]]></category>
		<category><![CDATA[Evolveum's Identity Management and Governance Blog]]></category>
		<guid isPermaLink="false">https://evolveum.com/?p=15968</guid>

					<description><![CDATA[<p>AI agents are becoming digital coworkers. So much so that Gartner predicts that by 2028, an average global Fortune 500 enterprise will have over 150,000 agents in use – up from less than 15 just last year. Even if that projection turns out to be way too optimistic and the actual numbers will land somewhere <a href="https://evolveum.com/ai-agent-governance-how-to-safely-deploy-and-manage-ai-identities/" rel="nofollow"><span class="sr-only">Read more about AI Agent Governance: How to Safely Deploy and Manage AI Identities</span>[&#8230;]</a></p>
<p>The post <a rel="nofollow" href="https://evolveum.com/ai-agent-governance-how-to-safely-deploy-and-manage-ai-identities/">AI Agent Governance: How to Safely Deploy and Manage AI Identities</a> appeared first on <a rel="nofollow" href="https://evolveum.com">Evolveum | Open Source Identity Management &amp; Governance</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>AI agents are becoming digital coworkers. So much so that <a href="https://www.gartner.com/en/newsroom/press-releases/2026-04-28-gartner-identifies-six-steps-to-manage-artificial-intelligence-agent-sprawl" target="_blank" rel="noopener">Gartner predicts that by 2028, an average global Fortune 500 enterprise will have over 150,000 agents in use</a> – up from less than 15 just last year. Even if that projection turns out to be way too optimistic and the actual numbers will land somewhere around 50%, it describes a workforce larger than most of the companies deploying it, assembled in only three years.</p>
<p>Most organizations are somewhere in the early part of this curve right now, and that&#8217;s exactly the moment to get governance right. It&#8217;s much easier to define the policy framework at the start than to retrofit it later on. Otherwise, organizations risk discovering gaps when scaling, during an audit, or worse, when one becomes a serious security incident.</p>
<p>This guide explores how organizations can deploy AI agents securely and enable innovation without losing control.</p>
<p>&nbsp;</p>
<ul>
<li><a href="#what-is-ai-agent">What is an AI agent?</a></li>
<li><a href="#how-ai-agents-differ-from-nhi">How do AI agents differ from other non-human identities (NHIs)?</a></li>
<li><a href="#what-can-go-wrong-with-ai-agents">What can go wrong when AI agents aren&#8217;t governed?</a></li>
<li><a href="#three-ai-agent-governance-questions">Three AI agent governance questions most organizations haven&#8217;t answered.</a></li>
<li><a href="#8-step-ai-governance-framework">How to govern AI agents: an 8-step guide.</a></li>
<li><a href="#how-ai-agent-governance-works-in-midpoint">How AI agent governance works in midPoint.</a></li>
</ul>
<p>&nbsp;</p>
<h2 id="what-is-ai-agent"><b>What is an AI agent?</b></h2>
<p>An AI agent is a software identity powered by a large language model (LLM) that has been given access to credentials and business systems so it can complete tasks autonomously. Unlike a chatbot that simply answers questions, an AI agent can perform work on your behalf. It can call APIs, query databases, read and write files, invoke external services, and even coordinate with other agents to complete more complex workflows.</p>
<p>To do that, an agent authenticates with credentials such as OAuth tokens, service accounts, and workload identities, allowing it to operate as a trusted user inside your environment. Once an AI agent receives credentials and permissions, it becomes another identity that must be governed throughout its lifecycle.</p>
<p>&nbsp;</p>
<h2 id="how-ai-agents-differ-from-nhi"><b>How do AI agents differ from other non-human identities (NHIs)?</b></h2>
<p><img loading="lazy" class="alignnone wp-image-15969" src="https://evolveum.com/wp-content/uploads/Screenshot-2026-09-09-at-17.10.41-300x156.png" alt="Comparison table showing how traditional non-human identities differ from AI agents across definition, behavior, workflow example, and security and governance approach" width="967" height="503" srcset="https://evolveum.com/wp-content/uploads/Screenshot-2026-09-09-at-17.10.41-300x156.png 300w, https://evolveum.com/wp-content/uploads/Screenshot-2026-09-09-at-17.10.41-1024x532.png 1024w, https://evolveum.com/wp-content/uploads/Screenshot-2026-09-09-at-17.10.41-768x399.png 768w, https://evolveum.com/wp-content/uploads/Screenshot-2026-09-09-at-17.10.41-1536x798.png 1536w, https://evolveum.com/wp-content/uploads/Screenshot-2026-09-09-at-17.10.41-2048x1064.png 2048w, https://evolveum.com/wp-content/uploads/Screenshot-2026-09-09-at-17.10.41-1320x686.png 1320w, https://evolveum.com/wp-content/uploads/Screenshot-2026-09-09-at-17.10.41-600x312.png 600w" sizes="(max-width: 967px) 100vw, 967px" /></p>
<p>AI agents are a type of non-human identity but they behave very differently from the static machine identities that IAM teams have managed for years.</p>
<p>Traditional identity governance focuses on granting access and reviewing it periodically. AI agents require continuous oversight because what matters isn&#8217;t just who has access, it&#8217;s what they&#8217;re trying to do right now.</p>
<p>&nbsp;</p>
<h2 id="what-can-go-wrong-with-ai-agents"><b>What can go wrong when AI agents aren&#8217;t governed?</b></h2>
<p>Unlike what we see in sci-fi movies, most governance failures don&#8217;t begin with a malicious AI agent. What’s more likely is that they start with an ordinary business problem that slowly snowballs into an identity problem.</p>
<h3><b>Sensitive data exposure</b></h3>
<p>Unlike a human employee reading a customer record on a screen, an AI agent often sends portions of that information into a language model as part of its reasoning process. Governance therefore needs to extend beyond controlling access to databases. Organizations should also consider what information an AI agent can access and process in the first place, and whether personally identifiable information should be masked before it is sent to an LLM for summarization.</p>
<h3><b>Privilege accumulation</b></h3>
<p>As organizations discover new use cases, agents tend to receive additional permissions without much review. What began as read-only CRM access gradually expands into access to multiple systems, while no one periodically asks whether those permissions are still required. Unlike employees, whose access is often reviewed during certification campaigns, AI agents are frequently overlooked because they aren&#8217;t seen as traditional identities.</p>
<h3><b>Lack of ownership</b></h3>
<p>AI agents also have a habit of outliving the projects that created them because no one clearly owns them. A developer builds an agent during a pilot, changes teams a few months later, and the agent continues operating because the business depends on it. Over time, the risk of everyone forgetting about these agents compounds.</p>
<h3><b>Shadow AI</b></h3>
<p>Not every AI agent is deployed through an approved IT project. Often, employees are creating agents themselves to solve everyday business problems, often without realizing the security implications. Just as Shadow IT introduced unmanaged applications, Shadow AI introduces unmanaged AI identities. If security teams don&#8217;t know an agent exists, they can&#8217;t govern its access and monitor its activity.</p>
<p>It&#8217;s worth noting that the instinct to clamp down makes this worse. Gartner&#8217;s own guidance on agent sprawl is that blocking or restricting AI agents isn&#8217;t a long-term solution, because employees who can&#8217;t work in sanctioned tools will go around the controls and adopt shadow AI instead — which presents far greater risk than the thing you were trying to prevent.</p>
<h3><b>Compliance: EU AI Act, GDPR, NIS2, DORA, and CRA</b></h3>
<p>As AI agents become part of everyday business processes, governance also becomes a compliance issue. An agent with access to sensitive data and regulated systems is subject to many of the same expectations as human employees.</p>
<p>&nbsp;</p>
<div style="max-width: 100%; overflow-x: auto;">
<table style="width: 100%; border-collapse: separate; border-spacing: 0; border: 1px solid #dae4f4; border-radius: 12px; font-family: 'Roboto', sans-serif, Arial;">
<thead>
<tr>
<th style="background: #3181c4; color: #ffffff; text-align: left; font-size: 13px; font-weight: bold; text-transform: uppercase; letter-spacing: 0.05em; padding: 14px 18px;">Regulation</th>
<th style="background: #3181c4; color: #ffffff; text-align: left; font-size: 13px; font-weight: bold; text-transform: uppercase; letter-spacing: 0.05em; padding: 14px 18px;">Primary focus</th>
<th style="background: #3181c4; color: #ffffff; text-align: left; font-size: 13px; font-weight: bold; text-transform: uppercase; letter-spacing: 0.05em; padding: 14px 18px;">Relevance to AI agent governance</th>
</tr>
</thead>
<tbody>
<tr>
<td style="padding: 16px 18px; border-top: 1px solid #dae4f4; border-left: 3px solid #ff9d00; font-weight: bold;"><a style="color: #3181c4; text-decoration: none;" href="https://gdpr-info.eu/" target="_blank" rel="noopener">GDPR</a></td>
<td style="padding: 16px 18px; border-top: 1px solid #dae4f4; color: #5b6b7a;">Protection of personal data</td>
<td style="padding: 16px 18px; border-top: 1px solid #dae4f4;">Governs how personal data is processed, including by any model provider in the chain &#8211; applies the moment an agent touches customer or employee data, regardless of where the model itself runs.</td>
</tr>
<tr style="background: #f5f8fc;">
<td style="padding: 16px 18px; border-top: 1px solid #dae4f4; border-left: 3px solid #ff9d00; font-weight: bold;"><a style="color: #3181c4; text-decoration: none;" href="https://artificialintelligenceact.eu/" target="_blank" rel="noopener">EU AI Act</a></td>
<td style="padding: 16px 18px; border-top: 1px solid #dae4f4; color: #5b6b7a;">Risk-based regulation of AI systems</td>
<td style="padding: 16px 18px; border-top: 1px solid #dae4f4;">Categorizes AI by its potential danger to society. Simple tools like internal document summarizers face minimal restrictions, whereas agents that make or heavily influence decisions about people face strict legal obligations. This tiering dictates the exact level of human oversight and transparency required.</td>
</tr>
<tr>
<td style="padding: 16px 18px; border-top: 1px solid #dae4f4; border-left: 3px solid #ff9d00; font-weight: bold;"><a style="color: #3181c4; text-decoration: none;" href="https://www.nis-2-directive.com/" target="_blank" rel="noopener">NIS2</a></td>
<td style="padding: 16px 18px; border-top: 1px solid #dae4f4; color: #5b6b7a;">Cybersecurity risk management for critical entities</td>
<td style="padding: 16px 18px; border-top: 1px solid #dae4f4;">Requires access control, logging, and demonstrable accountability across essential and important entities, and makes senior management personally responsible for compliance &#8211; including for AI-driven operations.</td>
</tr>
<tr style="background: #f5f8fc;">
<td style="padding: 16px 18px; border-top: 1px solid #dae4f4; border-left: 3px solid #ff9d00; font-weight: bold;"><a style="color: #3181c4; text-decoration: none;" href="https://www.digital-operational-resilience-act.com/" target="_blank" rel="noopener">DORA</a></td>
<td style="padding: 16px 18px; border-top: 1px solid #dae4f4; color: #5b6b7a;">Operational resilience for financial entities</td>
<td style="padding: 16px 18px; border-top: 1px solid #dae4f4;">Imposes comparable expectations to NIS2 on financial entities, with particular attention to third-party ICT risk &#8211; directly relevant wherever an agent or model runs on outsourced infrastructure.</td>
</tr>
<tr>
<td style="padding: 16px 18px; border-top: 1px solid #dae4f4; border-left: 3px solid #ff9d00; font-weight: bold;"><a style="color: #3181c4; text-decoration: none;" href="https://www.european-cyber-resilience-act.com/" target="_blank" rel="noopener">CRA</a></td>
<td style="padding: 16px 18px; border-top: 1px solid #dae4f4; color: #5b6b7a;">Cybersecurity of products with digital elements</td>
<td style="padding: 16px 18px; border-top: 1px solid #dae4f4;">Introduces mandatory cybersecurity requirements for products with digital elements, including systems that incorporate AI components. Manufacturers must build in secure-by-design principles throughout the product lifecycle before it reaches the market.</td>
</tr>
</tbody>
</table>
</div>
<p>&nbsp;</p>
<h2 id="three-ai-agent-governance-questions"><b>Three AI agent governance questions most organizations haven&#8217;t answered</b></h2>
<p>The risks above are the visible ones, and most organizations will recognize at least one from their own environment. Underneath them sit three harder problems that don’t often come up in discussions and where the genuinely difficult work is. They&#8217;re worth settling before you start building.</p>
<h3><b>Whose authority is the agent acting under?</b></h3>
<p>When an agent does something on behalf of a user, does it use its own permissions or theirs?</p>
<p>An agent acting for a user should be limited to the intersection of what the agent may do and what that user may do. In practice this means token exchange and on-behalf-of flows rather than static service accounts. It&#8217;s the single most important technical decision in agent identity, and it&#8217;s much easier to design in than to retrofit.</p>
<h3><b>What happens when an agent&#8217;s instructions come from an attacker?</b></h3>
<p>Your agent has perfectly scoped permissions and a clean audit trail, however, it reads an email containing text crafted to look like an instruction and decides to follow it. This is prompt injection, and the reason it belongs in a governance conversation is what it does to your threat model.</p>
<p>Identity governance unfortunately can’t solve this problem, but it can limit the damage. If the agent&#8217;s permissions are scoped to the intersection of its role and the user it&#8217;s acting for, an injected instruction can only misuse what&#8217;s inside that narrow overlap. That is why enforcement has to exist at the moment of action, not only at the moment of provisioning.</p>
<h3><b>What happens when AI agents call other agents?</b></h3>
<p>Agent A invokes agent B, which calls agent C. Does authority remain the same at each handoff, or does access just keep piling up so the last agent in the chain ends up able to do more than anyone meant for it to? And if something goes wrong six months from now, could you actually trace back and figure out who allowed it and reconstruct the chain? Most organizations can&#8217;t answer this yet. If your architecture involves multi-agent orchestration, answer it before you scale.</p>
<p>&nbsp;</p>
<h2 id="8-step-ai-governance-framework"><b>How to govern AI agents: an 8-step guide</b></h2>
<p><img loading="lazy" class="alignnone wp-image-15978" src="https://evolveum.com/wp-content/uploads/ai-agent-governance-chain-2row-blog-300x149.png" alt="Diagram of an 8-step framework for governing AI agents, from discovering existing agents and giving each one its own identity through guardrails, ownership, testing, and continuous monitoring." width="940" height="467" srcset="https://evolveum.com/wp-content/uploads/ai-agent-governance-chain-2row-blog-300x149.png 300w, https://evolveum.com/wp-content/uploads/ai-agent-governance-chain-2row-blog-1024x508.png 1024w, https://evolveum.com/wp-content/uploads/ai-agent-governance-chain-2row-blog-768x381.png 768w, https://evolveum.com/wp-content/uploads/ai-agent-governance-chain-2row-blog-1536x762.png 1536w, https://evolveum.com/wp-content/uploads/ai-agent-governance-chain-2row-blog-2048x1015.png 2048w, https://evolveum.com/wp-content/uploads/ai-agent-governance-chain-2row-blog-400x200.png 400w, https://evolveum.com/wp-content/uploads/ai-agent-governance-chain-2row-blog-1320x654.png 1320w, https://evolveum.com/wp-content/uploads/ai-agent-governance-chain-2row-blog-600x297.png 600w" sizes="(max-width: 940px) 100vw, 940px" /></p>
<p>Fortunately, none of these questions require reinventing identity governance. They require applying familiar identity principles to a new type of identity, and the following framework is a practical place to start.</p>
<h3><b>1. Find the agents you already have</b></h3>
<p>Every step below assumes you know an agent exists, so start by confirming that. Survey the business, check what&#8217;s been connected to your SaaS platforms, look at OAuth grants and API key usage, and ask teams directly what they&#8217;ve built. Discovery is uncomfortable and almost always produces surprises. Do it first.</p>
<h3><b>2. Give every agent its own identity</b></h3>
<p>The most common mistake is running agents as extensions of an existing user or application. If you do that, it will be impossible to separate what the person did from what the agent did. Each agent gets its own identity, with a lifecycle that runs from creation through to decommissioning.</p>
<h3><b>3. Authenticate and scope agents like agents, not like users</b></h3>
<p>Avoid shared service accounts and long-lived API keys. Use short-lived credentials and modern standards: <a href="https://www.nist.gov/blogs/cybersecurity-insights/back-future-why-agentic-ai-needs-strong-identity-foundation?utm_source=chatgpt.com" target="_blank" rel="noopener">NIST</a> identifies SPIFFE/SPIRE as a universal approach to authenticating software workloads, while OAuth 2.0 can provide delegated authorization when an agent needs to act on someone&#8217;s behalf. Whatever credentials remain should live in a managed secrets store with automatic rotation, never in a config file or prompt template. Then scope what&#8217;s granted to the task – instead of broad access, restrict the agent to exact actions, specific datasets, and precise APIs.</p>
<h3><b>4. Govern the tools, not just the data<br />
</b></h3>
<p><span style="font-weight: 400;">An agent&#8217;s real capability comes from the tools connected to it. Every integration and MCP server it can reach expands what it can do, and each one (hopefully) arrived through some approval process. Maintain an inventory of what each agent is connected to, who approved it, and what scopes it was granted. This is where most of the risk actually is.</span><b></b></p>
<h3><b>5. Enforce guardrail and human checkpoints where decisions happen</b></h3>
<p>Granting access is only half of the story, as runtime guardrails determine what happens once an agent reaches the data. For high-stakes decisions, keep a human in the loop. Standards like CIBA let the agent pause, request approval through a separate channel, and resume once granted, without anyone watching a screen.</p>
<h3><b>6. Make someone accountable</b></h3>
<p>If we’re treating AI agents as our little work helpers, then every agent needs a designated manager – be it a person or a team &#8211; who approves new permissions, responds to access reviews, answers audit questions, and decides when the agent retires. Ownership should be a required field at creation, and it should be reassigned when people move roles. Without it, everything else on this list eventually degrades.</p>
<h3><b>7. Test before you trust</b></h3>
<p>Run new agents in a sandbox with tightly scoped permissions and evaluate how they behave, ideally putting it up against deliberately hostile input. Grant production access when they&#8217;ve earned it, and treat every subsequent expansion as a decision requiring a rationale and an approval rather than a configuration change. This prevents permissions from silently piling up over time.</p>
<h3><b>8. Review continuously, monitor at runtime, and know how to stop</b></h3>
<p>Agents belong in the same certification campaigns as employees, with owners confirming entitlements are still justified. Log every significant action and the reasoning behind why it was permitted or denied. And know (before you need it) whether revoking an agent&#8217;s credentials kills active sessions immediately or just blocks new ones. When an agent is no longer needed, retire it properly: revoke credentials and tool access, save its logs, and document the shutdown.</p>
<p>&nbsp;</p>
<h2 id="how-ai-agent-governance-works-in-midpoint"><b>How AI agent governance works in midPoint</b></h2>
<p>Building a governance program for AI might sound daunting, but if you already use a mature identity governance platform, you likely have most of the foundations in place. You don&#8217;t necessarily need a separate, specialized tool to govern AI agents; platforms like midPoint can manage them much like any other non-human identity.</p>
<p><b>The Service object type</b> exists precisely for this. Services represent non-person identities, and because they carry credentials in much the same way users do, they can represent machine agents and similar things that behave like humans. Services are also abstract roles, so they can grant privileges to other entities.</p>
<p><b>Archetypes</b> provide the granular typing. An archetype describes what kind of thing an object is, (e.g. &#8220;Employee&#8221;, &#8220;Application&#8221;, &#8220;AI Agent&#8221;) and can be applied to Users, Roles, Orgs, and Services alike. Each archetype can be defined by policies, letting you treat AI agents differently from standard service accounts or human employees without building a parallel governance framework.</p>
<p>MidPoint roles can form <b>hierarchies through inducement relations</b>, and access rights can be assigned and unassigned automatically according to the organizational structure. Roles assigned to an organizational unit can provide access to identities within that unit, while inducements can be used to propagate privileges through a hierarchy.</p>
<p><b>Approval workflows, access certification, and audits</b> are core platform capabilities available to any identity type. Certification campaigns can automatically revoke access if a reviewer denies it, and comprehensive audit logs make meeting regulatory requirements much easier to manage.</p>
<p>Our partner <strong><a href="https://evolveum.com/partners/inalogy/" target="_blank" rel="noopener">Inalogy</a></strong> has extended this approach to address the specific requirements of AI agent governance, and a detailed guide can be found in this <a href="https://inalogy.com/ai-agent-governance-with-midpoint-idm/" target="_blank" rel="noopener">article. </a>They have extended midPoint with these three attributes:</p>
<ul>
<li><b>Business Roles</b> define who the agent is.</li>
<li><b>Application Roles</b> define what it may do, enforcing permissions on every single action rather than just at provisioning.</li>
<li><b>Skill Roles</b> define what it knows. This is an agent-specific tier: a skill is a set of instructions, procedures, and guardrails loaded into the agent&#8217;s context. Without the role, the agent never sees those instructions at all.</li>
</ul>
<p>Inducement ties the three together, as assigning a specific business role automatically triggers the corresponding application access and skill sets.</p>
<p>&nbsp;</p>
<div style="background-color: #9dc2e6; padding: 20px 24px; border-radius: 8px; border: none; outline: none; box-shadow: none; width: 100%; font-family: 'Roboto', sans-serif, Arial; color: #ffffff; display: flex; align-items: center; gap: 20px; box-sizing: border-box; margin: 25px 0;">
<div style="display: flex; align-items: center; flex-shrink: 0;"><img style="width: 65px; height: 65px; border-radius: 50%; object-fit: cover; background: #ffffff; padding: 5px; box-sizing: border-box; border: none;" src="https://evolveum.com/wp-content/uploads/midpoint-circle-logo.png" alt="midPoint logo" /></div>
<div style="width: 2px; background-color: #ffffff; opacity: 0.8; align-self: stretch; flex-shrink: 0;"></div>
<div style="text-align: left; display: flex; flex-direction: column; justify-content: center; gap: 8px; flex-grow: 1;">
<p style="margin: 0 !important; font-size: 16px !important; line-height: 1.4 !important; color: #ffffff !important;">See how Midpoint brings human and non-human identities together under one identity governance layer.</p>
<p style="margin: 0 !important; font-size: 16px !important; color: #ffffff !important;"><a style="color: #ffffff !important; font-weight: bold; text-decoration: underline;" href="https://evolveum.com/midpoint/" target="_blank" rel="noopener">Explore midPoint</a></p>
</div>
</div>
<p>&nbsp;</p>
<h2><b>The payoff of getting it right</b></h2>
<p>AI agents are already inside most environments, and building a governance framework now, while the count is on the lower end, will not only be much easier than trying to play catch up later, it&#8217;s also the right thing to do.</p>
<p>It won’t stop innovation either – <strong><a href="https://larridin.com/state-of-enterprise-ai" target="_blank" rel="noopener">the Larridin State of Enterprise AI Q1 2026 report</a></strong> found that organizations with formalized AI risk and compliance policies are 2.2x more likely to demonstrate ROI than those without. The bottom line is, companies that get AI agent governance right will reap the benefits of deploying AI agents faster, safer, and with more confidence.</p>
<p>&nbsp;</p>
<div>
<h2 style="font-size: 26px; font-weight: bold; color: #1b365d; margin-bottom: 20px;">Frequently Asked Questions</h2>
<details style="border-bottom: 1px solid #e0e0e0; padding: 16px 0; cursor: pointer;">
<summary style="font-size: 18px; font-weight: bold; color: #1b365d; list-style: none; display: flex; align-items: baseline; gap: 10px;"><span style="color: #9dc2e6; font-size: 20px; font-weight: bold; line-height: 1; display: inline-block;">+</span>Is AI agent governance legally required, or is it just best practice?</summary>
<div style="margin-top: 12px; padding-left: 24px; font-size: 16px; line-height: 1.6; color: #4a4a4a;">
<p style="margin: 0;">There isn&#8217;t one single AI-specific law that mandates AI agent governance. Regulations such as the EU AI Act, GDPR, and NIS2 can already create obligations around AI, data protection, security, and accountability. Even when there isn&#8217;t a specific rule for AI agents, existing requirements may still apply. Good governance is therefore both a compliance consideration and a practical security best practice.</p>
</div>
</details>
<details style="border-bottom: 1px solid #e0e0e0; padding: 16px 0; cursor: pointer;">
<summary style="font-size: 18px; font-weight: bold; color: #1b365d; list-style: none; display: flex; align-items: baseline; gap: 10px;"><span style="color: #9dc2e6; font-size: 20px; font-weight: bold; line-height: 1; display: inline-block;">+</span>If an AI agent causes a breach or makes a bad decision, who&#8217;s actually liable?</summary>
<div style="margin-top: 12px; padding-left: 24px; font-size: 16px; line-height: 1.6; color: #4a4a4a;">
<p style="margin: 0;">Responsibility sits with the organization that deployed the agent. Exactly who is liable depends on the circumstances and the laws that apply. That&#8217;s why it&#8217;s important to have comprehensive audit logs of each agent and clear ownership.</p>
</div>
</details>
<details style="border-bottom: 1px solid #e0e0e0; padding: 16px 0; cursor: pointer;">
<summary style="font-size: 18px; font-weight: bold; color: #1b365d; list-style: none; display: flex; align-items: baseline; gap: 10px;"><span style="color: #9dc2e6; font-size: 20px; font-weight: bold; line-height: 1; display: inline-block;">+</span>Should IAM own AI agent governance, or does it belong to security or legal?</summary>
<div style="margin-top: 12px; padding-left: 24px; font-size: 16px; line-height: 1.6; color: #4a4a4a;">
<p style="margin: 0;">In practice it tends to split naturally across teams, with IAM handling the identity lifecycle, while security takes on security and monitoring and legal keeps track of interpreting regulations. AI governance is a joint effort throughout the organization and not something that one department can solve on its own.</p>
</div>
</details>
</div>
<div style="margin-top: 20px;"><img loading="lazy" class="alignleft wp-image-12641" src="https://evolveum.com/wp-content/uploads/evolveum-logo-circle-outline-300x300.png" alt="evolveum identity governance administration logo" width="138" height="138" srcset="https://evolveum.com/wp-content/uploads/evolveum-logo-circle-outline-300x300.png 300w, https://evolveum.com/wp-content/uploads/evolveum-logo-circle-outline-150x150.png 150w, https://evolveum.com/wp-content/uploads/evolveum-logo-circle-outline-250x250.png 250w, https://evolveum.com/wp-content/uploads/evolveum-logo-circle-outline-174x174.png 174w, https://evolveum.com/wp-content/uploads/evolveum-logo-circle-outline-100x100.png 100w, https://evolveum.com/wp-content/uploads/evolveum-logo-circle-outline.png 500w" sizes="(max-width: 138px) 100vw, 138px" /><strong>About Evolveum:</strong><br />
Evolveum is the organization behind midPoint, the leading open source IGA platform recognized as a complete IGA by both Gartner and KuppingerCole. MidPoint bridges the gap between IT and business, making it an ideal choice for organizations seeking digital transformation to enhance security and efficiency.</div>
<p>The post <a rel="nofollow" href="https://evolveum.com/ai-agent-governance-how-to-safely-deploy-and-manage-ai-identities/">AI Agent Governance: How to Safely Deploy and Manage AI Identities</a> appeared first on <a rel="nofollow" href="https://evolveum.com">Evolveum | Open Source Identity Management &amp; Governance</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://evolveum.com/ai-agent-governance-how-to-safely-deploy-and-manage-ai-identities/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Evolveum Recognized as an Innovation Challenger in KuppingerCole&#8217;s 2026 IGA Leadership Compass</title>
		<link>https://evolveum.com/evolveum-recognized-as-an-innovation-challenger-in-kuppingercoles-2026-iga-leadership-compass/</link>
					<comments>https://evolveum.com/evolveum-recognized-as-an-innovation-challenger-in-kuppingercoles-2026-iga-leadership-compass/#respond</comments>
		
		<dc:creator><![CDATA[Mita Chu]]></dc:creator>
		<pubDate>Thu, 06 Aug 2026 15:25:30 +0000</pubDate>
				<category><![CDATA[Evolveum's Identity Management and Governance Blog]]></category>
		<category><![CDATA[News]]></category>
		<guid isPermaLink="false">https://evolveum.com/?p=15782</guid>

					<description><![CDATA[<p>Evolveum has been recognized as an Innovation Challenger in KuppingerCole&#8217;s latest Leadership Compass for Identity Governance and Administration (IGA). As an independent European open-source company, being yet again recognized alongside many of the industry&#8217;s largest and well-established IGA vendors like Sailpoint, IBM, Microsoft and Okta, is an important milestone for us. We believe this recognition <a href="https://evolveum.com/evolveum-recognized-as-an-innovation-challenger-in-kuppingercoles-2026-iga-leadership-compass/" rel="nofollow"><span class="sr-only">Read more about Evolveum Recognized as an Innovation Challenger in KuppingerCole&#8217;s 2026 IGA Leadership Compass</span>[&#8230;]</a></p>
<p>The post <a rel="nofollow" href="https://evolveum.com/evolveum-recognized-as-an-innovation-challenger-in-kuppingercoles-2026-iga-leadership-compass/">Evolveum Recognized as an Innovation Challenger in KuppingerCole&#8217;s 2026 IGA Leadership Compass</a> appeared first on <a rel="nofollow" href="https://evolveum.com">Evolveum | Open Source Identity Management &amp; Governance</a>.</p>
]]></description>
										<content:encoded><![CDATA[<div id="meta-origin" data-coolorigin="https%3A%2F%2Fnextcloud.evolveum.com%2Fcool%2Fclipboard%3FWOPISrc%3Dhttp%253A%252F%252Fnextcloud-aio-apache.nextcloud-aio%253A23973%252Findex.php%252Fapps%252Frichdocuments%252Fwopi%252Ffiles%252F269106_oc55742a9hrf%26ServerId%3D5C0ED57A%26ViewId%3D4%26Tag%3DD654F1D25EC203D9">
<p>Evolveum has been recognized as an Innovation Challenger in KuppingerCole&#8217;s latest Leadership Compass for Identity Governance and Administration (IGA).</p>
<p><a name="__DdeLink__52_259643312"></a>As an independent European open-source company, being yet again recognized alongside many of the industry&#8217;s largest and well-established IGA vendors like Sailpoint, IBM, Microsoft and Okta, is an important milestone for us. We believe this recognition reflects the strength of midPoint, our Identity Governance and Administration platform, and its ability to address complex, enterprise identity challenges.</p>
<h2 class="western"><a name="_pbr5mhtpjdh7"></a><span style="font-size: x-large;"><b>What is the KuppingerCole Leadership Compass?</b></span></h2>
<p>The KuppingerCole Leadership Compass is an independent analyst evaluation designed to help IT and security leaders navigate software markets and identify solutions that best meet their technical and business requirements.</p>
<p>The Leadership Compass evaluates vendors across multiple categories, including Overall, Product, Innovation, and Market Leadership while assessing capabilities such as identity lifecycle management, target system support, self-service and mobile support, audit, reporting and compliance and more.</p>
<h2 class="western"><a name="_ryehupysjb6n"></a><span style="font-size: x-large;"><b>Where midPoint stood out</b></span></h2>
<p>The report highlighted several capabilities that distinguish midPoint in the enterprise IGA market:</p>
<h3 class="western"><a name="_7oj9x8o3itwh"></a><span style="color: #000000;"><span style="font-size: medium;"><b>Simulations for safer deployments</b></span></span></h3>
<p><a href="https://evolveum.com/midpoint/#simulations-section">Simulations</a> are midPoint&#8217;s key differentiator, as highlighted by KuppingerCole. It enables organizations to analyse the impact of configuration and policy changes before implementing them in production, helping reduce deployment risk and identify potential issues before they go to production.</p>
<h3 class="western"><a name="_2lagzhl0kery"></a><span style="color: #000000;"><span style="font-size: medium;"><b>Flexible deployment options</b></span></span></h3>
<p>MidPoint supports a wide range of deployment models, including traditional server installations, containerized environments such as Docker and Kubernetes, and public or private cloud infrastructure. SaaS and managed services are available through a wide range of partners. This flexibility allows organizations to choose the deployment model that best fits their operational and regulatory requirements.</p>
<p><span style="font-size: medium;"><b>Robust identity lifecycle management</b></span></p>
<p>MidPoint provides robust identity lifecycle management, supporting workforce, partner, customer and non-human identities. The platform includes automated provisioning and deprovisioning, real-time synchronisation, schema discovery and extension, and just-in-time (JIT) provisioning to help organisations manage identities of all types throughout their lifecycle.</p>
<h3 class="western"><a name="_7iiuon8lpqv2"></a><span style="color: #000000;"><span style="font-size: medium;"><b>Comprehensive access governance</b></span></span></h3>
<p>MidPoint&#8217;s mature access governance capabilities includes centralised role management, hierarchical role models, role discovery and role mining. Smart Roles allow access policies to adapt dynamically based on organisational structure, user attributes or contextual information, helping organisations build scalable and maintainable role-based access control (RBAC) that adapts to organisational structures and user attributes.</p>
<h3 class="western"><a name="_b09932qpmt0i"></a><span style="color: #000000;"><span style="font-size: medium;"><b>Broad integration capabilities</b></span></span></h3>
<p>The platform offers an extensive connector ecosystem covering LDAP, Active Directory, relational databases, CSV, and numerous SaaS platforms, including Microsoft Entra ID, AWS, Google Workspace, Jira, Slack, ServiceNow, SAP SuccessFactors, and Microsoft 365. In the next release scheduled for October 2026, we will be releasing midPilot, an AI application onboarding assistant designed to help with integrating new applications more quickly while maintaining strong governance.</p>
<h2 class="western"><a name="_vt04d3silxc5"></a><span style="font-size: x-large;"><b>Looking ahead</b></span></h2>
<p>We&#8217;re proud to be recognised as an Innovation Challenger and encouraged that the report highlights many of the technical capabilities we&#8217;ve invested in over the years.</p>
<p>At the same time, we see this recognition as another step in our journey. The report highlights opportunities for further development, many of which are already reflected in our roadmap. With innovations such as midPilot, we&#8217;re excited to continue evolving midPoint and building on this recognition in future Leadership Compass evaluations.</p>
<p><strong><a href="https://www.kuppingercole.com/research/lc80864/identity-governance-and-administration-iga">Read the report </a></strong></p>
</div>
<p>The post <a rel="nofollow" href="https://evolveum.com/evolveum-recognized-as-an-innovation-challenger-in-kuppingercoles-2026-iga-leadership-compass/">Evolveum Recognized as an Innovation Challenger in KuppingerCole&#8217;s 2026 IGA Leadership Compass</a> appeared first on <a rel="nofollow" href="https://evolveum.com">Evolveum | Open Source Identity Management &amp; Governance</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://evolveum.com/evolveum-recognized-as-an-innovation-challenger-in-kuppingercoles-2026-iga-leadership-compass/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
