  <?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>[NEW WEBSITE] - Blogs</title>
    <link>/en/blogs</link>
    <description>Stay informed and inspired with our engaging blog content. Explore a diverse range of topics, from expert advice to in-depth insights.</description>
    <language>en</language>
    <pubDate>Fri, 31 Jul 2026 15:16:16 GMT</pubDate>
    <dc:date>2026-07-31T15:16:16Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Modernizing High‑Risk Legacy Software with AI in a Controlled Way</title>
      <link>/en/blogs/modernizing-high-risk-legacy-software-with-ai-in-a-controlled-way</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="/en/blogs/modernizing-high-risk-legacy-software-with-ai-in-a-controlled-way" title="" class="hs-featured-image-link"&gt; &lt;img src="/hubfs/202607_Apps_Hubspot_Blogpost_Modernizing%20High%20Risk%20Legacy%20Software%20with%20AI%20in%20a%20Controlled%20Way_EN_1920x1080px-1.png" alt="Modernizing High‑Risk Legacy Software with AI in a Controlled Way" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;span style="line-height: 23.75px;"&gt;This is particularly true in social security, where core systems often embody decades of legislation, policy changes, and highly specialized business rules. &lt;/span&gt;&lt;span style="line-height: 21.25px;"&gt;The system we modernized determines &lt;/span&gt;&lt;strong&gt;&lt;span style="line-height: 21.25px;"&gt;social security contributions&lt;/span&gt;&lt;/strong&gt;&lt;span style="line-height: 21.25px;"&gt;, which directly influence citizens’ rights and entitlements, including pension outcomes. &lt;/span&gt;&lt;span style="line-height: 23.75px;"&gt;Application modernization in such an environment is therefore not just a technology challenge; it is a matter of &lt;/span&gt;&lt;strong&gt;&lt;span style="line-height: 23.75px;"&gt;risk management, accountability, and trust&lt;/span&gt;&lt;/strong&gt;&lt;span style="line-height: 23.75px;"&gt;.&lt;/span&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="/en/blogs/modernizing-high-risk-legacy-software-with-ai-in-a-controlled-way" title="" class="hs-featured-image-link"&gt; &lt;img src="/hubfs/202607_Apps_Hubspot_Blogpost_Modernizing%20High%20Risk%20Legacy%20Software%20with%20AI%20in%20a%20Controlled%20Way_EN_1920x1080px-1.png" alt="Modernizing High‑Risk Legacy Software with AI in a Controlled Way" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;span style="line-height: 23.75px;"&gt;This is particularly true in social security, where core systems often embody decades of legislation, policy changes, and highly specialized business rules. &lt;/span&gt;&lt;span style="line-height: 21.25px;"&gt;The system we modernized determines &lt;/span&gt;&lt;strong&gt;&lt;span style="line-height: 21.25px;"&gt;social security contributions&lt;/span&gt;&lt;/strong&gt;&lt;span style="line-height: 21.25px;"&gt;, which directly influence citizens’ rights and entitlements, including pension outcomes. &lt;/span&gt;&lt;span style="line-height: 23.75px;"&gt;Application modernization in such an environment is therefore not just a technology challenge; it is a matter of &lt;/span&gt;&lt;strong&gt;&lt;span style="line-height: 23.75px;"&gt;risk management, accountability, and trust&lt;/span&gt;&lt;/strong&gt;&lt;span style="line-height: 23.75px;"&gt;.&lt;/span&gt;&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=2655225&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fwww.cegeka.com%2Fen%2Fblogs%2Fmodernizing-high-risk-legacy-software-with-ai-in-a-controlled-way&amp;amp;bu=https%253A%252F%252Fwww.cegeka.com%252Fen%252Fblogs&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Data &amp; AI</category>
      <category>* Application Services</category>
      <category>* Software Factory</category>
      <pubDate>Wed, 29 Jul 2026 12:19:25 GMT</pubDate>
      <guid>/en/blogs/modernizing-high-risk-legacy-software-with-ai-in-a-controlled-way</guid>
      <dc:date>2026-07-29T12:19:25Z</dc:date>
      <dc:creator>Bieke Meeussen</dc:creator>
    </item>
    <item>
      <title>WSO Web Shell and FreeDNS Abuse: Fingerprinting a threat actor's infrastructure</title>
      <link>/en/blogs/wso-web-shell-and-freedns-abuse-fingerprinting-a-threat-actors-infrastructure</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="/en/blogs/wso-web-shell-and-freedns-abuse-fingerprinting-a-threat-actors-infrastructure" title="" class="hs-featured-image-link"&gt; &lt;img src="/hubfs/Hubspot%201920x1080px.png" alt="WSO Web shell and FreeDNS Abuse: Fingerprinting the infrastructure of a threat actor" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;span&gt;During the investigation of an incident&lt;/span&gt;&lt;span&gt;, the CSIRT (Computer Security Incident Response Team) of * Modern SOC discovered &lt;/span&gt;&lt;span&gt;a threat actor-controlled infrastructure that was publicly exposed through a WSO (&lt;/span&gt;&lt;span&gt;web shell by ORb&lt;/span&gt;&lt;span&gt;) PHP web shell.&lt;/span&gt;&lt;span&gt; The investigation revealed that a threat actor was abusing 'FreeDNS' services of a DNS provider to register multiple subdomains under legitimate parent domains, without the domain owner’s approval. All these subdomains resolved to the same infrastructure, which hosted web shells and other malicious files that were actively used in phishing campaigns.&lt;/span&gt;&lt;/p&gt; 
