McAfee Network Security Platform

Transcription

1 Revision E McAfee Network Security Platform ( Manager-M-series, Mxx30-series, XC Cluster Release Notes) Contents About this release New features Enhancements Resolved issues Installation instructions Known issues Product documentation About this release This document contains important information about the current release. We recommend that you read the whole document. Network Security Platform follows a release process that is based on customer requirements and best practices followed by other McAfee teams. For details, read KB This release of Network Security Platform is to provide new features and enhancements on the Manager, M-series, Mxx30-series, and XC Cluster Sensor software. Release parameters Version Network Security Manager software version Signature Set M-series, Mxx30-series, M-8000XC Sensor software version XC-240 Load Balancer

2 Currently port 4167 is used as the UDP source port number for the SNMP command channel communication between Manager and Sensors. This is to prevent opening up all UDP ports for inbound connectivity from SNMP ports on the Sensor. Older JRE versions allowed the Manager to bind to the same source port 4167 for both IPv4 and IPv6 communication. But with the latest JRE version 1.8.0_131, it is no longer possible to do so, and the Manager uses port 4166 as the UDP source port to bind for IPv6. Manager 9.1 uses JRE version 1.8.0_131. If you have IPv6 Sensors behind a firewall, you need to update your firewall rules accordingly such that port 4166 is open for the SNMP command channel to function between those IPv6 Sensors and the Manager. Manager software version 9.1 is not supported on McAfee-built Dell-based Manager Appliances. McAfee recommends that you use Intel-based Manager Appliances instead. Upgrade support McAfee regularly releases updated versions of the signature set. You can choose to automatically download and deploy the signature set in the Manager. Consider the following before upgrading to Network Security Manager version 9.1: If you are using the Manager version with McAfee Cloud Threat Detection (McAfee CTD) environment only, then you can upgrade to Manager version 9.1. This version supports integration with McAfee CTD. If you are on Manager version , note that the Manager version 9.1 does not support the KVM and NSX environments. In this case, McAfee recommends you to continue using the Manager version Manager version does not support M-series, Mxx30-series, M-8000XC Sensors version The following is the upgrade matrix supported for this release: Component Minimum Software Version Manager/Central Manager software 8.1: , : , (only for McAfee CTD), M-series Sensor software (M-1250, M-1450, M-2750, M-2850, M-2950, M-3050, M-4050, M-6050, M-8000) Mxx30-series Sensor software (M-3030, M-4030, M-6030, M-8030) M-8000XC Sensor software 8.1: , : , XC

3 Heterogeneous support This version of 9.1 Manager software can be used to configure and manage the following devices: Device NS-series Sensors (NS3100, NS3200, NS5100, NS5200, NS7100, NS7200, NS7300, NS9100, NS9200, NS9300) Virtual IPS Sensors (IPS-VM100 and IPS-VM600) Version 8.1, 8.3, , 8.3, 9.1 Network Security Manager version 9.1 does not support KVM environment. Virtual Security System (IPS-VM100-VSS) 8.3, 9.1 Network Security Manager version 9.1 does not support VMware NSX environment. M-series Sensors (M-1250, M-1450, M-2750, M-2850, M-2950, M-3050, M-4050, M-6050, M-8000) 8.1, 8.3, 9.1 Mxx30-series Sensors (M-3030, M-4030, M-6030, M-8030) 8.1, 8.3, 9.1 M-8000XC Cluster Appliance 8.1, 8.3, 9.1 NTBA Appliances (T-200, T-500, T-600, T-1200) 8.1, 8.3, 9.1 Virtual NTBA Appliances (T-VM, T-100VM, T-200VM) 8.1, 8.3, 9.1 Integration support The above mentioned Network Security Platform software versions support integration with the following product versions: Table 1-1 Network Security Platform compatibility matrix Product Version supported McAfee epo 5.9.0, McAfee Global Threat Intelligence McAfee Endpoint Intelligence Agent 2.6 McAfee Logon Collector McAfee Threat Intelligence Exchange 2.1.0, McAfee Data Exchange Layer 3.0.1, Compatible with all versions McAfee Advanced Threat Defense , McAfee Virtual Advanced Threat Defense , McAfee Cloud Threat Detection McAfee MOVE AntiVirus Agentless McAfee MOVE AntiVirus Multi-Platform McAfee Vulnerability Manager , McAfee Host Intrusion Prevention 8.0 New features This release of Network Security Platform includes the following new features: 3

4 Migration from SHA1 to SHA256 signing algorithm With this release, the Network Security Platform announces the deprecation of SHA1 certificates to sign Sensor-Manager communication and replaces this with SHA256 certificates for this signature. This results in more secure communication between the Sensor and the Manager. Previous Releases In Network Security Platform early 8.1 deployments, both the Sensor and Manager certificates used 1024-bit RSA keys and were signed with Sha1WithRSAEncryption based signature. The Manager ports 8501, 8502, and 8503 serve the TLS channels from the Sensor. The cipher used by the Sensor and Manager was TLS1.0-RSA-AES128-SHA1. Starting with release and , the M-series Sensor certificate used 2048-bit RSA keys and Sha256WithRSAEncryption based signature. The Manager certificate used 2048-bit RSA keys but retained Sha1WithRSAEncryption based signature. The Manager ports 8506, 8507, and 8508 served the TLS channels from the Sensor. The cipher used by the Sensor was TLS1.0-RSA-AES128-SHA1. Current Release From release , the Manager supports 2048-bit RSA keys with Sha256WithRSAEncryption based signature. This release of the Manager reuses ports 8501, 8502, and 8503 to support this new posture that was previously allocated to certificates using 1024-bit RSA keys. The cipher used by the Sensor is TLS1.2-RSA-AES128-GCM-SHA256. Hence, after upgrading the Manager, Sensors deployed on these ports using 1024-bit RSA keys and weaker signatures will not be supported. If you are upgrading from versions 8.2 (EOL) or 8.3, you must activate ports 8501, 8502, and 8503 for Sensor-Manager communication. For more information, refer to the section Migration from SHA1 to SHA256 signing algorithm in the McAfee Network Security Platform 9.1 Installation Guide. The following table captures the migration of certificates. Table 2-1 Ports used based on encryption keys, certificates, and cipher suites Manager Port Channel Description Sensor software with 2048-bit RSA keys, 2048-bit RSA keys, 1024-bit RSA keys, SHA256 certificate, and SHA1 certificate, and SHA1 certificate, and TLS1.2-RSA-AES128- TLS1.0-RSA- TLS1.0-RSA- GCM-SHA256 AES128-SHA1 AES128-SHA Install Sensor Applicable --- Applicable 8502 Alert/Event Applicable --- Applicable 8503 Packet Log Applicable --- Applicable 8506 Install Sensor --- Applicable Alert/Event --- Applicable Packet Log --- Applicable File transfer Proprietary (file transfer channel) Proprietary (file transfer channel) Proprietary (file transfer channel) 8509 File transfer 2048-bit RSA Encryption 2048-bit RSA Encryption 1024-bit RSA Encryption 8510 File transfer 2048-bit RSA Encryption 2048-bit RSA Encryption 1024-bit RSA Encryption For more information, see McAfee Network Security Platform 9.1 Installation Guide. 4

