Cequence Security And KPMG Collaborate On Joint Report Examining How Organizations Can Govern And Secure Agentic AI
(MENAFN- Mid-East Info) New Cequence data in the report shows AI agents already signing in, booking and buying on behalf of customers, often without identifying themselves
Borderless Finance. AI-Native.
Your digital companion for smarter everyday choices. Built for how you live, earn, and grow. Move money at your pace with AI-powered finance, all in one tap.
Join the waiting list. Earn Dubai, UAE. - Nov, 2026 - Cequence Security, the leader in application, API, and agentic AI protection, today published Agentic AI Runtime Security, Governance, and Control, a report on governing AI agents as they act. This report has been developed with input from KPMG in Singapore, examining how organizations can govern and secure Agentic AI as agents move from generating content to autonomously taking consequential actions. The findings of the report will be presented to senior business, technology, and policy leaders at a joint event hosted at KPMG's office in Singapore on Nov. 19. Read the executive brief or download the full report. AI is shifting from answering questions to taking action, with agents now issuing refunds, updating records, and moving money. The report sets out how to govern those actions as they happen, for agents deployed by organizations. What Cequence's analysis and data show:-
Agents already act for customers: In one week of October 2026, Cequence's CQ Prime research team tracked more than a quarter million AI agent visits across five industries. About one in seven booked, bought, signed in or managed an account for the customer.
Many never say they are agents: At a Tier 1 telecommunications carrier, traffic from agents that didn't identify themselves as agents grew from about 100 requests a day to as many as 32,000 within three weeks of a major consumer AI agent's launch. They signed in as the customer and passed multi-factor authentication.
A trusted name proves nothing: At one online marketplace, more visits claimed to be Google-Agent than all the genuine agent visits Cequence tracked that week. Every visit went straight to the sign-in page and failed, a sign of attackers testing stolen passwords in bulk under a legitimate agent's name. Google was not involved.
-
Give each agent a specific job, not open-ended authority: Each agent should work from a plain-language job description turned into hard limits, so it can't decide on its own to do more.
Check every action in real time: A separate control outside the agent should approve, escalate, or block each action in real time, since harmless-looking steps can add up to something the agent isn't allowed to do. When it blocks an action, it should point the agent to the allowed route so the work still gets done.
Measure success by work completed, not actions blocked: Good governance and security let agents get more legitimate work done without the organization losing control.
Legal Disclaimer:
MENAFN provides the
information “as is” without warranty of any kind. We do not accept any
responsibility or liability for the accuracy, content, images, videos,
licenses, completeness, legality, or reliability of the information
contained in this article. If you have any complaints or copyright issues
related to this article, kindly contact the provider above.

Comments
No comment