McAfee Network Security Platform 8.3

Transcription

1 Manager-M-series Release Notes McAfee Network Security Platform 8.3 Revision A 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 few features and enhancements on the Manager and M-series Sensor software. Release parameters Version Network Security Manager software version Signature Set M-series Sensor software version 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_92, it is no longer possible to do so, and the Manager uses port 4166 as the UDP source port to bind for IPv6. 1

2 Manager 8.3 uses JRE version 1.8.0_92 and MySQL version 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 8.3 is not supported on McAfee-built Dell based Manager Appliances. McAfee recommends that you use Intel-based Manager Appliances instead. Upgrade recommendations McAfee regularly releases updated versions of the signature set. You can choose to automatically download and deploy the signature set in the Manager. The following is the upgrade matrix supported for this release: Component Manager/Central Manager software Minimum Software Version 8.1: , Upgrade from Manager versions and are not supported. M-series Sensor software 8.1: , : , (only for McAfee CTD), : , Heterogeneous support This version of 8.3 Manager software can be used to configure and manage the following hardware: Hardware NS9x00-series Sensors (NS3100, NS3200, NS5100, NS5200, NS7100, NS7200, NS7300, NS9100, NS9200, NS9300) Version 8.1, 8.3 NS3x00-series and NS5x00-series Sensors are not compatible with Manager version See Known Issues for more information. Virtual IPS Sensors (IPS-VM100 and IPS-VM600) 8.1, 8.3 Virtual Security System Sensors (IPS-VM100-VSS) 8.1, 8.3 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 Mxx30-series Sensors (M-3030, M-4030, M-6030, M-8030) 8.1, 8.3 M-8000XC Cluster Appliance 8.1, 8.3 NTBA Appliances (T-200, T-500, T-600, T-1200) 8.1, 8.3 Virtual NTBA Appliances (T-VM, T-100VM, T-200VM) 8.1, 8.3 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.1, McAfee Global Threat Intelligence Compatible with all versions 2

3 Table 1-1 Network Security Platform compatibility matrix (continued) Product Version supported McAfee Endpoint Intelligence Agent 2.6 McAfee Logon Collector McAfee Threat Intelligence Exchange McAfee Data Exchange Layer McAfee Advanced Threat Defense McAfee Virtual Advanced Threat Defense McAfee Cloud Threat Detection 2.2 McAfee MOVE AntiVirus Agentless McAfee MOVE AntiVirus Multi-Platform McAfee Vulnerability Manager McAfee Host Intrusion Prevention 8.0 Intel Security Controller 2.5 New features This release is to provide fixes for some of the previously known issues, and does not include any new features. Enhancements This release is to provide fixes for some of the previously known issues, and does not include any enhancements. 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: ID # The Sensor upgrade from the Manager fails for one of the Sensor in a failover pair The Report Format option for PDF in Executive Summary IPS reports do not generate, the Report Format output options for PDF are not working as expected In the Snort Variables window under Custom Attack Editor, when you delete and add another Snort variable, the Please enter macro name error is displayed When you use the custom attack editor to modify the Supported Device Type setting via bulk editing, the snort rule remains at 0% processing The Manager does not load all the pages inc Internet Explorer browser. The following table lists the medium-severity Manager software issues: 3

4 ID # The Manager is vulnerable to CVE Apache Tomcat vulnerability Imported signature set displays incorrect BTP value after saving When you import alerts in.csv format, alerts greater than 100,000 are not imported form attack log Attack log filter for Malware Confidence column for Very High fails Automatic update enabled for an NTBA Appliance generates the fault Key Value not found in the properties file once a day After a new monitor is added to the Dashboard tab, the page takes too long to refresh and load the information Admin Domains allocation screen does not load correctly The Device Summary Report of a particular child domain includes Sensor information of other domains The ems.log files are filled with "Alert Synchronization successful" entries The alert for failure to connect to the update server is incorrectly generated A quarantined host IP address cannot be released due to SNMP error Available devices and interfaces are not shown in the Scope page under Policy <Admin Domain Name> Intrusion Prevention Exceptions Ignore Rules Tables and rows in the Application Visualization module are not purged which leads to stale data being present in the Manager database Multiple attacks are smart blocked without configuring the policy The Central Manager does not synchronize changes to Block Settings without changing part of another attack set profile The Details tab for the ICMP_ECHO Anomaly alert in the Attack Log page does not show any information after details of another attack is viewed An attempt to quarantine an endpoint fails due to a communication error between the Manager and the selected device The Automatically-Generated Reports option in the Manager <Admin Domain Name> Reporting Report Automation is not displayed in the Manager The XC Load Balancer faults are not sent to the Manager The Manager quarantine API locks up after roughly two weeks of usage Data retrieved from an NTBA Appliance does not appear in the Dashboard tab The Manager displays the cannot invoke on IPv6 error message during quarantine of an IPv6 host The quarantine windows does not display all the hosts that are in quarantine The Sensor automatically deploys updates every one hour without configuration changes When you use the custom attack editor, you are unable to use one or more snort variables The Executive Summary report generation fails after a Manager upgrade / The epolicy Orchestrator is unable to pull logs from the Manager after the Manager is upgraded High-risk endpoints are not displayed in the Manager Creating any signature with source or destination fixed IP tests causes compilation failure The daily report for Top N Attacks displays the option Select Alerts to Display which is applicable only to weekly reports Log messages are repeated and incorrectly printed. 4

