See here for product details.
Much of the information required for the reports is extracted from audit log messages generated by Vormetric agents when user programs access files protected by a Guard Point, which is a directory protected by the Vormetric Filesystem agent. This requires that the Guard Point has been set up using a policy where the rules include an audit effect, and that the agent has been configured to send "INFO" level log messages to the Splunk system, either directly from the agent, or forwarded by the DSM.
If info-level audit logging of Guard Point accesses is not provided, the Splunk reports might not provide useful results.
The log streams provided to Splunk must in RFC5424 Syslog format, else field extraction will not work correctly. This is selected in the DSM when defining the syslog stream formats.
The reports and searches might not provide useful information until a sufficient volume of log events has been captured by Splunk.
This app by default assumes log data will be received by Splunk via TCP and/or UDP on port 5514.
1.0.8 - updated 13th Nov 2013
Updates to message catalogs to cover VTE 6.0.1 release, including changes to conform to Thales themes and copyright.
Updated to include V6 message catalogs for the Vormetric VTE agents, including Live Data Transform and Linux Docker support.
Added data model, named "Vormetric Security Intelligence" for use with Splunk 6.1 Pivot, and updated message catalogs to cover Vormetric 5.2.1 Agent and DSM releases.
As a Splunkbase app developer, you will have access to all Splunk development resources and receive a 50GB license to build an app that will help solve use cases for customers all over the world. Splunkbase has 1000+ apps and add-ons from Splunk, our partners and our community. Find an app or add-on for most any data source and user need, or simply create your own with help from our developer portal.