
Chris (Veracode, Inc.) asked a question.

Chris (Veracode, Inc.) asked a question.
Ask the Community
Get answers, share a use case, discuss your favorite features, or get input from the community.
By clicking “Accept All Cookies”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts.
.png)
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Application uploads (binary or source) are stored and transmitted encrypted, using currently-recognized best practices. They are temporarily decrypted only in memory, and only when necessary; they are never stored in the clear.
Uploads are made using TLS, and our TLS configuration is routinely tested to ensure it gets an A+ rating. The uploaded application is then encrypted with a unique AES256 key managed by a commercial key management system.
Our scanning servers temporarily decrypt the binary in memory while it is analyzed, and discard the decrypted binary and local-memory copy of the key the moment they're no longer needed for analysis.
At the end of the customer-defined retention period, the encrypted data is deleted from our systems. The AES key that was used to protect it is then destroyed, preventing access even if the encrypted data were recovered.