# identity-and-access Published articles for identity-and-access. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How CockroachDB and IBM LinuxONE Rockhopper 5 Power Resilient AI Infrastructure DevFeed: [How CockroachDB and IBM LinuxONE Rockhopper 5 Power Resilient AI Infrastructure]() Original publisher: [Read original article]() Author: Kyle Basile Published: 2026-07-07T00:00:00Z Content type: article Language: en Sources: [Cockroach Labs]() Topics: [AI Infrastructure](), [NVIDIA DGX](), [CockroachDB](), [ibm](), [Databases](), [AI Development]() Tags: [ai](), [ai-infrastructure](), [availability](), [cockroachdb](), [concurrency](), [consistency](), [customers](), [data](), [digital](), [distributed](), [engineering](), [enterprise](), [failover](), [financial](), [ibm](), [identity](), [identity-and-access](), [identity-and-access-management](), [infrastructure](), [security]() ### AI overview The article explains how enterprise AI workloads increase requirements for continuous data availability, high concurrency, real-time decision-making, and elastic scaling. It presents IBM LinuxONE Rockhopper 5 and CockroachDB as infrastructure and data-platform components for resilient AI applications, including semantic retrieval, embeddings, agent memory, and transactional consistency. ### Source excerpt Why does AI require a new approach to infrastructure? ## Guide: How to Unify Identity Across Cloud and Data Center Infrastructure DevFeed: [Guide: How to Unify Identity Across Cloud and Data Center Infrastructure]() Original publisher: [Read original article]() Author: info@goteleport.com (Mayur Pipaliya) Published: 2026-05-01T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [IAM](), [trust](), [certificates](), [SPIFFE](), [Cloud](), [data centers](), [Amazon Web Services](), [Entra ID]() Tags: [certificates](), [cloud](), [critical-infrastructure](), [data-center](), [entra-id](), [identity](), [identity-and-access](), [infrastructure](), [spiffe]() ### AI overview This guide explains identity fragmentation across cloud accounts, data centers, and colocated infrastructure. It describes siloed identity systems, credential sprawl, and differing access models, and presents approaches including hardware roots of trust, short-lived certificates, shared certificate authorities, SPIFFE workload identities, reverse tunnels, and protocol-level enforcement. ### Source excerpt Inside this guide, discover the root causes of identity fragmentation across cloud and data center environments -- and what it takes to unify identity. ## Zero Trust Architecture: From Perimeter Walls to "Never Trust, Always Verify" DevFeed: [Zero Trust Architecture: From Perimeter Walls to "Never Trust, Always Verify"]() Original publisher: [Read original article]() Author: hello@ankit-rana.com Published: 2026-03-16T00:00:00Z Content type: tutorial Language: en Sources: [Ankit Rana | Mechanical Sympathy]() Topics: [Zero Trust](), [Architecture & Design](), [Encryption](), [least privilege](), [zero trust network access](), [Authentication](), [Authorization](), [Monitoring](), [Network]() Tags: [architecture](), [authentication](), [cloud](), [encryption](), [identity-and-access](), [least-privilege](), [monitoring](), [network](), [network-security](), [observability](), [security](), [security-architecture](), [zero-trust](), [zero-trust-network-access](), [ztna]() ### AI overview This article explains Zero Trust Architecture as a security model that assumes the network may already be compromised. It contrasts Zero Trust with perimeter security and describes explicit verification, contextual authorization, least privilege, encryption, segmentation, and continuous monitoring. It also distinguishes the broader ZTA model from Zero Trust Network Access (ZTNA). ### Source excerpt Zero Trust starts from the assumption that the network is already compromised, so every request is authenticated, authorised, and encrypted regardless of where it originates. It rests on explicit verification, least privilege, micro-segmentation, continuous monitoring, and encryption everywhere. It is an architectural direction, not a product you buy. ## The Agentic Identity Journey: Building IAM for Autonomous Actors DevFeed: [The Agentic Identity Journey: Building IAM for Autonomous Actors]() Original publisher: [Read original article]() Author: Ken Adler Published: 2025-06-03T21:53:51Z Content type: opinion Language: en Sources: [Indeed]() Topics: [IAM](), [identity and access management](), [Artificial Intelligence](), [Web]() Tags: [agentic-ai](), [agentic-iam](), [architecture](), [authentication](), [authorization](), [autonomous](), [iam](), [identity](), [identity-and-access](), [identity-and-access-management](), [privacy](), [resilience](), [security](), [software]() ### AI overview This commentary introduces Indeed's perspective on building an Agentic IAM architecture for a future in which autonomous and potentially malicious software agents interact with its platform. It emphasizes precise authorization, trustworthy delegation, verifiable auditing, speed, resilience, and privacy, and presents the post as the first entry in a series. ### Source excerpt Every so often, the web changes in a way that rewires how we live. In the early days, Web 1.0 let us read. It was a window into information -- static pages, digital brochures, news sites. We were spectators peering into a new world. Then came Web 2.0, and we learned to write. We didn't [...] ## Exploring DORA Compliance in Practice: Key Takeaways from Our Recent Webinar DevFeed: [Exploring DORA Compliance in Practice: Key Takeaways from Our Recent Webinar]() Original publisher: [Read original article]() Author: sami@goteleport.com (Sami Ali) Published: 2025-05-07T00:00:00Z Content type: article Language: en Sources: [Teleport]() Topics: [IAM](), [Access Control](), [identity and access management](), [Authorization](), [Security](), [Resilience](), [Monitoring]() Tags: [access-control](), [auditability](), [compliance](), [emea](), [eu](), [financial](), [governance](), [iam](), [identity](), [identity-and-access](), [monitoring](), [security](), [webinar]() ### AI overview This webinar recap explains how the EU's Digital Operational Resilience Act (DORA) affects access control, identity governance, auditability, and third-party risk for financial institutions and service providers. It describes how Teleport can support practical controls such as role-based access and scoped infrastructure access. ### Source excerpt Learn how financial institutions can achieve DORA compliance through practical IAM solutions, with insights from Teleport and Falx on implementing effective controls. ## Managing Machine Identities to Reduce Anonymous Computing Risks DevFeed: [Managing Machine Identities to Reduce Anonymous Computing Risks]() Original publisher: [Read original article]() Author: jason@intellyx.com (Jason Bloomberg) Published: 2025-02-25T00:00:00Z Content type: opinion Language: en Sources: [Teleport]() Topics: [identity and access management](), [Security](), [Vulnerabilities](), [Network](), [GitHub Actions]() Tags: [ci-cd-pipeline](), [identity-and-access](), [identity-and-access-management](), [network](), [security](), [toolchain](), [vulnerabilities]() ### AI overview The article argues that anonymous computing occurs when infrastructure assets use fictitious or shared identities without identifying the human making a request. It presents machine-identity management as a way to reduce security vulnerabilities without obstructing necessary work. ### Source excerpt It's Finally Time to Embrace Trusted Computing Does your corporate network treat users on VPNs as trusted regardless of who they are? Does your web server connect to its database as a fictitious user with a password in a config file somewhere? Or perhaps the most frightening scenario: did your platform engineer log in as root to configure your CI/CD pipeline toolchain? ## 2024 Predictions from Teleport CEO Ev Kontsevoy DevFeed: [2024 Predictions from Teleport CEO Ev Kontsevoy]() Original publisher: [Read original article]() Author: ev@goteleport.com (Ev Kontsevoy) Published: 2024-02-07T00:00:00Z Content type: opinion Language: en Sources: [Teleport]() Topics: [Cybersecurity](), [Security & Privacy](), [Authentication](), [Architecture & Design]() Tags: [api-keys](), [authentication](), [browser](), [cloud-computing](), [cybersecurity](), [identity](), [identity-and-access](), [predictions](), [secrets](), [security](), [social-engineering](), [tokens]() ### AI overview Teleport CEO Ev Kontsevoy's 2024 predictions describe rising identity-focused attacks, closer collaboration between engineering and security teams, and broader adoption of secretless authentication to reduce risks from exposed credentials and human error. ### Source excerpt Teleport CEO forecasts 2024 cybersecurity shifts: secretless access, evolving security roles, M&A consolidation, and least privilege strategies. ## Easily Manage IAM Policies for Serverless REST Applications in GCP with Goblet DevFeed: [Easily Manage IAM Policies for Serverless REST Applications in GCP with Goblet]() Original publisher: [Read original article]() Author: Austen Novis Published: 2023-07-10T20:09:55Z Content type: tutorial Language: en Sources: [Engineering at Premise - Medium]() Topics: [Google Cloud Platform (GCP)](), [IAM](), [Serverless](), [Authorization](), [Python](), [Framework](), [API]() Tags: [api](), [cloud-computing](), [deployment](), [framework](), [gcp](), [goblet](), [google-cloud-platform](), [iam](), [identity-and-access](), [permission](), [python](), [serverless](), [tutorial]() ### AI overview This tutorial explains how the Goblet Python framework automates IAM policy management for serverless REST applications on Google Cloud Platform. It covers identifying deployment permissions, enabling required APIs, creating custom roles and service accounts, and adding invoker bindings for connected services. ### Source excerpt By Austen Novis, Staff Software Engineer Photo by Akhilesh Sharma on Unsplash Writing and deploying serverless applications has never been easier, especially on Google Cloud Platform (GCP). With a few clicks developers are able to deploy their application to the cloud and then trigger calls in a variety of ways from Cloud Schedulers and Pubsub Subscriptions to API Gateways. Deploying your resources to GCP seems straightforward until you get a 403 error, permission denied. This error causes frustration as the root cause can be a number of issues, and often the solution requires knowing GCP roles and permissions in an in depth manner. The issue can be caused by the user not having the correct permissions to deploy their services or the services themselves not having the correct permissions to connect to each other. Once you have identified the problem you will need to understand what roles have the required permissions, how to apply those roles, and where to apply them. Instead of application developers wasting their time researching GCP documentation, searching stack overflow, or reaching out to devops teams, IAM access should be as automated as much as possible. Using the Goblet framework, we are now able to view exactly what permissions are needed to deploy our serverless applications, enable required GCP service API's, create a new custom role with these permissions, create a service account with this role, and add the correct invoker bindings so that all serverless services can connect to each other. Goblet is a python framework for writing serverless applications in GCP with the goal of making it as simple as possible to write and deploy REST applications. Goblet uses simple decorators, similar to flask, to create the necessary configurations and automatically deploy the required services and infrastructure. For example, with code below we can deploy a simple cloudfunction that is triggered by a pubsub subscription and a cloud scheduler. Goblet will also take ca