Cybersecurity, Products

NIS2, CRA, and SBOM: What Delphi 13 Can Truly Do for Your Compliance in 2026

NIS2, CRA, and SBOM: What Delphi 13 Can Truly Do for Your Compliance in 2026 A Correct Technical and Regulatory Guide for Delphi Developers If you develop software in Italy, 2026 is a pivotal year. The European cybersecurity regulatory landscape is now fully operational: the NIS2 Directive, transposed via Legislative Decree 138/2024, imposes concrete obligations on companies operating in critical sectors. Alongside this sits the Cyber Resilience Act (CRA), an EU regulation introducing specific requirements for products with digital elements, including the mandatory production of a SBOM (Software Bill of Materials). For those working with Delphi, understanding exactly what these regulations require—and what the available tools can actually offer—is essential for making informed decisions. 1. NIS2 and CRA: Two Distinct Regulations, Complementary Goals A common mistake is confusing NIS2 and CRA. It is important to distinguish them: NIS2 (EU Directive 2022/2555) targets operators of essential and important services. It mandates risk management, incident notification, cybersecurity governance, and supply chain security. It does not prescribe specific technologies or explicitly mention SBOM as a requirement. Cyber Resilience Act (CRA, EU Regulation 2024/2847) targets manufacturers of products with digital elements. It is the CRA, not NIS2, that explicitly requires the production of an SBOM for software components. The CRA will be fully applicable in 2027, though vulnerability reporting obligations begin as early as September 2026. In practice, a Delphi developer providing software to critical sectors may need to comply with both: NIS2 as a supplier in the supply chain of an essential entity, and CRA as a manufacturer of a digital product. Therefore, an SBOM is a strongly recommended best practice for NIS2 and a direct legal obligation under the CRA. 2. SBOM: State of the Art for the Delphi Ecosystem Important Note: As of today (February 2026), RAD Studio 13 Florence does not include a native SBOM generation feature integrated directly into the IDE. Generating an SBOM in CycloneDX or SPDX format is available via third-party tools: DerScanner SCA + SBOM: Offered by Embarcadero in a promotional bundle with RAD Studio 13 licenses. This is an external tool, not a built-in compiler or IDE feature. Delphi Code Analyzer (delphiparser.com): A third-party commercial tool supporting Delphi code analysis (from Delphi 1 to 13) and SBOM generation in CycloneDX 1.5 format. This means that to produce an audit-ready SBOM, you must plan to integrate additional tools into your build process rather than relying on an “out of the box” function in Delphi 13. 3. The 2026 NIS2 Roadmap: Immediate Actions If your company falls within critical sectors (energy, healthcare, digital infrastructure, manufacturing, PA, etc.), the 2026 calendar allows for no delays: By February 28, 2026: Window open for registration or annual updates on the National Cybersecurity Agency (ACN) portal. From January 1, 2026: Obligation to notify CSIRT Italia of any “significant” incident, with a pre-notification within 24 hours. By October 2026: For entities notified in 2025, the minimum technical measures required by law must be fully operational. Sanctions: Up to €10 million or 2% of global turnover for essential entities; up to €7 million or 1.4% of turnover for important entities. NIS2 also stipulates direct liability for management bodies. 4. Why Delphi is an Ally for Compliance Native Compilation and Attack Surface Delphi applications are natively compiled into machine code, without dependencies on virtual machines or managed runtimes. This can simplify dependency management compared to ecosystems with vast package managers (npm, Maven, pip). However, honesty is required: the complexity of a Delphi application’s supply chain depends on the third-party components used (VCL/FMX, GetIt packages, commercial libraries). A Delphi project with many external dependencies can have a risk profile comparable to a Java or .NET application. Furthermore, native compilation introduces specific risks (buffer overflows, memory corruption) that managed runtimes mitigate natively. It should also be noted that modern .NET supports native AOT (Ahead-of-Time) compilation, making the comparison less stark than it once was. InterBase 15: Verified Security Features InterBase 15, released in Autumn 2025, introduces concrete, documented security features: AES-256 Encryption by default for data at-rest and in-transit. DES is no longer supported. Mandatory TLS 1.2+ for client-server communications. TLS 1.0 and 1.1 have been eliminated. OpenSSL 3.5 LTS as the cryptographic foundation. Optional FIPS 140-3 (Server Edition on Windows and Linux only). While FIPS 140-3 is a US standard, in the European NIS2 context, primary references remain ISO/IEC 27001 and ENISA frameworks. FIPS support is nonetheless a strong indicator of cryptographic maturity. SHA-256 password digest for password protection. Change Views™ for tracking data modifications, essential for audit trails. Separation of Duties (SYSDSO) with column-level encryption, implementing the principle of least privilege. The Practical Advantage of the RAD Studio 13 Bundle A concrete aspect deserving attention is the ecosystem of tools Embarcadero provides with a RAD Studio 13 license: InterBase 15 Developer Edition is included, providing all the security features of the Server Edition for development and testing. DerScanner SCA + SBOM is offered as a promotion for customers purchasing or upgrading to RAD Studio 13. GetIt with Versioning: RAD Studio 13 introduces support for versioning GetIt packages, allowing you to “pin” specific dependency versions. This facilitates build reproducibility and third-party component traceability. In practical terms, upgrading to RAD Studio 13 provides a modern encrypted database, an SBOM generation tool, and a versioned dependency management system in a single transaction. It’s not “automatic compliance,” but it significantly reduces the operational complexity required to achieve it. 5. Implementing Technical Measures in Delphi To make Delphi software compliant with NIS2 requirements, developers should focus on three pillars: Strong Authentication (MFA): NIS2 requires multi-factor authentication for critical access. In Delphi, you can integrate libraries like IPWorks Auth to implement OAuth, RADIUS, or Kerberos and manage X.509 certificates. Protected Communication: It is vital to support TLS 1.2 or higher and the latest OpenSSL versions, retiring obsolete protocols. InterBase 15 implements these requirements natively. Traceability and Audit: By leveraging InterBase Change Views™, developers can track who modified what, creating granular audit logs useful for managing significant incidents. 6. Supply

