Skip to content

Lumu Recognized in 2026 Frost Radar

Frost & Sullivan Spotlights Lumu as an Innovation Leader in the 2026

Leveraging its signature Continuous Compromise Assessment framework, Lumu Defender proactively exposes network threats to secure user identities, cloud workloads, and connected devices.

Lumu, the cybersecurity trailblazer behind the Continuous Compromise Assessment® methodology, announced today that it has earned the title of “Innovative Leader” in Frost & Sullivan’s prestigious 2026 Frost Radar™ for Network Detection & Response.

The Frost Radar serves as a rigorous industry benchmark, measuring top-tier technology vendors across two critical dimensions: Innovation and Growth. Lumu’s prominent placement in the 2026 report validates the company’s commitment to democratizing enterprise-grade cybersecurity. By translating raw security telemetry into definitive, actionable intelligence, Lumu enables security operations centers (SOCs) of all sizes to rapidly identify verified breaches, prioritize responses, and neutralize threats without drowning in operational complexity.

Key Drivers of Lumu’s Leadership Recognition

Frost & Sullivan specifically commended Lumu for its technological breakthroughs, including:

  • AI-Powered Autonomy: Self-driving security operations driven by artificial intelligence.
  • The “Agentic SOC”: A specialized platform that acts as an autonomous extension of security teams.
  • Total Network Visibility: Comprehensive monitoring across full-spectrum hybrid environments.
  • SIEM Optimization: Dramatically reducing alert fatigue and the escalating costs associated with legacy SIEM platforms.
  • Relentless Threat Hunting: Retrospective analysis powered by the Continuous Compromise Assessment model.

The Engine: Lumu Defender

At the heart of this recognition is Lumu Defender, the company’s flagship platform. Going far beyond traditional network perimeters, Defender safeguards devices, identities, and workloads. It ingests vast quantities of network metadata and channels it through Lumu’s proprietary “Illumination Process.” This engine utilizes deep correlation analysis, AI-driven anomaly detection, and known Indicators of Compromise (IoCs) to pinpoint threats with exceptional accuracy.

Furthermore, Lumu operates as a collective defense matrix—constantly adapting to new attack vectors by learning from the aggregated network telemetry of its entire global customer base. When a threat is verified, Defender maps the attack techniques directly to the MITRE ATT&CK framework, displaying impacted assets and potential blast radius. Through Lumu AutoPilot and seamless integrations with over 125 third-party security tools, the platform instantly orchestrates an automated defensive response.

Industry Perspectives

“Every organization faces sophisticated cyber threats, but too many lack the capabilities, expertise, and resources to manage them effectively. For too long, advanced detection and response solutions have catered to the largest enterprises, leaving other organizations underserved. We built Lumu to make effective security operations accessible to organizations of all sizes around the world, and we’re proud to be recognized for that accomplishment. Our cloud-native approach delivers network-level visibility and automated response capabilities that help teams identify and contain threats faster, without the complexity, cost, or operational burden of traditional security tools.”
— Ricardo Villadiego, Founder and CEO of Lumu

“As organizations face increasingly sophisticated cyber threats, they need solutions that deliver more than visibility. Lumu stands out for its ability to turn network intelligence into actionable security outcomes through AI-driven automation and continuous compromise assessment. Its approach addresses critical challenges in security operations, including alert fatigue, deployment complexity, and limited resources, making advanced detection and response more accessible to organizations of all sizes.”
— Keith Beizer, Senior Industry Analyst at Frost & Sullivan

About Lumu

Lumu is a cybersecurity company that helps organizations operate cybersecurity proficiently by measuring and understanding compromise in real time. Through its Continuous Compromise Assessment® model, Lumu empowers security teams to act immediately on confirmed compromises and minimize risk exposure.

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.

Graylog 7.2.2 Arrives with Security Fixes: An Upgrade Checklist for Teams

Logs are only useful when teams can trust the platform collecting, searching and routing them. A dropped output, a broken pipeline or an access-control weakness can turn a central view of the environment into a source of uncertainty just when an incident needs investigating.

Graylog’s 7.2.2 maintenance release, published on 4 November 2026, is a timely reason for IT and security teams to review their upgrade plans. The core release includes security hardening and a collection of fixes, while the matching Enterprise 7.2.2 update addresses several operational issues, including Kafka output handling and archive deletion.

What changed in Graylog 7.2.2

Graylog’s core changelog lists a mix of reliability fixes and security updates. The security items are particularly relevant to administrators:

  • Raw message parsing is more tightly permissioned. The endpoint now requires permission to create inputs or pipeline rules, helping prevent server-file probing through that endpoint.
  • Password-change handling has been hardened. This is a security-focused improvement to an important account-management path.
  • Dependencies have been updated. The release updates Jackson to 2.22.4 to address CVE-2026-110879, updates lz4-java to 1.12.1, and moves to OkHttp 5.5.1, which adds a TLS blocklist for eight compromised eMudhra intermediate CA certificates.

The same core release also fixes issues involving lookup-table default values, GeoIP database downloads across regions, event-definition pages, PDF report rendering and other parts of the administration experience. These are maintenance improvements rather than a headline new feature set.

For Enterprise users, the 7.2.2 changelog includes a fix intended to prevent Kafka output messages from being dropped when authentication, TLS or authorisation fails. It also changes archive deletion so that archives are removed through the backend on which they were written, addressing failures when archives span multiple backends. Other fixes cover OIDC login callbacks, report-generation warnings and log-view sorting.

