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

Tag: access control

  • Noma’s 8-Agent Laptop Coverage Shows AI Security Moving From Apps to Actions

    Noma’s 8-Agent Laptop Coverage Shows AI Security Moving From Apps to Actions

    TL;DR · 30-second read

    The Short Version

    Many programmers and office workers now use artificial intelligence assistants that act on their own. They edit code, open files and pass data to other systems, using the same logins and permissions as the person who installed them.

    Noma, a New York security company, launched software that finds these assistants on company laptops, decides what each one may do, and blocks risky actions as they happen.

    The bigger shift: companies are moving from asking “is this tool approved?” to “is this specific action allowed?” An assistant might be allowed to read a database but not delete it.

    On September 28, 2026, Noma Security announced in a release distributed via PR Newswire that it has extended its AI agent security platform to employee endpoints, meaning the laptops and desktops where staff work. The new capabilities find AI agents, MCP servers and skills running on managed machines. They place those assets under access control and apply runtime protection through Noma’s AI Detection and Response (AI-DR) layer. MCP servers are connectors built on the Model Context Protocol that let agents reach databases, repositories and applications. Skills are packaged instructions that agents load for specific tasks.

    Noma says coverage spans agents including Claude Code, Claude Cowork, Cursor, Codex, Windsurf, Kiro, Antigravity and OpenClaw. It works through tools companies already run: endpoint detection and response (EDR) software, mobile device management (MDM) software, agent hooks, AI and MCP gateways, and SDKs. Noma also says it plans to bring its Agent Boundaries feature to the endpoint, without giving a date.

    Executive Summary

    Noma’s announcement targets a specific problem. AI agents installed by individual employees inherit that employee’s credentials and can chain actions together across a session, such as reading files, calling tools and changing systems, without a human approving each step. Noma’s pitch is that the laptop, not the cloud, is where these agents are multiplying fastest and where security teams have the least visibility.

    The product has three layers. Discovery reads local evidence to build a live inventory. Access Control assigns every agent, MCP server and skill a status of approved, needs review or blocked, and ties it to the responsible employee’s identity. AI-DR watches behavior at runtime and can alert, steer, block, mask data or hand an action to a human.

    The release’s most important idea is stated in one line: “Approving an agent is not enough.” That marks a change in how enterprises govern AI tools. Deciding once whether an app is allowed is giving way to deciding, continuously, which individual actions an allowed agent may take.

    Why the Laptop Became the Blind Spot

    Enterprise AI security so far has concentrated on systems the company builds or buys centrally: homegrown applications on cloud AI platforms, and SaaS agent builders run through IT. Coding and productivity agents took a different route. Developers and business users often install them directly, the same way unsanctioned SaaS apps once spread before IT caught up. By the time security notices, the agent already holds the user’s access to source code, production infrastructure, documents and internal data.

    MCP servers and skills widen that reach. Each connector adds new tools an agent can call, and each skill adds new instructions it can follow. Noma’s argument is that this exposure “already exists before any attacker is ever involved.” The risk is not only malicious code. It is also a legitimate tool doing something broader than intended, with credentials nobody scoped for it.

    From Approving Apps to Governing Actions

    The headline shift is visible in how Noma structures control. Its release names at least eight agents from several vendors: Claude Code, Claude Cowork, Cursor, Codex, Windsurf, Kiro, Antigravity and OpenClaw. An approve-or-block decision per application does not scale across that many tools, each with its own connectors and update cycle. Noma instead governs at five levels: the agent, the MCP server, the skill, the individual tool and the specific action. Its example is precise. Read access can stay broadly available while create, update and delete operations are limited to a smaller group.

    The runtime layer extends the same logic across time. Noma says its Contextual Policies correlate prompts, tool calls, tool responses, data access and identity across a full session. The goal is to catch threats that “develop across a sequence of otherwise permitted actions.” This is the core of the argument. Every step can be individually allowed while the sequence is harmful, for example an approved database tool turning a routine task into mass deletion. To support the claim that sanctioned tools can misbehave, Noma cites a security researcher’s finding that xAI’s Grok Build coding assistant uploaded tracked repositories and full Git history to the provider’s cloud after being told not to open files.

    The people affected are concrete. Security teams gain a registry and policy engine keyed to user and group identity from the company’s identity provider. Developers and business users may see new review states, write restrictions, or human-approval steps inserted mid-session. Agent vendors face customers who expect hooks and telemetry detailed enough to support action-level enforcement.

    Riding on EDR and MDM: The Deployment Bet

    Noma does not install a new heavyweight agent on every laptop. It connects through EDR or MDM tools already deployed and reads configuration files, skills directories, connector history and running processes. Enforcement runs through agent hooks, gateways and SDKs. That lowers adoption friction, a real advantage in enterprises wary of adding more endpoint software.

    The trade-off is dependency. Discovery depends on what existing EDR and MDM tools can see. Inline blocking depends on how much control each agent’s hooks expose. The release frames inventory around managed devices, which leaves personal and unmanaged machines outside the described scope. The approach also places Noma alongside two sets of possible competitors: EDR vendors that already sit on the endpoint, and agent vendors that could build governance controls into their own products.

    What the Release Substantiates, and What It Does Not

    The functional description is specific. It names detectors (prompt injection, sensitive data leakage, tool poisoning, scope violations, behavioral drift), enforcement modes, and data sources. Security buyers can test claims at that level of detail.

    The commercial claims are less specific. “Market-leading,” “widely adopted by Fortune 500 customers,” “hundreds of AI-DR policies” and work with “dozens of Fortune 500 security teams” are not quantified or tied to named customers. The release gives no detection accuracy, false-positive rates or performance impact for inline blocking. Agent Boundaries is described as planned, with no timeline. None of this undercuts the product’s premise, but buyers will need proof-of-concept results rather than the announcement to judge effectiveness.

    Background

    Noma Security is a New York-based company that sells an AI and agent security platform for large enterprises. Before this announcement, the company described coverage across homegrown AI applications built on AWS Bedrock, Azure AI Foundry and Databricks, SaaS agent platforms such as Microsoft Copilot Studio and Salesforce AgentForce, and prebuilt agents like Claude Code, Cursor and GitHub Copilot on developer machines. Its backers include Evolution Equity Partners, Ballistic Ventures, Glilot Capital, Cyber Club London, Databricks Ventures and SVCI. The company says Gartner has recognized it as a leader in AI trust, risk and security management (AI TRiSM).

    The wider market context is the rapid spread of autonomous AI agents. These tools do more than suggest text: they take actions such as editing code, querying databases and operating SaaS apps. The Model Context Protocol has become a common way to connect agents to outside tools. That has made the question of what an agent is permitted to do a security and governance problem, not only a productivity one.

    Sources

    Source: Noma Extends Agent Security and Governance to the Employee Endpoint, Noma Security’s September 28, 2026 announcement of discovery, access control and runtime protection for AI agents on employee machines.

  • 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.