Cybersecurity

User Identity Theft on Discord

User Identity Theft on Discord In October 2025, Discord, the popular communication platform for millions of users, suffered a serious personal data theft that ignited a deep debate on online user security and privacy. The alarm came directly from the company, which confirmed that the cyber attack did not hit Discord’s main servers but occurred through an external vendor tasked with managing customer service and Trust & Safety support. The attack was identified and made public in the first days of October 2025, specifically on October 5, when Discord began notifying users potentially involved in the breach. The hackers managed to obtain an impressive amount of data—about 1.5 terabytes—including approximately 70,000 images belonging to users who had contacted customer support. Among the stolen data were sensitive personal details such as names, usernames, email addresses, and contact information like mobile phone numbers. Particularly concerning was the compromise of the last four digits of credit cards and, most importantly, photographs and scans of identity documents used by users for age verification, as required by regulations in some countries like the UK under the Online Safety Act. These documents are essential for proving users are of legal age, and their exposure represents a significant risk of identity theft and fraud. According to Discord, the attack was primarily for extortion, with the cyber criminals attempting to blackmail the company by threatening to disclose the stolen data. Fortunately, the company managed to block the compromised vendor’s access to its ticketing systems and promptly initiated collaboration with the competent authorities to identify those responsible for the attack. Discord also reassured users that no data related to personal messages, private chats, or servers was touched, as these are stored on separate, more protected infrastructures. Discord itself raised the alarm about the data theft through official communications, including detailed emails to affected users, explaining precisely what information had been exposed and suggesting actions to take to protect against possible scams or abuse. The platform emphasized the importance of maintaining high vigilance regarding digital security, even in relationships with external vendors, as critical flaws can open up precisely through these indirect channels. This event has reignited the debate on the complexity of security in large technological platforms which, while investing significant resources to protect their main systems, must deploy equal attention in managing partnerships and accessory services. The management of age and digital identity verification is particularly sensitive and requires rigorous security protocols precisely because it involves highly confidential data. In conclusion, the Discord data theft highlighted how cybersecurity is a continuous and complex process that must consider all links in the service chain. For users, it is crucial to adopt personal security measures like enabling two-factor authentication and avoiding sharing sensitive documents outside of official channels, while for companies, the challenge is to ensure robust protections even in dealings with external partners and vendors. Discord has already begun to act in this direction by collaborating with authorities and strengthening its internal controls to prevent future incidents of this kind.

