jain.com — data centers, connectivity and security, analyzed daily

Category: Security

  • Wand AI Adds Zeroport to Put Agents on Air-Gapped Systems

    Wand AI Adds Zeroport to Put Agents on Air-Gapped Systems

    TL;DR · 30-second read

    The Short Version

    Artificial intelligence programs are starting to touch the systems that actually run a country: power grids, water utilities, defence networks, government records. Those systems are deliberately kept off the internet so nothing outside can reach them.

    Wand AI and Zeroport say they have a way to let automated software workers operate them anyway. The software gets no connection at all. It sends keystrokes down a wire built so that data physically cannot travel back, and receives only a moving picture of the screen, like looking through a window.

    A separate computer watches every frame and can cut the session off mid-task.

    Wand AI said in a September 9 announcement distributed over PR Newswire that it has added Zeroport to its Sovereign AI offering, incorporating Zeroport’s Fantom hardware boundary and its Moativ enforcement layer into Wand’s agent platform. The stated goal is to let government programs point autonomous AI agents at segmented and air-gapped estates, including grid, water, SCADA, defence, banking and registry systems, without creating a network route into them.

    Under the joint reference architecture, Wand’s runtime dispatches an agent session to a dedicated Fantom Core rather than to an endpoint inside the protected network. Only keystroke and mouse input travels inward across a one-way hardware break, and only a display-only pixel stream travels outward. Moativ, an on-device model running on NVIDIA Jetson Thor accelerators inside the same appliance, inspects every input and every frame and can alert, block or physically sever the session. The companies say the architecture is available to sovereign programs and enterprises now, and that adopting Zeroport is elective rather than required.

    Executive Summary

    The announcement addresses a real and specific bottleneck. National AI programs are moving past document summarisation toward operating systems of record and systems of control, and those are precisely the estates that security teams spent a decade making unreachable. Connecting an agent to them the conventional way means provisioning an interface, a credential and a network path, which recreates the exposure the segmentation was designed to eliminate. Zeroport’s argument is that the route itself should be removed rather than narrowed.

    The technical claim has two halves, and they deserve separate treatment. The first is that the access path is physical: a partition built from the chip up that carries no IP packet and terminates no network session, so an agent reaches the protected system the way a cleared human operator does, keystrokes in and pixels out. The second is that the policy governing the agent lives out of band, on hardware the governed session has no address for, which answers a genuine weakness in software guardrails that run on the same computational plane as the model they police.

    What the companies have described is an architecture and a reference design, not a deployment record. No sovereign customer, contract value, pilot result or third-party certification accompanies the announcement, and the performance figures are stated as targets and capacities rather than measured production results. The architectural idea is coherent and the problem is well framed; the evidence that it works at national scale is still forthcoming.

    The Last Mile of Sovereign AI Is an Access Problem, Not a Model Problem

    Sovereign AI has largely been discussed as a question of ownership: whose chips, whose weights, whose data centre, whose law. That framing gets a country to a capable model sitting on domestic compute. It does not get the model anywhere near the substation control interface, the water treatment historian, or the case management system where the work actually is. Air-gapping means a network is physically or logically isolated with no routable connection to the outside, and organisations do it precisely because a path into those estates is a national risk before it is an IT risk.

    Wand’s positioning treats that last mile as the binding constraint on the value of AI labour, and the logic holds. An agent restricted to systems already reachable through ordinary enterprise controls is confined to the least consequential half of a ministry’s estate. The alternatives on offer today all involve a trade the release characterises fairly: virtual private networks, zero-trust network access and privileged access management gateways narrow and log the route but preserve it, so it remains enumerable and exploitable; guardrail software asserts policy on the same plane as the model, where a sufficiently capable model can be argued out of it; and leaving the estate offline removes the route by removing the workload.

    Zeroport cites roughly two-thirds of cyber-attacks as exploiting remote access tooling and 80 percent of breaches as involving stolen or compromised credentials. Neither figure is sourced in the announcement, and both are the kind of round number that circulates widely in vendor material, so they should be read as framing rather than evidence. The underlying point survives the caveat regardless: remote access is the dominant vector in most credible threat models, and an agentic layer multiplies the number of sessions requesting it.

    Physics Governs the Route; Software Still Governs the Judgment

    The strongest part of this architecture is also the most conventional. A one-way hardware break that admits only human-interface signals and emits only pixels is a descendant of the unidirectional gateway and data diode designs that have protected operational technology perimeters for years, combined with the display-only principle behind remote desktop and browser isolation. Applying that lineage to agent sessions is a sensible extension rather than an invention, and it inherits the property that matters: there is no packet to smuggle a payload inside, and nothing for a compromised or drifting agent to pivot into. Revoking an agent removes the path outright rather than closing a session on a path that persists.

    The second claim needs more care. Moativ enforces policy from silicon the governed session cannot address, which genuinely defeats the prompt-injection and goal-drift failure modes where an agent talks its way past a rule that lives in its own context. But Moativ is itself a model making content-level judgments about what is on screen and what was typed. Physics secures the channel; a classifier decides intent. That classifier can produce false negatives, in which a harmful action reads as sanctioned, and false positives, in which legitimate work is severed. On a control system, a wrongly terminated session mid-action is not a neutral outcome.

    The controls around that risk are described more concretely than most vendors manage. Rules are written in plain language and compiled into staged detectors, dry-run against a program’s own session history before they are armed, with autonomy set per group on a five-step dial running from observe through alert, investigate and terminate to self-tune. Dry-running policy against real historical sessions is the right way to calibrate an enforcement model, and the audit trail attaches screen content, keystrokes and rationale to every autonomous action. What is absent is any published figure for detection accuracy or intervention rate.

    Pixels In, Pixels Out: What the Agent Gives Up

    Routing an agent through a screen rather than an application programming interface is a security gain purchased with capability. Agents that drive graphical interfaces are measurably less reliable than agents calling structured interfaces, because they must locate controls visually, tolerate rendering variation, and recover from states no schema describes. Every task must be expressible as keystrokes and mouse movement against a live display, and nothing structured comes back, only pixels. For supervisory control work performed by a human operator today, that is a natural fit. For bulk data extraction, batch reconciliation or anything requiring high-volume structured output, it is a poor one, and it is worth noting that the pixel-only return path is exactly what makes exfiltration hard.

    The economics scale in a way network overlays do not. Capacity grows in Cores and then in appliances, with hundreds of concurrent sessions per appliance and thousands per rack, and humans and agents riding the same rails with no shared tunnel to bottleneck. That converts a licensing question into a hardware procurement question, which is familiar territory for defence and utility buyers and appears in a capital budget rather than an operating one. The dedicated pathways target sub-50-millisecond latency, stated as a design target, which is the threshold that separates a channel usable for live control from one fit only for after-the-fact review. All inspection happens on-premises and no session content leaves the rack, a claim that matters more to sovereign buyers than almost anything else in the architecture.

    An Ecosystem Assembled Layer by Layer

    This is the third such addition Wand has announced in the same pattern, following a storage efficiency layer and a model robustness layer, and alongside existing inference privacy and confidential computing capabilities. The construction is deliberate: a sovereign platform assembled from independently adoptable components, none a prerequisite for another, each addressing a distinct objection a national buyer might raise. It is a credible route to breadth for a company founded in 2023, and it lets Wand answer a procurement checklist without building every layer itself.

    It also leaves the commercial substance of each addition undefined. The announcement describes a joint reference architecture and mutual technical fit, but not whether Zeroport hardware is resold by Wand, jointly supported, revenue-shared, or merely certified as compatible. Buyers evaluating an integration care about which entity holds the support contract when an appliance severs a session on a live grid system. It is also worth recording plainly that Fusion Fund appears as an investor in both companies, which is unremarkable in a specialised market but relevant context for how ecosystem partnerships form.

    For Zeroport, founded in 2024 in Herzliya by security and military-intelligence veterans, the partnership offers distribution into national programs that a two-year-old hardware company would otherwise reach slowly. For Wand, whose offices include Abu Dhabi and whose stated customer base spans banks, asset managers and system integrators, it supplies an answer to the question sovereign buyers ask last and hardest: what happens when the agent has to touch the thing that matters.

    Background

    Sovereign AI describes a country’s effort to run artificial intelligence on domestic compute, under domestic law, with control over the models, data and policies involved. The first wave of national programs concentrated on procuring accelerators and building data centres. The second, now underway, tries to convert that capacity into operational work inside ministries, utilities and defence estates, which raises a problem the first wave never had to solve: the highest-value systems are the ones deliberately made unreachable.

    Wand AI, founded in 2023 and headquartered in Palo Alto with offices in New York and Abu Dhabi, sells an operating system for deploying and governing AI agents alongside humans, with identity, authority, audit and governance built in. It is backed by Shasta Ventures, Fusion Fund, Thiel Capital and Palo Alto Growth Capital, and has been assembling its sovereign offering as a series of independently adoptable layers covering inference privacy, confidential computing, model robustness and storage efficiency. Zeroport, founded in 2024 in Herzliya, Israel, holds multiple patents on its Fantom platform and says it is deployed across critical infrastructure, energy, defence, financial services and government environments, with backing from lool ventures, Clarim Ventures, CyberFuture and Fusion Fund.

    Sources

    Source: WAND AI adds ZEROPORT as an Agent Containment Layer to Enable Sovereign AI on Air-Gapped and Critical National Systems — the September 9, 2026 announcement describing the joint reference architecture, the Fantom hardware boundary, the Moativ on-device enforcement layer, and the two deployment points the companies support.

  • Cisco Buys WideField Security to Harden Splunk’s Identity Layer

    Cisco Buys WideField Security to Harden Splunk’s Identity Layer

    TL;DR · 30-second read

    The Short Version

    Many of the accounts logging into a large company’s systems are not people at all. They are software: automated services, and now artificial intelligence assistants that act on their own.

    Cisco has bought WideField Security, a company that keeps track of all of those accounts, human and machine, and flags the ones behaving strangely.

    Cisco will fold the technology into Splunk, the security monitoring software it already owns. Neither company has said what the deal cost.

    Cisco Systems has acquired WideField Security Inc., an identity-security software company, in a cross-border transaction that included a separate India workstream covering WideField’s Indian subsidiary. Bar & Bench reported on September 6 that JSA Advocates & Solicitors advised Cisco on the Indian legal and regulatory aspects — due diligence on the subsidiary, structuring, review of the US and Indian transaction documents from an Indian law perspective, negotiation, conditions-precedent fulfilment and closing assistance — with a team led by joint managing partner Vivek K. Chandy. Fenwick was Cisco’s lead counsel on the global transaction; Gunderson Dettmer represented WideField. No purchase price has been disclosed.

    WideField’s platform gives organisations visibility into human, non-human and AI-driven identities, and is intended to identify risk, strengthen authentication and support real-time threat detection and response. Its technology is to be incorporated into Cisco’s Splunk platform to enhance agentic security operations centre capabilities by normalising and correlating identity, session and activity telemetry drawn from multiple sources. The deal surfaces days after Cisco filed its annual report for fiscal 2026 with the Securities and Exchange Commission on September 2, covering the year ended July 25, 2026; that filing reports Cisco’s business across four revenue categories — networking, security, collaboration and observability.

    Executive Summary

    The strategic logic is narrow and specific rather than sweeping. Cisco is not buying an identity provider that issues logins; it is buying the layer that watches them. WideField’s stated capability — pulling identity, session and activity records from many systems and reconciling them into a single, comparable picture — is precisely the input a security operations centre needs before it can automate anything. Without normalised identity data, an AI-driven analyst is guessing.

    That points the deal squarely at Splunk, which Cisco acquired in 2024 in the largest transaction in its history. Splunk’s value has always been a function of what you feed it: it ingests machine data and lets analysts search and correlate it. Identity telemetry is one of the harder categories to ingest cleanly, because every directory, cloud provider and application describes an account differently. Buying a company that has already solved that plumbing is a faster path than building it inside a platform Cisco is still integrating.

    The timing matters for a second reason. As enterprises deploy AI agents that hold credentials and act autonomously, the number of identities inside a company grows without a corresponding growth in the number of employees. Each of those agents is an account that can be over-permissioned, hijacked or simply left running. Cisco’s four reporting categories in its fiscal 2026 annual report include security, and this acquisition is an argument about where that category’s growth is meant to come from.

    Identity Has Quietly Become the Control Plane

    For most of the last two decades, enterprise security spending followed the network: firewalls, segmentation, intrusion detection. That model assumed a perimeter. Cloud adoption dissolved it. When applications, data and staff all sit outside the corporate network, the only durable checkpoint left is the identity — the account, token or key presented at the moment of access. That is why identity security has become the fastest-moving line item in many security budgets, and why a networking vendor now needs a position in it.

    WideField’s framing of the problem is the current industry consensus stated plainly: human, non-human and AI-driven identities. Non-human identities are the service accounts, API keys and machine credentials that let one piece of software talk to another; they typically outnumber employee accounts by a wide margin, rotate rarely, and are governed far more loosely. AI-driven identities extend the problem, because an autonomous agent both holds credentials and generates activity that looks like a user’s. Telling a compromised agent from a busy one requires exactly the correlation of identity, session and activity data that WideField describes.

    The competitive read is that this pushes Cisco further into territory occupied by Microsoft, Palo Alto Networks, CrowdStrike and the identity-governance specialists. It does not, on the disclosed facts, make Cisco an identity provider competing with the directories enterprises already run. The nearer analogy is a monitoring and posture layer that sits above those directories — a position that is complementary to them right up until it is not.

    Splunk Is the Reason the Deal Makes Sense

    Read the acquisition as a Splunk roadmap item and it becomes legible. Cisco’s stated intent is to enhance Splunk’s agentic security operations centre capabilities — an operations centre where AI agents triage alerts, gather context and propose or take remediation steps, rather than a room of analysts doing it by hand. The bottleneck in that design is not the model. It is data quality. An agent cannot reason about whether a login is anomalous if the same person appears as three different identifiers across a cloud provider, a single sign-on tool and an internal application.

    Normalisation and correlation is unglamorous work, and it is also the work that determines whether an automated operations centre produces useful conclusions or expensive noise. Buying a team that has built it for identity data is a defensible use of capital, and it is a different kind of purchase from the volume-driven logic that governs data platform economics, where ingesting more telemetry raises both value and cost. What Cisco has not said is whether identity telemetry processed through WideField’s technology will be priced as part of existing Splunk entitlements or as a separate module — a commercially material question for anyone already managing a Splunk bill.

    There is also an integration risk worth naming without overstating it. Cisco is still absorbing Splunk. Layering a further acquisition into a platform mid-integration can accelerate a roadmap or fragment it, and the record of large networking vendors folding security startups into existing consoles is mixed. The measure of success will be whether the capability ships as a native part of the platform on a stated timeline, not whether it appears in a slide as an adjacency.

    A Tuck-In, Judged by What Was Not Announced

    No purchase price, no share count and no closing date have been made public, and Cisco has not published deal terms alongside the legal-advisory account. For a company of Cisco’s size that pattern usually indicates a transaction below the threshold at which separate disclosure is required — a tuck-in acquired for its technology and team rather than its revenue. WideField being represented by Gunderson Dettmer, a firm whose practice is built around venture-backed companies, is consistent with a private, venture-stage target rather than a mature software business, though the companies have not characterised it either way.

    That framing should temper expectations in both directions. A tuck-in will not move Cisco’s security revenue line in the near term, and readers should be sceptical of any suggestion that it repositions the company outright. Equally, tuck-ins are how platform gaps get closed, and the gap here is a real one. The honest assessment is that the strategic rationale is substantiated by the stated integration path, while the financial significance is simply unknown because it has not been disclosed.

    Why the India Leg Was a Separate Workstream

    The most concrete detail in the public account is structural: WideField had an Indian subsidiary substantial enough to require its own diligence, its own document review under Indian law, and conditions-precedent fulfilment before closing. The supporting workstreams named — employment, direct tax and indirect tax — indicate a subsidiary with employees and tax exposure worth examining, not a dormant shell. For an acquirer, that is where deal value quietly leaks: mispriced payroll liabilities, transfer-pricing history between the Indian entity and the US parent, and equity treatment for staff whose options convert on closing.

    This is a familiar shape for enterprise security startups, many of which run engineering and around-the-clock detection operations from India while selling into North America. It also means the acquisition carries a people question as much as a technology one. Retaining the engineers who built the normalisation logic is usually the difference between a capability that ships and a codebase that is quietly rewritten by the acquirer two years later.

    For buyers in India specifically, the practical implication is modest but real: capability originating in an Indian development centre is now attached to a global platform vendor’s support, compliance and procurement machinery. Neither company has said what happens to the subsidiary’s operations, headcount or reporting lines after closing.

    Background

    Cisco Systems is a global networking and technology company that builds AI-enabled networking, security and digital infrastructure products. Its annual report for fiscal 2026, filed with the SEC on September 2, 2026 and covering the year ended July 25, 2026, reports revenue across four categories: networking, security, collaboration and observability. The security and observability lines were substantially reshaped by Cisco’s 2024 acquisition of Splunk, a data platform used to ingest and analyse machine-generated logs, and the largest acquisition in Cisco’s history. Splunk gave Cisco a foothold in security analytics to sit alongside its long-standing network hardware franchise.

    Identity security emerged as a distinct market as enterprises moved workloads to the cloud and the traditional network perimeter stopped being a meaningful boundary. The category now spans identity providers that issue and verify credentials, governance tools that decide who should have access to what, and monitoring layers that watch how identities actually behave. The rapid adoption of AI agents — software that holds credentials and acts autonomously — has expanded the number of identities inside a typical organisation without a corresponding increase in staff, and has made behavioural monitoring of non-human accounts an active area of both product development and acquisition.

    Sources

    Source: JSA advises on India leg of Cisco’s acquisition of WideField Security — Bar & Bench, September 6, 2026, on the Indian, US and global legal workstreams behind Cisco’s purchase of WideField Security and the technology’s planned integration into Splunk.

    Primary sources: Cisco Systems, Annual Report on Form 10-K for the fiscal year ended July 25, 2026, filed with the SEC on September 2, 2026.

  • NeuralTrust’s London Office and the AI Agent Security Gap

    NeuralTrust’s London Office and the AI Agent Security Gap

    TL;DR · 30-second read

    The Short Version

    Companies are starting to let artificial intelligence software act on its own — sending emails, moving money, pulling up customer records — without a person approving each step. If one of those systems is tricked or badly set up, it can leak data or take a wrong action in seconds.

    NeuralTrust, a Barcelona company that sells software to watch and restrain those systems, has opened an office in London to serve British banks, airlines and large firms. It says it raised twenty million dollars in June to expand.

    NeuralTrust, a Barcelona-headquartered platform for securing AI agents, announced on 7 September 2026 that it has opened a dedicated London office at 167 Great Portland Street. The company says the site will serve as its hub for UK customers, partners and hiring, supporting a client base spanning financial services, technology and other large enterprises, and that it plans to recruit across sales, customer success and engineering in the coming months.

    The expansion follows a $20 million seed round the company raised in June 2026, which it describes as the largest cybersecurity seed financing by an EU company to date. NeuralTrust now lists offices in Barcelona, London and New York, and says its customers include global banks, airlines, energy companies and government agencies.

    Executive Summary

    The announcement is, on its face, a routine go-to-market step: a well-funded European security startup putting staff on the ground in one of the world’s largest financial centres. What makes it worth reading closely is the problem it is chasing. Enterprises are moving from AI systems that answer questions to AI agents — software that takes actions on a company’s behalf, calling internal tools, querying databases and triggering transactions, often with no human approving each step.

    That shift breaks a core assumption behind most existing security controls. Traditional tooling is built to police users, devices and network traffic against rules that are known in advance. An agent’s behaviour is generated at runtime from natural-language input, which means an attacker can attempt to redirect it with text — the class of attack known as prompt injection — rather than with code. NeuralTrust sells three products aimed at that gap: TrustGate, a gateway that sits between applications, agents, tools and models to enforce policy and control access; TrustGuard, runtime monitoring that blocks unsafe agent behaviour as it happens; and TrustTest, a red-teaming tool that probes AI systems for weaknesses before attackers find them.

    The strategic read is that NeuralTrust is betting UK buyers — particularly regulated banks and airlines, where an unauthorised automated action carries immediate legal and operational consequence — will pay for agent governance sooner than buyers elsewhere. The company’s UK managing director, Cameron Brown, frames the office in exactly those terms. Whether that bet pays off depends on questions the announcement does not settle.

    Why Agent Security Is Not Just Application Security

    The security industry has spent two decades learning to defend systems whose behaviour is deterministic: given the same input, the same code path runs. Agents break that. They are given goals in plain language, decide which tools to call, and chain those calls together in sequences nobody wrote down in advance. A firewall sees an outbound API request; it does not see that the request was the third step in a plan an agent improvised after reading a malicious instruction hidden in a customer support ticket.

    This is why the gateway pattern NeuralTrust is selling with TrustGate has become the consensus architecture across this young market. Putting a control point between the agent and everything it can touch — models, internal tools, data stores — restores the thing traditional security depends on and agents destroy: a chokepoint where policy can be enforced and activity can be logged. It is the same instinct that produced API gateways and, before them, web proxies. The harder part is TrustGuard’s job: deciding, in real time and without adding latency a user would notice, whether a given agent action is legitimate. That is a detection problem with no settled ground truth, and vendors across the category are still establishing what good looks like.

    Red teaming, NeuralTrust’s third product line, is the least glamorous and arguably the most immediately saleable piece. Security teams asked to sign off on an agent deployment need evidence, and “we attacked it ourselves and here is what broke” is evidence a CISO can take to a risk committee. It also maps cleanly onto assurance processes enterprises already run for conventional software.

    A Crowded Layer of the Stack

    NeuralTrust is not entering an empty field. The control point between an application and a model is contested by several groups at once: cloud providers shipping native guardrail and filtering services with their own model platforms; established API management and identity vendors extending existing gateways to cover model traffic; a cohort of AI-security startups funded through 2025 and 2026; and open-source projects that give engineering teams a serviceable proxy for free. Each has a structural advantage. The hyperscalers own the deployment surface and can bundle. The incumbents own the buyer relationship and the procurement slot. Open source owns the price.

    The independent vendor’s counter-argument is portability. An enterprise running agents across multiple model providers, several clouds and a mix of internal and third-party tools cannot govern that estate from any single provider’s native console, and will not want its policy layer to be an artefact of a vendor it may want to leave. NeuralTrust’s positioning — a platform spanning “every platform and endpoint” — is aimed squarely at that argument, and the customer profile it describes, global banks and airlines with heterogeneous estates and hard regulatory obligations, is where it is most persuasive.

    The commercial risk is timing rather than technology. If the market consolidates before independent vendors reach durable scale, the natural outcome is acquisition by a platform security company rather than category leadership. A $20 million seed is substantial for the stage, and larger than typical for European cybersecurity, but it is not the war chest of a firm intending to outspend cloud providers on distribution. Spreading a round of that size across Barcelona, London and New York simultaneously is an aggressive allocation, and it implies the company expects revenue to arrive quickly enough to fund the next phase.

    Why London, and What an Office Actually Proves

    London is a rational first international bet for this product. The concentration of banks, insurers and airlines in the UK gives a vendor a dense cluster of buyers who share the same risk profile, and financial services firms operate under supervisory expectations around operational resilience and third-party technology risk that push governance spending forward rather than leaving it to discretion. Sales cycles in the sector are slow and reference-driven, which rewards local presence: a named managing director and a staffed office change how a procurement committee reads a vendor’s commitment.

    It is worth being precise about what an office opening does and does not demonstrate. It is a genuine cost commitment and a credible signal of intent, and paired with disclosed funding it is more than a press exercise. It is not evidence of revenue, contracted capacity or customer count in the market being entered. NeuralTrust states that it partners with major UK industry bodies and serves financial services, technology and enterprise clients in the region, but attaches no names, numbers or contract values to those statements. Both things can be true at once: the expansion is real, and its commercial scale is unquantified.

    Reading the Supporting Claims

    NeuralTrust cites a Gartner prediction that by 2027, 40% of enterprises will demote or decommission autonomous AI agents because governance gaps surface only after something has gone wrong in production. That figure is a forecast, not a measurement of anything that has happened, and forecasts of AI adoption have proven volatile in both directions. It is nonetheless directionally consistent with what enterprise buyers report: pilots that reach production and then stall when nobody can answer basic questions about what the agent did, why, and who is accountable. Used as a description of a pattern, it is useful. Used as a market-size proxy, it should carry a wide error bar.

    The company also describes itself as a category leader recognised by Gartner, KuppingerCole and MarketsandMarkets, and its June round as the largest cybersecurity seed financing by an EU company to date. These are checkable claims of different weight. Analyst recognition depends heavily on which specific report, which category and which evaluation criteria — details the announcement does not specify. The funding superlative is narrowly scoped by geography, sector and stage, which is how such records are usually constructed; it says something real about European cybersecurity funding levels and less about NeuralTrust’s standing against globally funded competitors.

    None of this undercuts the underlying thesis, which is the strongest part of the announcement. The gap between how quickly enterprises can deploy agents and how quickly security teams can build monitoring, policy and incident response for them is real, widely reported by practitioners, and unlikely to close on its own. A vendor addressing it with a gateway, runtime controls and adversarial testing is addressing the right problem. The open question is execution, not diagnosis.

    Background

    Enterprise adoption of generative AI moved through a recognisable sequence: internal chat assistants, then retrieval systems answering questions over company documents, and now agents that take actions. The final step is where the security model changes, because an agent that can call an internal payments interface or update a customer record introduces operational risk in a way a chatbot does not. Security teams have found their existing tooling largely blind to it — identity systems were designed around human users, network controls around known traffic patterns, and neither explains why an autonomous system chose a particular sequence of steps.

    That gap produced a wave of specialist vendors from 2024 onward, converging on a common architecture of a policy-enforcing gateway, runtime behavioural monitoring and adversarial testing. NeuralTrust, founded in Barcelona, is among the more heavily funded European entrants, having raised a $20 million seed in June 2026 and previously launched what it describes as a runtime security mesh extensible across every AI agent. Its expansion into London places it in a market where financial-services regulation around operational resilience and third-party technology risk gives security buyers an unusually early mandate to govern AI systems in production.

    Sources

    Source: NeuralTrust Opens New London Office as UK Enterprises Race to Secure Their AI Agents — NeuralTrust’s 7 September 2026 announcement of a dedicated London office, its UK hiring plans and its TrustGate, TrustGuard and TrustTest product lines.

  • See’s Candies Data Breach Draws Class Action Investigation

    See’s Candies Data Breach Draws Class Action Investigation

    TL;DR · 30-second read

    The Short Version

    See’s Candies, the boxed-chocolate maker sold in shops across the country, told California regulators on August 13, 2026 that its computer systems were broken into. It has written to the people affected.

    A law firm that brings group lawsuits for consumers says it is now looking into whether those people have a claim. Published accounts describe a ransomware attack, in which criminals lock up or steal a company’s files and demand money.

    See’s has not said publicly how many people were affected, when the break-in happened, or exactly what was taken.

    Edelson Lechtzin LLP, a national class action law firm with offices in Pennsylvania and California, announced on September 5, 2026 that it is investigating data privacy claims arising from a cybersecurity incident at See’s Candies, Inc. The firm said See’s reported the incident to the California Attorney General’s Office on August 13, 2026 and notified affected individuals directly, and that reports attribute the incident to a ransomware attack.

    According to the firm’s announcement, the official notice did not detail the categories of information involved, the date of the breach, or the total number of individuals affected. Reports cited in the announcement indicate the exposed data may have included names, Social Security numbers, addresses, payment information, phone numbers, account records such as service plans and payment histories, and internal business records belonging to both customers and employees. The firm is offering free case evaluations and has not stated that a complaint has been filed.

    Executive Summary

    The immediate news is narrow: a plaintiffs’ firm has opened an intake investigation twenty-three days after See’s Candies filed a breach notice with California regulators. No lawsuit has been announced, no class has been certified, and See’s has not publicly confirmed the scope of the incident. On its own, an investigation announcement is a client-recruitment step, not a finding of fault.

    The wider significance is structural. California’s breach-notification regime turns a private security failure into a public, searchable record within days, and that record is monitored continuously by firms that specialize in consumer data litigation. For any company holding consumer and employee records at scale, the interval between incident disclosure and legal exposure is now measured in weeks, not quarters — regardless of how the intrusion happened or how well the response was run.

    That compresses the timeline for decisions that used to belong to the security team alone. Data retention, network segmentation, vendor contracts and notification readiness now determine litigation cost and regulatory posture, which makes them governance questions with security implementations rather than security questions with governance footnotes.

    From Regulator Filing to Legal Investigation in Three Weeks

    California’s breach-notification statute requires a business to submit a sample copy of its consumer notice to the Attorney General when more than 500 California residents are notified. Those submissions are published in a public, searchable database. It is an accountability mechanism — and it is also, in practice, a lead list. Firms that litigate consumer privacy claims monitor it as a matter of routine, which is how a filing dated August 13 produces an investigation announcement dated September 5.

    It is worth being precise about what that announcement is. An investigation is the intake phase: a firm publicizes an incident, collects contacts from people who received notification letters, and evaluates whether a viable class claim exists. The release carries an attorney-advertising notice, which is standard and required in some jurisdictions. None of that says anything about whether See’s Candies handled its data well or badly. It reflects the mechanics of the system, not an assessment of the company.

    The practical lesson for operators is that the notification decision is now also a litigation decision. The letter that satisfies a statutory duty simultaneously creates a public record, a plaintiff pool and a timeline that opposing counsel will scrutinize. Companies that draft breach notices under time pressure, without counsel who understand how the resulting document will be read a year later, hand away ground they cannot recover.

    What Is Substantiated — and What Is Not

    The announcement is candid about the limits of the underlying record: it states that the official notice did not detail the specific categories of information involved, did not disclose the date of the breach, and did not disclose the total number of individuals affected. Everything in the enumerated data list — Social Security numbers, payment information, account records — is presented as what reports indicate the breach “may have” involved. That is a materially different claim from a company confirming what was taken, and readers should hold it as the conditional statement it is.

    One item in that list deserves a flag. “Service plans and payment histories” is billing vocabulary at home in telecommunications, utilities or subscription services; it is not an obvious fit for a confectionery retailer, and See’s has not confirmed holding such records. It reads like language carried over from a general breach-notification template. Distinguishing template language from confirmed fact is not a small point when the categories drive the legal theory.

    The distinctions matter operationally too, because different data types imply different compromised systems. Social Security numbers at a retailer almost always live in human-resources and payroll platforms, not in store systems — so their involvement would point at corporate infrastructure rather than the point of sale. Payment card data points instead at commerce and transaction systems and pulls in contractual obligations under the payment card industry’s security standard, a private framework enforced by banks and card networks rather than by regulators. Until See’s specifies the categories, the blast radius of this incident cannot be assessed from the outside.

    The Economics That Make Consumer Breaches Expensive

    Breach cost is rarely dominated by the intrusion itself. It accumulates across forensic investigation, notification mailing, credit-monitoring offers, defense fees, regulatory engagement and settlement — and most of those line items scale with the number of people notified, which is precisely the figure See’s has not disclosed.

    California adds a specific multiplier. The state’s consumer privacy law gives residents a private right of action when unencrypted, unredacted personal information — a name combined with an identifier such as a Social Security number — is exposed through a business’s failure to maintain reasonable security. Statutory damages run from $100 to $750 per consumer per incident, or actual damages if greater. Claims for statutory damages carry a written-notice and cure requirement, so the path is not automatic, but the arithmetic explains why class size, not intrusion sophistication, tends to determine a case’s value.

    There is also a second, often underestimated class. Employees whose payroll records are exposed have a different relationship to the company than customers do, and their claims — negligence, breach of implied contract, state wage and privacy statutes — are typically stronger, because employees have no practical choice about handing over a Social Security number. A retailer that thinks of a breach as a customer problem may be looking at the smaller half of its exposure.

    Why This Is a Governance Question, Not an IT Ticket

    Ransomware economics changed several years ago. Encryption-only attacks were survivable with good backups; the prevailing model now combines encryption with data theft, so restoring systems resolves the outage but not the exposure. “We recovered without paying” is an operational win that leaves the legal and notification obligations entirely intact. Any board briefing that treats recovery time as the headline metric is measuring the wrong thing.

    For consumer brands, the valuable data is frequently not where the brand lives. It sits in payroll processors, loyalty platforms, e-commerce back ends, marketing clouds and customer-service tools — much of it operated by third parties under contracts that determine who investigates, who notifies, who pays and how fast anyone finds out. Vendor due diligence, breach-notification clauses and indemnity terms are therefore security controls in commercial clothing, and they are negotiated by procurement and legal, not by the security operations team.

    The controls that actually reduce exposure are unglamorous and mostly organizational: retention schedules that delete records the business no longer needs, because data you do not hold cannot be stolen; segmentation that keeps corporate and human-resources systems off the same flat network as store and commerce infrastructure; immutable or offline backups; and rehearsed notification workflows with counsel in the room before an incident, not after. Each requires budget authority and cross-functional mandate. That is what makes third-party retail data handling a governance problem — the cost lands in legal, brand and regulatory columns, while the fix has to be funded and enforced somewhere else entirely.

    Background

    See’s Candies was founded in Los Angeles in 1921 and has been owned by Berkshire Hathaway since 1972, selling boxed chocolates through company retail shops, mail order and online channels. The release describes it simply as a retail company serving customers nationwide. Like most consumer retailers of its size, it holds two distinct pools of sensitive data: customer records tied to purchases and shipping, and employee records tied to payroll and benefits — typically in separate systems, often operated in part by outside providers.

    The legal environment around those records has hardened considerably. Every US state now has a breach-notification statute, California publishes submitted notices in a public database, and its consumer privacy law added a private right of action with statutory damages for breaches involving unencrypted personal information. That combination — mandatory public disclosure plus a pre-set damages figure — supports a specialized plaintiffs’ bar that monitors regulator filings and moves within days of them. Investigation announcements of the kind issued here are a routine, high-volume feature of that ecosystem, and their appearance says more about the disclosure regime than about any individual company’s security practices.

    Sources

    Source: See’s Candies Data Breach: Edelson Lechtzin LLP Launches Investigation Into Exposure of Personal Information — a September 5, 2026 announcement from class action firm Edelson Lechtzin LLP stating that See’s Candies, Inc. reported a data security incident to the California Attorney General’s Office on August 13, 2026 and that the firm is evaluating potential claims on behalf of affected individuals. The release may be considered attorney advertising in some jurisdictions.

  • Tusker Buys Fortress SRM, Adding 50 Staff and a 24/7 SOC

    Tusker Buys Fortress SRM, Adding 50 Staff and a 24/7 SOC

    TL;DR · 30-second read

    The Short Version

    A Chicago technology company called Tusker has bought Fortress SRM, a Cleveland firm of about 50 people whose job is keeping businesses from being hacked.

    Fortress runs an operation staffed around the clock, every day of the year, where analysts watch customers’ computer networks for intruders and step in when one gets through. Most mid-sized companies cannot afford to staff that themselves, so they rent it from firms like this one.

    It is Tusker’s fifth purchase since 2017, and the company says more are planned.

    Tusker, a Chicago-headquartered technology solutions provider, announced on September 2, 2026 that it has acquired Fortress SRM, a Cleveland cybersecurity firm founded in 2018. According to Tusker’s announcement, the deal adds roughly 50 cybersecurity professionals, a 24/7 Security Operations Center, and a sixth regional hub covering the Ohio Valley. Financial terms were not disclosed.

    Fortress SRM serves customers across Ohio, northern Michigan and Wisconsin, with services spanning security consulting and advisory work, virtual CISO leadership, managed security, incident response and digital forensics. The transaction is Tusker’s fifth acquisition since 2017 and its first since the company consolidated its portfolio businesses under a single brand earlier this year. Tusker says it now has more than 400 employees and hubs in Chicago, Boston, Green Bay, Duluth, Eau Claire and Cleveland, and that further acquisitions are planned.

    Executive Summary

    The headline asset in this deal is not the customer list — it is the round-the-clock watch floor. A Security Operations Center, or SOC, is a team that monitors customer networks continuously for signs of intrusion and coordinates the response when something is found. Building one is a fixed-cost exercise: you need enough trained analysts to staff three shifts, weekends and holidays before you can credibly answer a single alert at 3 a.m. That cost only makes sense when it is spread across many customers, which is precisely why regional security firms that have already paid it are attractive to acquirers who have not.

    Tusker’s position is a common one in the mid-market channel. It has scale in the things that are hard to differentiate — hardware, deployment, help desk, lifecycle management — and comparatively thin capability in the thing customers are currently most anxious about. Buying a 50-person security practice with an operating SOC, a virtual CISO bench and a digital forensics capability is a faster route to that capability than hiring into a labor market where experienced detection-and-response analysts are scarce and expensive.

    For the wider market, the deal is a small but legible data point in an ongoing consolidation: independent regional managed security providers are being absorbed into broader IT services platforms, because mid-market buyers increasingly want detection and response as a subscription rather than a staffing problem. What Tusker’s announcement does not establish is how large or how profitable that practice is, or on what terms it changed hands.

    The Economics of Watching a Network at 3 a.m.

    Continuous security monitoring has an unforgiving cost structure. Coverage that is genuinely 24 hours a day, seven days a week, requires multiple analyst shifts plus slack for holidays, illness and turnover — before any tooling, threat intelligence feeds or escalation playbooks are paid for. A mid-sized manufacturer or hospital system that tried to build this in-house would be hiring a team it can keep busy only intermittently. The managed model works because that same team’s attention is sold in slices to dozens of organizations at once, and because attacks against one customer generate detection knowledge that protects the rest.

    That arithmetic is what makes an existing SOC a genuine asset rather than a line item. Fortress SRM’s described capability set — consulting and advisory, virtual CISO leadership, managed security, incident response and digital forensics, and the SOC itself — maps onto a full customer lifecycle: assess, advise, monitor, and respond when monitoring finds something. A firm that can only do the assessment half sells projects; a firm that can do the monitoring half sells contracts. Recurring revenue is the reason security practices command attention from acquirers, though Tusker has not said what portion of the acquired business is recurring.

    The Cross-Sell Case Cuts Both Ways

    Jess Walpole, president of Fortress SRM, framed the deal around customer convenience: security clients who also want help with desktops, servers, networks and modernization now get it from one partner. That is a real benefit, and it reflects a genuine mid-market preference for fewer vendors. But the more consequential flow probably runs the other direction. Tusker reports more than 400 employees and clients across the country; selling managed detection and response into an installed base that already trusts the provider with its infrastructure is a cheaper path to growth than winning security deals cold.

    Consolidation of this kind does raise a question buyers should ask openly, and it is a question about structure rather than about either company’s intentions. When the same organization advises on security strategy, supplies the hardware and manages the environment, the advisory function loses some of its natural independence. Virtual CISO services — essentially a fractional security executive rented by organizations too small to employ one — are valuable precisely because they are supposed to represent the customer’s interests. Providers that combine advisory with product and managed services can manage that tension well, through separate reporting lines, transparent product economics or a willingness to recommend third-party tooling, but customers should ask how it is being handled rather than assume.

    A Great Lakes Roll-Up Reaches the Ohio Valley

    Look at Tusker’s hub map — Chicago, Boston, Green Bay, Duluth, Eau Claire and now Cleveland — and the strategy reads clearly. With one East Coast exception, this is a Great Lakes and Upper Midwest platform assembled around mid-sized regional markets rather than the coastal metros where national systems integrators concentrate. Those markets have plenty of manufacturers, healthcare providers, municipalities and school districts that face the same regulatory and insurance pressure on cybersecurity as larger firms, with none of the in-house staff. Cleveland extends that footprint into the Ohio Valley and, per the announcement, into a service territory already covering Ohio, northern Michigan and Wisconsin.

    The risk in any roll-up is that the acquired capability degrades in transit. Tusker’s stated asset here is people: roughly 50 specialists whose value is entirely portable if they choose to leave. Integration also has to reconcile monitoring platforms, ticketing systems, escalation procedures and service-level commitments across organizations that built them independently — work that is invisible to customers when it goes right and very visible when it does not. Tusker has done this four times before and completed a brand unification earlier this year, which is evidence of a repeatable process rather than proof of a smooth outcome. The company also says more acquisitions are planned, which means integration capacity, not deal flow, is likely to be the binding constraint.

    Background

    Tusker began as a Chicago IT hardware distributor and has since assembled a broader technology services platform through acquisition, adding capabilities in advisory, professional services, managed services and lifecycle support. Formerly operating as ACP CreativIT, the company brought five regional firms under the single Tusker brand earlier in 2026 and has been named to the Channel Futures MSP 501 list of top managed service providers for 2026, its second appearance. The Fortress SRM deal is its fifth acquisition since 2017.

    The market context is a mid-market squeeze. Organizations of a few hundred to a few thousand employees now face the same ransomware exposure, cyber insurance questionnaires and regulatory expectations as large enterprises, without the budget for a standing security team. That gap created a generation of regional managed security providers — Fortress SRM among them, founded in 2018 — and those firms have in turn become acquisition targets for full-stack IT providers seeking recurring security revenue and capabilities that are slow and costly to build from scratch.

    Source: Tusker Acquires Fortress SRM to Expand Cybersecurity Services — Tusker’s September 2, 2026 announcement of its acquisition of the Cleveland cybersecurity firm, including headcount, service capabilities and regional hub details.

  • FedRAMP High Arrives for Defense Supply-Chain Compliance

    FedRAMP High Arrives for Defense Supply-Chain Compliance

    On September 1, 2026, Baltimore-based FutureFeed and CyberIllumination announced that both platforms have achieved FedRAMP High Authorized (Class D) status. FutureFeed is a compliance platform for NIST SP 800-171 and CMMC used across the Defense Industrial Base (DIB); CyberIllumination, operated by Continuous Compliance LLC and currently in beta, gives prime contractors and subcontractors a shared view of supply-chain cybersecurity posture.

    Per the release, Class D aligns with the historical FedRAMP High baseline, the standard applied to federal systems where a loss of confidentiality, integrity, or availability could have severe or catastrophic consequences. The authorizations followed independent third-party assessments of each platform’s security controls. Cloud service provider Project Hosts supported both efforts. FutureFeed reports more than 1,400 clients and 350-plus partners across the DIB.

    Executive Summary

    The announcement is narrow in substance and broad in signal. Two platforms that hold defense contractors’ most sensitive compliance artifacts — system security plans, risk assessments, audit evidence, supplier posture records — now carry the federal government’s highest authorization tier for unclassified cloud workloads. FedRAMP, the Federal Risk and Authorization Management Program, standardizes how cloud services are security-assessed for government use; its High baseline sits above the Low and Moderate tiers and applies to data whose compromise would be severe or catastrophic.

    Why it matters: the data these platforms aggregate is arguably more sensitive than any single customer’s own environment. A compliance tool serving 1,400 DIB organizations holds a consolidated map of where the defense supply chain is weakest — which controls are unimplemented, which remediation plans are open, and for how long. That concentration is exactly the profile FedRAMP High was written for, and it is the strongest argument in the release.

    What the release does not do is quantify its central marketing claim. It states that “few compliance platforms reach FedRAMP High” without a figure, names no federal agency customer, and does not disclose the authorization pathway, effective date, or cost. The security assessment is independently validated; the competitive framing around it is not.

    The Compliance Tool Becomes the Concentration Risk

    There is a structural irony in defense compliance software. To help a contractor prove it protects Controlled Unclassified Information (CUI), the platform must first collect a detailed inventory of that contractor’s security gaps. Multiply that across a customer base the size of FutureFeed’s stated 1,400 clients and 350-plus partners, and the vendor accumulates something no individual contractor holds: a cross-sectional view of where the defense industrial base is unprotected, documented in audit-ready detail.

    That is the honest case for FedRAMP High here, and it does not depend on marketing language. A system security plan describes architecture, boundaries, and control implementation. A plan of action and milestones (POA&M) is, functionally, a dated list of known weaknesses and when they will be fixed. Aggregated, these are high-value targets regardless of whether the platform itself ever touches a federal network. Holding the aggregator to the same bar as the systems it describes is a defensible design principle.

    For buyers, the practical read is that vendor due diligence in this category should now include the platform’s own authorization posture, not just its feature list. For competing vendors, the announcement raises the reference point in procurement conversations even where no regulation formally requires it.

    What FedRAMP High Buys — and What It Does Not

    Context matters for interpreting the tier. Under DFARS 252.204-7012, cloud service providers handling covered defense information for contractors are generally expected to meet requirements equivalent to the FedRAMP Moderate baseline. High sits above that. So this is a vendor electing to exceed the common contractual floor for its market segment — a legitimate differentiator, but one worth describing precisely rather than as a pass/fail gate that competitors have failed.

    It is also worth separating what an authorization certifies from what it implies. FedRAMP attests that a defined system boundary was assessed against a control baseline by an independent assessor at a point in time, and that continuous monitoring obligations apply thereafter. It does not certify product quality, data-handling ethics, uptime, or that every customer workload runs inside the authorized boundary. The release states that CyberIllumination runs in AWS GovCloud on U.S. soil; it does not state the hosting arrangement for FutureFeed, nor whether existing customers are automatically served from the authorized environment.

    The economics deserve a mention because they shape the market. FedRAMP authorization is a capital-intensive exercise in assessment, documentation, and ongoing monitoring — historically a barrier that favors larger vendors or those buying a compliant platform-as-a-service underneath them. That is precisely the gap Project Hosts describes filling with its FasTrack program, which the release says provides a path to authorization without securing an agency sponsor. Sponsorless pathways lower the barrier meaningfully; they also make “few platforms reach FedRAMP High” a claim with a shorter shelf life than the announcement implies.

    The Flow-Down Problem and the Case for Authorize-Once

    CyberIllumination’s stated premise is the more interesting product thesis in the release: compliance obligations flow down every tier of the defense supply chain, but visibility does not. A prime contractor may hold a contract requiring assurance about subcontractors it has limited insight into, while a small supplier answers substantially the same questionnaire for every prime it serves. The proposed fix — a supplier authorizes one compliance record and shares it with multiple primes, with audit logs of who accessed what — replaces N questionnaires with one record.

    This is a two-sided network, and two-sided networks are hard to start. Suppliers only benefit if enough primes accept the shared record; primes only adopt if enough suppliers are on it. The audit-log design is a sensible trust mechanism for the supplier side, since the objection to shared compliance data is usually not transparency but loss of control over who sees weaknesses. Whether primes will accept a third-party record in place of their own assurance process is an adoption question the release does not address.

    One detail is worth flagging plainly and without prejudice: the release describes CyberIllumination as currently in beta. Authorizing a pre-general-availability product at the High baseline is unusual sequencing, though not improper — building to the standard before scale is arguably better practice than retrofitting. It does mean the authorization currently applies to a platform with an undisclosed production customer base, and readers should not infer commercial traction from a security designation.

    Background

    Defense contractors have faced formal cybersecurity obligations for roughly a decade, beginning with DFARS clauses requiring implementation of NIST SP 800-171 to protect Controlled Unclassified Information. Self-attestation proved uneven, and the Department of Defense responded with the Cybersecurity Maturity Model Certification program, which introduces third-party verification and is being phased into contracts. The practical effect has been a surge in demand for software that helps contractors document, evidence, and sustain compliance rather than reconstruct it before each assessment.

    FutureFeed, based in Baltimore, built its business in that market, reporting more than 1,400 clients and 350-plus partners including managed service providers and consultants. CyberIllumination extends the same logic upward into the supply chain, addressing a persistent structural gap: obligations flow down through every contracting tier, but reliable visibility into whether lower tiers have met them does not flow back up. FedRAMP, meanwhile, has spent recent years modernizing its authorization process to reduce cost and time-to-authorization — context that makes new High-tier entrants in specialized software categories more likely, not less.

    Source: FutureFeed and CyberIllumination Achieve FedRAMP High Authorized (Class D) Status, the Federal Government’s Highest Cloud Security Bar — PR Newswire release issued from Baltimore on September 1, 2026, announcing FedRAMP High authorizations for two Defense Industrial Base compliance platforms.

  • AI Agents as Digital Actors: Governance Lags Adoption

    AI Agents as Digital Actors: Governance Lags Adoption

    Info-Tech Research Group, an IT research and advisory firm, published new research on 28 August 2026 from Arlington, Virginia, arguing that enterprise AI agents should be governed as a distinct class of digital actor rather than as ordinary IT assets or as earlier generative AI models. The blueprint, Govern Enterprise AI Agents While Preserving Innovation, sets out a three-phase framework for managing agent identity, access, autonomy limits and ongoing oversight.

    The firm names five governance gaps it says organizations hit as agent use spreads: shadow AI, capability mismatch, runtime drift, unmanaged access and ambiguous ownership. The blueprint ships with a governance playbook, a charter example, an executive dashboard template and a glossary. Info-Tech says it serves more than 30,000 IT, HR and marketing leaders and has operated for nearly 30 years.

    Executive Summary

    The core claim is narrow and worth taking seriously: an AI agent does not merely produce output, it takes action. It can call systems, trigger workflows and make decisions on its own, at machine speed. That breaks the assumption underneath most enterprise AI governance to date, which is that a human reviews and approves a model’s output before anything consequential happens. Info-Tech’s position is that one-time approval gates cannot govern something that keeps operating after the gate.

    Altaz Valani, principal advisory director at Info-Tech, frames the problem in the release as a mismatch on both sides: agents cannot be governed like IT assets because they act across systems, and they cannot be governed like employees because, in the firm’s words, they move quicker and lack emotions, conscience and consequences. The practical translation is that the controls that work on people — training, incentives, accountability, the fear of being fired — have no purchase here. What is left is identity, credentials, permissions, monitoring and a defined kill switch.

    That is not a new discipline. It is the same control discipline that regulated supply chains already run under. On the same day, Nelson Miller Group announced it had earned Cybersecurity Maturity Model Certification (CMMC) Level 2, the US Department of Defense standard that obliges defense manufacturers to demonstrate control over access to sensitive information. The difference is that defense suppliers are made to prove those controls by contract, while most enterprises are deploying agents years ahead of anything comparable.

    Approval Gates Do Not Govern Things That Keep Moving

    Most enterprise AI governance was designed for a request-and-response world. A team proposes a use case, a committee reviews it, a model is approved, and a human checks the output before it becomes a decision. That control model has a hidden dependency: the risk sits still long enough to be reviewed. An agent breaks the dependency because the approval happens once and the behaviour continues indefinitely, across systems, with credentials attached.

    Info-Tech’s five named gaps are really five ways that assumption fails. Shadow AI means agents created outside sanctioned tools that IT does not know exist — the same problem as unsanctioned SaaS, except the unsanctioned thing holds credentials and acts. Capability mismatch means an agent’s autonomy and access outrun the validation and monitoring applied to it. Runtime drift means an agent quietly expands its scope as tools, prompts and permissions change, so the thing running in month six is not the thing that was approved in month one. Unmanaged access means service accounts and permissions let an agent do more than anyone intended. Ambiguous ownership means that when something goes wrong, no one is clearly accountable.

    None of these are exotic. They are the standard failure modes of any privileged non-human identity, which is why the useful reading of this research is deflationary rather than alarming: agentic AI is largely an identity and access management problem wearing new clothes. The genuinely new part is speed and volume. As Valani notes in the release, many people will have multiple agents working for them — which means identity populations that were once measured in employees start being measured in some multiple of employees.

    The CMMC Parallel: Regulated Sectors Already Do This, Under Contract

    The comparison worth drawing is with the defense industrial base. CMMC is the US Department of Defense’s framework for verifying that contractors and subcontractors protect sensitive government information; Level 2 aligns with the NIST SP 800-171 control set for controlled unclassified information, covering access control, identification and authentication, audit and accountability, configuration management and incident response. Nelson Miller Group’s 28 August 2026 announcement that it earned Level 2 certification is, in commercial terms, a supply chain credential: it is how a manufacturer stays eligible for programs that handle protected data.

    Strip away the acronym and the CMMC control families read like a specification for governing agents: know every identity, prove who owns it, restrict what it can reach, log what it did, detect when it drifts, and be able to respond. The defense supplier does this because a contracting officer requires it and an assessment verifies it. The enterprise deploying a fleet of agents has no equivalent forcing function — no customer withholding a purchase order, no assessor arriving to check the evidence.

    That asymmetry is the real story. Control discipline in enterprise technology almost never arrives because it is a good idea; it arrives because a contract, a regulator or an insurer demands proof. Agentic AI is currently in the window between capability and requirement. Firms in regulated supply chains have an unusual advantage here: the muscle memory of proving controls to a third party transfers directly to governing non-human identities. Firms without that history are building the practice from a standing start, and doing it while the agents are already running.

    What the Release Substantiates, and What It Does Not

    This is analyst research promoting a paid deliverable, and it should be read as such — evenly, without either deference or dismissal. What is substantiated is a structured method. The three phases are specific and sequenced: Phase 1 establishes governance authority, decision rights and a small set of enforceable guardrails; Phase 2 maps the agent lifecycle, discovers agents wherever they are created, classifies them by risk and defines runtime monitoring and intervention actions by risk tier; Phase 3 assigns accountability across business owners, technical owners, AI governance and enterprise risk, then defines metrics, executive dashboard reporting and a phased rollout. The named artifacts — playbook, charter example, executive dashboard, glossary — are the ordinary output of this kind of advisory engagement and are reasonable to expect.

    What is not substantiated is the scale of the problem the framework addresses. The release describes a widening gap between adoption and governance but offers no survey data, no incidence rates for shadow agents, no measured cost of a runtime-drift failure and no baseline for how many organizations currently classify agents by risk at all. It refers to case studies without naming an organization or an outcome. The assertion that agents “lack conscience and cannot be morally incentivized” is a framing device rather than a finding; it is intuitively correct and empirically untested as stated here.

    That is not a criticism of the firm — vendor and analyst releases are marketing documents by design, and this one is unusually specific about method for the genre. It does mean a buyer should treat the framework as a hypothesis to be tested against their own environment rather than as evidence that their environment is on fire. The prudent question for a CIO is not whether the five gaps sound plausible, but which of them they can actually measure in their own estate this quarter.

    Who Gains: Identity Vendors, Platform Owners and Whoever Owns the Log

    If agent governance becomes an identity problem, the commercial gravity moves toward whoever already holds the identity layer. Identity and access management providers, privileged access management vendors and cloud platforms that issue and rotate machine credentials are positioned to extend existing products rather than sell new categories. Security operations vendors benefit from the runtime monitoring requirement, since drift detection is a telemetry problem before it is a policy problem. Governance, risk and compliance platforms gain a new object type to track.

    The harder position belongs to business units that have deployed agents quickly using departmental budgets and low-code tooling. Info-Tech’s Phase 2 — find agents wherever they are created — is the phase that generates conflict, because discovery inevitably surfaces work that was never registered with IT. Organizations that treat that discovery as an audit failure will drive the remaining agents further underground; the ones that treat it as an inventory exercise will get better data.

    For infrastructure operators specifically, there is a second-order consequence worth noting. Agents that act autonomously across systems generate authentication events, API calls and audit records continuously rather than in bursts tied to human working hours. Logging, retention and monitoring costs scale with that behaviour. Governance frameworks tend to be discussed as policy; the bill arrives as storage, egress and detection capacity.

    Background

    Info-Tech Research Group is an IT research and advisory firm that publishes structured methodologies — it calls them blueprints — covering IT strategy, security and governance, alongside affiliates McLean & Company for HR research and SoftwareReviews for software buying data. Its business model is subscription advisory, so its research releases both inform the market and market the firm; that dual purpose is standard for the analyst sector and is worth holding in mind when reading any single publication.

    The wider context is a two-year shift from generative AI, where models produce content a human then uses, to agentic AI, where software is granted credentials and permitted to act. That shift moves AI from a content-quality question into an access-control question, territory enterprise security teams have worked in for decades under frameworks such as NIST SP 800-171 and, for defense suppliers, the Department of Defense’s CMMC program. The unresolved issue is timing: regulated supply chains prove their controls because contracts require it, while most enterprises are deploying agents without an equivalent obligation.

    Source: AI Agents Must Be Governed as Persistent Digital Actors, Advises Info-Tech Research Group — the firm’s 28 August 2026 announcement of its Govern Enterprise AI Agents While Preserving Innovation blueprint, with background from Nelson Miller Group’s same-day CMMC Level 2 certification release.

  • MDR Buyer’s Remorse: What CISOs Must Fix Before Signing

    MDR Buyer’s Remorse: What CISOs Must Fix Before Signing

    Info-Tech Research Group, a global IT research and advisory firm, published a blueprint titled Streamline Security Detection & Response Outsourcing on August 27, 2026, from Arlington, Virginia. The firm argues that rising threat volume, expanding attack surfaces and thin security operations capacity are pushing more organizations toward managed detection and response (MDR) — an outsourced service where a third party watches an organization’s systems around the clock and reacts to suspected attacks — but that inconsistent vendor terminology makes providers hard to compare.

    The blueprint sets out a four-phase procurement methodology: Prepare, Set Outcomes, Procure, and Implement & Govern. Senior research analyst Seva Ioussoufovitch is quoted urging leaders not to “rush into a contract you’ll regret.” The full blueprint is available to Info-Tech clients and to media through the firm’s Media Insiders program.

    Executive Summary

    The announcement is advisory content rather than a product launch, but the problem it names is real and expensive. MDR has become a default answer for organizations that cannot staff a 24/7 security operations centre. Info-Tech’s position is that the market’s naming conventions — MDR, MSSP, SOCaaS, XDR-as-a-service and a long tail of branded packages — obscure genuine capability differences, so buyers end up comparing marketing categories instead of deliverables.

    Why it matters: detection and response is one of the few security functions where the buyer hands over not just tooling but decision-making during an incident. A contract that specifies how many alerts a provider triages, without specifying what the provider is authorized to do about them, who owns the resulting telemetry, and how the relationship unwinds, buys visibility the customer cannot act on. Info-Tech’s framing — capabilities and outcomes over acronyms — points in the right direction.

    The release also makes a secondary argument worth noting: MDR procurement is a natural moment to rationalize overlapping security tools, because modern providers often bring capabilities a buyer already licenses. That reframes an MDR deal from an added line item into a potential consolidation event, which changes the business case considerably.

    The Acronym Problem Is Really a Comparability Problem

    Info-Tech’s central observation — that providers use overlapping terms and branded descriptions for similar capabilities — sounds like a semantics complaint. It is actually a market-structure issue. When two offerings cannot be placed on the same axis, price competition weakens, because a buyer cannot credibly say a rival will do the same work for less. Differentiated naming is not necessarily deceptive; vendors genuinely build different things. But the practical effect is that the burden of constructing a comparison framework falls entirely on the buyer.

    That burden lands on exactly the teams least able to carry it. The release identifies limited security team bandwidth as one of its four named obstacles, alongside inconsistent terminology, growing vendor portfolios, and rushed decisions. The circularity is stark: organizations turn to MDR because they lack security operations capacity, then need meaningful security operations capacity to evaluate MDR properly. Structured requirements templates — the kind Info-Tech is selling — exist precisely to lower that evaluation cost. Whether a generic template is specific enough for a given environment is a fair question, and one the release does not address.

    Alert Volume Is the Wrong Unit of Account

    Info-Tech’s phase two calls for measurable KPIs and service level requirements, without prescribing which ones. That restraint is defensible in a general methodology, but it leaves the hardest question open. The metrics MDR contracts most commonly carry — alerts triaged, mean time to detect, mean time to acknowledge — measure the provider’s throughput, not the customer’s risk reduction. A provider can hit every one of them while an intrusion progresses, because acknowledging an alert is not containing an incident.

    The commercially decisive terms sit elsewhere: whether the provider may isolate a host, disable an account or block traffic without waiting for customer approval; how fast that authority applies at 3 a.m. on a holiday; and what happens when the provider acts and is wrong. Response authority is what separates managed detection from managed detection and response, and it is the clause most often softened during negotiation because it carries liability for both sides. Buyers who treat it as boilerplate discover the gap during their first serious incident. Info-Tech’s release does not name these specific terms; the emphasis on defining how responsibilities are divided between organization and provider in phase one is nonetheless the right place to force the conversation.

    Consolidation Cuts Both Ways

    The blueprint’s argument that MDR procurement can surface duplicate tooling is the most immediately monetizable idea in the release. If a provider’s platform already covers endpoint detection, log aggregation and threat intelligence, a buyer paying separately for all three has a genuine savings case — and a stronger negotiating position, because the deal is now worth more to the vendor. For infrastructure operators running their own colocation, network and cloud estates, this is often where the real economics of an MDR deal live.

    The counterweight is concentration. Folding detection tooling into a provider’s stack means the provider owns the pipeline that generates the evidence of its own performance. That raises questions the release does not take up: whether the customer retains a copy of raw telemetry in its own storage, in what format, for how long, and at what egress cost on the way out. A buyer who consolidates onto provider-owned tooling and later wants to switch may find that the practical cost of leaving is not the migration project but the loss of detection history — the baseline that makes anomaly detection work. Consolidation savings are real; they should be scored net of that exit risk, not gross.

    Governance Is the Phase Nobody Staffs

    Phase four asks organizations to actively govern provider performance rather than treat service reviews as passive status updates. This is the least glamorous part of the framework and probably the most predictive of whether a deal succeeds. An MDR relationship degrades quietly: detection rules go stale as the environment changes, integrations silently break after a cloud migration, escalation contacts leave the company. None of that shows up in a monthly alert-count report.

    The problem is that governance requires a named internal owner with time and authority — the same scarce resource whose absence justified outsourcing. Organizations that buy MDR as a headcount substitute and assign oversight as a fraction of someone’s week tend to get the relationship they resourced. The honest version of the business case treats MDR as a capacity multiplier that still requires a retained internal function, not as a full replacement. Info-Tech’s four phases imply that conclusion without stating it, and buyers would be well served to make it explicit in their own board-level justification.

    Background

    Managed detection and response emerged over the past decade as a response to a structural shortage: continuous threat monitoring requires staffing across three shifts, specialist tooling and constant tuning, which is out of reach for most organizations outside the largest enterprises. The category grew out of earlier managed security service provider (MSSP) models, which largely forwarded alerts to the customer, by adding investigation and, in principle, active response. Adjacent labels — SOC-as-a-service, extended detection and response, co-managed SIEM — overlap heavily in practice, which is the comparability problem Info-Tech’s blueprint addresses.

    Info-Tech Research Group is an IT research and advisory firm headquartered with a US presence in Arlington, Virginia, publishing prescriptive methodologies it calls blueprints alongside advisory services. Its business model is subscription research, so its published announcements function both as analysis and as marketing for the underlying deliverable. This particular release was distributed via PR Newswire’s CNW service on August 27, 2026, and follows other recent Info-Tech procurement guidance, including work on agentic AI contracting.

    Source: CISOs Risk MDR Buyer’s Remorse Without Clear Procurement Requirements, Says Info-Tech Research Group — Info-Tech Research Group’s August 27, 2026 announcement of its four-phase blueprint for procuring managed detection and response services.

  • SealingTech Wins $750M USCYBERCOM Award for Joint Cyber Hunt Kit Full-Rate Production

    SealingTech Wins $750M USCYBERCOM Award for Joint Cyber Hunt Kit Full-Rate Production

    Sealing Technologies (SealingTech), a subsidiary of Parsons Corporation (NYSE: PSN), announced on August 25, 2026 that it has received a five-year, sole-source Other Transaction Agreement from U.S. Cyber Command to begin full-rate production of the Joint Cyber Hunt Kit (JCHK), with a ceiling value of up to $750 million.

    The JCHK is a mobile, self-contained defensive cyber platform — effectively a deployable security operations center — built for the military’s Joint Cyber Protection Teams. It replaces a patchwork of service-specific kits with a single standardized system, and SealingTech is the sole prime contractor.

    Executive Summary

    The award moves the Joint Cyber Hunt Kit from prototyping into full-rate production, the acquisition milestone at which the Department of War commits to buying a system at scale rather than in test quantities. SealingTech, which had previously received a contract modification to continue the JCHK prototype, now holds the program outright as sole provider and prime contractor for up to five years.

    For Parsons, the win reinforces a strategic bet: the company says its cyber and electronic warfare business already represents more than 20% of total revenue, and SealingTech’s deployable edge hardware sits at the center of that portfolio. A $750 million ceiling on a single defensive-cyber hardware program is a substantial figure in a market segment historically dominated by services contracts rather than productized systems.

    The broader signal is infrastructural. Cyber defense at the tactical edge is being standardized, productized, and procured at industrial scale — the same trajectory that servers, storage, and networking followed in the commercial data-center world, now applied to fly-away kits that must operate on contested and disconnected networks.

    From Fragmented Kits to a Standardized Platform

    Until now, each military service largely fielded its own cyber-hunt equipment — different hardware, different software baselines, different logistics tails. According to the release, the JCHK deliberately replaces those fragmented, service-specific kits with a single joint system, improving interoperability and accelerating mission readiness for Cyber Protection Teams, the units tasked with finding and evicting adversaries from U.S. and allied networks.

    Standardization is the real story here. A common platform means common training, common spares, common software updates, and comparable telemetry across teams — the same logic that drives enterprises toward standardized server fleets. The release also notes the kit was co-developed with key allies, which matters for “hunt forward” missions, in which U.S. teams deploy to partner nations’ networks at their invitation to hunt for threats. A shared hardware baseline lowers the friction of operating on someone else’s infrastructure.

    The Deployable SOC as an Edge-Computing Product

    Functionally, the JCHK is a security operations center (SOC) compressed into transportable cases: expanded storage, high-throughput processing, and integrated analytics that let operators capture and interrogate network traffic on site, without reach-back to a distant cloud. The release emphasizes operation in “connected, disconnected, and contested environments” — meaning the kit must work when links home are degraded, jammed, or deliberately severed.

    That places this award squarely in the edge-computing trend familiar to commercial infrastructure buyers. The technical problems — dense compute in constrained power and thermal envelopes, ruggedization, rapid setup, local data gravity — mirror what telecoms and industrial operators face at their own edges. SealingTech built the JCHK on years of portable edge-compute and Cyber Fly-Away Kit engineering, and the defense market is effectively validating that deployable, modular infrastructure is now a product category, not a custom integration exercise.

    Ceiling Values, OTAs, and What $750M Actually Means

    The contract’s structure deserves scrutiny. This is an Other Transaction Agreement (OTA) — a flexible acquisition vehicle that sits outside traditional federal procurement regulations and is designed to move faster, often with non-traditional contractors. The $750 million figure is a ceiling over five years, not guaranteed revenue: actual orders will depend on annual budgets, fielding schedules, and USCYBERCOM’s demand. Investors should read it as the maximum size of the opportunity, not a booked backlog.

    The sole-source structure cuts both ways. For the government, a single prime simplifies configuration control and accountability on a standardized platform. For the market, it concentrates a significant defensive-cyber hardware franchise in one vendor, which typically strengthens pricing power and follow-on positioning — sustainment, refresh cycles, and software — while raising the familiar questions any single-supplier arrangement invites about long-term price competition and surge capacity. The release does not describe how the sole-source decision was justified, which is standard for announcements of this kind but worth noting.

    Winners, Losers, and the Parsons Portfolio Effect

    The clearest winner is Parsons, which acquired veteran-founded SealingTech (established 2012) and now sees that bet mature into a franchise program. With cyber and electronic warfare already exceeding 20% of company revenue by Parsons’ own description, JCHK full-rate production deepens a differentiated hardware-plus-software position that most services-oriented defense primes lack. The competitive implication is that vendors of the legacy service-specific kits the JCHK replaces lose their footholds as those systems retire.

    For the wider industry, the award signals that deployable cyber-hunt infrastructure is being militarized at genuine scale — procured like a weapons system, with full-rate production milestones and multi-year ceilings. That is likely to pull more edge-hardware makers, ruggedized-compute specialists, and analytics vendors toward the defense market, and it gives allied governments a reference model for their own deployable cyber programs.

    Background

    SealingTech was founded by veterans in 2012 and built its business around portable edge compute and Cyber Fly-Away Kits — transportable systems that let cyber operators bring analysis capability to networks in the field. Parsons Corporation, a defense and infrastructure technology firm traded on the NYSE, acquired the company in 2023 and folded it into a cyber and electronic warfare portfolio that Parsons says now exceeds 20% of total company revenue.

    The JCHK program itself emerged from U.S. Cyber Command’s push to unify the defensive cyber equipment used by its Cyber Protection Teams, which had historically relied on kits built separately by each military service. SealingTech carried the program through prototyping — including a publicly announced prototype-continuation contract modification — before this full-rate production award.

    Source: SealingTech, a Parsons Corporation company, receives $750 Million Joint Cyber Hunt Kit (JCHK) Full-Rate Production Award from USCYBERCOM — PR Newswire press release announcing the five-year sole-source production agreement, August 25, 2026.

  • NAPCO Fiscal 2026 Results: Record Revenue, $103M Recurring Run Rate

    NAPCO Fiscal 2026 Results: Record Revenue, $103M Recurring Run Rate

    NAPCO Security Technologies (NASDAQ: NSSC), the Amityville, New York-based maker of intrusion and fire alarm equipment, door-locking hardware and school safety solutions, reported record results for its fiscal fourth quarter and full year ended June 30, 2026. Full-year net revenue rose 11.4% to $202.3 million, and fourth-quarter revenue climbed 10.0% to a quarterly record $55.8 million.

    Recurring service revenue — the subscription-like fees tied to NAPCO’s wireless alarm communicators — grew 13.0% for the year to $97.5 million at gross margins above 90%, and now carries a prospective annual run rate of roughly $103 million. The board raised the quarterly dividend 13.3% to $0.17 per share.

    Executive Summary

    The announcement is a clean read on demand for electronic security at a moment when physical and cyber security budgets increasingly converge: both of NAPCO’s revenue streams grew. Equipment sales rebounded 10.0% for the year to $104.8 million on strong door-locking demand and a 36% fourth-quarter jump in intrusion product sales, driven primarily by StarLink fire communicators. Recurring service revenue (RSR) reached approximately 45% of total revenue in the fourth quarter — a meaningful shift for a company historically viewed as a hardware manufacturer.

    The headline profit numbers need unpacking, however. Fourth-quarter net income surged 52.7% to a record $17.8 million, but gross margin of 61.3% included roughly 600 basis points of benefit from tariff refunds — about $0.09 of the quarter’s $0.50 in diluted earnings per share. Full-year GAAP net income actually slipped 0.9% to $43.0 million because of a $16 million litigation settlement charge taken in the third quarter. Excluding that charge, non-GAAP net income rose 32.0% to $57.3 million.

    For investors and security-industry watchers, the takeaway is that NAPCO’s recurring-revenue flywheel keeps compounding at double-digit rates while the hardware business that feeds it has returned to growth — with two one-time items, one favorable and one unfavorable, muddying the year-over-year optics in opposite directions.

    Recurring Revenue Is Now the Engine

    NAPCO’s most important number is not the record top line — it is the $97.5 million of recurring service revenue earned at gross margins above 90%. In plain terms, every StarLink cellular communicator NAPCO sells to an alarm installer keeps paying the company monthly fees for the wireless connection that carries alarm signals, long after the hardware sale closes. That model converts one-time equipment purchases into an annuity, and the July 2026 run rate of approximately $103 million suggests the annuity is still building.

    At roughly 45% of fourth-quarter revenue, RSR is approaching parity with equipment sales, and it explains why company-wide gross margin has expanded from 55.6% to 59.2% year over year even before tariff refunds. This is the same economic logic that has re-rated software and connectivity businesses across the technology sector: predictable, high-margin, contracted revenue is worth more per dollar than transactional hardware revenue. The 13.0% RSR growth rate indicates that alarm dealers keep activating new communicators faster than old accounts churn off — though the release provides no subscriber or churn figures to verify the mix of the two.

    Headline Margins Come With Asterisks

    The fourth quarter’s 61.3% gross margin is the most impressive figure in the release, and also the one that deserves the most scrutiny. NAPCO discloses that tariff refunds contributed approximately 600 basis points of that margin — meaning the underlying quarterly gross margin was closer to the mid-50s. The refunds also added about $0.09 to the quarter’s $0.50 in diluted earnings per share. These are real dollars, but refunds of previously paid tariffs are by nature backward-looking; they say little about the cost structure going forward, and the release does not address ongoing tariff exposure.

    The full year carries the opposite distortion. A $16 million litigation settlement charge, taken in the third quarter and still sitting as an accrued (unpaid) liability on the June 30 balance sheet, turned what would have been strong GAAP net income growth into a 0.9% decline. The release does not describe what the litigation concerned. NAPCO’s non-GAAP presentation, which adds the charge back, shows 32.0% net income growth — a fair representation of operating momentum, but readers should note that non-GAAP measures are company-defined and, as NAPCO itself cautions, not standardized across companies. The honest picture lies between the two: core profitability improved substantially, flattered modestly by refunds and dented once by a settlement.

    The Hardware Rebound Feeds the Subscription Base

    Equipment revenue growing 10.0% to $104.8 million matters for more than its own sake, because in NAPCO’s model hardware is the on-ramp to recurring revenue. Management called out strong demand for door-locking products and a 36% fourth-quarter increase in intrusion product sales driven primarily by StarLink fire communicators — devices that replace legacy phone-line connections for fire alarm systems with cellular links. Every such device installed typically begins generating service fees, so today’s equipment growth is a leading indicator of tomorrow’s RSR.

    The demand backdrop is favorable in ways the release references but does not quantify: commercial fire-code compliance drives non-discretionary communicator upgrades, and NAPCO positions itself as a provider of school safety solutions, a segment with sustained public funding attention. What the release does not offer is any segment-level detail on how much of the growth came from fire, locking, access control or school safety specifically, or any forward guidance on whether the fourth quarter’s 36% intrusion growth is sustainable.

    A Fortress Balance Sheet and a Bigger Dividend

    Cash and equivalents grew to $126.9 million from $83.1 million a year earlier, alongside $10.6 million in marketable securities, and full-year free cash flow rose 15.2% to $59.2 million — a 29.3% free-cash-flow margin that would be enviable for a software company, let alone a manufacturer. That cash generation comfortably funds the raised dividend of $0.17 per quarter, payable October 2, 2026 to holders of record September 11, 2026.

    The 13.3% dividend increase is a signal of management confidence, but it also raises a capital-allocation question the release leaves open: with well over $135 million in cash and securities and modest capital-expenditure needs, NAPCO has firepower for acquisitions, buybacks or accelerated product investment, and the release articulates no plan for it beyond the dividend. In a consolidating security industry, that optionality cuts both ways — dry powder is valuable, but idle cash earns questions over time.

    Background

    NAPCO Security Technologies is one of the longer-standing independent manufacturers in the electronic security industry, headquartered in Amityville, New York, and operating through four divisions: NAPCO plus wholly owned subsidiaries Alarm Lock, Continental Instruments and Marks USA. Its products span intrusion and fire alarms, wireless alarm communicators, access control and architectural door locking, sold through professional security installers into commercial, industrial, institutional, residential and government settings — including a growing focus on school safety solutions.

    The company’s strategic story over recent years has been the deliberate layering of recurring service revenue on top of its hardware business: wireless communicators that replace phone-line alarm connections generate monthly service fees at gross margins above 90%. That shift places NAPCO in the multi-billion-dollar electronic security market at the intersection of physical hardware and subscription connectivity — the same hardware-plus-recurring model reshaping much of the broader security and infrastructure sector.

    Source: NAPCO Security Technologies, Inc. Reports Fiscal Q4 and Full Year 2026 Results — company press release issued via PR Newswire on August 24, 2026, announcing financial results for the quarter and fiscal year ended June 30, 2026.