Why this matters to IT teams

A logging or SIEM platform often sits across identity systems, endpoints, cloud services, firewalls, business applications and infrastructure. Its reliability affects more than the security team: infrastructure operations, audit preparation and incident response all depend on accurate, searchable records.

The Kafka fix is a useful example. If an output encounters an authentication or TLS problem, administrators need clear failure handling and confidence that messages are not silently lost. Likewise, archive operations need to behave predictably so that retained evidence can be managed and retrieved when required.

Logs may also contain usernames, email addresses, IP addresses, device identifiers and other information that can relate to individuals. Organisations should treat that data with appropriate care. The PDPA includes protection and retention-limitation obligations, so access controls, retention schedules and any overseas processing or transfer arrangements should be part of the logging design.

A practical upgrade checklist

  1. Confirm exactly what you run. Record whether the environment uses Graylog Open, Enterprise or Security, the current server and Data Node versions, and the versions of inputs, collectors and integrations. Do not assume the core and Enterprise changelogs describe identical changes.
  2. Read the full release notes and upgrade guidance. Check the supported upgrade path, dependency requirements and any product-specific instructions before scheduling a change.
  3. Back up the right components. Confirm that configuration, metadata and required log data or archives can be restored. Test the recovery process rather than relying on a backup job that has never been validated.
  4. Test the critical paths in staging. Exercise authentication and SSO, inputs, pipelines, lookup tables, event definitions, dashboards, reports, Kafka outputs and archive workflows. Include failure tests for expired credentials, rejected TLS connections and unavailable destinations.
  5. Review permissions and secrets. Check who can create inputs and pipeline rules, who can administer accounts, and how service credentials and certificates are stored and rotated.
  6. Validate after the upgrade. Monitor input health, processing queues, output failures, Data Node and search-cluster health, index growth, archive jobs and alert delivery. Compare event volumes with the pre-upgrade baseline.

Keep log data useful — and proportionate

More data is not automatically better. Agree which systems must be logged, which fields are necessary for detection and investigations, who can search sensitive records, and how long each class of data should be kept. Where logs contain personal data, align retention with a defined operational or legal purpose instead of keeping everything indefinitely.

For teams operating across Singapore and other markets, also map where logs are stored, which support teams or service providers can access them, and whether cross-border transfers are involved. These are governance and architecture decisions for the organisation; upgrading Graylog does not settle them on its own.

Use the release as a maintenance checkpoint

Graylog 7.2.2 is best approached as a security and reliability maintenance update, not as a promise of a new capability. Review the fixes against your own deployment, test the integrations that matter most, and schedule the change with a rollback plan and clear owners.

That disciplined approach helps Singapore teams keep log management dependable while reducing avoidable risk in the systems that support monitoring, investigations and day-to-day IT operations.

About Graylog
At Graylog, our vision is a secure digital world where organizations of all sizes can effectively guard against cyber threats. We’re committed to turning this vision into reality by providing Threat Detection & Response that sets the standard for excellence. Our cloud-native architecture delivers SIEM, API Security, and Enterprise Log Management solutions that are not just efficient and effective—whether hosted by us, on-premises, or in your cloud—but also deliver a fantastic Analyst Experience at the lowest total cost of ownership. We aim to equip security analysts with the best tools for the job, empowering every organization to stand resilient in the ever-evolving cybersecurity landscape.

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.

MSP Network Security: Make Every Customer Rollout Repeatable

For a managed service provider, adding another security product to the catalogue is rarely the difficult part. The work begins when the first customer needs it deployed, the second customer has a different endpoint mix, and the third wants the same outcome without another round of manual setup. That is where MSP network security becomes an operating-model question, not just a product decision.

Nord Security’s work with Acronis is a useful example of why integrations matter. The goal is not simply to connect two logos. It is to reduce the number of separate steps an MSP has to manage when delivering network protection across a customer base.

The operational tax hides in every rollout

MSPs often standardise their service descriptions long before they standardise the work behind them. A new customer still means checking the device estate, deciding who owns deployment, coordinating maintenance windows, confirming that endpoints have received the right software and explaining what happens when an installation fails.

Multiply those steps across several customer environments and the service desk becomes the glue between tools. Engineers switch consoles, chase deployment status and repeat tasks that should feel routine. The result is slower onboarding and less time for the work customers actually value: improving security posture, resolving incidents and planning the next stage of their IT environment.

A good integration should remove friction from a specific workflow. It should not be treated as a magic button that replaces service design, customer communication or operational checks.

What the Nord Security and Acronis connection changes

On 26 June 2026, Nord Security announced a partnership with Acronis to bring NordLayer deployment into Acronis Cyber Protect Cloud. The integration uses a NordLayer security deployment agent so MSPs can roll out NordLayer across multiple customers and endpoints from the Acronis console, rather than handling each installation as a separate manual task.

That matters because the deployment step is often repeated. If a provider already uses Acronis Cyber Protect Cloud to manage customer protection, being able to initiate NordLayer deployment from the same operational environment can reduce context switching and make the process easier to standardise.

The integration does not remove the need to define access policies, confirm device coverage or manage exceptions. It gives the MSP a more connected starting point for delivering those activities.

Turn the integration into a service playbook

