Credential reports aren't working as expected
I am a new analyst in an organization that uses RDM. I've been trying to audit the credentials stored in RDM for password duplicates. To that end, I have tried using the built-in reports, and I find that none of them are giving me the information I need.
The Credential entry references report seems not to account for credentials stored in other entry types.
The duplicate entry list does not specify which criteria is used to determine the duplication. It does not seem to detect duplicate strings in any field, but rather compare full entries.
The entry list does not display credential columns, so that's also impossible to use.
Did I miss any feature or function that would enable me to conduct my audit of credentials in my organization?
All Comments (2)
Hello,
Thank you for the detailed breakdown of what you have already tried. Your assessment of the built-in reports is correct: there is no existing report in Remote Desktop Manager that performs a cross-entry-type duplicate password audit the way you are describing.
To summarize the limitations you found:
- Credential entry references report only maps where dedicated Credential-type entries are referenced elsewhere. It does not inspect passwords stored directly on other entry types (RDP, SSH, Database, etc.).
- Duplicate entry report compares entire entries rather than individual fields, and its matching criteria are not documented, which is why it does not behave like a password-comparison tool.
- Entry list report is intended as a simplified, hyperlinked index of entries and does not expose credential columns.
One report you may not have tried yet is the Entry security analyzer (Reports, or the Tools tab), which scores each stored password individually for strength and can flag passwords exposed in known breaches. However, it evaluates passwords in isolation and does not cross-reference values between entries, so it will not surface reused passwords either.
At this time, there is no built-in feature that performs the audit you need. The recommended approach is to use the Devolutions.PowerShell module to enumerate all entries regardless of type, retrieve their stored passwords, and compare them programmatically (for example, grouping by password value or hash) to identify duplicates across your data source.
Let us know if you would like guidance on building that PowerShell audit script.
Best regards,
Carl Marien
@Carl Marien yes please, I would love to build a Powershell script to speed up this process. Do you have any KB I can refer to? Many thanks!