Method for automatic storing of malicious samples
The present invention relates to a method for automatically storing malicious samples, comprising collecting input samples from sample providers relating to malwares and goodwares, parsing each of the input samples to extract metadata relating to each of said input sample, adding the metadata relating to each of said input sample in a metadata database, storing each of the input sample in a sample storage, wherein the adding comprises converting the original hashes of each of the input samples to SHA256 hashes according to a hash mapping table operatively connected to the metadata database, and wherein the storing comprises defining the filename of each of the input samples equal to the corresponding SHA256 hash.
1 . A method for automatically storing malicious samples, comprising the steps of:
collecting, by a computerized data processing unit, input samples from sample providers relating to malwares and goodwares;
parsing, by said computerized data processing unit, each of said input samples to extract metadata, including an original hash, relating to each of said input sample;
adding, by said computerized data processing unit, said metadata relating to each of said input sample in a metadata database;
storing, by said computerized data processing unit, each of said input sample in a sample storage;
wherein said adding comprises converting the original hashes of each of said input samples to Secure Hash Algorithm 256 (“SHA256”) hashes according to a hash mapping table operatively connected to said metadata database, and
wherein said storing comprises defining the filename of each of said input samples equal to the corresponding SHA256 hash.
2 . The method for automatically storing malicious samples according to claim 1 , wherein said parsing comprises retrieving as metadata the platform and architecture details for each of said input samples which defines an executable, and
wherein said adding comprises filling the platform and architecture fields of said metadata database with said platform and architecture details.
3 . The method for automatically storing malicious samples according to claim 1 , wherein said parsing comprises retrieving as metadata the malware family details for each of said input samples, and
wherein said adding comprises filling the malware family fields of said metadata database with said malware family details.
4 . The method for automatically storing malicious samples according to claim 1 , wherein said parsing comprises retrieving as metadata the filetype details for each of said input samples, and
wherein said adding comprises filling the filetype fields of said metadata database with said filetype details.
5 . The method for automatically storing malicious samples according to claim 1 , wherein said parsing comprises retrieving as metadata In The Wild (“ITW”) filenames for each of said input samples, and
wherein said adding comprises filling ITW filename fields of said metadata database with said ITW filenames.
6 . The method for automatically storing malicious samples according to claim 1 , wherein said parsing comprises retrieving as metadata the hash details for each of said input samples, and
wherein said adding comprises filling the hash fields of said metadata database with said hash details.
7 . The method for automatically storing malicious samples according to claim 1 , wherein said storing comprises arranging said input sample relating to malwares in a malware sample storage and said input sample relating to goodwares in a goodware sample storage separated from said malware sample storage.
8 . The method for automatically storing malicious samples according to claim 1 , wherein it further comprises updating said hash mapping table at predetermined time intervals.