Absent Member.
Absent Member.

How does the MD5 hashing work with the obfuscation of SmartConnector fields?


I plan to use field-based obfuscation on their custom Smart/FlexConnector to hash private data that should not be displayed. But I'm not comfortable with using this until I understand how the MD5 hashing itself works.

Does anyone have any information as to how the obfuscation works? Is it a straight MD5 translation, or is salt added to the hash? At which point does the data become hashed, from an architectural standpoint? Does the data become hashed before being sent out across the wire from the smartconnector to the destination (ESM/logger/etc)?

Would you consider this to be a secure method of obfuscating private data to create a unique identifier within ArcSight, yet keep the original data protected against reverse hashing?

Labels (4)
0 Replies
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.