&lt;p style="text-align: justify;"&gt;&lt;span&gt;This blog, authored by &lt;strong&gt;Cristina Aldea&lt;/strong&gt; and &lt;strong&gt;Christos Katopis&lt;/strong&gt; from * CSIRT, provides both an overview and a detailed report on the threat actor’s infrastructure as well as the malicious files that were located in their server.&lt;/span&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="/en/blogs/wso-web-shell-and-freedns-abuse-fingerprinting-a-threat-actors-infrastructure" title="" class="hs-featured-image-link"&gt; &lt;img src="/hubfs/Hubspot%201920x1080px.png" alt="WSO Web shell and FreeDNS Abuse: Fingerprinting the infrastructure of a threat actor" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;span&gt;During the investigation of an incident&lt;/span&gt;&lt;span&gt;, the CSIRT (Computer Security Incident Response Team) of * Modern SOC discovered &lt;/span&gt;&lt;span&gt;a threat actor-controlled infrastructure that was publicly exposed through a WSO (&lt;/span&gt;&lt;span&gt;web shell by ORb&lt;/span&gt;&lt;span&gt;) PHP web shell.&lt;/span&gt;&lt;span&gt; The investigation revealed that a threat actor was abusing 'FreeDNS' services of a DNS provider to register multiple subdomains under legitimate parent domains, without the domain owner’s approval. All these subdomains resolved to the same infrastructure, which hosted web shells and other malicious files that were actively used in phishing campaigns.&lt;/span&gt;&lt;/p&gt; 
&lt;p style="text-align: justify;"&gt;&lt;span&gt;This blog, authored by &lt;strong&gt;Cristina Aldea&lt;/strong&gt; and &lt;strong&gt;Christos Katopis&lt;/strong&gt; from * CSIRT, provides both an overview and a detailed report on the threat actor’s infrastructure as well as the malicious files that were located in their server.&lt;/span&gt;&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=2655225&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fwww.cegeka.com%2Fen%2Fblogs%2Fwso-web-shell-and-freedns-abuse-fingerprinting-a-threat-actors-infrastructure&amp;amp;bu=https%253A%252F%252Fwww.cegeka.com%252Fen%252Fblogs&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Cyber security &amp; Networking</category>
      <category>Threat Analysis Report</category>
      <pubDate>Thu, 23 Jul 2026 13:45:45 GMT</pubDate>
      <guid>/en/blogs/wso-web-shell-and-freedns-abuse-fingerprinting-a-threat-actors-infrastructure</guid>
      <dc:date>2026-07-23T13:45:45Z</dc:date>
      <dc:creator>Christos Katopis</dc:creator>
    </item>
    <item>
      <title>Turning hardware circularity into a strategic advantage for sustainable growth</title>
      <link>/en/blogs/hardware-circularity-strategic-advantage</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="/en/blogs/hardware-circularity-strategic-advantage" title="" class="hs-featured-image-link"&gt; &lt;img src="/hubfs/2607-ESG_Hardware_circularity_visual_1920x1080px%202-1.png" alt="Hardware circularity graphic with * CTO Luc Greefs, highlighting sustainability, CO2 neutrality by 2030, and responsible reuse and recycling" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;At *, sustainability is a core business principle, not a side initiative. As a global IT services provider, we see technology as a driver of positive change, especially in our data centers, where performance, energy use, and environmental responsibility intersect.&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="/en/blogs/hardware-circularity-strategic-advantage" title="" class="hs-featured-image-link"&gt; &lt;img src="/hubfs/2607-ESG_Hardware_circularity_visual_1920x1080px%202-1.png" alt="Hardware circularity graphic with * CTO Luc Greefs, highlighting sustainability, CO2 neutrality by 2030, and responsible reuse and recycling" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;At *, sustainability is a core business principle, not a side initiative. As a global IT services provider, we see technology as a driver of positive change, especially in our data centers, where performance, energy use, and environmental responsibility intersect.&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=2655225&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fwww.cegeka.com%2Fen%2Fblogs%2Fhardware-circularity-strategic-advantage&amp;amp;bu=https%253A%252F%252Fwww.cegeka.com%252Fen%252Fblogs&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>ESG</category>
      <pubDate>Wed, 22 Jul 2026 11:51:19 GMT</pubDate>
      <author>luc.greefs@cegeka.com (Luc Greefs)</author>
      <guid>/en/blogs/hardware-circularity-strategic-advantage</guid>
      <dc:date>2026-07-22T11:51:19Z</dc:date>
    </item>
    <item>
      <title>Essential 5-Step Guide to Mature Identity Governance</title>
      <link>/en/blogs/essential-5-step-guide-to-mature-identity-governance</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="/en/blogs/essential-5-step-guide-to-mature-identity-governance" title="" class="hs-featured-image-link"&gt; &lt;img src="/hubfs/0.0%20*%20(new)/1.%20Visuals/Website/Cybersecurity_Elimity_webinar_blog_thumbnail_1920x1080.png" alt="Essential 5-Step Guide to Mature Identity Governance" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;Are you searching for a streamlined and cost-effective method to manage user access without the intricacies of a full-scale Identity Governance and Administration (IGA) suite?&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="/en/blogs/essential-5-step-guide-to-mature-identity-governance" title="" class="hs-featured-image-link"&gt; &lt;img src="/hubfs/0.0%20*%20(new)/1.%20Visuals/Website/Cybersecurity_Elimity_webinar_blog_thumbnail_1920x1080.png" alt="Essential 5-Step Guide to Mature Identity Governance" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;Are you searching for a streamlined and cost-effective method to manage user access without the intricacies of a full-scale Identity Governance and Administration (IGA) suite?&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=2655225&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fwww.cegeka.com%2Fen%2Fblogs%2Fessential-5-step-guide-to-mature-identity-governance&amp;amp;bu=https%253A%252F%252Fwww.cegeka.com%252Fen%252Fblogs&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Cyber security &amp; Networking</category>
      <pubDate>Fri, 17 Jul 2026 08:35:58 GMT</pubDate>
      <guid>/en/blogs/essential-5-step-guide-to-mature-identity-governance</guid>
      <dc:date>2026-07-17T08:35:58Z</dc:date>
      <dc:creator>Patricia O’Brien</dc:creator>
    </item>
    <item>
      <title>Scaling AI Agents: Why Not All Agents Should Be Managed the Same Way</title>
      <link>/en/blogs/scaling-ai-agents-why-not-all-agents-should-be-managed-the-same-way</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="/en/blogs/scaling-ai-agents-why-not-all-agents-should-be-managed-the-same-way" title="" class="hs-featured-image-link"&gt; &lt;img src="/hubfs/Managed_Agents_2_blog_thumbnail_1920x1080px_EN.png" alt="Scaling AI Agents: Why Not All Agents Should Be Managed the Same Way" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;span style="line-height: 22.0083px;"&gt;That rapid growth introduces a challenge many organizations underestimate. Building an AI agent is relatively easy. Managing dozens or even hundreds of agents as they become more widely adopted is where complexity starts to emerge.&lt;/span&gt;&lt;/p&gt; 