5 Memory usage monitor Prior to release 9.1, the Flow Usage monitor in the Dashboard tab was used to view the device TCP and UDP flow utilization. In release 9.1, the Flow Usage monitor is replaced with a Memory Usage monitor which displays memory usage (in percentage) of the selected device using the following four metrics: Flow Pool - Memory allocated to inspect all flows Decrypted Flow Pool - Memory allocated to inspect decrypted SSL flows Packet Buffer - Packet buffer space utilized by the Sensor System Memory - System memory utilized (CPU utilization) by the Sensor Options are also available to display percentage based on low, medium, or high usage. The parameters listed above can be viewed by going to Devices <Admin Domain Name> Devices <Device Name> Troubleshooting Performance Charts and clicking on the Memory tab. This helps a security administrator to monitor the memory usage at all times and take action before it reaches the threshold limit. The memory usage is displayed with a series of data points in the form of individual line charts for all the four parameters. You can configure the threshold for memory usage in the following pages: Memory usage threshold for an admin domain is configured in the Thresholds page under Devices <Admin Domain Name> Global Common Device Settings Performance Monitoring Thresholds. Memory usage threshold for a specific device is configured in the Thresholds page under Devices <Admin Domain Name> Devices <Device Name> Setup Performance Monitoring Thresholds. When the Sensor memory usage reaches the threshold, faults for the memory usage parameters are triggered. You can view these faults in the System Faults page under Manager <Admin Domain Name> Troubleshooting System Faults. You can generate Next Generation Reports for memory usage metrics in the Next Generation Reports page under Analysis <Admin Domain Name> Event Reporting Next Generation Reports. For more information, see McAfee Network Security Platform 9.1 IPS Administration Guide. Product integration With this release, Network Security Platform supports integration with McAfee epolicy Orchestrator version and McAfee Virtual Advanced Threat Defense version For more information on the product integration, see McAfee Network Security Platform 9.1 Integration Guide. Enhancements This release of Network Security Platform includes the following enhancements: Central Manager UI redesign to migrate away from Java In release 9.1, the following existing UI pages have been enhanced to use the extjs framework: Attack Log With release 9.1, the alerts that were previously displayed in the Alerts tab in the Real-Time Threat Analyzer in the Central Manager are now displayed in Attack Log. 5

6 The following actions can be performed in the Central Manager Attack Log. Update Policy Delete Alerts Create exceptions Save Attack Log Perform GTI Forensics Acknowledge alerts Assignment of alert Unacknowledge alerts To view the alerts, go to Analysis <Admin Domain Name> Attack Log. To view Endpoint information, go to the Analysis <Admin Domain Name> Quarantine in the corresponding Manager. For more information, see McAfee Network Security Platform 9.1 Manager Administration Guide. Grouping alerts in the Attack Log page The Attack Log page, depending on the traffic passing through your network, might display several alerts that run into multiple pages. It becomes inefficient to search for specific groups of alerts. Version 9.1 enables you to filter the display of alerts based on specific criteria. The Group by this field option has been made available to group and view a consolidated list of alerts in the Attack Log page. Alerts can be grouped by any of the categories in the Attack Log page, except the following: Time, Attack Count, and Alert ID under the Event column NSP ID under the Attack column Packet Capture Layer 7 Data In a Central Manager setup, you can additionally group the alerts based on the version of the Manager. For more information, see McAfee Network Security Platform 9.1 Manager Administration Guide. Configuration option changes for custom attack signatures While configuring user-defined signatures (UDS) for M-series Sensors from the Custom Attack Editor (under Policy <Root Admin Domain> Intrusion Prevention Policy Types IPS Policies), you only had the option to apply the UDS with a combination of both M-series and NS-series Sensors and not specific to either. In release 9.1, you have the following options to apply UDS specific to each Sensor: M-series only NS-series only Virtual IPS Sensors only In release 9.1, in addition to the options available to apply UDS for specific Sensor models, you have options to apply UDS in the following new combinations: Any M-series and NS-series Sensors only M-series and Virtual IPS Sensors only NS-series and Virtual IPS Sensors only For more information, see McAfee Network Security Platform 9.1 Custom Attack Definitions Guide. 6

