- play_arrow What's New for Users in JSA Vulnerability Manager 7.4.0
- play_arrow Installations and Deployments
- Installations and Deployments
- Vulnerability Backup and Recovery
- Ports Used for Communication Between JSA and JSA Vulnerability Manager Managed Hosts
- Options for Moving the Vulnerability Processor in Your JSA Vulnerability Manager Deployment
- Options for Adding Scanners to Your JSA Vulnerability Manager Deployment
- JSA Vulnerability Manager High-availability Scans
- Extending the JSA Vulnerability Manager Temporary License Period
- JSA Vulnerability Manager High-availability Scans
- play_arrow Overview Of JSA Vulnerability Manager
- play_arrow Vulnerability Scanning Strategy and Best Practices
- Vulnerability Scanning Strategy and Best Practices
- Scan Policy Types
- Scan Duration and Ports Scanning
- Tune Your Asset Discovery Configuration
- Tune Your Asset Discovery Performance
- Web Application Scanning
- Scanner Placement in Your Network
- Dynamic Scanning
- Network Bandwidth for Simultaneous Asset Scans
- Network Interface Cards on Scanners
- Vulnerability Management for Asset Owners
- Vulnerability Scan Notifications
- Triggering Scans of New Assets
- Configuring Environmental Risk for an Asset
- External Scanning FAQs
- play_arrow False Positives Management
- play_arrow Authenticated Patch Scans
- play_arrow Scanning on Windows-based Assets
- Scanning on Windows-based Assets
- Configuring an Authenticated Scan Of the Windows Operating System
- Remote Registry
- Enabling Remote Registry Access to Assets on the Windows Operating System
- Assigning Minimum Remote Registry Permissions
- Configuring WMI
- Setting Minimum DCOM Permissions
- Setting DCOM Remote Access Permissions
- Administrative Shares
- Enabling Administrative Shares
- Disabling Administrative Shares
- Manually Configuring NTLMv2 Authentication to Prevent Scan Failures
- play_arrow Vulnerability Exception Rules
- play_arrow Scan Investigations
- Scan Investigations
- Searching Scan Results
- Including Column Headings in Asset Searches
- Managing Scan Results
- Republishing Scan Results
- Asset Risk Levels and Vulnerability Categories
- Asset, Vulnerability, and Open Services Data
- Viewing the Status Of Asset Patch Downloads
- Vulnerability Risk and PCI Severity
- Troubleshooting Scan Issues
- Emailing Asset Owners When Vulnerability Scans Start and Stop
- play_arrow Management Of Your Vulnerabilities
- Management Of Your Vulnerabilities
- Common Vulnerability Scoring System (CVSS)
- Investigating Vulnerability Risk Scores
- Custom Risk Classification
- Searching Vulnerability Data
- Vulnerability Instances
- Network Vulnerabilities
- Asset Vulnerabilities
- Open Service Vulnerabilities
- Investigating the History Of a Vulnerability
- Reducing the Number Of False Positive Vulnerabilities
- Investigating High Risk Assets and Vulnerabilities
- Prioritizing High Risk Vulnerabilities by Applying Risk Policies
- Configuring Custom Display Colors for Risk Scores
- Identifying the Patch Status Of Your Vulnerabilities
- Removing Unwanted Vulnerability Data
- Configuring Vulnerability Data Retention Periods
- play_arrow Vulnerability Remediation
- play_arrow Vulnerability Reports
- play_arrow Scanning New Assets That Communicate with the Internet
- Scanning New Assets That Communicate with the Internet
- Creating an Asset Saved Search for New Assets
- Creating an On-demand Scan Profile
- Creating a Policy Monitor Question to Test for Internet Communication
- Monitoring Communication Between New Assets and the Internet
- Configuring an Offense Rule to Trigger a Scan
- play_arrow Security Software Integrations
- play_arrow IBM Security SiteProtector Integration
- play_arrow Vulnerability Research, News, and Advisories
- play_arrow JSA Vulnerability Manager Engine for OpenVAS Vulnerability Tests
Scan Policies
A scan policy provides you with a central location to configure specific scanning requirements.
You must have the correct license capabilities to perform the following scanning operations. If you need assistance to obtain a new or updated license key, contact your Juniper Customer Support.
You can use scan policies to specify scan types, ports to be scanned, vulnerabilities to scan for and scanning tools to use. In JSA Vulnerability Manager, a scan policy is associated with a scan profile and is used to control a vulnerability scan. You use the Scan Policies list on the Details tab of the Scan Profile Configuration page to associate a scan policy with a scan profile.
You can create a new scan policy or copy and modify a pre-configured policy that is distributed with JSA Vulnerability Manager.
Pre-configured Scan Policies
The following pre-configured scan policies are distributed with JSA Vulnerability Manager:
Full scan
Discovery scan
Database scan
Patch scan
PCI scan
Web scan
A description of each pre-configured scan policy is displayed on the Scan Policies page.
Scan Policy Automatic Updates for Critical Vulnerabilities
As part of JSA Vulnerability Manager daily automatic updates, you receive new scan policies for tasks such as detecting zero-day vulnerabilities on your assets.
Use scan policies that are delivered by automatic update to create scan profiles to scan for specific vulnerabilities. To view all scan policies on your system, go to Administrative >Scan Policies on the Vulnerabilities tab.
You must not edit scan policies that are delivered by automatic update as your changes might be overwritten by later updates. You can create a copy and edit it.
If you delete a scan policy that is delivered by automatic update, it can be recovered only by Juniper Customer Support.
Modifying a Pre-configured Scan Policy
In JSA Vulnerability Manager, you can copy a pre-configured scan policy and modify the policy to your exact scanning requirements.
Click the Vulnerabilities tab.
In the navigation pane, select Administrative >Scan Policies.
On the Scan Policies page, click a pre-configured scan policy.
On the toolbar, click Edit.
Click Copy.
In the Copy scan policy window, type a new name in the Name field and click OK.
Click the copy of your scan policy and on the toolbar, click Edit.
In the Description field, type new information about the scan policy.
Note:If you modify the new scan policy, you must update the information in the description.
To modify your scan policy, use the Port Scan, Vulnerabilities, Tool Groups, or Tools tabs.
Note:Depending on the Scan Type that you select, you cannot use all the tabs on the Scan Policy window.
Configuring a Scan Policy
In JSA Vulnerability Manager, you can configure a scan policy to meet any specific requirements for your vulnerability scans. You can copy and rename a preconfigured scan policy or you can add a new scan policy. You can't edit a preconfigured scan policy.
Click the Vulnerabilities tab.
In the navigation pane, select Administrative >Scan Policies.
On the toolbar, click Add.
Type the name and description of your scan policy.
To configure a scan policy, you must at least configure the mandatory fields in the New Scan Policy window, which are the Name and Description fields.
From the Scan Type list, select the scan type.
To manage and optimize the asset-discovery process, click the Asset Discovery tab.
To manage the ports and protocols that are used for a scan, click the Port Scan tab.
To include specific vulnerabilities in your patch scan policy, click the Vulnerabilities tab.
Note:The Vulnerabilities tab is available only when you select a patch scan.
To include or exclude tool groups from your scan policy, click the Tool Groups tab.
Note:The Tool Groups tab is available only when you select a zero-credentialed full–scan or full-scan plus policy.
To include or exclude tools from a scan policy, click the Tools tab.
Note:The Tools tab is available only when you select a zero-credentialed Full Scan or FullScan Plus policy.
Note:If you do not modify the tools or tool groups, and you select the Full option as your scan type, then all the tools and tool groups that are associated with a full scan are included in your scan policy.
Click Save.
