Armor vs Metasploit

• Security - we have requirements met right out of the box and the implementation of new resources is done with security in mind.
• Speed - We can scale resources easy and the infrastructure is fast and efficient.
• Responsiveness - Support tickets are handled very fast with almost immediate solutions.

Read full review

• Scanning our network for new or existing vulnerable systems.
• Automation of manual tests and exploits to allow what used to be days of effort to be squeezed into hours.
• Metasploit has become an integral part in our validation of new systems before their inclusion in our production network.

Read full review

• Authentication and access against the secure messaging portal is overkill when the response I'm logging in to see merely says, "yes, we have your message. An agent will respond shortly". There should be an option to receive updates like this through email.
• The online portal that allows us to clone servers is very slow to respond. More than once I've spun up an additional server due to the lack of visual feedback on the initial request.
• The web application firewall does not seem to be sophisticated enough to differentiate between logged in administrators and end users. We use a CMS system which allows admins to create scripts. These often get barred by the WAF even though they are not malicious.

Read full review

• Have encountered issues with updating especially after moving from BackTrack to Kali.
• Sometimes it gets a little buggy, but that's a rare occurrence.

Read full review

• We have been able to weed out false positives with a more manual vetting of scanned vulnerabilities.
• Our teams have become more well versed in penetration testing with Metasploit to understand the vulnerabilities potentially present.

Read full review