Document toolbox

box.win_intrust

Owned by Juan Tomás Alonso Nieto (Deactivated)

Last updated: Aug 22, 2023

2 min read

[ 1 Introduction ] [ 2 Valid tags and data tables ] [ 3 How is the data sent to Devo? ] [ 4 Table structure ]

Introduction

The tags beginning with box.win_intrust identify Windows event logs generated by Quest InTrust.

Valid tags and data tables

The full tag must have at least 2 levels. The first two are fixed as box.win_intrust. The third level identifies the type of events sent.

These are the valid tags and corresponding data tables that will receive the parsers' data:

Product / Service	Tags	Data tables

Product / Service	Tags	Data tables
Windows inTrust	`box.win_intrust.application`	`box.win_intrust`
	`box.win_intrust.application`	`box.win_intrust.application`
	`box.win_intrust.invalid`	`box.win_intrust.invalid`
	`box.win_intrust.other`	`box.win_intrust.other`
	`box.win_intrust.security`	`box.win_intrust.security`
	`box.win_intrust.system`	`box.win_intrust.system`

For more information, read more about Devo tags.

How is the data sent to Devo?

Windows logs generated by InTrust must be sent to the Devo platform via the Devo Relay to secure communication. See the required relay rules below:

Relay rule 1

Source port → Enter the required free port
Source data → gatheringEventLog\"\s?:\s?\"(Security|Application|System)
Target tag → box.win_intrust.\\D1
Select the Stop processing and Is prefix checkboxes

Relay rule 2

Source port → Enter the required free port
Target message → box.win_intrust.other
Select the Stop processing and Is prefix checkboxes

Table structure

These are the fields displayed in these tables: