HCLTech and Anthropic have announced a global partnership centred on deploying Claude in enterprise environments. HCLTech plans a dedicated Anthropic business unit and centre of excellence, with secure sandboxes, implementation services and integrations across parts of its software portfolio, including BigFix, AppScan and Actian.

The companies describe policy guardrails and human oversight as part of the offer. Those statements set an expectation, but customers will still need evidence at the level of each workflow: which model and tools are used, where data is processed, what actions require approval and how behaviour is logged, tested and reversed.

The commercial significance is that agent governance is becoming a managed transformation product. Many buyers will not procure a model in isolation. They will buy a combination of model access, systems integration, security controls, change management and operational support. That gives service providers considerable influence over the quality of the resulting control environment.

A good implementation contract should therefore specify measurable control outcomes, not just delivery milestones. Examples include complete agent inventory, traceable tool calls, prompt-injection testing, rollback procedures and clear responsibility across the model provider, integrator and customer. Governance cannot disappear into the gap between those parties.

Execution Level Governance- What audit-ready agent governance actually looks like
David Girvin, founder and CEO of Assury argues that model-in-the-loop review, AI governing AI, is fundamentally unreliable for regulated environments: even the best-performing models miss a meaningful share of violations, the reviewing model is typically provided by the same vendor being reviewed, and prompt injection or context poisoning can compromise both the acting agent and its supposed overseer simultaneously. He makes the case for deterministic, architecturally enforced controls instead, walking through Assury's approach of autonomy zones, session risk accumulation, and credential starvation, which lets a compromised agent be cut off from its tools instantly rather than relying on time-boxed access. The conversation touches on why David is sceptical of just-in-time credentialing as a solution for agent security more broadly, since agent sessions don't run on predictable human timescales, along with the current gap between how identity and security vendors are pitching agent protection and what he sees happening at the execution layer in practice. He also discusses the compliance and audit implications of probabilistic decision-making, arguing that regulated industries will increasingly need tamper-evident, hash-chained audit trails that can withstand scrutiny from auditors and regulators who are only beginning to understand agentic risk, and reflects on a named frontier lab's own published framework as an example of the gap between research and practitioner reality. Elsewhere, David reflects candidly on building a bootstrapped security company in an increasingly crowded market, why he turned down aggressive VC funding to stay in control of the product, and what a credible third-party assessment of his own gateway would need to look like given that Assury sits directly in the execution path for every customer's agents.
BrightTALK
Share this post
The link has been copied!