Cybersecurity

Iberian Peninsula Blackout: The IT Impact

Iberian Peninsula Blackout: The IT Impact On April 28, 2025, a large-scale blackout affected Spain, Portugal, and part of southern France, causing severe disruptions to IT and digital systems. Impacts on IT and Digital Systems Communication network outages: mobile networks and the internet experienced major interruptions, making communication and access to information difficult. Suspension of banking and payment services: ATMs and electronic payment systems were disabled, preventing financial transactions and access to cash. Transport disruptions: rail and metro lines, including the Madrid metro, were evacuated due to power outages, blocking control and safety systems. Hospital service interruptions: hospitals had to rely on emergency generators to keep critical systems running, such as intensive care and diagnostic equipment. From the staff at Delphi Studio, an IT company in Valencia, we received reports of a power outage lasting about 12 hours. However, after power was restored, everything returned to normal and servers are operational again to continue Delphi code development. Cause Investigations Spanish and Portuguese authorities launched investigations to determine the blackout’s causes. The National Institute for Cybersecurity (Incibe) is assessing the possibility of a cyberattack, although early analyses suggest a technical issue or cable fault as the main cause. Portuguese energy company REN pointed to a rare atmospheric phenomenon called “induced atmospheric vibration” as a possible origin of the outage. Service Restoration By the evening of April 28, power was restored in many areas, with 99% of energy demand met in Spain and most substations operational in Portugal. However, the disruptions to IT and digital systems highlighted the vulnerability of critical infrastructure during prolonged power outages. This event underscores the importance of strengthening the resilience of IT systems and communication networks by implementing security measures and emergency plans to ensure continuity of essential services during crises.

Cybersecurity

Serious security breach in the Polyfill.io project: over 100,000 websites compromised.

Serious security breach in the Polyfill.io project: over 100,000 websites compromised. A serious supply chain attack was recently discovered involving the Polyfill.io service, used by thousands of websites to ensure compatibility with older browsers. The attack affected over 100,000 sites, raising significant concerns about online security and trust in third-party libraries. The Polyfill.io Breach Polyfill.io provides “polyfills,” pieces of JavaScript code that implement modern functionalities in older browsers. This service was compromised after the domain management was transferred to the Chinese company Funnull in February 2024. Shortly thereafter, the code distributed through Polyfill.io began to contain malicious scripts, primarily targeting mobile devices, which redirected users to sports betting sites and adult content. The Response from the Tech Community The attack raised immediate concerns among security experts and web infrastructure providers. Cloudflare and Fastly quickly implemented secure versions of the Polyfill service to mitigate the risks. Additionally, Google began notifying its advertisers about the potential risks related to sites that loaded code from Polyfill.io, blocking ads on these compromised sites. Recommendations for Webmasters Security experts strongly recommend immediately removing any references to Polyfill.io from websites. In addition, it is advised to adopt security measures such as: Implementing a Content Security Policy (CSP): to restrict the sources from which scripts can be loaded. Using Subresource Integrity (SRI): to verify that the resources downloaded have not been tampered with. Regularly Monitoring Dependencies: performing periodic security audits to detect any abnormal behavior. The Polyfill.io incident is a clear example of the risks associated with using third-party libraries and highlights the importance of adopting robust security practices to protect web infrastructure. Companies must remain vigilant, regularly update their dependencies, and follow best practices for security.

Scroll to Top