Dev48
Language
  • About
  • Services
  • Industries
  • Technologies
  • Articles
  • Contacts
Book a call
    Home/Articles/Securing ai agents in technology media and telecom five zero trust rules
Dev48
info@dev48.org+375 29 320-40-96WhatsApp@isky_by

© 2026 · All rights reserved.

Securing AI agents in technology, media, and telecom: Five Zero Trust rules

Source: Okta•November 19, 2026 at 09:16 AM

Securing AI agents in technology, media, and telecom: Five Zero Trust rules

Learn the 5 essential rules to secure autonomous AI agents and best practices for implementing an identity-first, Zero Trust enterprise security architecture in TMT

TL;DR

Securing autonomous AI agents requires an identity-first, Zero Trust architecture built on five technical controls:

  • Short-lived credentials
  • Dual-layer on-behalf-of authorization
  • Cryptographically attested agent identities
  • Continuous automated offboarding
  • Fail-closed system designs.

For TMT companies, these controls protect source code and API supply chains, streaming revenue and

Why AI agent security demands an identity-first architecture

Technology, media, and telecom (TMT) companies are deploying AI agents across their workforces faster than almost any other industry:

  • Technology: Engineering teams use agents to write and review code.
  • Media and entertainment: Production teams use them to tag, transcode, and route media.
  • Telecommunications: Network operations teams use them to triage alerts and adjust configurations.

Each agent works on behalf of an employee and has access to real systems, posing a major security risk. Safe deployment requires an identity-first approach that balances autonomy with tight centralized control.

Securing this paradigm requires answering three core questions highlighted in the blueprint for the secure agentic enterprise:

  • Where are my agents?
  • What can they connect to?
  • What can they do?

By establishing clear guardrails around authentication and authorization, TMT organizations can innovate rapidly while helping protect critical systems. Here are the five essential rules for securing autonomous AI agents in the enterprise.

Five core rules for securing AI agent architectures

Rule 1: Eliminate long-lived agent credentials in favor of short-lived tokens

Giving an AI agent direct, permanent credentials such as static API keys or personal access tokens creates severe risk. When an agent uses these credentials, it effectively impersonates a user with broad, often unknown privileges—meaning a single compromised key can cause widespread system damage.

  • The fix: Instead, agents should only use short-lived access tokens retrieved through a central identity provider.
  • Architectural enforcement: Architectures must explicitly block direct OAuth grants and session-impersonating agentic browsers. This design establishes a central control plane that allows security teams to rapidly revoke access with a single kill switch if an agent strays.

In TMT, this risk is concrete: A coding agent with a standing token can push changes across every repository its owner can reach; a media agent with a permanent storage key can read an entire unreleased content library; and a network agent holding static configuration keys can execute unapproved changes.

Rule 2: Enforce true dual-layer on-behalf-of authorization

Most current AI deployments rely on problematic user impersonation that obscures accountability and breaks least-privilege principles. Resolving this requires tying identity and execution together into a single, cohesive governance framework.

  • Dual-layer verification: True "on-behalf-of" flows require dual-layer authorization: The authorization server independently verifies the permissions of both the active agent and the underlying human subject.
  • Effective scope: The agent is granted only the intersection of the two permission sets.
  • Auditability: This dynamic context enables full visibility, as audit logs record both identities simultaneously, helping ensure clear, end-to-end trace-level accountability.

This matters most where a single agent acts for both an engineer and a vendor, or a production planner and a freelancer. The overlap check stops the agent from inheriting access the human in the chain should not have.

Rule 3: Require cryptographic identity and tamper-evident audits

You cannot secure an agent if you cannot uniquely and reliably identify it. Autonomous agents must authenticate using cryptographically unique identifiers that rely on secure storage and remote attestation.

  • Immutable audit logs: Every authorization request and action taken by the agent must be captured in an immutable audit trail that maintains cryptographic integrity.
  • Revocation control: You need a central control plane to maintain the authority to rapidly revoke these credentials whenever necessary.