Before rolling the workflow out to every customer, document a simple service pattern that engineers can repeat:

  • Establish the baseline. Record the customer’s users, endpoint groups, locations and agreed network-security requirements. Keep customer-specific decisions visible instead of relying on an engineer’s memory.
  • Pilot with a representative group. Choose a small set of endpoints that reflects the customer’s real mix of devices and working patterns. Confirm the deployment process, user impact and support hand-off before expanding.
  • Make exceptions explicit. Identify devices that cannot be updated during the normal window, systems that need special handling and users who require a different access arrangement. Assign an owner and review date to each exception.
  • Close the loop. Confirm which endpoints completed deployment, which need attention and who will follow up. A deployment request is not finished just because it was launched from a console.

This playbook can be adapted for different service tiers without pretending every customer is identical. The baseline stays consistent; the approved policies and exceptions reflect each customer’s needs.

Measure the service, not just the software installation

Acronis published a Nord Security case study on 24 September 2026 that reported device adoption had grown by 350% in the first five months of the ecosystem partnership. The case study also said the partnership gave Nord Security exposure to more than 21,000 Acronis service providers. Those are vendor-reported results, not a guarantee that every MSP will see the same outcome, but they underline the commercial value of making a security service easier to reach and deploy.

For an MSP, useful operational measures are more specific: time from customer approval to first protected endpoint, percentage of the agreed estate covered, number of failed or deferred deployments, repeat support tickets and the time needed to resolve exceptions. Review those figures by customer and service tier. They reveal whether the integration is improving delivery or simply moving the manual work somewhere else.

Keep customer environments distinct while the workflow stays consistent

Standardisation should make the service predictable, not flatten every customer into one policy. A professional-services firm, a retail group and a manufacturer may have different working hours, device ownership models and tolerance for change windows. Keep the onboarding checklist and reporting format consistent, while validating the access requirements and rollout plan with each customer.

It is also worth agreeing who owns each decision. The MSP may operate the deployment, but the customer should still approve the users, devices and access requirements covered by the service. Clear ownership prevents a convenient integration from turning into an unclear responsibility boundary.

Make the next customer easier than the last

When evaluating MSP network security solutions, look beyond the feature list. Ask how deployment fits into the tools your engineers already use, what evidence confirms that coverage is complete, how customer-specific exceptions are handled and how the service will be reported month after month.

Nord Security’s Acronis integration points towards a more repeatable way to deliver NordLayer across customer environments. The real benefit for an MSP comes when that technical connection is backed by a clear playbook, measurable service outcomes and a customer experience that feels organised from the first rollout.

About Nord Security
Nord Security is a cybersecurity company known for its flagship product, NordVPN. The company is dedicated to providing online security and privacy solutions to individuals and businesses globally.

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.

Guardz Brings Prisma Browser Protection to MSPs: What Buyers Should Check

For many employees, the browser is the real front door to work. It is where they open Microsoft 365, Google Workspace, finance systems, customer records and increasingly, generative AI tools. That makes browser sessions, extensions and file transfers an attractive target for attackers — even when endpoint and email controls are already in place.

Guardz’s latest move puts that risk in the spotlight. The company has announced an integration of Palo Alto Networks’ Prisma Browser for Business into its MSP-focused security platform. For service providers and IT leaders, the announcement is worth watching, but there is an important availability detail to check before planning a rollout.

What Guardz has announced

On 2 November 2026, Guardz announced that Prisma Browser for Business is joining its platform, connecting browser protection with email, identity, endpoint, data and user-risk signals. The aim is to help MSPs investigate related activity as one incident instead of treating a suspicious web page, email and endpoint alert as unrelated events.

The announced capabilities include:

  • Phishing and session-theft protection: inline machine-learning detection and Advanced URL Filtering to help block malicious pages, including fake sign-in pages and attempts to steal active session tokens.
  • File and extension controls: WildFire file analysis, scanning of browser uploads and downloads, and identification of risky extensions.
  • Connected investigations: browser events can be correlated with the original email, Microsoft 365 activity and endpoint telemetry to give analysts a wider view of activity around one identity.
  • AI usage controls: technicians can apply client-specific restrictions on copying, pasting, uploading and downloading content by website or category. A per-client AI usage report is also intended to show which tools are being used.

Guardz says deployment can be managed through the platform and rolled out using RMM or MDM. The announcement describes an extension for existing Chrome and Edge profiles, with a standalone browser option for Linux and other situations where protection should not depend on the browser already installed.

Why the browser deserves its own security review

Traditional security tools still matter, but each sees a different part of the story. Email security may identify the lure. Identity monitoring may spot an unusual sign-in. Endpoint detection may see a process launch. None of those views automatically explains what happened inside the browser session that connected them.

That gap matters when an attacker steals a session token after a user completes MFA, abuses a malicious extension, or tricks someone into pasting a command from a web page. It also matters when employees move business information into unapproved AI services through normal browser actions.

For MSPs supporting several customers, the operational challenge is multiplied across tenants. A useful browser-security layer should make it easier to connect a web event to the user, device, application and data involved — without forcing technicians to jump between disconnected consoles for every investigation.

What MSPs should confirm first

Product availability: Guardz’s 2 November launch article says the browser-security offering is currently available to MSPs in the United States and directs organisations elsewhere to contact their local Guardz team. Partners should therefore confirm local availability, licensing, support arrangements and any rollout prerequisites before quoting or promising the capability.

Coverage and compatibility: Ask which browsers, operating systems and device-management methods are supported in the relevant market. Confirm how unmanaged devices, personal profiles, remote workers and shared workstations are handled. A browser control that only covers part of the fleet can leave an awkward blind spot.

