Encl (1) SSPINST 5500.1.pdf

DEPARTMENT OF THE NAVY

DIRECTOR, STRATEGIC SYSTEMS PROGRAMS

1250 10TH STREET SE SUITE 3600

WASHINGTON NAVY YARD DC 20374-5127

SSPINST 5500.1

SP33

7 Nov 2023

SSP INSTRUCTION 5500.1

From: Director, Strategic Systems Programs

Subj: CHECK-IN AND CHECK-OUT PROCEDURES FOR RESIDENT CONTRACTOR

PERSONNEL

Ref: (a) OPNAVINST 3440.17A, Navy Installation Emergency Management Program

(b) SSPINST 5300.1S Check-In Check Out and Personnel Movement Procedures for

Civilian Personnel

(c) SSPINST 5239.15B, User Access Program For Strategic Systems Programs

Information Systems

(d) SSPINST 5230.9C, Appropriate Use of Strategic Systems Programs Information

Technology Resources

(e) DoD Manual 5220.32, Volume 1, National Industrial Security Program: Industrial

Security Procedures for Government Activities of 1 Aug 2018

(f) SECNAVINST 5510.36B, Department of the Navy Information Security Program

Encl: (1) SSP Resident Contractor Package

1. Purpose. To provide policy and assign responsibilities for the check-in and check-out process for Strategic Systems Programs (SSP) resident contractors.

a. Background. SSP contractors are an essential element of the SSP workforce. To comply with reference (a), SSP provides for the successful integration of resident contractors into the organization by ensuring they receive proper orientation and training and are accurately accounted for in local emergency plans. This directive is created to meet this objective.

b. Reason for Change. To clarify the use of the term “resident contractors” and update the check-in and check-out procedures.

c. Authority. Reference (a) provides Director, Strategic Systems Programs the authority to issue this directive.

d. Scope and Applicability

(1) This directive applies to resident contractors, also referred to as onsite contractors, who work on contract in SSP spaces and are required to follow governing security requirements

(information, physical, and personnel).

Note: This directive applies Enterprise-Wide. Field activities, including the Strategic

Weapons Facilities (SWF), Naval Ordnance Test Unit (NOTU), and Program

Management Offices (PMOs), must develop local operating procedures for site-specific guidance, routinely.

(2) It does not apply to offsite contractors who work from their corporate location and use corporate assets or Government Furnished Equipment to access Strategic Weapons Systems applications via either a corporate connection to the Strategic Weapons Systems Network

(SWSNET) or the SWSNET Application Gateway.

2. Cancellation. SSPINST 5230.18 is canceled and superseded in its entirety.

3. Policy. It is SSP policy that resident contractors:

a. Complete the Resident Contractor Package provided by the sponsor and found on the

Security homepage under the "Industrial Security" tab.

b. Attend a local SSP Security or local field activity security orientation as applicable before receiving an SSP badge. If the local SSP Security orientation cannot happen prior to receiving an SSP badge, the Resident Contractor Package will be returned to the field activity Security

Office or the SPHQ Security Front Desk within 5 business days of on-boarding.

c. Adhere to all requirements in references (c) and (d) to obtain and maintain access to SSP information technology (IT) systems and assets as required to perform their duties.

d. For SPHQ and Field Activities complete all mandatory training listed in Resident

Contractor Package via Department of the Navy (DON) Total Workforce Management Services

(TWMS).

4. Responsibilities

a. Branch and Field Activity Heads are responsible for the overall implementation of this directive. They must ensure their resident contractors adhere to the policy and procedures contained herein.

b. Government supervisors or sponsors will:

(1) Provide the resident contractor with the Resident Contractor Package and ensure the completed checklist is returned to the local Security Office.

(2) Follow reference (c) to request access to SSP IT systems and assets be issued to their resident contractors if required to perform their duties.

(3) Return SSP IT assets issued to their resident contractors to the local SSP IT Help

Desk upon their separation from supporting the contract.

c. Resident Contractor local supervisor will:

(1) Make arrangements for facility access (i.e., Common Access Cards (CAC), SSP badge, base parking).

(2) Escort resident contractor in government spaces until facility access is gained.

(3) Notify local SSP Security Office that resident contractor will be working on-site and confirm that they have received the Resident Contractor Package.

