Notifications
Clear all
Topic starter
01/08/2026 10:47 pm
TL;DR: An MCP-connected AI can create tenants, deploy rules, enable Git Sync, and generate keys from a single prompt, collapsing manual onboarding into minutes, according to LimaCharlie. That speed improves operations, but it also means identity, privilege, and audit assumptions must be rebuilt around agentic execution rather than human-paced workflows.
NHIMG editorial — based on content published by LimaCharlie: Agentic AI Security: Spin Up a Fully Configured Tenant in Minutes
By the numbers:
- Only 44% of organisations have implemented any policies to manage their AI agents, despite 92% agreeing that governing AI agents is critical to enterprise security.
- Systems with least-privileged AI access had a 17% incident rate vs 76% for over-privileged systems.
- When AWS credentials are exposed publicly, attackers attempt access within an average of 17 minutes , and as quickly as 9 minutes in some cases.
Questions worth separating out
Q: How should security teams govern AI agents that can access enterprise systems?
A: Security teams should govern AI agents as non-human identities with explicit ownership, scoped privileges, and continuous monitoring.
Q: Why do agentic AI workflows create new IAM risk compared with traditional automation?
A: Traditional automation usually follows fixed rules and predictable paths, so its access model is easier to review.
Q: What breaks when AI workloads use NHI-style credentials without lifecycle control?
A: What breaks is reviewability and revocation.
Practitioner guidance
- Inventory every prompt-to-action path Map which prompts can trigger tenant creation, API key issuance, rule deployment, or integration changes.
- Constrain agent permissions to task-scoped APIs Split platform APIs so the agent can only invoke the minimum set of endpoints needed for a specific onboarding task.
- Govern AI-generated secrets as NHIs Register every AI-created key, token, or certificate as a managed non-human identity with owner, expiry, rotation, and revocation controls.
What's in the full article
LimaCharlie’s full blog covers the operational detail this post intentionally leaves for the source:
- The exact prompt and resulting tenant-provisioning sequence from Claude Code, including the order of platform actions.
- The mechanics of Git Sync setup and how the repository is linked to tenant configuration state.
- The platform-specific workflow for generating the keys needed to complete the onboarding flow.
- The demonstration context for MSSPs that need repeatable tenant baselines across multiple clients.
👉 Read LimaCharlie’s blog on spin-up of a fully configured agentic AI tenant →
Agentic AI security tenants: what IAM teams need to watch?
Explore further
01/08/2026 10:56 pm
Agentic SecOps creates an identity governance problem, not just an automation problem. When an AI can create tenants, generate keys, and modify security posture from a single prompt, the actor is exercising runtime authority rather than merely triggering a workflow. That changes the governance surface from task completion to delegated execution, which is a different control model. Practitioners should treat this as an NHI governance issue with agentic characteristics, not as a conventional orchestration feature.
A few things that frame the scale:
- Only 44% of organisations have implemented any policies to manage their AI agents, despite 92% agreeing that governing AI agents is critical to enterprise security, according to The 2026 Infrastructure Identity Survey.
- A separate finding from the same survey shows that 53% of security leaders expect AI to run major portions of their infrastructure autonomously within the next three years.
A question worth separating out:
Q: How do teams keep version control from masking governance gaps in agentic operations?
A: Use version control for traceability, but pair it with identity controls that answer who authorised the change, which actor executed it, and whether the action stayed inside policy. A clean repo history does not prove the agent was correctly scoped or that its privileges were appropriate.
👉 Read our full editorial: Agentic AI security tenants expose new IAM and governance gaps
