{"product_id":10622,"v_id":10622,"product_name":"McAfee Advanced Threat Defense","certification_status":"Certified","certification_date":"2015-05-27T00:00:00Z","tech_type":"Network Device","vendor_id":{"name":"Intel Corporation","website":"www.intelsecurity.com"},"vendor_poc":"Andy Nissan","vendor_phone":"651-628-5385","vendor_email":"andy.nissan@intel.com","assigned_lab":{"cctl_name":"Gossamer Security Solutions"},"product_description":"<p class=\"Body\">The Target of Evaluation (TOE) is the Intel Corporation McAfee Advanced Threat Defense models 3000 and 6000 running software version 3.4.6 products.&nbsp;</p>\r\n<p class=\"Body\">McAfee Advanced Threat Defense (MATD detects today&rsquo;s stealthy, zero-day malware with layered approach. It combines low-touch antivirus signatures, reputation, and real-time emulation defenses with in-depth static code and dynamic analysis (sandboxing) to analyze actual behavior. &nbsp;</p>\r\n<p class=\"Body\">The MATD processes the files through the down selectors for statistical analysis and provides a sandbox test environment which includes virtual machines running customer environments, anti-virus, anti-malware, local blacklist and whitelists. Files are executed within virtual machine environments that are monitored by the log file. The log file is then used to generate a security report of the potential malware.</p>\r\n<p class=\"Body\">For the purpose of evaluation, MATD was treated as a network device offering CAVP certified cryptographic algorithms, security auditing, secure administration, trusted updates, self-tests, and secure connections to other servers (e.g., to transmit audit records).</p>\r\n<p class=\"Body\">MATD is provided as a hardware network appliance. The product provides a web interface over TLS and a console connection.</p>\r\n<p class=\"Body\">There are two versions of the MATD product (6000 and 3000). While there are different models in the TOE, they differ primarily in physical form factor, number and types of connections and slots, and relative performance. There are some performance differences among the models, but they each provide the same security characteristics.</p>","evaluation_configuration":"<p class=\"Body\">The evaluated configuration of consists of McAfee Advanced Threat Defense with software version 3.4.6 running on one of the following modules:</p>\r\n<ul>\r\n<li>ATD-6000: McAfee Advanced Threat Defense 6000, 2U 4x Xeon E5-4640 (2.5GHz), 256GB DDR3, 16TB of HDD storage and 1600MB of SSD storage.</li>\r\n<li>ATD-3000: McAfee Advanced Treat Defense 3000, 1U 2x Xeon E5-2658 (2.1GHz), 192GB DDR3, 8TB of HDD storage and 800MB of SSD storage</li>\r\n</ul>","security_evaluation_summary":"<p>The evaluation was carried out in accordance with the Common Criteria Evaluation and Validation Scheme (CCEVS) process and scheme. The criteria against which the McAfee Advanced Threat Defense models 3000 and 6000 running software version 3.4.6 products was judged are described in the Common Criteria for Information Technology Security Evaluation, Version 3.1 rev 4.&nbsp; The evaluation methodology used by the evaluation team to conduct the evaluation is the Common Methodology for Information Technology Security Evaluation, Version 3.1 rev 4.&nbsp; Gossamer Security Solutions determined that the evaluation assurance level (EAL) for the product is EAL 1.&nbsp; The product, when delivered and configured as identified in the NDPP Admin Guide v3.4.6, 5/20/15 document, satisfies all of the security functional requirements stated in the Intel Corporation McAfee Advanced Threat Defense (NDPP11e3) Security Target, Version 0.5, May 22, 2015.&nbsp; The project underwent CCEVS Validator review.&nbsp; The evaluation was completed in May 2015.&nbsp; Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report (report number CCEVS-VR-VID10622-2015) prepared by CCEVS.</p>","environmental_strengths":"<p>The logical boundaries of the McAfee Advanced Threat Defense models 3000 and 6000 running software version 3.4.6 TOE are realized in the security functions that it implements. Each of these security functions is summarized below.</p>\r\n<p><strong>Security Audit</strong> - The TOE generates audit events associated with identification and authentication, management, updates, and user sessions.&nbsp; The TOE can store the events in a local log or export them to a syslog server using a TLS protected channel.</p>\r\n<p><strong>Cryptographic Support</strong> - The TOE provides CAVP certified cryptography in support of its TLS implementation.&nbsp;&nbsp;&nbsp; Cryptographic services include key management, random bit generation, encryption/decryption, digital signature and secure hashing.</p>\r\n<p><strong>User Data Protection</strong> - The TOE ensures that residual information is protected from potential reuse in accessible objects such as network packets.</p>\r\n<p class=\"Body\"><strong>Identification and Authentication</strong> - The TOE requires users to be identified and authenticated before they can use functions mediated by the TOE, with the exception of reading the login banner.&nbsp; It provides the ability to both assign attributes (user names, passwords and roles) and to authenticate users against these attributes.</p>\r\n<p><strong>Security Management</strong> - The TOE provides a command line (CLI) management interface as well as a graphical user interface (GUI) accessed via the web.&nbsp; The web interface is protected with TLS. The management interface is limited to the authorized administrator (as defined by a role).</p>\r\n<p class=\"Body\"><strong>TSF Protection</strong> - The TOE provides a variety of means of protecting itself.&nbsp; The TOE performs self-tests that cover the correct operation of the TOE. It provides functions necessary to securely update the TOE.&nbsp; It provides a hardware clock to ensure reliable timestamps.&nbsp; It protects sensitive data such as stored passwords and cryptographic keys so that they are not accessible even by an authorized administrator.</p>\r\n<p><strong>TOE Access</strong> - The TOE can be configured to display a logon banner before a user session is established.&nbsp; The TOE also enforces inactivity timeouts for local and remote sessions.</p>\r\n<p class=\"Body\"><strong>Trusted Path/Channels</strong> - The TOE provides a local console which is subject to physical protection. For remote access, the web GUI is protected by TLS thus ensuring protection against modification and disclosure.</p>\r\n<p class=\"Body\">The TOE also protects its audit records from modification and disclosure by using TLS to communicate with the syslog server.</p>","features":[]}