Hello Guys,
I have already deployed Symantecav parser in my decoder, But however hash file(SHA 256,SHA 1 ,MD5) are not yet parsed in pre-defined parser.
In symantecav parser I could see that sha256,sha1& MD5 are mapped as dummy variable, May I Know why sha files mapped as dummy variable.
If I have write a parser mapping manually ,it will affect my efficiency or else cpu utilization of decoder.
Kindly help suggest me on the same.
Thanks&Regards,
Suresh K
Hello Ankush,
Yes your right, Md5 hash meta key alone already parsed under checksum, what about sha 1& sha 256 hashes?
My question was in pre-defined Symantecav parser why sha1,sha256& MD5 hashes were mapped under dummy variable. Kindly explain on this query
I cant able to share the logs -> Highly confidential.
Thanks,
Suresh K
The log sample I tested had SHA-1 hash value and I see that is parsing correctly in "checksum” meta, so you may want to check if you are using the latest parser or not.
If you are using latest parser and still have issues, then your logs might be a different format from the one I am testing..
Since you are not able to share the logs here, so I would suggest to open a case with support for parser update or use the Log Parser Tool to add support for the same.
LPT is a easy to use tool. Here are some video links to LPT which I have found useful:
Sadly I don't have any sample log which has SHA-256 hash to test, however the most important thing at this point ( and there a few more about storage and indexing) to note is that -:
Since SHA-256 hash is 256 characters long and any single meta can only store maximum 255 characters, so adding SHA-256 hash into a single meta key (like checksum) will truncate after 255 chars. And if you usecase/rule/logic/alert is somewhat like matching SHA-256 hash with an external threat intel, then without the last character it might not be very useful.
Hello Ankush,
checksum meta key dedicatedly mapped for "ir.md5" met kay then how did you map the both md5 and sha1 in single meta key as checksum.
Kindly help me on the same.
Thanks,
Suresh K
you can customize your parser with the following by modifying just the event that you need to modify from the OOTB parser
An example is here
How To Customize a Log Parser - LOGBinder Example
which event id are these messages coming from so we can take a look at the matching parser event from the RSA GitHub site and see where you think the dummy variable is coming into play.
Based on the sample logs i had, i can see that hash values are parsed in "checksum" meta.
Can you share the sample log by exporting from GUI and we can check this further?
Regards
Ankush