Step 10. Create and Assign Actions

For an introduction to Actions, see What are Actions?.

By default, the TLC installer creates two Tripwire-defined Actions:

An enabled Email Action configured to send email alerts to the address entered for the Administrator account when TLC was installed.

A disabled Notification Action with no defined notifications.

In this step, you will configure these Actions and create your own. You will then assign an Action as an Output in a new Correlation Rule.

To configure the Tripwire-defined Email Action or Notification Action, or to create a new Action:

1. In the side bar, select Resources >Configuration ManagerConfiguration Manager.
2. In the side bar of the Configuration Manager, select CorrelationCorrelation > ActionsActions.
3. To create an Action, clickAddCreate Action.

To edit an existing Action, double-click the Action in the workspace.

4. Complete the Action properties dialog and click OK.

For further details, see Working with Actions.

To create a new Correlation Rule with one of your Actions as an Output:

1. In the side bar, select Resources >Configuration ManagerConfiguration Manager.
2. In the side bar of the Configuration Manager, select CorrelationCorrelation >Correlation RulesRules.
3. ClickAddCreate rule.
4. In the Correlation Rule properties dialog, configure the Input, Decision(s), and Output(s) for the rule. (Your Actions are available in the Outputs > Actions group in the Symbols panel.)

For further details, see Working with Correlation Rules.

Tips 

If you complete the configuration steps for your TLC environment and the Audit Logger does not contain the expected log messages from a Log Source, you should first confirm that the Log Source is properly configured. For example, by default, a Windows system does not audit successful logins. Therefore, to send successful login events to TLC, you must first enable auditing of successful logins on the Windows system.

If a Log Source has been properly configured, and you still are not seeing the expected log messages in the Audit Logger, enable the Log 'Not Logged Events' to File setting in the Primary Manager's properties dialog. Then, review the contents of the logs\notlogged.log file in the Manager's installation directory. For further details, see Changing a Manager's Log Settings.