&lt;p&gt;&lt;span style="line-height: 22.0083px;"&gt;The reality is simple: &lt;/span&gt;&lt;strong&gt;&lt;span style="line-height: 22.0083px;"&gt;not all agents should be managed in the same way.&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt; 
&lt;p&gt;&lt;span style="line-height: 22.0083px;"&gt;Yet many organizations fall into one of two extremes. They either apply the same governance model to every agent, creating unnecessary friction, or they apply little to no governance at all until risks begin to surface.&lt;/span&gt;&lt;/p&gt; 
&lt;p&gt;&lt;span style="line-height: 22.0083px;"&gt;Neither approach scales.&lt;/span&gt;&lt;/p&gt; 
&lt;p&gt;&lt;span style="line-height: 22.0083px;"&gt;To strike the right balance, organizations need a framework that connects how agents are used, the level of risk they introduce, and the amount of governance they require.&lt;/span&gt;&lt;/p&gt; 
&lt;p&gt;&lt;span style="line-height: 22.0083px;"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;div class="hs-cta-embed hs-cta-simple-placeholder hs-cta-embed-216720779644" style="max-width:100%; max-height:100%; width:1920px;height:540px"&gt; 
 &lt;a href="/hs/cta/wi/redirect?encryptedPayload=AVxigLKwdjxKvU%2FcwhOTklLJ4vaoka4fXsO3x9Zi3SUybP19XNK8kcikzflTYwnycYLfsILmT14Js6tmJ9P3sTbdCCh6z%2BpAiImjuhlAOVahZO6DEVciO21aB2%2FY0dL9WCWQSUwSPpYi1KABnedvEFLjiBmA7WkPmq2M2qz1QDv47U0tkgzIbcqE9bcsf7Vz4pfq9TvzlZPP%2F6roLt%2FJdpb%2FcEllx5a%2F0G57fcZnvtICJnlUbT%2FYfGeWzTOpocAb4DAFOflPMu%2Bxw33ztQ%3D%3D&amp;amp;webInteractiveContentId=216720779644&amp;amp;portalId=2655225"&gt; &lt;img alt="DeX_Governing_AI_Agents_at_Scale_HubSpot_CTA_1920x540px (1)" src="https://no-cache.hubspot.com/cta/default/2655225/interactive-216720779644.png" style="height: 100%; width: 100%; object-fit: fill"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;br&gt;
