Configuring pm, Setting schedules – Fortinet FortiDB User Manual

Page 12

Advertising
background image

FortiDB Version 3.2 Privilege Monitor User Guide

10

15-32000-81364-20081219

Setting Schedules

Configuring PM

Configuring PM

There are three general parts of Privilege Monitor to configure:

• Schedules

• Receivers for Alert Email

• Guarded Items

Setting Schedules

Scheduling is configured based upon two criteria:

• The type of time source to use for scheduling: timer- or calendar-based. For a

timer-based schedule, you set a time interval for the monitoring. For a
calendar-based schedule, you choose to have the monitoring run at a specific
day and/or time. You can also combine the two.

• The scope of the schedule:

• Module level: The entire PM module; a schedule that applies to all the
databases, System Views, and UDRs

• Database level: A particular database and its System Views, and UDRs
within the module

• Guarded Item

1

level: System Views, or UDRs within the database

If no other schedule is specified, the default-monitoring

2

schedule is every ten

minutes. This applies to all databases and their contained System Views, and
UDRs. If a Module level schedule is the only one set, it applies to all databases
within that module. If a database level schedule is set, it will override any module
level schedule for that particular database. If a Guarded Item-level schedule is set,
it will override any module- or database-level schedule.

1.

Guarded Items are database objects (here System Views that you monitor directly) policies,

or rules that you employ to monitor those objects. While sometimes used interchangeably, a policy is a

best-business practice and a rule is the FortiDB-MA implementation of a policy.
2.

A default schedule is one used for monitoring in the absence of any other overriding

schedule.

Advertising