Policy detail: Check exactly what administrators can restrict — such as uploads, downloads, copy and paste, extension installation or access to selected AI sites. Understand whether policies can differ by customer, department, device and sensitivity level, and how exceptions are approved.

Investigation workflow: Ask to see a realistic demonstration that links a browser event with email, identity and endpoint evidence. Confirm what analysts can search, what gets retained, how incidents are escalated and which response actions are automated versus handled by a human analyst.

Privacy and data handling: Browser telemetry can reveal employee activity and may include customer or employee personal data. Organisations should document the purpose of monitoring, restrict access to investigation data, set sensible retention periods and assess any overseas processing or transfers against their PDPA responsibilities. These are governance checks for the buyer, not a claim that any product by itself makes an organisation compliant.

Make it a layer, not a silver bullet

Browser protection should complement — not replace — endpoint detection, identity controls, email security, secure configuration and user awareness. A pilot is a sensible way to test whether the extra visibility improves detection and response without disrupting everyday work.

Start with a small group that uses business-critical SaaS applications and approved AI tools. Measure deployment effort, blocked threats, false positives, policy exceptions and the time needed to investigate a test scenario. Then decide whether the operational benefit justifies a wider rollout.

The direction is clear: as more business activity moves into browser sessions, security teams need visibility at that layer too. For MSPs, the next step is to validate regional availability and prove that browser signals genuinely improve the incident picture across each customer environment.

About Guardz
Guardz is on a mission to create a safer digital world by empowering Managed Service Providers (MSPs). Their goal is to proactively secure and insure Small and Medium Enterprises (SMEs) against ever-evolving threats while simultaneously creating new revenue streams, all on one unified platform.

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.

From HR Record to Network Access: Building a Cleaner Employee Lifecycle with NAC Integration

When someone joins a company, changes teams or leaves, their network access should follow the change. In many organisations, though, the HR record, directory account, device inventory and network policy are maintained in separate places. The result is familiar: a new starter waits for access, a mover keeps permissions from an old role, or a leaver’s network access is only removed after someone remembers to raise a ticket.

A well-planned network access control integration can make those hand-offs more consistent. Rather than treating access as a series of one-off requests, IT teams can connect the systems that already know who a person is with the controls that decide which devices and identities can use the network.

The hand-off is where access gets messy

Most access problems are not caused by a lack of policy. They happen because the right information reaches the right team too late. HR knows that an employee has changed department. The directory knows which account belongs to that person. The network sees a laptop, phone or other endpoint trying to connect. If those systems do not exchange useful context, an administrator has to bridge the gap manually.

That manual process becomes harder when a business has multiple offices, remote users, contractors and shared devices. A checklist may work for a small team, but it is easy to miss one wireless network, VPN route or device group when the environment grows.

Connect the systems that already know the person

Start by identifying the authoritative source for each piece of information. HR should own employment status and organisational changes. A directory or identity provider should own account identity and group membership. Endpoint management should provide device context. Network access control should apply the relevant access decision when a user or device connects.

NACVIEW describes the ability to retrieve endpoint data from sources such as Active Directory, SQL databases, LDAP and RADIUS. Its solution information also describes two-way integration with security tools such as MDM, SIEM, firewall and UTM platforms. Those connections can help reduce repeated data entry and give access decisions more context than a username alone.

The important design choice is not to connect everything at once. Agree which system is authoritative for each attribute, how often updates are exchanged, and what should happen when a record is incomplete or a connector is unavailable.

Three employee events worth automating first

New starter: make the first connection predictable

When a new employee is approved, the workflow should establish the identity, assign the appropriate directory groups and prepare the network policy before the person arrives. Keep the initial access set narrow. Add access to additional systems only when the role requires it and the relevant owner has approved the change.

Role change: remove yesterday’s access as well as adding today’s

A department transfer is not simply an instruction to add another group. Review the permissions that were appropriate for the previous role and remove those that are no longer needed. This is especially important for shared workstations, privileged support accounts and devices used across teams.

Departure: close the network path, not just the mailbox

When an employee leaves, the offboarding workflow should coordinate directory status, remote access and the network policy that applies to their devices. Define how exceptions are handled for handover periods, legal holds or approved contractors, and record who authorised them.

Where NACVIEW adds network context

Identity records explain who should be allowed to connect; network access control helps apply that decision to the actual connection. NACVIEW’s published solution overview covers wired, wireless and VPN access, device identification and visibility, and the use of directory and authentication data. It also describes integration with other security platforms so a network response can be coordinated with information from the wider environment.

The company has also described a university deployment in which integration with HR and student-service systems helped automate the granting and blocking of network access as people started or ended their relationship with the institution. That is a useful illustration of the lifecycle model: access changes because the source record changes, not because an administrator has to remember a separate network task.

Keep automation safe when identity data is imperfect

Automation should make the expected path faster without turning a bad record into a broad outage. Before enabling automatic changes, decide how to handle duplicate names, missing employee IDs, delayed HR updates, service accounts and devices that are shared between users. For high-impact changes, consider a review queue or a short approval step rather than silently applying every update.

  • Use a stable identifier, not a display name, to match records.
  • Log the source and time of every lifecycle change.
  • Define a fallback when a directory or integration service is unavailable.
  • Test both access removal and access restoration before expanding the workflow.
  • Keep emergency and service accounts under a separately reviewed process.

Prove the workflow with a small pilot

