Content deleted Content added
Branding changes for VirusScan Enterprise to McAfee VirusScan Enterprise. |
m clean up spacing around commas and other punctuation fixes, replaced: ,h → , h (2) |
||
| (17 intermediate revisions by 17 users not shown) | |||
Line 1:
{{Short description|Department of Defense suite of software applications}}
{{
== History ==
Seeing the need to supply a comprehensive, department-wide security suite of tools for DOD System Administrators, the ESSG started to gather requirements for the formation of a host-based security system in the summer of 2005. In March 2006, [[BAE Systems]] and McAfee were awarded a contract to supply an automated host-based security system to the department. After the award, 22 pilot sites were identified to receive the first deployments of HBSS.<ref>
On October 9, 2007, the [[Joint Task Force for Global Network Operations]] (JTF-GNO) released [[Communications Tasking Order]] (CTO) 07-12 (''Deployment of Host Based Security System (HBSS)'') mandating the deployment of HBSS on all Combatant Command, Service and Agency (CC/S/A) networks within DOD with the completion date by the 3rd quarter of 2008.<ref>
Lessons learned from the pilot deployments provided valuable insight to the HBSS program, eventually leading to the [[Defense Information Systems Agency]] (DISA) supplying both pre-loaded HBSS hardware as well as providing an HBSS software image that could be loaded on compliant hardware platforms. This proved to be invaluable to easing the deployment task on the newly trained HBSS System Administrators and provided a consistent department-wide software baseline. DISA further provided step-by-step documentation for completing an HBSS baseline creation from a freshly installed operating system. The lessons learned from the NIPRNet deployments simplified the process of deploying HBSS on the SIPRNet.
Line 15:
* March 27, 2007: The ESSG approved the HBSS for full-scale deployment throughout the DoD enterprise
* October 9, 2007: The [[Joint Task Force for Global Network Operations|JTF-GNO]] releases CTO 07-12
* November, 2009: The [[United States Air Force|Air Force]] awarded [[Northrop Grumman
== HBSS components ==
Throughout its lifetime, HBSS has undergone several major baseline updates as well as minor maintenance releases. The first major release of HBSS was known as Baseline 1.0 and contained the McAfee ePolicy orchestrator engine, HIPS, [[software compliance profiler]] (SCP), [[rogue system detection]] (RSD), [[asset baseline manager]] (ABM), and assets software. As new releases were introduced, these software products have evolved, had new products added, and in some cases, been completely replaced for different products.
As of January, 2011, HBSS is currently at Baseline 4.5, Maintenance Release 2.0 (MR2). MR2 contains the following software:▼
=== HBSS Baseline 4.5 MR2 components ===
▲As of January, 2011, HBSS is currently at Baseline 4.5, Maintenance Release 2.0 (MR2). MR2 contains the following software:
==== Microsoft products ====
{|
|-
! Software application
Line 58 ⟶ 52:
==== Optional products/components ====
{|
|-
! Software application
Line 77 ⟶ 71:
==== SIPRNet-only products/components ====
{|
|-
! Software application
Line 87 ⟶ 81:
| Rollup Extender
| 1.2.8
|}
== How HBSS works ==
The heart of
* Providing a consistent front-end to the point products
* Consolidating point product data for analysis
Line 100 ⟶ 92:
<!----==== Security compliance profiler ====
The security compliance profiler (SCP) was one of the original products provided in HBSS Baseline 1.0. It was removed from HBSS as of Baseline 2.0 and replaced with the policy auditor component. The SCP is an integral component of ePO that provides enterprise-wide reporting on security patches, including the Microsoft® operating systems.<ref>'''System Compliance Profiler''', http://www.mcafee.com/us/enterprise/products/promos/system_security_management/epolicy_orchestrator/compliance_profiler.html, 3/14/2010</ref>
---->
Line 125 ⟶ 117:
==== Device control module/data loss prevention ====
The DCM component of HBSS was introduced in HBSS Baseline 2.0 specifically to address the use of USB devices on DOD networks. JTF-GNO CTO 09-xxx, ''removable flash media device implementation within and between Department of Defense (DOD) networks'' was released in March, 2009 and allowed the use of USB removable media, provided it meets all of the conditions stated within the CTO. One of these conditions requires the use of HBSS with the DCM module installed and configured to manage the USB devices attached to the system.<ref>
==== Assets publishing service ====
Line 131 ⟶ 123:
== Obtaining HBSS ==
According to JTF-GNO CTO 07-12, all DOD agencies are required to deploy HBSS to their networks. DISA has made HBSS software available for download on their [[Public key infrastructure|PKI]] protected [https://patches.csd.disa.mil/ patch server]. Users attempting to download the software are required to have a [[
Additionally, HBSS administrators require the satisfactory completion of HBSS training and are commonly appointed by the unit or section commander in writing.
== Learning HBSS ==
In order to receive and administer an HBSS system, system administrators must satisfactorily complete online or in class HBSS training as well as be identified as an HBSS administrator. Online training takes 30 hours to complete while in class training requires four days, excluding travel. An advanced HBSS class is also available to HBSS administrators wishing to acquire a more in-depth knowledge of the system. HBSS online and in class training is managed by DISA
== HBSS support ==
The DISA Risk Management Executive Office (RE) formerly [[field security office]] (FSO) provides free technical support for all HBSS Administrators through their help desk. DISA has three tiers of support, from Tier I to Tier III. Tier I and Tier II support is provided by DISA FSO, while Tier III support is provided by McAfee. DISA FSO Support is available using one of the following methods:<ref>
{|
| |||