Information Systems Security Manager (ISSM) - Marine Corps ...

NAVSO P-5239-04SEPTEMBER 1995FOREWORDThe Navy Staff Office Publication (NAVSO P) 5239, Information Systems Security(INFOSEC) Program Guidelines is issued by the Naval Information Systems ManagementCenter. It consists of a series of modules that provide procedure, technical, administrative,and supplemental guidance for all information systems, whether business or tactical. Itapplies to information systems used in the automated acquisition, storage, manipulation,management, movement, control, display, switching, interchange, transmission, or receipt ofdata. Each module focuses on a distinct program element and describes a standardmethodology for planning, implementing, and executing that element of the INFOSECprogram within the Department of the Navy (DON).This module, the Information Systems Security Manager (ISSM) Guidebook, describesthe roles and responsibilities of the ISSM within the DON INFOSEC program.Terminology associated with information systems in general, and INFOSECspecifically, varies from service to service and from Command to Command. The AutomatedData Processing Security Officer (ADPSO) from a decade ago is now referred to as an ISSM.Section 2 discusses common DON terms for INFOSEC roles.Organizational differences make it difficult to precisely define discrete roles andresponsibilities, because organizations may choose to implement the ISSM responsibilitiesdefined in this guidebook differently. For example, the location and size of the activity orCommand, and the complexity of the ISs and networks may dictate how the role of the ISSMis implemented. In large Commands the security responsibilities defined here may be dividedamong numerous security personnel. Some Commands may have a single individualperforming all the functions identified. Regardless of the implementation, the guidebookaddresses the broadest set of functions identified for the ISSM position.During the preparation of this guidebook, several activities were contacted andinterviewed for technical inputs. The security personnel of the Commander-in-Chief, U.S.Atlantic Fleet (CINCLANTFLT), the Space and Naval Warfare Systems Command(SPAWAR), and the Naval Sea Systems Command Automated Data System Activity(SEAADSA) were extremely helpful in providing information and guidance.ii