Explanation:
AWS Security Hub provides a central view of security alerts and compliance status across AWS accounts. When integrated with AWS Organizations, you can designate an administrator account that can automatically enable Security Hub for all existing and future member accounts in the organization. Security Hub natively supports the CIS AWS Foundations Benchmark, making it the most operationally efficient solution. Amazon Inspector is for software vulnerabilities and unintended network exposure, and GuardDuty is for threat detection, not compliance benchmarking.
Ultimate access to all questions.
Question #17\n\nA company manages a set of accounts on AWS by using AWS Organizations. The company's security team wants to use a native AWS service to regularly scan all AWS accounts against the Center for Internet Security (CIS) AWS Foundations Benchmark. What is the MOST operationally efficient way to meet these requirements?
A
Designate a central security account as the AWS Security Hub administrator account. Create a script that sends an invitation from the Security Hub administrator account and accepts the invitation from the member account. Run the script every time a new account is created. Configure Security Hub to run the CIS AWS Foundations Benchmark scans.
B
Run the CIS AWS Foundations Benchmark across all accounts by using Amazon Inspector.
C
Designate a central security account as the Amazon GuardDuty administrator account. Create a script that sends an invitation from the GuardDuty administrator account and accepts the invitation from the member account. Run the script every time a new account is created. Configure GuardDuty to run the CIS AWS Foundations Benchmark scans.
D
Designate an AWS Security Hub administrator account. Configure new accounts in the organization to automatically become member accounts. Enable CIS AWS Foundations Benchmark scans.
E
None of the above
F
Not Applicable
No comments yet.