5 ID # The Summary page for a failover pair displays two different names The Manager fails to establish communication with its database OpenSSL vulnerabilities: Encrypt-Then-Mac renegotiation crash (CVE ) BN_mod_exp may produce incorrect results on x86_64 (CVE ) Truncated packet could crash via OOB read (CVE ) Bad (EC) DHE parameters cause a client crash (CVE ) Montgomery multiplication may produce incorrect results (CVE ) After editing Custom Attacks and saving the changes, IPS Policy editor cannot be modified unless you logout from the client and login again After Manager upgrade to verison 8.3, all alerts are not synchronized to the Secondary Manager database in an MDR pair The Manager attempts to connect to msas.mcafee.com without using the proxy Unable to view the source user information in Attack Log SNMP notification sends incorrect values for the ivsensoripaddress field The RADIUS Server page does not appear when selected The Manager fails to save advanced configuration option to Restrict SSH Access to CLI, in the Advanced Device Settings page under Devices <Admin Domain Name> Global IPS Device Settings When you save a UDS with an IPv4 address, the process sticks at 0% The Manager health check fails due to database login in the Health Check page under Manager <Admin Domain Name> Troubleshooting The Active Directory server over SSL does not work when custom certificate is used for the Active Directory server The Manager dashboard does not display the Throughput Usage, Memory Usage, and CPU Usage monitors When you use a web proxy with XFF headers, the IP on the X-Forwarded-For field does not correspond with the reported Attacker IP LDAP over SSL does not work after a Manager upgrade The performance charts displays no data for the Minutes filter under Devices <Admin Domain Name> Devices <Device Name> Troubleshooting Performance Charts The Faults Report does not display the alert Successful scheduled Botnet detectors download even though callback detectors are successfully updated Quarantined IP addresses are not displayed in the Manager. The following table lists the low-severity Manager software issues: ID # Unable to add an Additional Text information in the Syslog and fault notification. Resolved Sensor software issues The following table lists the high-severity Sensor software issues: ID # Due to a deadlock condition in the Management processor, packet forward to datapath processors are stopped. This in turn results in auto recovery or reboot. 5

6 The following table lists the medium-severity Sensor software issues: ID # The Sensor may reboot in scenarios when guest portal is enabled and hundred thousand guest portal requests per second are consistently seen on the Sensor in a period of 10 to15 minutes The Sensor may go to bad health in scenarios where attack Callback Detectors: Connection Using High Confidence C&C Server Domain Name Detected is disabled and an error scenario is not handled Smart blocked attacks show different results in the syslog notification for IV_RESULT_STATUS For certain set of attacks, the attack ID logging causes an exception and the Sensor autorecovers During a fan hardware issue, "Fan normal" event is falsely seen even though the fan is not restored to normal state The Sensor reboots suddenly due to a datapath exception raised while sending netflows to NTBA Trust establishment between Manager and Sensor is down on port R1 for a short period Log errors such as "Port Speed Unknown" are generated for 10G and 40G ports The modified management port speed setting is not saved after reboot The Sensor logs have a typo in the reboot message Invalid "<" and ">" characters are sent as part of URL information to Advanced Threat Defense In the Sensor, the Ignore rule does 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 reboots continuously due to an issue in the datapath processor when SSL decryption and malware are enabled TCP packets are dropped by the Sensor if you attempt a configuration update simultaneously while traffic is run by a test generator The Sensor reboots when stale TCP connections between the Sensor and NTBA Appliance containing large data are not closed 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 The Sensor forwards malformed packets to Advanced Threat Defense which results in packet drop Filename and domain in URL path contains duplicate domain name information when submitted to Advanced Threat Defense, Out-of-order TCP segments are queued for download which results in timeout or in exceptionally long delays McAfee Logon Collector configuration update fails in the Sensor due to running out of internal resources. Allocated internal resources are not freed when not in use The Sensor incorrectly blocks unsupported and unknown ciphers incorrectly and infrequently The Sensor fails to block retransmitted packets for malware attacks configured for blocking. 6

7 Installation instructions Manager server/client system requirements The following table lists the 8.3 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 Only X64 architecture is supported. Recommended Windows Server 2012 R2 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. 7

8 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 (Server with a GUI) Japanese operating system Only X64 architecture is supported. Windows Server 2012 R2 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.5 Update 3 ESXi 6.0 Update 1 CPU Intel Xeon CPU ES 2.00 GHz; Physical Processors 2; Logical Processors 8; Processor Speed 2.00 GHz Memory Internal Disks Physical Memory: 16 GB 1 TB The following table lists the 8.3 Manager client requirements when using Windows 7, Windows 8, or Windows 2012: 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 Windows 10, English or Japanese RAM 2 GB 4 GB 8

9 Minimum Recommended CPU 1.5 GHz processor 1.5 GHz or faster Browser Internet Explorer 10, 11, or Microsoft Edge Mozilla Firefox Google Chrome (App mode in Windows 8 is not supported.) To avoid the certificate mismatch error and security warning, add 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, and Windows 8.1, 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: KB86387 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. 8.3 product documentation list The following software guides are available for Network Security Platform 8.3 release: Quick Tour Custom Attacks Definition Guide Installation Guide (includes Upgrade Guide) XC Cluster Administration Guide Manager Administration Guide Integration Guide Manager API Reference Guide NTBA Administration Guide CLI Guide Best Practices Guide 9

10 IPS Administration Guide Troubleshooting Guide Virtual IPS Administration Guide Copyright 2017 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. 00