7 Option to remediate an endpoint which are manually quarantined In release 9.1, an option is available to direct an endpoint to the remediation portal when you manually quarantine it. Earlier, the Manager did not have an option to remediate an endpoint when it was quarantined manually. This option is available in the Add to Quarantine window in the following pages under the Analysis tab: Threat Explorer Quarantine Callback Activity Attack Log High-Risk Endpoints While quarantining an endpoint manually, the Add to Quarantine window provides you with a Remediate checkbox which when selected, directs that endpoint to a pre-configured remediation portal. Further, a new column Remediate is added in the Quarantine page which indicates whether remediation is enabled or disabled for that endpoint. For more information, see McAfee Network Security Platform 9.1 Manager Administration Guide. Bulk import of SSL certificates In previous releases, the SSL certificates had to be imported for every Sensor separately. With release 9.1, you can import up to 200 certificates files and perform a configuration update to all the Sensors. You can bulk import the certificate files only at the admin domain level. For more information, see McAfee Network Security Platform 9.1 IPS Administration Guide. Layer 7 data capture enhancements In the earlier releases, the time taken to display alerts in the Manager from the time they were generated in the Sensor, was prolonged. This was due to the alerts generated to support layer 7 data capture feature. They display additional information such as HTTP URL, response code, FTP user name, etc. Excess number of these alerts could cause further delays. In version 9.1, an enhancement is made to reduce generation of these excessive alerts by delaying the alert generation either by a maximum of 5 seconds, or until the Layer 7 session is terminated. Increase in memory size for handling signature sets With a growing number of threats, the frequency of signature set updates and the number of attacks in each update constantly increase. As a means to accommodate a larger signature set size in the future, the memory size allocated to signature sets on the Sensor has been increased. Multiple attachments extraction in SMTP In earlier releases, the Sensor could extract only a single attachment from the SMTP traffic for malware inspection. In release 9.1, the Sensor has the ability to extract multiple attachments from SMTP traffic. Resolved issues The current release of the product resolved these issues. For a list of issues fixed in earlier releases, see the Release Notes for the specific release. Resolved Manager software issues The following table lists the high-severity Manager software issues: 7

8 ID # Issue Description Attack detection occurs even after the protected group is removed or the subnet is removed from a protected group Virtual Probe status is displayed as inactive when active and vice versa In the Snort Variables window under Custom Attack Editor, after deleting and then adding a Snort variable displays the error, Please enter macro name Creation of new UDS fails with the error Number of Characters > 255 even when the number of characters are less than Characters specified within the specified range generates the error Number of Characters > The Manager user interface fails to load in Internet Explorer version The device integrated with the NTBA appliance is not displayed in the device list under Devices <Admin Domain Name> Devices Incorrect description is displayed in the alert details panel in Attack Log for Endpoint Executables and Malware Files The Attack Log does not display data for EIA executables Incorrect quarantined IP address is displayed for MAID alerts. The following table lists the medium-severity Manager software issues: ID # Issue Description Traffic is blocked using SmartBlocking even when SmartBlocking is disabled Custom attacks are not saved In the Quarantine page, the quarantined IP with the option Until explicitly released is not displayed The Quarantine page in the Manager does not display the list of all quarantined hosts In the Custom Attack Editor, Snort variable created to replace all variables fails with errors The Executive Summary report generation fails after a Manager upgrade High-risk endpoints are not displayed in the Manager Creating custom signature with fixed source or destination IP addresses causes test compilation failure Sensor settings cannot be saved under Devices <Admin Domain Name> Global IPS Device Settings Advanced Device Settings Snort signatures are not triggered for HTTP response data The Manager displays the error SensorConfigurationException: Agent Not Supported when an IP address is removed from the quarantined list in the Quarantine page Summary page of the failover peer displays two different names The Manager attempts to connect to msas.mcafee.com without using a proxy The epo Dashboard Data retriever user role does not allow epo integration with the Manager under Manager <Admin Domain Name> Users and Roles Roles Unable to view the source user information in Attack Log The RADIUS servers page under Manager <Admin Domain Name> Setup External Authentication RADIUS Servers displays the error An unexpected error occurred during the processing of your request. Check the log file for possible errors The Manager fails to enable the option Restrict SSH Access to CLI under Devices <Admin Domain Name> Devices <Device Name> Setup Advanced Advanced Device Settings The attempt to add a username that includes an apostrophe in the Add a User page fails. 8

