AWS Identity & Access Management vs. SecurID

AWS Identity & Access Management is well suited to managing AWS application access between services. Very helpful for both third-party products and in-house developed software. Very happy with how easy it is to create access keys and then share them in our environment. AWS IAM can also be used to manage individual users, but I highly recommend using AWS SSO for that purpose instead. Much easier to deploy for console access and from a security side easier to turn off in one click from your SSO provider.

Incentivized

Easy to implement and support. Flexible platforms and user-friendly interface. Not a lot of customization is available to customers and response time of support could be better. There are now competing products that utilize new features like facial recognition. Using camera and fingerprint sensors are becoming standard in smartphones so RSA SecureID should offer those as options.

Incentivized

• Customized access per key to limit scope
• Safely distributes access keys
• Provides access audits

Incentivized

• RSA Authentication Manager is easy to deploy and configure.
• It is a scalable solution meant for a large enterprise.
• Some of the key features of RSA Authentication Manager where it particularly does well are provisioning, mapping, and logging.
• It has a very nice console with good administrative and troubleshooting options.
• Reliable security for VPN, applications, and wifi.

Incentivized

• Better integration with roles and policies so you don't need three windows open to create a new IAM user
• Display recommended configurations based on services being used
• Easier options to base config on existing users

Incentivized

• Slow to provide updates to latest operating system versions.
• While the GUI is clean and easy to use, it does look very dated.
• There is not an option for a temporary code to log in. It would be nice for situations where you are at a remote site but don't have your device (laptop, phone, etc.) with you, as well as other situations.

Incentivized

We would be unable to manage the interconnected nature of our AWS services without AWS IAM.

Incentivized

Long story short, does the job. Can use company credentials to setup and access the account for SecurID. Easy to setup and implement. Doesn't have a high learning curve.

Incentivized

Using it very frequently, it's important that its straight forward and I do not have to go through unnecessary hoops to achieve something seemingly simple. Can setup using the company credentials and do not have to setup up a separate account. Setup was fast and easy. GUI is very straight forward and quick.

Incentivized

Their support for onboarding and set-up is quite good. The only issues we tend to have are obtaining new user devices. These need to be planned ahead of time.

Incentivized

While we do not use Microsoft Azure for our servers and other customer-facing services. If we did, we would have to use Microsoft Azure Active Directory to manage access to services appropriately. It's difficult to quantify the differences between the services as they are truly different. I would recommend choosing AWS or Azure, then using the identity management provided by the same vendor.

Incentivized

Overall MS AAD is good but we have had a few too many reliability issues with the product that have lead to enterprise authentication outages over the last year. The Senior executives have a preference on Securid to be more reliable than MS AAD. SecurID does a better job in Integration for legacy on-premise applications for instance.

Incentivized

• Without IAM, it would be difficult to use AWS across services. Increased ROI

Incentivized

• Implementing RSA SecurID has allowed us to help our clients understand we are committed to compliance.
• Implementing RSA SedcurID has, however, negatively impacted employee productivity. Employees need to be aware of the additional steps they need to take to authenticate to a protected system.
• RSA SecurID has helped us with our compliance audits.

Incentivized