&lt;p&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="/en/blogs/scaling-ai-agents-why-not-all-agents-should-be-managed-the-same-way" title="" class="hs-featured-image-link"&gt; &lt;img src="/hubfs/Managed_Agents_2_blog_thumbnail_1920x1080px_EN.png" alt="Scaling AI Agents: Why Not All Agents Should Be Managed the Same Way" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;span style="line-height: 22.0083px;"&gt;That rapid growth introduces a challenge many organizations underestimate. Building an AI agent is relatively easy. Managing dozens or even hundreds of agents as they become more widely adopted is where complexity starts to emerge.&lt;/span&gt;&lt;/p&gt; 
&lt;p&gt;&lt;span style="line-height: 22.0083px;"&gt;The reality is simple: &lt;/span&gt;&lt;strong&gt;&lt;span style="line-height: 22.0083px;"&gt;not all agents should be managed in the same way.&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt; 
&lt;p&gt;&lt;span style="line-height: 22.0083px;"&gt;Yet many organizations fall into one of two extremes. They either apply the same governance model to every agent, creating unnecessary friction, or they apply little to no governance at all until risks begin to surface.&lt;/span&gt;&lt;/p&gt; 
&lt;p&gt;&lt;span style="line-height: 22.0083px;"&gt;Neither approach scales.&lt;/span&gt;&lt;/p&gt; 
&lt;p&gt;&lt;span style="line-height: 22.0083px;"&gt;To strike the right balance, organizations need a framework that connects how agents are used, the level of risk they introduce, and the amount of governance they require.&lt;/span&gt;&lt;/p&gt; 
&lt;p&gt;&lt;span style="line-height: 22.0083px;"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;div class="hs-cta-embed hs-cta-simple-placeholder hs-cta-embed-216720779644" style="max-width:100%; max-height:100%; width:1920px;height:540px"&gt; 
 &lt;a href="/hs/cta/wi/redirect?encryptedPayload=AVxigLKwdjxKvU%2FcwhOTklLJ4vaoka4fXsO3x9Zi3SUybP19XNK8kcikzflTYwnycYLfsILmT14Js6tmJ9P3sTbdCCh6z%2BpAiImjuhlAOVahZO6DEVciO21aB2%2FY0dL9WCWQSUwSPpYi1KABnedvEFLjiBmA7WkPmq2M2qz1QDv47U0tkgzIbcqE9bcsf7Vz4pfq9TvzlZPP%2F6roLt%2FJdpb%2FcEllx5a%2F0G57fcZnvtICJnlUbT%2FYfGeWzTOpocAb4DAFOflPMu%2Bxw33ztQ%3D%3D&amp;amp;webInteractiveContentId=216720779644&amp;amp;portalId=2655225"&gt; &lt;img alt="DeX_Governing_AI_Agents_at_Scale_HubSpot_CTA_1920x540px (1)" src="https://no-cache.hubspot.com/cta/default/2655225/interactive-216720779644.png" style="height: 100%; width: 100%; object-fit: fill"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;br&gt;
&lt;p&gt;&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=2655225&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fwww.cegeka.com%2Fen%2Fblogs%2Fscaling-ai-agents-why-not-all-agents-should-be-managed-the-same-way&amp;amp;bu=https%253A%252F%252Fwww.cegeka.com%252Fen%252Fblogs&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Digital Employee Xperience</category>
      <pubDate>Mon, 13 Jul 2026 14:34:43 GMT</pubDate>
      <guid>/en/blogs/scaling-ai-agents-why-not-all-agents-should-be-managed-the-same-way</guid>
      <dc:date>2026-07-13T14:34:43Z</dc:date>
      <dc:creator>Vincent Vandersmissen</dc:creator>
    </item>
    <item>
      <title>Avoiding Agent Sprawl: A Practical Framework for Control and Scale</title>
      <link>/en/blogs/avoiding-agent-sprawl-a-practical-framework-for-control-and-scale</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="/en/blogs/avoiding-agent-sprawl-a-practical-framework-for-control-and-scale" title="" class="hs-featured-image-link"&gt; &lt;img src="/hubfs/DeX_Avoiding_Agent_Sprawl_blog_thumbnail_1920x1080px_EN.png" alt="Avoiding Agent Sprawl: A Practical Framework for Control and Scale" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;span style="line-height: 22.0083px;"&gt;The pattern itself is familiar.&lt;/span&gt;&lt;/p&gt; 
