By using AWS re:Post, you agree to the Terms of Use
/Best practices to deploy GuardDuty, Macie, Sec Hub and Config in a Multi-account environment?/

Best practices to deploy GuardDuty, Macie, Sec Hub and Config in a Multi-account environment?

1

In a multi-account environment w/ AWS Organizations enabled - what are the best practices for deploying/enabling GD, Macie, Sec Hub?

  • how to enable the services (stacksets, pipeline, orgs)
  • what roles/SRLs are optional (comply w/ least privilege)
  • how to handle finding aggregation
  • recommendations for upkeep of services
  • gotcha's to look out for
5 Answers
3

hi, I'd strongly recommend 2 AWS whitepapers exactly providing answers to your various questions:

  1. AWS Security Reference Architecture: https://d1.awsstatic.com/APG/aws-security-reference-architecture.pdf
  2. Organizing Your AWS Environment UsingMultiple Accounts: https://docs.aws.amazon.com/whitepapers/latest/organizing-your-aws-environment/organizing-your-aws-environment.pdf#organizing-your-aws-environment
answered 7 months ago
1

AWS released "Best practices for setting up your multi-account AWS environment." See: https://aws.amazon.com/blogs/mt/best-practices-for-organizational-units-with-aws-organizations/ . In addition, AWS recently released (11/18/2021) nested organization units (making account implementation of security controls easier). See: https://aws.amazon.com/about-aws/whats-new/2021/11/aws-control-tower-supports-nested-organizational-units/

answered 7 months ago
  • Nested OUs were released for environments governed by AWS Control Tower in 11/2021, they have previously been available natively for all organizations.

1

This blog post also may be useful - it covers some key best practices for enabling and managing (inc. the management of access to) Security Hub and how to integrate with other services such as Guard Duty: https://aws.amazon.com/blogs/security/nine-aws-security-hub-best-practices/

answered 7 months ago
0

In addition to all of the other comments (which you should definitely refer to the security architecture), there's two common principles that are recommended for all organizations. (1) Enable AWS security services at the organization level. This allows the services to view findings new accounts as they are added to your organization. (2) Set a single security account as the delegated administrator for your security services. This allows your security team access to findings across your org from all of the security services outside without needing to use the management account.

answered 7 months ago
-1

There's a lot packed in that question. 

I would advise you to look into Control Tower to manage and govern your multi-account environment. 

https://aws.amazon.com/controltower 

To extend Control Tower with Pipelines, look at Customization for Control Tower. 

https://aws.amazon.com/solutions/implementations/customizations-for-aws-control-tower/ 

Between these two solutions, you have a powerful way of governing and securing your mult-account environment. 

With respect to GuardDuty, SecurityHub and Macie, enable them in Organization for all accounts. 

Organizations should be set up in your Management (formerly Master) account. 

Findings should be sent downstream to a SEIM solution. 

With respect to what roles are "optional", it all depends what you have in mind for those roles. In general, the goal should be to keep the grubby, human fingers out of the environment, which can be achieved using pipelines.

answered 7 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions