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
Loading...
+ 106 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.