Amazon SCS-C02 Dumps - Pass AWS Certified Security - Specialty (old) Exam in 2026

Centralize Access Management with IAM Roles:

Create roles in the testing and production accounts with permissions specific to resources in those accounts.

Add a policy that allowssts:AssumeRolefor trusted accounts.

Establish Trust Between Accounts:

Update the trust policies of the roles in the testing and production accounts to allow the roles in the development account to assume them.

Example Trust Policy:

{

'Version': '2012-10-17',

'Statement':

[

{

'Effect': 'Allow',

'Principal': {

'AWS': 'arn:aws:iam::<Development-Account-ID>:role/<Role-Name>'

},

'Action': 'sts:AssumeRole'

}

]

}

Role Switching for Access:

Developers in the development account can use the AWS Management Console or CLI to assume the roles in the testing or production accounts.

Advantages of This Solution:

Scalability: No need to create individual credentials for each developer in every account.

Security: Credentials are dynamically assumed and not shared across accounts.

Ease of Management: Centralized role management simplifies permissions and reduces administrative overhead.

Cross-Account Access in AWS

Using Roles to Delegate Permissions

IAM Policies and Trust Relationships

The correct combination of conditions to add to the IAM policy is A and C. These conditions will ensure that IAM users must use MFA to access certain services in the AWS production account, and that each session will expire after 2 hours.

Option A: ''Bool'' : { ''aws:MultiFactorAuthPresent'' : ''true'' } is a valid condition that checks if the principal (the IAM user) has authenticated with MFA before making the request. This condition will enforce MFA for the IAM users to accessthe specified services.This condition key is supported by all AWS services that support IAM policies1.

Option B: ''Bool'' : { ''aws:MultiFactorAuthPresent'' : ''false'' } is the opposite of option A. This condition will allow access only if the principal has not authenticated with MFA, which is not the desired requirement.This condition key is supported by all AWS services that support IAM policies1.

Option C: ''NumericLessThan'' : { ''aws:MultiFactorAuthAge'' : ''7200'' } is a valid condition that checks if the time since the principal authenticated with MFA is less than 7200 seconds (2 hours). This condition will enforce the session duration limit for the IAM users.This condition key is supported by all AWS services that support IAM policies1.

Option D: ''NumericGreaterThan'' : { ''aws:MultiFactorAuthAge'' : ''7200'' } is the opposite of option C. This condition will allow access only if the time since the principal authenticated with MFA is more than 7200 seconds (2 hours), which is not the desired requirement.This condition key is supported by all AWS services that support IAM policies1.

Option E: ''NumericLessThan'' : { ''MaxSessionDuration'' : ''7200'' } is not a valid condition key. MaxSessionDuration is a property of an IAM role, not a condition key. It specifies the maximum session duration (in seconds) for the role, which can be between 3600 and 43200 seconds (1 to 12 hours).This property can be set when creating or modifying arole, but it cannot be used as a condition in a policy2.

This option suggests updating the outbound network ACL for the subnet in us-east-1b to explicitly deny all connections as the first rule, replacing the security group with a new one that only allows connections from a diagnostics security group, and launching a new EC2 instance with diagnostic tools to investigate the suspicious instance. This option will immediately mitigate the attack and provide the necessary tools for investigation.

https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/using-managed-response-headers-policies.html#managed-response-headers-policies-security

The SecurityHeadersPolicy is a managed policy provided by Amazon CloudFront that includes a set of recommended security headers to enhance the security of your website. These headers help protect against various types of attacks, including man-in-the-middle attacks. By applying the SecurityHeadersPolicy to your CloudFront distribution, the necessary security headers will be automatically added to the responses sent by CloudFront. This reduces operational overhead because you don't have to manually configure or manage the headers yourself.

Create an Account-Wide Data Protection Policy:

Use AWS CloudWatch Logs account-level data protection policies to prevent sensitive data exposure.

Define the policy with appropriate AWS managed data identifiers or custom identifiers specific to the company's sensitive data.

Apply the policy across all log groups in the account, ensuring coverage for both existing and future log groups.

Restrict Developer Access to Unmasked Data:

Explicitly deny thelogs:UnmaskIAM permission to developers. This prevents developers from accessing unmasked sensitive data in log entries.

Automatic Policy Application:

Account-wide data protection policies automatically apply to new log groups created in the future, ensuring scalability and compliance without manual intervention.

Testing and Verification:

Test the policy with sample log entries containing sensitive data to ensure proper masking.

Verify that developers can troubleshoot logs without exposing sensitive information.

AWS CloudWatch Logs Data Protection Documentation

AWS Identity and Access Management Permissions for CloudWatch Logs