Notifications
Clear all
Topic starter
12/07/2026 12:18 pm
TL;DR: KVM deployment, operation, integrated support, and AlmaLinux-based transition paths are the focus of NTT Data and Cybertrust Japan’s cooperation around Prossione Virtualization, according to Cybertrust Japan. The governance issue is no longer whether virtualisation is possible, but how organisations sustain control, recovery, and long-term support without creating fragile platform dependencies.
NHIMG editorial — based on content published by Cybertrust Japan: Prossione Virtualization collaboration, support model, and roadmap discussion
Questions worth separating out
Q: How should security teams govern privileged non-human identities in virtualisation environments?
A: Security teams should treat virtualisation management accounts as high-risk non-human identities with separate ownership, scoped permissions, and continuous review.
Q: Why do virtualisation platforms create governance risk over time?
A: Virtualisation platforms create governance risk when ownership, support, and lifecycle management are unclear.
Q: What do teams get wrong about open-source virtualisation support?
A: Teams often assume that open-source software reduces governance requirements, when it actually shifts the burden to support structure, internal skills, and partner coordination.
Practitioner guidance
- Define host-level privileged access boundaries Map every administrator, operator, and recovery role that can alter the KVM host or management plane, then remove standing access wherever the role does not require permanent elevation.
- Build a supportability checklist for procurement Before standardising on a virtualisation stack, require documented patch responsibility, escalation routing, operating system support coverage, and lifecycle transition plans.
- Separate operating access from recovery access Create distinct roles for routine platform administration, emergency recovery, and configuration change so that one account cannot both operate and restore the estate.
What's in the full article
Cybertrust Japan's full article covers the operational detail this post intentionally leaves for the source:
- The product and service roadmap for Prossione Virtualization 1.0 and the planned 2.0 transition path.
- The support model for AlmaLinux-based deployments and how it maps to existing Red Hat Enterprise Linux customers.
- The collaboration structure between Cybertrust Japan and NTT Data for implementation, operations, and training.
- The service catalogue details behind system integration, platform operation, and long-term maintenance.
👉 Read Cybertrust Japan's analysis of Prossione Virtualization support and roadmap →
KVM virtualization trust and support models are changing for teams?
Explore further
12/07/2026 12:31 pm
Operational trust, not feature count, is now the real virtualisation buying criterion. The article shows that KVM adoption is being judged by whether organisations can sustain it, not simply whether they can deploy it. That shifts the market conversation toward supportability, recovery, and long-term maintainability. Practitioners should evaluate virtualisation platforms as operational control systems, not just software stacks.
A question worth separating out:
Q: How do you know if a virtualisation operating model is sustainable?
A: A sustainable operating model can answer three questions without hesitation: who owns the platform, how recovery happens, and what support exists across version changes. If those answers depend on tribal knowledge, the model is brittle. Sustainability shows up as documented runbooks, tested recovery, and clear escalation paths.
👉 Read our full editorial: KVM virtualization trust is shifting toward operational control