9 ID # Issue Description The Manager health check fails due to database login under Manager <Admin Domain Name> Troubleshooting Health Check Snort rule for UDP packets does not generate alerts and drops the packets on port The Manager Dashboard page does not display the Throughput Usage, Memory Usage, and CPU Usage monitors LDAP over SSL does not work after a Manager upgrade The performance charts does not display data for Minutes filter under Devices <Admin Domain Name> Devices <Device Name> Troubleshooting Performance Charts The Faults report displays Scheduled botnet detectors download is in progress even after the callback detectors are successfully updated Quarantined hosts generates alerts in the Threat Analyzer Sensor performance alert causes alert channel to go down Running a health check fails when the Manager is connected through proxy settings A difference exists between severity of detected alerts and configured severity An error is displayed while exporting packet captures of an alert from the Attack Log page The Manager uses SHA128 bit encryption algorithm instead of SHA In the Attack Log page, filtering attacks for Attack SmartBlocked are not displayed in the Results column When adding an Ignore Rule from the Attack Log page, the action to create a new rule object fails in the Add Ignore Rule window The malware confidence (severity) for the same alert displays inconsistent value in the Manager (Attack Log, Alert Details, and Malware Files) and Syslog Message The configuration options are disabled for alert relevance in Manager <Admin Domain Name> Integration Vulnerability Assessment MVM Alert Relevance The Manager incorrectly considers a Sensor to be part of a failover pair Login for epo Dashboard Data Retriever user role displays an error Manually quarantined IP address from the Attack Log page is not displayed in the Manager quarantine list The Manager sends additional messages in the syslog notification for some alerts The Manager is vulnerable to CVE The actions performed to enable or disable the monitoring ports in the Sensor are displayed incorrectly in the User Activity Log page. For example, if the port action is from Enabled to Disabled, it is displayed as Disabled to Enabled in the Manager In the Manager, the list to select the child domain is disabled Expired SSL certificate can be imported to the Manager which is displayed as Valid Alert count mismatch exists between the Primary and Secondary Manager The Devices tab does not display the tab options When an attack is blocked using the Recommended for Smart Blocking (RfSB) feature, its attack result in the SNMP trap displays [777] instead of Smart Blocked The data truncation error description is very long The Result column does not display attacks for smartblocked attacks in the Attack Log after Manager upgrade notifications are incorrectly sent for alerts that are not configured to send notifications Direct link to view the Sensor status on the System Health monitor of the Dashboard page is disabled. 9

