# Identity Published articles for Identity. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Who gets to define an AI agent's intent? DevFeed: [Who gets to define an AI agent's intent?]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-09-15T20:25:55Z Content type: article Language: en Sources: [WorkOS Blog]() Topics: [AI Agent](), [Artificial Intelligence]() Tags: [ai](), [ai-agent](), [identity](), [policy](), [scopes](), [tool](), [workflow]() ### AI overview The article explains how to define an AI agent's intent while preserving identity, resource-access controls, and company policy. It argues that the requester should specify the agent's purpose and intended effects, while the organization determines which actions are permitted. Using Airlock examples, it distinguishes task intent from policy decisions such as approval or denial of specific operations. ### Source excerpt An agent's task describes the work to do. Learn how to define useful intent while keeping identity, resource access, and company policy in force. ## How Confluent Uses Third-Party Risk Assessments to Support Vendor Due Diligence DevFeed: [How Confluent Uses Third-Party Risk Assessments to Support Vendor Due Diligence]() Original publisher: [Read original article]() Author: Bethany Carter Published: 2026-09-15T16:40:06Z Content type: article Language: en Sources: [Confluent: Data in motion]() Topics: [Security](), [Business Security](), [vulnerability management](), [Cloud]() Tags: [apra](), [automated](), [cloud](), [compliance](), [confluent](), [confluent-cloud](), [data-protection](), [gdpr](), [identity](), [iso](), [nist](), [security](), [standards](), [third-party](), [trust-center](), [vulnerability-management]() ### AI overview Confluent explains how its Trust Center provides third-party risk assessment reports to support vendor security, resilience, compliance, procurement, and customer due diligence. The article describes assessments including ProcessUnity Global Risk Exchange and control mapping to customer frameworks. ### Source excerpt Confluent's Trust Center simplifies vendor risk reviews with CyberGRX, CyberVadis, SIG, CAIQ, and TruSight/KY3P assessments. ## Australia's Essential Eight replacement shifts cybersecurity compliance toward continuous exposure management DevFeed: [Australia's Essential Eight replacement shifts cybersecurity compliance toward continuous exposure management]() Original publisher: [Read original article]() Author: Ben Mudie Published: 2026-09-15T13:32:00Z Content type: article Language: en Sources: [Tenable Blog]() Topics: [Exposure Management](), [Cybersecurity](), [Security](), [Cloud](), [App]() Tags: [australia](), [ciso](), [cloud](), [compliance](), [cybersecurity](), [enterprise](), [essential-eight](), [exposure-management](), [identity](), [operational](), [organization]() ### AI overview The article describes Australia's replacement of the Essential Eight with an outcomes-focused cybersecurity framework covering enterprise IT, cloud, operational technology, and potentially agentic AI. It argues that organizations will need continuous evidence of their security posture, and presents exposure management as a way to identify and prioritize weaknesses and support current posture validation. ### Source excerpt Australia's move from the Essential Eight to an outcomes-based cybersecurity model will push organizations from conducting periodic point-in-time, checklist compliance assessments to having continuous evidence of a solid security posture. Key takeaways The Australian Signals Directorate (ASD) is moving from the Essential Eight cybersecurity framework to a new outcomes-focused Essentials series covering enterprise IT, cloud, operational technology (OT), and potentially agentic AI. The Essential Eight itself only ever covered on-premises enterprise IT, built around eight named technical controls, such as application control and patching. It never extended to the security of cloud, identity, or OT. The shift challenges the traditional checklist approach to cybersecurity, where organizations demonstrate compliance through periodic assessments and point-in-time reports. In dynamic environments spanning IT, cloud, identity, and OT, security posture can change quickly and repeatedly between assessments. Exposure management can help organizations continuously understand where they are exposed, prioritize the most critical weaknesses, and provide evidence of their current security posture. ASD's strategic shift to active security posture validation Can you prove your security posture is solid, right now, on demand? That's the question the Australian Signals Directorate (ASD) has effectively put in front of every Australian organization's board, CISO, and C-suite. ASD's decision to retire the Essential Eight signals a fundamental move away from point-in-time, checklist-based security toward an outcomes-focused model where organizations will need to demonstrate continuous compliance. It's no longer enough to show that your organization had a control in place at the time of the last assessment. In a technology environment that changes continuously across IT, cloud, identity, and operational technology (OT), organizations must be able to answer a much more immediate question: Ho ## Give every teammate and agent the right level of access to your Workers DevFeed: [Give every teammate and agent the right level of access to your Workers]() Original publisher: [Read original article]() Author: Visal In Published: 2026-09-15T13:00:00Z Content type: release Language: en Sources: [Cloudflare Blog]() Topics: [Workers](), [Authorization](), [Developer Platform](), [debug]() Tags: [agent](), [api](), [cloudflare](), [debug](), [developer](), [developer-platform](), [developers](), [identity](), [least-privilege](), [logs](), [metrics](), [monitor](), [product-news](), [scope](), [security](), [traces](), [workers](), [workflows]() ### AI overview Cloudflare now lets teams scope access to individual Workers and assign narrower Developer Platform roles. Teammates, CI tokens, and agents can receive only the permissions needed to debug, deploy, or monitor safely. ### Source excerpt You can now scope access to individual Workers and assign narrower Developer Platform roles, so teammates, CI tokens, and agents get only the access they need to debug, deploy, or monitor safely. ## What is CIAM in 2026 and why does it matter? DevFeed: [What is CIAM in 2026 and why does it matter?]() Original publisher: [Read original article]() Author: Ravleen Kaur Published: 2026-09-15T00:00:00Z Content type: tutorial Language: en Sources: [Twilio Blog]() Topics: [identity and access management](), [trust](), [ai-governance](), [Security](), [Artificial Intelligence](), [IAM](), [Generative AI]() Tags: [ai-agents](), [ai-governance](), [email](), [fraud](), [fraud-detection](), [identity](), [identity-and-access-management](), [industry-insights](), [messaging](), [mobile](), [trust]() ### AI overview This article explains how customer identity and access management (CIAM) is evolving from point-in-time password checks into a continuous trust and control layer. It describes CIAM's role in authenticating users, governing delegated authority for AI agents, evaluating risk across channels, and balancing low-friction access with fraud detection. It also distinguishes customer identity from workforce IAM. ### Source excerpt Discover how customer identity and access management (CIAM) uses continuous trust, deepfake defense, and agentic AI governance to protect users. ## How to answer the identity questions on an enterprise security questionnaire DevFeed: [How to answer the identity questions on an enterprise security questionnaire]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-09-14T00:00:00Z Content type: article Language: en Sources: [WorkOS Blog]() Topics: [Security](), [Single sign-on (SSO)](), [Provisioning](), [OpenID connect (OIDC)](), [App]() Tags: [configuration](), [enterprise](), [how-to](), [identity](), [integration](), [oidc](), [okta](), [provisioning](), [saml](), [security](), [sign-in](), [sso]() ### AI overview A practical guide to answering identity-related questions in enterprise security questionnaires. It explains what reviewers are really assessing behind SAML single sign-on and SCIM provisioning questions, including implementation details such as per-organization configuration, certificate rotation, and reliable deprovisioning. ### Source excerpt Every line has a literal answer and a real question behind it. Here is what the buyer is actually checking, which answers you can buy, and the three you cannot fake. ## CrowdStrike Announces Agentic Identity Provider DevFeed: [CrowdStrike Announces Agentic Identity Provider]() Original publisher: [Read original article]() Author: Ryan Terry Published: 2026-09-12T11:17:51.295154Z Content type: release Language: en Sources: [Blog]() Topics: [AI Agent](), [Next-Gen Identity Security](), [Authorization](), [Security](), [Authentication]() Tags: [2026](), [agentic](), [ai](), [ai-agent](), [api-keys](), [applications](), [authentication](), [authorization](), [cloud-infrastructure](), [code](), [enterprise](), [identity](), [identity-control](), [next-gen-identity-security](), [saas](), [security]() ### AI overview CrowdStrike announces Agentic Identity Provider, a capability in CrowdStrike Falcon Next-Gen Identity Security that gives AI agents trusted identities and continuously controls their access according to real-time security and business context. The announcement also covers expanded privileged access across SaaS applications, endpoints, code repositories, and cloud infrastructure. ### Source excerpt CrowdStrike gives every AI agent a trusted identity and controls their access based on real-time context, and expands modern privileged access. ## CrowdStrike Delivers the Next Evolution of the Agentic SOC DevFeed: [CrowdStrike Delivers the Next Evolution of the Agentic SOC]() Original publisher: [Read original article]() Author: Brandon Benke Published: 2026-09-12T11:17:51.295154Z Content type: article Language: en Sources: [Blog]() Topics: [Agentic SOC](), [SOC](), [Security](), [Artificial Intelligence](), [Automation](), [data](), [real-time](), [Reconnaissance](), [Cloud](), [Network]() Tags: [2026](), [agentic](), [agentic-soc](), [agents](), [ai](), [automation](), [cloud](), [data](), [identity](), [network](), [operations](), [platform](), [real-time](), [saas](), [security](), [soc]() ### AI overview CrowdStrike describes the next evolution of its agentic SOC, where analysts and AI agents work together in a unified system to investigate and respond to threats in real time. The Falcon platform combines data generation, enrichment, investigation, orchestration, and governance, with capabilities for detection-ready third-party data and coordinated specialist agents. ### Source excerpt Expert agents that reason together, learn your environment, and run on data CrowdStrike owns. See how we deliver the agentic SOC. Learn more! ## Set Up Cloud OIDC From the Pulumi CLI DevFeed: [Set Up Cloud OIDC From the Pulumi CLI]() Original publisher: [Read original article]() Author: Sean Yeh Published: 2026-09-11T00:00:00Z Content type: tutorial Language: en Sources: [Pulumi]() Topics: [OpenID connect (OIDC)](), [Command-line interface](), [AWS IAM](), [Cloud](), [AWS Identity and Access Management (IAM)](), [Azure](), [Google Cloud Platform (GCP)]() Tags: [automated](), [aws](), [azure](), [cli](), [cloud](), [configuration](), [docs](), [esc](), [google-cloud](), [how-to](), [iam](), [identity](), [oidc](), [openid-connect](), [product](), [pulumi](), [pulumi-cli](), [security](), [terminal](), [workflow]() ### AI overview This tutorial explains how to use the Pulumi CLI command pulumi env setup to configure Pulumi ESC as an OIDC provider for AWS, Azure, and Google Cloud. It covers interactive onboarding, non-interactive flags for scripts and agents, cloud credentials, account selection, access policies, and automatic creation of identity providers, IAM roles, policy attachments, and ESC environments. ### Source excerpt Pulumi ESC can act as an OpenID Connect (OIDC) provider for AWS, Azure, and Google Cloud, issuing short-lived, signed tokens that these clouds exchange for temporary credentials. This eliminates hard-coded credentials and improves your security posture. Last year, we introduced an onboarding flow in the Pulumi Cloud console that makes it super easy to configure OIDC for your cloud provider in a few guided steps. We're bringing Pulumi Cloud into the CLI so agents can use its capabilities directly from the terminal, without requiring a human to complete steps in the console. The new pulumi env setup command brings OIDC onboarding to that workflow, with interactive prompts for guided setup and non-interactive flags for scripts and agents. pulumi env setup - how it works Run the command with your desired cloud provider (aws, azure, gcp). For example: pulumi env setup aws The command then asks what it needs to configure your cloud, including your credentials, the accounts to configure, and the level of access. The questions differ per cloud. For AWS, it asks: How to authenticate to AWS. It uses the credentials you already have, or it signs you in with AWS SSO. Which accounts to configure. Which policy to attach to the OIDC role. Choose AdministratorAccess for Pulumi Deployments, ReadOnlyAccess for Pulumi Insights, or any other policy ARN. Then, it will print out the plan: About to configure OIDC for organization my-org: account 111111111111: create role pulumi-esc-oidc-622e86ea-319ba4c675bb3c00-role attach arn:aws:iam::aws:policy/AdministratorAccess create ESC environment my-org/aws-login/sandbox-account-env Proceed? [yes/no] After you confirm, the command creates the identity provider, the IAM role, and the policy attachment in each account. It then creates one ESC Environment per account, with the aws-login provider already configured. Non-interactive setup You can also run the command without interactive prompts by passing in the necessary flags. Each cloud has its ow ## (Re)introducing Developer Story DevFeed: [(Re)introducing Developer Story]() Original publisher: [Read original article]() Author: Philippe Beaudette Published: 2026-09-10T18:01:54Z Content type: news Language: en Sources: [Stack Overflow Blog]() Topics: [Programming](), [Code](), [Large Language Model](), [datasets]() Tags: [career](), [community](), [company](), [cv](), [datasets](), [developer](), [identity](), [llms](), [news](), [privacy](), [profile](), [programming](), [se-stackoverflow](), [se-tech](), [skills](), [work]() ### AI overview Stack Overflow is reintroducing Developer Story, a profile feature designed to showcase developers' careers, specialties, contributions, and technical identity. The article also introduces Stack Identity, a broader vision for verified proof of developer work, with privacy controls and integrations for verified contributions from other sites. ### Source excerpt For the past few years, we've been looking at ways to bring a little more of the individual developer back to Stack. ## The Machine With Many Faces: Post-Exploitation Identity Misuse in SPIFFE/SPIRE DevFeed: [The Machine With Many Faces: Post-Exploitation Identity Misuse in SPIFFE/SPIRE]() Original publisher: [Read original article]() Author: Eviatar Garzi Published: 2026-09-10T10:00:43Z Content type: article Language: en Sources: [Unit 42]() Topics: [Kubernetes]() Tags: [api](), [containers](), [cryptographic](), [identity](), [json](), [kubernetes](), [linux](), [malware](), [node](), [open-source](), [research](), [secrets](), [spiffe](), [spire](), [spoof](), [spoofing](), [threat-research](), [tool]() ### AI overview Research on a post-exploitation technique in which root access to a Kubernetes node can let an attacker spoof cgroup metadata used by SPIRE workload attestation, impersonate co-located workloads, and obtain SVIDs. ### Source excerpt Learn how root access on a compromised K8s node allows attackers to utilize SPIFFE/SPIRE metadata to spoof and harvest co-located workload identities. The post The Machine With Many Faces: Post-Exploitation Identity Misuse in SPIFFE/SPIRE appeared first on Unit 42. ## How Heurist Finance built an AI-native investment workbench on Amazon Bedrock AgentCore DevFeed: [How Heurist Finance built an AI-native investment workbench on Amazon Bedrock AgentCore]() Original publisher: [Read original article]() Author: JW Wang Published: 2026-09-09T18:11:12Z Content type: article Language: en Sources: [Artificial Intelligence]() Topics: [Amazon Bedrock](), [Claude](), [Orchestration](), [tracing]() Tags: [advanced-300](), [agent](), [ai](), [amazon-bedrock-agentcore](), [anthropic-claude](), [customer-solutions](), [identity](), [memory](), [observability](), [sandbox](), [tracing]() ### AI overview Heurist Finance uses Amazon Bedrock AgentCore to run a conversational investment workbench that accesses premium data per query and produces auditable, personalized research responses. ### Source excerpt Learn how Heurist built Heurist Finance, a conversational AI investment workbench, on Amazon Bedrock AgentCore. This customer story shows how AgentCore payments, Identity, Memory, Code Interpreter, and Observability let a small team buy premium market data per query, isolate analysis in a sandbox, and keep every action auditable. ## Passkey-themed social engineering leads to identity and cloud compromise DevFeed: [Passkey-themed social engineering leads to identity and cloud compromise]() Original publisher: [Read original article]() Author: Microsoft Security Research, Krithika Ramakrishnan, Bharat Vaghela, Vaibhav Deshmukh, Subhajit Ghosh, Anusha Chakraborty, Akash Chaudhuri, Victor Chingtham and Ivan Macalintal Published: 2026-09-09T17:41:18Z Content type: article Language: en Sources: [Microsoft Security Blog]() Topics: [MFA](), [data-processing]() Tags: [adversary-in-the-middle-aitm](), [apis](), [attacks](), [authentication](), [cloud](), [data](), [identity](), [mfa](), [phishing](), [security](), [social-engineering]() ### AI overview Microsoft Security Research describes a passkey-themed social-engineering campaign that compromises cloud identities through AiTM phishing or device-code flows, establishes authentication persistence, and collects cloud data. It outlines investigation signals and recommends revoking sessions and removing unauthorized authentication methods after confirmed compromise. ### Source excerpt Passkey-themed social engineering is being used to compromise identities and enable broader cloud attacks. Learn how threat actors establish MFA persistence, abuse Microsoft Graph for reconnaissance, and access SharePoint, OneDrive, and email data, along with key detection and mitigation guidance. The post Passkey-themed social engineering leads to identity and cloud compromise appeared first on Microsoft Security Blog. ## Why MCP security is about permissions overhaul DevFeed: [Why MCP security is about permissions overhaul]() Original publisher: [Read original article]() Author: Mohit Bansal Published: 2026-09-09T00:00:00Z Content type: article Language: en Sources: [Webflow Blog]() Topics: [Model Context Protocol (MCP)](), [Authorization](), [AI Agent](), [anthropic](), [GitHub]() Tags: [agent](), [ai](), [ai-agent](), [anthropic](), [github](), [identity](), [infrastructure](), [mcp](), [prompt-injection](), [security](), [server]() ### AI overview MCP security failures often arise from over-scoped credentials and weak permission boundaries rather than protocol bugs. The article examines prompt injection, tool poisoning, and confused deputy risks, and argues for redesigning access around the minimum permissions each task requires. ### Source excerpt Most MCP breaches trace back to over-scoped credentials, not broken code. Here's what a real permissions redesign checks for. ## Infrastructure identity for platform engineers DevFeed: [Infrastructure identity for platform engineers]() Original publisher: [Read original article]() Author: Sam Barlien Published: 2026-09-08T12:20:22Z Content type: tutorial Language: en Sources: [Platform Engineering Blog]() Topics: [Platform Engineering](), [internal developer platform](), [Zero Trust](), [IAM](), [AI Agent]() Tags: [iam](), [identity](), [internal-developer-platform](), [platform-engineering](), [zero-trust]() ### AI overview A guide for platform engineers on adopting infrastructure identity: assigning cryptographic identities and short-lived, just-in-time access to people, machines, workloads, and AI agents. It argues that this approach can replace static secrets and network-based trust in an internal developer platform. ### Source excerpt Discover how platform engineers can eliminate static secrets and embed Zero Trust into their IDP using short-lived, cryptographic infrastructure identities. ## Kubernetes access via an identity provider: Public client, not confidential DevFeed: [Kubernetes access via an identity provider: Public client, not confidential]() Original publisher: [Read original article]() Author: Kolawole Olowoporoku | CNCF Ambassador and Senior Platform Engineer Published: 2026-09-08T11:30:00Z Content type: tutorial Language: en Sources: [Cloud Native Computing Foundation]() Topics: [Kubernetes](), [Authorization](), [client]() Tags: [api](), [architecture](), [authentication](), [blog](), [browser](), [iam](), [identity](), [integration](), [kubernetes](), [on-prem](), [operations]() ### AI overview The article explains how to replace static Kubernetes credentials with identity-provider login using a public OIDC client and PKCE. It describes kubectl with kubelogin, Keycloak, kube-apiserver token validation, and RBAC-based access decisions. ### Source excerpt Access control belongs on the same day-zero checklist as networking and storage. On most on-prem clusters, it never makes the list. The Identity Gap Managed cloud Kubernetes ships IAM or SSO integration out of the box.... ## Three identity vendors shipped the same agent access pattern in eight days DevFeed: [Three identity vendors shipped the same agent access pattern in eight days]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-09-04T16:24:43Z Content type: article Language: en Sources: [WorkOS Blog]() Topics: [Auth0](), [Authorization](), [MCP](), [OpenID connect (OIDC)](), [Single sign-on (SSO)](), [Model Context Protocol]() Tags: [anthropic-claude](), [api](), [auth0](), [authorization](), [cross-app-access](), [identity](), [mcp](), [oidc](), [okta](), [sso]() ### AI overview Okta, Auth0, and Descope shipped implementations of the Cross App Access agent-access pattern between August 24 and September 1. The pattern uses a Client ID Metadata Document to identify calling software and an ID-JAG token exchange to let an identity provider control application access. ### Source excerpt Okta, Auth0, and Descope all shipped Cross App Access between August 24 and September 1. The two-layer pattern underneath it outlasts whichever vendor wins. ## How to Carry User Identity Across Federated Kubernetes and AI Platforms DevFeed: [How to Carry User Identity Across Federated Kubernetes and AI Platforms]() Original publisher: [Read original article]() Author: Elizabeth Goodman Published: 2026-09-03T22:36:02Z Content type: tutorial Language: en Sources: [NVIDIA Developer](), [NVIDIA Technical Blog]() Topics: [AI Platform](), [Kubernetes](), [AI, ML & Data Engineering]() Tags: [ai-platform](), [ai-platforms-deployment](), [api](), [aws](), [cloud](), [cloud-services](), [data](), [data-center-cloud](), [developer-tools-techniques](), [how-to](), [identity](), [infrastructure](), [kubernetes](), [software-defined-data-center]() ### AI overview The article presents a central identity-gateway pattern for carrying user identity across federated Kubernetes, data, and AI platforms. It uses OIDC, a shared session store, stateless data-plane gateways, and an identity-validation API to establish trusted local identity context without distributing raw tokens to every application. ### Source excerpt Modern AI platforms are no longer a single application behind one login screen. A user may start in a central portal, open a governed dataset, launch a notebook... ## Impersonating IT support: how threat actors turn a remote session into enterprise-wide access DevFeed: [Impersonating IT support: how threat actors turn a remote session into enterprise-wide access]() Original publisher: [Read original article]() Author: Microsoft Security Research, Sagar Patil, Arlette Umuhire Sangwa, Jesse Birch and Ravikant Tiwari Published: 2026-09-02T22:51:18Z Content type: article Language: en Sources: [Microsoft Security Blog]() Topics: [High Profile Threats](), [Node.js]() Tags: [c2](), [identity](), [infrastructure](), [javascript](), [microsoft-teams](), [node-js](), [powershell](), [security](), [social-engineering](), [windows]() ### AI overview Microsoft analyzes an intrusion campaign in which attackers impersonate IT support through Microsoft Teams, obtain remote access, deploy a Node.js and JavaScript implant, and move laterally through enterprise systems. The article provides detection, mitigation, and hunting guidance. ### Source excerpt Microsoft Threat Intelligence observed a human-operated intrusion campaign that abuses Microsoft Teams external collaboration to impersonate IT support, gain remote access, and deploy a Node.js-based implant. Learn how attackers move from social engineering to lateral movement using legitimate tools, and how Microsoft Defender helps detect and disrupt the activity. The post Impersonating IT support: how threat actors turn a remote session into enterprise-wide access appeared first on Microsoft Security Blog. ## Agentic security: Detection and response at machine speed DevFeed: [Agentic security: Detection and response at machine speed]() Original publisher: [Read original article]() Author: Gee Rittenhouse Published: 2026-09-02T18:36:37Z Content type: article Language: en Sources: [AWS Security Blog]() Topics: [Security & compliance, Cloud security](), [workload protection](), [AI Strategy]() Tags: [agentic](), [ai-agents](), [announcements](), [artificial-intelligence](), [autonomous](), [cloud](), [cloud-security](), [foundational-100](), [identity](), [security](), [security-blog](), [security-identity-compliance](), [zero-trust]() ### AI overview AWS discusses why autonomous AI agents require continuous security detection and response at machine speed. It outlines an enterprise framework that extends established practices such as identity governance, least privilege, defense in depth, and backup and recovery to agentic workloads. ### Source excerpt After talking with enterprise security leaders over the past year, one thing has become clear: the rise of autonomous AI agents is the most significant shift in security posture since the move to cloud. Organizations across every industry are adopting AI agents that authenticate on behalf of users, execute multistep workflows, and make decisions across [...] ## Workload identity trust policies govern CI/CD access to production cloud resources DevFeed: [Workload identity trust policies govern CI/CD access to production cloud resources]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-09-02T00:00:00Z Content type: article Language: en Sources: [WorkOS Blog]() Topics: [OpenID connect (OIDC)](), [CI/CD](), [GitHub Actions](), [GitHub](), [Cloud](), [Amazon Web Services]() Tags: [aws](), [ci-cd](), [github](), [identity](), [oidc](), [policy](), [production](), [secrets](), [trust]() ### AI overview This article explains that workload identities used by service principals and CI/CD federation can evade human-focused access reviews. It argues that OIDC trust policies are the key boundary controlling which federated jobs can obtain short-lived cloud access tokens and reach production resources. ### Source excerpt Service principals and CI/CD federation skip the access reviews that catch humans. The OIDC trust policy string is what actually decides who reaches production. ## Cybersecurity IR Workshop: The workshop you shouldn't miss DevFeed: [Cybersecurity IR Workshop: The workshop you shouldn't miss]() Original publisher: [Read original article]() Author: Microsoft Defender Experts Cybersecurity Incident Response Published: 2026-09-01T18:55:35Z Content type: article Language: en Sources: [Microsoft Security Blog]() Topics: [Incident response](), [incident]() Tags: [cloud](), [cybersecurity](), [dart](), [defender](), [identity](), [incident](), [incident-response](), [logs](), [microsoft](), [resilience](), [security](), [telemetry]() ### AI overview Microsoft's DART describes a scenario-driven incident-response readiness workshop that lets teams test their plans against simulated security incidents. It covers detection, investigation, containment, communication, threat hunting, and the use of tools, logs, and telemetry under pressure. ### Source excerpt Cyber resilience starts before a crisis. Gain practical insights from DART to strengthen readiness and response. The post Cybersecurity IR Workshop: The workshop you shouldn't miss appeared first on Microsoft Security Blog. ## How Android Strongbox and Open Standards Enable the Future of High-Assurance Digital Credentials DevFeed: [How Android Strongbox and Open Standards Enable the Future of High-Assurance Digital Credentials]() Original publisher: [Read original article]() Author: Jason Wong Published: 2026-09-01T12:00:00Z Content type: article Language: en Sources: [Security]() Topics: [Hardware](), [Architecture & Design](), [cross-platform]() Tags: [android](), [android-security](), [compliance](), [cross-platform](), [cryptographic](), [hardware](), [identity](), [none](), [open](), [security]() ### AI overview Android Strongbox uses tamper-resistant hardware, key attestation, and remote key provisioning to support high-assurance digital credentials based on open, cross-platform standards. ### Source excerpt Checking phone to see image of digital credential ## How Identity Federation Empowers Partner API Strategy DevFeed: [How Identity Federation Empowers Partner API Strategy]() Original publisher: [Read original article]() Author: Kristopher Sandoval Published: 2026-09-01T07:00:00Z Content type: article Language: en Sources: [Nordic APIs]() Topics: [API](), [Security](), [Authorization]() Tags: [access-control](), [api](), [api-governance](), [api-integration](), [api-security](), [api-strategy](), [authentication](), [authorization](), [b2b](), [blog](), [governance](), [identity](), [identity-control](), [security](), [strategy]() ### AI overview The article explains how business-to-business identity federation can strengthen partner API security, access control, governance, and identity lifecycle management. It discusses the risks and integration complexity enterprises face when connecting with many partners. ### Source excerpt Business identity is a complex issue rife with risks across the board. Large enterprises often require deep, flexible integrations with dozens or hundreds of partners, but this comes with significant risk -- between the potential for information leakage, concerns around replays or data usage for continued insecure access, and the sheer friction of such a ... [Next page]()