Choose one department, one site or one clearly defined user group. Measure how long a new starter waits for network access, how quickly a departure is removed from relevant access paths, how many manual tickets are still needed and how often administrators have to correct an identity match. Review the exceptions with HR, service desk and network teams before widening the scope.

The best network access control integration is not the one with the most connectors. It is the one that turns reliable identity changes into consistent network decisions, while leaving a clear trail when a human needs to step in.

About NACVIEW
A powerful network access control (NAC) solution designed to provide organizations with comprehensive visibility and control over their network infrastructure. Developed by leading network security company, NACVIEW offers advanced features and capabilities to ensure secure and efficient network access for users and devices.

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.

GREYCORTEX Mendel 5.0: A Smarter Way to Prioritise IT/OT Network Risk

Security teams rarely struggle to collect enough alerts. The harder job is deciding which device deserves attention first, understanding what it is communicating, and turning that evidence into an action that does not disrupt business operations.

That challenge gets more complicated in mixed IT and operational technology (OT) environments. Servers, workstations, cameras, printers, medical devices and industrial controllers do not all behave alike, and many cannot be treated like a standard employee laptop. Network visibility becomes an important part of the picture.

Start with the device that is becoming risky

GREYCORTEX Mendel 5.0 introduces a device risk score based on security events and how unusual a device’s behaviour is compared with other devices on the same network. The score is tracked over time, so analysts can see whether a host is becoming riskier rather than treating every alert as an isolated event.

That historical view can help a small security team prioritise investigation. A device whose score is climbing may deserve a closer look than a host that has generated the same low-level noise for weeks. It is still a triage signal, not an automatic incident verdict: teams should validate the score against asset criticality, maintenance windows and what the system is meant to do.

Follow the traffic to understand the context

Once a device looks unusual, the next question is what it is talking to. Mendel 5.0’s Traffic Flow Map puts a host and its significant communication partners into one view. Analysts can inspect connections using measures such as flows, packets, data volume, retransmissions and unreplied flows, then move from one device to another without leaving the map.

For an IT/OT environment, that context matters. A workstation suddenly communicating with an unfamiliar server is one kind of investigation; a controller exchanging traffic with an approved engineering station during a planned maintenance window is another. A visual path through the connections helps the analyst ask better questions before escalating or blocking traffic.

Use AI assistance to speed up the first pass

Mendel 5.0 also adds an AI Assistant that explains devices, IP addresses and security events in plain language. GREYCORTEX says it can identify likely device roles, assess external IP addresses, explain an event, estimate whether it may be a false positive and suggest investigation steps in priority order.

That can make technical findings easier to hand over to an operations colleague or manager who does not spend all day reading network telemetry. Treat the assistant as decision support, though. Confirm its interpretation with packet evidence, asset records and the people responsible for the affected process—especially before taking action on production OT equipment.

Why this is relevant to operators

Singapore’s Cyber Security Agency has been putting greater emphasis on visibility and readiness for critical infrastructure. In a July 2026 speech, Minister Josephine Teo described the priorities as “lock down, find first, and fix fast”, and highlighted the difficulty of seeing what is happening inside many OT environments. CSA’s updated Cybersecurity Code of Practice for Critical Information Infrastructure was issued on 29 July 2026.

For organisations that operate or support essential services, the practical takeaway is straightforward: do not assess network detection only by the number of alerts it generates. Ask whether it helps your team discover unfamiliar assets, understand communications between connected systems, investigate unusual behaviour and coordinate a safe response. The same discipline is useful for manufacturers, logistics operators, healthcare groups and other businesses with connected facilities, even when they are not designated CII owners.

A practical evaluation checklist

  • Coverage: Confirm which network segments, sites, VLANs and OT zones can be monitored, and identify any blind spots.
  • Asset context: Check how the platform identifies devices and how teams can correct or enrich asset details.
  • Prioritisation: Ask how risk scores are calculated, what changes them and how analysts can review score history.
  • Investigation: Test whether traffic maps help analysts trace a device’s communication path and distinguish normal operational traffic from suspicious activity.
  • Response: Agree who can approve containment or blocking actions, and how IT and OT teams will coordinate during an incident.
  • Deployment and data handling: GREYCORTEX says Mendel runs on-premises, including in fully air-gapped deployments; its AI processing runs within EU infrastructure and can be disabled. Buyers should validate telemetry flows, data handling and AI settings against internal policy before deployment.

Make the investigation workflow the measure of success

A network detection platform should do more than add another console to the security stack. The useful test is whether it helps an analyst move from “something looks odd” to “this is the device, this is its communication path, this is why it matters, and this is the next safe step”.

Mendel 5.0’s risk scoring, Traffic Flow Map and AI Assistant are designed around that workflow. IT and OT teams evaluating the platform should test those capabilities with representative traffic and real operational scenarios, then measure investigation time, false-positive handling and the quality of evidence they can hand to incident responders.

About GREYCORTEX
GREYCORTEX uses advanced artificial intelligence, machine learning, and data mining methods to help organizations make their IT operations secure and reliable.

MENDEL, GREYCORTEX’s network traffic analysis solution, helps corporations, governments, and the critical infrastructure sector protect their futures by detecting cyber threats to sensitive data, networks, trade secrets, and reputations, which other network security products miss.

MENDEL is based on 10 years of extensive academic research and is designed using the same technology which was successful in four US-based NIST Challenges.

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.

Keepit’s 2026 Data Report: Why SaaS Recovery Testing Must Start with Identity

