Novell, Inc., makes no representations or warranties with respect to the contents or use of this documentation, and
specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
Further, Novell, Inc., reserves the right to revise this publication and to make changes to its content, at any time,
without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc., makes no representations or warranties with respect to any software, and specifically disclaims
any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc.,
reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to
notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the
trade laws of other countries. You agree to comply with all export control regulations and to obtain any required
licenses or classification to export, re-export or import deliverables. You agree not to export or re-export to entities on
the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws.
You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. See the
Novell International Trade Services Web page (http://www.novell.com/info/exports/) for more information on
exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export
approvals.
Novell, Inc., has intellectual property rights relating to technology embodied in the product that is described in this
document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S.
patents listed on the Novell Legal Patents Web page (http://www.novell.com/company/legal/patents/) and one or
more additional patents or pending patent applications in the U.S. and in other countries.
Novell, Inc.
404 Wyman Street, Suite 500
Waltham, MA 02451
U.S.A.
www.novell.com
Online Documentation: To access the latest online documentation for this and other Novell products, see
the Novell Documentation Web page (http://www.novell.com/documentation).
Novell Trademarks
For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/
trademarks/tmlist.html).
Third-Party Materials
All third-party trademarks are the property of their respective owners.
SentinelTM is a security information and event management solution that receives information from
many sources throughout an enterprise, standardizes it, prioritizes it and presents it to you to make
threat, risk and policy related decisions. The Sentinel 6.1 RD User Reference Guide is your
reference for the following:
Collector administrator functions
Collector and Sentinel meta tags
Sentinel console user permissions
Sentinel correlation engine
Sentinel command line options
Sentinel server database views
This guide assumes that you are familiar with Network Security, Database Administration and Linux
operating system.
This documentation is intended for Information Security Professionals.
Feedback
We want to hear your comments and suggestions about this manual and the other documentation
included with this product. Please use the User Comments feature at the bottom of each page of the
online documentation and enter your comments there.
Additional Documentation
Sentinel technical documentation is broken down into several different volumes. They are:
The Sentinel SDK site provides the details about developing collectors (proprietary or
JavaScript) and JavaScript correlation actions.
Documentation Conventions
In this documentation, a greater-than symbol (>) is used to separate actions within a step and items
within a cross-reference path.
novdocx (en) 13 May 2009
A trademark symbol (®, ™, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party
trademark.
When a single path name can be written with a backslash for some platforms or a forward slash for
other platforms, the path name is presented with forward slashes to reflect the Linux* convention.
®
Users of platforms that require a backslash, such as NetWare
, should use backlashes as required by
your software.
Contacting Novell
Novell Website (http://www.novell.com)
Novell Technical Support (http://support.novell.com/
Every Sentinel event or correlated event has certain fields that are automatically populated (such as
Event Time and Event UUID) and other fields that may or may not be populated, depending on the
type of event, the collector parsing, and the mapping service configuration. This event data is visible
in Active Views, historical queries, and reports. They are stored in the database and can be accessed
via the report views. They can also be used in actions available through the right-click event menu,
correlation actions, and iTRAC workflow actions.
Section 1.1, “Event Field Labels and Tags,” on page 11
Section 1.2, “List of Fields and Representations,” on page 15
1.1 Event Field Labels and Tags
Each field can be referred to by a user-friendly label or a short tag. The user-friendly label is visible
throughout the Sentinel Control Center interface, for example:
Column headers for Active Views, historical event queries, and the Active Browser
Correlation wizard drop-down menus
Active View configuration drop-down menus
1
Each field has a default label, but that label is user-configurable using the Event Configuration
option on the Admin tab. For more information, see “Admin” section in Sentinel 6.1 Rapid
Deployment User Guide.
user who initiated the event, but this can be changed by the administrator. When a user changes the
default label, the changes are reflected in most areas of the interface, including any correlation rules,
filters, and right-click menu options.
WARNING: Changing the default label for variables other than Customer Variables may cause
confusion when working with Novell Technical Services or other parties who are familiar with the
default names. In addition, JavaScript Collectors built by Novell refer to the default labels described
in this chapter and are not automatically updated to refer to new labels.
Each field also has a short tag name that is always used for internal references to the field and is not
user-configurable. This short tag name may not correspond exactly to the default label; Sentinel
labels have changed over the years, but the underlying short tags remain the same for backward
compatibility. (For example, InitUserName is the default label for the account name of the user who
initiated the event. The default label was previously SourceUserName, and the underlying short tag
is “sun”.)
NOTE: Many of the default labels were updated for clarity in the Sentinel 6.1 release. Because all
filters, actions, and correlation rule definitions are defined using the short tags, even though the label
may be visible in the interface, there is no change in functionality due to the label renaming.
InitUserName
is the default label to represent the account name of the
Sentinel 6.1 Rapid Deployment Event Fields
11
Each field is associated with a specific data type, which corresponds to the data type in the database:
string: limited to 255 characters (unless otherwise specified)
integer: 32-bit signed integer
UUID: 36 character (with hyphens) or 32 character (without hyphens) hexadecimal string in
the format XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX (For example, 6A5349DA-7CBF-1028-9795-000BCDFFF482)
date: Collector Variable must be set with date as number of milliseconds from January 1, 1970
00:00:00 GMT. When displayed in Sentinel Control Center, meta-tags of type date are
displayed in a regular date format.
IPv4: IP address in dotted decimal notation (that is – xxx.xxx.xxx.xxx)
This section has the following information:
Section 1.1.1, “Free-Form Filters and Correlation Rules,” on page 12
Section 1.1.2, “Actions,” on page 13
Section 1.1.3, “Proprietary Collectors,” on page 15
Section 1.1.4, “JavaScript Collectors,” on page 15
novdocx (en) 13 May 2009
1.1.1 Free-Form Filters and Correlation Rules
You can use either the tag or the label when you write free-form language in the Sentinel Control
Center. The Sentinel interface shows the user-friendly label.
Figure 1-1 Correlation Wizard displaying labels in drop-down and free-form language
12Sentinel 6.1 Rapid Deployment Reference Guide
Figure 1-2 Filter Wizard displaying labels in drop-down and free-form language
novdocx (en) 13 May 2009
The representation of fields in the free-form RuleLG language is usually prefaced by “e.” for
example, “e.InitUserName” or “e.sun” can refer to the Initiator User Name for the incoming or
current event. In special cases, “w.” may be used to refer to a field in a past event (for example,
“w.InitUserName”). For more information about the RuleLG language, see Chapter 3, “Sentinel 6.1
Rapid Deployment Correlation Engine RuleLG Language,” on page 37.
1.1.2 Actions
Users can use either the tag or the label when they define parameters to be sent to right-click Event
Menu actions, correlation actions, and iTRAC workflow actions.
To pass a field value to an action, you may use a checklist that shows the labels or type the parameter
name directly into the configuration.
When you type the label or short tag for a field to be used in an action, the name can be enclosed in
percent signs (%tag%) or dollar signs ($tag$). For example:
%sun% in a correlation action refers to the value of InitUser in the correlated event
$sun$ in a correlation action refers to the value of InitUser in the current, “trigger” event (the
final event that caused the correlation rule to fire)
NOTE: In a right-click menu event operating on a single event, there is no functional
difference between %sun% and $sun$.
For example, to pass the Initiator User Name to a command line action to look up information from
a database about that user, you could use %InitUserName% or %sun%. For more information about
Actions, see “Actions and Integrators” section in Sentinel 6.1 Rapid Deployment User Guide.
14Sentinel 6.1 Rapid Deployment Reference Guide
Figure 1-4 Configuration Action window
novdocx (en) 13 May 2009
1.1.3 Proprietary Collectors
Proprietary Collectors, written in Novell’s own language, always use variables based on the short
tag to refer to event fields. The short tag name must be prefaced by a letter and underscore, where
the letter indicates the data type for the field (i_ for integer, s_ for string).
1.1.4 JavaScript Collectors
JavaScript Collectors usually refer to event fields using an “e.” followed by the same user-friendly
label set in Event Configuration in the Sentinel Control Center. For a Sentinel system with a default
configuration, for example, the Initiator User Name would be referred to as “e.InitUserName” in the
JavaScript Collector. There are some exceptions to this general rule. Refer to the Sentinel Collector
SDK (http://developer.novell.com/wiki/index.php?title=Develop_to_Sentinel) for more details.
1.2 List of Fields and Representations
The table on the following pages shows the default labels, descriptions and data types for the
Sentinel event fields, along with the proper way to refer to the tags in filters, correlation rules,
actions, and proprietary collector scripts. Fields that cannot or should not be manipulated in the
Collector parsing do not have a Collector variable.
Sentinel 6.1 Rapid Deployment Event Fields15
Table 1-1 Labels and Meta-tags used in Sentinel Control Center and proprietary Collector language
novdocx (en) 13 May 2009
Default Label
Filters and
Correlation
Rules
Menu and
Correlation
Actions
Proprietary
Collector
Language
Data
Typ e
Description
DeviceEventTimeStringe.et%et%s_ETstringThe normalized date and
time of the event, as
reported by the sensor.
DeviceEventTimee.det%det%dateThe normalized date and
time of the event, as
reported by the sensor.
SentinelProcessTimee.spt%spt%dateThe date and time
Sentinel received the
event.
BeginTimee.bgnt%bgnt%s_BGNTdateThe date and time the
event started occurring
(for repeated events).
EndTimee.endt%endt%s_ENDTdateThe date and time the
event stopped occurring
(for repeated events).
RepeatCounte.rc%rc%s_RCintegerThe number of times the
same event occurred if
multiple occurrences were
consolidated.
EventTimee.dt%dt%dateThe normalized date and
time of the event, as given
by the Collector.
SentinelServiceIDe.src%src%UUIDUnique identifier for the
SARBOXe.cv90%cv90%s_CV90stringSet to 1 if the asset is
governed by SarbanesOxley.
HIPAAe.cv91%cv91%s_CV91stringSet to 1 if the asset is
governed by the Health
Insurance Portability and
Accountability Act
(HIPAA) regulation.
GLBAe.cv92%cv92%s_CV92stringSet to 1 if the asset is
governed by the GrammLeach Bliley Act (GLBA)
regulation.
FISMAe.cv93%cv93%s_CV93stringSet to 1 if the asset is
governed by the Federal
Information Security
Management Act (FISMA)
regulation.
NISPOMe.cv94%cv94%s_CV94stringSet to 1 via an asset map
if the target asset is
governed by the National
Industrial Security
Program Operating
Manual (NISPOM)
CustomerVar95 thru
CustomerVar100
CustomerVar101 thru
CustomerVar110
CustomerVar111 thru
CustomerVar120
CustomerVar121 thru
CustomerVar130
CustomerVar131 thru
CustomerVar140
CustomerVar141 thru
CustomerVar150
CustomerVar151 thru
CustomerVar160
e.cv95 thru
e.cv100
e.cv101
thru
e.cv110
e.cv111
thru
e.cv120
e.cv121
thru
e.cv130
e.cv131
thru
e.cv140
e.cv141
thru
e.cv150
e.cv151
thru
e.cv160
%cv95%
thru
%cv100%
%cv101%
thru
%cv110%
%cv111%
thru
%cv120%
%cv121%
thru
%cv130%
%cv131%
thru
%cv140%
%cv141%
thru
%cv150%
%cv151%
thru
%cv160%
s_CV95
thru
s_CV100
s_CV101
thru
s_CV110
s_C V111
thru
s_CV120
s_CV121
thru
s_CV130
s_CV131
thru
s_CV140
s_CV141
thru
s_CV150
s_CV151
thru
s_CV160
stringString variable reserved
for customer use. Stored
in database.
stringInteger variable reserved
for customer use. Stored
in database.
stringDate variable reserved for
customer use. Stored in
database.
stringUUID variable reserved
for customer use. Stored
in database.
stringIPv4 variable reserved for
customer use. Stored in
database.
stringString variable reserved
for customer use. Stored
in database.
stringInteger variable reserved
for customer use. Not
stored in database.
22Sentinel 6.1 Rapid Deployment Reference Guide
novdocx (en) 13 May 2009
Default Label
CustomerVar161 thru
CustomerVar170
CustomerVar171 thru
CustomerVar180
CustomerVar181 thru
CustomerVar190
CustomerVar191 thru
CustomerVar200
Filters and
Correlation
Rules
e.cv161
thru
e.cv170
e.cv171
thru
e.cv180
e.cv181
thru
e.cv190
e.cv191
thru
e.cv200
Menu and
Correlation
Actions
%cv161%
thru
%cv170%
%cv171%
thru
%cv180%
%cv181%
thru
%cv190%
%cv191%
thru
%cv200%
Proprietary
Collector
Language
s_CV161
thru
s_CV170
s_CV171
thru
s_CV180
s_CV181
thru
s_CV190
s_CV191
thru
s_CV200
Data
Typ e
Description
stringDate variable reserved for
customer use. Not stored
in database.
stringUUID variable reserved
for customer use. Not
stored in database.
stringIPv4 variable reserved for
customer use. Not stored
in database.
stringString variable reserved
for customer use. Not
stored in database.
Sentinel 6.1 Rapid Deployment Event Fields23
novdocx (en) 13 May 2009
24Sentinel 6.1 Rapid Deployment Reference Guide
2
Sentinel 6.1 Rapid Deployment
novdocx (en) 13 May 2009
Control Center User Permissions
SentinelTM allows administrators to set user permissions in the Sentinel Control Center at a granular
admin
level. The only user created by default is the
created by the Sentinel Administrator, or someone with similar permissions.
The permissions in the User Manager are grouped into several major categories:
Each of these groups of settings are described in the following sections:
Section 2.1, “Changing User Permissions,” on page 25
Section 2.2, “General,” on page 27
Section 2.3, “Active Views,” on page 28
Section 2.4, “iTRAC,” on page 29
Section 2.5, “Incidents,” on page 30
Section 2.6, “Integrators,” on page 30
Section 2.7, “Actions,” on page 31
Section 2.8, “Event Source Management,” on page 31
Section 2.9, “Analysis Tab,” on page 32
Section 2.10, “Administration,” on page 32
Section 2.11, “Correlation,” on page 33
, or Sentinel Administrator. All other users are
2
Section 2.12, “Solution Pack,” on page 33
Section 2.13, “Identity,” on page 33
Section 2.14, “Reporting,” on page 34
Section 2.15, “Downloading,” on page 35
Section 2.16, “Java Webstart,” on page 35
2.1 Changing User Permissions
1 Log into the Sentinel Control Center as a user with the User Management permissions.
2 Click the Admin tab.
3 Select User Configuration from Admin tab. Alternatively, Select User Manager from User
Configuration in the Navigator.
Sentinel 6.1 Rapid Deployment Control Center User Permissions
25
4 Right click user and select User Details.
novdocx (en) 13 May 2009
5 Select the Permissions tab.
26Sentinel 6.1 Rapid Deployment Reference Guide
novdocx (en) 13 May 2009
6 Deselect the check boxes for which you want to restrict the user.
7 Click OK.
2.2 General
Table 2-1 Permissions-General
Permission NameDescription
Save WorkspaceAllows user to save preferences. If this permission is unavailable, user
will never be prompted to save changes to preferences when logging out
or exiting the Sentinel Control Center.
Column ManagementAllows user to manage the columns in the Active View tables.
SnapshotAllows user to take a snapshot of Active View tables.
Sentinel 6.1 Rapid Deployment Control Center User Permissions27
2.2.1 General – Public Filters
Table 2-2 Permissions-General-Public Filters
Permission NameDescription
Create Public FiltersAllows user to create a filter with an owner ID of PUBLIC. If user does
not have this permission, then the value PUBLIC will not be listed as
one of the owner IDs that user can create a filter for.
Modify Public FiltersAllows user to modify a public filter.
Delete Public FiltersAllows user to delete a public filter.
2.2.2 General – Manage Private Filters of Other Users
Table 2-3 Permissions-General-Manage Private Filters of Other Users
novdocx (en) 13 May 2009
Permission NameDescription
Create Private Filters for Other UsersAllows user to create private filters for themselves or for
other users.
Modify Private Filters of Other UsersAllows user to modify their own private filters and private
filters created by other users.
Delete Private Filters of Other UsersAllows user to delete their own private filters and private
filters created by other users.
View/Use Private Filters of Other UsersAllows user to view/use their own private filters and private
filters crated by other users.
2.2.3 General – Integration Actions
Table 2-4 Permissions-General-Integration Actions
Permission NameDescription
Send to HP Service DeskAllows user to send events, incident and associated objects to
Remedy. (requires the optional Remedy integration component)
2.3 Active Views
Table 2-5 Permissions-Active Views
Permission NameDescription
View Active Views TabAllows user to see and use the Active Views tab, menu and other
related functions associated with the Active Views tab.
28Sentinel 6.1 Rapid Deployment Reference Guide
Permission NameDescription
Use/View Active Views Allows user to access the Active Views charts.
2.3.1 Active Views – Menu Items
Table 2-6 Permissions-Active Views-Menu Items
Permission NameDescription
Use Assigned Menu ItemsAllows user to use assigned menu items in the
Active Views Events table (the right-click menu).
Add to Existing IncidentAllows user to add events to existing incidents
using the Active Views Events table (the right-click
menu).
Remove from IncidentAllows user to remove events from an existing
incident using the Events tab Events table (the
right-click menu).
novdocx (en) 13 May 2009
Email EventsAllows user to e-mail events using the Active Views
Events table (the right-click menu).
View Advisor Attack DataAllows user to view the Advisor Attack Data stream.
View VulnerabilityAllows user to view the vulnerabilities present in the
Sentinel database
2.4 iTRAC
Table 2-7 Permissions-iTRAC
Permission NameDescription
View iTRAC TabAllows user to see and use the iTRAC tab, menu and other related
functions associated with the iTRAC tab.
Activity ManagementAllows user to access the Activity Manager.
Manage Work Items Of UsersGives user administrative control over all workitems, including
those assigned to other users.
2.4.1 iTRAC - Template Management
Table 2-8 Permissions-iTRAC-Template Management
Permission NameDescription
View/Use Template ManagerAllows user to access the Template Manager.
Create/Modify TemplatesAllows user to create and modify templates.
Sentinel 6.1 Rapid Deployment Control Center User Permissions29
2.4.2 iTRAC - Process Management
Table 2-9 Permissions-iTRAC-Process Management
Permission NameDescription
View/Use Process ManagerAllows user to access the Process View Manager.
Start/Stop ProcessesAllows user to use the Process View Manager.
2.5 Incidents
Table 2-10 Permissions-Incidents
Permission NameDescription
View Incidents TabAllows user to see and use the Incidents tab, menu and other related
functions associated with the View Incidents tab.
novdocx (en) 13 May 2009
Incident AdministrationAllows user to modify an incident.
View Incident(s)Allows user to view/modify the details of an incident. If the user does not
have this permission, then the Incident Details window will not be displayed
when the user either double-clicks an Incident in the Incident View window
or right-clicks the incident or selects the Modify option.
Create Incident(s)Allows user to create Incidents in the in the Incident View window or by right
clicking on the incident and select Modify option. Alternatively you can
select Create Incident menu item in the Incidents menu bar and clicking
Create Incident option in the tool bar.
Modify Incident(s)Allows user to modify an incident in the Incident Details window.
Delete Incident(s)Allows user to delete incidents.
Assign Incident(s)Allows user to assign an incident in the Modify and Create Incident window.
Email IncidentsAllows user to e-mail Incidents of interest.
Incident ActionsAllows user to view Execute Incident Action menu option in an Incident and
to execute actions.
Add NotesAllows user to add any number notes to an incident.
2.6 Integrators
Table 2-11 Permissions-Integrators
Permission NameDescription
View IntegratorAllows user to view Integrators, open Integrator Manager, use
update, refresh, help, test buttons and view integrator event details.
30Sentinel 6.1 Rapid Deployment Reference Guide
Permission NameDescription
Manage IntegratorAllows user to manage (add/modify/delete) the configured
Integrators.
Manage Integrator PluginsAllows user to manage (add/modify/delete) the Integrators plugins.
2.7 Actions
Table 2-12 Permissions-Action Manager
Permission NameDescription
View ActionsAllows user to use Action Manager and view Actions.
Manage ActionsAllows user to add/edit/delete actions of type "Execute Action
Plugins"
Manage Action PluginsAllows user to add/edit/delete Action Plugins.
novdocx (en) 13 May 2009
2.8 Event Source Management
Table 2-13 Permissions-Event Source Management
Permission NameDescription
View StatusAllows user to view the status of ESM components.
View ScratchpadAllows user to design and configure ESM components.
Configure ESM ComponentsAllows you to configure ESM components.
Control ESM ComponentsAllows you to control and manage ESM components.
Manage PluginsAllows you to manage Collector and Connector Plugins.
View Raw DataAllows you to view/parse raw data.
Debug CollectorAllows you to debug Collector.
Command and Control consists of:
start/stop individual ports
start/stop all ports
restart hosts
rename hosts
Sentinel 6.1 Rapid Deployment Control Center User Permissions31
2.9 Analysis Tab
Table 2-14 Permissions-Analysis Tab
Permission NameDescription
Analysis TabAllows user to see and use the View Analysis tab, menu and other
related functions associated with the System Overview tab.
2.10 Administration
Table 2-15 Permissions-Administration
Permission NameDescription
View Administration TabAllows user to see and use the View Administration tab, menu and
other related functions associated with the View Administration tab.
novdocx (en) 13 May 2009
DAS StatisticsAllows user to view DAS activity (DAS binary and query).
Event ConfigurationAllows user to rename columns, set mappings from mapping files.
This function is associated with Mapping Configuration.
Map Data ConfigurationAllows user to add, edit and delete mapping files.
Event Menu ConfigurationAllows user to access the Menu Configuration window and add new
options that display on the Event menu when you right-click an
event.
Report Data ConfigurationAllows user to enable or disable summary tables used in
aggregation.
User ManagementAllows user to add, modify and delete user details
User Session ManagementAllows user to view, lock and terminate active users (logins to
Sentinel Control Center).
iTRAC Role ManagementAllows user to view and use the role manager in the Admin Tab.
View ServersAllows user to monitor the status of all processes.
Control ServersAllows user to start, restart and stop processes.
2.11 Correlation
Table 2-18 Permissions-Correlation
Permission NameDescription
View Correlation TabAllows user to use the Correlation functions.
novdocx (en) 13 May 2009
View/Use Correlation Rule ManagerAllows user to start or stop the Correlation Rules.
View/Use Correlation Engine ManagerAllows user to deploy/undeploy the Correlation Rules.
View/Use Dynamic ListsAllows user to Create, use, view, modify the Dynamic
Lists.
2.12 Solution Pack
Table 2-19 TPermissions-Solution Pack
Permission NameDescription
Solution DesignerAllows user to access Solution Designer.
Solution ManagerAllows user to access Solution Manager.
2.13 Identity
Table 2-20 Permissions-Action Manager
Permission NameDescription
View/Use Identity Address BookAllows user to view and use Identity Browser.
Sentinel 6.1 Rapid Deployment Control Center User Permissions33
2.14 Reporting
Table 2-21 Reporting Permissions
Permission NameDescription
Run/View ReportsAllows user for the following:
View the report results and sample reports
Run the reports by using the Run option Now in the
Reports page of the Web interface.
For more information on Running the reports, see
“Running Reports” in the Sentinel 6.1 Rapid Deployment
User Guide.
NOTE: Users with Run/View permission cannot schedule
reports . They cannot use the run options Daily, Once, Weekly, and Monthly.
Delete the report results
Rename the report results
Restart report runs
novdocx (en) 13 May 2009
Manage ReportsAllows user for the following:
Access the reporting features listed under Run/View
Reports permission
Schedule report runs.
In addition to the the run option Now, the user can also run
the reports using the run options Once, Daily, Weekly, and
Monthly.
For more information on Running the reports, see
“Running Reports” in the Sentinel 6.1 Rapid Deployment
User Guide.
Upload report definitions
Delete report definitions
34Sentinel 6.1 Rapid Deployment Reference Guide
2.15 Downloading
Table 2-22 Downloading Permissions
Permission NameDescription
Download Client InstallersAllows user for the following:
Download Collector Manager Installer
The Collector Manager Installer helps you install the Sentinel
Collector Manager on any machine from which you want to
forward events.
Download Client Installer
The Client Installer helps you install the Sentinel Control
Center and Sentinel Data Manager on any client machine.
2.16 Java Webstart
novdocx (en) 13 May 2009
All the authenticated users can web start the Sentinel Control center. With the following new
permissions you can restrict users from webstarting Sentinel Data Manager and Solution Designer.
For more information on Webstart, refer to “Applications and Installers”.
Table 2-23 Web Start Permissions
Permission NameDescription
Run SDM Through WebStartAllows user to run SDM by using the WebStart option in the
Sentinel 6.1 Rapid Deployment Web interface.
Run Solution Designer Through
WebStart
Allows user to run Solution Designer by using the WebStart option
in the Sentinel 6.1 Rapid Deployment Web interface.
Sentinel 6.1 Rapid Deployment Control Center User Permissions35
novdocx (en) 13 May 2009
36Sentinel 6.1 Rapid Deployment Reference Guide
3
Sentinel 6.1 Rapid Deployment
novdocx (en) 13 May 2009
Correlation Engine RuleLG
Language
This section has the following information about SentinelTM correlation engine Rule LG language.
Section 3.1, “Correlation RuleLG Language Overview,” on page 37
Section 3.2, “Event Fields,” on page 38
Section 3.3, “Event Operations,” on page 38
Section 3.4, “Rule Operations,” on page 42
Section 3.5, “Operators,” on page 44
Section 3.6, “Order of Operators,” on page 45
Section 3.7, “Differences between Correlation in 5.x and 6.x,” on page 45
3.1 Correlation RuleLG Language Overview
The Sentinel Correlation Engine runs rules that are written in the Correlation RuleLg language.
Rules are created in the Sentinel Control Center. Users can create rules using a wizard for the
following rule types:
3
Simple Rule
Composite Rule
Aggregate Rule
Sequence Rule
These rules are converted to the Correlation RuleLg language when the rules are saved. The same
rule types, plus even more complex rules, can be created in the Sentinel Control Center using the
Custom/Freeform option. To use the Custom/Freeform option, the user must have a good
understanding of the Correlation RuleLg language.
RuleLg uses several operations, operators, and event field short tags to define a rule. The Correlation
Engine loads the rule definition and uses the rules to evaluate, filter, and store in memory events that
meet the criteria specified by the rule. Depending on the rule definition, a correlation rule might fire
based on
the value of one field or multiple fields
the comparison of an incoming event to past events
the number of occurrences of similar events within a defined time period
one or more subrules firing
one or more subrules firing in a particular order
Each of these constructs is represented by an operation in RuleLg.
Sentinel 6.1 Rapid Deployment Correlation Engine RuleLG Language
37
3.2 Event Fields
All operations function on event fields, which can be referred to by their labels or by their short tags
within the correlation rule language. For a full list of labels and short tags, see Chapter 1, “Sentinel
6.1 Rapid Deployment Event Fields,” on page 11. The label or metatag must also be combined with
a prefix to designate whether the event field is part of the incoming event or a past event that is
stored in memory.
Examples:
e.DestinationIP (Destination IP for the current event)
e.dip (Destination IP for the current event)
w.dip (Destination IP for any stored event)
WARNING: If you rename the label of a metatag, do not use the original label name when creating
a correlation rule.
3.3 Event Operations
novdocx (en) 13 May 2009
Event operations evaluate, compare, and count events. They include the following operations:
Filter: Evaluates the current events to determine whether they can potentially trigger a rule to
fire
Window: Compares the current event to past events that have been stored in memory
Trig g e r : Counts events to determine whether enough events have occurred to trigger a rule
Each operation works on a set of events, receiving a set of events as input and returning a set of
events as output. The current event processed by a rule often has a special meaning for the semantic
of the language. The current event is always part of the set of events in and out of an operation
unless the set is empty. If an input set of an operation is empty, then the operation is not evaluated.
3.3.1 Filter Operation
Filter consists of a Boolean expression that evaluates the current event from the real-time event
stream. It compares event attributes to user-specified values using a wide set of operators
The Boolean expression is a composite of comparison and match instructions.
<Boolean expressions 1…n> are expressions using one or more event field names
and filter operators
For example, this rule detects whether the current event has a severity of 4 and the resource event
field contains either “FW” or “Comm.”
filter(e.sev = 4 and (e.res match regex ("FW") or e.res match regex ("Comm")))
38Sentinel 6.1 Rapid Deployment Reference Guide
Boolean Operators
Filter expressions can be combined using the Boolean operators AND, OR and NOT. The filter
boolean operator precedence (from highest [top] to lowest [bottom] precedence) is:
Table 3-1 Boolean Operators
OperatorMeaningOperator TypeAssociativity
Notlogical notunaryNone
Andlogical andbinaryleft to right
Orlogical orbinaryleft to right
In addition to Boolean operators, filter supports the following operators.
Standard Arithmetic Operators
Standard arithmetic operators can be used to build a condition that compares the value of a Sentinel
metatag and a user-specified value (either a numeric value or a string field). The standard arithmetic
operators in Sentinel are =, <, >, !=, <=, and >=.
The match regex operator can be used to build a condition where the value of a metatag matches a
user-specified regular expression value specified in the rule. This operator is used only for string
tags, and the user-specified values for this operator are case-sensitive.
Examples:
filter(e.Collector match regex ("IBM"))
filter(e.EventName match regex ("Attack"))
Match Subnet Operators
The match subnet operator can be used to build a condition where the value of a metatag maches a
user-specified subnet specified in the rule in CIDR notation. This operator is used only for IP
address fields.
Example:
filter(e.DestinationIP match subnet (10.0.0.1/22))
Inlist Operator
The inlist operator is used to perform a lookup on an existing dynamic list of string values, returning
true if the value is present in the list. For more information on Dynamic Lists, see “Correlation Tab”
in Sentinel 6.1 Rapid Deployment User Guide.
For example, this filter expression is used to evaluate whether the Source IP of the current event is
present on a dynamic list called MailServerList. If the Source IP is present in this list, the expression
evaluates to TRUE.
filter(e.sip inlist MailServerList)
As another example, this filter expression combines the NOT and the INLIST operator. This
expression evaluates to TRUE if the Source IP is not present in the dynamic list called
MailServerList.
filter(not (e.sip inlist MailServerList))
This filter expression is used to evaluate whether the event name of the current event equals “File
Access” and the Source User Name is also not present on a dynamic list called AuthorizedUsers. If
both conditions are true for the current event, the expression evaluates to TRUE.
filter(e.evt="File Access" and not(e.sun inlist AuthorizedUsers))
ISNULL Operator
The isnull operator returns true if the metatag value is equal to NULL.
novdocx (en) 13 May 2009
Example:
Filter(isnull(e.SIP))
Output Sets
The output of a filter is either the empty set (if the Boolean expression evaluates to false) or a
set containing the current event and all of the other events from the incoming set (if the
Boolean expression evaluates to true).
If filter is the last or only operation of a correlation rule, then the output set of the filter is used
to construct a correlated event. The trigger events are the filter operation output set of events
with the current event first.
If filter is not the last operation of a correlation rule (that is, filter is followed by a flow
operatior), then the output set of a filter is used as the input set to other operations (through the
flow operator).
Additional Information
The filter operator can be used to compare metatag values with other metatag values, for
example:
e.SourceIP=e.DestinationIP
3.3.2 Window Operation
Window compares the current event to a set of past events that are stored in a “window.” The events
in the window can be all past events for a certain time period, or they can be filtered.
The Boolean expression is a composite of comparison instructions and match instructions with the
Boolean operators AND, OR and NOT.
<Boolean expression> is an expression comparing a metatag value from the
current event to a metatag value from a past event (or a user-specified
constant)
<filter expression> is optional and specifies filter criteria for the past
events
<evaluation period> specifies the duration for which past events matching the
filter expression are maintained, specified in seconds (s), minutes (m), or
hours (h). If no letter is specified, seconds are assumed.
For example, this rule detects whether the current event has a source IP address in the specified
subnet (10.0.0.10/22) and matches an event(s) that happened within the past 60 seconds.
window(e.sip = w.sip, filter(e.sip match subnet (10.0.0.10/22),60)
As another example, this rule is a domino type of rule. An attacker exploits a vulnerable system and
uses it as an attack platform.
window((e.sip = w.dip AND e.dp = w.dp AND e.evt = w.evt), 1h)
novdocx (en) 13 May 2009
This rule identifies a potential security breach after a denial of service attack. The rule fires if the
destination of a denial of service attack has a service stopped within 60 seconds of the attack.
filter(e.rv51="Service" and e.rv52="Stop" and e.st = "H") flow window (e.sip =
w.dip, filter(e.rv52="Dos"), 60s) flow trigger(1,0))
Output Sets
If any past event evaluates to true with the current event for the simple boolean expression, the
output set is the incoming event plus all matching past events.
If no events in the window match the current event for the simple boolean expression, the
output set is empty.
If a window is the last or only operation of a correlation rule, then the output set of the window
is used to construct a correlated event (the correlated events being the window operation output
set of events with the current event first).
Additional Information
You must prepend a metatag name with "e." to specify the current event or with "w." to specify
the past events
All window simple Boolean expressions must include a metatag in the form w.[metatag].
For more information about valid filter expressions, see Section 3.3.1, “Filter Operation,” on
page 38.
Every event coming in to the Correlation Engine that passes this filter is put into the window of
past events
If no filter expression exists, then all events coming into the Correlation Engine are maintained
by the window. With extremely high event rates or long durations, this might require a large
amount of memory.
The current event is not placed into the window until after the current event window evaluation
is complete
To minimize memory usage, only the relevant parts of the past events, not all metatag values,
are maintained in memory.
3.3.3 Trigger Operation
Trigger is used to specify a number of events for a user-specified duration.
The syntax for trigger is:
Trigger (<number of events>, <evaluation period>[, discriminator (<list of
tags>))
Where
<number of events> is an integer value specifying the number of matching
events that are necessary for the rule to fire
<evaluation period> specifies the duration for which past events matching the
filter expression are maintained, specified in seconds (s), minutes (m), or
hours (h). If no letter is specified, seconds are assumed.
discriminator is a field to group by
novdocx (en) 13 May 2009
For example, this rule detects if 5 events with the same source IP address happen within 10 seconds.
trigger(5,10,discriminator(e.sip))
Output Sets
If the specified count is reached within the specified duration, then a set of events containing all
of the events maintained by the trigger is output; if not, the empty set is output.
When receiving a new input set of events, a trigger first discards the outdated events (events
that have been maintained for more than the duration) and then inserts the current event. If the
number of resulting events is greater than or equal to the specified count, then the trigger
outputs a set containing all of the events.
If a trigger is the last operation (or the only operation) of a correlation rule, then the output set
of the trigger is used to construct a correlated event (the correlated events being the trigger
operation output set of events with the current event first).
If a trigger is not the last operation of a correlation rule (that is, it is followed by a flow
operator), then the output set of a trigger is used as the input set to other operations (through the
flow operator).
The discriminator (meta-tag list) is a comma-delimited list of meta-tags. A trigger operation
keeps different counts for each distinct combination of the discriminator meta-tags.
3.4 Rule Operations
Rule operations work on subrules that have been combined into a compound rule. They include:
Gate
Sequence
42Sentinel 6.1 Rapid Deployment Reference Guide
3.4.1 Gate Operation
The gate operation is used to create a composite rule which is used in identifying complex situations
from the occurrence of simple situations.
The composite rule is made up of one or more nested subrules and can be configured to fire if some,
any or all of the subrules fire within a specified time window. The subrules can be a simple rule or
another composite rule. For more information on Composite Rule, see “Correlation Tab” in Sentinel
6.1 Rapid Deployment User Guide.
The syntax for gate is:
Gate(<subrule 1 rulelg>, <subrule 2 rulelg>…<subrule n ruleLg>, <mode>,
<evaluation period>, discriminator(<list of tags>))
Where
Subrule Rulelgs are the rulelg definitions for 1 to n subrules
mode = all | any | 1 | 2 | … | n, which is the number of subrules that must be
triggered in order for the gate rule to trigger
<evaluation period> specifies the duration for which past events matching the
filter expression are maintained, specified in seconds (s), minutes (m), or
hours (h). If no letter is specified, seconds are assumed.
discriminator is a field to group by
novdocx (en) 13 May 2009
For example, this rule is a typical perimeter security IDS inside/outside rule
Sequence rules are similar to gate rules, except that all child rules must fire in time order for the
sequenced rule to evaluate to true.
The subrules can be a simple rule or another composite rule.
The syntax for sequence is:
Sequence(<subrule 1 rulelg>, <subrule 2 rulelg>…<subrule n ruleLg>,
<evaluation period>, discriminator(<list of tags>))
Where
Subrule Rulelgs are the rulelg definitions for 1 to n subrules
<evaluation period> is a time period expressed in seconds (s), minutes (m), or
hours (h)
discriminator is a field to group by
For example, this rule detects three failed logins by a particular user in 10 minutes followed by a
successful login by same user.
Operators are used to transition between operations or expressions. The fundamental operators used
between operations are:
Flow operator
Union operator
Intersection operator
Discriminator operator
3.5.1 Flow Operator
The output set of events of the left-hand side operation is the input set of events for the right-hand
side operation. Flow is typically used to transition from one correlation operation to the next.
For example:
filter(e.sev = 5) flow trigger(3, 60)
novdocx (en) 13 May 2009
The output of the filter operation is the input of the trigger operation. The trigger only counts events
with severity equal to 5.
3.5.2 Union Operator
The union of the left side operation output set and the right side operation output set. The resulting
output set contains events from either the left-hand side operation output set or the right-hand side
operation output set without duplicates.
For example:
filter(e.sev = 5) union filter(e.sip = 10.0.0.1)
is equivalent to
filter(e.sev = 5 or e.sip = 10.0.0.1)
3.5.3 Intersection Operator
The intersection of the left side operation output set and the right side operation output set. The
resulting output set contains events that are common in both the left-hand side operation output set
and the right-hand side operation output set without duplicates.
The discriminator operator allows users to group by event fields within other event operations.
Discriminator can be used within the trigger, gate, or sequence operations. This is the last operation
when executing a condition. The input for this operator will generally be the output of other
operations, if any.
For example, this filter expression is used to identify five severity 5 events within 60s that all have
the same Source IP. Note that the attribute (SIP in this example) can be any value, even a NULL, but
it must be the same for all five events in order for the rule to fire.
FeaturesCorrelation in Sentinel 5.xCorrelation in Sentinel 6.1RD
SensorType fieldSentinel 6.x merges the “C”
(Correlated Events) and “W”
(watchlist events) SensorTypes.
All events generated by the
Correlation Engine are now
labeled “C” in the SensorType
field.
novdocx (en) 13 May 2009
Correlation Actions and
Correlation Rules
Boolean expressionsfilter operation supported the
Boolean expressions AND and
OR.
Creating a rule from a PUBLIC
filter
Update functionality for rulesUpdates to a rule were based on
GUI OptionSentinel 6.x doesn't have the GUI
a sliding window based on the
trigger time period.
Correlation Actions and
Correlation Rules are decoupled
in Sentinel 6.x
The window operation supports
Boolean expressions
OR: window(e.dip=w.dip OR
e.sip=w.sip,
filter(e.sev>2),60)
AND: window(e.evt=w.evt
AND e.sun=w.sun,
filter(e.sev>2),60)
option to create a rule from a
PUBLIC filter. The filter criteria
must be defined in the correlation
wizard or language.
The update functionality for a rule
that is triggered more than once
is configurable in Sentinel 6.x.The
update functionality can be set
when the rule is deployed; the
rule actions might happen every
time the rule is triggered, or they
can be set to occur once and then
wait for some period of time
before the action occurs again.
This prevents multiple
notifications on a single, ongoing
event.
The e.all metatagThe e.all metatag has been
46Sentinel 6.1 Rapid Deployment Reference Guide
The IN, NOT IN, and difference
operators are deprecated.
Correlation rules using these
operators must be modified
before running them in Sentinel
6.x.
deprecated. Correlation rules
using this operator should be
updated to use specific short tags
before running them in Sentinel
6.x.
4
Sentinel 6.1 Rapid Deployment
novdocx (en) 13 May 2009
Data Access Service
The Data Access Service (DAS) is Sentinel Server's persistence service and provides a message bus
interface to the database. Some of the services it provides are event storage, Historical Query, event
drill down, vulnerability, Advisor data retrieval, and configuration manipulation.
Section 4.1, “DAS Container Files,” on page 47
4.1 DAS Container Files
DAS is a collection of services provided by different processes. Each process is a container
responsible for different types of database operations. These processes are:
DAS Core: DAS Core is responsible for the following:
Performs general Sentinel Service operations including Login and Historical Query.
Provides the server-side functionality for Active Views.
Calculates event data summaries that are used in reports.
Provides the server-side functionality for the Sentinel iTRAC functionality.
Provides a command line interface to certain DAS services. Used primarily for third-party
integration.
4
Provides the server-side of the SSL proxy connection to Sentinel Server.
DAS Binary: Performs event database insertion.
DAS Proxy is not directly part of the DAS collection of services. It is part of the Communication
Server and does not directly connect to the database.
Section 4.1.1, “Reconfiguring Database Connection Properties,” on page 47
The primary settings in these configuration files that can be configured using the dbconfig utility are
related to the database connection, including:
username
password
hostname
port number
database (database name)
Sentinel 6.1 Rapid Deployment Data Access Service
47
If any of these database connection settings need to be changed, they must be changed in every
das_*.xml
file using the
dbconfig
utility. Using the –a argument, this utility can update all files at
the same time (For example, update all files in the <Install_directory>\config or <Install_directory>/
config directory). Alternately, using the –n argument, this utility can update a single file’s contents if
only one file need to be updated. Typically, all files should be updated at the same time.
novdocx (en) 13 May 2009
WARNING: Do not manually edit the database connection properties. Use the
dbconfig
utility to
change any database connection values within these files.
To Reconfigure Database Connection Properties:
1 Login to the machine where DAS is installed as the admin user.
Other settings in the files can be adjusted manually (without using dbconfig):
maxConnections
batchSize
loadSize
Changing these settings might affect database performance and should be done with caution
4.1.2 DAS Logging Properties Configuration Files
The following files are used to configure logging of the DAS process. These files are typically
changed when troubleshooting the DAS process.
das_core_log.prop
das_binary_log.prop
They are located in the following locations:
<Install_directory>/config
These files contain the configuration that determines how the DAS processes will log messages. The
most important part of the configuration is the logging levels, which indicate how verbose the log
messages should be. The section of the file to configure these settings is:
###### Configure the logging levels
# Logging level rules are read from the top down.
# Start with the most general, then get more specific.
#
# Defaults all loggers to INFO (enabled by default)
.level=INFO
#
48Sentinel 6.1 Rapid Deployment Reference Guide
# < Set level of specific loggers here >
#
# Turns off all logging (disabled by default)
#.level=OFF
######
novdocx (en) 13 May 2009
NOTE: The logger
.level
is a wildcard logger name that refers to all loggers. Setting this logger’s
level will affect all loggers.
The available logging levels are:
OFF: disables all logging
SEVERE (highest value): indication that a component has malfunctioned or there is a loss/
corruption of critical data
WARNING: if an action can cause a component to malfunction in the future or if there is non-
critical data loss/corruption
INFO: audit information
CONFIG: for debugging
FINE: for debugging
FINER: for debugging
FINEST: (lowest value) – for debugging
ALL: will log all levels
When one specifies a logging level, all log messages of that level and higher (in the above list) will
actually be logged. For example, if one specifies the INFO level, then all INFO, WARNING and
SEVERE message will be logged.
NOTE: At 10 second intervals, the logging properties file will be checked to see if any changes
have occurred since it was last read. If the file has changed, the LogManagerRefreshService will reread the logging properties file. Therefore, it is not necessary to restart the processes to begin using
the updated logging levels.
Log messages are written to
das_binary_0.*.log
das_core_0.*.log
<Install_Directory>/log
in the following files:
The 0 indicates the unique number to resolve conflicts and the * indicates a generation number to
distinguish rotated logs. For example,
das_query0.0.log
is the log with index 0 (latest) file in a
rotated set of log files for the DAS Query process.
Log messages are also written to the process’s console (standard output). However, since the
processes are running as services, users do not have access to the console output. It is possible,
however, to capture the console output in the
sentinel0.*.log file
. This is useful, for example,
if the process is producing an error that is not printed to the process’s own log file. This can be
enabled by adding the following line to the
Sentinel 6.1 Rapid Deployment Data Access Service49
novdocx (en) 13 May 2009
50Sentinel 6.1 Rapid Deployment Reference Guide
5
Sentinel 6.1 Rapid Deployment
novdocx (en) 13 May 2009
Accounts and Password Changes
This section discusses the users that are created or used during Sentinel installation and normal
Sentinel operations. These user accounts are used for normal operations of Sentinel, such as event
inserts into the Sentinel database.
The administrator might select to occasionally change the passwords for these accounts. To ensure
continued normal Sentinel operations, there are special procedures necessary to update the
passwords in all necessary locations.
Section 5.1, “Sentinel Default Users,” on page 51
Section 5.2, “Password Changes,” on page 51
5.1 Sentinel Default Users
This section discusses the users that are created by the Sentinel RD installer.
The following operating system user is created:
novell: This user is primarily for system use and does not have a password. To log in as this
user, the administrator must set a password for novell or su to novell as root.
5
The following users are all created as database users in the PostgreSQL Server database.
postgres: This user owns the database and is for system use only. It is not possible to log in as
this user.
dbauser: This user owns the Sentinel schema and the password is set during installation. This
account should be used to log into the Sentinel Database Manager.
admin: This user is the Sentinel administrator and the password is set during installation. This
account should be used to log into the web interface and the Sentinel Control Center in order to
create more users.
rptuser: This user is used by the system to run reports. The password set to the same password
as the dbauser.
appuser: This user is used by the system for a wide variety of operations. The password is set
to the same password as the dbauser.
5.2 Password Changes
Corporate policy might require that passwords be changed on a regular schedule. Passwords can be
changed using either the Sentinel Control Center or standard database utilities. After changing a
password, some Sentinel components need to be updated to use the new password.
Section 5.2.1, “Changing Application User Passwords,” on page 52
Section 5.2.2, “Changing Database Passwords,” on page 52
Sentinel 6.1 Rapid Deployment Accounts and Password Changes
51
5.2.1 Changing Application User Passwords
This procedure can be used to change the password for the Sentinel Administrator account (admin)
or any other Sentinel Control Center or Web interface user.
1 Log in to the Sentinel Control Center as the Sentinel Administrator or another user with User
Management permissions.
For more information on logging into the SCC, see “Accessing Novell Sentinel Web Interface”
in the Sentinel 6.1 Rapid Deployment User Guide.
2 Click Admin > User Configuration. The User Manager window displays.
3 Double-click admin user account or right-click User Details.
4 Modify the account password and confirm password. Click OK.
No additional updates are needed in the Sentinel system.
5.2.2 Changing Database Passwords
Changing the passwords for system users, such as dbauser, rptuser, or appuser, must be done using
standard database utilities; it cannot be done by using the Sentinel Control Center. Some of these
passwords are encrypted and stored in configuration files and used in normal Sentinel operations.
These configuration files must be updated after the passwords are changed. System user passwords
can be updated using standard database utilities.
novdocx (en) 13 May 2009
IMPORTANT: Changing password for the postgre user is not supported in Sentinel 6.1 Rapid
Deployment.
“Updating PostgreSQL Database Password” on page 52
“Updating Sentinel Configuration Files” on page 53
“Updating Sentinel Data Manager Connection Properties” on page 53
If the appuser password is changed, several Sentinel configuration files must be updated with an
encrypted form of the new password or the system cannot access the database. The dbconfig utility
is designed to encrypt the password and add it to the appropriate files.
novdocx (en) 13 May 2009
To update the Sentinel configuration files with a new password:
1 Change the password for the Sentinel DB Administrator User by using dbconfig utility.
2 This utility is used to set the database connection related information in the config file/s under
/opt/novell/sentinel6_rd_x86/config
directory such as username, password, database
name, port, hostname.
Updating Sentinel Data Manager Connection Properties
If the dbauser password is changed, the Sentinel Data Manager connection properties must be
updated in order for any automated Sentinel Data Manager command line tasks to continue to work
(if applicable in your environment). These password change procedures are only necessary if extra
Sentinel Data Manager jobs have been created and scheduled or the Sentinel Data Manager
command line interface is used.
To update the saved SDM connection settings:
1 Run the following command and use the new dbauser password for the <dbPass> parameter.
For more information, see “Sentinel Data Manager” in Sentinel 6.1 Rapid Deployment User
Sentinel 6.1 Rapid Deployment Accounts and Password Changes53
novdocx (en) 13 May 2009
54Sentinel 6.1 Rapid Deployment Reference Guide
6
Sentinel 6.1 Rapid Deployment
novdocx (en) 13 May 2009
Database Views for PostgreSQL
This section lists the views in the PostgreSQL DB schema for SentinelTM 6.1 Rapid Deployment.
These views provide information for developing your own reports (JasperReports*).
Section 6.1, “Views,” on page 55
Section 6.2, “Deprecated Views,” on page 119
6.1 Views
Below listed are the views available with Sentinel Rapid Deployment.
Section 6.1.1, “ACTVY_PARM_RPT_V,” on page 58
Section 6.1.2, “ACTVY_REF_PARM_VAL_RPT_V,” on page 59
Section 6.1.3, “ACTVY_REF_RPT_V,” on page 59
Section 6.1.4, “ACTVY_RPT_V,” on page 59
Section 6.1.5, “ADV_ATTACK_MAP_RPT_V,” on page 60
Section 6.1.6, “ADV_ATTACK_PLUGIN_RPT_V,” on page 60
Section 6.1.7, “ADV_ATTACK_RPT_V,” on page 61
Section 6.1.8, “ADV_ATTACK_SIGNATURES,” on page 62
6
Section 6.1.9, “ADV_FEED_RPT_V,” on page 62
Section 6.1.10, “ADV_MASTER_RPT_V,” on page 63
Section 6.1.11, “ADV_PRODUCT_RPT_V,” on page 63
Section 6.1.12, “ADV_PRODUCT_SERVICE_PACK_RPT_V,” on page 64
Section 6.1.13, “ADV_PRODUCT_VERSION_RPT_V,” on page 64
Section 6.1.14, “ADV_VENDOR_RPT_V,” on page 65
Section 6.1.15, “ADV_VULN_KB_RPT_V,” on page 66
Section 6.1.16, “ADV_VULN_PRODUCT_RPT_V,” on page 66
Section 6.1.17, “ADV_VULN_SIGNATURES,” on page 67
Section 6.1.18, “ANNOTATIONS_RPT_V,” on page 67
Section 6.1.19, “ASSET_CATEGORY_RPT_V,” on page 67
Section 6.1.20, “ASSET_HOSTNAME_RPT_V,” on page 68
Section 6.1.21, “ASSET_IP_RPT_V,” on page 68
Section 6.1.22, “ASSET_LOCATION_RPT_V,” on page 68
Section 6.1.23, “ASSET_RPT_V,” on page 69
Section 6.1.24, “ASSET_VALUE_RPT_V,” on page 69
Section 6.1.25, “ASSET_X_ENTITY_X_ROLE_RPT_V,” on page 70
Section 6.1.26, “ASSOCIATIONS_RPT_V,” on page 70
Sentinel 6.1 Rapid Deployment Database Views for PostgreSQL
55
Section 6.1.27, “ATTACHMENTS_RPT_V,” on page 71
Section 6.1.28, “AUDIT_RECORD_RPT_V,” on page 71
Section 6.1.29, “CONFIGS_RPT_V,” on page 72
Section 6.1.30, “CONTACTS_RPT_V,” on page 72
Section 6.1.31, “CORRELATED_EVENTS_RPT_V (legacy view),” on page 73
Section 6.1.32, “CORRELATED_EVENTS_RPT_V1,” on page 73
Section 6.1.33, “CRITICALITY_RPT_V,” on page 73
Section 6.1.34, “CUST_HIERARCHY_V,” on page 74
Section 6.1.35, “CUST_RPT_V,” on page 74
Section 6.1.36, “ENTITY_TYPE_RPT_V,” on page 75
Section 6.1.37, “ENV_IDENTITY_RPT_V,” on page 75
Section 6.1.38, “ESEC_CONTENT_GRP_CONTENT_RPT_V,” on page 75
Section 6.1.39, “ESEC_CONTENT_GRP_RPT_V,” on page 76
Section 6.1.40, “ESEC_CONTENT_PACK_RPT_V,” on page 76
Section 6.1.41, “ESEC_CONTENT_RPT_V,” on page 76
novdocx (en) 13 May 2009
Section 6.1.42, “ESEC_CTRL_CTGRY_RPT_V,” on page 77
Section 6.1.43, “ESEC_CTRL_RPT_V,” on page 77
Section 6.1.44, “ESEC_DISPLAY_RPT_V,” on page 78
Section 6.1.45, “ESEC_PORT_REFERENCE_RPT_V,” on page 79
Section 6.1.46, “ESEC_PROTOCOL_REFERENCE_RPT_V,” on page 79
Section 6.1.47, “ESEC_SEQUENCE_RPT_V,” on page 80
Section 6.1.48, “ESEC_UUID_UUID_ASSOC_RPT_V,” on page 80
Section 6.1.49, “EVENTS_ALL_RPT_V (legacy view),” on page 80
Section 6.1.50, “EVENTS_ALL_RPT_V1 (legacy view),” on page 81
Section 6.1.51, “EVENTS_ALL_V (legacy view),” on page 81
Section 6.1.52, “EVENTS_RPT_V (legacy view),” on page 81
Section 6.1.53, “EVENTS_RPT_V1 (legacy view),” on page 81
Section 6.1.54, “EVENTS_RPT_V2,” on page 81
Section 6.1.55, “EVENTS_RPT_V3,” on page 86
Section 6.1.56, “EVT_AGENT_RPT_V,” on page 90
Section 6.1.57, “EVT_AGENT_RPT_V3,” on page 91
Section 6.1.58, “EVT_ASSET_RPT_V,” on page 91
Section 6.1.59, “EVT_ASSET_RPT_V3,” on page 93
Section 6.1.60, “EVT_DEST_EVT_NAME_SMRY_1_RPT_V,” on page 94
Section 6.1.61, “EVT_DEST_SMRY_1_RPT_V,” on page 94
Section 6.1.62, “EVT_DEST_TXNMY_SMRY_1_RPT_V,” on page 95
Section 6.1.63, “EVT_NAME_RPT_V,” on page 95
Section 6.1.64, “EVT_PORT_SMRY_1_RPT_V,” on page 96
56Sentinel 6.1 Rapid Deployment Reference Guide
Section 6.1.65, “EVT_PRTCL_RPT_V,” on page 96
Section 6.1.66, “EVT_PRTCL_RPT_V3,” on page 97
Section 6.1.67, “EVT_RSRC_RPT_V,” on page 97
Section 6.1.68, “EVT_SEV_SMRY_1_RPT_V,” on page 97
Section 6.1.69, “EVT_SRC_COLLECTOR_RPT_V,” on page 98
Section 6.1.70, “EVT_SRC_GRP_RPT_V,” on page 98
Section 6.1.71, “EVT_SRC_MGR_RPT_V,” on page 99
Section 6.1.72, “EVT_SRC_OFFSET_RPT_V,” on page 99
Section 6.1.73, “EVT_SRC_RPT_V,” on page 99
Section 6.1.74, “EVT_SRC_SMRY_1_RPT_V,” on page 100
Section 6.1.75, “EVT_SRC_SRVR_RPT_V,” on page 101
Section 6.1.76, “EVT_TXNMY_RPT_V,” on page 101
Section 6.1.77, “EVT_USR_RPT_V,” on page 102
Section 6.1.78, “EVT_XDAS_TXNMY_RPT_V,” on page 102
Section 6.1.79, “EXTERNAL_DATA_RPT_V,” on page 102
novdocx (en) 13 May 2009
Section 6.1.80, “HIST_CORRELATED_EVENTS_RPT_V (legacy view),” on page 103
Section 6.1.81, “HIST_EVENTS_RPT_V (legacy view),” on page 103
Section 6.1.82, “IMAGES_RPT_V,” on page 103
Section 6.1.83, “INCIDENTS_ASSETS_RPT_V,” on page 103
Section 6.1.84, “INCIDENTS_EVENTS_RPT_V,” on page 104
Section 6.1.85, “INCIDENTS_RPT_V,” on page 104
Section 6.1.86, “INCIDENTS_VULN_RPT_V,” on page 105
Section 6.1.87, “L_STAT_RPT_V,” on page 105
Section 6.1.88, “LOGS_RPT_V,” on page 106
Section 6.1.89, “MSSP_ASSOCIATIONS_V,” on page 106
Section 6.1.90, “NETWORK_IDENTITY_RPT_V,” on page 106
Section 6.1.91, “ORGANIZATION_RPT_V,” on page 107
Section 6.1.92, “PERSON_RPT_V,” on page 107
Section 6.1.93, “PHYSICAL_ASSET_RPT_V,” on page 107
Section 6.1.94, “PRODUCT_RPT_V,” on page 108
Section 6.1.95, “ROLE_RPT_V,” on page 108
Section 6.1.96, “RPT_LABELS_RPT_V,” on page 109
Section 6.1.97, “SENSITIVITY_RPT_V,” on page 109
Section 6.1.98, “SENTINEL_HOST_RPT_V,” on page 109
Section 6.1.99, “SENTINEL_PLUGIN_RPT_V,” on page 110
Section 6.1.100, “SENTINEL_RPT_V,” on page 110
Section 6.1.101, “STATES_RPT_V,” on page 110
Section 6.1.102, “UNASSIGNED_INCIDENTS_RPT_V,” on page 111
Sentinel 6.1 Rapid Deployment Database Views for PostgreSQL57
Section 6.1.103, “USERS_RPT_V,” on page 111
Section 6.1.104, “USR_ACCOUNT_RPT_V,” on page 112
Section 6.1.105, “USR_IDENTITY_EXT_ATTR_RPT_V,” on page 113
Section 6.1.106, “USR_IDENTITY_RPT_V,” on page 113
Section 6.1.107, “VENDOR_RPT_V,” on page 114
Section 6.1.108, “VULN_CALC_SEVERITY_RPT_V,” on page 114
Section 6.1.109, “VULN_CODE_RPT_V,” on page 114
Section 6.1.110, “VULN_INFO_RPT_V,” on page 115
Section 6.1.111, “VULN_RPT_V,” on page 115
Section 6.1.112, “VULN_RSRC_RPT_V,” on page 116
Section 6.1.113, “VULN_RSRC_SCAN_RPT_V,” on page 117
Section 6.1.114, “VULN_SCAN_RPT_V,” on page 117
Section 6.1.115, “VULN_SCAN_VULN_RPT_V,” on page 118
Section 6.1.116, “VULN_SCANNER_RPT_V,” on page 118
Section 6.1.117, “WORKFLOW_DEF_RPT_V,” on page 118
novdocx (en) 13 May 2009
Section 6.1.118, “WORKFLOW_INFO_RPT_V,” on page 119
6.1.1 ACTVY_PARM_RPT_V
View contains information about iTRAC activities.
Column NameDatatypeComment
ACTVY_PARM_IDuuidActivity parameter identifier
ACTVY_IDuuidActivity identifier
PARM_NAMEcharacter varying(255)Activity Parameter name
PARM_TYP_CDcharacter varying(1)Activity parameter type code
DATA_TYPcharacter varying(50)Activity parameter data type
DATA_SUBTYPcharacter varying(50)Activity parameter data subtype
FEED_DATE_CREATEDtimestamp with time zoneDate of the Feed that carried
information on this product
Sentinel 6.1 Rapid Deployment Database Views for PostgreSQL63
Column NameDatatypeComment
FEED_DATE_UPDATEDtimestamp with time zoneDate of the Feed that
uptimestamp with time zoned
information on this product
ACTIVE_FLAGintegerReserved for future use
DATE_CREATEDtimestamp with time zoneDate the entry was created
DATE_MODIFIEDtimestamp with time zoneDate the entry was modified
CREATED_BYintegerUser who created object
MODIFIED_BYintegerUser who last modified object
6.1.12 ADV_PRODUCT_SERVICE_PACK_RPT_V
View references ADV_PRODUCT_SERVICE _PACK table that stores Advisor service pack
information, such as service pack name, version ID and timestamp with time zone.
novdocx (en) 13 May 2009
Column NameDatatypeComment
SERVICE_PACK_IDintegerService Pack ID
VERSION_IDintegerVersion ID
SERVICE_PACK_NAMEcharacter varying(32)Name of the Service Pack
FEED_DATE_CREATEDtimestamp with time zoneDate of the Feed that carried
information on this product
FEED_DATE_UPDATEDtimestamp with time zoneDate of the Feed that uptimestamp
with time zoned information on this
product
ACTIVE_FLAGintegerReserved for future use
BEGIN_EFFECTIVE_DATE timestamp with time zoneDate from which the entry is valid
END_EFFECTIVE_DATEtimestamp with time zoneDate until which the entry is valid
DATE_CREATEDtimestamp with time zoneDate the entry was created
DATE_MODIFIEDtimestamp with time zoneDate the entry was modified
CREATED_BYintegerUser who created object
MODIFIED_BYintegerUser who last modified object
6.1.13 ADV_PRODUCT_VERSION_RPT_V
View references ADV_PRODUCT_VERSION table that stores Advisor product version
information, such as version name, product and version ID.
Column NameDatatypeComment
VERSION_IDintegerVersion ID
64Sentinel 6.1 Rapid Deployment Reference Guide
Column NameDatatypeComment
PRODUCT_IDintegerProduct ID
VERSION_NAMEcharacter varying(128)Version Name of the product
FEED_DATE_CREATED timestamp with time zone Date of the feed that carried the information
on the entry
FEED_DATE_UPDATED timestamp with time zone Date of the feed that carried the
uptimestamp with time zone on the entry
ACTIVE_FLAGintegerReserved for future use
DATE_CREATEDtimestamp with time zone Date the entry was created
DATE_MODIFIEDtimestamp with time zone Date the entry was modified
CREATED_BYintegerUser who created object
MODIFIED_BYintegerUser who last modified object
6.1.14 ADV_VENDOR_RPT_V
novdocx (en) 13 May 2009
View references ADV_VENDOR table that stores Advisor address information.
Column NameDatatypeComment
VENDOR_IDintegerID of the vendor
VENDOR_NAMEcharacter varying(128)Name of the vendor
CONTACT_PERSONcharacter varying(128)Contains the contact person name for the
vendor
ADDRESS_LINE_1character varying(128)Address of the vendor
ADDRESS_LINE_2character varying(128)Address of the vendor
ADDRESS_LINE_3character varying(128)Address of the vendor
ADDRESS_LINE_4character varying(128)Address of the vendor
CITYcharacter varying(128)City of the vendor
STATEcharacter varying(128)State of the vendor
COUNTRYcharacter varying(128)Country of the vendor
ZIP_CODEcharacter varying(128)Zip code of the vendor
URLcharacter varying(256)Web URL of the vendor
PHONEcharacter varying(32)Contact number of the vendor
FAXcharacter varying(32)Fax number of the vendor
EMAILcharacter varying(128)Email of the vendor
PAGERcharacter varying(32)Pager of the vendor
FEED_DATE_CREATEDtimestamp with time
zone
Date of the feed that carried the information
on the entry
Sentinel 6.1 Rapid Deployment Database Views for PostgreSQL65
Column NameDatatypeComment
novdocx (en) 13 May 2009
FEED_DATE_UPDATEDtimestamp with time
zone
ACTIVE_FLAGintegerReserved for future use
DATE_CREATEDtimestamp with time
zone
DATE_MODIFIEDtimestamp with time
zone
CREATED_BYintegerUser who created object
MODIFIED_BYintegerUser who last modified object
Date of the feed that carried the uptimestamp
with time zone on the entry
Date the entry was created
Date the entry was modified
6.1.15 ADV_VULN_KB_RPT_V
Column NameDatatypeComment
VULN_KB_IDintegerKnowledge base ID mapping CVE_ID,
OSVDB_ID, BUGTRAQ_ID
CVE_IDcharacter varying(10)CVE ID for the related vulnerability
OSVDB_IDintegerOSVDB ID for the related vulnerability
BUGTRAQ_IDintegerBugtraq id for the related vulnerability
DATE_PUBLISHEDtimestamp with time zoneDate the entry was published
DATE_UPDATEDtimestamp with time zoneDate the entry was uptimestamp with time zoned
DATE_CREATEDtimestamp with time zoneDate the entry was created
DATE_MODIFIEDtimestamp with time zoneDate the entry was modified
CREATED_BYintegerUser who created object
MODIFIED_BYintegerUser who last modified object
6.1.16 ADV_VULN_PRODUCT_RPT_V
View references ADV_VULN_PRODUCT table that stores Advisor vulnerability attack ID and
service pack ID.
Column NameDatatypeComment
SERVICE_PACK_IDintegerContains the service pack id
ATTACK_IDintegerContains the attack id
DATE_CREATEDtimestamp with time
zone
DATE_MODIFIEDtimestamp with time
zone
Date the entry was created
Date the entry was modified
66Sentinel 6.1 Rapid Deployment Reference Guide
Column NameDatatypeComment
CREATED_BYintegerUser who created object
MODIFIED_BYintegerUser who last modified object
6.1.17 ADV_VULN_SIGNATURES
Column NameDatatypeComment
VULN_KEYintegerVulnerability key
VULN_SCANNER_NAMEcharacter varying(128)Vulnerability scanner name
VULN_NAMEcharacter varying(256)Vulnerability name
VULN_IDcharacter varying(256)Vulnerability ID
6.1.18 ANNOTATIONS_RPT_V
novdocx (en) 13 May 2009
View references ANNOTATIONS table that stores documentation or notes that can be associated
with objects in the SentinelRD system such as cases and incidents.
DATE_CREATEDtimestamp with time zoneDate the entry was created
DATE_MODIFIEDtimestamp with time zoneDate the entry was modified
CREATED_BYintegerUser who created object
MODIFIED_BYintegerUser who last modified object
6.1.44 ESEC_DISPLAY_RPT_V
View references ESEC_DISPLAY table that stores displayable properties of objects. Currently used
in renaming meta-tags. Used with Event Configuration (Business Relevance).
novdocx (en) 13 May 2009
Column NameDatatypeComment
DISPLAY_OBJECTcharacter varying(32)The parent object of the property
TAGcharacter varying(32)The native tag name of the property
LABELcharacter varying(32)The display string of tag.
POSITIONintegerPosition of tag within display.
WIDTHintegerThe column width
ALIGNMENTintegerThe horizontal alignment
FORMATintegerThe enumerated formatter for displaying the
property
ENABLEDbooleanIndicates if the tag is shown.
TYPEintegerIndicates datatype of tag.
1 = string
2 = ulong
3 = timestamp with time zone
4 = uuid
5 = ipv4
DESCRIPTIONcharacter varying(255)Textual description of the tag
DATE_CREATEDtimestamp with time zone Date the entry was created
DATE_MODIFIEDtimestamp with time zone Date the entry was modified
CREATED_BYintegerUser who created object
MODIFIED_BYintegerUser who last modified object
REF_CONFIGcharacter varying(4000)Referential data configuration
78Sentinel 6.1 Rapid Deployment Reference Guide
6.1.45 ESEC_PORT_REFERENCE_RPT_V
View references ESEC_PORT_REFERENCE table that stores industry standard assigned port
numbers.
SOURCE_IPintegerSource IP address in numeric format
SOURCE_IP_DOTTEDcharacter varyingSource IP in dotted format
SOURCE_HOST_NAMEcharacter varying(255)Source host name
SOURCE_PORTcharacter varying(32)Source port
novdocx (en) 13 May 2009
DESTINATION_IPintegerDestination IP address in numeric
format
DESTINATION_IP_DOTTEDcharacter varyingDestination in dotted format
DESTINATION_HOST_NAME character varying(255)Destination host name
DESTINATION_PORTcharacter varying(32)Destination port
SOURCE_USER_NAMEcharacter varying(255)Source user name
DESTINATION_USER_NAME character varying(255)Destination user name
FILE_NAMEcharacter varying(1000)File name
EXTENDED_INFOcharacter varying(1000)Extened information
CUSTOM_TAG_1character varying(255)Customer Tag 1
CUSTOM_TAG 2character varying(255)Customer Tag 2
CUSTOM_TAG 3integerCustomer Tag 3
RESERVED_TAG_1character varying(255)Reserved Tag 1
Reserved for future use by Novell. This
field is used for Advisor information
concerning attack descriptions.
RESERVED_TAG_2character varying(255)Reserved for future use by Novell. Use
of this field for any other purpose might
result in data being overwritten by
future functionality.
RESERVED_TAG_3integerReserved for future use by Novell. Use
VULNERABILITY_RATINGintegerVulnerability rating
82Sentinel 6.1 Rapid Deployment Reference Guide
of this field for any other purpose might
result in data being overwritten by
future functionality.
Column NameDatatypeComment
CRITICALITY_RATINGintegerCriticality rating
DATE_CREATEDtimestamp with time zoneDate the entry was created
DATE_MODIFIEDtimestamp with time zoneDate the entry was modified
CREATED_BYintegerUser who created object
MODIFIED_BYintegerUser who last modified object
RV01 - 10integerReserved Value 1 - 10
Reserved for future use by Novell. Use
of this field for any other purpose might
result in data being overwritten by
future functionality.
RV11 - 20timestamp with time zoneReserved Value 11 - 20
Reserved for future use by Novell. Use
of this field for any other purpose might
result in data being overwritten by
future functionality.
novdocx (en) 13 May 2009
RV21 - 25uuidReserved Value 21 - 25
Reserved for future use by Novell to
store UUIDs. Use of this field for any
other purpose might result in data being
overwritten by future functionality.
RV26 - 31character varying(255)Reserved Value 26 - 31
Reserved for future use by Novell. Use
of this field for any other purpose might
result in data being overwritten by
future functionality.
RV33character varying(255)Reserved Value 33
Reserved for EventContex
Use of this field for any other purpose
might result in data being overwritten
by future functionality.
RV34character varying(255)Reserved Value 34
Reserved for SourceThreatLevel
Use of this field for any other purpose
might result in data being overwritten
by future functionality.
RV35character varying(255)Reserved Value 35
Reserved for SourceUserContext.
Use of this field for any other purpose
might result in data being overwritten
by future functionality.
Sentinel 6.1 Rapid Deployment Database Views for PostgreSQL83
Column NameDatatypeComment
RV36character varying(255)Reserved Value 36
Reserved for DataContext.
Use of this field for any other purpose
might result in data being overwritten
by future functionality.
RV37character varying(255)Reserved Value 37
Reserved for SourceFunction.
Use of this field for any other purpose
might result in data being overwritten
by future functionality.
RV38character varying(255)Reserved Value 38
Reserved for
SourceOperationalContext.
novdocx (en) 13 May 2009
Use of this field for any other purpose
might result in data being overwritten
by future functionality.
RV40 - 43character varying(255)Reserved Value 40 - 43
Reserved for future use by Novell. Use
of this field for any other purpose might
result in data being overwritten by
future functionality.
RV44character varying(255)Reserved Value 44
Reserved for DestinationThreatLevel.
Use of this field for any other purpose
might result in data being overwritten
by future functionality.
RV45character varying(255)Reserved Value 45
Reserved for DestinationUserContext.
Use of this field for any other purpose
might result in data being overwritten
by future functionality.
RV46character varying(255)Reserved Value 46
Reserved for VirusStatus.
84Sentinel 6.1 Rapid Deployment Reference Guide
Use of this field for any other purpose
might result in data being overwritten
by future functionality.
Column NameDatatypeComment
RV47character varying(255)Reserved Value 47
Reserved for future use by Novell. Use
of this field for any other purpose might
result in data being overwritten by
future functionality.
RV48character varying(255)Reserved Value 48
Reserved for
DestinationOperationalContext.
Use of this field for any other purpose
might result in data being overwritten
by future functionality.
RV49character varying(255)Reserved Value 49
Reserved for future use by Novell. Use
of this field for any other purpose might
result in data being overwritten by
future functionality.
novdocx (en) 13 May 2009
TAXONOMY_IDbigintTaxonomy identifier
REFERENCE_ID_01 - 20bigintReserved for future use by Novell. Use
of this field for any other purpose might
result in data being overwritten by
future functionality.
CV01 - 10integerCustom Value 1 - 10
Reserved for use by Customer,
typically for association of Business
relevant data.
CV11 - 20timestamp with time zoneCustom Value 11 - 20
Reserved for use by Customer,
typically for association of Business
relevant data.
CV21 - 29character varying(255)Custom Value 21 – 29
Reserved for use by Customer,
typically for association of Business
relevant data.
CV30 - 34character varying(4000)Custom Value 30 – 34
Reserved for use by Customer,
typically for association of Business
relevant data.
CV35 – 100character varying(255)Custom Value 35 – 100
Reserved for use by Customer,
typically for association of Business
relevant data.
Sentinel 6.1 Rapid Deployment Database Views for PostgreSQL85
6.1.55 EVENTS_RPT_V3
This is the primary reporting view for SentinelRD. This view contains current event and historical
events.
Column NameDatatypeComment
EVENT_IDuuidEvent identifier
RESOURCE_NAMEcharacter varying(255)Resource name
SUB_RESOURCEcharacter varying(255)Subresource name
SEVERITYintegerEvent severity
EVENT_PARSE_TIMEtimestamp with time zoneEvent time
EVENT_DATETIMEtimestamp with time zoneEvent date time
EVENT_DEVICE_TIMEtimestamp with time zoneEvent device time
SENTINEL_PROCESS_TIMEtimestamp with time zoneSentinelRD process time
novdocx (en) 13 May 2009
BEGIN_TIMEtimestamp with time zoneEvents begin time
END_TIMEtimestamp with time zoneEvents end time
REPEAT_COUNTintegerRepeat count
TARGET_SERVICE_PORTintegerTarget service port
INIT_SERVICE_PORTintegerService port
BASE_MESSAGEcharacter varying(4000)Base message
EVENT_NAMEcharacter varying(255)Event name
EVENT_TIMEcharacter varying(255)Event time
CUST_IDbigintCustomer identifier
INIT_ASSET_IDbigintInitiator asset identifier
TARGET_ASSET_IDbigintTarget asset identifier
AGENT_IDbigintAgent identifier
PROTOCOL_IDbigintProtocol identifier
ARCHIVE_IDbigintArchive id
INIT_IPintegerIP
INIT_IP_DOTTEDcharacter varyingIP dotted
INIT_HOST_NAMEcharacter varying(255)Host name
INIT_SERVICE_PORT_NAMEcharacter varying(32)Service port name
TARGET_IPintegerTarget IP
TARGET_IP_DOTTEDcharacter varyingDotted Target IP
TARGET_HOST_NAMEcharacter varying(255)Target host name
86Sentinel 6.1 Rapid Deployment Reference Guide
Column NameDatatypeComment
TARGET_SERVICE_PORT_NAMEcharacter varying(32)Target service port name
INIT_USER_NAMEcharacter varying(255)User name
TARGET_USER_NAMEcharacter varying(255)Target user name
FILE_NAMEcharacter varying(1000)File name
EXTENDED_INFOcharacter varying(1000)Extended info
INIT_USER_IDcharacter varying(255)Initiator user ID
INIT_USER_IDENTITYuuidInitiator user identity
TARGET_USER_IDcharacter varying(255)Target user ID
TARGET_USER_IDENTITYuuidTarget user identity
EFFECTIVE_USER_NAMEcharacter varying(255)Effective user name
EFFECTIVE_USER_IDcharacter varying(255)Effective user ID
novdocx (en) 13 May 2009
EFFECTIVE_USER_DOMAINcharacter varying(255)Effective user domain
TARGET_TRUST_NAMEcharacter varying(255)Target trust name
TARGET_TRUST_IDcharacter varying(255)Target trust ID
DATE_CREATEDtimestamp with time zoneDate the entry was created
90Sentinel 6.1 Rapid Deployment Reference Guide
H - host-based
N - network-based
V - virus
O – other
Identifier (UUID)
Column NameDatatypeComment
DATE_MODIFIEDtimestamp with time zoneDate the entry was modified
CREATED_BYintegerUser who created object
MODIFIED_BYintegerUser who last modified object
6.1.57 EVT_AGENT_RPT_V3
View references EVT_AGENT table that stores information about Collectors. The column names in
this view reflects the name change of Sensor to Observer. This view is designed for use in
SentinelRD.
Column NameDatatypeComment
AGENT_IDbigintCollector identifier
CUST_IDbigintCustomer identifier
AGENTcharacter varying(64)Collector
novdocx (en) 13 May 2009
PORTcharacter varying(64)Port
REPORTER_HOST_NAMEcharacter varying(255)Reporter host name
PRODUCT_NAMEcharacter varying(255)Product name
OBSERVER_HOST_NAMEcharacter varying(255)Observer host name