AWS Control Tower vs. Cloud Storage Security vs. Netskope CASB

We were wanting to prove the concept of a low touch process for quickly spinning up boilerplate AWS environments. We were able to get started quickly and to ensure that the AWS Well-Architected Framework principles were followed - at least upfront - however, we found that for our use case and expertise level it ultimately wasn't a fit. We have the skills on our team to manage more of this on our own. My recommendation would be contingent on what skills are already available on your team: if you can "do it yourself" you might as well so that you don't pay for resources you don't need and you have finer grain control over what's created.

Incentivized

The Netskope CASB solution is well-suited for any company due to the proliferation of SaaS applications. With the agent being installed on endpoints, the product is well suited for remote work environments where a managed corporate network may not be available. The agent allows visibility and controls to be applied to any networks the devices connect to.

• Easily create new AWS accounts.
• Easily secure and manage AWS accounts.
• Landing zone with SSO is a huge win for larger teams.

Incentivized

• Policies against integrated SaaS applications.
• Visibility into cloud applications usage and risk.
• Cloud Confidence Index (research into security confidence of providers).

Incentivized

• The AWS SSO GUI is not very intuitive and determining how to apply policies to users without creating redundant logins has been a challenge.
• The default guardrails do not fully encompass all the security checks that we needed.
• There does not appear to be any way to control roles at the IAM level from the control tower account through the GUI.
• Some features on AWS accounts still require logging into the individual account with the root user and cannot be done from AWS Control Tower.

Incentivized

• Public IP for user can be from different country then it came from
• Sometimes you can't get anywhere with Netscope ON
• Location is the key for speed so users complain for speed of 'internet'
• Some location blocks Netscope IP ranges

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

Really easy to use for administrators and for end users, as all is unified in one single agent. Management and deployment is also very easy to do, so overall it is a user and administrator friendly product.

Incentivized

There have been some struggles with their infrastructure keeping pace with demand and load. Support can only do so much and has to defer to known problems being escalated.

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 felt that Netskope provided a more holistic view in the CASB space from a user and usage perspective. In addition, the cost structure for Menlo was a bit higher and was a bit more complicated in the installation and maintenance perspectives

Incentivized

• Less time manually deploying accounts which was error prone.
• Central logging allowed us to have 1 place to view logs.

Incentivized

• ROI is difficult to quote but protection against threat is biggest ROI for any company
• Confidential data is governed at micro level
• Upload/download of documents even to unwarranted sites like pdf convertor is blocked

Incentivized