AWS Control Tower vs. Cisco Umbrella Easy Protect for MSPs

AWS Control Tower is great if you have multiple organizations or disciplines inside a company that needs to be separated for billing purposes or separation of concern. Multiple accounts is part of AWS's well-architected framework and are generally a good idea. AWS Control Tower makes central logging easy which enables those logs to be quickly picked up by a logging tool to provide even more reports and insight. For smaller organizations, AWS Control Tower may seem like an over-engineered solution

Incentivized

If you have a large number of clients that need to access different products within your company it is a good fit. If you just need to protect access within your company, you'd probably just want to look into Cisco Umbrella. The MSP product is specifically tapered to [manage] access from 3rd parties outside of the company.

Incentivized

• AWS Control Tower integrates with AWS organizations
• AWS Control Tower provides Account Factory to provision preconfigured AWS accounts
• AWS Control Tower helps to isolate workloads and billing via AWS accounts separation
• AWS Control Tower supports data residency controls out of the box
• AWS Control Tower supports post provisioning actions to newly provisioned AWS accounts: for example it can trigger enabling VPC flow logs in the new account

Incentivized

• This level of abstraction leaves you vulnerable to not knowing exactly what's been created, and that can enable you to mess things up.
• Because it provisions things on your behalf, you might end up paying for resources you don't need.
• The import process of existing accounts, which we did not end up pursuing, is tedious and manual.

Incentivized

• Analyzing security logs can be challenging as the interface is rather slow and due to the large quantity of logged data.
• It is not always clear why a resource was blocked as there are 2 types of block lists
• Clients sometimes have to re-logon in order to get an updated policy rolled out.

Incentivized

There is no way to easily close an AWS account whether it was created manually or via the AWS Control Tower. It takes too many steps to close it vs to provision a new AWS account

Incentivized

Using AWS Systems Manager and other slightly lower level components has been helpful for us to manage parts of our AWS presence at a more granular level than AWS Control Tower was designed for. It's not at all an apples-to-apples comparison as they solve different use cases, but for us, the use case associated with AWS Systems Manager was a better fit for our specific needs and skillsets. We did not need everything that AWS Control Tower was doing for us.

Incentivized

• AWS Control tower allowed us to drop several third-party vendors for security appliances and logging, which saved us considerable funds.
• AWS Control tower reduced the amount of time we spend deploying AWS accounts.
• AWS Control tower reduced the amount of time we have to spend on quarterly security audits.

Incentivized

• Not always clear which block list caused an access issue. [There are] several places that need to be checked.
• Client policies take a while to get updated, sometimes need to re-logon

Incentivized