Scality becomes the authority for vulnerability numbering under the auspices of the European Cybersecurity Agency

French storage software provider Scality has begun independently assigning public identifiers for vulnerabilities in its products, under the European root of the Common Vulnerabilities and Exposures (CVE) program. This initiative is supervised by the European Union Agency for Cybersecurity (ENISA) and follows new regulations established by the Cyber Resilience Act (CRA), which emphasizes the responsibility of vendors in reporting vulnerabilities.

Security teams continuously monitor vulnerabilities using a common identifier assigned through the CVE program, which maintains a public registry of known weaknesses. Their scanning tools, incident management systems, and patching processes rely heavily on these records. Traditionally, identifiers were issued by CVE Numbering Authorities (CNAs), which were solely affiliated with MITRE, the U.S.-based organization managing the CVE program. As of January 2024, ENISA has become a CNA and on November 20, 2025, it assumed the role of root authority, tasked with recruiting, training, and overseeing subordinate CNAs.

On July 21, Scality, which markets the RING, ARTESCA, and ADI storage software solutions, was designated as a numbering authority under ENISA’s root and publicly announced this status on November 10. The company now verifies vulnerabilities reported in its products, assigns them CVE identifiers, and releases the corresponding records—detailing the affected versions and corrective actions—concurrently with the release of patches.

A European Root with Twenty CVE Authorities

As of August 6, ENISA oversees twenty CNAs under its root, including twelve recruited by the agency and eight transferred from MITRE, which includes the NATO Communications and Information Agency and AISLE, described as a company specializing in AI and cybersecurity. This means that organizations focused on vulnerability discovery are now empowered to assign CVE identifiers for their own products. Additionally, more than 90 European authorities may join through voluntary transfers, out of a total of 510 authorities across 42 countries, according to ENISA.

In its cybersecurity report for the EU published on November 10, ENISA noted that AI is streamlining the discovery of vulnerabilities. The agency also reported an increase in the number of member states with a coordinated national vulnerability disclosure policy, rising from 7 to 17 since 2024. ENISA also operates the European Vulnerability Database (EUVD), which aggregates insights from national incident response teams and vendors. As discoveries surge, the governance of numbering and disclosure—historically dominated by the U.S.—now gains a European dimension.

CRA: Reporting Exploited Vulnerabilities Within 24 Hours

Since September 11, Article 14 of the Cyber Resilience Act mandates manufacturers of products containing digital components to report actively exploited vulnerabilities and significant incidents. The regulation requires early notification within 24 hours, a follow-up notification within 72 hours, and a final report no later than fourteen days after a patch is made available. Notifications must go through ENISA’s centralized reporting platform, while other CRA obligations will come into effect on December 11, 2027. This means a manufacturer that learns of a publicly exploited vulnerability in its product has one day to alert authorities.

However, holding the status of a numbering authority does not exempt Scality from any of these notification requirements. The two processes are distinct; the CVE identifier renders a vulnerability public and searchable through tools, while notifications under the CRA inform authorities within legally mandated timeframes. By assigning its own identifiers, a vendor can effectively manage the timing and quality of public information regarding its vulnerabilities, aligning it with the release of patches.

Providing Vulnerability Information at Source

Scality has stated that its clients explicitly requested CVE coverage for its software. “Our customers utilize Scality solutions in some of the most regulated environments in the world, and their security teams have made their expectations clear: they want vulnerability information provided by the vendor, formatted for their existing tools,” explained Anh Nguyen-Phuoc, Scality’s Chief Information Security Officer.

As a result, vulnerabilities in a company’s storage software receive identifiers from the vendor, who understands the code, at the moment a patch is available, allowing them to automatically integrate into vulnerability inventory tools. The trade-off lies in the timeline, as the vendor also determines when to publish this information. While the practice of coordinated disclosure encouraged by ENISA limits this flexibility, it does not eliminate it.

Disclosure of Vulnerabilities as a Vendor Responsibility

The CRA establishes vulnerability management as a legal obligation for vendors, complete with deadlines, while ENISA builds the accompanying infrastructure for numbering and reporting. For a European vendor, becoming a numbering authority effectively places them closer to the agency that sets these standards. Scality does this in the storage industry, where its software safeguards backups and data essential for recovery after an attack.

For IT departments and CISOs purchasing software, the critical question to pose to a vendor has now shifted to how they publish their vulnerabilities—under what identifier, in what timeframe after a fix, and under which root of the CVE program. A vendor that manages its own records is now accountable to its clients.

Scroll to Top