(4) Direct new resident contractor to local IT Help Desk for IT training and orientation.

(5) Introduce new resident contractor to government staff members.

(6) Escort separating resident contractor to the local IT Help Desk to return all IT assets

(i.e. laptop, SIPRNET token) and to the local security office to turn in their CAC and SSP badge during check-out.

d. Local SSP Security Manager will:

(1) Maintain the Resident Contractor Checklist once completed.

(2) Conduct local security orientation for arriving contractors.

(3) Complete “Part III - Security Manager Validates the Background Investigation or clearance Information” of the SAAR-N for all resident contractor accounts and all SSP

Classified Local Area Network accounts, per reference (c).

(4) Maintain official local resident contractor roster.

(5) Conduct, in coordination with Total Force Management Branch (SPHR44), an annual validation of the resident contractors in TWMS against the official local resident contractor roster.

e. Local SSP Training Coordinator ( i.e.,SPHR44) will:

(1) Add resident contractors in TWMS that are on the official resident contractor roster.

(2) Publish mandatory training to resident contractors in TWMS. See Resident

Contractor Package list.

(3) Provide training reports to local security office and Information Systems Security

Manager (ISSM) or Special Security Officer (SSO) upon request.

f. SSP Enterprise Business Office (SPEBO) will add resident contractors to Navy

Enterprise Resource Planning, if required.

g. SSP resident contractor will:

(1) Complete the Resident Contractor Package and provide to local security office.

(2) Comply with all applicable policies and guidance while working in SSP spaces.

Report any security incidents to Command Security Officer and Industrial Security SP3222.

(3) Take mandatory training by due date (due dates are announced in the SSP Newsletter or via electronic mail).

(4) Follow all guidance obtained during Security and IT orientations.

(5) Notify government supervisor or sponsor when separating from SSP.

Note: Resident Contractor should make an appointment 2 to 3 days before departure date with local security office for security debriefing, per the Resident Contractor Package.

(6) Return SSP-issued IT assets to the local SSP IT Helpdesk and SSP badge and CAC to the local security office upon separating from SSP.

5. Records Management

a. Records created as a result of this directive, regardless of format or media, must be maintained and dispositioned per the records disposition schedules located on the DON Assistant for Administration, Directives and Records Management Division portal page at https://portal.secnav.navy.mil/orgs/DUSNM/DONAA/DRM/Records-and-Information-

Management/Approved%20Record%20Schedules/Forms/AllItems.aspx.

b. For questions concerning the management of records related to this directive or the records disposition schedules, please contact the SPHQ Records Manager (SP153) or the

OPNAV Records Management Program (DNS-16).

6. Review and Effective Date. Per OPNAVINST 5215.17A, SP33 will review this directive annually around the anniversary of its issuance date to ensure applicability, currency and consistency with Federal, DoD, Secretary of the Navy and Navy policy and statutory authority using OPNAV 5215/40 Review of Instruction. This directive will be in effect for 10 years, unless revised or canceled in the interim and will be reissued by the 10-year anniversary date if it is still required, unless it meets one of the exceptions in OPNAVINST 5215.17A, paragraph 9.

Otherwise, if the directive is no longer required, it will be processed for cancellation as soon as the need for cancellation is known following the guidance in OPNAV Manual 5215.1 of May

2016 and SSP Manual 5215.1 of July 2017.

7. Forms Control. All forms referenced in this directive can be obtained from SP332 Security

Web site https://web.swsnet.ssp.navy.mil/sp332/industrial-security

T. C. ARNOLD-BERRIOS

By direction

Releasability and Distribution:

This instruction is not cleared for public release and is available electronically to SSP users via the SSP eSSPINST Web site.

https://web.swsnet.ssp.navy.mil/sp332/industrial-security

DD Mmm YYYY

Enclosure (1)

SSP RESIDENT CONTRACTOR PACKAGE

2 Enclosure (1)

3 Enclosure (1)

4 Enclosure (1)

5 Enclosure (1)

6 Enclosure (1)

7 Enclosure (1)

8 Enclosure (1)

9 Enclosure (1)

10 Enclosure (1)

11 Enclosure (1)

12 Enclosure (1)

13 Enclosure (1)

14 Enclosure (1)

15 Enclosure (1)

16 Enclosure (1)