ESET NeoCortex powers LiveCortex with specialised AI designed to connect security signals and reduce alert noise. Here is what Singapore IT teams should evaluate.
Continue reading
Segura Adds Self-Service Vendor Access Portal for Safer Third-Party Privileged Access
Third-party access is one of those IT tasks that can quietly become a security headache. A supplier needs to troubleshoot a system, an MSP has to maintain infrastructure, or an auditor needs temporary access to review a configuration. If every request depends on an administrator manually creating an account and arranging a connection, the process can become slow and difficult to govern.
Segura’s Platform v4.2.15 adds a Vendor Access Portal to Domum Remote Access. The self-service portal lets vendors, managed service providers and auditors register, sign in and request time-limited access to resources that an organisation has chosen to publish. Administrators still control approval, access limits and session policies.
Let vendors request access without handing over control
Previously, third-party accounts depended on the customer’s team creating each account. With the Vendor Access Portal, an external user can register and submit an access request. The request includes a justification, a requested session duration within the resource’s configured limit and an optional IT service management ticket reference.
An administrator reviews the registration and request before releasing access. This changes the administrative workload without turning the portal into an open door: third parties only see resources published for their organisation, and access remains subject to the customer’s policies.
Authentication, network restrictions and controlled sessions
The portal supports passwordless sign-in using an email address and a one-time code. On first sign-in, the user receives a code through the configured channel and registers an authenticator app for subsequent sign-ins. This adds a verification step without requiring the organisation to issue a permanent password to every external user.
Administrators can apply portal-wide IP and geolocation allow-lists. They can also configure restrictions for each vendor organisation and define the days, hours and number of sessions when access is released. Sessions run through the Segura Web Proxy rather than connecting directly to the target resource, and they follow the same session policies as other Domum sessions.
Two portal roles help separate responsibilities. Portal Configuration users manage settings, access restrictions and published resources, while Portal Operators review registrations and access requests. This can help organisations avoid giving every person who processes vendor requests broad administrative rights.
Why this matters to organisations
Businesses often rely on external technology providers to support networks, servers, applications, cloud environments and business-critical systems. That support is necessary, but standing privileged accounts and informal remote-access arrangements can leave organisations with more access than they intended.
A structured request-and-approval process gives IT and security teams a clearer record of why access was needed, how long it was requested for and who approved its release. The optional ITSM ticket reference can also help connect a remote session to a change request or incident record.
For organisations handling customer information or operating regulated services, this workflow can support stronger access governance. It should sit alongside a broader privileged access management programme, including least-privilege permissions, named user accounts, session monitoring, credential rotation, periodic access reviews and documented offboarding procedures.
Implementation checklist for IT and security teams
- Publish only necessary resources. Start with a small set of systems and define which vendor organisations can request each resource.
- Set sensible access limits. Use time windows and maximum session durations that match the support task, rather than granting broad, long-lived access.
- Configure network controls. Review approved IP ranges and locations, including how legitimate support teams connect when staff work remotely.
- Assign clear portal roles. Separate portal configuration from day-to-day request handling and keep permissions scoped to each responsibility.
- Connect requests to service workflows. Encourage vendors to include a change or incident ticket reference so approvals can be checked against business context.
- Test the user journey. Validate registration, MFA enrolment, request approval, session release, proxy access and audit records with a pilot vendor before wider rollout.
Make third-party access easier to manage
The Vendor Access Portal in Segura Platform v4.2.15 aims to reduce manual account provisioning while keeping approval and session control with the organisation. For IT teams, it offers a more consistent way to handle supplier and MSP access without relying on permanent privileged accounts or ad hoc remote connections. Start with a defined vendor group, review the access policies and audit trail, and expand only after the process works smoothly for both administrators and external users.
About Segura®
Segura® strive to ensure the sovereignty of companies over actions and privileged information. To this end, we work against data theft through traceability of administrator actions on networks, servers, databases and a multitude of devices. In addition, we pursue compliance with auditing requirements and the most demanding standards, including PCI DSS, Sarbanes-Oxley, ISO 27001 and HIPAA.
About Version 2 Limited
Version 2 Digital is one of the most dynamic IT companies in Asia. The company distributes a wide range of IT products across various areas including cyber security, cloud, data protection, end points, infrastructures, system monitoring, storage, networking, business productivity and communication products.
Through an extensive network of channels, point of sales, resellers, and partnership companies, Version 2 offers quality products and services which are highly acclaimed in the market. Its customers cover a wide spectrum which include Global 1000 enterprises, regional listed companies, different vertical industries, public utilities, Government, a vast number of successful SMEs, and consumers in various Asian cities.
CyberLink Moves Face Recognition onto Axis Cameras with FaceMe Security 8.9.2
CyberLink FaceMe Security 8.9.2 runs facial recognition on compatible Axis cameras. See what Singapore IT and facilities teams should assess.
Continue reading
Microsoft 365 EWS Retirement: What IT Teams Should Do Before April 2027
Microsoft’s retirement of Exchange Web Services (EWS) is no longer a distant roadmap item. Enforcement has started rolling out across Microsoft 365 tenants, and the service is scheduled to be switched off permanently on 1 April 2027. For organisations using CloudM Migrate for Microsoft 365 projects, that makes migration readiness a task to put on the calendar now.
CloudM’s support update of 30 October 2026 explains that some Microsoft 365 workloads in CloudM Migrate still use EWS. The company is moving those connectors to Microsoft Graph, but that work is not generally available yet. In the meantime, customers need to make sure the CloudM application is permitted to use EWS in each affected tenant.
What is changing with EWS?
Microsoft is moving Exchange Online integrations away from EWS and towards Microsoft Graph. The change is being enforced progressively rather than on one single date for every tenant. From October 2026, Microsoft began setting EWS to disabled in tenants where it had not been explicitly configured. It also introduced an application allow-list model, so simply setting EWS to enabled is no longer enough once enforcement reaches a tenant.
From 1 April 2027, EWS will be fully disabled in Exchange Online. No tenant setting or allow-list entry will keep it working after that date. If a migration project depends on an EWS-based workload, the team needs a tested plan well before the cut-off.
Which CloudM Migrate workloads could be affected?
CloudM says the change affects Microsoft 365 migrations involving mail, calendars, contacts, tasks and notes where the current connector uses EWS. The impact depends on the workloads in scope, the tenant’s EWS configuration and whether the CloudM application registration is already on the relevant allow list.
There is one important detail for IT teams: Microsoft may have created an allow list based on applications that used EWS in the previous 60 days. Apps that are used infrequently, or were created more recently, may not be included automatically. A migration that worked during an earlier test is not proof that every production tenant is ready.
What should IT teams do now?
- Inventory active migration projects. Identify every Microsoft 365 tenant and workload that relies on CloudM Migrate, including mail, calendar, contact, task and note data.
- Check the tenant’s EWS settings. Confirm whether Microsoft’s enforcement has reached the tenant and whether an application allow list is in place. Do not rely on the legacy EWS-enabled setting alone.
- Allow-list the CloudM application. Follow CloudM’s current guidance to add its Migrate app registration to Microsoft’s EWS allow list for the affected tenant. Have the Microsoft 365 administrator verify the application ID and policy change.
- Allow time for the change to take effect. CloudM advises allowing up to 24 hours after updating the allow list before testing the migration again.
- Run a representative test. Validate each workload, check data counts and permissions, and confirm that the migration can complete within the planned change window.
- Keep the Graph transition on the roadmap. Ask your migration partner to confirm when Microsoft Graph support for the required workloads becomes generally available and what version or configuration will be needed.
Plan migration windows around the deadline
For organisations, the risk is not just a failed connector. A migration can affect staff access, project deadlines and business operations, especially when email and collaboration data are being moved between tenants. Build the EWS check into the project plan, schedule a test before the production cutover, and make sure the Microsoft 365 owner and migration partner agree on who is responsible for the allow-list change.
It is also worth checking how the migration handles data governance. Confirm where migration data is processed, who can access it, how temporary copies are protected and how exceptions are recorded. These questions matter for organisations handling personal data, confidential customer information or regulated business records under Singapore’s PDPA and internal security policies.
Do not leave the check until the final cut-off
CloudM’s guidance gives customers an interim way to keep affected migrations running while its Microsoft Graph work progresses. That is useful, but it should not become a reason to postpone planning. Tenant-by-tenant enforcement has already begun, and the April 2027 retirement date is fixed.
If your organisation is planning a Microsoft 365 migration, ask your IT team or CloudM partner to review the EWS dependency now. A short compatibility check, allow-list review and controlled test can help prevent a last-minute disruption when the migration window matters most.
About CloudM
CloudM is an award-winning SaaS company whose humble beginnings in Manchester have grown into a global business in just a few short years.
Our team of tech-driven innovators have designed a SaaS data management platform for you to get the most from your digital workspace. Whether it’s Microsoft 365, Google Workspace or other SaaS applications, CloudM drives your business through a simple, easy-to-use interface, helping you to work smarter, not harder.
By automating time-consuming tasks like IT admin, onboarding & offboarding, archiving and migrations, the CloudM platform takes care of the day-to-day, allowing you to focus on the big picture.
With over 35,000 customers including the likes of Spotify, Netflix and Uber, our all-in-one platform is putting office life on auto-pilot, saving you time, stress and money.
About Version 2 Limited
Version 2 Digital is one of the most dynamic IT companies in Asia. The company distributes a wide range of IT products across various areas including cyber security, cloud, data protection, end points, infrastructures, system monitoring, storage, networking, business productivity and communication products.
Through an extensive network of channels, point of sales, resellers, and partnership companies, Version 2 offers quality products and services which are highly acclaimed in the market. Its customers cover a wide spectrum which include Global 1000 enterprises, regional listed companies, different vertical industries, public utilities, Government, a vast number of successful SMEs, and consumers in various Asian cities.
SealPath’s 2026 Data Protection Report: Why Teams Need Persistent Document Control
Most organisations have got better at controlling who can open a file inside their own systems. The harder question is what happens after that file is shared with a supplier, customer, external adviser or an AI tool. SealPath’s 2026 State of Data Protection report highlights a gap between access policies and the ability to keep control of information once it leaves the organisation.
The report is based on a survey of 1,052 security and technology professionals, with fieldwork carried out in July and August 2026. Its findings are useful for businesses reviewing data protection, secure collaboration and the controls they need as employees make wider use of generative AI.
Access control is only part of the job
According to the report, 85% of respondents say they apply least-privilege access. However, only 36% can change a document’s permissions after it has been sent, and just 21% say they have persistent protection in place. That difference matters because a file can move beyond the original repository very quickly: it may be downloaded, forwarded, copied into a project workspace or shared with an external party.
Revoking access to a folder or user account does not always solve the problem if a copy of the document is already outside the organisation’s control. Security teams need to consider the file itself, not just the location where it was first stored.
AI use adds another route for sensitive information to travel
The report found that 48% of participants confirmed that sensitive information had been entered into AI tools, while another 20% suspected this had happened. Although 78% said their organisation had an AI usage policy, only 26% reported technical measures to block sensitive information from being uploaded to those tools.
This is a practical challenge, not simply a policy issue. Staff may paste contract clauses into an assistant to prepare a summary, upload engineering drawings for analysis or use internal reports to draft a presentation. The intention may be harmless, but the organisation still needs to know what information is being shared and whether the destination is approved.
Why persistent document protection is worth evaluating
SealPath’s information rights management approach applies protection to the document, rather than relying only on the repository around it. Its platform combines encryption with usage permissions and traceability, helping organisations control who can access a protected file and what they are allowed to do with it. Depending on the configuration, administrators can also track access and revoke permissions after a document has been shared.
That model can be useful for contracts, financial records, customer information, product designs and other documents that regularly move between internal teams and external partners. SealPath describes SaaS and on-premises deployment options, alongside integrations with common business applications and storage environments.
What the findings mean for buyers
Organisations should assess these controls against the way information actually moves through the business. The report found that 72% of respondents share sensitive information with third parties at least occasionally, but only 46% said they could revoke access to shared information and 32% could audit third-party access. Those gaps are relevant to businesses working with regional suppliers, outsourced service providers, legal advisers and overseas subsidiaries.
The report also found that 83% of respondents consider data sovereignty important or mandatory, and 72% apply that consideration to AI tools that process sensitive information. For local buyers, this is a reminder to ask where data is stored and processed, which administrators can access it, how keys and permissions are managed, and what happens when a document crosses a national boundary.
These questions should sit alongside the organisation’s obligations under Singapore’s PDPA and its own contractual and industry requirements. A technology platform can support governance, but it does not replace the need for clear policies, staff training, supplier due diligence and legal review.
A practical checklist before choosing a solution
- Identify high-value information. Start with documents that would create material risk if they were copied or shared without approval.
- Protect the file after sharing. Check whether permissions remain enforceable when a document is downloaded or sent outside the original repository.
- Test revocation and audit. Confirm that administrators can withdraw access and review who opened a document, including external users.
- Check application fit. Validate support for the file types and tools your teams already use, especially Office documents, PDFs and engineering or CAD files where relevant.
- Review deployment and data flows. Compare SaaS and on-premises options, hosting locations, integrations, identity controls and administrator access.
- Pilot real workflows. Test with a small group that regularly shares sensitive files with customers or partners, and measure both security outcomes and user friction.
Move from policy statements to controls that travel with the data
The main lesson from the 2026 report is that a policy can say who should access information, but it cannot by itself protect every copy once a document starts moving. IT and security teams should review whether their current controls can follow sensitive information through collaboration, external sharing and approved AI use.
Persistent document protection is one option to assess as part of that wider programme. The right starting point is a focused pilot using the documents and sharing scenarios that matter most to the business, with clear success measures for usability, access control, auditability and data governance.
About SealPath
SealPath is the European leader in Data-Centric Security and Enterprise Digital Rights Management, working with significant companies in more than 25 countries. SealPath has been helping organizations from different business verticals such as Manufacturing, Oil and Gas, Retail, Finance, Health, and Public Administration, to protect their data for over a decade. SealPath’s client portfolio includes organizations within the Fortune 500 and Eurostoxx 50 indices. SealPath facilitates the prevention of costly mistakes, reducing the risk of data leakage, ensuring the security of confidential information, and protecting data assets.
About Version 2 Limited
Version 2 Digital is one of the most dynamic IT companies in Asia. The company distributes a wide range of IT products across various areas including cyber security, cloud, data protection, end points, infrastructures, system monitoring, storage, networking, business productivity and communication products.
Through an extensive network of channels, point of sales, resellers, and partnership companies, Version 2 offers quality products and services which are highly acclaimed in the market. Its customers cover a wide spectrum which include Global 1000 enterprises, regional listed companies, different vertical industries, public utilities, Government, a vast number of successful SMEs, and consumers in various Asian cities.
Actiphy ImageServer: Centralising Backup Operations for Businesses
For many IT teams, getting a backup job to complete is only the first step. The real work starts afterwards: checking that the image is healthy, moving copies to the right places, consolidating older recovery points and proving that a system can actually boot when it is needed. As backup estates grow across servers, virtual machines and remote offices, those follow-up tasks can become a workload of their own.
Actiphy’s latest announcement is aimed at that operational gap. On 26 October 2026, the company introduced Actiphy ImageServer, a platform that brings backup-image management and secure storage together, while moving several post-backup tasks away from the protected servers and workstations.
One place to manage the work after backup
ImageServer combines the image-management capabilities of Actiphy ImageCenter with the storage capabilities of Actiphy StorageServer. Instead of leaving every protected machine to handle the follow-up processing, administrators can use a dedicated server to run verification, replication, consolidation and BootCheck tasks.
That separation can be useful when backup activity competes with production workloads. A busy file server or application host should not have to carry unnecessary processing overhead just because the backup estate needs routine housekeeping. Centralising those jobs also gives administrators a clearer view of what has run, what is waiting and what needs attention.
What stands out in Actiphy ImageServer
- Inter-file deduplication: ImageServer can identify common data blocks across backup images in the same bucket and reuse existing blocks. Actiphy reports reductions of about 71% for uncompressed backups and about 54% for backups using ActiveImage Protector’s IDDC in its own testing. Treat those figures as vendor test results, not a guaranteed saving for every environment.
- Automated workflows: Administrators can automate verification, replication, consolidation and BootCheck, and define the order and time windows for those jobs.
- Flexible replication targets: Supported destinations include network shares, FTP/FTPS, SFTP, WebDAV, Amazon S3 and compatible storage services such as Wasabi and Microsoft Azure.
- Centralised monitoring: A web console provides visibility into storage use, connected clients, transfer speeds, task status, events and history. Image Browser also supports file-level recovery.
- Security controls: The product supports HTTPS, user authentication, TOTP-based two-factor authentication, event notifications and scheduled summary reports.
Why Singapore businesses may want to look at it
For organisations operating from several Singapore offices, retail outlets, clinics, warehouses or regional sites, backup administration can become fragmented. Different teams may be responsible for different servers, and copies may be sent to a mix of local storage and cloud destinations. A central management point can make it easier to standardise how backups are checked and replicated, without adding the same post-processing load to every protected machine.
It is also worth thinking about recovery rather than storage alone. A backup that has never been tested is an assumption, not a recovery plan. Routine verification and BootCheck help teams build evidence that backup images are usable. File-level recovery can also be handy when the request is simply to retrieve one deleted document rather than restore an entire system.
Questions to ask before deployment
Start with the basics: which ActiveImage Protector versions and image types are in scope, how many backup generations need to be retained, and how much data is expected to move during each replication window? Actiphy lists a four-core CPU recommendation, 16GB of memory as a minimum and 32GB or more as a recommendation for some workloads. A separate storage destination is also required for backup images, so include that capacity in the design.
Next, decide where each copy should live. Singapore organisations should check the location of cloud storage, cross-border transfer arrangements, retention rules and any contractual or regulatory requirements that apply to the data. Consider network bandwidth and egress costs too, especially if large image files are replicated outside Singapore.
Finally, run a realistic recovery exercise. Measure how long it takes to find the right image, restore a file and bring a representative server back online. Confirm who can administer the console, enable two-factor authentication and document the recovery steps. If deduplication is part of the business case, test it against your own data rather than relying only on headline percentages.
A practical next step
If your organisation already uses ActiveImage Protector, ImageServer is worth evaluating as a way to bring backup storage, verification and replication workflows under more consistent control. The strongest case will come from mapping it to your current backup volumes, storage destinations and recovery objectives, then testing the workflow with a representative workload before rolling it out more widely.
About Actiphy
Actiphy founded in 2007, focuses on developing and offering innovative backup and disaster recovery solutions for complete protection of all your systems and data. ActiveImage Protector backs up Windows, Linux machines on physical and virtual environments and restore systems and data fast for you to be up and running with minimal downtime and data loss. Today Actiphy hold 20% of the image backup market in Japan and are expanding our services in the Asia/Pacific and North American regions, as well as in Europe, the Middle East and Africa.
About Version 2 Limited
Version 2 Digital is one of the most dynamic IT companies in Asia. The company distributes a wide range of IT products across various areas including cyber security, cloud, data protection, end points, infrastructures, system monitoring, storage, networking, business productivity and communication products.
Through an extensive network of channels, point of sales, resellers, and partnership companies, Version 2 offers quality products and services which are highly acclaimed in the market. Its customers cover a wide spectrum which include Global 1000 enterprises, regional listed companies, different vertical industries, public utilities, Government, a vast number of successful SMEs, and consumers in various Asian cities.
Scale Computing HyperCore 9.8.6: What IT Teams Should Know
Distributed IT is rarely neat. A Singapore business might run its core applications in a central data centre while keeping point-of-sale, manufacturing, video, clinic or warehouse systems running at smaller sites. Those workloads still need reliable virtualisation, storage and recovery, but sending an engineer to every location for routine maintenance is not a great long-term operating model.
Scale Computing’s latest SC//HyperCore update gives infrastructure teams a timely reason to review that edge strategy. The company’s documentation lists version 9.8.6 as the latest release for October 2026. It is classified as an Early Production Release, so teams should check its availability and release status with Scale Computing before planning a production rollout.
What is new in SC//HyperCore 9.8.6?
The update includes a redesigned virtual-machine console and C1E processor power-state management. SC//HyperCore Guest Tools move to version 5.0-1, adding VirtIO SCSI drivers. Scale Computing also reports improved performance and faster boot times on HE250 nodes.
The release addresses several operational issues as well. These include in-place re-imaging problems, NVMe power management on supported Crucial drives, a boot-stability issue and incorrect VM creation or modification timestamps returned by the REST API. The release notes also list fixes for CVE-2026-64847 and CVE-2026-63374.
That mix is useful because infrastructure updates are not just about new features. More predictable hardware behaviour, clearer VM administration and security fixes can all reduce the amount of time teams spend troubleshooting the platform underneath their applications.
Why the platform model matters at the edge
SC//HyperCore is built on KVM and integrates with Scale Computing’s SCRIBE storage layer. Rather than asking administrators to assemble a separate hypervisor, storage appliance and management stack, the platform brings compute, storage and virtual-machine management together. Scale Computing’s AIME engine is designed to automate routine administration, watch for infrastructure issues and help return clusters to a known-good state.
For businesses with multiple locations, that integrated approach can make a difference. Local applications can continue running close to the users and equipment that depend on them, while infrastructure teams manage the environment more consistently. This can be relevant for retail branches, logistics sites, manufacturing floors, healthcare facilities and other locations where downtime has an immediate operational impact.
Scale Computing’s security documentation also describes controls such as role-based access, detailed system logging, signed software updates and network isolation. Its shared-responsibility guidance is clear that customers still need to manage identities, review logs, secure guest operating systems and meet the compliance obligations that apply to their own workloads.
Plan the upgrade carefully
Before moving to a new release, check the current SC//HyperCore version on every cluster and follow the published update path for that branch. Scale Computing lists 9.8.6 as the October 2026 release and describes the supported update paths as non-disruptive. The documented path from the 9.7 branch goes through 9.7.12, while the 9.6 branch goes through 9.6.32.
Because 9.8.6 is marked Early Production, it may not appear in every cluster’s web interface. Scale Computing advises customers to contact Support if the release is not available to them. That classification matters: check whether the build is appropriate for your hardware and support requirements before treating it as a routine production update.
For a controlled rollout, take an inventory of cluster versions, hardware models, guest operating systems, storage capacity and application dependencies. Confirm that backups and recovery procedures are current, test the update on a representative cluster where possible, and schedule the change with the teams responsible for the applications. After the upgrade, validate VM start-up, storage performance, network connectivity, monitoring and any integrations that use the REST API.
Security and compliance still need an owner
An integrated platform can reduce the number of separate components that administrators need to maintain, but it does not remove the need for good operational controls. Singapore organisations should continue to assess personal-data handling against the PDPA and their own sector or contractual requirements. Do not assume that a platform’s alignment with selected international frameworks automatically makes every application or deployment compliant.
Keep privileged access limited, enable strong authentication, forward relevant logs to your monitoring or SIEM platform, and patch the guest operating systems and applications running inside the virtual machines. Treat the hypervisor as one important layer in a broader security and resilience plan.
Is it time to review your edge infrastructure?
SC//HyperCore 9.8.6 is a useful prompt to review both the health of existing clusters and the way remote sites are supported. The right decision is not simply to install the newest build everywhere. It is to confirm release suitability, follow the supported upgrade path and make sure the platform continues to meet the recovery, security and availability needs of each location.
For Singapore IT teams looking to simplify distributed infrastructure, a structured assessment of current workloads, hardware, network design and operational processes is a sensible place to start.
About Scale Computing
Scale Computing is a leader in edge computing, virtualization, and hyperconverged solutions. Scale Computing HC3 software eliminates the need for traditional virtualization software, disaster recovery software, servers, and shared storage, replacing these with a fully integrated, highly available system for running applications. Using patented HyperCore™ technology, the HC3 self-healing platform automatically identifies, mitigates, and corrects infrastructure problems in real-time, enabling applications to achieve maximum uptime. When ease-of-use, high availability, and TCO matter, Scale Computing HC3 is the ideal infrastructure platform. Read what our customers have to say on Gartner Peer Insights, Spiceworks, TechValidate and TrustRadius.
About Version 2 Limited
Version 2 Digital is one of the most dynamic IT companies in Asia. The company distributes a wide range of IT products across various areas including cyber security, cloud, data protection, end points, infrastructures, system monitoring, storage, networking, business productivity and communication products.
Through an extensive network of channels, point of sales, resellers, and partnership companies, Version 2 offers quality products and services which are highly acclaimed in the market. Its customers cover a wide spectrum which include Global 1000 enterprises, regional listed companies, different vertical industries, public utilities, Government, a vast number of successful SMEs, and consumers in various Asian cities.
EasyVista: Building Trustworthy AI Governance into IT Service Management
AI is already showing up in IT service management (ITSM) — from virtual agents and suggested ticket responses to automated routing and workflow actions. The harder question for Singapore IT leaders is no longer whether these tools can work in a demo. It is whether they can be trusted, governed and measured once they become part of everyday service delivery.
In its October 2026 discussion of AI governance, EasyVista highlights a useful distinction: governance is not an administrative layer to add after an AI project goes live. It is part of the foundation that makes AI outcomes repeatable, secure and accountable. That message is especially relevant to organisations operating across multiple departments, subsidiaries or regional offices.
Why AI governance belongs in the ITSM plan
ITSM platforms often handle information that is operationally sensitive: employee details, device records, access requests, incident descriptions, business application data and service histories. When AI is introduced into these workflows, organisations need to understand what information the system can access, what it can generate, which actions it can take and who remains accountable.
Without clear controls, a promising pilot can become difficult to operate consistently. A virtual agent might answer common questions well but struggle with exceptions. An automated routing model may perform at launch and then drift as services, teams and user behaviour change. An AI assistant might save time while creating uncertainty about whether its recommendations are accurate or appropriate.
Five practical governance building blocks
1. Give every AI use case an owner
Assign a business owner and a technical owner for each AI-enabled service workflow. Define who approves changes, who reviews incidents, and who can pause or disable the capability. For higher-impact decisions, establish an escalation route that reaches a person with the authority to act.
2. Classify risk before enabling automation
Not every ITSM task needs the same level of oversight. Suggesting a knowledge article is different from approving privileged access, changing a production configuration or closing a security incident. Classify use cases by their potential impact, autonomy and reversibility. Match the approval process to the risk instead of applying one blanket rule.
3. Protect the data used by AI
Review what information is sent to AI services, where it is processed, how long it is retained and which users or systems can retrieve it. For Singapore organisations, include the relevant Personal Data Protection Act (PDPA) obligations in the privacy review, alongside contractual, customer and sector-specific requirements. Restrict access to sensitive ticket content and avoid putting confidential information into prompts unless the service and workflow have been approved for that use.
4. Keep humans in the loop where it matters
Use automation for predictable, low-risk tasks where the result can be checked and reversed. Keep human approval for actions that affect access rights, sensitive records, business-critical systems or people’s entitlements. Make it easy for service desk staff to challenge an AI recommendation, correct the record and escalate an unusual case.
5. Monitor outcomes after launch
Governance does not end when a pilot is signed off. Track the quality of AI-generated answers, misrouted tickets, escalation rates, time to resolution, user feedback and the number of actions that require correction. Review performance when workflows, data sources or models change. Keep an audit trail that lets the team understand what the AI recommended and what action was ultimately taken.
How to make this work in a Singapore organisation
Start with one service workflow that has a clear business outcome, such as password-reset guidance, common software requests or routing incidents to the right support team. Document the current process, define what the AI is allowed to do, and agree on a baseline for service quality before enabling automation.
For organisations supporting staff across Singapore and the wider Asia-Pacific region, test the experience with different teams, locations, working hours and language needs. Make sure the knowledge base is current and that service ownership is clear across internal IT, outsourced providers and business application teams. If the underlying asset and service data is incomplete, AI will simply make inconsistent processes faster.
Where an ITSM platform fits
An ITSM platform can provide important governance controls by connecting service requests, incidents, changes, knowledge, assets and workflow history. EasyVista positions its platform around service management, monitoring, remote support, automation and AI. Buyers should assess how those capabilities work together in their own environment, rather than judging an AI feature in isolation.
During an evaluation, ask vendors to demonstrate permission boundaries, approval steps, audit history, data handling, exception management and the process for reviewing AI performance. Use realistic service desk scenarios and include the people who will operate the workflows after deployment.
Make trust part of the rollout
AI can help IT teams respond faster and reduce repetitive work, but speed alone is not a measure of success. A well-governed deployment gives staff clear boundaries, gives managers visibility into outcomes and gives users a route to human help when the automated answer is not good enough.
For Singapore businesses, the sensible path is to build governance into ITSM from the first use case: assign ownership, assess risk, protect data, retain human oversight and keep measuring results. That is how an AI pilot becomes a dependable part of service operations.
About EasyVista
EasyVista is a leading IT software provider delivering comprehensive IT solutions, including service management, remote support, IT monitoring, and self-healing technologies. We empower companies to embrace a customer-focused, proactive, and predictive approach to IT service, support, and operations. EasyVista is dedicated to understanding and exceeding customer expectations, ensuring seamless and superior IT experiences. Today, EasyVista supports over 3,000 companies worldwide in accelerating digital transformation, enhancing employee productivity, reducing operating costs, and boosting satisfaction for both employees and customers across various industries, including financial services, healthcare, education, and manufacturing.
About Version 2 Limited
Version 2 Digital is one of the most dynamic IT companies in Asia. The company distributes a wide range of IT products across various areas including cyber security, cloud, data protection, end points, infrastructures, system monitoring, storage, networking, business productivity and communication products.
Through an extensive network of channels, point of sales, resellers, and partnership companies, Version 2 offers quality products and services which are highly acclaimed in the market. Its customers cover a wide spectrum which include Global 1000 enterprises, regional listed companies, different vertical industries, public utilities, Government, a vast number of successful SMEs, and consumers in various Asian cities.
Parallels Desktop 27.1.0: What IT Teams Should Know About the Latest Update
For Singapore organisations that rely on Windows applications but standardise on Apple silicon Macs, virtualisation stability is more than a convenience. It can affect engineering work, software testing, finance operations and day-to-day productivity. Parallels Desktop 27.1.0, released on 29 October 2026, is a maintenance update focused on stability and compatibility across virtual machines.
What the 27.1.0 update changes
The update addresses several practical issues reported by users. It fixes a problem that prevented hard disk settings from being configured or changed in a virtual machine, and corrects a false non-SSD warning that could appear after upgrading to Parallels Desktop 27 when the TRIM option was incorrectly disabled.
For Windows virtual machines, Parallels lists fixes for OpenGL and 3D rendering problems that affected a range of CAD, modelling, navigation, benchmark and other applications. The named applications include SolidWorks, Rhino, DraftSight, ZW3D, PrusaSlicer and several specialist engineering tools. The update also addresses issues involving AirPods Pro 2 audio, shared iCloud folders, Coherence windows, Excel menus, shared printers and drag-and-drop in full-screen mode.
Linux and macOS virtual machines receive fixes too. These include a headless Parallels Tools installation issue on Ubuntu, image copy-and-paste failures between macOS and Ubuntu, and a freeze affecting nested virtual machines on Apple M4 and M5 hardware. Parallels also lists fixes for macOS virtual machine creation in daemon or automation environments.
Why this matters to Singapore IT teams
Many Singapore businesses support mixed-device environments. Developers may use Macs while still needing Windows-only tools; engineering teams may depend on specialist CAD software; and regional offices may share a common desktop standard across different locations. A compatibility issue in a virtual machine can quickly become a service desk ticket, a project delay or an avoidable workaround.
For teams using Parallels Desktop in a managed environment, the Enterprise Edition changes are worth noting. Version 27.1.0 adds an administrator policy to enforce a preferred virtual machine view mode — Window, Full Screen or Coherence — so users cannot change the setting themselves. The release also fixes several Golden Image deployment issues, including VM naming alignment, declarative deployment errors and installation freezes.
What administrators should do before rolling it out
- Check your current build. Confirm which Parallels Desktop 27 release is installed on managed Macs and identify devices still running earlier builds.
- Prioritise affected workloads. Test the update first on Macs used for CAD, 3D modelling, specialist Windows applications, Ubuntu development or automated VM provisioning.
- Validate business-critical workflows. Check graphics rendering, file sharing, audio devices, printing, Coherence mode and full-screen drag-and-drop — not just whether the VM starts.
- Review enterprise policies. If you use the Enterprise Edition, decide whether a centrally enforced view mode will reduce support overhead or disrupt users who rely on a particular workflow.
- Keep a rollback plan. Back up important virtual machines and confirm that your endpoint management and recovery procedures are ready before a wider deployment.
One more point: review the deprecation notices
The 27.1.0 notes also identify several lower-use features that are deprecated and may be removed in a future major release. These include certain startup behaviours, Dock and recent-file integrations, some full-screen and input options, and selected virtual hardware settings. Linux users should pay particular attention to the planned removal of the option to use Rosetta for running x86 binaries in Linux virtual machines. These are not all immediate removals, but they are a useful prompt to check scripts, user documentation and standard operating procedures.
Practical takeaway
Parallels Desktop 27.1.0 is primarily a reliability update rather than a headline feature release. Singapore IT teams should treat it as a targeted maintenance deployment: identify users with affected workloads, test the applications they actually depend on, and then roll it out through the organisation’s normal Mac management process. That approach is more useful than updating every device without checking what the virtual machines are being used for.
About Parallels
Parallels® is a global leader in cross-platform solutions, enabling businesses and individuals to access and use the applications and files they need on any device or operating system. Parallels helps customers leverage the best technology available, whether it’s Windows, Linux, macOS, iOS, Android or the cloud.
About Version 2 Limited
Version 2 Digital is one of the most dynamic IT companies in Asia. The company distributes a wide range of IT products across various areas including cyber security, cloud, data protection, end points, infrastructures, system monitoring, storage, networking, business productivity and communication products.
Through an extensive network of channels, point of sales, resellers, and partnership companies, Version 2 offers quality products and services which are highly acclaimed in the market. Its customers cover a wide spectrum which include Global 1000 enterprises, regional listed companies, different vertical industries, public utilities, Government, a vast number of successful SMEs, and consumers in various Asian cities.
