Which security investments are you prioritising for FY27?
Identity, cloud security posture, AI security, SOC automation, resilience? Share your top two and why.
In short
Identity covers how people, services and devices prove who they are and what they may access: single sign-on, multi-factor authentication, privileged access and managing accounts from joining to leaving. Buyers care because stolen credentials and over-broad permissions sit behind many breaches, and identity now spans staff, cloud workloads and AI agents.
Written by Techarda editors · Updated · How we work
The newest Identity and access stories from the last 90 days. Each one opens with our summary and a link to the original source.
Why the controls on an AI agent have to live outside of it, and what a security operations team can implement and maintain those controls. The new privileged user in your environment Security teams spent two decades learning how to work with the people they trust most. Domain admins, DBAs, finance approvers and contractors with VPN access all get a mature playbook: verified identity, scoped…
Discover how to secure AI agents in your cloud environment with Tenable One Cloud Exposure. We explore Microsoft Entra Agent ID and provide essential best practices for robust agentic AI identity security. Key takeaways Understand your current maturity level and then build an appropriate action plan to secure your agent identities. Use your cloud providers’ native tools or Tenable One Cloud…
Wiz CIRT responded to AI-driven attacks spanning cloud, Kubernetes, CI/CD, and identity. Learn how these attacks behave and how to detect them.
TL;DR: OCI specification fundamentally separates the “WHERE” (addressing, routing, registry URLs, and transports) from the “WHAT” (the immutable artifact, its layers, and its execution contract). The key realization of this post is that OCI focuses almost exclusively on the “WHAT.” By standardizing the content, its cryptographic identity, and how it unpacks, OCI leaves addressing and routing…
Identity alone doesn't guarantee a bot will behave responsibly. We are introducing a system to continuously evaluate whether Verified bots honor site preferences, like robots.txt and HTTP 429s, ensuring they remain accountable over time.
Every turn of the AI loop adds new weights, traces, and access paths. CoreWeave CISO Jim Higgins discusses keeping identity, keys, and telemetry attached to the work as it moves.
Connect AI agents to CloudBees CI with single sign-on instead of API tokens, and keep runtime credentials out of build logs. Now generally available.
Agents represent a fundamental shift in cloud operations. They can act on behalf of users or autonomously, make non-deterministic decisions, and request data across projects at unprecedented speed and scale. Because agents are a distinct category of non-human identity (NHI), they require unique secure-by-default guardrails. Traditional, manually-operated network perimeters are vulnerable to…
Showing the newest 60 of 67. The feed archive lists every story by month.
Stories say what companies announced. These threads are where people who work with Identity and access compare notes.
Identity, cloud security posture, AI security, SOC automation, resilience? Share your top two and why.
Identity-first access, device posture, microsegmentation: which parts are done and which keep slipping?
The active companies with the most Identity and access stories in the last 90 days. It counts news coverage, not quality, market share or fit for your needs.
Where Identity and access sits among the categories Techarda covers. Each hub shows who is active, and each guide sets out how to evaluate vendors.
Plain definitions of terms that come up in Identity and access stories, from the Techarda glossary.
Multi-factor authentication that can’t be tricked into working on a fake site, such as passkeys or hardware security keys. Codes sent by text message and one-tap approvals can be phished or worn down by repeated prompts.
Controls for accounts with powerful rights, such as administrators and service accounts: vaulting credentials, granting access only when needed, recording sessions and removing standing privilege where possible.
Give every workload and agent its own identity with the least access it needs, prefer short-lived credentials to long-lived keys, and review them as you would human accounts. Machine identities are easy to forget.
Stories are filed under topics automatically from their headline and summary, so the odd one may sit in the wrong place. Spotted one, or a topic we should add? Email engage@techarda.com. All topics.