In TMT, these logs also support regulatory and content-rights reviews. Network operators and studios can show exactly which agent changed a configuration or released a file, and when.

Rule 4: Implement continuous, automated agent lifecycle management

Least privilege is an ongoing discipline, not a one-time configuration. Unmonitored agents (shadow AI) become prime targets for attackers.

  • Blast radius reduction: Restricting an agent's privileges minimizes the potential blast radius if an LLM experiences prompt injection or generates unintended actions.
  • Automated deprovisioning: Security teams must regularly review agent inventories to retire those showing inactivity, weak business value, or erratic performance. Offboarding unused agents also helps prevent abandoned credentials from becoming easy targets for attackers.

Agents tied to a finished production, a retired network project, or a departed contractor are common sources of orphaned access. Review them on the same cycle as human leavers.

Rule 5: Mandate fail-closed, policy-enforced security architectures

System disruptions or security failures must never result in expanded capabilities for an AI agent.

  • Fail-secure defaults: If an agent's authentication, authorization, or security harness is interrupted, the system must rapidly default to a loss of availability.
  • Resilience strategy: Failing closed helps ensure that security degradation doesn’t translate into unverified autonomous access. For example, a successful denial-of-service attack against a security subsystem should shut the agent down rather than leave it unmonitored.

Build an identity-first security foundation with Okta for AI Agents

Securing autonomous AI agents requires moving beyond traditional access controls to establish centralized visibility, short-lived credentials, and strict fail-closed architectures.

Okta for AI Agents can help you implement these identity-first guardrails and safely deploy agentic workflows in your enterprise.

Download our AI Identity Security Compliance Checklist to discover how to help prevent shadow AI, enforce fine grained authorization, and implement a centralized control plane that allows you to innovate confidently without compromising security.

These materials are intended for general informational purposes only and are not intended to be legal, privacy, security, compliance, or business advice. ©2026 Okta, Inc. and/or its affiliates.

← All articles

What this article says

More in Cybersecurity

All →
Stocks making the biggest moves premarket: Palo Alto Networks, Take-Two Interactive, Everpure & moreПресса
Palo Alto Networks

Stocks making the biggest moves premarket: Palo Alto Networks, Take-Two Interactive, Everpure & more

NGINX HTTP/2 Vulnerabilities: How to Identify Affected Images and Apply Security Updates
Aqua Security

NGINX HTTP/2 Vulnerabilities: How to Identify Affected Images and Apply Security Updates

Secure SI by Design Consortium Officially Approved by U.S. Government
CyberArk

Secure SI by Design Consortium Officially Approved by U.S. Government

Java4Shell Remote Code Execution (RCE) Vulnerability - CVE-2026-114938
Elastic

Java4Shell Remote Code Execution (RCE) Vulnerability - CVE-2026-114938

NCC Group marks fifth year of Empowering You sponsorship with 2026 cyber security leadership graduations
NCC Group

NCC Group marks fifth year of Empowering You sponsorship with 2026 cyber security leadership graduations

Expert commentary: Responding to the critical Java4Shell vulnerability
NCC Group

Expert commentary: Responding to the critical Java4Shell vulnerability

More from Okta

Putting the Blueprint Alliance into practice: Why securing AI starts with identity and requires a connected st
Okta

Putting the Blueprint Alliance into practice: Why securing AI starts with identity and requires a connected st

How Okta can help meet CMMC 2.0 Access Control requirements
Okta

How Okta can help meet CMMC 2.0 Access Control requirements

Celebrating identity leadership: Okta Certification Circle and Champions light the way
Okta

Celebrating identity leadership: Okta Certification Circle and Champions light the way

Your endpoints are running AI agents you can't see
Okta

Your endpoints are running AI agents you can't see

How Okta Identity Governance helps you see, define, and control your entitlements
Okta

How Okta Identity Governance helps you see, define, and control your entitlements

Shadow AI just got proactive: Securing personal AI agents at the endpoint
Okta

Shadow AI just got proactive: Securing personal AI agents at the endpoint