IBM Domino Administrator 9.0.1 Social Edition Help

ADMINISTERING

Creating Security probes
You can create a Security probe.

Procedure

1. From the Domino® Administrator, click the Files tab.

2. Open the Monitoring Configuration database (EVENTS4.NSF).

3. Choose DDM Configuration.

4. Choose any DDM probe view, and then click New DDM Probe.

5. Choose Security.

Table 1. Probe selection

Field	Action
Probe Subtype	Choose one: Best Practices Configuration Database ACL Database Review Review
Probe Description	Type a description of the new probe.

Table 2. Probe options

Field Action

Which server should run this probe? Specify the server that will run this probe.

Which servers should run this probe? Choose one:

All servers in the domain -- Runs the probe on all servers in the domain.
Special target servers -- Specify the type of servers to run the probe, such as POP3 servers or the administration server for the Domino Directory.
Only the following servers -- Specify the servers on which the Security probe will run.

Which servers should be probed? Choose one:

All servers in the domain -- Probes all servers in the domain.
Only the following servers: -- Probes the servers that you specify.

Which servers' security configuration should be probed? Choose one:

All servers in the domain -- The security probe runs against the security configuration for all servers in the domain.
Only the following servers -- Security configurations are probed for the servers you specify.

Select one or more databases to probe Specify the names of the databases to probe. The default is NAMES.NSF.

Which servers should not be probed? Specify the names of servers that are not to be probed.

Table 3. Specific options

Field Action

Which server should be used as the guideline server? Specify the name of the server to use as the "good" server against which other Server documents are verified.

Which server settings should be compared to the guideline server settings? Choose the settings you want to compare to those in the Server document for the server being probed. Check as many settings as apply.

Generate an event when any of the entries listed have access greater than "access level." Complete this field for as many access levels as necessary. Specify the people, groups, and servers that apply to each specific access level.

Which server settings should be validated? Specify the individual server settings to validate against a set of "good" settings.

Review all ACL members whose privileges are equal to or greater than Specify the ACL privilege level from which the probe should begin checking ACL member privileges. Beginning with the ACL privilege you select, all member privileges at that level and higher are reviewed by the security probe.

Review the following database properties Specify the database properties to be reviewed by the security probe.

Review agents defined as Specify one or both of these agents to be reviewed by the security probe:

Restricted
Unrestricted

Which server settings should be reported? Specify the individual settings from the Server document that are to be reported. Select Directory Profile Note and Security settings in my configuration document if you want the settings in those documents reviewed by the probe.

Table 4. Schedule options

Field Action

How often should this probe run? Choose one:

Run multiple times per day -- If you choose this option, complete the field Defined schedule.
Daily -- If you choose this option, complete the field On which days should this probe run .
Weekly -- If you choose this option, complete the field On which day of the week should this probe run.
Monthly -- If you choose this option, complete the field On which day of the month should this probe run.

Defined schedule Specify the number of minutes between each run of the probe.

Should this probe run twenty-four hours per day, seven days per week? Choose one:

Yes -- Run the probe continuously.
No -- The probe runs on the days and at the times that you specify. After you choose this option, create a schedule in the On which days should this probe run? field.

On which days should this probe run? Choose the days on which to run the probe.

On which day of the week should this probe run? Specify the day of the week on which to run this probe.

On which day of the month should this probe run? Enter the day of the month on which to run this probe. For example, enter 15 to run the probe on the 15th day of the month.

During which hours of the day should this probe run? Specify the start time in the From field, and the end time in the To field. The probe will run during those hours.

At what time should this probe run Specify the time that you want the probe to run.

How should missed probes be handled? Choose one:

Ignore missed probe -- The missed probe is not run or rescheduled.
Run missed probe at startup -- The next time that the server starts, the missed probe runs.
Run missed probe at next time range -- The missed probe reschedules itself once. For example, if a probe scheduled to run every Tuesday at 5:00 AM fails to run, the probe reschedules itself to run on Wednesday at 5:00 AM. After that, the probe returns to its regular schedule.

Related concepts
Security probes
DDM probes
Maintaining DDM Probes

Feedback on Help or Product Usability?

Help on Help

All Help Contents

Feedback on Help or Usability?

Help on Help

All Help Contents

Field	Action
Which server should run this probe?	Specify the server that will run this probe.
Which servers should run this probe?	Choose one: All servers in the domain -- Runs the probe on all servers in the domain. Special target servers -- Specify the type of servers to run the probe, such as POP3 servers or the administration server for the Domino Directory. Only the following servers -- Specify the servers on which the Security probe will run.
Which servers should be probed?	Choose one: All servers in the domain -- Probes all servers in the domain. Only the following servers: -- Probes the servers that you specify.
Which servers' security configuration should be probed?	Choose one: All servers in the domain -- The security probe runs against the security configuration for all servers in the domain. Only the following servers -- Security configurations are probed for the servers you specify.
Select one or more databases to probe	Specify the names of the databases to probe. The default is NAMES.NSF.
Which servers should not be probed?	Specify the names of servers that are not to be probed.

Field	Action
Which server should be used as the guideline server?	Specify the name of the server to use as the "good" server against which other Server documents are verified.
Which server settings should be compared to the guideline server settings?	Choose the settings you want to compare to those in the Server document for the server being probed. Check as many settings as apply.
Generate an event when any of the entries listed have access greater than "access level."	Complete this field for as many access levels as necessary. Specify the people, groups, and servers that apply to each specific access level.
Which server settings should be validated?	Specify the individual server settings to validate against a set of "good" settings.
Review all ACL members whose privileges are equal to or greater than	Specify the ACL privilege level from which the probe should begin checking ACL member privileges. Beginning with the ACL privilege you select, all member privileges at that level and higher are reviewed by the security probe.
Review the following database properties	Specify the database properties to be reviewed by the security probe.
Review agents defined as	Specify one or both of these agents to be reviewed by the security probe: Restricted Unrestricted
Which server settings should be reported?	Specify the individual settings from the Server document that are to be reported. Select Directory Profile Note and Security settings in my configuration document if you want the settings in those documents reviewed by the probe.

Field	Action
How often should this probe run?	Choose one: Run multiple times per day -- If you choose this option, complete the field Defined schedule. Daily -- If you choose this option, complete the field On which days should this probe run . Weekly -- If you choose this option, complete the field On which day of the week should this probe run. Monthly -- If you choose this option, complete the field On which day of the month should this probe run.
Defined schedule	Specify the number of minutes between each run of the probe.
Should this probe run twenty-four hours per day, seven days per week?	Choose one: Yes -- Run the probe continuously. No -- The probe runs on the days and at the times that you specify. After you choose this option, create a schedule in the On which days should this probe run? field.
On which days should this probe run?	Choose the days on which to run the probe.
On which day of the week should this probe run?	Specify the day of the week on which to run this probe.
On which day of the month should this probe run?	Enter the day of the month on which to run this probe. For example, enter 15 to run the probe on the 15th day of the month.
During which hours of the day should this probe run?	Specify the start time in the From field, and the end time in the To field. The probe will run during those hours.
At what time should this probe run	Specify the time that you want the probe to run.
How should missed probes be handled?	Choose one: Ignore missed probe -- The missed probe is not run or rescheduled. Run missed probe at startup -- The next time that the server starts, the missed probe runs. Run missed probe at next time range -- The missed probe reschedules itself once. For example, if a probe scheduled to run every Tuesday at 5:00 AM fails to run, the probe reschedules itself to run on Wednesday at 5:00 AM. After that, the probe returns to its regular schedule.