Tech Blog

everyWAN Blog

Technology, cybersecurity and IT trends that matter

Deep Analysis
Cybersecurity
IT Trends
Filter by:
Frontal de un rack de servidores con varias generaciones de equipos apiladas, iluminadas por sus propios pilotos
8 min read

Multi-hypervisor is not a phase: it is what you will maintain twice

Sixty percent of the VMware customers surveyed by Unisphere Research are considering a multi-hypervisor strategy, and the four barriers they cite most — operational complexity 40%, multi-vendor management 38%, and tied at 37% securing the increased attack surface and team skills — are precisely what running two platforms at once installs in your shop. The list of what you end up maintaining twice, what genuinely does get halved, and when the dual state is the right call.

Pasillo en penumbra de una sala de servidores, con dos filas de armarios cerrados y sus pilotos encendidos
9 min read

Your VMware provider expires before your contract does

On 8 October 2026 IBM handed "hundreds" of its VMware cloud customers over to another company. None of them signed that deal. The date that governs a hosted VMware cloud is not in your contract: it is in the partner agreement your provider holds with Broadcom. Inside: the January FAQ sentence that describes what just happened nine months in advance, the seven dates with their owner in one table, the two days between 31 March and 2 April 2027, why "VCF 7" does not exist in Broadcom's documentation, and four questions that fit in one email.

Sala con filas de puestos de trabajo idénticos, mamparas bajas y sillas vacías
12 min read

Microsoft retires Targeted Release: your test ring is now paid for by everyone else

On 7 October 2026 Microsoft published advisory MC1490899 and updated three documentation pages the same day: Targeted release retires in January 2027 and from November 2026 its list can no longer be touched. The coverage reads it as a rename to Standard and Deferred. It is not. Reading the three pages together yields something else: to keep a validation group that runs ahead, Microsoft's own recommendation is not to move the pilot forward but to hold everyone else back by thirty days. Inside: the official mapping table read backwards, the documented cap of 100 users where each member of a security group counts one by one, the two kinds of change Deferred does NOT delay, and the seven checks that fit in half an hour before 31 October.

Frontal de varios servidores de rack apilados, con sus bandejas de disco etiquetadas y los pilotos de estado encendidos
9 min read

Piloting a VMware alternative is not migrating

Gartner has put a number on leaving VMware, and the number will be misquoted all autumn: by 2029, 55% of enterprises "will initiate proofs of concept" for alternatives, up from 25% in 2026. Initiate pilots, not migrate. Our argument is that most of those pilots will not help anyone decide anything, because they are built to succeed: install it, boot a VM, close the meeting. The six things an honest pilot has to try to break — starting with the restore, not the migration — the variable no analyst can give you (your renewal date), and the cases where we still tell people to stay.

Hilera de buzones de correo metálicos alineados junto a un camino de tierra
5 min read

onmicrosoft.com is no longer just an ugly domain: it is the slow lane

On 28 August Microsoft warned (MC1463510) that organisations using only the default domain will face external messaging limits in Teams, with rollout from mid-September. Read on its own it looks like an anti-spam tweak. Read alongside email it is something else: the limit of 100 external recipients per rolling 24 hours for onmicrosoft.com domains finished rolling out to every size band on 1 June 2026, with its own 550 5.7.236 bounce code. The case that catches companies who think they are unaffected, and why fixing it is not buying a domain but changing what people log in with.

Plan de continuidad sin ensayar: un servidor sacado a medias del rack con los cables de alimentación desenchufados
9 min read

A continuity plan nobody has rehearsed is a document, not a plan

Uptime Institute's May 2026 annual outage analysis says the leading driver of outages with human error behind them is still failing to follow procedures that were already established. Established: the document existed. And 87% of those who suffered an impactful outage believe it could have been prevented with better management, processes or configuration — seven points more than in 2024. What is missing, what a drill that works looks like, and when you should NOT run one.

Archivo de oficina con cajas y carpetas apiladas en estanterías metálicas bajo luz natural
5 min read

They are not old bugs: they are old classes of bug. We ran the numbers on CISA's catalogue

We downloaded CISA's Known Exploited Vulnerabilities catalogue and counted its 1,685 entries. Of the 201 added in 2026, 123 carry an identifier from this same year and the median gap is zero: what is old is not the individual bug but the class. We measured that too, using the file's own cwes field: CWE-20, improper input validation, tops the catalogue with 118 entries, followed by command injection and out-of-bounds write. And something turned up that we were not looking for: on 10 June directive BOD 26-04 revoked BOD 22-01, and since then 81% of what goes in arrives with a three-day deadline instead of the previous 23%.

Subscribe to our newsletter

To receive IT stories, everyWAN news and exclusive subscriber offers, sign up to our mailing list

Minorisa de Sistemas Informaticos y Gestión S.L. © 2026
everyWAN
everyWAN