MARADMIN 165/24
R 031126Z APR 24
MSGID/GENADMIN/CMC DCI WASHINGTON DC//
SUBJ/SENSITIVE COMPARTMENTED INFORMATION SECURITY PROGRAM ESTABLISHMENT PROCESS//
REF/A/DODM 5105.21, VOL 1//
REF/B/DODM 5200.01, VOL 1//
REF/C/SECNAVINST 5510.30C//
REF/D/MCO 5510.18B//
REF/E/MCO 5311.1E//
REF/F/MARADMIN 411/23//
NARR/REF A IS SCI ADMINISTRATIVE SECURITY MANUAL: ADMINISTRATION OF INFORMATION AND INFORMATION SYSTEMS SECURITY. REF B IS DOD INFO SEC PROGRAM; OVERVIEW, CLASSIFICATION, AND DECLASSIFICATION. REF C IS DON PERSONNEL SECURITY PROGRAM. REF D IS USMC INFORMATION AND PERSONNEL SECURITY PROGRAM. REF E IS TOTAL FORCE STRUCTURE PROCESS. REF F IS USMC INTELLIGENCE COMMUNITY DIRECTIVE 705 FACILITY PRE-CONSTRUCTION AND ACCREDITATION PROCESS.//
POC/DC I/C. BAER/CIV/SSO, DC I/703-693-6005/CHARLENE.BAER@USMC.MIL//
POC/DC I/D. CORNELIUS/GYSGT/SSR, DC I/703-693-9164/DAVID.CORNELIUS@USMC.MIL//
POC/DC I/HQMC_INTEL_SSO@USMC.MIL//
GENTEXT/REMARKS/1.  Purpose.  This MARADMIN outlines the authorities and requirements for establishing a command sensitive compartmented information (SCI) program and amplifies guidance provided in reference (f).
2.  Background.  In order to fulfill mission requirements associated with the Stand-In Forces (SIF) concept and to perform other sensing and sense-making tasks on behalf of the Joint Force, a large number of Marine battalions, squadrons, and other units will require the capability to receive, process, store, and transmit data at the TOP SECRET/SENSITIVE COMPARTMENTED INFORMATION (TS/SCI) level.  To do so with appropriate security and agility, these units will all require TS/SCI programs.
2.a.  To facilitate the expansion of Intelligence Community Directive (ICD) 705-compliant facilities and the delivery of associated systems and equipment to meet the demands of the Service’s Force Design, commands that do not currently have an SCI program and a Special Security Officer (SSO) will need to establish both and be accredited in order to receive an ICD 705 facility and SCI equipment.
2.b.  A unit does not require its own ICD-705 compliant facility to have an SCI program.  A unit must have an SCI program, however, to oversee and manage an ICD-705 facility.
3.  Execution.
3.a.  Per references (a) – (d), upon determining that their commands require SCI tasks, functions, data, programs, systems, equipment, or facilities to perform their missions, commanding officers shall establish their commands’ SCI Security Programs.  An SCI program requires commanders to designate, in writing, a Senior Intelligence Officer (SIO) and an SSO.  Designated individuals must either have a military rank at or above the E7 level, or a civilian grade of GS9 or above.
3.a.1.  Per reference (a), the designated command SSO works directly for the SIO and is responsible for the day-to-day security, management, operations, implementation, use, and dissemination of SCI within the activity.  The SSO shall have direct access to the commanding officer for personnel security matters. 
3.a.2.  In accordance with reference (c), units seeking to establish an SCI program must send their SIO and SSO designation letters to the United States Marine Corps (USMC) SSO in order to establish the command’s security organizational code in the Defense Information Security System (DISS).  Every SCI personnel security program requires these documents.  The USMC SSO will assist the command SSO and will provide him or her with instructions regarding policies and requirements related to SCI personnel security, SCI information security, physical security, security training, and other procedures needed to support the command’s SCI security program and SSO assignment.
3.a.3.  Per references (b) and (c), the SSO may be designated as the activity security manager (ASM) if he or she meets the grade requirements for the position.  However, the activity security manager cannot function as the SSO without the endorsement of the Service’s Head of the Intelligence Community Element (HICE), Headquarters Marine Corps’ (HQMC) Deputy Commandant for Information.  Commands shall submit Command SSO and ASM designation letters to the USMC SSO for HICE endorsement.
3.b.  In order to establish the requirement for an SCI program, commanders must modify their units’ missions and tables of organization and equipment.
3.b.1.  To that ensure personnel at each unit are cleared for appropriate systems access, commanders must identify which billets require SCI access and, in accordance with reference (e), submit a table of organization and equipment change request (TOECR) to modify billet identification codes (BIC) for all personnel who need it.  The SCI designator for BICs is commonly known as an “I” code.
3.b.2.  To modify their unit’s mission and equipment set, commanders must submit a MCBUL 5400 that changes its mission and table of equipment (T/E) to incorporate SCI.
3.c.  Steps necessary to create an SCI Program.
3.c.1.  Commander establishes the operational necessity for SCI access.
3.c.2.  Command requests and receives an approved TOECR to convert BIC's to “SCI required” (“I” code).
3.c.3.  HQMC publishes MCBUL 5400 changing the unit mission and associated tables of equipment to account for SCI materials.
3.c.4.  Commander designates SIO and SSO in writing.
3.c.4.a.  Command submits SIO/SSO designation letters to USMC SSO.
3.c.4.b.  USMC SSO establishes Command SCI SMO Code in DISS.
3.c.5.  USMC SSO coordinates with Command SSO to establish a command SCI security program with all applicable policies, procedures, and all required training.
3.c.6.  Command SSO attends ICD 704 training for SCI personnel security management.
3.c.7.  Command SSO attends ICD 705 training for SCI physical security, construction, and management
4.  Coordinating Instructions.
4.a.  SSO and ASM designation letters shall specify the training and certifications required for each position in accordance with references (a) - (d).  For example, if an individual is designated as both the SSO and ASM, both sets of training requirements must be annotated in the designation letter.
4.b.  Per para 9.e.  of reference (d), the command security instruction shall delineate the duties of the Command Security Manager and the SSO to ensure proper coordination, and to prevent gaps in coverage between these separate programs’ responsibilities.
5. Direct all questions to MARADMIN points of contact.
6. Release authorized by LtGen Matthew G. Glavy, Headquarters Marine Corps, Deputy Commandant for Information.//