000			01613 a2200277 4500
008			051207s xx 000 0 eng
022			_a1522-3264;
050			_aAC1.S5
082			_a050
100			_aBurke, Bill,
245		0	_aCyberwar. _cBill Burke.
260			_bVirginian-Pilot, _c2005.
440			_aSIRS Enduring Issues 2006. _nArticle 72, _pScience, _x1522-3264;
500			_aArticles Contained in SIRS Enduring Issues 2006.
500			_aOriginally Published: Cyberwar, June 26, 2005; pp. A1+.
520			_a"On a Thursday morning in May [2005], as some three dozen sailors in uniform and a handful of tieless civilians gathered around, the briefing officer delivered the news: There had been a Category 1 incident at a large local Navy installation. For the assembled group, a Category 1 was serious business--not the low end of the scale, like the one hurricane trackers use. Someone out there in cyberspace had seized control of a couple of the Navy's network computers. Incidents of this magnitude could damage equipment, scramble data or even result in harm to sailors." (VIRGINIAN-PILOT) This article describes cyberattacks on Navy computers and examines how the Navy is fighting these attacks.
599			_aRecords created from non-MARC resource.
650			_aComputer hackers
650			_aComputer security
650			_aCyberterrorism
650			_aInternet crimes
610			_aU.S. _bDept. of Defense
610			_aU.S. Navy _xCommunication systems
710			_aProQuest Information and Learning Company _tSIRS Enduring Issues 2006, _pScience. _x1522-3264;
942			_c UKN
999			_c37827 _d37827