# Security Blog Published articles for Security Blog. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Architecting a secure landing zone in the AWS European Sovereign Cloud DevFeed: [Architecting a secure landing zone in the AWS European Sovereign Cloud]() Original publisher: [Read original article]() Author: Pablo Pagani Published: 2026-09-16T21:20:48Z Content type: article Language: en Sources: [AWS Security Blog]() Topics: [Amazon Web Services](), [Cloud](), [Architecture & Design](), [AWS IAM](), [Infrastructure as code](), [CI/CD](), [SIEM, Security](), [Incident response]() Tags: [advanced-300](), [aws](), [aws-identity-and-access-management-iam](), [ci-cd](), [cloud](), [eu](), [europe](), [incident-response](), [infrastructure-as-code-iac](), [partition](), [security](), [security-blog](), [security-identity-compliance](), [technical-how-to]() ### AI overview This article explains how to architect a secure, scalable landing zone in the AWS European Sovereign Cloud. It describes the aws-eusc partition boundary and covers governance, identity, logging, data protection, network design, CI/CD, artifact distribution, and incident response. ### Source excerpt The AWS European Sovereign Cloud is a new, independent cloud for Europe, physically and logically separate from existing AWS Regions and operated within the European Union (EU). It provides the same services, features, and APIs as AWS commercial Regions, but runs as a distinct AWS partition (aws-eusc), with its own control plane, AWS Identity and [...] ## AWS STS simplifies session token size limits and adds session token size monitoring DevFeed: [AWS STS simplifies session token size limits and adds session token size monitoring]() Original publisher: [Read original article]() Author: Rishi Tripathy Published: 2026-09-15T22:21:59Z Content type: release Language: en Sources: [AWS Security Blog]() Topics: [Amazon Web Services](), [Security](), [Monitoring](), [Amazon CloudWatch](), [AWS CloudTrail](), [API]() Tags: [advanced-300](), [amazon-cloudwatch](), [apis](), [aws](), [aws-cloudtrail](), [aws-security-token-service](), [aws-sts](), [infrastructure](), [metrics](), [monitoring](), [security](), [security-blog](), [security-identity-compliance](), [technical-how-to](), [token]() ### AI overview AWS Security Token Service has replaced its separate packed policy and overall session token limits with a single 4,096-byte limit. It now reports session token size and limit utilization in API responses, Amazon CloudWatch metrics, and AWS CloudTrail events. ### Source excerpt AWS Security Token Service (AWS STS) has simplified session token size limits, giving you more room for your session policies and session tags. STS has replaced the packed policy size and the overall session token size limits with a single token size limit of 4,096 bytes. STS now reports session token size in API responses, [...] ## Architecting resilient authentication with Amazon Cognito multi-Region replication DevFeed: [Architecting resilient authentication with Amazon Cognito multi-Region replication]() Original publisher: [Read original article]() Author: Abrom Douglas Published: 2026-09-15T19:00:52Z Content type: tutorial Language: en Sources: [AWS Security Blog]() Topics: [Amazon Cognito](), [Replication](), [Authentication](), [identity and access management](), [Amazon Web Services](), [real-time](), [JSON Web Tokens]() Tags: [advanced-300](), [amazon-cognito](), [authentication](), [aws](), [failover](), [identity-and-access-management](), [real-time](), [replication](), [security-blog](), [security-identity-compliance](), [technical-how-to](), [token]() ### AI overview This AWS article explains how Amazon Cognito multi-Region replication supports resilient authentication by replicating user pools across AWS Regions, with eventual consistency, failover, and interoperable sessions and JSON web tokens. It also covers preparation, architecture decisions, and failover strategies for B2C, B2B, and M2M use cases. ### Source excerpt Your consumer identity and access management (CIAM) system is the foundation of your customer experience. It's how users sign in, access services, and engage with your applications. As your business scales across geographies, ensuring authentication is always available becomes a core architectural requirement. However, building multi-Region authentication has traditionally required complex custom replication solutions that [...] ## Operationalizing least privilege: Automate IAM remediation through your CI/CD pipeline DevFeed: [Operationalizing least privilege: Automate IAM remediation through your CI/CD pipeline]() Original publisher: [Read original article]() Author: Luis Pastor Published: 2026-09-15T15:53:51Z Content type: tutorial Language: en Sources: [AWS Security Blog]() Topics: [AWS Identity and Access Management (IAM)](), [CI/CD](), [Infrastructure as code](), [AWS CloudFormation](), [Amazon Web Services]() Tags: [aws](), [aws-cloudformation](), [aws-cloudtrail](), [aws-iam](), [aws-identity-and-access-management-iam](), [aws-organizations](), [best-practices](), [ci-cd](), [expert-400](), [iam](), [infrastructure-as-code-iac](), [least-privilege](), [pull-request](), [security](), [security-blog](), [security-identity-compliance](), [technical-how-to]() ### AI overview This article describes an automated workflow for operationalizing least privilege in AWS. It explains how AWS IAM Access Analyzer identifies unused permissions and how remediation can be routed through different paths for infrastructure-as-code-managed, manually created, and unused IAM principals. ### Source excerpt The principle of least privilege is straightforward to articulate but challenging to maintain at scale. When teams first deploy applications to AWS, they often grant broader permissions than strictly necessary; it's faster to get things working, and the plan is always to tighten permissions later. But later rarely comes. Permissions accumulate, AWS Identity and Access [...] ## AWS Security Reference Architecture: A deep dive into PCI DSS compliance DevFeed: [AWS Security Reference Architecture: A deep dive into PCI DSS compliance]() Original publisher: [Read original article]() Author: Avik Mukherjee Published: 2026-09-14T17:46:56Z Content type: article Language: en Sources: [AWS Security Blog]() Topics: [Amazon Web Services](), [Security](), [Architecture & Design](), [Network Segmentation](), [Encryption](), [Logging](), [Access Control](), [Cloud]() Tags: [access-control](), [amazon-web-services](), [announcements](), [architecture](), [compliance](), [encryption](), [foundational-100](), [logging](), [network-segmentation](), [pci-dss](), [security](), [security-blog](), [security-identity-compliance]() ### AI overview AWS announces the AWS Security Reference Architecture (AWS SRA) PCI DSS Deep Dive, a guide that extends the core AWS SRA with prescriptive architecture-level guidance for organizations handling cardholder data on AWS. It explains how AWS SRA patterns address PCI DSS concerns including account scoping, network segmentation, encryption, logging, and access control. ### Source excerpt Amazon Web Services (AWS) is excited to announce the publication of the AWS Security Reference Architecture (AWS SRA) Payment Card Industry (PCI) Data Security Standard (DSS) Deep Dive. This new guide extends the core AWS SRA to provide prescriptive, architecture-level guidance for organizations that store, process, or transmit cardholder data on AWS. Organizations subject to [...] ## The state of AI for security: Measuring what matters most for building trust DevFeed: [The state of AI for security: Measuring what matters most for building trust]() Original publisher: [Read original article]() Author: Anshumali Shrivastava Published: 2026-09-09T19:09:14Z Content type: article Language: en Sources: [AWS Security Blog]() Topics: [Cybersecurity](), [Vulnerabilities](), [dataset]() Tags: [advanced-300](), [ai](), [artificial-intelligence](), [benchmark](), [cybersecurity](), [generative-ai](), [machine-learning](), [open-source](), [security](), [security-blog](), [security-identity-compliance](), [thought-leadership](), [vulnerability](), [vulnerability-management]() ### AI overview The article introduces Deception Benchmark, a benchmark for evaluating whether AI models can distinguish real software vulnerabilities from safe code that appears risky. It argues that reducing false alarms is central to making AI security tools trustworthy and compares this focus with existing security evaluations. ### Source excerpt Security teams are starting to actively use AI for security work, including vulnerability triage, penetration testing, threat modeling, incident response, and code review. The promise is speed, but a security tool that moves fast and raises too many false alarms doesn't save time. Engineers spend time on false alarms, on-call is noisier, and teams distrust [...] ## OSPAR 2026 report now available with 167 services in scope DevFeed: [OSPAR 2026 report now available with 167 services in scope]() Original publisher: [Read original article]() Author: James Chang Published: 2026-09-04T18:13:04Z Content type: news Language: en Sources: [AWS Security Blog]() Topics: [Security, Privacy and Abuse Prevention](), [Cryptography]() Tags: [amazon-web-services-aws](), [announcements](), [compliance](), [cryptography](), [financial-services](), [foundational-100](), [security](), [security-blog](), [security-identity-compliance]() ### AI overview AWS completed its annual OSPAR assessment under the OSPAR 2.0 framework. The certification covers 167 AWS services in the Asia Pacific (Singapore) Region and is intended to support customer compliance due diligence. ### Source excerpt We're pleased to confirm the successful completion of our annual Amazon Web Services (AWS) Outsourced Service Provider's Audit Report (OSPAR) assessment on July 29, 2026, in line with the OSPAR version 2.0 framework. The Association of Banks in Singapore (ABS) established the Guidelines on Control Objectives and Procedures for Outsourced Service Providers (ABS Guidelines) to [...] ## Incident response guide for AWS CloudTrail investigations - Part 2 DevFeed: [Incident response guide for AWS CloudTrail investigations - Part 2]() Original publisher: [Read original article]() Author: Oscar Diaz Published: 2026-09-03T21:15:53Z Content type: article Language: en Sources: [AWS Security Blog]() Topics: [Incident response](), [AWS CloudTrail](), [AWS IAM](), [web applications]() Tags: [advanced-300](), [amazon-bedrock](), [aws](), [aws-cloudtrail](), [aws-identity-and-access-management-iam](), [best-practices](), [incident-response](), [security-blog](), [security-identity-compliance]() ### AI overview An incident-response guide for investigating AWS CloudTrail events through a multi-stage attack scenario. It traces an SSRF vulnerability on an EC2-hosted web application to IMDSv1 credential harvesting, IAM activity, and unauthorized Amazon Bedrock access across Regions. ### Source excerpt In Part 1 of this guide, we examined two common incident scenarios: cross-account Amazon Simple Storage Service (Amazon S3) data deletion with ransomware implications, and cryptocurrency mining deployed through AWS CloudFormation using exposed AWS Management Console credentials. We also introduced key incident response terminology and investigative frameworks for analyzing AWS CloudTrail events. In this second [...] ## Incident response guide for AWS CloudTrail investigations - Part 1 DevFeed: [Incident response guide for AWS CloudTrail investigations - Part 1]() Original publisher: [Read original article]() Author: Oscar Diaz Published: 2026-09-03T21:15:39Z Content type: tutorial Language: en Sources: [AWS Security Blog]() Topics: [AWS CloudTrail](), [Incident response](), [AWS IAM]() Tags: [advanced-300](), [analysis](), [aws-cloudtrail](), [best-practices](), [guide](), [incident-response](), [logs](), [security](), [security-blog](), [security-identity-compliance]() ### AI overview A practical guide to investigating suspicious AWS activity through CloudTrail logs. It covers scenarios such as cross-account unauthorized access, cryptocurrency mining, and AI service abuse, with investigation questions, annotated logs, and preventive lessons. ### Source excerpt AWS CloudTrail logs contain the evidence you need when investigating suspicious activity in your AWS environment, but knowing which fields matter and how to interpret them can mean the difference between surface-level analysis and uncovering the full scope of an incident. This guide walks you through real-world scenarios, showing you how to analyze CloudTrail events [...] ## Managing identity source transition for AWS IAM Identity Center DevFeed: [Managing identity source transition for AWS IAM Identity Center]() Original publisher: [Read original article]() Author: Xiaoxue Xu Published: 2026-09-02T20:36:31Z Content type: tutorial Language: en Sources: [AWS Security Blog]() Topics: [migration](), [AWS IAM]() Tags: [advanced-300](), [automation](), [aws-iam-identity-center](), [compliance](), [identity-and-access-management](), [migration](), [security-blog](), [security-identity-compliance](), [technical-how-to]() ### AI overview A walkthrough for safely changing the identity source used by AWS IAM Identity Center, including an Active Directory-to-Okta example. ### Source excerpt September 2, 2026: This post was republished to include Active Directory migration strategies and automation for permission sets. AWS IAM Identity Center manages user access to Amazon Web Services (AWS) resources, including both AWS accounts and applications. You can use IAM Identity Center to create and manage user identities within the Identity Center identity store [...] ## 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 [...] ## We invited a direct competitor into Security Hub Extended. Here's why. DevFeed: [We invited a direct competitor into Security Hub Extended. Here's why.]() Original publisher: [Read original article]() Author: Michael Fuller Published: 2026-08-31T19:00:07Z Content type: opinion Language: en Sources: [AWS Security Blog]() Topics: [AWS Security Hub](), [Security & compliance, Cloud security](), [workload protection](), [vulnerability scanning](), [eBPF](), [Linux Kernel]() Tags: [announcements](), [aws-security-hub](), [cloud-security](), [container](), [ebpf](), [foundational-100](), [linux-kernel](), [security](), [security-blog](), [security-identity-compliance](), [vulnerability-scanning](), [workload-protection]() ### AI overview AWS explains why it invited Upwind, a cloud security competitor, into Security Hub Extended. The post says the partnership responds to customer demand, expands choice between posture management and runtime-first protection, and simplifies integration through AWS billing, support, and operations. ### Source excerpt When customers keep pointing you to a solution that overlaps with parts of your own offering, you have a choice to make. This post is about the choice we made with Upwind, and why we'd make it again. AWS Security Hub Extended exists because customers told us what was working for them in enterprise security [...] ## Automate IAM Identity Center governance with continuous discovery and reporting DevFeed: [Automate IAM Identity Center governance with continuous discovery and reporting]() Original publisher: [Read original article]() Author: Jonathan Nguyen Published: 2026-08-31T17:18:31Z Content type: tutorial Language: en Sources: [AWS Security Blog]() Topics: [AWS IAM](), [CSV]() Tags: [advanced-300](), [authentication](), [aws](), [aws-iam-identity-center](), [aws-organizations](), [compliance](), [iam](), [iam-identity-center](), [identity](), [integration](), [security](), [security-blog](), [security-identity-compliance](), [technical-how-to]() ### AI overview The article explains how to plan identity governance for AWS IAM Identity Center and use an automated discovery and reporting sample solution to track application access assignments across an organization. ### Source excerpt AWS IAM Identity Center integrates with external identity provider (IdP) to provide customers with a centralized authentication and authorization solution for AWS resources across AWS Organizations. AWS continues to invest into IAM Identity Center with a growing number of AWS services that natively integrate with IAM Identity Center. As your AWS organization scales, maintaining visibility [...] ## Extend your data perimeter to the AWS Management Console with Private Access DevFeed: [Extend your data perimeter to the AWS Management Console with Private Access]() Original publisher: [Read original article]() Author: Madhur Kulkarni Published: 2026-08-28T18:53:57Z Content type: article Language: en Sources: [AWS Security Blog]() Topics: [AWS Management Console](), [VPC](), [network security](), [Authentication](), [Amazon Web Services](), [Virtual Private Network](), [Amazon EC2](), [Amazon WorkSpaces]() Tags: [advanced-300](), [authentication](), [aws](), [aws-management-console](), [aws-organizations](), [iam](), [network](), [network-security](), [private-access](), [routing](), [security](), [security-blog](), [security-identity-compliance](), [technical-how-to](), [vpc]() ### AI overview AWS Management Console Private Access is generally available with support for VPCs without internet connectivity. Supported console traffic, including authentication flows, static assets, console-only APIs, and AWS service API calls, can route through VPC endpoints, eliminating the need for an internet gateway, NAT gateway, or public-internet route. ### Source excerpt Organizations in regulated industries such as financial services, government, defense, and healthcare restrict their sensitive workloads to isolated network environments with no access to the public internet. Until now, customers could restrict AWS Management Console access to authorized AWS accounts and corporate networks, but the console itself required internet connectivity. This was creating tension between [...] ## Extend Amazon Bedrock Guardrails to Tool Interactions Using the Strands Agents SDK DevFeed: [Extend Amazon Bedrock Guardrails to Tool Interactions Using the Strands Agents SDK]() Original publisher: [Read original article]() Author: Stephan Traub Published: 2026-08-27T16:20:05Z Content type: tutorial Language: en Sources: [AWS Security Blog]() Topics: [AI Bots](), [AWS IAM]() Tags: [ai-agents](), [amazon-bedrock](), [amazon-bedrock-guardrails](), [artificial-intelligence](), [aws-identity-and-access-management-iam](), [expert-400](), [generative-ai](), [model-context-protocol](), [security-blog](), [security-identity-compliance](), [strands-agents](), [tools](), [validation]() ### AI overview A tutorial on extending Amazon Bedrock Guardrails beyond model prompts and responses to validate AI-agent tool interactions with Strands Agents SDK lifecycle hooks. ### Source excerpt If you're running AI agents in production, Amazon Bedrock Guardrails protects the model boundary. But your agents also invoke tools, fetch external data, and communicate with other systems. That data flows outside the model boundary, where model-level guardrails can't reach. You can extend guardrail coverage to those interactions using three validation checkpoints built with the [...] ## ICYMI: July 2026 @AWS Security DevFeed: [ICYMI: July 2026 @AWS Security]() Original publisher: [Read original article]() Author: Rodolfo Brenes Published: 2026-08-26T19:32:55Z Content type: news Language: en Sources: [AWS Security Blog]() Topics: [Application Security](), [AI-assisted coding](), [AWS IAM]() Tags: [ai-agent](), [ai-coding](), [ai-security](), [amazon-bedrock](), [announcements](), [aws](), [compliance](), [ddos](), [firewall](), [foundational-100](), [iam](), [secrets](), [security](), [security-blog](), [security-identity-compliance]() ### AI overview A July 2026 AWS Security roundup covering AI-agent security, data protection, supply-chain protection, firewall automation, DDoS mitigation, and compliance readiness. ### Source excerpt If you found time for a bit of vacation this summer, you might be in catch-up mode. Here's a list to help: all the expert blog posts, new service capabilities, code samples, and workshops, in case you missed it, from July 2026. AWS Security Blog post This month's AWS Security Blog posts covered AI agent [...] ## Detecting multi-stage attacks on AWS: A guide to cross-service signal correlation DevFeed: [Detecting multi-stage attacks on AWS: A guide to cross-service signal correlation]() Original publisher: [Read original article]() Author: Nisha Kashyap Published: 2026-08-26T17:39:19Z Content type: article Language: en Sources: [AWS Security Blog]() Topics: [Amazon Web Services (AWS)](), [Security](), [Detection engineering](), [Amazon CloudWatch Logs](), [AWS CloudTrail](), [VPC Flow Logs](), [Amazon S3](), [data]() Tags: [advanced-300](), [amazon-cloudwatch](), [amazon-cloudwatch-logs](), [amazon-guardduty](), [amazon-route-53](), [amazon-web-services-aws](), [analysis](), [aws-cloudtrail](), [aws-security-hub](), [best-practices](), [cybersecurity](), [guide](), [incident-response](), [logs](), [s3](), [security](), [security-blog](), [security-identity-compliance](), [shared-responsibility-model](), [technical-how-to](), [threat-detection](), [vpc-flow-logs]() ### AI overview This article explains how security engineers can detect multi-stage attacks on AWS by correlating signals across services with business context. It presents examples using CloudWatch Logs Insights and discusses expanding the correlations into an automated pipeline. ### Source excerpt A single alert from one security service tells you something happened. Read that signal alongside activity from other services and your own business context, and you will know whether what happened is part of a multi-stage attack. Consider a short sequence. An identity calls GetCallerIdentity from a source address it hasn't previously used. Within minutes, [...] ## Fast Track ISM-ready cloud environments and IRAP Assessments with Landing Zone Accelerator on AWS DevFeed: [Fast Track ISM-ready cloud environments and IRAP Assessments with Landing Zone Accelerator on AWS]() Original publisher: [Read original article]() Author: Kevin Donohue Published: 2026-08-25T21:53:49Z Content type: article Language: en Sources: [AWS Security Blog]() Topics: [Security & compliance, Cloud security](), [Amazon Web Services](), [Cloud](), [Security](), [Deployment](), [configuration](), [Critical Infrastructure]() Tags: [announcements](), [architecture](), [australia](), [aws](), [cloud](), [cloud-security](), [compliance](), [critical-infrastructure](), [deployment](), [foundational-100](), [governance](), [government](), [infrastructure](), [irap](), [public-sector](), [security](), [security-best-practices](), [security-blog](), [security-identity-compliance]() ### AI overview This AWS security post announces an independent assessment report on Landing Zone Accelerator on AWS (LZA). It explains how LZA can automatically deploy multi-account AWS environments with coverage for Australian Government Information Security Manual (ISM) security controls, and describes configuration-drift testing and compliance documentation intended to support IRAP assessment readiness. ### Source excerpt This post announces the availability of a new independent assessment report available on AWS Artifact analyzing how Landing Zone Accelerator on AWS (LZA) can automatically deploy multi-account environments in Amazon Web Services (AWS) with Australian Government Information Security Manual (ISM) security controls coverage at scale. The report includes findings from an independent third-party analysis conducted [...] ## AWS Network Firewall now supports rule hit count DevFeed: [AWS Network Firewall now supports rule hit count]() Original publisher: [Read original article]() Author: Preetkumar Shah Published: 2026-08-20T18:40:20Z Content type: article Language: en Sources: [AWS Security Blog]() Topics: [Firewall](), [Amazon Web Services](), [Amazon CloudWatch Logs](), [Network](), [Security](), [Amazon S3](), [log management](), [Incident response]() Tags: [amazon-cloudwatch](), [amazon-cloudwatch-logs](), [amazon-s3](), [announcements](), [aws](), [aws-network-firewall](), [compliance](), [firewall](), [incident](), [incident-response](), [intermediate-200](), [logs](), [network](), [s3](), [security](), [security-blog](), [security-identity-compliance](), [storage]() ### AI overview AWS Network Firewall now provides rule hit counts for stateful rules, using alert-log data to show how often rules match network traffic. The feature helps teams identify unused rules, support incident response, and demonstrate security-control effectiveness for compliance. ### Source excerpt As firewall rule sets grow in complexity, security teams face a common challenge: manual log analysis is used to determine which rules are actively matching traffic and which are consuming capacity without being triggered. This lack of visibility creates operational and compliance gaps. Organizations with governance policies that require removal of dormant rules after a [...] ## Propagate user authorization context in AI agents with Amazon Bedrock AgentCore DevFeed: [Propagate user authorization context in AI agents with Amazon Bedrock AgentCore]() Original publisher: [Read original article]() Author: Anshu Bathla Published: 2026-08-19T17:24:15Z Content type: article Language: en Sources: [AWS Security Blog]() Topics: [Amazon Bedrock AgentCore](), [AI Agent](), [Authorization](), [AWS Identity and Access Management (IAM)](), [Amazon Bedrock Knowledge Bases](), [Amazon DynamoDB](), [Amazon S3](), [prompt injection](), [Amazon Web Services](), [Software as a service]() Tags: [access-control](), [advanced-300](), [ai-agents](), [amazon-bedrock](), [amazon-bedrock-agentcore](), [amazon-bedrock-knowledge-bases](), [amazon-dynamodb](), [amazon-s3](), [artificial-intelligence](), [authorization](), [aws](), [prompt-injection](), [security-blog](), [security-identity-compliance](), [technical-how-to]() ### AI overview This article explains how to propagate user authorization context through AI agents built with Amazon Bedrock AgentCore. It presents a pattern for enforcing least-privilege access in downstream data services and infrastructure, so agents can access DynamoDB, Bedrock Knowledge Bases, S3-backed documents, and other sources only within the requesting user's permissions. ### Source excerpt Many teams now deploy AI agents that pull from Amazon DynamoDB tables, document repositories, software as a service (SaaS) platforms, and internal knowledge bases to answer questions and automate workflows. A key risk in these deployments is that the agent has no awareness of who's asking, so it might return data the user shouldn't see. [...] ## Implement custom authentication for tools integration using request Lambda interceptor in AgentCore Gateway DevFeed: [Implement custom authentication for tools integration using request Lambda interceptor in AgentCore Gateway]() Original publisher: [Read original article]() Author: Nishant Mainro Published: 2026-08-18T20:46:26Z Content type: tutorial Language: en Sources: [AWS Security Blog]() Topics: [Amazon Bedrock AgentCore](), [Amazon Bedrock](), [AI Agent](), [Security](), [IAM](), [Model Context Protocol](), [OAuth 2.0](), [Architecture & Design](), [JSON Web Tokens]() Tags: [advanced-300](), [ai-agents](), [amazon-bedrock](), [amazon-bedrock-agentcore](), [artificial-intelligence](), [aws-identity-and-access-management-iam](), [aws-lambda](), [model-context-protocol](), [oauth](), [prompt-injection](), [secrets](), [security](), [security-blog](), [security-identity-compliance](), [technical-how-to]() ### AI overview This tutorial explains how to use a request Lambda interceptor in Amazon Bedrock AgentCore Gateway to support legacy Basic Authentication for downstream tool APIs. The interceptor retrieves service credentials from AWS Secrets Manager and constructs the authentication header while keeping credentials isolated from the AI agent. The article also describes the inbound MCP request flow and cautions that Basic Auth should be treated as an interim measure, with modernization toward OAuth 2.0, SAML, OpenID Connect, or IAM recommended. ### Source excerpt When deploying AI agents with Amazon Bedrock AgentCore, organizations benefit from built-in modern support for OAuth 2.0, AWS Identity and Access Management (IAM), and API key authentication through Amazon Bedrock AgentCore Gateway. However, some enterprise environments still use legacy authentication mechanisms such as HTTP Basic Authentication (Basic Auth) (RFC 7617). The extensible architecture of AgentCore [...] ## Security Hub Extended adds Supply Chain Security as its tenth category DevFeed: [Security Hub Extended adds Supply Chain Security as its tenth category]() Original publisher: [Read original article]() Author: Michael Fuller Published: 2026-08-18T17:04:28Z Content type: news Language: en Sources: [AWS Security Blog]() Topics: [supply-chain-security](), [Security](), [Amazon Web Services]() Tags: [amazon-web-services-aws](), [announcements](), [aws](), [aws-security-hub](), [black-hat](), [engineering](), [enterprise](), [foundational-100](), [leadership](), [open-source](), [partners](), [payment](), [pricing](), [security](), [security-blog](), [security-identity-compliance](), [software](), [streaming](), [supply-chain](), [supply-chain-security](), [uncategorized](), [vulnerability]() ### AI overview AWS Security Hub Extended adds Supply Chain Security as its tenth category, with Chainguard and Socket as curated partners. The article frames software supply-chain risk as an enterprise security concern and describes pay-as-you-go and private-offer procurement options. ### Source excerpt Since February, we've grown AWS Security Hub Extended from 14 curated partners across 9 categories to 23 partners across 10. At Black Hat this month, 14 of those partners were at the Amazon Web Services (AWS) booth demoing live. Four of those partners delivered theater talks and ten were featured on SecurityLive streaming. We hosted [...] ## Updates to your AWS Sign-In experience DevFeed: [Updates to your AWS Sign-In experience]() Original publisher: [Read original article]() Author: Vaibhav Chowla Published: 2026-08-17T17:22:33Z Content type: release Language: en Sources: [AWS Security Blog]() Topics: [Amazon Web Services (AWS)](), [AWS IAM](), [identity and access management](), [AWS IAM Identity Center](), [browser]() Tags: [amazon-web-services-aws](), [aws](), [aws-iam](), [aws-iam-identity-center](), [aws-identity-and-access-management-iam](), [browser](), [identity-and-access-management](), [intermediate-200](), [scripted](), [security-blog](), [security-identity-compliance](), [uncategorized](), [updates]() ### AI overview AWS is gradually introducing a redesigned sign-in and sign-up experience to a limited number of customers. The changes add new account access options, unify the initial email entry point, and refresh the session selection page while existing customers continue using their current credentials and sign-in methods. ### Source excerpt Amazon Web Services (AWS) is gradually introducing updates to the AWS Sign-In and sign-up experience to a limited number of customers. We're sharing these changes so you will know what to expect as we gradually make the updated experience available to more customers. These updates include new options for creating and accessing AWS accounts. To [...] ## AWS Certificate Manager will discontinue email validation to prove domain validation for certificates DevFeed: [AWS Certificate Manager will discontinue email validation to prove domain validation for certificates]() Original publisher: [Read original article]() Author: Adam Aboudi Published: 2026-08-13T21:23:00Z Content type: article Language: en Sources: [AWS Security Blog]() Topics: [AWS Certificate Manager](), [Amazon Web Services](), [Command-line interface]() Tags: [announcements](), [aws](), [aws-certificate-manager](), [aws-management-console](), [blog](), [cli](), [dns](), [foundational-100](), [security-blog](), [security-identity-compliance](), [validation]() ### AI overview AWS Certificate Manager will discontinue support for email-validated public certificates by September 30, 2027. Customers using email validation must migrate to DNS validation, ahead of the CA/B Forum's March 15, 2028 deadline. The article explains the rationale, timeline, and how to identify affected certificates in the ACM console or AWS CLI. ### Source excerpt Today, we're announcing that AWS Certificate Manager (ACM) will discontinue support for email-validated public certificates by September 30, 2027. If you use email validation for your ACM public certificates, you need to migrate to DNS validation before that date. This change aligns with the Certification Authority/Browser (CA/B) Forum's industry-wide deprecation of email-based domain validation and [...] [Next page]()