&lt;p&gt;&lt;span style="line-height: 22.0083px;"&gt;Organizations have seen it before with &lt;/span&gt;&lt;strong&gt;&lt;span style="line-height: 22.0083px;"&gt;SharePoint&lt;/span&gt;&lt;/strong&gt;&lt;span style="line-height: 22.0083px;"&gt;, &lt;/span&gt;&lt;strong&gt;&lt;span style="line-height: 22.0083px;"&gt;Microsoft Teams&lt;/span&gt;&lt;/strong&gt;&lt;span style="line-height: 22.0083px;"&gt;, and the &lt;/span&gt;&lt;strong&gt;&lt;span style="line-height: 22.0083px;"&gt;Power Platform&lt;/span&gt;&lt;/strong&gt;&lt;span style="line-height: 22.0083px;"&gt;. Each wave expanded access, accelerated innovation, and eventually introduced the same downside: too much growth without enough visibility, ownership, or control. The result was complexity, duplication, and governance gaps that had to be addressed later.&lt;/span&gt;&lt;/p&gt; 
&lt;p&gt;&lt;span style="line-height: 22.0083px;"&gt;&lt;br&gt;&lt;em&gt;Figure 1: Sprawl history across digital workplace applications&lt;/em&gt;&lt;br&gt;&lt;/span&gt;&lt;/p&gt; 
&lt;p&gt;&lt;span style="line-height: 22.0083px;"&gt;Now the same pattern is emerging with AI agents, only faster and with far greater business impact.&amp;nbsp;&lt;/span&gt;&lt;/p&gt; 
&lt;p&gt;&lt;span style="line-height: 22.0083px;"&gt;&lt;a href="https://www.gartner.com/en/newsroom/press-releases/2026-04-28-gartner-identifies-six-steps-to-manage-artificial-intelligence-agent-sprawl"&gt;&lt;u&gt;According to Gartner&lt;/u&gt;&lt;/a&gt;, &lt;em&gt;"By 2028, a typical enterprise could have over 150,000 AI agents in use."&lt;/em&gt;&lt;br style="white-space-collapse: preserve;"&gt;Yet only &lt;strong&gt;13% of organizations believe they have the right governance in place.&lt;/strong&gt;&lt;/span&gt;&lt;/p&gt; 
&lt;p&gt;&lt;span style="line-height: 22.0083px;"&gt;That is what leads to &lt;strong&gt;agent sprawl&lt;/strong&gt;: the rapid and uncontrolled proliferation of AI agents across the organization.&lt;/span&gt;&lt;/p&gt; 
&lt;p&gt;&lt;span style="line-height: 22.0083px;"&gt;The challenge is not agent creation itself, but how to govern agents once they begin to scale. Organizations that act early can avoid repeating the mistakes of earlier technology waves and put the right model in place before sprawl becomes costly to reverse.&lt;/span&gt;&lt;/p&gt; 
&lt;p&gt;&lt;span style="line-height: 22.0083px;"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;div class="hs-cta-embed hs-cta-simple-placeholder hs-cta-embed-216720779644" style="max-width:100%; max-height:100%; width:1920px;height:540px"&gt; 
 &lt;a href="/hs/cta/wi/redirect?encryptedPayload=AVxigLKwdjxKvU%2FcwhOTklLJ4vaoka4fXsO3x9Zi3SUybP19XNK8kcikzflTYwnycYLfsILmT14Js6tmJ9P3sTbdCCh6z%2BpAiImjuhlAOVahZO6DEVciO21aB2%2FY0dL9WCWQSUwSPpYi1KABnedvEFLjiBmA7WkPmq2M2qz1QDv47U0tkgzIbcqE9bcsf7Vz4pfq9TvzlZPP%2F6roLt%2FJdpb%2FcEllx5a%2F0G57fcZnvtICJnlUbT%2FYfGeWzTOpocAb4DAFOflPMu%2Bxw33ztQ%3D%3D&amp;amp;webInteractiveContentId=216720779644&amp;amp;portalId=2655225"&gt; &lt;img alt="DeX_Governing_AI_Agents_at_Scale_HubSpot_CTA_1920x540px (1)" src="https://no-cache.hubspot.com/cta/default/2655225/interactive-216720779644.png" style="height: 100%; width: 100%; object-fit: fill"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="/en/blogs/avoiding-agent-sprawl-a-practical-framework-for-control-and-scale" title="" class="hs-featured-image-link"&gt; &lt;img src="/hubfs/DeX_Avoiding_Agent_Sprawl_blog_thumbnail_1920x1080px_EN.png" alt="Avoiding Agent Sprawl: A Practical Framework for Control and Scale" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;span style="line-height: 22.0083px;"&gt;The pattern itself is familiar.&lt;/span&gt;&lt;/p&gt; 
