Thanks @Nagaraj. This type of post makes it much easier for others in the community to help you out.
@JasonWalker is correct. Just because you can see it installed on a machine, doesn’t mean it is part of the Software Catalog from HCL.
A cursory search of the Software Catalog shows 50 entries for Tripwire Enterprise. Looking into the Software Products & Metric report finds three versions of the Tripwire Enterprise Agent, with version 8 being the newest.
There are 10 signatures for this version or it’s descendants, 6 of these are for UNIX - version 8.0 to 8.5.
I cannot see what version you have in the computer report, but a reasonable possibility is that you are running a version newer than 8.5.
The signature for version 8.5 on UNIX is:
<MultipleInstance><Iterator name="INSTALL_PATH" export="true"><Vector filter="*agent?bin?" ignoreCase="true"><FindFilePathEx name="twdaemon"/></Vector></Iterator><Instance><Variable name="IS_INSTALLED"><PackageInfoMatch vendor="Tripwire*" name="TWeagent" version="8.5*"/></Variable><Condition withVariable="IS_INSTALLED"><Action onValue="false" do="SKIP"/></Condition></Instance></MultipleInstance>
The scanner is looking for the presence of twdaemon and an RPM package from vendor whose name starts with Tripwire, called TWeagent, with a version that starts with 8.5.
Having found the signature, you can go to the machine to investigate how it was installed and see where the disconnect comes from.