<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Erp-En — TechCom</title>
    <link>https://techcom.org.ua/en/tag/erp-en/</link>
    <description>Latest TechCom news and insights on enterprise IT solutions.</description>
    <generator>UB CMS</generator>
    <language>en</language>
    <lastBuildDate>Mon, 20 Jul 2026 17:33:44 +0300</lastBuildDate>
    <atom:link href="https://techcom.org.ua/en/tag/erp-en/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Applying Zero Trust to legacy ERP via PAM, IAP, and microsegmentation</title>
      <link>https://techcom.org.ua/en/cybersecurity/zero-trust-legacy-erp-security/</link>
      <pubDate>Mon, 20 Jul 2026 17:33:44 +0300</pubDate>
      <guid>https://techcom.org.ua/en/cybersecurity/zero-trust-legacy-erp-security/</guid>
      <description>&lt;p&gt;Legacy ERP often remains the &#34;heart&#34; of an enterprise: it handles finances, procurement, production, logistics, and management reporting. At the same time, such systems often lack support for modern multi-factor authentication, SAML/OIDC, contextual access policies, or sufficiently granular privilege control. Completely rewriting the code or replacing the ERP can be too risky for business continuity, so a CISO needs an intermediate, yet manageable, path to risk reduction.&lt;/p&gt;&lt;p&gt;The threat landscape makes this task practical rather than theoretical. The ENISA Threat Landscape 2025 identifies phishing as the leading initial access vector. In the same reporting period, 53.7% of organizations affected by cyberattacks belonged to essential entities within the scope of NIS2. For industry, critical infrastructure, and large enterprise organizations, this means that if a user account is compromised, the ERP must not remain an open target for direct access and lateral movement.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Corporate AI requirements: the necessity of domain-specific language models</title>
      <link>https://techcom.org.ua/en/software-development/domain-specific-models-when-corporate-ai-needs-its-own-language/</link>
      <pubDate>Thu, 18 Jun 2026 06:07:17 +0300</pubDate>
      <guid>https://techcom.org.ua/en/software-development/domain-specific-models-when-corporate-ai-needs-its-own-language/</guid>
      <description>&lt;!-- wp:freeform --&gt;&#xA;&lt;p&gt;The integration of artificial intelligence into corporate processes is no longer a future prospect but a practical reality. However, when it comes to critical data, specific business processes, and stringent security requirements, general large language models (LLMs) often prove insufficient. This year and in the coming ones, a clear trend is observed: enterprises are increasingly turning to domain-specific language models (DSLM) that enable greater accuracy, control, and compliance with regulatory norms.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Electronic document management as a stable foundation during AI-driven shifts</title>
      <link>https://techcom.org.ua/en/electronic-document-management/electronic-document-management-a-proven-business-foundation-amid-ai-uncertainty/</link>
      <pubDate>Thu, 18 Jun 2026 06:06:52 +0300</pubDate>
      <guid>https://techcom.org.ua/en/electronic-document-management/electronic-document-management-a-proven-business-foundation-amid-ai-uncertainty/</guid>
      <description>&lt;!-- wp:freeform --&gt;&#xA;&lt;p&gt;Technological progress is measured by the speed at which new acronyms emerge, and business leaders face a paradox: the more promises, the less concrete information. This is particularly true in the realm of artificial intelligence, where terms like AGI (Artificial General Intelligence), &#34;Agents,&#34; and &#34;Superintelligence&#34; are often used to justify new investments, but without clear definitions or verifiable capabilities. This uncertainty poses a risk of misallocated budgets, as it&#39;s difficult to assess the real value of a solution when its ultimate goal remains vague.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Evaluating RPA integration with ERP: digital bridge or temporary fix?</title>
      <link>https://techcom.org.ua/en/bpm-en/rpa-after-erp-a-bridge-or-a-digital-patch/</link>
      <pubDate>Mon, 15 Jun 2026 15:39:49 +0300</pubDate>
      <guid>https://techcom.org.ua/en/bpm-en/rpa-after-erp-a-bridge-or-a-digital-patch/</guid>
      <description>&lt;p&gt;Following an ERP deployment, manual tasks rarely vanish entirely. Large organizations often face persistent integration gaps involving legacy software, Excel spreadsheets, paper-based workflows, and email-driven approvals. RPA offers a rapid solution to these gaps by mimicking user actions to transfer data without requiring extensive integration projects. However, for CIOs and COOs, the critical question remains: is the robot addressing a temporary technical deficit, or is it legitimizing an ERP workaround that should have been eliminated during the initial implementation?&lt;/p&gt;</description>
    </item>
    <item>
      <title>University data breach linked to Oracle PeopleSoft vulnerability</title>
      <link>https://techcom.org.ua/en/cybersecurity/oracle-peoplesoft-vulnerability-exploited-in-university-data-breach/</link>
      <pubDate>Fri, 12 Jun 2026 06:08:40 +0300</pubDate>
      <guid>https://techcom.org.ua/en/cybersecurity/oracle-peoplesoft-vulnerability-exploited-in-university-data-breach/</guid>
      <description>&lt;!-- wp:freeform --&gt;&#xA;&lt;p&gt;Between May 27 and June 9 of this year, a large-scale attack once again demonstrated the vulnerability of educational institutions. The ShinyHunters group, also known as UNC6240, successfully exploited the critical zero-day vulnerability CVE-2026-35273 in Oracle PeopleSoft software. This occurred even before Oracle published an official advisory on June 10, 2026 (Mandiant, 2026).&lt;/p&gt;&lt;p&gt;This incident exemplifies how cybercriminals leverage the time gap between vulnerability discovery and patch release, jeopardizing confidential data and operational resilience for organizations, particularly within the education sector.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Selection criteria for electronic document management systems</title>
      <link>https://techcom.org.ua/en/electronic-document-management/checklist-for-selecting-electronic-document-management-systems/</link>
      <pubDate>Wed, 10 Jun 2026 06:07:06 +0300</pubDate>
      <guid>https://techcom.org.ua/en/electronic-document-management/checklist-for-selecting-electronic-document-management-systems/</guid>
      <description>&lt;!-- wp:freeform --&gt;&#xA;&lt;p&gt;Selecting an electronic document management (EDM) system is an architectural decision that impacts operational efficiency, regulatory compliance, and an organization&#39;s adaptability. Research indicates that software IT projects, on average, exceed their budget by 45% and deliver 56% less expected value. This risk can be minimized by focusing on the right questions during vendor system demonstrations.&lt;/p&gt;&#xA;&#xA;&lt;h2&gt;Choosing an EDM system: why mistakes are costly&lt;/h2&gt;&#xA;&lt;p&gt;Errors during the EDM system selection phase lead not only to financial losses but also to reduced productivity, legal risks, and staff demotivation. An inadequate system may not meet legal requirements, have slow document processing speeds, or be difficult to integrate with other corporate systems. This creates bottlenecks that hinder digitalization and impede effective data management.&lt;/p&gt;</description>
    </item>
    <item>
      <title>System Integration Strategies Replacing Monolithic ERP</title>
      <link>https://techcom.org.ua/en/bpm-en/system-integration-an-alternative-to-monolithic-erp/</link>
      <pubDate>Fri, 10 Apr 2026 09:00:00 +0300</pubDate>
      <guid>https://techcom.org.ua/en/bpm-en/system-integration-an-alternative-to-monolithic-erp/</guid>
      <description>&lt;p&gt;Implementing a large monolithic ERP has traditionally been considered the answer to enterprise needs for a unified management system. However, reality shows that monolithic ERPs are difficult to adapt to specific business needs, are expensive, and often evolve into a rigid, &#39;concrete&#39; system that stakeholders are hesitant to modify.&lt;/p&gt;&lt;h2&gt;The Problem with the Monolithic Approach&lt;/h2&gt;&lt;p&gt;Any configuration often requires extensive customization, making upgrades painful. Unused modules incur significant licensing costs. Implementations can stretch for years. Furthermore, vendor lock-in becomes virtually impossible to overcome without a complete re-engineering of processes.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