Most organisations have a plan for getting a deleted document or mailbox back. Fewer have rehearsed what happens when the identity service that controls access to those applications is the thing that fails.

That gap matters as businesses move more day-to-day work into Microsoft 365, Google Workspace, Salesforce and other SaaS platforms. A backup can contain the data, but recovery still depends on people being able to authenticate, reach administration tools and restore the right configuration in the right order.

Keepit’s Annual Data Report 2026 offers a useful prompt for reviewing that dependency. The report is based on aggregated, anonymised backup and restore activity from Keepit’s production environment between 1 January and 31 December 2025. It is operational data rather than a survey, but it reflects activity within Keepit’s own customer environment and should not be read as a universal industry benchmark.

Three findings worth taking seriously

Keepit highlights three patterns in the report:

  • Bulk recovery is being tested: nine in ten enterprises in the dataset had validated bulk recovery. That is an encouraging sign that many organisations are practising larger-scale recovery, not just assuming it will work.
  • Identity recovery gets less attention: identity systems were tested around four times less often than productivity systems. That is a significant gap when identity is the control plane for access to other SaaS applications.
  • Most restores are small and targeted: 90% of restores were single-file downloads. Everyday recovery is often about putting one item back quickly, rather than rebuilding an entire environment.

The takeaway is not that every business needs to run a full disaster-recovery exercise every week. It is that recovery testing should reflect the incidents teams are likely to face, while also covering the less frequent failures that could lock administrators out of everything else.

Why identity can become the recovery bottleneck

Identity platforms manage much more than usernames and passwords. They can control single sign-on, multifactor authentication methods, conditional access policies, group membership, privileged roles, application registrations and service principals used by integrations and automation.

If a user deletes a file, an administrator may be able to restore that file while the rest of the tenant keeps working. If a privileged identity is compromised, a conditional access policy is changed incorrectly, or a critical application registration disappears, the impact can spread across multiple services.

There is also a recovery dependency that is easy to miss: administrators may need the identity platform to sign in to the backup console, ticketing system, documentation repository or cloud management portal. If the identity service is unavailable or untrusted, a recovery plan that starts with “log in and restore” may not be usable.

That is why identity should be treated as part of the recovery sequence, not simply as another SaaS workload to protect.

Where Keepit’s product direction fits

Keepit’s product story is increasingly framed around protecting a trusted copy of business data that can be used for recovery and, over time, as a governed foundation for AI. In August 2026, the company announced AI Truth Cloud, organised around five pillars: Protect, Observe, Recover, Prove and Integrate.

Keepit described AI Connector Backup, its Model Context Protocol platform and AI Safe Room as core capabilities forming the immediate roadmap foundation. The announcement discusses protection for AI-related assets such as agent configurations, skills, projects and models, as well as ways to connect AI workflows to managed data. Buyers should confirm which of these capabilities are generally available, which are in development, and what is included in their specific subscription before treating them as deployable features.

Keepit also publishes protection services for business applications including Microsoft 365, Microsoft Entra ID, Salesforce, Google Workspace, Jira, Confluence and Okta. For an organisation, the practical question is whether the applications and data objects it relies on are covered at the level needed for a real recovery scenario.

A practical recovery checklist for IT teams

  1. Map the dependencies. List the SaaS services that support critical business processes, then map the identity provider, SSO configuration, DNS, administrator accounts and integrations each one depends on. Include the systems used to access backup and recovery tools.
  2. Test more than file restores. Keep granular tests for deleted files, messages and records, but add controlled exercises for bulk recovery and identity configuration. Include representative users, groups, privileged roles, authentication methods, conditional access policies and application registrations.
  3. Prove you can get in during an identity incident. Validate break-glass accounts, offline runbooks and emergency access to backup tooling. Use credentials and administration paths that do not rely entirely on the identity service being tested.
  4. Keep the recovery copy outside the production blast radius. Ask how backup data is isolated, whether it is immutable, who can administer or delete it, and whether production administrators can shorten retention or alter recovery points. Separate credentials and administrative control are as important as the storage location.
  5. Measure recovery against business needs. Set realistic recovery time and recovery point objectives for each application. During exercises, record how long it takes to locate the right restore point, recover the data, validate permissions and dependencies, and return the service to users.
  6. Review data location and handling. Ask where backup data is stored, who can access it for support, whether subprocessors are involved, how long data is retained, and how deletion and incident notification are handled. Organisations should assess any overseas transfer of personal data against the PDPA’s Transfer Limitation Obligation, and ensure reasonable protection and appropriate retention practices. A backup product does not by itself make an organisation PDPA-compliant.
  7. Include AI-related data in the inventory. If teams use AI assistants or agents connected to SaaS applications, identify the configurations, prompts, project data, permissions and integration records that would be difficult to recreate. Ask vendors what is protected today and what remains on the roadmap.

Residency is not the same as recoverability

Keepit’s October 2026 writing on cloud sovereignty makes a useful distinction: knowing where data is stored and who controls the provider is not the same as knowing whether the organisation can restore data after an outage, compromise or accidental deletion. Its discussion of the proposed EU Cloud and AI Development Act is about a European policy proposal, not a legal requirement. The broader procurement lesson still applies here: evaluate both data control and the independence of the recovery path.

For buyers, that means asking not only where a backup resides, but also whether it is separately administered, protected from production credentials, recoverable if the primary identity service is down, and handled in line with the organisation’s own privacy and retention obligations.

