Pass the Amazon Web Services AWS Certified Specialty SCS-C02 Questions and answers with Dumpstech

what the Security Engineer should do to block the malicious bot. SFTP is a protocol that allows secure file transfer over SSH. EC2 is a service that provides virtual servers in the cloud. A public subnet is a subnet that has a route to an internet gateway, which allows it to communicate with the internet. A brute force attack is a type of attack that tries to guess passwords or keys by trying many possible combinations. A malicious bot is a software program that performs automated tasks for malicious purposes. Route 53 is a service that provides DNS resolution and domain name registration. A DNS sinkhole is a technique that redirects malicious or unwanted traffic to a different destination, such as a black hole server or a honeypot. By modifying the hosted zone in Route 53 and creating a DNS sinkhole for the malicious IP, the Security Engineer can block the malicious bot from reaching the EC2 instance on the public subnet. The other options are either ineffective or inappropriate for blocking the malicious bot.

because this is a solution that can monitor each S3 bucket for unrestricted public write access and use IAM managed services. S3 is a service that provides object storage in the cloud. Systems Manager is a service that helps you automate and manage your AWS resources. You can use Systems Manager to monitor S3 bucket policies for public write access by using a State Manager association that runs a predefined document called AWS-FindS3BucketWithPublicWriteAccess. This document checks each S3 bucket in an account and reports any bucket that has public write access enabled. The other options are either not suitable or not feasible for meeting the requirements.

A bastion host is a special purpose computer on a network specifically designed and configured to withstand attacks. The computer generally hosts a single application, for example a proxy server, and all other services are removed or limited to reduce the threat to the computer.

In IAM, A bastion host is kept on a public subnet. Users log on to the bastion host via SSH or RDP and then use that session to manage other hosts in the private subnets.

Options A and B are invalid because the bastion host needs to sit on the public network. Option D is invalid because bastion hosts are not used for monitoring For more information on bastion hosts, just browse to the below URL:

https://docsIAM.amazon.com/quickstart/latest/linux-bastion/architecture.htl

The correct answer is: Bastion hosts allow users to log in using RDP or SSH and use that session to SSH into internal network to access private subnet resources.

Submit your Feedback/Queries to our Experts

Understand IMDSv2 Metrics:

IMDSv2 adds a layer of security to EC2 instance metadata by requiring a session token.

TheEC2MetadataNoTokenCloudWatch metric tracks the number of calls to IMDSv1.

Enable the IMDS Metrics:

Ensure that the EC2 instances have theDetailed Monitoringfeature enabled to publish metrics to CloudWatch.

Create a CloudWatch Dashboard:

In the CloudWatch console, create a dashboard that displays theEC2MetadataNoTokenmetric for all instances.

Verify Zero Value:

Monitor theEC2MetadataNoTokenmetric. If the value is zero for all instances, it confirms that IMDSv1 is no longer in use.

Secure Access and Validation:

Regularly monitor the dashboard to ensure no instance reverts to using IMDSv1.

Instance Metadata Service (IMDS) Documentation

CloudWatch Metrics for EC2 Instances

AWS Security Best Practices for Metadata Service

B. Amazon Inspector now supports Lambda scanning for vulnerabilities. Designating a delegated administrator provides centralized visibility into findings across the organization.

C. Tag-based suppression enables filtering of findings for non-production resources (e.g., test or dev Lambda functions). By using tags and configuring suppression filters in Inspector, only relevant production findings appear in the dashboard.

This approach provides continuous monitoring, centralized reporting, and filtering based on environment, fulfilling Infrastructure Security requirements.

Q: Which data sources does GuardDuty analyze? GuardDuty analyzes CloudTrail management event logs, CloudTrail S3 data event logs, VPC Flow Logs, DNS query logs, and Amazon EKS audit logs. GuardDuty can also scan EBS volume data for possible malware when GuardDuty Malware Protection is enabled and identifies suspicious behavior indicative of malicious software in EC2 instance or container workloads. The service is optimized to consume large data volumes for near real-time processing of security detections. GuardDuty gives you access to built-in detection techniques developed and optimized for the cloud, which are maintained and continuously improved upon by GuardDuty engineering.

the kms:ViaService condition key can be used to restrict a CMK to work with only a specific AWS service6. By configuring the CMKkey policy to allow KMS actions only when the kms:ViaService condition matches the Amazon S3 service name, you can ensure that only Amazon S3 can use the CMK7. The other options are either incorrect or insufficient for constraining a CMK to work with only Amazon S3.

Restrict Root User Capabilities Using Service Control Policies (SCPs):

SCPs in AWS Organizations provide the ability to control permissions for AWS accounts in the organization.

Create a new organizational unit (OU) and move all member accounts into this OU.

Create SCP for Root User Restrictions:

Define an SCP that denies critical actions likeiam:CreateUser,iam:DeleteUser, or other high-risk actions for the root user. Example SCP:

{

"Version": "2012-10-17",

"Statement": [

{

"Effect": "Deny",

"Action": "*",

"Resource": "*",

"Condition": {

"StringEquals": {

"aws:PrincipalAccountRoot": "true"

}

}

}

]

}

Enforce Multi-Factor Authentication (MFA):

Enable MFA on root accounts for additional security.

Monitor Root User Activity:

Use AWS CloudTrail to monitor and log root user actions. Configure alerts with CloudWatch for any unauthorized root usage.

AWS Organizations SCP Documentation

Best Practices for Root User Account

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