&lt;p&gt;&lt;span style="line-height: 22.0083px;"&gt;Organizations have seen it before with &lt;/span&gt;&lt;strong&gt;&lt;span style="line-height: 22.0083px;"&gt;SharePoint&lt;/span&gt;&lt;/strong&gt;&lt;span style="line-height: 22.0083px;"&gt;, &lt;/span&gt;&lt;strong&gt;&lt;span style="line-height: 22.0083px;"&gt;Microsoft Teams&lt;/span&gt;&lt;/strong&gt;&lt;span style="line-height: 22.0083px;"&gt;, and the &lt;/span&gt;&lt;strong&gt;&lt;span style="line-height: 22.0083px;"&gt;Power Platform&lt;/span&gt;&lt;/strong&gt;&lt;span style="line-height: 22.0083px;"&gt;. Each wave expanded access, accelerated innovation, and eventually introduced the same downside: too much growth without enough visibility, ownership, or control. The result was complexity, duplication, and governance gaps that had to be addressed later.&lt;/span&gt;&lt;/p&gt; 
&lt;p&gt;&lt;span style="line-height: 22.0083px;"&gt;&lt;br&gt;&lt;em&gt;Figure 1: Sprawl history across digital workplace applications&lt;/em&gt;&lt;br&gt;&lt;/span&gt;&lt;/p&gt; 
&lt;p&gt;&lt;span style="line-height: 22.0083px;"&gt;Now the same pattern is emerging with AI agents, only faster and with far greater business impact.&amp;nbsp;&lt;/span&gt;&lt;/p&gt; 
&lt;p&gt;&lt;span style="line-height: 22.0083px;"&gt;&lt;a href="https://www.gartner.com/en/newsroom/press-releases/2026-04-28-gartner-identifies-six-steps-to-manage-artificial-intelligence-agent-sprawl"&gt;&lt;u&gt;According to Gartner&lt;/u&gt;&lt;/a&gt;, &lt;em&gt;"By 2028, a typical enterprise could have over 150,000 AI agents in use."&lt;/em&gt;&lt;br style="white-space-collapse: preserve;"&gt;Yet only &lt;strong&gt;13% of organizations believe they have the right governance in place.&lt;/strong&gt;&lt;/span&gt;&lt;/p&gt; 
&lt;p&gt;&lt;span style="line-height: 22.0083px;"&gt;That is what leads to &lt;strong&gt;agent sprawl&lt;/strong&gt;: the rapid and uncontrolled proliferation of AI agents across the organization.&lt;/span&gt;&lt;/p&gt; 
&lt;p&gt;&lt;span style="line-height: 22.0083px;"&gt;The challenge is not agent creation itself, but how to govern agents once they begin to scale. Organizations that act early can avoid repeating the mistakes of earlier technology waves and put the right model in place before sprawl becomes costly to reverse.&lt;/span&gt;&lt;/p&gt; 
&lt;p&gt;&lt;span style="line-height: 22.0083px;"&gt;&lt;/span&gt;&lt;/p&gt;
&lt;div class="hs-cta-embed hs-cta-simple-placeholder hs-cta-embed-216720779644" style="max-width:100%; max-height:100%; width:1920px;height:540px"&gt; 
 &lt;a href="/hs/cta/wi/redirect?encryptedPayload=AVxigLKwdjxKvU%2FcwhOTklLJ4vaoka4fXsO3x9Zi3SUybP19XNK8kcikzflTYwnycYLfsILmT14Js6tmJ9P3sTbdCCh6z%2BpAiImjuhlAOVahZO6DEVciO21aB2%2FY0dL9WCWQSUwSPpYi1KABnedvEFLjiBmA7WkPmq2M2qz1QDv47U0tkgzIbcqE9bcsf7Vz4pfq9TvzlZPP%2F6roLt%2FJdpb%2FcEllx5a%2F0G57fcZnvtICJnlUbT%2FYfGeWzTOpocAb4DAFOflPMu%2Bxw33ztQ%3D%3D&amp;amp;webInteractiveContentId=216720779644&amp;amp;portalId=2655225"&gt; &lt;img alt="DeX_Governing_AI_Agents_at_Scale_HubSpot_CTA_1920x540px (1)" src="https://no-cache.hubspot.com/cta/default/2655225/interactive-216720779644.png" style="height: 100%; width: 100%; object-fit: fill"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=2655225&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fwww.cegeka.com%2Fen%2Fblogs%2Favoiding-agent-sprawl-a-practical-framework-for-control-and-scale&amp;amp;bu=https%253A%252F%252Fwww.cegeka.com%252Fen%252Fblogs&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Digital Employee Xperience</category>
      <pubDate>Mon, 13 Jul 2026 14:08:40 GMT</pubDate>
      <guid>/en/blogs/avoiding-agent-sprawl-a-practical-framework-for-control-and-scale</guid>
      <dc:date>2026-07-13T14:08:40Z</dc:date>
      <dc:creator>Vincent Vandersmissen</dc:creator>
    </item>
    <item>
      <title>Enhancing Atlassian Security and Governance: Transitioning from Bot Users to Service Accounts</title>
      <link>/en/blogs/enhancing-atlassian-security-governance-from-bot-users-to-service-accounts</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="/en/blogs/enhancing-atlassian-security-governance-from-bot-users-to-service-accounts" title="" class="hs-featured-image-link"&gt; &lt;img src="/hubfs/Enhancing%20Atlassian%20Security%20and%20Governance_blog_thumbnail_1920x1080px.png" alt="Enhancing Atlassian Security and Governance: Transitioning from Bot Users to Service Accounts" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;For years, the “Standard Operating Procedure” for Atlassian integrations was simple: create a fake user called &lt;code&gt;jira_bot&lt;/code&gt;, buy it a license, and generate an API token that lasts indefinitely. It worked, it was convenient, and plenty of teams used it.&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="/en/blogs/enhancing-atlassian-security-governance-from-bot-users-to-service-accounts" title="" class="hs-featured-image-link"&gt; &lt;img src="/hubfs/Enhancing%20Atlassian%20Security%20and%20Governance_blog_thumbnail_1920x1080px.png" alt="Enhancing Atlassian Security and Governance: Transitioning from Bot Users to Service Accounts" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;For years, the “Standard Operating Procedure” for Atlassian integrations was simple: create a fake user called &lt;code&gt;jira_bot&lt;/code&gt;, buy it a license, and generate an API token that lasts indefinitely. It worked, it was convenient, and plenty of teams used it.&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=2655225&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fwww.cegeka.com%2Fen%2Fblogs%2Fenhancing-atlassian-security-governance-from-bot-users-to-service-accounts&amp;amp;bu=https%253A%252F%252Fwww.cegeka.com%252Fen%252Fblogs&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Quality Engineering</category>
      <pubDate>Mon, 13 Jul 2026 08:25:21 GMT</pubDate>
      <guid>/en/blogs/enhancing-atlassian-security-governance-from-bot-users-to-service-accounts</guid>
      <dc:date>2026-07-13T08:25:21Z</dc:date>
      <dc:creator>Bram Geukens</dc:creator>
    </item>
    <item>
      <title>AI used as a human-centered force for good</title>
      <link>/en/blogs/ai-used-as-a-human-centered-force-for-good</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="/en/blogs/ai-used-as-a-human-centered-force-for-good" title="" class="hs-featured-image-link"&gt; &lt;img src="/hubfs/2607-ESG_visual_1920x1080px-1.png" alt="AI used as a human-centered force for good" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;span style="font-weight: bold;"&gt;RotterMaatje &lt;/span&gt;is a great example of responsible technology in practice. Developed by colleagues from * Netherlands in collaboration with &lt;a href="https://www.pauluskerkrotterdam.nl/"&gt;Pauluskerk Rotterdam&lt;/a&gt; and &lt;a href="https://www.rotterdamuas.com/"&gt;Rotterdam University of Applied Sciences&lt;/a&gt;, the initiative demonstrates how artificial intelligence (AI) can be used to address social challenges and expand access for vulnerable communities.&amp;nbsp;&lt;/p&gt; 