10 ID # Issue Description The An internal application error occurred message is displayed when trying to access the Global Threat Intelligence from the Manager Error is displayed in the Manager when the number of quarantined IP addresses exceeds Attacks names are displayed as --- after a signature set upgrade under Policy <Admin Domain Name> Intrusion Prevention Policy Types IPS Policies The Manager automatically deploys the signature sets even when automatic deployment is disabled The performance charts for Device Throughput Usage, Port Throughput, and CPU Usage under Devices <Admin Domain Name> Devices <Device Name> Troubleshooting Performance Charts does not display weekly data When deploying updates to the Sensor, the Running Tasks and User Activity Log pages displays the device name as null Importing user-defined signatures in the Manager causes error In an MDR scenario, both the Primary and Secondary Managers send fault notification for port link failures Communication between the Manager and the Sensor is disconnected after restarting the Manager service The trend analysis report scheduled for weekly or monthly time period does not display the data for the last day The fault for Gateway Anti-Malware file update is displayed in the Manager even when it successfully updated in the Sensor File pruning option does not delete old signature files The syslog fault notifications for a high-availability Sensor cluster from the Manager contains the cluster name instead of the node name Executive Summary report shows several Address Not Resolved results in the Hostname columns in the Top N Source IP and Top N Destination IP sections The Policy <Admin Domain Name> Intrusion Prevention Policy Types Inspection Options Policies page freezes when you enable endpoint reputation analysis and disable name resolution/global Threat Intelligence The Manager update date is not displayed in the Manager <Admin Domain Name> Troubleshooting Health Check page The Manager command channel should request for TLS1.2 connection with NTBA In the Attack Log page, the policy update fails when selecting a policy under Update Policy options from the Other Actions list SNMP trap displays incorrect port name The Traffic Statistics page displays an error when clicked Unable to export custom attacks in the Policy <Admin Domain Name> Intrusion Prevention Policy Types IPS Policies Custom Attacks Snort Format Other Actions Export page The clean files count for the Blacklist engine should be changed to NA instead of 0 in the Devices <Admin Domain Name> Devices <Device Name> Troubleshooting Traffic Statistics page. The following table lists the low-severity Manager software issues: ID # Issue Description The syslog notifications for performance faults does not include the value that triggered the fault or the threshold. Resolved software issues for M-series, Mxx30-series, M-8000XC Sensors The following table lists the medium-severity Sensor software issues: 10

11 ID # Issue Description The Sensor reads the incorrect input without proper validation and starts establishing trust using SHA2 based signature methods After upgrade, the Sensor automatically reboots Alerts are generated even after disabling layer 7 DDoS response status The management port speed settings are not updated after Sensor reboot In the Sensor, the Ignore rules do not work when same TCP/HTTP based protocol packet in the flow is resent The Sensor observes latency due to improper distribution of MPLS traffic The Sensor does not free data on successive connections to an unresponsive NTBA which causes the Sensor to reboot Configuration push fails after certain number of times when there are Alert Exceptions with Any Any or when IPv6 Alert Exceptions and no IPv6 Scanning is enabled. Internal resources fail to get freed for such configurations Incorrect layer 7 alert data is rejected by the Manager due to which the Sensor stops sending alerts Invalid characters are sent as URL information to Advanced Threat Defense After Sensor upgrade, FTP traffic does not flow through the Sensor The Sensor fails to detect exploit attacks Out-of-order TCP segments are queued for download which results in timeout or in exceptionally long delays The output for resolve gti server CLI command displays incorrect destination The Sensor fails to generate alert while detecting TOR traffic in a proxy environment. Resolved XC-240 software issues There are no resolved issues for XC-240 applicable to this release. 11

12 Installation instructions Manager server/client system requirements The following table lists the 9.1 Manager server requirements: Operating system Minimum required Any of the following: Windows Server 2008 R2 Standard or Enterprise Edition, English operating system, SP1 (64-bit) (Full Installation) Windows Server 2008 R2 Standard or Enterprise Edition, Japanese operating system, SP1 (64-bit) (Full Installation) Windows Server 2012 R2 Standard Edition (Server with a GUI) English operating system Windows Server 2012 R2 Standard Edition (Server with a GUI) Japanese operating system Windows Server 2012 R2 Datacenter Edition (Server with a GUI) English operating system Windows Server 2012 R2 Datacenter Edition (Server with a GUI) Japanese operating system Windows Server 2016 Standard Edition (Server with a GUI) English operating system Windows Server 2016 Standard Edition (Server with a GUI) Japanese operating system Windows Server 2016 Datacenter Edition (Server with a GUI) English operating system Windows Server 2016 Datacenter Edition (Server with a GUI) Japanese operating system Only X64 architecture is supported. Recommended Windows Server 2016 Standard Edition operating system Memory 8 GB Supports up to 3 million alerts in Solr. >16 GB Supports up to 10 million alerts in Solr. CPU Server model processor such as Intel Xeon Same Disk space 100 GB 300 GB or more Network 100 Mbps card 1000 Mbps card Monitor 32-bit color, 1440 x 900 display setting 1440 x 900 (or above) The following are the system requirements for hosting Central Manager/Manager server on a VMware platform. 12

