- play_arrow Vulnerability Assessment Scanner Overview
- play_arrow Troubleshooting Scanners
- play_arrow AXIS Scanner
- play_arrow Beyond Security Automatic Vulnerability Detection System Scanner Overview
- play_arrow Digital Defense Inc AVS Scanner Overview
- play_arrow eEye Scanner Overview
- play_arrow IBM AppScan Enterprise Scanner Overview
- IBM AppScan Enterprise Scanner Overview
- Creating a Customer User Type for IBM AppScan Enterprise
- Enabling Integration with IBM AppScan Enterprise
- Creating an Application Deployment Map in IBM AppScan Enterprise
- Publishing Completed Reports in IBM AppScan Enterprise
- Adding an IBM AppScan Enterprise Vulnerability Scanner
- play_arrow IBM Guardium Scanner Overview
- play_arrow IBM SiteProtector Scanner Overview
- play_arrow Juniper Profiler NSM Scanner Overview
- play_arrow McAfee Vulnerability Manager Scanner Overview
- play_arrow nCircle IP360 Scanner Overview
- play_arrow Nessus Scanner Overview
- play_arrow netVigilance SecureScout Scanner Overview
- play_arrow NMap Scanner Overview
- play_arrow Outpost24 Vulnerability Scanner Overview
- play_arrow Qualys Scanner Overview
- play_arrow Rapid7 NeXpose Scanners Overview
- play_arrow SAINT Security Suite Overview
- play_arrow Tenable.io Scanner Overview
- play_arrow Tenable SecurityCenter Scanner Overview
- play_arrow Scheduling a Vulnerability Scan
- play_arrow Viewing the Status Of a Vulnerability Scan
- play_arrow Supported Vulnerability Scanners
Enable WMI for Microsoft SCCM Scanners
Before you can configure a Microsoft SCCM scanner, you must configure your system DCOM settings for each host that you want to monitor.
The scanner host must meet the following conditions:
You are a member of the Read-only Analyst Role on that host.
One of the following operating systems is installed:
Windows 7
Windows 2008
Windows 2008 R2
Windows 2012
Windows 2012 R2 (only 64 bit is supported)
Vista software
Note:SCCM is not supported on versions of Windows that were moved to End of Life by Microsoft. If a software version date is beyond the Extended Support End Date, the product might not function as expected. Juniper does not make code or vulnerability fixes to resolve issues for older operating systems. For example, Microsoft Windows Server 2003 R2 and Microsoft Windows XP are operating systems that are beyond the Extended Support End Date. Any questions about this announcement can be discussed in the JSA forums. For more information about support lifecycles, see the Microsoft Support lifecycle website (https://support.microsoft.com//en-us/lifecycle/search)
DCOM is configured and enabled.
If a firewall is installed on the host or is located between the host and JSA, such as a hardware or other intermediary firewall, the firewall must be configured to allow DCOM communication. Configure the firewall to allow port 135 to be accessible on the host, and allow DCOM ports. DCOM ports are random ports above 1024. Depending on your version of Windows, you might need to configure specific ports to be accessible to DCOM. For more information, see your Windows documentation.
Windows Management Instrumentation (WMI) is enabled.
The remote registry service is activated.