Turn backup confidence into tested recovery

Keepit’s report points to a straightforward improvement: do not let identity recovery remain the part of the SaaS plan that nobody practises. Start with one critical workload, test a small set of identity objects in a controlled environment, and then run an exercise that follows the full sequence from emergency access through to application recovery.

That kind of rehearsal gives IT leaders something more useful than a green backup dashboard: evidence that people, access paths and recovery procedures can work together when the business needs them most.

About Keepit
At Keepit, we believe in a digital future where all software is delivered as a service. Keepit’s mission is to protect data in the cloud Keepit is a software company specializing in Cloud-to-Cloud data backup and recovery. Deriving from +20 year experience in building best-in-class data protection and hosting services, Keepit is pioneering the way to secure and protect cloud data at scale.

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.

TACACS+ Solution for Network Device Access: Make Every Admin Change Traceable

Portnox passwordless zero trust access for console-based applications including RDP, SSH, VNC and Telnet
Portnox passwordless zero trust access for console-based applications including RDP, SSH, VNC and Telnet

A network engineer is halfway through a firewall change when a question lands in the incident channel: who made the last configuration change on the switch upstream? The device is reachable, the service is still running, but the team cannot confidently connect the change to a person, an approval or a command history. That is not just an audit headache. It makes troubleshooting slower and turns routine administration into a trust exercise.

Network infrastructure needs its own access-control discipline. A shared administrator password may get the job done, but it makes individual accountability difficult. A stronger design separates who can reach a device, what that person can do once connected and how the activity is recorded.

Three questions every admin session should answer

For switches, routers, firewalls and other network appliances, start with the familiar AAA model: authentication, authorisation and accounting.

  • Authentication: Is this the named administrator, using an approved identity and a strong sign-in method?
  • Authorisation: Which devices and commands is that administrator allowed to use? Read-only troubleshooting should not automatically carry the same privileges as a configuration change.
  • Accounting: What did the administrator actually do, on which device and at what time? A login record alone is not a useful substitute for command-level evidence.

Centralising these decisions helps avoid a different local account and password policy on every device. It also gives the security team a consistent way to remove access when roles change or a contractor’s engagement ends.

Why TACACS+ is relevant to infrastructure teams

TACACS+ is commonly used to centralise authentication, authorisation and accounting for network-device administration. Its command-authorisation model is particularly useful when an organisation wants to distinguish between viewing a configuration, running diagnostic commands and changing production settings.

Portnox describes its cloud-delivered TACACS+ service as a way to centralise authentication and granular command authorisation for routers, switches, firewalls and other critical systems, with detailed session logging. That gives network teams a route to more consistent controls without treating every device as a separate identity-management island.

RADIUS and TACACS+ are sometimes discussed together because both appear in network access architectures, but they are not interchangeable in every deployment. RADIUS is widely used for user and device network authentication, while TACACS+ is often selected when administrators need more granular control and accounting for commands executed on network equipment. Map the actual use cases before deciding which protocol belongs at each enforcement point.

Keep the management plane separate from everyday connectivity

One common mistake is to treat an administrator’s access path as just another user connection. The management plane deserves tighter controls than ordinary browsing or office Wi-Fi.

Use individual administrator identities wherever possible. Define role-based command sets for network operations, security engineering, service providers and read-only auditors. Keep emergency access separate, tightly monitored and tested. If a supplier needs to maintain one firewall, do not give that account the same reach as an internal infrastructure lead.

Also review the surrounding controls: multi-factor authentication or certificate-backed identity where supported, a restricted management path, device posture checks for the administrator’s endpoint, and a documented approval process for high-impact changes. Centralised command accounting is most valuable when it can be matched with a change ticket and a named owner.

Do not confuse device administration with remote application access

Network teams often need to secure more than a switch command line. They may also connect to server consoles, remote desktops or management applications. Those are related problems, but they are not the same enforcement point.

In a 10 February 2026 announcement, Portnox said its passwordless Zero Trust Network Access capabilities were expanding to console-based applications, including RDP, SSH, VNC and Telnet. The announcement described certificate-based authentication, continuous device-posture checks and risk-adaptive policies for those connections.

That ZTNA layer can complement infrastructure AAA: use application-level access controls to govern who can establish a remote console session, and use TACACS+ where network-device command authorisation and accounting are required. Keep the boundaries clear in the architecture so a successful remote login is not mistaken for approval to run every privileged command.

Make the audit trail useful during a real incident

Logs are only valuable if responders can answer practical questions quickly. Decide what evidence should be retained, who can review it and how it connects to your change-management process. For critical devices, the record should help an investigator identify the administrator, target device, command activity and session timing without stitching together screenshots and chat messages.

Test the failure cases too. What happens if the central authentication service is unavailable? Which emergency accounts remain available, who can use them and how is their use reviewed afterwards? A resilient design should not force engineers to choose between restoring a service and following a security policy.

A focused rollout beats a network-wide switch flip

Start with a small group of non-critical devices and a handful of administrator roles. Inventory the platforms and firmware versions, identify the protocols they support, define read-only and change-capable command sets, then test normal access, denied commands, emergency access and log review.

Before expanding, confirm that the process works for internal staff and approved service partners. Measure how quickly access can be granted and revoked, whether the audit trail answers the questions an incident responder would ask, and how much manual administration has been removed.

