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

Tag: government IT

  • Kasm and Everfox Partner on Cross-Domain Workspace Access for Defense

    Kasm and Everfox Partner on Cross-Domain Workspace Access for Defense

    Kasm Technologies and Everfox announced a strategic technology partnership on August 20, 2026, combining Kasm Workspaces — a container-based platform that streams desktops and applications to users in disposable, policy-controlled sessions — with Everfox’s Trusted Thin Client, a purpose-built zero-trust endpoint for accessing networks at different security classification levels. The joint solution, available now, targets government, defense, and intelligence agencies that today issue multiple devices or run parallel virtual-desktop stacks to keep classified networks separated.

    Executive Summary

    The announcement pairs two specialized vendors around one problem: giving cleared personnel access to applications and desktops across multiple classification levels from a single device. In classified environments, networks at different levels (for example, unclassified versus secret) are deliberately kept apart, which historically means separate computers, separate virtual desktop infrastructure (VDI) stacks, and the cost and desk clutter that come with them. Everfox contributes the cross-domain access layer — its Trusted Thin Client bridges those separated networks on validated hardware — while Kasm contributes the workspace layer, streaming containerized desktops and applications into ephemeral sessions that are centrally managed and fully wiped when they end, so no data persists on the endpoint.

    The companies emphasize that adoption does not require a rip-and-replace: Kasm Workspaces integrates with existing hypervisors, cloud environments, and identity providers, letting agencies layer modern workspace delivery onto current infrastructure and migrate at their own pace. The announcement is a technology partnership with immediate availability, but it names no customers, contract values, or accreditation milestones — it establishes a joint offering, not demonstrated adoption.

    The Economics of Endpoint Sprawl

    The clearest business case in this release is cost consolidation. In many classified settings, working across networks means a physical computer per classification level on each desk, or a separate VDI environment per network — each with its own licensing, patching, and support burden. The release frames the joint solution as a direct replacement for these “multi-endpoint, multi-VDI-stack approaches,” collapsing them into one validated device and one workspace platform. If the technology performs as described, the savings show up not just in hardware counts but in operational overhead: fewer stacks to patch, fewer images to maintain, and central policy enforcement instead of per-device configuration.

    That said, the release quantifies none of this. There are no cost-comparison figures, seat counts, or reference deployments, so the economic argument rests on the general premise that fewer endpoints and fewer parallel stacks cost less — plausible, but unproven in this document.

    Containers as a Challenger to Legacy VDI

    The more interesting technical bet is architectural. Traditional VDI runs each user a full virtual machine, which is resource-heavy and rigid. Kasm’s model instead streams desktops and applications from containers — lightweight, fast-starting software packages — into browser-delivered sessions that exist only for the duration of use and are destroyed at termination. In security terms, ephemerality is a feature: a session that is fully wiped leaves no residual data on the endpoint, which matters enormously when the endpoint touches multiple classification levels.

    Defense environments, however, are conservative adopters for good reason. Cross-domain solutions face some of the most demanding assurance expectations in government IT, and the release does not address how the combined stack is accredited or evaluated for cross-domain use — only that Everfox’s hardware is “validated” and its solutions are “purpose-built” for high-assurance environments. Whether container isolation plus a trusted thin client satisfies each agency’s specific approval processes is the question that will actually determine adoption, and it is not answered here.

    The No-Rip-and-Replace Pitch

    Both companies clearly understand their buyer. Agencies running classified missions cannot take infrastructure offline for a wholesale migration, so the release leans hard on incrementalism: Kasm integrates with existing hypervisors, clouds, and identity providers, and agencies can “transition at a pace that does not put critical missions at risk.” Kasm’s chief product officer, Daniel Ben-Chitrit, also stresses the absence of vendor lock-in and the platform’s on-premise deployment model — both sensitive points for government buyers wary of dependency on any single supplier or on commercial cloud availability.

    Strategically, the partnership is complementary rather than overlapping: Everfox gets a modern desktop-delivery story to pair with its cross-domain plumbing, and Kasm gets a credentialed route into classified networks it could not plausibly enter alone. The risk cuts the other way too — a technology partnership without disclosed go-to-market commitments, joint contract vehicles, or named integrator support can remain a datasheet exercise. The release states the joint solution is available now, which is a stronger claim than a roadmap announcement, but availability and adoption are different things.

    Background

    Kasm Technologies builds an open-core platform for streaming containerized desktops, browsers, and applications to users through the web browser — a container-based alternative to virtual desktop infrastructure (VDI), the long-standing enterprise approach of hosting each user’s desktop as a virtual machine in a data center. Everfox operates in the cross-domain solutions market, supplying trusted access and secure data transfer between networks at different classification levels for government, defense, and intelligence customers, where high-assurance requirements have historically favored purpose-built hardware and specialized vendors.

    The partnership lands amid a broader government push to modernize classified-environment IT, where the default pattern of one endpoint per network has become an acknowledged cost and usability burden. It also extends a run of alliance announcements from Kasm, which recently shipped Kubernetes support in Workspaces 1.19 and a stealth-networking integration with Dispersive, suggesting a deliberate strategy of pairing its workspace layer with specialized security partners rather than building those capabilities alone.

    Source: Kasm Technologies and Everfox Announce Strategic Partnership to Deliver Secure Cross Domain Workspace Access for Government and Defense — PR Newswire press release, August 20, 2026, announcing the joint containerized cross-domain workspace solution.

  • Anthropic Pledges $15M to Cyber Defense for State and Local Governments

    Anthropic Pledges $15M to Cyber Defense for State and Local Governments

    Anthropic, the AI company behind the Claude family of models, has launched a $15 million cyber defense program aimed at state, local, tribal and territorial (SLTT) governments, as first reported by StateScoop on June 13, 2026. The commitment marks one of the more visible moves by a frontier AI vendor into public-sector cybersecurity, a domain historically served by federal grant programs, information-sharing organizations, and traditional security contractors.

    Executive Summary

    The announcement is straightforward in outline: $15 million, directed at the roughly 90,000 units of government below the federal level in the United States — states, counties, cities, tribal nations, and territories — under the banner of cyber defense. These entities collectively run elections, 911 dispatch, water utilities, courts, and school districts, yet many operate with security budgets that would not cover a single enterprise analyst’s salary.

    Why it matters: SLTT governments are among the most frequently attacked and least defended organizations in the country, and the question of who should fill that gap — federal agencies, states themselves, or private vendors — is unsettled. An AI company stepping in with direct funding reframes that debate. It also positions AI-assisted security tooling in front of a vast, fragmented public-sector market at a moment when both the threat landscape and the defensive toolchain are being reshaped by AI. The reported release, however, is thin on mechanics: the program’s structure, eligibility, and deliverables are not detailed in the source material, so the scale of real-world impact remains to be demonstrated.

    The Soft Underbelly of American Cyber Defense

    SLTT governments occupy an unenviable position: they hold sensitive data (voter rolls, health records, court files) and run critical services (water, dispatch, schools), yet they buy security with some of the smallest IT budgets in the economy. Ransomware crews have long understood this asymmetry — small municipalities and school districts have been recurring victims precisely because a locked-up 911 system or payroll server creates immediate pressure to pay. Any credible new funding source for this tier of government addresses a real, well-documented gap, not a manufactured one.

    The structural problem is fragmentation. Unlike a federal agency, there is no single buyer, no shared baseline, and often no dedicated security staff at all in smaller jurisdictions. Programs that work at this tier tend to deliver shared services — centralized monitoring, common tooling, pooled expertise — rather than writing thousands of small checks. Whether Anthropic’s program takes that shape is not specified in the source reporting, and it is the single biggest determinant of whether $15 million produces measurable defense or diffuse goodwill.

    Why an AI Vendor Is Writing This Check

    There are at least three plausible and non-exclusive readings. First, genuine mission alignment: Anthropic has publicly framed itself around AI safety, and AI is already changing offensive tradecraft — faster phishing, faster vulnerability discovery — so an AI vendor investing in the defensive side of that ledger is coherent. Second, market development: public-sector security is a large, sticky market, and a philanthropic or subsidized entry builds relationships and reference deployments with thousands of potential future customers. Third, policy positioning: frontier AI companies face active regulatory scrutiny, and visible contributions to public cyber defense are a constructive answer to the question of whether AI makes society safer or more exposed.

    None of these motives is disqualifying — corporate programs routinely serve mission and market at once. The fair test is not motive but design: whether aid is delivered without product lock-in, whether recipients are chosen on need, and whether outcomes are reported. The source material does not yet answer any of those questions, so judgment should wait for the program’s actual terms.

    What $15 Million Does — and Does Not — Buy

    Context matters for the number. Fifteen million dollars is meaningful as a corporate program and modest against the scale of the problem: spread evenly across all SLTT entities it would amount to a few hundred dollars each, and federal SLTT-focused cyber grant programs have operated at hundreds of millions per year. That comparison is not a criticism — it is a sizing exercise. Concentrated well (for example, on shared services, incident-response capacity, or training for the smallest jurisdictions), $15 million can move the needle for a defined cohort. Spread thin, it becomes a press release with a long tail of small line items.

    The more durable effect may be signaling. If a frontier AI company treats SLTT cyber defense as a priority worth funding, it invites peers — other AI vendors, cloud providers, security firms — to match or exceed the commitment, and it gives state CISOs a new category of partner to negotiate with. For the infrastructure sector, it is also a reminder that the security perimeter of public services increasingly runs through commercial AI and cloud platforms, and the entities operating those platforms are becoming direct participants in public-sector defense, not just suppliers to it.

    Background

    Anthropic was founded in 2021 and develops the Claude family of AI models, competing with OpenAI, Google, and others at the frontier of the field. The company has made AI safety central to its public identity, and — like its peers — has faced growing questions about how AI reshapes cybersecurity, since the same capabilities that help defenders analyze threats can help attackers craft them.

    Public-sector cyber defense below the federal level has long been a recognized weak point in the United States: thousands of small governments with critical responsibilities, uneven funding, and heavy dependence on federal grants and shared-service organizations. Vendor-funded assistance programs are not new — cloud and security companies have offered discounted or donated services to governments before — but a frontier AI company committing a dedicated eight-figure program to the SLTT tier is a notable extension of that pattern.

    Source: Anthropic launches $15M cyber defense program for state, local, tribal and territorial governments — StateScoop’s June 13, 2026 report on Anthropic’s public-sector cybersecurity funding commitment.

  • CISA Nears New AI Cyber Directive: Binding Federal Rules Take Shape

    CISA Nears New AI Cyber Directive: Binding Federal Rules Take Shape

    The Cybersecurity and Infrastructure Security Agency (CISA) is close to issuing a new cyber directive addressing artificial intelligence, according to a June 5, 2026 report from Federal News Network. Directives are CISA’s most forceful policy instrument: unlike advisory frameworks, they carry mandatory compliance obligations for federal civilian executive branch agencies.

    Executive Summary

    According to Federal News Network, CISA is nearing release of a new cyber directive focused on artificial intelligence. The report, surfaced via Google News on June 5, 2026, offers few public details, but the vehicle itself is the story: a CISA directive is not a white paper or a best-practices guide — it is an enforceable order to federal civilian agencies, typically issued under authority Congress granted in the Federal Information Security Modernization Act.

    If the directive materializes as reported, it would mark a shift in federal AI security policy from encouragement to obligation. To date, most of CISA’s AI work — its AI roadmap, joint secure-AI-development guidelines, and deployment guidance — has been voluntary. A directive would convert some portion of that guidance into requirements with deadlines and reporting obligations, which is precisely the moment such policies start reshaping agency budgets and vendor behavior.

    The caveat matters as much as the headline: the source material available here is a headline-level report, not the directive text. Scope, deadlines, and requirements remain unconfirmed, and readers should treat any characterization of the directive’s contents as premature until CISA publishes it.

    From Voluntary Guidance to Enforceable Mandate

    The distinction between CISA guidance and a CISA directive is the difference between advice and law-adjacent obligation. Binding Operational Directives (BODs) — the agency’s standard mandatory instrument — compel federal civilian executive branch agencies to take specific actions on defined timelines, with CISA tracking compliance. Prior BODs, such as the 2021 order requiring agencies to remediate known exploited vulnerabilities, demonstrably changed federal patching behavior because they attached deadlines and oversight to what had previously been discretionary hygiene.

    Applying that machinery to AI would be a first-of-its-kind move. Federal AI security posture has so far been shaped by a patchwork of executive orders, Office of Management and Budget memoranda on AI governance and acquisition, and voluntary CISA publications. Those set expectations; none of them gave CISA a compliance-tracking lever specific to AI systems. A directive would create one, and it would signal that the government now views insecure AI deployments as an operational risk on par with unpatched software or exposed management interfaces.

    What Compliance Could Actually Demand of Agencies

    While the directive’s contents are unconfirmed, CISA’s past directives follow a recognizable pattern: inventory what you have, assess or remediate it, and report status. For AI, even the inventory step is nontrivial. Agencies would need to identify where AI models and AI-enabled services run inside their environments — including capabilities embedded in commercial software they did not procure as “AI.” Federal agencies have historically struggled with basic asset visibility, which is why CISA issued a directive on that very subject in 2022; AI discovery layers a harder problem on top of an unsolved one.

    Security requirements for AI systems also differ from conventional IT controls. Model supply chains, training-data provenance, prompt-injection exposure, and access controls around model endpoints are newer disciplines with immature tooling and thin federal workforce expertise. Any directive with aggressive deadlines will collide with those capacity constraints, and how CISA balances urgency against feasibility will determine whether the order drives real security improvement or a paperwork exercise.

    Market Ripples: Vendors, Contractors, and the Compliance Economy

    Federal mandates create markets. When agencies are ordered to inventory, secure, or monitor a class of technology, procurement demand follows — for discovery tooling, AI security testing, model monitoring, and compliance reporting. Vendors selling AI systems into government should expect security questionnaires and contract clauses to tighten in the directive’s wake, because agencies typically push their own obligations downstream to suppliers.

    There is also a well-documented spillover effect: federal security mandates often become de facto commercial baselines, as happened with federal cloud security authorization standards. Enterprises watching a CISA AI directive would gain a ready-made template for their own AI governance programs. For infrastructure and security providers, that makes this directive worth tracking even for firms with no federal business — it is a preview of the requirements large customers may soon impose on their own vendors.

    Background

    CISA was created in 2018 to lead civilian federal cybersecurity, and its directive authority — the power to order federal civilian agencies to act — has become its most consequential tool, used against threats ranging from actively exploited software flaws to compromised network appliances. On AI specifically, CISA published an AI roadmap in late 2023 and co-authored international guidelines for secure AI system development and deployment, but all of that work was advisory.

    Meanwhile, federal AI adoption has accelerated under successive executive orders and OMB policies pushing agencies to use AI while managing its risks. That combination — fast adoption plus voluntary security guidance — created exactly the gap a directive is designed to close, which is why reports of a mandatory CISA AI directive represent a meaningful escalation rather than routine policy output.

    Source: CISA close to issuing new cyber AI directive — Federal News Network report, June 5, 2026, that CISA is nearing release of a new mandatory cyber directive addressing artificial intelligence.