- play_arrow What's New for Administrators
- play_arrow Overview of JSA Administration
- play_arrow User Management
- play_arrow License Management
- play_arrow System Management
- System Management
- System Health Information
- JSA Component Types
- Data Nodes
- Network Interface Management
- JSA System Time
- NAT-Enabled Networks
- Off-site Hosts Management
- Managed Hosts
- Configuration Changes in your JSA Environment
- Deploying Changes
- Restarting the Event Collection Service
- Shutting Down a System
- Restarting a System
- Collecting Log Files
- Changing the Root Password on Your JSA Console
- Resetting SIM
- play_arrow Event Data Processing in JSA
- Event Data Processing in JSA
- DSM Editor Overview
- Properties in the DSM Editor
- Property Configuration in the DSM Editor
- Opening the DSM Editor
- Configuring a Log Source Type
- Configuring Property Autodetection for Log Source Types
- Configuring Log Source Autodetection for Log Source Types
- Configuring DSM Parameters for Log Source Types
- Custom Log Source Types
- Custom Property Definitions in the DSM Editor
- Event Mapping
- Exporting Contents from the DSM Editor
- play_arrow Using Reference Data in JSA
- play_arrow User Information Source Configuration
- play_arrow Juniper Networks X-Force Integration
- play_arrow Managing Authorized Services
- play_arrow Backup and Recovery
- play_arrow Flow Sources Management
- play_arrow Remote Networks and Services Configuration
- play_arrow Server Discovery
- play_arrow Domain Segmentation
- play_arrow Multitenant Management
- Multitenant Management
- User Roles in a Multitenant Environment
- Domains and Log Sources in Multitenant Environments
- Provisioning a New Tenant
- Monitoring License Usage in Multitenant Deployments
- Rules Management in Multitenant Deployments
- Network Hierarchy Updates in a Multitenant Deployment
- Retention Policies for Tenants
- play_arrow Asset Management
- play_arrow Configuring JSA to Forward Data to Other Systems
- Forward Data to Other Systems
- Adding Forwarding Destinations
- Configuring Forwarding Profiles
- Configuring Routing Rules to Forward Data
- Using Custom Rules and Rule Responses to Forward Data
- Configuring Routing Rules to Use the JSA Data Store
- Viewing Forwarding Destinations
- Viewing and Managing Forwarding Destinations
- Viewing and Managing Routing Rules
- play_arrow Event Store and Forward
- play_arrow Security Content
- play_arrow SNMP Trap Configuration
- play_arrow Protect Sensitive Data
- play_arrow Log Files
- play_arrow Event Categories
- play_arrow Common Ports and Servers Used by JSA
- play_arrow RESTful API
Custom Offense Close Reasons
You can manage the options listed in the Reason for Closing list box on the Offenses tab.
When a user closes an offense on the Offenses tab, the Close Offense window is displayed. The user is prompted to select a reason from the Reason for Closing list box. Three default options are listed:
False-positive, tuned
Non-issue
Policy violation
Administrators can add, edit, and delete custom offense close reasons from the Admin tab.
Adding a Custom Offense Close Reason
When you add a custom offense close reason, the new reason is listed on the Custom Close Reasons window and in the Reason for Closing list box on the Close Offense window of the Offenses tab.
The Custom Offense Close Reasons window provides the following parameters.
Parameter | Description |
|---|---|
Reason | The reason that is displayed in the Reason for Closing list box on the Close Offense window of the Offenses tab. |
Created by | The user that created this custom offense close reason. |
Date Created | The date and time of when the user created this custom offense close reason. |
On the navigation menu (
), click Admin.In the System Configuration section, click Custom Offense Close Reasons.
Click Add.
Type a unique reason for closing offenses. Reasons must be between 5 and 60 characters in length.
Click OK.
Your new custom offense close reason is now listed in the Custom Close Reasons window. The Reason for Closing list box on the Close Offense window of the Offenses tab also displays the custom reason you added.
Editing Custom Offense Close Reason
Editing a custom offense close reason updates the reason in the Custom Close Reasons window and the Reason for Closing list box on the Close Offense window of the Offenses tab.
On the navigation menu (
), click Admin.In the System Configuration section, click Custom Offense Close Reasons.
Select the reason you want to edit.
Click Edit.
Type a new unique reason for closing offenses. Reasons must be between 5 and 60 characters in length.
Click OK.
Deleting a Custom Offense Close Reason
Deleting a custom offense close reason removes the reason from the Custom Close Reasons window and the Reason for Closing list box on the Close Offense window of the Offenses tab.
On the navigation menu (
), click Admin.In the System Configuration section, click Custom Offense Close Reasons.
Select the reason you want to delete.
Click Delete.
Click OK.
