Content deleted Content added
IznoPublic (talk | contribs) remove unnecessary collapsing |
Citation bot (talk | contribs) Alter: url. URLs might have been anonymized. Add: archive-date, archive-url. Removed parameters. | Use this bot. Report bugs. | Suggested by BrownHairedGirl | Linked from User:BrownHairedGirl/url=web.archive.org | #UCB_webform_linked 505/2186 |
||
Line 6:
== 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>{{Cite web|date=2010-06-19|title=Host Based Security System (HBSS)|url=http://www.disa.mil/hbss/index.html|access-date=2021-08-18|archive-url=https://web.archive.org/web/20100619104318/http://www.disa.mil/hbss/index.html|
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>{{Cite web|date=2010-12-05|title=infoexchange|url=http://www.afcea.org/events/landwarnet/08/infoexchange.asp|access-date=2021-08-18|archive-url=https://web.archive.org/web/20101205013909/http://www.afcea.org/events/landwarnet/08/infoexchange.asp|
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 119:
==== 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>{{Cite web|date=2011-01-20|title=DoD Can Use USB Securely {{!}} Blog Central|url=http://blogs.mcafee.com/enterprise/public-sector/dod-can-use-usb-securely|access-date=2021-08-18|archive-url=https://web.archive.org/web/20110120192355/http://blogs.mcafee.com/enterprise/public-sector/dod-can-use-usb-securely|
==== Assets publishing service ====
Line 133:
== 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>{{Cite web|date=2010-02-12|title=DoD Information Assurance Tools|url=http://iase.disa.mil/tools/index.html|access-date=2021-08-18|archive-url=https://web.archive.org/web/20100212232302/http://iase.disa.mil/tools/index.html|
{|
|