AWS Control Tower vs. Tenable Cloud Security

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

In its current version, it is basic. There are nice new features that should provide a good overall picture of the configuration and security of the account.

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

• Easy to connect to cloud account
• Provides basic configuration details or account, networking, what's public

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

• Difficult to attribute the vulnerabilities to the correct instance - cloud is too dynamic. Is supposed to be fixed in new version - we will see.

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

We looked at this over a year ago, the space was still young. Censys provided what we originally needed, but was soon outdone by Tenable with their initial release. I am sure that Censys improved as well, but it was easier to expand on our current Tenable license.

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

• Being a Tenable One customer - these are just new features we suddenly own. As long as you have the asset count available

Incentivized