&lt;p&gt;In a world where digital transformation can widen inequalities, RotterMaatje takes a different approach. Rather than optimizing processes alone, it puts people first. The chatbot helps individuals experiencing homelessness, volunteers navigating complex support systems, and residents seeking reliable information about healthcare, shelter, legal assistance, and social services.&amp;nbsp;&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="/en/blogs/ai-used-as-a-human-centered-force-for-good" title="" class="hs-featured-image-link"&gt; &lt;img src="/hubfs/2607-ESG_visual_1920x1080px-1.png" alt="AI used as a human-centered force for good" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;span style="font-weight: bold;"&gt;RotterMaatje &lt;/span&gt;is a great example of responsible technology in practice. Developed by colleagues from * Netherlands in collaboration with &lt;a href="https://www.pauluskerkrotterdam.nl/"&gt;Pauluskerk Rotterdam&lt;/a&gt; and &lt;a href="https://www.rotterdamuas.com/"&gt;Rotterdam University of Applied Sciences&lt;/a&gt;, the initiative demonstrates how artificial intelligence (AI) can be used to address social challenges and expand access for vulnerable communities.&amp;nbsp;&lt;/p&gt; 
&lt;p&gt;In a world where digital transformation can widen inequalities, RotterMaatje takes a different approach. Rather than optimizing processes alone, it puts people first. The chatbot helps individuals experiencing homelessness, volunteers navigating complex support systems, and residents seeking reliable information about healthcare, shelter, legal assistance, and social services.&amp;nbsp;&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=2655225&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fwww.cegeka.com%2Fen%2Fblogs%2Fai-used-as-a-human-centered-force-for-good&amp;amp;bu=https%253A%252F%252Fwww.cegeka.com%252Fen%252Fblogs&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>ESG</category>
      <pubDate>Thu, 09 Jul 2026 11:36:46 GMT</pubDate>
      <guid>/en/blogs/ai-used-as-a-human-centered-force-for-good</guid>
      <dc:date>2026-07-09T11:36:46Z</dc:date>
      <dc:creator>Kim Wilmes</dc:creator>
    </item>
    <item>
      <title>How do you integrate and manage business-critical applications outside your ERP?</title>
      <link>/en/blogs/how-do-you-integrate-and-manage-business-critical-applications-outside-your-erp</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="/en/blogs/how-do-you-integrate-and-manage-business-critical-applications-outside-your-erp" title="" class="hs-featured-image-link"&gt; &lt;img src="/hubfs/0.0%20*%20(new)/1.%20Visuals/Website/Beyond-ERP---Managing-and-Integrating-Business-Critical-Applications_1920x1080px.png" alt="How do you integrate and manage business-critical applications outside your ERP?" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;h2&gt;Why is integrating applications outside your ERP so important?&lt;/h2&gt; 
