Logged Actions; Viewing The Log File - Juniper SECURITY THREAT RESPONSE MANAGER 2008.2 Administration Manual

Deploying Changes
Viewing STRM
Audit Logs

Logged Actions

Table 1-1 Administrative Console Menu Options (continued)
Menu Option Sub-Menu
STRM Restart
Help Help and Support
About STRM
Administration Console
The Administration Console provides several toolbar options including:
Table 1-2 Administration Console Toolbar Options
Icon Description
Opens the deployment editor interface.
Deploys all changes made through the Administration Console.
Once you update your configuration settings using the Administration Console,
you must save those changes to the staging area. You must either manually
deploy all changes using the Deploy menu option or, upon exit, a window appears
prompting you to deploy changes before you exit. All deployed changes are then
enforced throughout your deployment.
Using the Administration Console menu, you can deploy changes as follows:
Deploy All - Deploys all configuration settings to your deployment.
•
• Deploy configuration changes - Deploys any configuration changes from the
current session to your deployment.
Changes made by STRM users are recorded in the audit logs. You can view the
audit logs to monitor changes to STRM and the users performing those changes.
All audit logs are stored in plain text and are archived and compressed once the
audit log file reaches a size of 200 MB. The current log file is named
Once the file reaches a size of 200 MB, the file is compressed and renamed as
follows:
audit.1.gz, audit.2.gz
time a log file is archived. STRM stores up to 50 archived log files.
This section provides information on using the audit logs including:
Logged Actions
•
•

Viewing the Log File

STRM logs the following categories of actions in the audit log file:
STRM Administration Guide
Description
Restarts the STRM application.
Opens user documentation.
Displays version information.
, etc with the file number incrementing each
Deploying Changes
audit.log
5
.