Notifications
Clear all
Topic starter
25/08/2026 9:13 am
TL;DR: Organizations need clearer identity, access, and session controls as AI systems, services, and agents reach into private resources, according to Tailscale. The underlying issue is not connectivity alone, but governing non-human access with records, time bounds, and trustable policy.
NHIMG editorial — based on content published by Tailscale: The TailscaleUp-date
Questions worth separating out
Q: How should security teams govern AI models that can call tools and access data?
A: Security teams should govern AI models as non-human identities with named owners, limited scope, short-lived credentials, and continuous authorization.
Q: Why do shared credentials create more risk in agentic and machine-to-machine access?
A: Shared credentials collapse accountability and expand blast radius.
Q: What breaks when privileged access is not continuously governed?
A: When privileged access is not continuously governed, standing privilege persists, dormant accounts remain usable, and the attack surface expands across human and machine identities.
Practitioner guidance
- Inventory AI and automation access paths Map every model, agent, service, and workflow that can reach internal repositories, databases, or admin tools, then assign each path a named owner and policy boundary.
- Replace standing privileged access with task-scoped sessions Require approval, time limits, and session recording for production databases, cloud consoles, and other sensitive systems instead of leaving reusable credentials in place.
- Separate machine access from privileged access Use different controls for routine service connectivity and high-risk admin actions so that broad machine reach does not implicitly grant elevated authority.
What's in the full article
Tailscale's full product preview covers the operational detail this post intentionally leaves for the source:
- The specific Aperture changes for model, agent, and tool governance that are only summarised here.
- The session-control workflow for approved privileged access to production systems.
- The programmable connectivity primitives and API changes that developers and platform teams can build on.
- The in-person and virtual TailscaleUp session details, workshops, and keynote coverage.
AI agent access, privileged sessions, and programmable connectivity?
Explore further
25/08/2026 9:14 am
Software acting on behalf of people is now an identity problem, not just an automation problem. When AI systems, services, and agents can reach into internal tools and databases, the security question becomes who or what is authorised to act, not whether the network is reachable. That shifts the centre of gravity from perimeter routing to identity governance for non-human actors. Practitioners should treat these flows as first-class NHI relationships.
A few things that frame the scale:
- The average estimated time to remediate a leaked secret is 27 days, despite 75% of organisations expressing strong confidence in their secrets management capabilities, according to The State of Secrets in AppSec.
- Only 44% of developers are reported to follow security best practices for secrets management, which helps explain why access governance often diverges from policy.
A question worth separating out:
Q: Who should own access paths created by programmable connectivity?
A: The team that creates the access path should also own its policy, review, and retirement. If software can create connectivity directly, governance cannot stop at network configuration. It must include classification, logging, lifecycle review, and a clear decision on when that path is no longer needed.
👉 Read our full editorial: TailscaleUp points to tighter identity controls for AI and privileged access
