Color logo - no background Piergiorgio Venuti

From Cyberfero to Cyberfero: rebranding of the leading cybersecurity company

Estimated reading time: 3 minutes

Dear customers and partners, we are pleased to announce that our company is officially changing its name: from today Cyberfero becomes Cyberfero!

In this article we will illustrate in detail all the news and reassurances related to this rebranding, which marks the evolution of our company.

What changes at a practical level

At a practical level, the change of name from Cyberfero to Cyberfero does not entail any substantial changes for our customers.

The staff, as well as the services offered and their quality, remain unchanged. The company will continue to operate with the same seriousness and competence as always.

Access to services

Most of our services have already been migrated to the new cyberfero.com domain. Therefore, accessing the old secure-od.com domain, you will be automatically redirected to the new one.

We invite you to save the new addresses in your favorites for easier access. For services not yet transferred, they will continue to work regularly on the old domain until the migration is completed.

Billing

The next invoices will be issued with the new company name Cyberfero srl instead of Cyberfero srl. Nothing changes for customers administratively.

What users need to do to continue using the services

Users absolutely do not have to do anything. The transition to the new name and domain will be completely automatic and transparent for users. The services will work exactly like before.

Why the name change

Cyberfero, founded in 2011, was initially more focused on the provision of cloud computing services. Over the years the core business has shifted more and more towards cybersecurity services, which today represent the main activity.

We therefore decided to reflect this change also in the name, opting for Cyberfero.

Social Networks

Our social channels have been updated to reflect the name change, but will continue to be constantly updated to communicate all the news to followers.

The complete list of channels can be found in the site footer. We invite you to follow us to stay up to date on webinars, events and other news. Also register for the newsletter!

Curiosities about the new name

Cyberfero name
  • “Cyber” is an abbreviation for “Cyber Security” and refers to IT security.
  • “Fero” comes from the Latin “ferre” which means “to bring”.

So “Cyberfero” means “bringer of cyber security”, or “he who promotes and spreads IT security”.

Cyberfero shield

The logo depicts a shield, which evokes the concept of security through defense. But it also includes the idea of attack testing, to strengthen the shield itself.

Tell us what you think!

We are curious to know your impressions about this change. We invite you to share your opinions with us, both through our social channels and by writing to us at [email protected].

Your feedback is very valuable, it will help us better understand how the new Cyberfero name and identity was welcomed.

We look forward to hearing what you think!

Useful links:

Share


RSS

More Articles…

Categories …

Tags

RSS feed: Unknown Feed Unknown Feed

RSS feed: Full Disclosure Full Disclosure

  • SEC Consult SA-20261104-0 :: Improper device certificate validation enables AiTM attacks in Siemens SICAM Toolbox II device communication November 5, 2026
    Posted by SEC Consult Vulnerability Lab via Fulldisclosure on Nov 04SEC Consult Vulnerability Lab Security Advisory < 20261104-0 > ======================================================================= title: Improper device certificate validation enables AiTM attacks product: Siemens SICAM Toolbox II device communication vulnerable version:
  • Apache Struts2 Tiles Plugin <=7.4.0 and >=6.3.0 Preparer Cache Vulnerabilities November 5, 2026
    Posted by Daniel Owens via Fulldisclosure on Nov 04The Apache Struts2 Tiles plugin version =6.3.0) codebase includes a `ViewPreparer` construct, replete with multiple ViewPreparer factories, that contains several important vulnerabilities including unsynchronised, unbounded caches. The lack of proper synchronisation means that certain factories will create caches that race, risking lost cache entries, corrupted internal bucket […]
  • unixODBC <=2.3.14 Rude Truncation via Narrowing Conversion Causes Out-of-Bounds `memcpy` November 5, 2026
    Posted by Daniel Owens via Fulldisclosure on Nov 04unixODBC versions
  • unixODBC <=2.3.14 Multiple Races November 5, 2026
    Posted by Daniel Owens via Fulldisclosure on Nov 04The unixODBC driver manager library contains multiple races of importance / interest, including a set of data races in the connection-pooling configuration state data that can cause one thread to read a half-written pool-size or timeout value, which can lead to a variety of harmful effects, as […]
  • unixODBC <=2.3.14 Multiple Heap Buffer Overflows, Underflows, and Over-Reads November 5, 2026
    Posted by Daniel Owens via Fulldisclosure on Nov 04unixODBC versions 2.3.14 and below contain multiple heap buffer overflows, underflows, and over-reads. Attackers who can influence various arguments passed thereto can trigger the heap-based buffer overflows inside of the unixODBC driver manager itself, potentially corrupting the shared heap state across connections, crash the driver manager (thereby […]
  • Apache Struts2 Core Arbitrary Code Execution via OGNL Sandbox Escape November 2, 2026
    Posted by Daniel Owens via Fulldisclosure on Nov 01Description Apache Struts2 Core version 7.4.0 and below attempt to prevent arbitrary code execution via Object-Graph Navigation Language (OGNL) through several different mechanisms but only in a cursory fashion -- the libraries only guard against immediate calls evaluated by the OGNL engine via `SecurityMemberAccess`, but an allowed […]
  • Apache Struts2 Core TokenHelper Token Cryptographic Timing Side-Channel November 2, 2026
    Posted by Daniel Owens via Fulldisclosure on Nov 01Description The Apache Struts2 Core 7.4.0 and below performs session token comparisons cryptographically insecure early-exit comparison functions (e.g., `!=`, `memcmp`, byte-by-byte loops with `break`) that return as soon as the first mismatched byte is encountered. The execution time of the comparison is therefore proportional to the number […]
  • Apache Struts2 Spring Plugin Uses a Previously Closed Resource November 2, 2026
    Posted by Daniel Owens via Fulldisclosure on Nov 01Description The Apache Struts2 Spring Plugin opens a Spring `ApplicationContex` via a try-with-resources block and, outside of said block, then continues to use the closed resource, resulting in an uncaught `IllegalStateException`. This particular issue prevents proper functionality and indicates poor code quality and code review standards and […]
  • Apache Struts2 Core Integer Overflow November 2, 2026
    Posted by Daniel Owens via Fulldisclosure on Nov 01Description Apache Struts2 Core version 7.4.0 and below fails to properly prevent integer overflows, causing wrap-arounds and other issues on a downstream forced casting into types smaller than `BigInteger`. Importantly, this finding underscores why all applications using Struts and other such platforms should perform their own input […]
  • Apache Struts2 Core Cross-Origin Protection Exemption Miskeyed to a Deployment-Wide Path November 2, 2026
    Posted by Daniel Owens via Fulldisclosure on Nov 01Description Apache Struts2 Core version 7.4.0 and below&apos;s `FetchMetadataInterceptor`, `CoepInterceptor`, and `CoopInterceptor` each compare their `exemptedPaths` configuration -- a per-interceptor-reference, administrator-supplied set of paths intended to exempt specific actions from the corresponding cross-origin protection -- against `HttpServletRequest.getContextPath()`. `getContextPath()` is fixed for the entire deployed web...

Customers