Microsoft Virtualization
My first ” Windows Server 2008 Hyper V Launch Event” ended with success, we had with the last minute cancellations 10 attendees and the evaluation was 8.76 ( out of 9) based on the online metric that matters. I’m planning to do the second “launch event” in December (depends on the numbers of attendees)
Do not miss out the next one 😉
Here are some attendee feedback regarding the event
..got a much clearer picture on Hyper V works and understand where its place is going to be in my environment…very good evening… thank you
James Kindon , MVP
Awesome night.Thanks again!
Michael Hickin
This guy keeps the attention on him and knows how to sell (teach) the content very well. Thanks Erdal (Amigo)
Tony Hodge
Erdal is one of the best presenters ever, I am sure he will have even a better career in the near future
I never thought Microsoft can do Virtualization, from Microsoft Virtual Server its a big jump, I think VMware is getting a good competition. Also few words about Erdal, he was just great, I met him first time but I will make sure to stay in touch. Thank you CEO IT Training and Microsoft for the event
Sam Nguyen
CISO Insight
Looking back at 2008, virtualisation was the cloud before we called it cloud. Hyper-V was Microsoft’s answer to VMware ESX, and the conversation was about consolidating physical servers into virtual machines. Fast forward to 2026, and virtualisation underpins everything from container orchestration with Kubernetes to serverless computing. The security principles we established in those early days — isolation, resource segmentation, hypervisor hardening — remain foundational, even as the technology stack has evolved beyond recognition.
The Evolution from Virtualisation to Cloud-Native Infrastructure
This event from 2008 represents a fascinating snapshot of where enterprise infrastructure was heading. Microsoft’s Hyper-V had just launched, and the industry was in the early stages of understanding how virtualisation would transform data centre operations. The debates of that era — VMware vs Hyper-V, Type 1 vs Type 2 hypervisors, virtualisation licensing models — seem quaint now, but the decisions organisations made then shaped their infrastructure trajectories for the next decade.
What we did not fully anticipate in 2008 was how virtualisation would become the foundation for cloud computing. The ability to abstract hardware from software, to provision and deprovision workloads programmatically, and to move workloads between physical hosts without downtime — these capabilities evolved directly into the infrastructure-as-a-service model that now dominates enterprise IT. The security implications of this evolution have been profound.
Virtualisation Security: Then and Now
In 2008, virtualisation security focused primarily on hypervisor hardening, virtual machine isolation, and preventing VM escape attacks. These concerns remain valid, but the attack surface has expanded enormously. Modern virtualisation security must address container security, serverless function security, orchestration platform security (Kubernetes hardening), and the management plane security of cloud infrastructure itself. The principle remains the same — ensure strong isolation between workloads — but the implementation complexity has increased by orders of magnitude.
For CISOs managing modern infrastructure, the key lesson from the virtualisation era is that abstraction layers create both opportunities and risks. Every layer of abstraction (hypervisor, container runtime, orchestrator) introduces a new attack surface while simultaneously providing new points for security control enforcement. The security team must understand each layer deeply enough to make informed risk decisions about where to invest in controls.
Frequently Asked Questions
Is traditional virtualisation still relevant in 2026?
Yes. While containers and serverless computing have gained significant adoption, traditional hypervisor-based virtualisation remains the backbone of many enterprise data centres and all major cloud providers. VMware and Microsoft Hyper-V continue to run critical workloads. Many organisations operate a hybrid model with VMs for legacy applications and containers for cloud-native workloads.
What are the main security concerns with container environments?
Key concerns include vulnerable base images, misconfigured container runtime settings, excessive container privileges, insecure container registries, inadequate network policies between containers, and secrets management. Container environments require a shift-left security approach where security is integrated into the build and deployment pipeline rather than applied after deployment.
Related reading: For modern infrastructure security guidance, explore our Zero Trust Security Hub or visit the Cyber Resilience Framework for building resilient architecture across hybrid environments.