A TACACS+ solution should make network administration more accountable without turning every maintenance task into a paperwork marathon. When identity, command permissions and session records line up, teams can troubleshoot with greater confidence and prove who changed what when it matters.

About Portnox
Portnox provides simple-to-deploy, operate and maintain network access control, security and visibility solutions. Portnox software can be deployed on-premises, as a cloud-delivered service, or in hybrid mode. It is agentless and vendor-agnostic, allowing organizations to maximize their existing network and cybersecurity investments. Hundreds of enterprises around the world rely on Portnox for network visibility, cybersecurity policy enforcement and regulatory compliance. The company has been recognized for its innovations by Info Security Products Guide, Cyber Security Excellence Awards, IoT Innovator Awards, Computing Security Awards, Best of Interop ITX and Cyber Defense Magazine. Portnox has offices in the U.S., Europe and Asia. For information visit http://www.portnox.com, and follow us on Twitter and LinkedIn.。

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.

Backup and Disaster Recovery Software: Keep Windows Recovery Media Current

A backup job can finish successfully and still leave an uncomfortable question hanging over the IT team: can the organisation actually start the machine it needs to restore? Recovery depends on more than the backup image. The boot environment, storage and network drivers, recovery tools and target hardware all have to work together when the pressure is on.

That is why recovery media deserves its own maintenance routine. Actiphy’s 6 November 2026 update is a timely reminder: the company released an ActiveImage Protector patch and new builds of Boot Environment Builder and Actiphy Rapid Deploy to support a re-released Windows Assessment and Deployment Kit (ADK).

Recovery media has a software lifecycle too

When a recovery workflow uses Windows PE-based media, the Windows ADK is part of the toolchain used to build that environment. An updated ADK can change the foundation on which recovery or deployment media is built. If the media is treated as a one-time project, it can quietly fall behind the operating systems, drivers and hardware that the business now runs.

Actiphy’s 6 November notice identifies Windows ADK version 10.1.26100.9457, re-released in September 2026, as the compatibility target. The update covers ActiveImage Protector patch 26.10.29.1, Boot Environment Builder 1.0.17.1587 and Actiphy Rapid Deploy 5.1.2.762. It is a compatibility update, not a claim that every recovery scenario is automatically validated by installing the patch.

ActiveImage Protector supports image-based protection for physical and virtual Windows and Linux environments, while its product documentation describes both Windows PE and Linux-based boot environments. That flexibility makes it even more important to record which recovery path is used for each workload.

Separate a successful backup from a successful restore

Backup reports usually tell administrators whether data was copied and whether a job completed. A restore rehearsal answers a different question: can the team use that copy to bring a system or its data back in a realistic environment?

For a Windows server, the recovery team may need to boot from prepared media, recognise the storage controller, obtain network connectivity, locate the backup repository and select the correct recovery point. A missing driver or an outdated boot image can turn a routine restore into a prolonged troubleshooting exercise.

File-level recovery also matters. A request to retrieve one deleted folder should not require the team to rebuild an entire server if the backup platform supports granular recovery. Actiphy’s ActiveImage Protector documentation describes image-based backups as well as point-in-time file and folder recovery, so teams can plan different restore paths for different incidents.

Build a repeatable validation routine

After updating the relevant Actiphy components, use a short, documented test cycle rather than assuming the new media is ready:

  • Inventory recovery paths. Record which physical servers, virtual machines and endpoints rely on Windows PE media, Linux media or another recovery method.
  • Rebuild the media that matters. Use the supported Boot Environment Builder version and keep the build date, ADK version and driver set with the image.
  • Boot representative hardware. Test a sample of the actual server and workstation models in use, including the storage and network adapters that recovery depends on.
  • Locate a real recovery point. Confirm that the booted environment can reach the relevant local, network or cloud repository and display the expected backup images.
  • Restore into an isolated target. Validate a representative machine or workload without overwriting production. Check that the restored operating system starts and that the application owner can complete a basic functional test.
  • Record elapsed time. Compare the result with the recovery time objective and note any manual steps that would be difficult to repeat during an actual outage.

Keep the test evidence with the recovery runbook. If a hardware model, storage controller, network path or operating-system baseline changes, the team can see which parts of the test need to be repeated.

Reduce the work left on protected systems

Recovery readiness is also affected by what happens after a backup has been written. Verification, replication, consolidation and boot checks can consume processing time and create additional administration when they are run separately across many protected machines.

Actiphy announced ImageServer on 26 October 2026 as a central platform for storing and managing ActiveImage Protector backups and coordinating post-backup tasks. Its published feature set includes Inter-File Deduplication and Workflow automation for verification, replication, consolidation and BootCheck. The design moves those post-backup processes to a dedicated server, rather than making each protected system carry the same processing burden.

For an IT team, the useful question is how to sequence those jobs around the working day. For example, verification can run after backup receipt, replication can be scheduled for a quieter window and consolidation can be reserved for a maintenance period. The schedule should reflect the available storage, network capacity and recovery objectives rather than simply choosing the most aggressive setting.

Questions to settle before the next maintenance window

Before calling a backup and disaster recovery software project complete, ask who owns the recovery media, when it was last rebuilt, which ADK and driver versions it contains, and when a full restore was last tested. Confirm that the people responsible for the application know what success looks like after the operating system starts.

Actiphy’s November update gives administrators a concrete compatibility point to review. The wider lesson is more durable: keep the recovery toolchain under change control, test it against representative systems and make the restore procedure familiar before an incident forces the team to learn it under pressure.

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.