An enterprise is improving the security posture of an existing internal administration portal hosted in a Shared Services VPC. The application runs on Amazon EC2 instances behind an internal Application Load Balancer (ALB). Users access the portal from the on-premises network via an AWS Transit Gateway connected to an AWS Direct Connect gateway. Remote administrators must also access the portal, authenticating via an external OpenID Connect (OIDC) identity provider. The security team wants to prevent DNS exfiltration from the EC2 instances and ensure that remote administrator access is restricted to corporate-approved devices. Which of the following actions should the Solutions Architect recommend? (Select TWO.)
- Associate a Route 53 Resolver DNS Firewall rule group with the Shared Services VPC to block DNS queries for known exfiltration domains and non-approved external domains.Cevap
- Configure the internal ALB listener rule to authenticate remote administrators directly using OIDC with the external IdP, and configure the backend application to validate the authentication tokens and device claims.Cevap
- CAttach a Service Control Policy (SCP) to the Shared Services organizational unit (OU) that grants the sts:AssumeRoleWithWebIdentity API action to remote administrators, allowing them to bypass local IAM trust policy requirements.
- DDeploy AWS WAF on the internal ALB, placing a general allow rule for partner networks at priority 10, followed by specific block rules for unauthorized client IP ranges and SQL injection patterns at priority 20 and 30.
- EConfigure the application to encrypt administrator session state files in an Amazon S3 bucket using the AWS-managed KMS key (aws/s3), and modify the bucket policy to delegate cross-account KMS decrypt permissions to the remote administrators' account.
Cevap
Associate a Route 53 Resolver DNS Firewall rule group with the Shared Services VPC to block DNS queries for known exfiltration domains, and configure the internal ALB listener rule to authenticate remote administrators directly using OIDC with the external IdP while verifying device claims in the application.
The correct actions are to associate a Route 53 Resolver DNS Firewall rule group with the Shared Services VPC to block DNS exfiltration and configure the Application Load Balancer (ALB) to perform OIDC authentication for remote administrators, passing the verified claims to the backend application. Route 53 Resolver DNS Firewall filters outbound DNS queries to block unauthorized domains, satisfying the network security requirement. ALB OIDC integration offloads federated authentication securely, allowing the application to enforce device compliance by checking the ID token claims.
Adım Adım Çözüm
Anahtar Kavram
Strengthening network and identity security using Route 53 Resolver DNS Firewall, Application Load Balancer OIDC integration, and avoiding common misconfigurations in AWS SCPs, AWS WAF rule priorities, and KMS key types.