What does Cryptosense Analyzer do?
- Discovers and maps the cryptography your applications use.
- Finds crypto-related security flaws in applications and their crypto libraries.
- Shows how to fix these flaws.
- Helps demonstrate cryptographic security to QA, customers and auditors.
How do I use it?
Cryptosense Analyzer deals with traces of cryptographic operations. To make a trace file you attach Cryptosense App Tracer to a running application which records calls to the crypto library. If we want to test the library instead of the application, we use Cryptosense Fuzzer. For many standard libraries, we carry out the testing ourselves at Cryptosense and build the results into the Analyzer.
In both cases the resulting trace file is then uploaded to the Cryptosense Analyzer platform where we apply our proprietary analysis algorithms and analyze the trace against our unique rule base.
Our last 5 deployments averaged 868 instances per application across 9 different findings, with more than 8 findings being classed as high or medium criticality. We found less than 1 false positive.
How can I get Cryptosense Analyzer?
Cryptosense Analyzer is available in SaaS edition or as an on-premise installation. Licensing is by annual subscription, per application. More information on SaaS pricing is available here. For a quote for an on-premise installation please get in touch.
Which APIs do you support?
– Java (JCE/JCA and Bouncycastle low level interface)
– OpenSSL (libssl and libcrypto)
– .NET is in development
How do I know if I need to use Cryptosense Analyzer?
If you’re not sure how much cryptography is in your applications, you can use our (free) Cryptosense Analyzer Static Scanner tool to scan code for calls to crypto functions. It can be used to find out how much cryptography is called in an application, or to evaluate the degree to which a trace recorded by our agents covers all the cryptography in an application.
What types of flaws can Cryptosense Analyzer find?
– Incorrect choice of parameters to cryptographic functions
– Inappropriate combinations of cryptographic operations
– Incorrect use of randomness
– Weak cryptographic keys
– Weak passwords
– Weak password-based key deriviation
– Key management vulnerabilities
– Inappropriate key-lengths and group parameters
– Weak cryptographic algorithms
– Implementation vulnerabilities in cryptographic libraries
I’m not a cryptography expert, will I understand the results?
We provide extensive support and detailed documentation to help you get the most from your analysis. Cryptosense Knowledge Base is a rich source of detailed information about Symmetric and Asymmetric Algorithms, Padding Modes, Cryptographic Attacks and Key Management. Request a demo to see a typical Analyzer output.