13 Table 5-1 Virtual machine requirements Component Minimum Recommended Operating system Any of the following: Windows Server 2008 R2 Standard or Enterprise Edition, English operating system, SP1 (64-bit) (Full Installation) Windows Server 2008 R2 Standard or Enterprise Edition, Japanese operating system, SP1 (64-bit) (Full Installation) Windows Server 2012 R2 Standard Edition (Server with a GUI) English operating system Windows Server 2012 R2 Standard Edition (Server with a GUI) Japanese operating system Windows Server 2012 R2 Datacenter Edition (Server with a GUI) English operating system Windows Server 2012 R2 Datacenter Edition (Server with a GUI) Japanese operating system Windows Server 2016 Standard Edition (Server with a GUI) English operating system Windows Server 2016 Standard Edition (Server with a GUI) Japanese operating system Windows Server 2016 Datacenter Edition (Server with a GUI) English operating system Windows Server 2016 Datacenter Edition (Server with a GUI) Japanese operating system Only X64 architecture is supported. Windows Server 2016 Standard Edition operating system Memory 8 GB >16 GB Supports up to 3 million alerts in Solr. Supports up to 10 million alerts in Solr. Virtual CPUs 2 2 or more Disk Space 100 GB 300 GB or more Table 5-2 VMware ESX server requirements Component Minimum Virtualization software ESXi 5.1 Update 2 ESXi 5.5 Update 3 ESXi 6.0 Update 1 ESXi

14 The following table lists the 9.1 Manager client requirements when using Windows 7, Windows 8, or Windows 10: Operating system Minimum Windows 7, English or Japanese Windows 8, English or Japanese Windows 8.1, English or Japanese Windows 10, English or Japanese The display language of the Manager client must be the same as that of the Manager server operating system. Recommended RAM 2 GB 4 GB CPU 1.5 GHz processor 1.5 GHz or faster Browser Internet Explorer 10, 11 Mozilla Firefox Google Chrome (App mode in Windows 8 is not supported) To avoid the certificate mismatch error and security warning, add the Manager web certificate to the trusted certificate list. Internet Explorer 11 Mozilla Firefox 20.0 or later Google Chrome 24.0 or later In Mozilla Firefox version 52 or Google Chrome version 42 and above, the NPAPI plug-in is disabled by default. For the Manager client, in addition to Windows 7, Windows 8, Windows 8.1 and Windows 10, you can also use the operating systems mentioned for the Manager server. The following are Central Manager and Manager client requirements when using Mac: Mac operating system Yosemite El Capitan Browser Safari 8 or 9 For more information, see McAfee Network Security Platform Installation Guide. Known issues For a list of known issues in this product release, see this McAfee KnowledgeBase article: Network Security Platform software issues: KB88813 Product documentation Every McAfee product has a comprehensive set of documentation. Find product documentation 1 Go to the McAfee ServicePortal at and click Knowledge Center. 2 Enter a product name, select a version, then click Search to display a list of documents. 14

15 9.1 product documentation list The following software guides are available for Network Security Platform 9.1 release: Quick Tour AWS Deployment Guide Installation Guide (includes Upgrade Guide) CLI Guide Manager Administration Guide XC Cluster Administration Guide Custom Attack Definitions Guide Integration Guide Manager API Reference Guide Best Practices Guide IPS Administration Guide Troubleshooting Guide Copyright 2018 McAfee, LLC McAfee and the McAfee logo are trademarks or registered trademarks of McAfee, LLC or its subsidiaries in the US and other countries. Other marks and brands may be claimed as the property of others. 0E00