AWS Control Tower vs. Morphisec

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

In order to have a clean work area and operating system, it is essential to have the reinforcement of a program that is effective in eliminating each of the threats that constantly appear in each of the projects. Morphisec Guardb is the perfect ally that we recommend to maintain a serenity and digital stability.

Incentivized

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

Incentivized

• Stops ransomware attacks in a unique fashion before they can infect and spread in an environment.
• Works flawlessly so far with our additional security tools and platforms.
• Has a very small footprint as an application so does not interfere with day to day operations on our endpoints.

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

• Has a lot of false alerts.
• Limited support for VDIs.

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

Morphisec won out in our search for strong protection against ransomware and zero-day attacks by offering a unique approach to preventing them, to begin with. There were some additional offerings that did some things very well themselves, but in the end, it came down to a few things Morphisec seemed to be the best in our research at least. Those things included how it specifically protected against ransomware and zero-day attacks, the small footprint it needs to run, and it's ability to just slot into our environment and allow us the flexibility to continue using our current XDR and NextGenAV platforms as well.

Incentivized

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

Incentivized

• One of the biggest and best features that this program implemented in my work area is the efficiency and security of trusting to be the main user to carry out the most important jobs in my company.
• Morphisec Guard was created with the intention that each company, regardless of its content, can work without having to deal with different types of attacks and threats that destroy the development of my work.

Incentivized