&lt;p&gt;Applications that remain outside your ERP are often business-critical. They support unique processes that differentiate your organization. If these applications are not properly integrated with your ERP, you end up with data silos, duplicate data entry, and error-prone workflows. On top of that, you increase the risk of compliance and security issues.&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="/en/blogs/how-do-you-integrate-and-manage-business-critical-applications-outside-your-erp" title="" class="hs-featured-image-link"&gt; &lt;img src="/hubfs/0.0%20*%20(new)/1.%20Visuals/Website/Beyond-ERP---Managing-and-Integrating-Business-Critical-Applications_1920x1080px.png" alt="How do you integrate and manage business-critical applications outside your ERP?" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;h2&gt;Why is integrating applications outside your ERP so important?&lt;/h2&gt; 
&lt;p&gt;Applications that remain outside your ERP are often business-critical. They support unique processes that differentiate your organization. If these applications are not properly integrated with your ERP, you end up with data silos, duplicate data entry, and error-prone workflows. On top of that, you increase the risk of compliance and security issues.&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=2655225&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fwww.cegeka.com%2Fen%2Fblogs%2Fhow-do-you-integrate-and-manage-business-critical-applications-outside-your-erp&amp;amp;bu=https%253A%252F%252Fwww.cegeka.com%252Fen%252Fblogs&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>ERP</category>
      <category>* Application Services</category>
      <pubDate>Thu, 25 Jun 2026 06:03:57 GMT</pubDate>
      <author>Peter.Hertogen@cegeka.com (Peter Hertogen)</author>
      <guid>/en/blogs/how-do-you-integrate-and-manage-business-critical-applications-outside-your-erp</guid>
      <dc:date>2026-06-25T06:03:57Z</dc:date>
    </item>
    <item>
      <title>AI-Assisted COBOL Modernization: Why Understanding the System Matters More Than Rewriting It</title>
      <link>/en/blogs/ai-assisted-legacy-modernization-unlocking-cobol-systems-through-understanding</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="/en/blogs/ai-assisted-legacy-modernization-unlocking-cobol-systems-through-understanding" title="" class="hs-featured-image-link"&gt; &lt;img src="/hubfs/0.0%20*%20(new)/1.%20Visuals/Website/AI-Assisted%20COBOL%20Modernization_1920x1080px.png" alt="AI-Assisted Legacy Modernization: Unlocking COBOL Systems Through Understanding" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;h2&gt;What Leaders Often Get Wrong About Legacy Modernization&lt;/h2&gt; 
&lt;p&gt;A common assumption is that legacy modernization is primarily a technical challenge. Replace COBOL, migrate code, move to a new platform. That’s the narrative. In reality, the bigger issue is organizational memory loss.&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="/en/blogs/ai-assisted-legacy-modernization-unlocking-cobol-systems-through-understanding" title="" class="hs-featured-image-link"&gt; &lt;img src="/hubfs/0.0%20*%20(new)/1.%20Visuals/Website/AI-Assisted%20COBOL%20Modernization_1920x1080px.png" alt="AI-Assisted Legacy Modernization: Unlocking COBOL Systems Through Understanding" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;h2&gt;What Leaders Often Get Wrong About Legacy Modernization&lt;/h2&gt; 
&lt;p&gt;A common assumption is that legacy modernization is primarily a technical challenge. Replace COBOL, migrate code, move to a new platform. That’s the narrative. In reality, the bigger issue is organizational memory loss.&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=2655225&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fwww.cegeka.com%2Fen%2Fblogs%2Fai-assisted-legacy-modernization-unlocking-cobol-systems-through-understanding&amp;amp;bu=https%253A%252F%252Fwww.cegeka.com%252Fen%252Fblogs&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Data &amp; AI</category>
      <category>* Application Services</category>
      <category>* Software Factory</category>
      <pubDate>Fri, 19 Jun 2026 06:43:34 GMT</pubDate>
      <guid>/en/blogs/ai-assisted-legacy-modernization-unlocking-cobol-systems-through-understanding</guid>
      <dc:date>2026-06-19T06:43:34Z</dc:date>
      <dc:creator>Benny Vranckx</dc:creator>
    </item>
  </channel>
</rss>
