**KSC SECURITY HANDBOOK**

**\* Responsible Office**: Director of Spaceport Services

##### PREFACE

This handbook provides instructions and procedures to implement an
effective Kennedy Space Center (KSC) Security Program. It applies
directly to KSC, Florida, and will be complied with, to the fullest
extent possible, in other areas which are under the jurisdiction of KSC.

In instances where a conflict may exist between KSC requirements and
other agency requirements affecting other KSC jurisdictional activities,
the more stringent security guidance may be applied. However, any such
conflicts will be referred to the KSC Protective Services Branch for
resolution.

This handbook will be revised as the development of new and improved
security concepts dictate.

This Handbook supersedes KHB 1610.1B, in its entirety.

> J. Chris Fairey
>
> Director of Spaceport Services

Distribution:

Tech Doc Library

**TABLE OF CONTENTS**

**SECTION I: GENERAL**

**[PARA.]{.underline} [PAGE]{.underline}**

**CHAPTER 101 - INTRODUCTION**

101.1 Purpose 101-1

101.2 Applicability and Space 101-1

**CHAPTER 102 - RESPONSIBILITY FOR SAFEGUARDING**

102.1 General 102-1

102.2 Kennedy Space Center Installation Security Officer 102-1

102.3 NASA KSC Employees 102-2

102.4 Incorporation Into Contracts 102-3

102.5 Heads of Primary Organizations 102-3

**CHAPTER 103 - EXECUTIVE SUMMARY**

103.1 General 103-1

103.2 Information Security 103-1

103.3 Technical Security 103-2

103.4 Physical Security 103-2

**CHAPTER 104 - SECURITY INSPECTIONS AND AUDITS**

104.1 Purpose 104-1

104.2 Responsibilities 104-1

104.3 General Provisions 104-1

104.4 Audits 104-2

104.5 Security Inspections 104-3

104.6 Violations 104-3

**SECTION II: INFORMATION SECURITY**

**CHAPTER 201 - SECURITY AWARENESS AND TRAINING**

201.1 General 201-1

201.2 Organizational Requirements 201-1

201.3 Briefings 201-2

201.4 Security Awareness Library 201-4

201.5 Required Documentation 201-4

**CHAPTER 202 - CLASSIFYING AND MARKING**

202.1 Classified Information 202-1

202.2 Classifying Information 202-1

202.3 Marking Classified Material 202-4

202.4 Document Markings 202-4

202.5 Page Marking 202-5

202.6 Portion Marking 202-6

202.7 Compilations 202-7

202.8 File, Folder, or Group of Documents 202-7

202.9 Transmittal Documents 202-7

202.10 Wholly Unclassified Material 202-7

202.11 Notes, Drafts, Working Papers 202-7

202.12 Electronically Transmitted Messages 202-8

202.13 Special Categories of Material 202-8

202.14 Declassifying and Downgrading 202-10

202.15 Warning Notices 202-10

202.16 Remarking Old Material 202-11

202.17 Marking Foreign Classified Material 202-12

**CHAPTER 203 - SAFEGUARDING CLASSIFIED MATERIAL**

203.1 General 203-1

203.2 Access to Classified Material 203-1

203.3 Storage 203-1

203.4 Storage Provisions 203-2

203.5 Storage Containers 203-2

203.6 Combinations 203-4

203.7 Opening, Locking, and Checking Storage Containers 203-6

203.8 Accounts 203-7

203.9 Account Custodians 203-7

203.10 Designating Custodians 203-8

203.11 Accountability 203-9

203.12 Accountability Records 203-11

203.13 Accountability Procedures 203-11

203.14 Inventories 203-15

203.15 Assistance Visits 203-15

203.16 Transmission 203-15

203.17 Incoming Shipments 203-19

203.18 Reproduction 203-20

203.19 Destruction 203-22

203.20 Destruction Procedures 203-22

203.21 Foreign Government Information 203-23

203.22 Secure Conference Rooms 203-23

**CHAPTER 204 - CLASSIFIED INFORMATION INCIDENT REPORTING**

204.1 General 204-1

204.2 Security Violation and Compromise

of Classified Information 204-1

204.3 Other Reportable Incidents 204-5

204.4 Training 204-5

204.5 Penalties 204-6

> **CHAPTER 205 - FOREIGN CONTACTS, REQUESTS FOR INFORMATION AND FOREIGN
> TRAVEL**

205.1 General 205-1

205.2 Responsibilities 205-1

205.3 Reporting Contacts with Foreign Nationals

and Representatives of a Designated Country

or Area 205-1

205.4 Reporting Requests for Information 205-2

205.5 Foreign Travel 205-3

205.6 Designated Countries and Areas 205-5

**SECTION III: TECHNICAL SECURITY**

**CHAPTER 301 - TECHNICAL SECURITY SAFEGUARD SYSTEMS**

301.1 General 301-1

301.2 Concept 301-1

301.3 System Descriptions 301-1

301.4 Requirements 301-2

301.5 Intrusion Detection Systems 301-3

301.6 Close Circuit Television (CCTV) 301-15

301.7 Access Control Systems (ACS) 301-15

301.8 System Upgrade 301-16

**CHAPTER 302 - COMMUNICATIONS SECURITY**

302.1 General 302-1

302.2 Responsibilities 302-1

302.3 Objectives 302-5

302.4 COMSEC Program 302-5

302.5 COMSEC Equipment Maintenance 302-6

302.6 COMSEC Material Control System 302-7

302.7 Emergency Planning and Actions 302-7

302.8 COMSEC Evaluations 302-9

302.9 COMSEC Awareness 302-9

302.10 COMSEC Training 302-10

> **CHAPTER 303 -TEMPEST\--CONTROL OF COMPROMISING EMANATIONS**

303.1 General 303-1

303.2 Responsibilities 303-1

303.3 TEMPEST 303-2

**CHAPTER 304 - TECHNICAL SURVEILLANCE COUNTERMEASURES**

304.1 General 304-1

304.2 Responsibilities 304-1

304.3 Requirements 304-2

304.4 Procedures 304-2

304.5 Discovery of Devices/Suspect Devices 304-3

**SECTION IV: PHYSICAL SECURITY**

**CHAPTER 401 - LAW ENFORCEMENT**

401.1 General 401-1

401.2 Law Enforcement Duties 401-1

401.3 Jurisdiction 401-5

401.4 NASA and J-BOSC Points of Contact 401-8

**CHAPTER 402 - PROTECTIVE FORCES**

402.1 General 402-1

402.2 Management of Protective Forces 402-2

402.3 Protective Forces Duties 402-4

402.4 Protective Forces Training 402-6

402.5 Protective Forces Equipment 402-8

**CHAPTER 403 - INCIDENT MANAGEMENT SYSTEM**

403.1 General 403-1

403.2 Responsibilities 403-1

403.3 Security Incident Management Team 403-2

403.4 Preparation and Planning 403-2

403.5 Natural Disasters 403-3

403.6 Bombs and Bomb Threats 403-3

403.7 Hostage/Terrorist Incidents 403-5

403.8 Criminal Acts 403-11

**CHAPTER 404 - BADGES AND PASSES**

404.1 General 404-1

404.2 Responsibilities 404-1

404.3 Access to KSC/Cape Canaveral Air Force Station

(CCAFS) 404-1

404.4 Badge Receipting 404-3

404.5 Display and Control of the Badge 404-3

404.6 Lost Badge/Area Permit Reporting 404-4

404.7 Termination, Leave of Absence,

Vacation, and Foreign Travel 404-5

404.8 Violations 404-5

404.9 Pass Requests by Telephone 404-6

404.10 Adverse Information Reporting 404-6

404.11 Resident Badges 404-6

404.12 Nonresident Badges 404-8

404.13 Temporary Passes (Machine Passes) KSC Form 28-100 404-10

404.14 Guest Badges 404-17

404.15 Exit Pass 404-19

404.16 Special Badges and Placards 404-19

**CHAPTER 405 - PERSONNEL CONTROL AND AREA PERMITS**

405.1 General 405-1

405.2 Responsibilities 405-1

405.3 Display and Safeguarding of KSCAP and TAA 405-2

405.4 Access Provisions 405-2

405.5 Safety Familiarization Requirements 405-5

405.6 Temporary Area Authorizations 405-5

405.7 Requesting Area Permits, PACAS Cards, TAA's 405-6

405.8 Lost Area Permit, TAA, or PACAS Card 405-7

\***CHAPTER 406 - FOREIGN VISITORS**

406.1 General 406-1

406.2 Responsibilities 406-1

406.3 Visitor Identification/Program Definitions 406-2

406.4 Visit Types and Definitions 406-3

406.5 Visit Request Procedures 406-4

406.6 Access Authorizations 406-5

406.7 Accreditation Process 406-6

406.8 Tours 406-7

406.9 Foreign Public Information Media 406-7

406.10 Discussions and Requests for Materials 406-7

406.11 Extending Invitations to Visit NASA/KSC 406-8

406.12 Visits to Merritt Island (MILA) Spacecraft

Tracking Data Network (STDN) Station, Florida 406-8

\*Denotes change.

**CHAPTER 407 - SECURITY MEASURES**

407.1 General 407-1

407.2 Security Areas 407-1

407.3 Access Controls 407-2

407.4 Perimeter and Area Protection and Control 407-2

407.5 NASA Resource Protection Program 407-3

407.6 Inspection of Persons and Personal Effects

on NASA Property 407-3

**CHAPTER 408 - PROTECTIVE BARRIERS AND OPENINGS**

408.1 Protective Barriers and Openings 408-1

408.2 Barricade Classification and Specifications 408-4

408.3 Security Fences 408-6

408.4 Walls 408-8

408.5 Perimeter Openings 408-9

408.6 Inspection of Barriers 408-12

408.7 Signs and Posting of Boundaries 408-12

**CHAPTER 409 - PROTECTIVE LIGHTING**

409.1 Protective Lighting 409-1

409.2 Types of Protective Lighting 409-2

409.3 Specification of Illumination 409-4

409.4 Emergency Power 409-4

409.5 Maintenance 409-4

409.6 Controls and Switches 409-5

**CHAPTER 410 - PORT AND HARBOR SECURITY**

410.1 General 410-1

410.2 Responsibilities 410-1

410.3 Sensitivity 410-3

410.4 Safeguards and Security Measures 410-3

410.5 Transportation, Accountability, and Documentation 410-4

410.6 Security Forces 410-4

410.7 Harbor and Waterway Patrol 410-4

**CHAPTER 411 - TRAFFIC AND PARKING CONTROL**

411.1 Purpose 411-1

411.2 General 411-1

411.3 Moving/Nonmoving Traffic Regulations 411-1

411.4 Overweight/Overdimension Equipment/Vehicles/ Authority/Escort
411-7

411.5 Crash Reporting Procedure 411-12

411.6 KSC Traffic Citation Point Assessment System 411-12

411.7 KSC Traffic Appeals System 411-13

411.8 Assignment of Reserved Parking Spaces 411-14

411.9 Assignment Responsibilities for Reserved Parking 411-15

411.10 Procedures for Requesting Reserved Parking 411-16

411.11 Traffic Management Review Board 411-21

**CHAPTER 412 - VIOLATIONS OF LAW INCIDENT REPORTING**

412.1 General 412-1

412.2 Behavior of Cleared Persons 412-2

412.3 Other Reportable Incidents 412-2

412.4 Penalties 412-3

**CHAPTER 413 - TRANSPORTATION AND MATERIAL SECURITY**

413.1 General 413-1

413.2 Types of Cargo/Material 413-1

413.3 Responsibilities 413-2

413.4 Minimum Standards 413-4

413.5 Nonofficial Deliveries 413-12

**CHAPTER 414 - REGISTERED KEY AND LOCK SYSTEM (RKLS), LOCKSMITH
SERVICES**

414.1 Purpose 414-1

414.2 Responsibilities 414-1

414.3 General 414-3

414.4 Key Control Custodians and Alternates 414-4

414.5 Key and Lock Accountability/Control 414-4

414.6 J-BOSC Locksmith Services 414-9

414.7 Key Security/Control 414-7

414.8 Audits/Accountability 414-7

414.9 KSC Key Accountability System (KKAS) 414-7

414.10 Training 414-8

414.11 Key Audit Agent 414-9

**CHAPTER 415 - CONTROL OF WEAPONS**

415.1 General 415-1

415.2 Applicability 415-1

415.3 Policy 415-1

415.4 Definitions 415-1

415.5 Authority to Carry Firearms 415-2

415.6 Responsibilities 415-2

415.7 Control, Issuance, and Carrying of Firearms

by KSC Personnel 415-4

415.8 Possession of Weapons by KSC Employees and

Requests for Waivers 415-5

415.9 Prohibited Weapons and Items 415-7

**CHAPTER 416 - KSC FLAG POLICY**

416.1 General 416-1

416.2 Scope 416-1

416.3 Authority 416-1

416.4 Responsibilities 416-1

416.5 Procedures 416-2

**SECTION V: PERSONNEL SECURITY**

**CHAPTER 501 - KSC CHILD CARE DEVELOPMENT CENTER PROGRAM**

501.1 General 501-1

501.2 Responsibilities 501-1

501.3 Initiating Investigations for New Child Care Service Providers
501-3

501.4 Disqualifying Criteria 501-3

501.5 Adverse Information 501-5

501.6 Periodic Reinvestigations 501-5

**CHAPTER 502 - FEDERAL EMPLOYEE SECURITY PROGRAM (FESP)**

502.1 General 502-1

502.2 Position Sensitivity Levels 502-1

502.3 Responsibilities 502-2

502.4 NASA Pre-Employment Screening 502-3

502.5 Initiating Investigations for New NASA Employees 502-3

502.6 Periodic Reinvestigations 502-3

502.7 Security Clearances 502-4

502.8 Security Clearances for Civil Servants 502-5

502.9 Certifying Security Clearances from KSC 502-6

502.10 Certifying Security Clearances to KSC 502-6

502.11 Co-operative (Co-op) Education Students 502-7

**CHAPTER 503 - PERSONNEL RELIABILITY PROGRAM (PRP)**

503.1 General 503-1

503.2 Responsibilities 503-1

503.3 Mission Critical Space Systems Areas (MCSSA) 503-5

503.4 Other Area Designation Personnel Screening

Requirements 503-6

503.5 Authorized Requestors 503-6

503.6 Acceptance of Other Programs 503-7

503.7 Verifying PRP Certification to Other

Installations 503-8

503.8 Forms and Procedures 503-9

503.9 Specific Criteria 503-10

503.10 Disposition of Cases with Adverse Information 503-11

503.11 Employment Status 503-11

503.12 Interim PRP 503-11

**CHAPTER 504 - AUTOMATED INFORMATION PERSONNEL SECURITY PROGRAM**

504.1 General 504-1

504.2 Responsibilities 504-1

**APPENDICES**

Appendix A Definitions and Acronyms A-1

Appendix B Miscellaneous Controlled Activities B-1

Appendix C NASA and J-BOSC Points of Contact C-1

Appendix D KSC Barricade Locations D-1

**LIST OF REFERENCES**

[PUBLICATION NUMBER]{.underline} [PUBLICATION NAME]{.underline}

> Atomic Energy Act of 1954
>
> Executive Order No. 12065 National Security Information, June 28,
> 1978, 43 F.R. 28949
>
> Executive Order No. 12356 National Security Information, April 2,
> 1982, 47 F.R. 14874
>
> Florida Department of Transportation (FDOT) Manual
>
> Manual on Uniform Traffic Control Devices for Streets and Highways

Presidential Directive No. 42 National Space Policy, July 4, 1982

Presidential Proclamation 3044 Display of the Flag of the United States
of America at Half-staff upon the Death of Certain Officials and Former
Officials (as amended)

Public Law 93-288 Federal Response Plan, April 1992 (as amended)

Public Law 94-344 Flag of the United States - Display Rules

14 CFR Part 1205, Subpart 10 Inspection of Persons and Personal Effects
on NASA Property

14 CFR, Part 1214, Subpart 1214.5 STS Mission Critical Space System
Personnel Reliability Program

18 U.S.C. 799 Violations of Regulations of the National Aeronautics and
Space Agency

22 CFR Part 125 Arms Control Act

35 U.S.C. 205, Subpart 27.3 Federal Acquisition Regulation

[PUBLICATION NUMBER]{.underline} [PUBLICATION NAME]{.underline}

36 CFR Parks, Forests and Public Property

42 U.S.C. 2456 National Aeronautics and Space Act of 1958

50 CFR Wildlife and Fisheries

50 U.S.C. App. 2401-2420 Export Administration Act of 1979

DOD 5220.22-M National Industrial Security Operating Manual

ESMC JOP NO. 15E-3-50 Joint Operating Procedure, Eastern Range, 45th
Space Wing and NASA

FL Statute, Sec. 821.18 Trespass

FL Statute, Sec 861.01 Obstructing Highways

FL Statute, Sec 877.03 Breach of Peace, Obstructing Justice

FPM 751-4 Federal Personnel Manual - Enforced Leave

K-RQ-0001.2 (as revised) Space Shuttle Program Contingency Action Plan
for KSC

JHB 2000 (as revised) Consolidated Comprehensive Emergency Management
Plan (CCEMP)

KHB 1710.2 (as revised) KSC Safety Practices Handbook

KHB 4000.1 (as revised) Supply Support System Manual

K-STSM-09.3.1 STS Operations Plan, Flight Crew Rescue

KVT-PL-00211 Shuttle Transportation System Salvage Plan

[PUBLICATION NUMBER]{.underline} [PUBLICATION NAME]{.underline}

IL-HDBK-419 Grounding, Bonding and Shielding

NSTISSAM TEMPEST/1-91 Compromising Emanation Laboratory Test
Requirements, Electromagnetic

NSTISSAM TEMPEST/1-95 Shielded Enclosures

NSTISSAM TEMPEST/2-95 Red/Black Installation Guide

NPG 1600.6 (as revised) Communications Security Procedures and
Guidelines

NPG 1620.1 (as revised) Security Procedures and Guidelines

NPD 1020.2 (as revised) Displaying the United States Flag at Half-staff

NSTS 07700, Vol. VIII NSTS Operations

PVT-PL-0014 KSC Off-Site Operations Plan

PVT-PL-0015 Convoy Operations Plan

SCG-17 NASA TSCM Security Classification Guide

#### CHAPTER 101

**INTRODUCTION**

> 101.1 [PURPOSE]{.underline}
>
> a\. It is the purpose of this handbook to ensure that security
> policies, regulations, and guidance for security matters on NASA,
> Kennedy Space Center (KSC) are fully addressed.
>
> b\. This handbook prescribes the minimum standards, procedures,
> specifications, and guidelines to be followed at KSC to ensure
> uniformity and effectiveness.
>
> 101.2 [APPLICABILITY AND SCOPE]{.underline}
>
> a\. This handbook is applicable to all personnel, facilities,
> property, and classified material at KSC, regardless of custody.
>
> b\. The information detailed in this handbook will also provide the
> level of detail necessary to apply the security standards as
> identified to support the Resource Protection Program for KSC.
>
> c\. This handbook applies to all KSC organizational elements and to
> their associated contractors to the extent specified in their
> respective contracts. It also applies to other Government agencies,
> visitors to KSC, and sites under KSC\'s operational jurisdiction.
>
> d\. Modifications to existing facilities and systems, required for
> full compliance with NASA Resource Protection requirements, will be
> made as funds are available.

**CHAPTER 102**

**RESPONSIBILITY FOR SAFEGUARDING**

102.1 [GENERAL]{.underline}

> Directors of field organizations are levied the responsibility for
> ensuring proper safeguarding of facilities, property, information,
> and/or material under their jurisdiction to include component
> activities geographically located apart from the parent installation.

\* 102.2 [KENNEDY SPACE CENTER INSTALLATION SECURITY
OFFICER]{.underline}

> The Director of Spaceport Services appoints the Installation Security
> Officer (ISO) of KSC who is responsible for:
>
> a\. Ensuring that Protective Services Branch personnel are immediately
> and fully responsive to any request for assistance received from an
> individual relating to security, as set forth in this handbook.
>
> b\. Establishing and maintaining the standards and implementing the
> procedures, specifications, and guidelines outlined in this handbook.
>
> c\. Personally approving the modification or substitution of any
> provision set forth in this handbook after a specific determination
> that such modification or substitution provides protection for
> classified material or installation property at least equal to that
> prescribed within.
>
> d\. Promptly and fully determining the circumstances of any loss or
> subjection to possible compromise of classified information or
> material at the installation and taking such action as may be
> necessary to formally notify the originating office or agency.
>
> e\. Establishing more rigid standards, procedures, specifications, or
> guidelines than prescribed in this handbook whenever conditions or
> circumstances arise which indicate that increased security needs are
> necessary in the interest of National Security.
>
> f\. Ensuring that points of contact within the Protective Services
> Branch for each chapter of this handbook are identified.

102.3 [NASA KSC EMPLOYEES]{.underline}

> a\. NASA and contractor supervisors, at all levels, are responsible
> for ensuring that they and the personnel under their jurisdiction, to
> whom classified material is entrusted, are fully knowledgeable of and
> comply with the provisions set forth in this handbook and installation
> security regulations where applicable.
>
> b\. All NASA employees generating, having possession of, or otherwise
> handling classified information or material are responsible for:
>
> \(1\) Familiarizing themselves with and complying with the
> requirements of this handbook.
>
> \(2\) Verifying that a prospective recipient of classified information
> or material has both:
>
> \(a\) A security clearance equal to the degree of classification
> involved.
>
> \(b\) An official \"need-to-know\" for the information or material
> involved.
>
> \(3\) Immediately reporting to NASA Security, any loss or suspected
> compromise of classified information or material.
>
> \(4\) Bringing to the attention of their supervisor any known or
> suspected practice or condition which does not constitute compliance
> with this handbook.
>
> c\. NASA supervisors at all levels are responsible for ensuring that
> they, and the personnel under their jurisdiction, who occupy KSC
> facilities, are knowledgeable of the security requirements for the
> protection and safeguarding of those facilities and will bring to the
> attention of NASA Security, any condition or practice not commensurate
> with established security procedures or requirements.

102.4 [INCORPORATION INTO CONTRACTS]{.underline}

> The Director, Procurement Office, will incorporate this handbook into
> all contracts consistent with its applicability and scope.

102.5 [HEADS OF PRIMARY ORGANIZATIONS]{.underline}

> Heads of primary organizations will ensure that personnel under their
> control adhere to the requirements and concepts of this handbook.

**CHAPTER 103**

**EXECUTIVE SUMMARY**

103.1 [GENERAL]{.underline}

> a\. Chapter 101, Introduction, explains the purpose of the KSC
> Security Handbook and provides the applicability and scope for its
> use.
>
> b\. Chapter 102, Responsibility for Safeguarding, provides the levels
> of responsibility for all employees performing duties on KSC or within
> its jurisdictional boundaries.
>
> c\. Chapter 103, Executive Summary, provides a summary of information
> contained within the chapters of this KSC Security Handbook.
>
> d\. Chapter 104, Security Inspections and Audits, authorizes the
> conduct of periodic inspections and audits to ensure KSC\'s compliance
> with Executive, Federal, State, local, and NASA orders, regulations,
> and directives.

103.2 [INFORMATION SECURITY]{.underline}

> a\. Chapter 201, Security Awareness and Training, identifies the
> minimum security awareness and training requirements for KSC and the
> responsibilities for providing specialized briefings, authorizes a
> security awareness library, and directs that training documentation be
> maintained.
>
> b\. Chapter 202, Classifying and Marking, prescribes the requirements
> for classifying, declassifying, downgrading, and marking material
> which is protected in the interest of national security. It covers
> KSC\'s implementation of NASA and DoD requirements for identifying and
> marking national security information.
>
> c\. Chapter 203, Safeguarding Classified Material, consists of
> instructions and procedures pertaining to access, storage,
> accountability, transmission, reproduction, and destruction of
> classified material.
>
> d\. Chapter 204, Classified Information Incident Reporting, covers all
> actual or suspected incidents which breach security policy,
> regulations, and law pertaining to the control and/or access to
> classified material/information.
>
> e\. Chapter 205, Foreign Contacts, Requests for Information and
> Foreign Travel, establishes instructions and reporting criteria for
> contacts with foreign nationals and unauthorized requests for
> information. It also provides security briefing criteria for official
> and personal foreign travel to designated countries and areas.

103.3 [TECHNICAL SECURITY]{.underline}

> a\. Chapter 301, Technical Security Safeguard Systems, establishes
> requirements and procedures for requesting and specifying technical
> security safeguards, provides an explanation of some system
> capabilities, the use and need for various systems, and establishes
> standards for design and development of systems.
>
> b\. Chapter 302, Communications Security (COMSEC), establishes
> responsibilities and provides guidance for KSC\'s COMSEC program to
> include identification of requirements for design, equipment requests,
> inspections, and evaluations of secure communications equipment.
>
> c\. Chapter 303, TEMPEST\--Control of Compromising Emanations,
> explains the emanations problem in general terms, establishes KSC
> TEMPEST requirements and associated procedures, and outlines the
> function of the TEMPEST coordinator.
>
> d\. Chapter 304, Technical Surveillance Countermeasures (TSCM),
> establishes program requirements, associated procedures, and guidance
> for proper handling of technical surveillance devices. Additionally,
> it provides the guidance and requirements for TSCM surveys.

103.4 [PHYSICAL SECURITY]{.underline}

> a\. Chapter 401, Law Enforcement, describes KSC law enforcement
> functions, relationships, duties, and responsibilities, and the
> jurisdictions in effect. It also identifies jurisdiction of state and
> local agencies. Points of contact and emergency telephone numbers are
> included in this chapter.
>
> b\. Chapter 402, Protective Services, provides the policies and
> requirements for management, operations, training, and equipping
> KSC\'s protective forces.
>
> c\. Chapter 403, Security Incident Management, provides management
> instruction for all actual and/or suspected/probable crisis incidents
> that may occur requiring emergency planning, control, and/or
> resolution. Incidents may result from natural disasters, industrial
> accidents, or malicious or criminal acts.
>
> d\. Chapter 404, Badges and Passes, establishes the procedures and
> details the responsibilities for issuing and controlling
> identification badges, temporary passes, and special badges in use at
> the Kennedy Space Center.
>
> e\. Chapter 405, Personnel Control and Area Permits, establishes
> responsibilities and provides guidelines for issuing and controlling
> KSC Area Permits (KSCAP), Personnel Access Control and Accountability
> System (PACAS) cards, and Temporary Area Authorizations (TAA\'s) used
> to control access to operational flight hardware and restricted areas
> at KSC and NASA facilities at Cape Canaveral Air Force Station,
> Florida.
>
> f\. Chapter 406, Foreign Visitors, provides procedures for handling
> visitors coming under Foreign National or Foreign Representative
> category requesting access to KSC.
>
> g\. Chapter 407, Security Measures, identifies appropriate levels of
> protection given to assets based upon their value, from unauthorized
> access, damage, destruction, compromise, or theft, by the use of
> preventative and active security measures and procedures.
>
> h\. Chapter 408, Protective Barriers and Openings, establishes KSC\'s
> minimum criteria for security barriers and openings, with the
> exceptions of specific criteria for facilities, hardware, and
> operations identified in the NASA Resource Protection Program for KSC.
>
> i\. Chapter 409, Protective Lighting, provides the detail necessary to
> understand protective lighting principles. It discusses several types
> of protective lighting concepts and their effectiveness.
>
> j\. Chapter 410, Port and Harbor Security, establishes minimum
> security protective measures, but does not preclude unique or specific
> planning for individual sensitive activities, for all assets on
> terminals and waterways of KSC or areas under its jurisdiction.
>
> k\. Chapter 411, Traffic and Parking Control, provides the provisions
> and procedures for the supervision of motor vehicle traffic and the
> reserved parking program at KSC. It provides moving and nonmoving
> traffic regulations and the assessment of points for violations.
>
> l\. Chapter 412, Violations of Law Incident Reporting, provides the
> reporting responsibilities and requirements when a violation of law is
> suspected or has occurred. It identifies reportable types of behavior
> of cleared personnel. Other types of reportable incidents are also
> identified.
>
> m\. Chapter 413, Transportation and Material Security, specifies
> minimum safeguards and security measures to be taken to protect NASA
> and contractor assets during storage and movement. It does not limit
> users from instituting more stringent controls.
>
> n\. Chapter 414, KSC Registered Key Control/Locksmith Services,
> identifies the organizational responsibilities for controlling keys
> and locks under the control of the KSC Key Accountability System
> (KKAS). It describes the services of the J-BOSC Locksmith Office and
> their interface with security representatives requiring locksmith
> services.
>
> o\. Chapter 415, Control of Weapons, establishes control over the
> introduction and possession of weapons on KSC. It also prescribes the
> qualifications necessary before any individual is authorized to
> possess/use a weapon (firearm) on KSC or areas under KSC jurisdiction.
>
> p\. Chapter 416, KSC Flag Policy, provides the guidance necessary to
> implement and maintain a consistent policy governing the flying of the
> United States flag on the KSC.

**\* CHAPTER 104**

**SECURITY INSPECTIONS AND AUDITS**

104.1 [PURPOSE]{.underline}

> This chapter provides for the establishment and conduct of a security
> inspection and audit program to ensure KSC\'s compliance with this
> handbook, Executive Order, Federal regulations, NASA Security
> guidance, and laws applicable to KSC and areas under its
> jurisdictional control.

104.2 [RESPONSIBILITIES]{.underline}

> a\. The Chief, Protective Services Branch, is responsible for:
>
> \(1\) Security inspections and audits of KSC organizations for their
> adherence to the security requirements with which they are lawfully
> obligated to comply.
>
> \(2\) Reporting the results of security inspections and audits to the
> Director of Spaceport Services, the organizations audited, and if
> appropriate, to other Government agencies.
>
> b\. Heads of primary organizations are responsible for:
>
> \(1\) Complying with the provisions of this chapter.
>
> \(2\) At the request of the Chief, Protective Services Branch,
> providing points of contact within their organization to accommodate
> audit teams or inspectors.

104.3 [GENERAL PROVISIONS]{.underline}

> a\. Scheduled and unscheduled audits may be conducted by NASA Security
> personnel, or their designees, to assess the effectiveness of KSC\'s
> adherence to security regulations, directives and policy.
>
> b\. Inspections and audits will be performed to provide a method of
> informing organizations of problems, or potential problems, in their
> security program.
>
> c\. Results of inspections and audits will be documented and provided
> to top management. Follow-up reviews may be performed to ensure
> corrections have been implemented.
>
> d\. Security Inspection and Audit Teams will:
>
> \(1\) Coordinate with the organization to be inspected/audited to
> ensure that the scheduled inspections/audits are conducted on a
> noninterference basis.
>
> \(2\) Provide, in advance, a written \"Notification of Inspection\" to
> the organization being audited and request they complete the attached
> audit information survey.
>
> e\. Each organization will:
>
> \(1\) Provide an organizational point of contact for scheduled or
> unscheduled inspections or audits.
>
> \(2\) Complete the pre-inspection/audit information survey and return
> it to NASA Security at least 5 working days prior to the scheduled
> inspection.

104.4 [AUDITS]{.underline}

> a\. Audits will focus on the information security aspects of KSC
> activities and will be designed to effectively assess the proper
> application of security measures concerning the marking, handling,
> storage, transmission, and destruction of classified material.
>
> b\. Periodic information security audits will consist of, but not
> necessarily be limited to, the following:
>
> \(1\) Classified account inventory
>
> \(2\) Storage containers/combination change
>
> \(3\) Classified account custodian training
>
> \(4\) Administrative procedures
>
> \(5\) General security training attendance
>
> c\. In conjunction with the periodic information security audit, an
> inventory of Guest Badges will be conducted if the organization being
> inspected has guest badges issued to them.
>
> d\. Prior to the start of the audit, security teams/inspectors will
> provide an initial briefing to an organizational point of contact and
> an outbriefing upon completion.

104.5 [SECURITY INSPECTIONS]{.underline}

> a\. The Chief, Protective Services Branch, in fulfilling the role of
> the Installation Security Officer, has the overall responsibility to
> ensure a secure working environment for all KSC employees. To
> accomplish this, NASA Security may perform scheduled and unscheduled
> security inspections of KSC organizations to ensure compliance with
> all aspects of this handbook and other applicable security
> regulations.
>
> b\. In addition to security inspections conducted by representatives
> of NASA Security, the Joint-Base Operations Support Contractor, under
> the auspices of Chief, Protective Services Branch, Chapter 402.1 c
> (2), conducts periodic Resource Protection Surveys.
>
> c\. Security inspections will focus on, but not necessarily be limited
> to, the following:
>
> \(1\) Physical security.
>
> \(2\) Technical security.
>
> \(3\) Operations security.
>
> \(4\) Administrative security (exclusive of classified accounts).
>
> \(5\) Mission specific security when classified requirements are
> identified.
>
> \(6\) General security training attendance.

104.6 [VIOLATIONS]{.underline}

> If evidence that a suspected or actual violation of a security
> regulation or breech of law is found, the provisions of Chapter 204,
> \"Classified Information Incident Reporting,\" or Chapter 412,
> \"Violations of Law Incident Reporting,\" will be followed.

### CHAPTER 201

**SECURITY AWARENESS AND TRAINING**

201.1 [GENERAL]{.underline}

> Security awareness is achieved through a continuing process of
> information and motivation. At KSC this will be accomplished through a
> series of formal briefings arranged by NASA Security and through the
> respective efforts of each organization. In addition to security
> awareness, employees must be trained in the materials and methodology
> of security. Each organization will develop and undertake a program of
> security training.

201.2 [ORGANIZATIONAL REQUIREMENTS]{.underline}

> a\. Each organization will provide its employees with a program of
> security awareness and training commensurate with the employees\'
> involvement with sensitive or classified information, material, or
> operations. To a reasonable extent, security awareness and training
> will be tailored to the employees\' duties, functions, or situations.
> For example, employees who are not cleared for access to classified
> information need not be instructed in the procedures for classified
> document control. On the other hand, a group of employees who work in
> a closed area (access to which is considered equivalent to access to
> classified information) must be informed of their security
> responsibilities and instructed in security procedures for working in
> that area. The intent is to motivate employees and ensure that they
> have the requisite knowledge to fulfill their security
> responsibilities.
>
> b\. [Security Awareness]{.underline}. Each organization will implement
> security awareness measures to supplement the required briefings
> identified below. Since each organization is responsible for various
> and sundry protectable resources, it is not practical to define in
> detail the composition of organizational security awareness programs.
> Rather, each will implement a program commensurate with the security
> requirements under which it operates. Some awareness measures which
> organizations may consider include:
>
> \(1\) Periodic discussions by supervisors of the need for, and
> benefits of, security.
>
> \(2\) Displaying security reminders, such as posters, stickers, and
> notices.
>
> \(3\) Using audio-visual aids, such as security films, video tapes,
> and slide presentations.
>
> \(4\) Establishing a system for handling security questions or
> suggestions.
>
> c\. [Security Training]{.underline}. In conjunction with security
> awareness, each organization will train its employees in the security
> measures for which they are responsible. This security training will
> include:
>
> \(1\) Identification of the material or information which must be
> protected.
>
> \(2\) Explanation of the location and use of security equipment.
>
> \(3\) Instruction in routine security procedures.
>
> \(4\) Instruction in the procedures to be followed in the event
> security is breached.
>
> \(5\) Explanation of each employee\'s individual security
> responsibilities.
>
> \(6\) Any other training or briefing required by other chapters of
> this handbook, NASA regulation, Federal law, Executive Order, or
> regulation.
>
> d\. [Special Considerations.]{.underline} To be effective, security
> must be considered at every phase of an activity. Organizations
> involved in the design, procurement, and construction of facilities or
> systems must be aware of the protectable resources with which they are
> involved and of the security requirements attached to those resources.
> These organizations will provide sufficient security training to
> enable their employees to identify, protect, or plan for the
> protection of those resources. This may be accomplished by ensuring
> that employees have a thorough understanding of these portions of all
> classification guides for which they have a need-to-know.

201.3 [BRIEFINGS]{.underline}

> a\. [Required General Briefings]{.underline}. The following briefings
> have been approved by NASA Security, and are provided to KSC
> government employees on a scheduled basis by the Joint-Base Operations
> Support Contractor (J-BOSC). Attendance at briefings may be arranged
> by telephoning the J-BOSC Security Awareness Office, 861-5657.
> Contractor employees may attend on a space-available basis:
>
> \(1\) [Security Orientation]{.underline}. This briefing is required
> for all persons who work at KSC. Contractor organizations may use this
> briefing to give their employees a security awareness orientation.
>
> \(2\) [Safeguarding Classified Material.]{.underline} This briefing is
> required for all persons working at KSC who are cleared for access to
> classified material.
>
> \(3\) [Hostile Intelligence Threat.]{.underline} This briefing is
> required for all KSC employees, both NASA and contractor, who have a
> Secret or Top Secret clearance.
>
> \(4\) [Cleared Employee Rebriefing.]{.underline} This briefing is an
> abbreviated version of (2) and (3) above. It is required annually for
> all persons who have previously attended (2) and (3).
>
> \(5\) [Triennial Uncleared Employee Review]{.underline}. This briefing
> is an abbreviated review of (1), (2), and (3) above. It is required
> every third year after initial orientation for all personnel who do
> not hold a SECRET or TOP SECRET clearance.
>
> \(6\) [Classified Custodian Briefing]{.underline}. This briefing is
> required biennially for all personnel designated as Classified
> Custodians or Alternate Custodians.
>
> The J-BOSC maintains an index of all KSC individuals who have attended
> general security briefings. This index is updated and distributed
> monthly. Each organization is given a copy of that part of the index
> that applies to it. Accompanying the index is a listing of those
> persons who are due to attend the CLEARED EMPLOYEE REBRIEFING.
>
> b\. [Specialized Briefings.]{.underline}
>
> \(1\) NASA Security will arrange for briefings on:
>
> \(a\) Cryptographic equipment maintenance.
>
> \(b\) Communications Security (COMSEC).
>
> \(2\) NASA Security will arrange for briefings on TEMPEST design
> considerations.
>
> c\. [Program-Specific Security Briefings]{.underline}.
>
> \(1\) Launch Site Support Managers (LSSM\'s), when necessary, will
> arrange for briefings dealing with the special security or
> classification requirements associated with DoD payloads. Individuals
> will be briefed only on that information for which they have a
> need-to-know as determined by the LSSM\'s. LSSM\'s will ensure that
> NASA Security is provided a list of the attendees and an
> identification of the information they were given. (NOTE: This
> information is sensitive and in many cases may be classified.)
>
> \(2\) Other program-specific briefings (e.g., STARLAB, Space Station)
> will be arranged by the respective Office of Primary Responsibility.

201.4 [SECURITY AWARENESS LIBRARY]{.underline}

> The J-BOSC maintains a library of security awareness material,
> primarily audio-visual. Items from the library are available for loan
> to organizations to which this chapter applies. A listing of the
> library\'s contents and the procedures and terms for loan may be
> obtained from the J-BOSC Security Awareness Office, mail stop SGS-323,
> or by telephoning 861-5657.

201.5 [REQUIRED DOCUMENTATION]{.underline}

> To provide a means of auditing for compliance with the requirements of
> this chapter, organizations will document their security awareness and
> training efforts pursuant to paragraph 201.2 above. At a minimum, this
> documentation should include:
>
> a\. A description of the security awareness and training and a listing
> of the employees to which it is given.
>
> b\. An explanation of how that course of awareness and training is
> determined and at what level(s) it is given. (It is expected that
> security awareness and training will not be offered one-on-one, but
> will be provided to groups of employees who share common or similar
> jobs, functions, or situations).

**CHAPTER 202**

**CLASSIFYING AND MARKING**

202.1 [CLASSIFIED INFORMATION]{.underline}

> Information (and material) which is protectable in the interests of
> the national security is assigned to one of three classifications,
> from highest to lowest: TOP SECRET, SECRET, and CONFIDENTIAL. The
> classifications reflect the degree of adverse impact that unauthorized
> disclosure of the information could have on the national security.
>
> Only certain persons within the Federal Government, referred to as
> original classification authorities or original classifiers, are
> authorized to classify information. It is not practical, and often not
> possible, for them to review all information which is potentially
> protectable in the interest of the national security. Instead, they
> describe in Security Classification Guides (SCG\'s) the types of
> information which must be protected. These SCG's not only identify the
> kinds of information that are classified, but also indicate the level
> of classification and how long the classification will remain valid.
> Most importantly, these guides serve as the authority for cleared
> persons to classify the information described in the SCG\'s.
>
> a\. [Original Classification Authority]{.underline}. Original
> classification authority has been retained at NASA Headquarters. Any
> questions concerning classification of information or material should
> be directed to NASA Security.
>
> b\. [Derivative Classification Authority]{.underline}. There are two
> sources of derivative classification authority. They are security
> classification guides and previously classified information.
> Derivative classification authority may be exercised by any person who
> is cleared for access to classified information.

202.2 [CLASSIFYING INFORMATION]{.underline}

> The originator of material determines its classification, the
> authority for the classification, downgrading and declassifying
> instructions, and warning notices.
>
> a\. [Derivative Classification From a Classified Source.]{.underline}
> Classified sources are classified documents or other classified
> material. They can be expected to bear the following information:
>
> \(1\) Classified sources are marked with their classification.
>
> \(2\) The authority for that classification is contained on a
> \"classified by\" line on the front of the document. The \"classified
> by\" line usually will show one of the following:
>
> \(a\) The title of an original classification authority.
>
> \(b\) The title of a security classification guide.
>
> \(c\) The title of another classified document.
>
> \(d\) "Multiple sources," if the authority is from more than one
> source.
>
> \(3\) Below the authority will be listed any instructions for
> downgrading or declassifying. To the greatest extent possible, these
> instructions show the action that will be taken upon a specific date
> or event. If a specific date or event cannot be determined when the
> source is generated, then the instructions will show \"Originating
> Agency Determination Required\" or \"OADR.\"
>
> \(4\) Warning notices may be included. The most common warning notices
> concern:
>
> \(a\) Restricted Data and Formerly Restricted Data as defined in the
> Atomic Energy Act of 1954.
>
> \(b\) Intelligence sources and methods.
>
> \(c\) COMSEC material.
>
> \(d\) The dissemination and reproduction of the classified material.
>
> \(5\) The office which originated the classified source.
>
> \(6\) Sometimes portions of classified sources are marked to indicate
> specifically which information is classified and which is
> unclassified. (See paragraph 202.6.)
>
> If there is doubt concerning the classification of the extract,
> protect it at the same level as the material from which it was
> extracted and seek a classification determination from NASA Security.
>
> b\. [Derivative Classification From a Security Classification
> Guide.]{.underline} When a cleared person authors or compiles
> information (or creates material; such as, photographs, maps, charts,
> and hardware), he/she will compare it with all applicable and
> available SCG\'s to determine if it contains classified information.
> Several SCG\'s apply at KSC and, if classified, will be provided only
> to those cleared persons who have a need-to-know. The Space
> Transportation System Security Classification Guide (STS SCG) is the
> major source of derivative classification authority at KSC. It is
> unclassified and is available to all cleared persons.
>
> Security classification guides provide the level of classification,
> the classification authority, downgrading and declassifying
> instructions, and sometimes warning notices. This information will be
> shown on any material which is derivatively classified from an SCG.
> The material will be marked according to the provisions of this
> chapter.
>
> c\. [Derivative Classification From Multiple Sources]{.underline}.
> When the authority for classifying information comes from more than
> one source document, SCG, or combination thereof, it is referred to as
> \"Multiple Sources.\" Offices which classify new material in this
> manner are responsible for keeping a record which identifies the
> multiple sources. The level of classification will be the highest
> required by any of the sources. Any downgrading and declassifying
> instructions and warning notices will be the most restrictive of the
> sources. The material will be marked according to the provisions of
> this chapter.
>
> d\. [Original Classification]{.underline}. When information or
> material is not derivatively classifiable, but appears to require
> protection in the interests of the national security, it will be
> protected as if it were classified SECRET, and an original
> classification determination will be requested from the Lead, NASA
> Security.
>
> e\. [Documents, Pages, and Portions.]{.underline} Documents, pages,
> and portions are classified at the highest level of any of the
> information contained in their parts.
>
> \(1\) Documents are classified at the highest level of any of their
> pages. For example, if a document consists of three pages which are
> classified CONFIDENTIAL, UNCLASSIFIED, and SECRET, then the entire
> document is classified SECRET.
>
> \(2\) Pages are classified at the highest level of any of their
> portions. For example, if a page consists of an UNCLASSIFIED heading,
> a TOP SECRET table, and a CONFIDENTIAL paragraph, then the entire page
> is classified TOP SECRET.
>
> \(3\) A portion is any part that can stand on its own. The most common
> portions are titles, paragraphs, tables and illustrations, and
> captions. Portions are classified at the highest level of any the
> information contained therein.
>
> f\. [Compilations]{.underline}. Sometimes material is classified based
> on association or compilation of otherwise unclassified pieces of
> information. Similarly, elements of information which are classified
> CONFIDENTIAL or SECRET may require reclassification when they are
> associated or compiled. The requirements which are mentioned above for
> original and derivative classification apply to compilations. (Refer
> to paragraph 202.7.)

202.3 [MARKING CLASSIFIED MATERIAL]{.underline}

> A marking is a physical designation or notation which is placed on
> classified documents or affixed to other classified material or the
> material\'s container. Marking serves as a warning that the material
> is classified and must be protected. It shows the level of
> classification and, thereby, the degree of protection that is
> required. Marking also facilitates downgrading and declassifying
> whenever these actions are appropriate.

202.4 [DOCUMENT MARKINGS]{.underline}

> a\. The classification of a document will be conspicuously marked at
> the top and bottom of its front and back. The front of a document is
> its cover or, if none, then the title page or first page.
>
> b\. Document fronts will bear:
>
> \(1\) The document\'s title and the date that it was prepared. If
> possible, the title will be unclassified. The classification of the
> title will be shown in parenthesis following it; e.g., (U), (C), or
> (S). This parenthetical notation becomes a part of the title and will
> be included whenever the title is copied for record or reference
> purposes. If the title is classified (then an unclassified designator
> will also be shown).
>
> \(2\) A \"Classified by\" line.
>
> \(a\) If the document is originally classified, then it will show the
> title of the original classifier.
>
> \(b\) If the document is derivatively classified, it will show the
> title of the SCG or source material or \"multiple sources.\" If an SCG
> is cited, then its date will also be shown.
>
> \(3\) A \"Declassify on\" line. If possible, this line will show a
> specific date or event; for example, \"Declassify on July 1, 1984\" or
> \"Declassify on completion of A-B-C Mission.\" Otherwise, this line
> will show \"Declassify on: Originating Agency Determination Required\"
> or \"Declassify on: OADR.\"
>
> \(4\) The office which originated the document. For documents which
> are generated under the KSC system, office of origin is:
>
> \(a\) NASA KSC for all NASA KSC organizational elements.
>
> \(b\) The company name for all contractor organizations.
>
> \(5\) Any applicable warning notices. (See paragraph 202.15.)

202.5 [PAGE MARKING]{.underline}

> Each page of a classified document will be conspicuously marked at its
> top and bottom with its classification (Refer to paragraph 202.2.).
> Pages that are unclassified will be so marked. To be conspicuous, the
> markings must be plainly visible and noticeably larger than the
> printed letters of the text.
>
> For electronically transmitted messages and other documents produced
> by automatic data processing (not word processing) equipment, these
> markings may be in letters the same size as the text, provided they
> are applied by the printing equipment and highlighted by spacings and
> asterisks; for example:
>
> **\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\***
>
> **\* S E C R E T \* or \*\*\*\* S E C R E T \*\*\*\***
>
> **\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\***

202.6 [PORTION MARKING]{.underline}

> a\. Each paragraph or similar portion of a classified document will be
> marked to show the highest classification of the information which it
> contains (refer to paragraph 202.2.e.). Portions that are unclassified
> will be so marked. The marking will be placed immediately after the
> portion\'s letter or number or, if none, immediately before the
> beginning of the portion. The following parenthetical symbols are used
> for marking portions: (TS)-TOP SECRET, (S)-SECRET, (C)-CONFIDENTIAL,
> and (U)-UNCLASSIFIED.
>
> When appropriate, the symbols \"RD\" for Restricted Data and \"FRD\"
> for Formerly Restricted Data will be added; for example, \"(S-RD)\" or
> \"(C-FRD).\" (Refer to paragraph 202.15.)
>
> b\. Illustrations, photographs, figures, graphs, drawings, charts,
> etc., which are contained in classified documents will be clearly
> marked to show their classification. Such markings will not be
> parenthetically abbreviated and will be prominently placed within or
> contiguous to the illustration, etc. Captions will be marked as a
> separate portion as described in paragraph a above.
>
> c\. When a portion contains elements of information of more than one
> classification, and segregation into separate portions would destroy
> continuity or context, the highest classification of any element will
> be applied to that portion.
>
> d\. All titles, including those of chapters, sections, and the like,
> will be parenthetically marked; i.e., (TS), (S), (C), or (U), to
> indicate their classification. The marking will be placed immediately
> following and to the right of the title. If appropriate, other symbols
> such as \"RD\" or \"FRD\" will be added.

202.7 [COMPILATIONS]{.underline}

> When classification is required to protect a compilation of
> information, the classification will be conspicuously marked on the
> front and back of the document and at the top and bottom of each page.
> An explanation of the basis for the assigned classification will be
> included on the front of the document or in its text.

202.8 [FILE, FOLDER, OR GROUP OF DOCUMENTS]{.underline}

> When a file, folder, or group of classified documents is removed from
> secure storage, it will be marked conspicuously with the highest
> classification of any classified document it contains.

202.9 [TRANSMITTAL DOCUMENTS]{.underline}

> A transmittal document will be conspicuously marked on its face with
> the highest classification of the information transmitted by it. It
> will also bear a legend showing its classification, if any, when
> standing alone. For example, an unclassified document that transmits a
> classified document as an attachment will bear a notation
> substantially as follows: \"Unclassified When Separated From
> Classified Enclosures.\" A transmittal document that is unclassified
> when separated from its classified enclosure need only be marked on
> the first page at top and bottom. If a transmittal document is not in
> itself classified, then its portions do not need to be marked.

202.10 [WHOLLY UNCLASSIFIED MATERIAL]{.underline}

> Normally, unclassified material will not be marked or stamped
> \"UNCLASSIFIED\" unless it is essential to convey that it has been
> reviewed for classification and has been determined to be
> unclassified.

202.11 [NOTES, DRAFTS, WORKING PAPERS]{.underline}

> Whenever classified material is initially written, typed, drawn,
> transcribed (including shorthand), or otherwise created, but is not
> finished, it will be marked with the highest classification of the
> information which it contains and will bear the date it was created.
> The material will be accounted for in accordance with Chapter 203,
> paragraph 203.11e.

202.12 [LECTRONICALLY TRANSMITTED MESSAGES]{.underline}

> a\. The first item of information in the text of a classified,
> electronically transmitted message will be its overall classification.
> Paper copies of classified, electronically transmitted messages will
> be marked at the top and bottom with their classification. Portions
> will be marked as prescribed in paragraph 202.6. When messages are
> printed by an automated system, markings may be applied by the system,
> provided they are conspicuous and clearly distinguishable from the
> printed text. In addition, copies not electronically transmitted (such
> as, mail and courier copies) will be marked as required for paper
> copies of documents.
>
> b\. A \"Classified By\" line is not required on messages. Instead the
> message\'s originator is considered to be its classifier and is
> responsible for maintaining adequate records to show the classifying
> authority.
>
> c\. The last line of text of a classified message will provide
> instructions for downgrading and/or declassifying unless the message
> contains Restricted or Formerly Restricted Data.

202.13 [SPECIAL CATEGORIES OF MATERIAL]{.underline}

> a\. [Hardware]{.underline}. As a minimum, all classified hardware will
> be conspicuously marked with its classification, the date of
> classification, downgrading and/or declassifying instructions, and the
> name and address of the preparing organization. If the material does
> not lend itself to marking, this information will be attached by tag,
> sticker, or similar device. If the size or irregular features of
> hardware preclude marking or tagging, then it will be kept in a
> container which is tagged or marked.
>
> b\. [Charts, Maps, and Drawings.]{.underline} Classified charts, maps,
> and drawings will be marked with their classification. Whenever
> practical, legends and titles will be selected which themselves are
> not classified. Classified legend, title, or scale blocks will be
> marked in a manner that differentiates between the overall
> classification of the document and the classification of the legend or
> title itself. The highest classification of the information it
> contains will be marked at the top and bottom of each document. If
> folding or rolling charts, maps, or drawings would cover the
> classification markings, additional markings will be applied that are
> clearly visible when the document is folded or rolled. Other
> applicable markings will be included in or near the legend, title, or
> scale blocks.
>
> c\. [Photographs]{.underline}. Negatives and positives will be marked
> with their classification and any other applicable markings. Roll
> negatives or positives may be marked at the beginning and end of each
> strip. Negatives and positives will be kept in containers bearing
> conspicuous classification markings. All prints and reproductions will
> be conspicuously marked on the face side of the print, if possible.
> When markings cannot be applied to the face side, they may be stamped
> on the reverse side or affixed by tape, staple, or other comparable
> means. When self-processing film is used to photograph or reproduce
> classified information, all parts of the last exposure will be removed
> from the camera and destroyed as classified waste, or the camera will
> be protected as classified material.
>
> d\. [Transparencies and Slides]{.underline}. Classification will be
> clearly marked on the image of each transparency or slide, if
> possible, or on its border, holder, or frame. Other applicable
> markings will be shown on the border, holder, or frame.
>
> e\. [Motion Picture Films]{.underline}. Classified motion picture
> films and video tapes will be marked at the beginning and end of each
> reel by titles bearing the appropriate classification and other
> applicable markings. Such markings must be visible when projected or
> played. Reels will be kept in containers bearing conspicuous
> classification and other applicable markings. Audio tracks associated
> with films and video tapes will contain statements of classification
> as outlined in paragraph f. below.
>
> f\. [Recordings]{.underline}. Each classified sound, magnetic, or
> electronic recording will contain at its beginning and end a clearly
> audible statement of its level of classification. Recordings will be
> kept in containers or on reels that bear conspicuous classification
> and other markings.
>
> g\. [Microforms]{.underline}. Microforms are copies usually produced
> in sizes too small to be read by the unaided eye. Accordingly,
> appropriate markings will be conspicuously placed on the microform
> medium, or its container or jacket, so they are readable by the
> unaided eye. The images on the microform will be marked according to
> their content so that when they are enlarged and displayed or printed,
> the markings will be conspicuous and readable.
>
> h\. [Miscellaneous Material]{.underline}. Such as typewriter ribbons,
> printer ribbons, preliminary notes, rejects and similar items sued to
> process or formulate classified information should be treated as
> classified material. When no longer needed will be destroyed as
> classified waste. Carbons, and similar items for a specific purpose,
> there is no need to mark, stamp, or otherwise indicate that the
> information is classified. See Paragraph 203.11 for disposition
> instructions.

202.14 [ECLASSIFYING AND DOWNGRADING]{.underline}

> When a document qualifies for downgrading or declassifying, the
> individual having custody of it is responsible for changing its
> markings.
>
> Declassifying, either automatically or by individual review and
> determination, is not automatically an approval for public disclosure.
> Accordingly, KSC personnel will process all requests for public
> disclosure of \"declassified\" information through NASA Security.

202.15 [WARNING NOTICES]{.underline}

> Warning notices will be prominently displayed on classified documents
> or materials, when applicable. In the case of documents, these warning
> notices will be conspicuously marked adjacent to the classification on
> the front. Transmittal documents, including those that are
> unclassified, will also bear any applicable warning notices. When it
> is not possible to mark warning notices on other materials, their
> applicability to the classified information will be included in the
> written notification of the material\'s classification.
>
> a\. [Restricted Data]{.underline}. Classified documents or material
> containing Restricted Data as defined in the Atomic Energy Act of
> 1954, as amended, will be marked as follows:
>
> **\"RESTRICTED DATA\"**
>
> \"This material contains Restricted Data as defined in the Atomic
> Energy Act of 1954. Unauthorized disclosure is subject to
> administrative and criminal sanctions.\"
>
> b\. [Formerly Restricted Data]{.underline}. Classified documents or
> material containing Formerly Restricted Data as defined in Section
> 142.d, Atomic Energy Act of 1954, as amended, but no Restricted Data,
> will be amended as follows:
>
> **\"FORMERLY RESTRICTED DATA\"**
>
> \"Unauthorized disclosure is subject to administrative and criminal
> sanctions. Handle as Restricted Data in foreign dissemination. Section
> 144.b, Atomic Energy Act, 1954.\"
>
> c\. [Intelligence Sources and Methods Involved]{.underline}. Documents
> that contain information relating to intelligence sources or methods
> will include the following marking:
>
> **\"WARNING NOTICE - Intelligence Sources or Methods Involved\"**
>
> d\. [COMSEC Material]{.underline}. COMSEC documents will bear the
> following notation:
>
> **\"COMSEC Material\--Access by Contractor Personnel Restricted to
> U.S. Citizens Holding Final Government Clearance.\"**
>
> e\. [Dissemination and Reproduction Notice]{.underline}. Classified
> information that the originator has determined to be subject to
> special dissemination or reproduction limitations, or both, will
> include, as applicable, a statement or statements as follows:
>
> **\"Reproduction requires approval of originator or higher Government
> authority.\"**
>
> \"**Further dissemination only as directed by (insert appropriate
> office or official) or higher Government authority.\"**

202.16 [EMARKING OLD MATERIAL]{.underline}

> a\. Documents and material classified under Executive Order (E.O.)
> 12065, \"National Security Information,\" June 28, 1978, that are
> marked for automatic downgrading or automatic declassification on a
> specific date or event will be downgraded and declassified pursuant to
> those markings. Information extracted from these documents or material
> for use in new documents or material will be marked for
> declassification using the guidelines for derivative classification.
>
> b\. Classified documents and material classified under E.O. 12065, or
> other predecessor E.O.\'s that are not marked for automatic
> downgrading or automatic declassification on a specific date or event
> will not be downgraded or declassified without authorization of the
> originator. Such documents or material need not be remarked.
> Information extracted from these documents or material for use in new
> documents or material will be marked for declassification upon the
> determination of the originator; that is, the \"Declassify On\" line
> will be completed with the notation \"Originating Agency\'s
> Determination Required\" or \"OADR.\"

202.17 [ARKING FOREIGN CLASSIFIED MATERIAL]{.underline}

> a\. Foreign government security classification designations generally
> parallel U.S. classification designations. If a foreign government
> document is received with the security classification designation
> marked in English, no other classification marking shall be applied.
>
> b\. If the foreign classification designation is not shown in English,
> the equivalent overall U.S. classification designation and the country
> of origin shall be conspicuously marked on the document.
>
> c\. Many foreign governments and international organizations use a
> fourth security designation identified as \"RESTRICTED\" to denote a
> requirement for security protection of a lesser degree than
> CONFIDENTIAL. Documents received that are marked with any of the
> classification designations listed in the last (fourth) column on the
> equivalency chart shall be marked \"RESTRICTED\" together with the
> country of origin.
>
> d\. When classified foreign government information is incorporated
> into a NASA/KSC or NASA contractor-Generated document, that document
> shall be identified in a manner to ensure that such information is not
> declassified prematurely or made accessible to nationals of a third
> country without consent of the originator. This requirement shall be
> met by marking the face of the document with the notation \"CONTAINS
> FOREIGN GOVERNMENT INFORMATION.\"
>
> e\. Portions of NASA/KSC or NASA contractor-generated documents
> containing classified foreign government information shall be marked
> to reflect the country of origin, as well as the appropriate
> classification (for example, \"U.K. RESTRICTED\" or \"U.K. - S\"),
> except where such markings would reveal that the information is
> foreign government information when that fact must be concealed, or if
> a confidential relationship not otherwise evident in the document is
> revealed.
>
> f\. Classified foreign government information to be included in any
> NASA/KSC or NASA contractor-generated document shall be reviewed by
> NASA Security before inclusion in the document.
>
> g\. All such documents containing foreign government information shall
> include on the \"Declassify on\" line the following notation:
> \"Originating Agency\'s Determination Required\" or \"OADR,\" unless
> the foreign entity has specified or agreed to a date or event for
> declassification.
>
> Note: Appendix XIV of DoD 5220.22-M, The National Industrial Security
> Program Operating Manual (NISPOM), contains the Equivalent Foreign and
> International Pact Organization Security Classifications.

**CHAPTER 203**

**SAFEGUARDING CLASSIFIED MATERIAL**

203.1 [GENERAL]{.underline}

> This chapter establishes the Kennedy Space Center\'s system for
> safeguarding classified material.

203.2 [ACCESS TO CLASSIFIED MATERIAL]{.underline}

> a\. Only those individuals who have been granted the appropriate
> security clearance and have a need-to-know will be given access to
> classified material.
>
> b\. A recipient\'s clearance must equal or exceed the material\'s
> classification. The custodian of the classified material must verify
> that the recipient is cleared at the proper level. The level of
> clearance of KSC Government and KSC contractor employees may be
> verified by calling the applicable NASA or contractor security office.
> During non-duty hours, the Visitor\'s Record Center (VRC), 867-7763,
> may verify clearances. Clearances of visitors to KSC may be verified
> at any time by calling the VRC.
>
> c\. The need-to-know principle states that a person\'s clearance for
> access to classified material does not automatically entitle the
> individual to that access. The individual must also have a need for
> access to the classified information or material sought in connection
> with the performance of official duties or contractual obligations.
> The final responsibility for determining whether an individual\'s
> official duties require possession of, or access to, any element or
> item of classified information rests upon the individual who has
> authorized possession, knowledge, or control of the information and
> not upon the prospective recipient.

203.3 [STORAGE]{.underline}

> Classified information must be under the personal control and
> observation of an authorized person, or stored in an approved
> container or storage area at all times. Approved containers and
> storage areas are defined as GSA-approved safe-type steel file
> cabinets equipped with a built-in, three-position, dial-type
> combination lock, or an approved vault or vault-type room that meets
> the standards as published by the General Services Administration, or
> other secure storage areas as approved by the Protective Services
> Branch.

203.4 [STORAGE PROVISIONS]{.underline}

> a\. Each organization will periodically review its classified holdings
> for the purposes of reducing them and maintaining them at an absolute
> minimum.
>
> b\. Classified material which is temporarily removed from the normal
> workplace (e.g., for conferences, studies, or meetings) must be under
> the continuous control of its authorized holder or properly stored at
> the temporary location.
>
> c\. Classified material may only be used and stored at places of
> official business on KSC/CCAFS. Classified material will not be
> removed from KSC to a place of residence or other off-Center location
> without the approval of NASA Security.
>
> d\. Classified waste will be properly stored in containers or
> facilities approved for storage of classified materials while awaiting
> destruction.

203.5 [STORAGE CONTAINERS]{.underline}

> a\. Containers which have been approved for storing classified
> material will not be used for storing items such as funds, weapons,
> controlled drugs, precious metals, or other valuable unclassified
> property. [NASA Security may waive this restriction in an emergency,
> provided action is initiated promptly to provide separate storage for
> the unclassified items.]{.underline}
>
> b\. Classified material storage containers will not be relocated
> without prior approval from the applicable NASA or contractor security
> office. The applicable security office will then notify, in writing,
> NASA Security. A custodian or appropriately cleared designated
> representative will accompany a container while it is being moved if
> it contains classified material. If the classified material is removed
> from the container before it is moved, and the container is not
> accompanied, the combination will be changed before the container is
> again used for storing classified material.
>
> c\. Before a container is placed in service as a classified container,
> a written request for authorization must be sent to the applicable
> NASA or contractor security office. The applicable security office
> will then notify, in writing, NASA Security.
>
> d\. A reasonable effort must be made to use equipment already
> available through the consolidation or disposal of existing records
> and other stored materials before requesting additional storage
> containers.
>
> e\. Organizational elements needing security containers must submit
> requests through their contractor security office or, for NASA
> accounts, directly to NASA Security.
>
> f\. Requests for purchase of additional security containers will be
> submitted to NASA Security.
>
> g\. Requests for security containers will include the classification
> and type of classified material to be stored (e.g., documents,
> engineering drawings, magnetic tapes, etc.), the anticipated volume of
> material, and the proposed location of the containers.
>
> h\. Requests to NASA Security will be by:
>
> \(1\) NASA KSC managers at the branch level or higher for their
> accounts.
>
> \(2\) The heads of other NASA organizations or other Government
> agencies at KSC for their accounts. This includes organizations which
> do not otherwise participate in the KSC Classified Material Control
> System (CMCS).
>
> \(3\) The security officer or, if none, the heads of contractor
> organizations at KSC for their accounts. This includes companies which
> do not otherwise participate in the KSC CMCS.
>
> i\. Security containers which are no longer being used for classified
> storage, and will not be needed during the foreseeable future, will be
> identified, in writing, to NASA Security.
>
> j\. Before a container with a built-in combination lock is taken out
> of service, the J-BOSC Locksmith Services Office will be requested to
> service the unit, set a factory combination, and affix a turn-in label
> to the container.

203.6 [COMBINATIONS]{.underline}

> a\. Combination Changes.
>
> \(1\) All combinations will be changed upon:
>
> \(a\) The initial receipt of the container or possession of the vault
> or area.
>
> \(b\) The relief, transfer, discharge, termination, hospitalization,
> leave of absence, suspension, or revocation of the clearance of any
> person who knows the combination.
>
> \(c\) The compromise or suspected compromise of the container or its
> combination (e.g., discovery that the container has been left unlocked
> and unattended).
>
> \(2\) The combinations to all vaults and all containers used by NASA
> KSC organizations will be changed by:
>
> \(a\) The J-BOSC Locksmith Services Office.
>
> \(b\) The container\'s custodian under the instruction of the J-BOSC's
> Locksmith Services Office.
>
> \(c\) Other personnel as authorized by NASA Security.
>
> \(3\) All other organizations will change their own combinations. A
> representative of the Locksmith Services Office may instruct the
> custodian or provide technical assistance, if requested through NASA
> Security.
>
> \(4\) To facilitate combination changes, custodians should apply for
> J-BOSC Locksmith Services Office support at least 10 working days
> prior to annual combination changes. KSC Form 20-36, \"Locksmith
> Services Request,\" will be used to schedule such support.
>
> b\. A Standard Form (SF) 700, Security Container Information, will be
> used to record the combination of each container. The SF-700 is in
> three parts and will be maintained as follows:
>
> \(1\) Part 1 will contain the names, addresses, and phone numbers of
> employees who are to be contacted if the safe, to which the form
> pertains, is found open and unattended. It will be attached to the
> inside of the locking drawer.
>
> \(2\) Part 2 will contain the same information as Part 1 and serves as
> the envelope. It will be marked with the highest classification of any
> material to be stored in the container.
>
> \(3\) Part 2A will contain the combination and will be marked with the
> highest classification of any material to be stored in the container.
>
> \(4\) Detach Part 2A and place in Part 2, seal the envelope and place
> the notation on the outside of Part 2, \"Declassify upon next
> combination change, destroy as classified waste.\"
>
> c\. The envelope, Part 2, must be stored in a container according to
> its classification, but not in the container to which the combination
> applies.
>
> d\. Written records of superseded combinations will be treated as
> classified waste.
>
> e\. NASA Security will maintain written records of lock and padlock
> combinations for:
>
> \(1\) Vaults on KSC.
>
> \(2\) Containers utilized by NASA KSC personnel.
>
> \(3\) Other organizations as requested.
>
> f\. Contractor security offices or heads of contractor organizations
> and other Government organizations will maintain records of lock and
> padlock combinations for containers used by their organizations.
>
> g\. Combinations will always be memorized and will never be written,
> in any form, except for those which are placed in sealed envelopes
> (Part 2, SF-700) for retention in an approved security container.

203.7 [OPENING, LOCKING, AND CHECKING STORAGE CONTAINERS]{.underline}

> a\. A Standard Form 702, Security Container Check Sheet, will be used
> to record the opening, locking, and checking of each container. SF-702
> is not required for containers that have been approved solely for the
> storage of unclassified material. KSC Form 20-18NS, No Classified
> Material Stored in This Container, will be affixed to containers being
> used for unclassified storage.
>
> b\. When a classified container is open, it must be under the control
> of a person whose name appears on the Standard Form 700 as being
> authorized to control the contents of that container.
>
> c\. To prevent the unauthorized removal or switching of padlocks, each
> combination padlock used for security storage containers or for a
> security area will be locked and placed in a drawer, or locked to the
> hasp, whenever a container or area is open. The custodian will
> maintain the serial number of the combination padlock to confirm
> switching has not occurred.
>
> d\. A classified container must be locked when unattended. To lock the
> container, all doors or drawers must be closed, and the combination
> dial must be turned at least four revolutions in the same direction.
> Each door or drawer will be checked to be sure that it is latched.
>
> e\. After a classified container is locked it should be checked. The
> check may be done by anyone, regardless of clearance level.
>
> f\. Reversible \"open-closed\" or \"open-locked\" signs will be used
> on each security container in which classified information is stored.
> Signs are available through normal supply channels. One acceptable
> sign, Optional Form 95, is available through the Forms Warehouse.
>
> g\. At the end of the work period, all desks, in and out baskets, and
> work areas will be checked to further ensure that no classified
> material has been left unsecured.

203.8 [ACCOUNTS]{.underline}

> a\. A classified material account is required for each organizational
> element which must retain classified material.
>
> b\. Each classified account must have appropriate storage capability
> for materials assigned to the account.
>
> c\. Requests for establishment of classified material accounts will be
> forwarded in writing to the Classified Material Control Center (CMCC).
> The following may request classified material accounts for their
> organizational elements:
>
> \(1\) NASA KSC managers at the branch level or higher.
>
> \(2\) The heads of other NASA organizations or other Federal agencies
> at KSC.
>
> \(3\) The security officers or, if none, the heads of contractor
> organizations at KSC.
>
> d\. [Closing an Account.]{.underline} When an account is no longer
> needed, it will be closed. The primary custodian will transfer the
> account\'s classified material to other accounts or to the CMCC for
> destruction.

203.9 [ACCOUNT CUSTODIANS]{.underline}

> a\. One individual will be appointed as primary custodian of each
> classified account and will be responsible for all containers assigned
> to the account and the classified material held by the account.
>
> b\. The primary custodian\'s duties include, but are not limited to:
>
> \(1\) Keeping a record of all accountable classified material in the
> account.
>
> \(2\) Receiving classified material into the account and transmitting
> classified material out of the account.
>
> \(3\) Reporting to the CMCC any accountable and nonaccountable
> classified material which is generated at KSC or received from outside
> the accountability system.
>
> \(4\) Hand receipting classified material to persons who are
> appropriately cleared and have a need-to-know.
>
> \(5\) Storing the classified material assigned to the account.
>
> \(6\) Ensuring that classified material under his/her control is
> properly marked in accordance with Chapter 202 of this handbook.
>
> \(7\) Transferring classified material to the CMCC for destruction
> when it is no longer needed.
>
> c\. At least one alternate custodian will be appointed for each
> account. The number of alternate custodians will be held to a minimum
> consistent with operational requirements.
>
> d\. The alternate custodian will assume duties of the primary
> custodian in his/her absence.
>
> e\. Each primary and alternate custodian must hold a security
> clearance equal to, or greater than, the holdings of the account.

203.10 [DESIGNATING CUSTODIANS]{.underline}

> a\. The primary and alternate custodians will be designated, in
> writing, to the CMCC. The designations shall include full names, mail
> codes, telephone numbers, and office locations so that clearances may
> be verified.
>
> b\. The following personnel are authorized to make such designations
> at KSC:
>
> \(1\) NASA KSC managers at the branch level or higher, for themselves
> and their subordinates.
>
> \(2\) The heads of the other NASA organizations or other Government
> agencies at KSC for themselves and their subordinates.
>
> \(3\) Supervisors of contractor activities at KSC may designate
> custodians for their functional areas. However, such designations must
> be approved by the contractor security office or by the head of the
> contractor organization.
>
> c\. Individuals with authority to designate custodians are required to
> submit to the CMCC, a written, updated list of all custodians assigned
> to each account:
>
> \(1\) Whenever a change in custodian occurs. (Notification should be
> given at least 1 week in advance of the change.)
>
> \(2\) Annually, from the date of the last notification, if no change
> in custodian has occurred during the previous year.
>
> d\. Individuals with authority to designate custodians are also
> responsible for ensuring that such designees are made available for
> training. Training will include, as a minimum, accountability
> procedures, safeguarding, storage, and methods of reporting security
> violations or incidents. Initial training and annual refresher
> training are required (SA-008).
>
> e\. Other individuals of the same organization may be authorized
> access to the contents of classified containers and have knowledge of
> the container combination without being assigned as a custodian. The
> custodian will maintain a list of all persons with access to the
> container/vault and place it next to the SF-700.

203.11 [ACCOUNTABILITY]{.underline}

> a\. To manage its classified holdings, KSC uses a system of classified
> material accounts reporting to a CMCC.
>
> b\. The CMCC maintains a record of all accountable classified
> material. Classified material sent to KSC is received by the CMCC.
> Classified material received directly by other KSC organizations
> within the KSC CMCS will be immediately reported to the CMCC.
> Similarly, all accountable classified material which is generated at
> KSC will be reported to the CMCC. As directed, and with limitations,
> the CMCC processes classified material and notifies intended recipient
> to arrange for transporting such material within KSC, and between KSC
> and CCAFS and PAFB. The CMCC also arranges the reproduction and
> distribution of classified documents, destroys classified material
> that is no longer needed, and provides instruction to account
> custodians.
>
> c\. Accountable classified material will be accounted for within the
> KSC Classified Material Control System by KSC Form 16-122, Classified
> Material Receipt.
>
> d\. The CMCC will maintain a record of all non-accountable classified
> material (except working papers) utilizing KSC Form 7-66NS,
> CONFIDENTIAL Material Log.
>
> e\. [Classified working papers]{.underline} are temporary in nature.
> Classified information created and/or accumulated for use in the
> preparation of finished permanent documents, such as Operations and
> Maintenance Instructions (OMI\'s), Operations Directives (OD\'s), etc.
> Working papers may not be reproduced or distributed without being
> entered into the KSC CMCC accountability system.
>
> f\. [Working papers]{.underline} will be:
>
> \(1\) Dated when created.
>
> \(2\) Marked with the highest classification of any information they
> contain.
>
> \(3\) Protected in accordance with the assigned classification.
>
> \(4\) Accounted for, controlled, and marked in the manner prescribed
> for a finished document of the same classification when:
>
> \(a\) Released by the originator to an individual or account not
> serviced by the KSC CMCC or transmitted electrically or through
> message channels within KSC.
>
> \(b\) Retained for no more than 90 days from date of origin.
>
> \(c\) Filed permanently.
>
> \(d\) Reproduced.
>
> g\. Classified waste includes material such as carbon paper,
> typewriter and printer ribbons, preliminary notes, working papers,
> printing plates, stencils, masters, stenographer\'s notes, worksheets,
> or any other material used to process or formulate classified
> information. When no longer needed, such media will be destroyed as
> classified waste.
>
> h\. The appropriate cover sheet will be attached to classified
> material when not in secure storage; i.e., Standard Form 704 attached
> to SECRET material and SF-705 attached to CONFIDENTIAL material.

203.12 [ACCOUNTABILITY RECORDS]{.underline}

> a\. [Accountable Material]{.underline}. Accountable classified
> materials entered into the KSC CMCS are assigned control numbers by
> the CMCC; receipts are prepared, and the paper cover sheets are
> attached.
>
> \(1\) Records will be maintained by the CMCC for all accountable
> classified material.
>
> \(2\) Each account maintains records consisting of KSC Forms 16-122.
> The records are grouped into an \"active\" file, an \"inactive\" file,
> and a \"suspense\" file. The active file contains receipts for the
> material stored by the account. The suspense file contains receipts
> for material which is charged out to an individual or is temporarily
> loaned to another account. The inactive file contains receipts for
> material which has been permanently transferred out of the account.
> Each record in the inactive file will be maintained for 2 full
> calendar years.
>
> b\. [Non-accountable Material]{.underline}. Non-accountable classified
> material (refer to paragraph 203.11) will be logged on KSC Form
> 7-66NS, CONFIDENTIAL Material Log, when received by the CMCC. Although
> there is no requirement for custodians to log non-accountable material
> in their accounts, they may do so by using KSC Form 7-66NS.

203.13 [ACCOUNTABILITY PROCEDURES]{.underline}

> a\. Material received from outside the KSC Classified Material Control
> System.
>
> \(1\) The CMCC will check the material received against the sender\'s
> receipt. Any discrepancies will be brought to the attention of the
> originator/sender for appropriate action. The CMCC will sign the
> receipt, keep a copy for its records, and return the original to the
> sender.
>
> \(2\) The CMCC will prepare a KSC Form 16-122 for all accountable
> classified material and log all non-accountable CONFIDENTIAL
> classified material on KSC Form 7-66NS. CMCC will contact the account
> which services the material\'s addressee(s) for pickup.
>
> \(3\) The account\'s custodian will check the accountable material
> against the KSC Form 16-122, sign the receipt, return the \"CMCC\"
> copy to the courier, attach the \"material\" copy to the material, and
> file the \"custodian\" copy in the account\'s active file.
>
> b\. If classified material is received directly from outside the KSC
> CMCS by any department or person other than the CMCC, the recipient
> will immediately contact the CMCC.
>
> c\. Accountable classified material generated at KSC will be entered
> into the KSC CMCS.
>
> d\. [Permanent Transfer Within the KSC CMCS.]{.underline}
>
> \(1\) When accountable material is transferred to another account, the
> custodian will prepare a KSC Form 16-122. The custodian will contact
> the CMCC for instructions. The custodian will remove the old
> \"custodian\" copy from the active file, attach the \"sender\" copy to
> it, and place both in the account\'s inactive file.
>
> \(2\) The custodian who receives accountable classified material will
> check it against the KSC Form 16-122 and sign the receipt. The
> \"material\" copy of the form will be attached to the material, the
> \"custodian\" copy will be placed in the account\'s active file, and
> the original filed with CMCC.
>
> e\. [Temporary Loan Within the KSC CMCS]{.underline}. Accountable
> classified material may be issued temporarily to personnel who are
> cleared at the appropriate level and have a need-to-know. The
> custodian will have the recipient sign the reverse side of the
> \"custodian\" copy of the KSC Form 16-122, which will then be filed in
> the suspense file. The recipient is responsible for safeguarding the
> classified material until it is returned to the account. When the
> material is returned, the custodian will initial the reverse side of
> the \"custodian\" copy and return it to the active file. Material will
> be issued for temporary use for a maximum of 5 consecutive days.
> Material required for more than 5 days will be permanently
> transferred.
>
> f\. [Transfer Outside the KSC CMCS.]{.underline} Classified material
> transmitted outside the KSC Classified Material Control System will be
> processed through the CMCC. The custodian will prepare a KSC Form
> 16-122 to transfer the material to the CMCC. The name and complete
> address of the person to whom the material is to be sent will be
> included in the remarks section of the form. The address will include
> mail codes, attention lines, or an individual\'s name. The custodian
> will notify the CMCC for instructions. The custodian will remove the
> old \"custodian\" copy from the active file, attach to it the new
> \"sender\" copy, and place them in the inactive file. The CMCC will
> prepare the material for transmittal, verify the mailing address, and
> the addressee\'s authorization to receive classified material.
>
> g\. [Downgrading/Declassifying.]{.underline}
>
> \(1\) When SECRET material is downgraded to CONFIDENTIAL, the
> custodian will note the authority for downgrading in the remarks
> section of the \"custodian\" and \"material\" copies of the
> controlling KSC Form 16-122. The \"custodian\" copy will be filed in
> the inactive file and the \"material\" copy will be sent to the CMCC.
>
> \(2\) In those cases where downgraded material remains accountable,
> the custodian will note the authority for downgrading in the remarks
> section of the \"custodian\" and \"material\" copies of the KSC Form
> 16-122, refile the copies, and notify CMCC of actions taken.
>
> \(3\) When accountable material is to be declassified, the custodian
> will annotate the \"material\" and \"custodian\" copies of the KSC
> Form 16-122 in the remarks section with the declassification
> authority. The custodian will send the \"material\" copy to the CMCC
> and place the \"custodian\" copy in the inactive file.
>
> \(4\) A copy of the document (letter, message, etc.) authorizing
> downgrading or declassification will be attached to each copy of the
> material affected.
>
> h\. [Upgrading.]{.underline}
>
> \(1\) Material which is upgraded to TOP SECRET will be processed by
> NASA Security.
>
> \(2\) Non-accountable CONFIDENTIAL material which is upgraded to
> SECRET will require a classified material receipt. The custodian will
> prepare a KSC Form 16-122, note in the remarks section that the
> material is being upgraded and include the authority for it, and
> process the material in the same manner as accountable material which
> is generated at KSC.
>
> \(3\) CONFIDENTIAL Restricted Data and Formerly Restricted Data
> already bears a KSC Form 16-122. When it is upgraded to SECRET, the
> custodian will note the authority for the upgrade on the \"material\"
> and \"custodian\" copies of the form and will notify the CMCC.
>
> \(4\) Unclassified material to be upgraded will be processed as newly
> classified material through the applicable Government or contractor
> security office.
>
> i\. [Destruction.]{.underline} (Refer to paragraphs 203.19 and 203.20
> for additional instructions on destroying classified material.) The
> primary custodian will authorize destruction of classified material
> assigned to the account. The custodian will ensure that the material
> is no longer required before authorizing destruction.
>
> \(1\) For accountable material, the custodian will prepare a KSC Form
> 16-122 and transfer the material to the CMCC. The primary custodian
> will sign the section labeled \"Authorized for Destruction.\" The
> custodian will notify the CMCC and request destruction instructions.
> The custodian will remove the old \"custodian\" copy from the active
> file, attach the new \"sender\" copy to it, and place both in the
> inactive file.
>
> \(2\) Bulk Destruction Procedures. When an account has 5 or more
> accountable documents to be destroyed, the following procedure may be
> used. The custodian will prepare, in duplicate, KSC Form 20-32,
> Certificate of Classified Document Destruction. The primary custodian
> will prepare this form for CMCC use. The custodian will retain a
> duplicate copy of the Form 20-32. Attach all \"custodian\" copies of
> KSC Form 16-122 to the KSC Form 20-32 and place in the account\'s
> inactive file.

203.14 [INVENTORIES]{.underline}

> a\. The CMCC may be requested to assist in an inventory, at least
> annually, of each account. The primary custodian will assist in the
> inventory, locating and personally viewing each piece of accountable
> classified material that is charged to the account.
>
> b\. An account will be inventoried by the CMCC upon the removal or
> replacement of a custodian or alternate custodian. The inventory will
> be completed before the custodian departs. Discrepancies will be
> reported to NASA Security.
>
> c\. Whenever a classified storage container is found unlocked and
> unattended, the primary custodian will conduct an inventory jointly
> with a CMCC representative. An incident report will be filed as
> required by Chapter 204 of this handbook.

203.15 [ASSISTANCE VISITS]{.underline}

> a\. The assistance visit program ensures compliance with the
> procedures set forth in this handbook and verifies the adequacy of all
> classified document accounts within the purview of the KSC Classified
> Material Control System.
>
> b\. Assistance visits may be made to each classified account to
> ascertain that all applicable procedures are properly implemented and
> effectively utilized. NASA Security representatives will identify and
> document any discrepancies noted during such visits and prepare a
> written report of their findings.

203.16 [TRANSMISSION]{.underline}

> a\. [General Requirements.]{.underline}
>
> \(1\) Classified material transmitted outside of the KSC Classified
> Material Control System will be processed through the CMCC.
>
> \(2\) Classified material will normally be brought into or taken out
> of KSC and CCAFS by the U.S. Postal Service. All material not
> delivered in this manner must be immediately turned in to the CMCC.
>
> \(3\) Classified material may not be transmitted outside the
> continental United States without the written approval of NASA
> Security.
>
> \(4\) NASA Security will be notified if classified material is
> received and the package:
>
> \(a\) Has been improperly wrapped.
>
> \(b\) Shows any evidence or signs of tampering.
>
> \(c\) Has been improperly transmitted.
>
> b\. [Preparation/Method of Transmission on KSC/CCAFS]{.underline}. All
> personnel who transport classified materials will comply with the
> accountability procedures of paragraph 203.12, if applicable, and
> prepare the material for transport as follows:
>
> \(1\) All classified material will have the appropriate cover sheet
> attached when not in secure storage.
>
> \(2\) Outside the immediate office work area and between buildings
> within the KSC Industrial area, the LC-39 area, and the CCAFS area,
> classified material must be carried in a sealed envelope or other
> opaque cover with appropriate addresses and department numbers of both
> sending and receiving organizations on the cover.
>
> \(3\) The sealed package must be placed within another envelope or
> opaque cover (briefcase, box, etc.). Additional care should be taken
> to adhere to the accountability procedures of paragraph 203.13 to
> include the use of classified material receipts.
>
> \(4\) If the classified material is large or is an item of equipment
> not suitable for packaging as described above, it will be enclosed in
> an opaque covering that will conceal all classified characteristics.
>
> c\. [Preparation/Method of Transmission off KSC/CCAFS.]{.underline}
>
> \(1\) For Space Shuttle Launch Team members located at PAFB and
> elsewhere outside the confines of KSC/CCAFS, follow the procedures of
> paragraph b.(3) above.
>
> \(2\) U.S. Certified and Registered mail are the only methods for
> mailing classified material from KSC through postal services. U.S.
> Certified mail may be used to transmit CONFIDENTIAL material within
> the United States. Only U.S. Registered mail will be used to transmit
> SECRET material.
>
> \(3\) CONFIDENTIAL and SECRET material may be sent via U.S. Postal
> Express Mail Service. Contact the CMCC for information concerning this
> service.
>
> d\. [Shipping Equipment and Large Items]{.underline}. Organizations
> requiring shipment of classified equipment or large items not suitable
> for mailing will coordinate all packing and transfer procedures with
> the CMCC.
>
> e\. [Transporting Classified Materials on KSC/CCAFS.]{.underline}
>
> \(1\) CMCC couriers are authorized to transport classified materials
> on KSC/CCAFS. They are the only couriers authorized to transport
> classified materials "to organizations not within the KSC CMCS," to
> J-BOSC Reprographics for reproduction processing, and to destruction
> facilities for destruction.
>
> \(2\) Custodians and other individuals may transport classified
> materials on KSC/CCAFS for official business purposes and/or in
> support of the STS Launch Team, when authorized by the KSC Protective
> Services Branch. Contractor employees must coordinate with their
> applicable security office and be approved by NASA Security.
>
> \(3\) Any person who transports classified materials will:
>
> \(a\) Wear his/her NASA or KSC identification badge.
>
> \(b\) Not divulge to anyone, except as required in the execution of
> his/her duties, the fact that classified material is being
> transported.
>
> \(c\) Not read, discuss, or expose the classified material in public
> vehicles or public places.
>
> \(d\) Not place classified material in open or detachable compartments
> of private, public, or Government conveyances, such as trailers and
> luggage racks or in open truck bodies.
>
> \(e\) Maintain personal custody and safeguard such material at all
> times.
>
> \(f\) Contact NASA Security, by the quickest means available, if the
> classified material is seized by unauthorized persons, lost, stolen,
> or otherwise subjected to possible compromise.
>
> f\. [Transporting Classified Materials off KSC/CCAFS.]{.underline}
>
> \(1\) Couriers who carry or accompany classified material will be
> briefed by their security officer concerning the requirements and
> limitations of courier duty. A separate briefing will be given for
> each courier assignment. The courier must read and sign a copy of the
> \"Courier Instructions\" which are contained in Appendix G. KSC Form
> 20-49, Authorization to Hand-Carry Classified Material, will be
> prepared by the courier\'s security officer and approved by NASA
> Security. The KSC Form 20-49 must remain in the courier\'s possession
> while transporting classified material.
>
> \(2\) Couriers required to transport classified materials aboard
> commercial aircraft will be issued a letter by NASA Security. The
> letter will be used to identify the courier to airline personnel. The
> KSC Form 20-49 will not be shown to airline personnel.
>
> \(3\) KSC Form 20-49 must be completed by all couriers upon completion
> of courier duty outside KSC/CCAFS/PAFB. The form will be returned to
> the CMCC upon completion. Sections concerning deviations in itinerary
> must explain any deviation or incidents which occurred during the
> assignment.

203.17 [INCOMING SHIPMENTS]{.underline}

> a\. Any organization which receives a classified shipment will:
>
> \(1\) Contact the CMCC immediately upon receipt of the shipment.
>
> \(2\) Sign, date, and distribute copies of the freight bill, delivery
> receipt, or other paperwork concerning the shipment except for the
> classified material receipt.
>
> \(3\) Properly store and protect the classified shipment until it is
> delivered or transferred to the consignee.
>
> b\. The CMCC will:
>
> \(1\) Inspect the classified shipment for proper marking, method of
> shipment, quantity, and content as stated on the Classified Material
> Receipt enclosed with the shipment.
>
> \(2\) Complete the Classified Material Receipt and return the original
> copy to the sender.
>
> \(3\) Enter the material into the CMCS.
>
> \(4\) Assign the material to the account of the consignee.
>
> c\. The consignee will store the material according to the provisions
> of this chapter. If adequate storage is not available, the consignee
> will arrange through his/her security officer for alternate storage or
> guard service.
>
> d\. Consignees will normally be notified by the consignor when
> shipments of classified equipment and/or large items are expected to
> arrive at KSC. If a consignee does not receive notification of a
> classified shipment within 1 working day after the estimated date of
> arrival, the consignee should first determine that the shipment has
> not arrived at KSC, then contact the consignor by telephone or
> telegraphic message so that the consignor can initiate tracer action.

203.18 [REPRODUCTION]{.underline}

> a\. Reproduction of classified material will be kept to a minimum
> consistent with efficient operations, and limited in order to lessen
> the risk of compromise and the expense of subsequent protection.
>
> b\. Reproduction, for purposes of this chapter, is any activity that
> duplicates classified information. This includes, but is not limited
> to, photocopying, printing, and photographing, all of which is
> addressed herein. Any other reproduction of classified material must
> be in accordance with procedures as approved by NASA Security.
>
> c\. Classified material may be reproduced only on equipment that has
> been approved for that purpose by NASA Security.
>
> d\. Key personnel, as listed below, may authorize reproduction of
> classified materials for their respective organizational elements:
>
> \(1\) Branch chiefs or higher of NASA organizational elements for
> materials classified up to and including SECRET.
>
> \(2\) The security officer, or a designated representative, of other
> organizations for material classified up to and including SECRET.
> Organizations which do not have a security officer at KSC will consult
> NASA Security, when classified reproduction is needed.
>
> \(3\) Section chiefs or higher of NASA organizational elements for
> material which is classified up to, and including CONFIDENTIAL.
>
> e\. Persons identified in paragraph d. above who request reproduction
> of classified documents must provide specimen signatures on KSC Form
> 20-65NS, Classified Reproduction Authority. The form shall be prepared
> in two copies and forwarded to NASA Security. The security office will
> review and complete the form, retain one copy, and forward the
> original to the CMCC. The security officer will promptly notify the
> CMCC of any change in information on the form. Appendix B contains a
> sample and instructions for KSC Form 20-65NS.
>
> f\. All requests for reproduction of accountable and non-accountable
> classified material must be forwarded to the CMCC. NASA Security may
> authorize reproduction of classified materials by other individuals or
> organizational functions when deemed necessary in support of launch
> operations.
>
> g\. Persons requesting reproduction of accountable and non-accountable
> classified materials shall sign a KSC Form 16-8, Reproduction and
> Documentation Work Order, note in the \"special instructions\" section
> that the material to be reproduced is classified, and indicate the
> number of copies requested. If necessary, a distribution list should
> be included. The requester shall deliver the classified material and
> KSC Form 16-8 to the custodian of his/her account. The custodian shall
> follow the accountability procedures of paragraph 203.13.
>
> h\. SECRET and CONFIDENTIAL material originated outside NASA and
> having a specific prohibition regarding reproduction requires the
> authorization of the originating organization. Requests to the
> originating organization for authorization to reproduce the material
> will be routed through NASA Security. Upon receipt, authorizations to
> reproduce will be attached to the KSC Form 16-8.
>
> i\. Category One working papers will not be reproduced without first
> being entered into the KSC Classified Material Control System.
>
> j\. Category Two operational working papers to be reproduced shall be
> delivered in person to the CMCC or other Designated Area Reproduction
> Point (DARP).
>
> k\. The CMCC or custodian at the DARP will maintain the original of
> KSC Form 29-149, Classified Reproduction Request (Operational Working
> Papers), with the following information recorded:
>
> \(1\) Title of document.
>
> \(2\) Date and origination of document.
>
> \(3\) Classification of document.
>
> \(4\) Number of copies requested.
>
> \(5\) Total number of pages reproduced.
>
> \(6\) Name of requester.
>
> DARP\'s will forward the KSC Forms 29-149 to the CMCC at least once
> every 15 days. Working papers will be marked, stamped, and dated, as
> applicable, in accordance with requirements of paragraph 203.11.
>
> l\. Organizations not within the KSC CMCS may obtain reproduction of
> classified material by delivering it directly to the J-BOSC
> Reprographics Work Order Section, KSC Headquarters Building, Room
> 1340. Specimen signatures of individuals authorized to request
> reproduction must be provided to J-BOSC Reprographics on KSC Form
> 20-65NS. Instructions of paragraph g. above will be followed when
> requesting reproduction of classified materials.

203.19 [DESTRUCTION]{.underline}

> a\. Classified material within the KSC Classified Material Control
> System will be destroyed only by the CMCC.
>
> b\. When doubt exists as to the propriety of destroying classified
> material received from another Federal department or agency, consult
> NASA Security, for instructions.
>
> c\. To prevent an unnecessary accumulation of classified material,
> each organization will continuously review its classified holdings and
> will reduce it to the minimum needed for efficient operations. Surplus
> copies will be transferred or destroyed as soon as practical.
> Accountability records for accountable material will be maintained 2
> years from the date that all materials listed thereon have been
> destroyed.
>
> d\. At regular intervals classified waste will be passed to the CMCC
> for destruction so that the amount on hand is kept to a minimum.

203.20 [DESTRUCTION PROCEDURES]{.underline}

> a\. The primary custodian will follow the procedures of paragraph
> 203.13.i for destruction of accountable and non-accountable classified
> material.
>
> b\. Classified working papers will be destroyed as classified waste.
>
> c\. Custodians will store other classified waste in authorized
> classified containers until it can be transferred to the CMCC for
> destruction.

203.21 [FOREIGN GOVERNMENT INFORMATION]{.underline}

> a\. Classified foreign government information shall be protected and
> accounted for in accordance with the procedures as specified in this
> chapter for comparable U.S. classified information.
>
> b\. Foreign government documents marked \"RESTRICTED\" or marked with
> any classification designation listed in the last (fourth) column on
> the equivalency chart (DOD 5220.22-M, NISPOM, appendix B) shall be
> protected as U.S. CONFIDENTIAL.

203.22 [SECURE CONFERENCE ROOMS]{.underline}

> General requirements for establishing and maintaining Secure
> Conference Rooms are contained in Chapter 27, NHB 1620.3, NASA
> Security Handbook.

**CHAPTER 204**

**CLASSIFIED INFORMATION INCIDENT REPORTING**

204.1 [GENERAL]{.underline}

> a\. Time is critical when reporting and investigating incidents
> involving classified material. All organizations will take steps to
> ensure the timely reporting of incidents covered by this chapter.
>
> b\. In cases where a physical examination of a particular item or site
> is likely during the course of an investigation, the item or site will
> be preserved exactly as found, provided that this does not either
> jeopardize safety, nor disclose classified information. Refer to
> paragraph 204.2b.(1).
>
> c\. When an incident may gravely affect the national security or the
> preservation of critical national resources, the Installation Security
> Officer or a NASA-KSC investigator, may, as long as safety is not
> jeopardized, initiate the following:
>
> \(1\) Order that the scene of the incident be protected to assure the
> preservation of evidence by freezing conditions and configurations.
>
> \(2\) Impound material.
>
> \(3\) Conduct interviews.
>
> \(4\) Order persons who are knowledgeable of the incident or
> investigation not to discuss it except as directed by the Installation
> Security Officer or NASA-KSC investigator.

204.2 [SECURITY VIOLATIONS AND COMPROMISE OF CLASSIFIED
INFORMATION]{.underline}

> a\. Classified information is vulnerable to compromise when personnel
> allow themselves to become negligent. The most common security
> violations are:
>
> \(1\) Failing to properly secure classified material in an authorized
> container when it is not under
>
> their immediate, continuing control and supervision.
>
> \(2\) Not properly preparing classified material for transmission, or
> improperly transmitting such material.
>
> \(3\) Discussing or attempting to \"talk around\" classified
> information during telephone conversations or in places where
> unauthorized persons are present.
>
> \(4\) Misplacing or otherwise losing control of classified material
> (including classified waste).
>
> \(5\) Releasing classified information without properly determining
> the recipient\'s identity, clearance status, and need-to-know. Also
> see paragraph 204.3.
>
> b\. [Emergency Action and Reporting Requirements]{.underline}.
> Individuals who observe that classified information is not being given
> the prescribed protection, or that classified material has been lost
> or compromised, will:
>
> \(1\) Immediately take all interim action possible to restore the
> prescribed security controls over the information or material. An
> examination of an item or site is likely during the course of an
> investigation (such as, in the burglary of a safe), then take care to
> preserve the site as long as this will not seriously degrade the
> integrity or the security of other areas, material, or information.
> Refer to paragraph 204.1b.
>
> \(2\) Report the circumstances promptly to an immediate supervisor,
> or, if not immediately available, directly to NASA Security. Non-NASA
> personnel will report the circumstances to their employer\'s security
> personnel or, if none, directly to NASA Security .
>
> c\. The following actions apply to NASA Security for KSC
> organizations. They apply to the security personnel of other
> organizations provided they have at least one employee duty stationed
> at KSC who performs security duties full time. Otherwise, these
> actions will be performed by NASA Security for the other organization.
>
> \(1\) [Preliminary Action and Inquiry]{.underline}. Once apprised that
> there has been any loss of prescribed security control over classified
> information, security personnel will take appropriate action to:
>
> \(a\) Immediately fully restore security controls over the information
> or material.
>
> \(b\) Ensure that all classified material involved is accounted for by
> the custodian(s) as expeditiously as possible. However, if Secret or
> Top Secret material is involved, an inventory will be conducted
> immediately. Additionally, CMCC personnel will be involved in the
> inventory regardless of what office is involved.
>
> \(c\) Immediately change the combination of each locking device which
> may have been subjected to compromise.
>
> \(d\) Promptly conduct a preliminary inquiry to determine if the
> information or material has been compromised.
>
> \(e\) Promptly inform NASA Security of the preliminary actions taken.
> Subsequently, provide the written results of the inquiry.
>
> \(2\) [Action Required When Classified Information Was Not
> Compromised]{.underline}. If the preliminary inquiry indicates that
> the information or material was not compromised, but that a security
> violation did occur, security personnel will:
>
> \(a\) Determine the circumstances surrounding the security violation
> and the identity of the individual(s) responsible.
>
> \(b\) Obtain a written account of the violation from the responsible
> individual(s).
>
> \(c\) Provide copies of a report containing essential details of the
> incident to the responsible individual\'s supervisor(s), and NASA
> Security.
>
> \(d\) Take corrective action to eliminate the practice or condition
> which caused or permitted the security violation.
>
> \(e\) Notify the responsible KSC organization, other Government
> agency, or contractor, if the security violation involves improper
> mailing, wrapping, accountability, or addressing of an envelope (or
> other cover) containing classified material.
>
> \(3\) [Action Required for Possible Loss or Compromise of Classified
> Information.]{.underline}
>
> \(a\) Action by Security Personnel. If the preliminary inquiry
> indicates that classified information has been compromised, security
> personnel will immediately turn the matter over to NASA Security.
>
> \(b\) [NASA Security:]{.underline}
>
> [1.]{.underline} Conducts a full inquiry for the purpose of taking
> corrective measures and appropriate administrative, disciplinary, or
> legal action.
>
> [2.]{.underline} Takes every reasonable measure to promptly regain
> custody of all missing material and to restore appropriate security
> controls.
>
> [3.]{.underline} Promptly notifies the following of the incident and
> of each pertinent development: The Lead, NASA Security, will notify
> the Installation Security Officer and subsequently, as appropriate,
> inform senior management officials and program managers; the Director,
> NASA Headquarters/NASA Security Office and the agency or organization
> originating the classified information or material. Unless otherwise
> directed, no additional dissemination of information will be made
> while the incident is under active investigation.
>
> \(4\) [Corrective Action.]{.underline} Within the limitations set
> forth in this chapter and the NASA Physical Security Handbook,
> determine the circumstances which permitted the loss or compromise,
> and take all necessary action to preclude a recurrence.
>
> \(5\) [Final Report.]{.underline} Within the guidelines and
> limitations set forth in this chapter, at the conclusion of the
> investigation, prepare a final report of all pertinent findings.
> Provide copies of this report, as appropriate, to all persons,
> organizations, and agencies previously provided preliminary copies of
> the incident report.

204.3 [OTHER REPORTABLE INCIDENTS]{.underline}

> The following incidents may relate to the protection of either
> classified information or critical Government resources. These
> incidents will be reported in the manner described in paragraph 204.2.
> This list is not all inclusive. Other incidents, similar to those
> listed below, may require reporting.
>
> a\. The presence of uncleared individuals, without proper escort, in a
> security area.
>
> b\. The presence of an individual in a security area who does not have
> a need for being in that area.
>
> c\. Requests for classified information from sources whose need to
> know is questionable.

204.4 [TRAINING]{.underline}

> a\. Anyone involved in a security compromise who is found to be in
> violation of law or policy will be required to attend specific
> security training to preclude further incidents or violations.
>
> b\. Specific training may be recommended by the security office
> handling the investigation.
>
> c\. Unless the individual\'s clearance is suspended or revoked, the
> training must be accomplished prior to the individual returning to
> duties involving classified material or information.
>
> d\. A record of the training will be maintained with the incident\'s
> investigative case file.

204.5 [PENALTIES]{.underline}

> a\. Willful disregard of any security instruction or policy may result
> in removal from Federal service.
>
> b\. Careless or negligent failure to observe any security instruction
> or policy could result in disciplinary action pursuant to KMI 3751.1,
> \"Employee Conduct and Discipline\" and Chapter 751 of the Federal
> Personnel Manual.
>
> c\. In the event of security violations by military personnel detailed
> to KSC, the verbal admonishment for the first violation may be
> administered in the same manner as for civilian employees. Subsequent
> violations will be reported to the individual\'s military
> organization, where military disciplinary procedures may apply.

**CHAPTER 205**

**FOREIGN CONTACTS, REQUESTS FOR INFORMATION**

**AND FOREIGN TRAVEL**

205.1 [GENERAL]{.underline}

> This Chapter provides instructions and reporting criteria for contacts
> with foreign nationals and unauthorized requests for information. It
> also provides security briefing criteria for official and personal
> foreign travel to designated countries and areas.

205.2 [RESPONSIBILITIES]{.underline}

> a\. Government employees at the Kennedy Space Center will follow the
> guidance in this Chapter.
>
> b\. Contractor employees will follow the guidance in the National
> Industrial Security Program Operating Manual (NISPOM), Standard
> Practice Procedures, and this Chapter.

205.3 [REPORTING CONTACTS WITH FOREIGN NATIONALS AND REPRESENTATIVES OF
A DESIGNATED COUNTRY OR AREA]{.underline}

> a\. [\"Establishments\"]{.underline} means embassies, consulates,
> press, airline, travel or business offices representing designated
> countries or areas.
>
> b\. [\"Foreign National or Representatives\"]{.underline} means any
> designated country or area diplomat, visitor, tourist, student,
> journalist, engineer, or scientist. Representatives also include
> United States citizens representing or acting on behalf of a
> designated country or area.
>
> c\. [\"Contacts"]{.underline} mean any form of meeting, association,
> or communication, regardless of who made the contact. The contact
> could be for social, official, private, or any other reason. Contacts
> made in person, by radio; i.e., HF, UHF, or VHF, telephone, letter,
> post cards, facsimile, computer/Internet access (electronic
> mail/electronic bulletin boards) and receiving subscriptions to
> designated country publications are reportable.
>
> d\. Report all contacts with Foreign Nationals, representatives, or
> establishments of designated countries or areas, including contacts
> made or received by family members.
>
> e\. [For NASA KSC Government Employees]{.underline}:
>
> Report \"contacts\" to the J-BOSC Security Awareness Office, 861-5657,
> SGS-323.
>
> f\. [For Contractor Personnel]{.underline}:
>
> Follow your company\'s Standard Practice Procedures (SPP\'s), the
> National Industrial Security Program Operating Manual, and this
> Chapter, as appropriate, to report \"contacts\".

205.4 [REPORTING REQUESTS FOR INFORMATION]{.underline}

> a\. All requests for information or materials made by anyone without a
> need-to-know or outside official channels are unauthorized requests.
> This means classified or unclassified information, documents,
> publications, material or equipment that is under government or
> contractor control.
>
> b\. Additional restrictions may also apply on requests for information
> and the release of information or materials; examples are: The Export
> Administration Act of 1979 (50 U.S.C App. 2401-2420), The Arms Export
> Control Act as implemented by the International Traffic in Arms
> Regulations (ITAR), 22 CFR Part 125, and the Federal Acquisition
> Regulation, 35 U.S.C. 205, Subpart 27.3.
>
> c\. Do not decide for yourself the significance of a request for
> information. Take the following action after an unauthorized request:
>
> d\. [For NASA KSC Government Employees]{.underline}
>
> \(1\) Report all unauthorized requests for information to NASA
> Security, 867-2453.
>
> \(2\) Do not discuss the information with anyone other than a
> representative of NASA Security. If the situation occurs away from a
> NASA installation, and urgency is considered appropriate, contact the
> nearest FBI Office.
>
> (Note: The first page of a telephone directory, in the United States,
> usually contains the telephone number of the nearest FBI Office.)
>
> e\. [For Contractor Personnel]{.underline}
>
> Follow the provisions of the National Industrial Security Program
> Operating Manual and your company\'s Standard Practice Procedures
> (SPP\'s). If a company security representative is not immediately
> available, report the occurrence to a representative of NASA Security.

205.5 [FOREIGN TRAVEL]{.underline}

> a\. [For NASA KSC Government Employees]{.underline}:
>
> \(1\) Travel to countries/areas, that are not listed as designated
> countries or areas, does not require a travel preapproval. Before
> traveling however, all employees should request a Foreign Travel
> Briefing, from the J-BOSC Security Awareness Office, to increase their
> security awareness.
>
> \(2\) Foreign travel, whether official or personal, into
> countries/areas that are listed as designated countries or areas,
> requires preapproval of the Installation Security Officer. NASA KSC
> employees occupying Mission-Critical positions, performing
> Mission-Critical duties, or having access to classified information,
> must provide NASA Security with the following information at least 3
> weeks before their departure:
>
> \(a\) Full name, date and place of birth.
>
> \(b\) Current citizenship.
>
> \(c\) Organization, duty station, and job title.
>
> \(d\) Purpose of travel.
>
> \(e\) Security clearance.
>
> \(f\) Date of last defensive security briefing.
>
> \(g\) Passport number, issue and expiration date, and identification
> of all visas.
>
> \(h\) Whether or not they are assigned to a Mission-Critical position
> or are performing Mission-Critical duties.
>
> \(i\) Whether or not they have access to classified material.
> (Classified custodian, alternate, or user.) If yes, identify the
> classified account or material used.
>
> \(j\) Identify any previous security violations or disclosure of
> classified information.
>
> \(k\) Furnish dates of planned entry/visit/exit for each designated
> country/city/area on the trip.
>
> \(l\) Identify relationships and addresses of relatives living in any
> designated country or area.
>
> \(m\) Identify previous designated countries or areas visited, and the
> dates of such visits.
>
> \(n\) Identify any citizens of designated countries or areas with whom
> the employee has associated or corresponded and the nature of such
> association or correspondence.
>
> \(3\) NASA KSC employees not occupying Mission-critical
> positions/duties or having access to classified information, that
> desire official or personal travel to a designated country or area, do
> not need a preapproval for foreign travel. However, a foreign travel
> briefing from the Security Awareness Office, 861-5657, is required
> before departure.
>
> \(4\) All NASA KSC employees traveling to, from, or within designated
> countries or areas require a security debriefing upon their return to
> work. Contact the Security Awareness Office for an appointment.
>
> b\. [For Contractor Employees]{.underline}:
>
> Follow your company\'s Standard Practice Procedures, the National
> Industrial Security Program Operating Manual and this Chapter, as
> appropriate.

205.6 [DESIGNATED COUNTRIES AND AREAS. \*]{.underline}

> a\. For travel within the purview of this Chapter designated countries
> or areas are:
>
> Afghanistan
>
> Albania
>
> Angola
>
> \* Armenia
>
> \* Azerbaijan
>
> \* Belarus
>
> Bulgaria
>
> Cuba
>
> \* Estonia
>
> Ethiopia
>
> \* Georgia
>
> Iran
>
> Iraq
>
> Kampuchea
>
> \* Kazakhstan
>
> \* Kyrgyzstan
>
> Laos
>
> \* Latvia
>
> Libya
>
> \* Lithuania
>
> \* Moldava
>
> Mongolia (O)
>
> Nicaragua
>
> North Korea
>
> People\'s Republic of China, including Tibet
>
> Rumania
>
> \* Russia/Union of Soviet Socialist Republics (former Republics)
>
> South Yemen
>
> \* Tajikistan
>
> \* Turkmenistan
>
> \* Ukraine
>
> \* Uzbekistan
>
> Kurile Islands
>
> Sakhalin (S)
>
> Syria
>
> Socialist Republic of Vietnam
>
> \*\* Yugoslavia.
>
> \* Former USSR
>
> \*\* Divided Country
>
> b\. World situations have caused political changes in recent
> months/years. Prior to traveling, contact the Security Awareness
> Office, 861-5657, for a current list of Designated Countries and
> areas, travel requirements, and information about your destination(s).
>
> \* Status of countries and areas could change at any time. Consult the
> Security Awareness Office for the current status of the country/area
> to which you are traveling.

**CHAPTER 301**

**TECHNICAL SECURITY SAFEGUARD SYSTEMS**

301.1 [GENERAL]{.underline}

> This chapter establishes technical standards to be applied during
> design, development, and procurement of technical security safeguards
> at KSC and other areas/facilities under the cognizance of KSC.

301.2 [CONCEPT]{.underline}

> The design, installation, and operation of technical security
> safeguard systems are intended to enhance the overall security posture
> of an area/facility and contribute to the attainment of both
> operational effectiveness and KSC security objectives. Such safeguards
> and systems are designed to detect actual or attempted illegal
> penetrations of sensitive/critical areas. They must, therefore, be
> supported by a monitoring station and a security force capable of
> responding promptly to indicators of illegal penetrations.

301.3 [SYSTEM DESCRIPTIONS]{.underline}

> a\. [Intrusion Detection Systems (IDS)]{.underline}. IDS are used as
> technical aids for the security forces to expand conventional
> capability and to alert security guards and responsible personnel of
> intrusions at protected facilities. As a minimum, rooms or buildings
> containing mission-critical assets should be equipped with appropriate
> intrusion detection systems.
>
> b\. [Closed Circuit Television (CCTV).]{.underline} CCTV is used as an
> aid to security force personnel in true/false alarm assessment, as a
> motion detector (with additional circuitry added), and for personnel
> identification in conjunction with access control systems. Areas
> considered for CCTV coverage are those requiring continuous
> surveillance, those areas which require visual monitoring but which
> would otherwise impose an excessive expenditure of security force
> support, and those areas requiring other special visual surveillance.
>
> c\. [Access Control Systems (ACS).]{.underline} The objectives of an
> access control system are to permit only authorized persons to enter
> and exit controlled areas, and to provide information to the
> respective access control monitor, which will facilitate assessment
> and response to indications of unauthorized entry. Access controls can
> be found in many different forms. In general, security is enhanced by
> supplementing the conventional guard force with an access control
> system.

301.4 [REQUIREMENTS]{.underline}

> a\. [Identifying the Need.]{.underline} It is the responsibility of
> site management to identify to NASA Security the fact that an area or
> facility may need the added protection of a technical security
> safeguard/system. NASA Security will arrange for a Risk Analysis which
> will identify specific security weaknesses in and around the
> area/facility. NASA Security provides the policies and procedures by
> which these analyses are judged and will determine the appropriate
> technical security measures to be instituted.
>
> b\. [Requesting the Safeguard/System]{.underline}.
>
> \(1\) Requester/Site Manager must develop a written statement of
> justification identifying the need for a technical security
> safeguard/system at the facility. This statement should identify the
> need or requirement rather than specifying the method of
> accomplishment. This written statement should include certain
> site-specific data; such as, exact location, estimated need date, and
> concept of operations (normal and emergency).
>
> \(2\) The need identified in the written justification is then
> forwarded to NASA Security. After Risk Analysis is completed, the
> requirements are refined jointly between the requester and NASA
> Security.
>
> \(3\) After requirements are refined and a method to satisfy them
> agreed to, the requester generates an Engineering Support Request
> (ESR). The NASA Security, Technical Security Specialist will, by
> signature, concur with the ESR before its insertion into the
> implementation process.
>
> c\. [NASA Security Role.]{.underline} Once a requester or Site Manager
> has identified a valid need for a technical security safeguard/system,
> NASA Security is obligated to ensure that the need is satisfied in a
> competent, cost-effective manner that is compatible with other
> existing and planned Centerwide systems. Therefore, NASA Security will
> be the focal point for all such projects, from concept development to
> system activation/operation.
>
> d\. [Joint-Base Operations Support Contractor's (J-BOSC)
> Role]{.underline}. J-BOSC\'s responsibility in relation to technical
> security safeguards/systems is, generally, one of operations and
> maintenance (O&M) and of sustaining engineering functions, including
> Facility Project design and implementation. They are responsible for
> the performance of preventive, corrective and breakdown maintenance of
> all field equipment to ensure that ESS maintains a high level of
> operational performance. Inherent in this responsibility is the
> development of maintenance plans, each tailored to the unique system
> being maintained. Maintenance plans will include, as appropriate,
> requirements for testing/retesting. All maintenance and other system
> support plans will be coordinated with NASA Security for concurrence,
> prior to publication and implementation. J-BOSC implements
> modifications to system configuration, responds to daily operational
> troubles and documents all associated activity. Their responsibilities
> also include maintaining and updating ESS system drawings and keeping
> the Government fully informed of major security activities.

301.5 [INTRUSION DETECTION SYSTEMS]{.underline}

> a\. [Requirements for Interior and Exterior Intrusion Detection
> Systems]{.underline}
>
> \(1\) [Equipment Enclosure]{.underline}. All electronic equipment
> enclosures used for Intrusion Detection Applications shall be
> protected against tampering by being equipped with tamper switches or
> triggering mechanisms electrically compatible with the alarm system.
> Internal wiring of equipment shall be such that the tamper switches
> and triggering mechanisms are not bypassed even though the detector
> itself is operating in the \"Access\" mode. All controls which affect
> the sensitivity of the units shall be located inside the
> tamper-resistant enclosure.
>
> \(2\) [Environmental Requirements]{.underline}. All units shall be
> designed or selected for the temperature range and highest relative
> humidity ambient to the unit\'s intended location.
>
> \(3\) [Dependability]{.underline}. The sensitivity and stability of
> all detectors shall be designed to withstand neutralization or
> compromise. All systems shall be designed to provide a probability of
> detection of 0.9 or better with a confidence level of 95 percent.
>
> \(4\) [Electronic Components.]{.underline} To the extent practicable,
> all electronic components shall be state of the art and be solid state
> type.
>
> \(5\) [Detectors/Sensors.]{.underline} All detectors and/or sensors
> shall initiate a signal under any of the following conditions: (1)
> When sensing a stimulus or condition for which it was designed to
> react; (2) if primary power fails; (3) If the detector\'s circuitry is
> opened, shorted, or grounded if such condition is capable of
> compromising the device\'s normal operation; or (4) If a tamper switch
> or triggering mechanism is activated. To the extent feasible, the
> device shall be designed to initiate an alarm if any part or component
> fails or ages to the extent to render the detector ineffective.
> Terminals shall be located within the detector enclosure and readily
> accessible to permit wiring for required combinations of detector
> units. All controls and terminals which are not required for operation
> of the detector shall not be readily accessible.
>
> \(6\) [Alarm Monitoring Equipment]{.underline}. The alarm monitoring
> equipment shall have an access/secure and alarm reset functions. An
> alarm shall create a lock-on condition which shall require manual
> restoration, and controls shall be provided to reset the system. When
> a detector circuit is conditioned for authorized entry into the
> protected area (Access Mode), the alarm monitoring equipment shall
> continue to indicate alarms if circuit supervisory limits are exceeded
> or if any tamper switches are disturbed.
>
> \(7\) [Recording.]{.underline} The alarm monitoring equipment for each
> system shall have recording capability. The minimum information to be
> provided for recording shall be: (1) Zone identification; (2)
> Intrusion; (3) Tamper; (4) Power fail/low battery; (5) Date; and (6)
> Time.

8.  [Circuit Supervisory/Units.]{.underline} The circuit supervisors
    shall provide security to the communication link between the
    detectors and/or sensors and the alarm monitoring equipment. Circuit
    supervision shall be required in wired and wireless systems.
    Supervision in a wireless system may be achieved either in a
    full-duplex active mode, or half-duplex timed and coded mode.

> b\. [Interior Intrusion Detection]{.underline}.
>
> \(1\) [Detectors]{.underline}. Detectors shall be Underwriters
> Laboratory listed and shall be one of the following types:
>
> I - Balanced Magnetic Switch
>
> II - Passive Infrared Detector
>
> III - Vibration Detector
>
> IV - Capacitance Detector
>
> V - Ultrasonic Motion Detector
>
> VI - Microwave Motion Detector
>
> VIII - Closed Circuit Television Motion Detector
>
> IX - Conductive Foil
>
> X - Breakwire
>
> XI - Dual Technology
>
> XII - Photoelectric
>
> XIII - Fiber Optic
>
> XIV - Glass Break Detector
>
> \(2\) [Balanced Magnetic Switches (Type I).]{.underline} The switch
> mechanism shall be of the balanced magnetic type and shall initiate an
> alarm upon increase, decrease, or attempted substitution of an
> external magnetic field. The switch and magnet shall be enclosed in
> separate housings of cast, nonferrous durable material and provide
> reasonable protection against moisture and dust. The mechanism shall
> be adjustable from 1/4 inch to 1 inch to accommodate installation
> variances. The switch shall be electrically protected so that a sudden
> surge of voltage greater than required for normal operations will
> create and alarm. The switch shall be designed so an alarm is
> initiated whenever the switch housing is moved more than one inch from
> the magnet housing. When simulating a closed position, the switch
> shall be rated for a minimum of 500,000 activations without
> malfunction.
>
> \(3\) [Passive IR Detector (Type II)]{.underline}. This detector shall
> initiate an alarm when a temperature differential between target and
> background of 2 degrees Celsius or greater occurs within the field of
> view. The sensor shall detect a person, 5 feet tall weighing 70
> pounds, walking at the rate 0.5 to 10 feet per second (FPS) out to a
> range of at least 30 feet. The system shall stabilize within 2 minutes
> after being turned on and shall not be capable of being defeated by
> the use of portable IR absorbent or reflective material placed between
> the sensor and a person moving in the protected area. The system shall
> not generate a false alarm as a result of changes in temperature
> caused by heating, ventilating or air conditioning equipment
> operation.
>
> \(4\) [Vibration Detector (Type III)]{.underline}. This detector shall
> consist of piezoelectric pickup devices, or an equivalent device,
> connected through an amplifier/accumulator designed to initiate an
> alarm signal in response to structurally borne vibration caused by
> explosion, a short series of blows, a longer series of lighter blows,
> or similar phenomena. The amplifier/accumulator shall integrate the
> input stimuli with respect to time, up to the preset alarm level. In
> addition, the amplifier/accumulator shall be so designed that stimuli
> of insufficient magnitude to initiate an alarm are bled off to the
> normal quiescent level at a rate of decay from the level immediately
> below alarm to 10% to 15% of alarm level in not less than 5, or more
> than 15, minutes.
>
> \(5\) [Capacitance Detector (Type IV)]{.underline}. This detector
> shall consist of a control unit containing circuitry designed to
> detect a change in the capacitive coupling which exists between one or
> more antennas and ground. Antennas shall be energized to create an
> electrostatic or electromagnetic field, so that if the protected
> object is touched by a person wearing a heavy glove or approached
> within 6 inches by a conductive mass of the density and size of a
> human 5 feet tall, weighing 70 pounds or larger, the capacitive
> coupling between antennas and ground will be initiated. The detector
> shall be designed to disconnect antennas when the detector is in the
> \"access\" mode and will create an alarm when the detector is placed
> in the \"secure\" mode.
>
> \(6\) [Ultrasonic Motion Detector (Type V)]{.underline}. This detector
> shall consist of one or more transmitter/receiver elements and the
> necessary control circuitry. The detector shall sense disturbances in
> a field (minimum height of field: 8 feet) of acoustic energy above a
> frequency of 18 KHz. Movement of a human, 5 feet tall, weighing 70
> pounds or larger, within the protected area for a distance of 3 feet
> or more at any velocity between 0.5 fps and 10 fps, shall cause the
> control unit to initiate an alarm signal.
>
> \(7\) [Microwave Motion Detector (Type VI)]{.underline}. This detector
> shall consist of transmitter/receiver elements and necessary control
> circuitry to saturate the protected area with electromagnetic energy.
> Movement of a human 5 feet tall, weighing 70 pounds or larger, within
> the protected area for a distance of 3 feet or more at any velocity
> between 0.5 fps and 10 fps, shall cause the detector to initiate an
> alarm signal. The microwave detectors shall be designed so that
> nuisance alarms due to electromagnetic emission of other equipment
> such as fluorescent lights or motors are prevented.
>
> \(8\) [Pressure Mat Detector (Type VII).]{.underline} This detector
> shall be in the form of a flat mat and shall initiate an alarm when a
> weight of 70 pounds or more is applied to any 3 square-inch top
> surface of the mat. Detectors shall be resistant to water and dust and
> the wiring circuitry shall be capable of supervision. The detector
> shall be rated to withstand no less than 500,000 activations without
> failure.
>
> \(9\) [Video Motion Detector (Type VIII).]{.underline} This detector
> shall detect the presence of an intruder by electronically comparing
> successive scenes for difference in images. An alarm shall be
> initiated when the compared images differ by more than 6.5%. The
> detector shall be capable of desensitizing portions of the viewed
> areas where naturally moving objects occur. Comparison of present
> video information with previous information shall occur at least twice
> per second. Failure of the camera shall produce an alarm independent
> of any detectable scene difference occurring in the secure area. The
> video motion processor shall be designed to operate with cameras which
> automatically compensate for scene illumination.
>
> \(10\) [Conductive Foil (Type IX)]{.underline}. This material is
> intended for application to glass and other surfaces to detect
> intrusion. It is installed and connected into an electrically
> supervised detector circuit. Breaking or grounding the foil shall
> cause an alarm to be initiated. Foil shall not exceed 1.2 pounds in
> tensile strength and shall be capable of carrying a maximum electrical
> current of 60 milli-amperes at 60 volts with a temperature rise of not
> more than 1 degree Celsius. Adhesive and protective coating material
> necessary for application shall be provided with the foil and shall be
> of types resistant to aging, moisture, and temperature change. Foil
> for glass shall be not more than 1/2-inch wide. Foil for other
> purposes shall be not more than 1-inch wide.
>
> \(11\) [Breakwire (Type X)]{.underline}. This wire is intended to be
> used in fabricating screens and grids, open wiring, and grooved
> striping in various configurations to detect penetrations through
> movable openings, floors, walls, ceilings, and skylights. When
> correctly arranged, properly installed, and connected into an
> electrically supervised detector circuit, cutting, breaking, or
> grounding the breakwire shall initiate an alarm. Hard drawn breakwire
> used in fabricating security screens shall not exceed 4.0 pounds
> tensile strength and shall be able to carry a current of 60 milli-amps
> at 60 volts with a temperature rise of not more than 1 degree Celsius.
> Wire shall not be larger than 24 AWG.
>
> \(12\) [Dual Technology (Type XI)]{.underline}. Dual technology
> sensors may be any mixture of passive infrared, ultrasonic and
> microwave elements. Which ever mixture is used, each element must meet
> the appropriate standards for that technology individually. The dual
> technology unit must also electronically combine the outputs of the
> individual elements to minimize false alarms. Each element must be
> capable of independent testing, zone alignment and verification. The
> unit must provide independent element failure status indication.
>
> \(13\) [Photoelectric (Type XII)]{.underline}. These sensors shall be
> multibeam modulated type consisting of a minimum of two transmitters
> and two receivers per set. A photo electric system shall be capable of
> detecting an individual 5 feet tall, weighing a minimum of 70 pounds
> passing between the transmitters and receivers at a rate up to 30 feet
> per second, whether walking, running, jumping, crawling, or rolling.
> Furthermore, the sensors shall be able to operate as above with an
> excess gain factor of 20.
>
> Photoelectric sensors shall be installed so that, at any point, the
> lowest beam is no higher than 9 inches above grade, and the highest at
> least 63 inches above ground. Sufficient overlap of beams shall exist
> such that an individual cannot intrude between the beams and remain
> undetected.
>
> c\. [Exterior Intrusion Detection]{.underline}.
>
> \(1\) [Systems.]{.underline} Systems used for exterior intrusion
> detection shall be Underwriters Laboratory listed and be one of the
> following listed types. Any system/sensor rated for exterior intrusion
> detection may be used for interior service, where applicable.
>
> I - Mechanical Fence Sensor
>
> II - Electromechanical Fence Sensor
>
> III - Strain Sensitive Cable
>
> IV - Magnetic Point Sensor
>
> V - Magnetic Buried Line Sensor
>
> VI - Seismic Buried Line Sensor
>
> VII - Photoelectric Detector
>
> VIII - Microwave Detector
>
> IX - E-Field Detector
>
> X - Video Motion Detector
>
> XI - Passive Infrared Detector
>
> XII - Fiber Optic Sensor
>
> \(2\) [Mechanical Fence Sensors (Type I)]{.underline}. This system
> shall initiate an alarm upon movement of the fence. All sensors in
> this system shall house adjustable sensitivity mechanical switches
> with normally opened or closed contacts as specified. The sensors
> shall be mounted on the fence posts at a maximum of 20 feet apart or
> every fence post for high security applications. If the sensors are
> mounted on the fence fabric, they shall be placed at a maximum of 10
> feet apart. This system shall employ some count and time criteria in
> the signal processor to differentiate between intrusions and nuisance
> indications.
>
> \(3\) [Electromechanical Fence Sensors (Type II)]{.underline}. This
> system shall be capable of initiating an alarm when the sensor is
> acted upon by accelerations generated in the fence fabric during
> penetration. Transducers shall be placed on every fence post or on the
> fence fabric between posts. Each transducer shall be connected in
> series along the fence with a common cable to form a single zone of
> protection. The maximum single detection zone shall not exceed 300
> feet. The cable shall be routed in sealed conduit and the transducers
> shall be installed in electrical enclosures. If the cable is installed
> underground, it shall be either routed in conduit or be direct burial
> cable.
>
> \(4\) [Strain Sensitive Cables (Type III)]{.underline}. This system
> shall be capable of initiating an alarm when the duration of a series
> of impulses is exceeded. (This is determined by the sensitivity
> setting.) Movement of the cable will produce an output voltage when
> the cable is moved. Cables shall be fastened directly to the fence
> using wire ties so movement of the fence fabric is coupled directly to
> the transducer cable.
>
> \(5\) [Magnetic Point Sensors (Type V).]{.underline} This system shall
> be capable of detecting an individual weighing more than 70 pounds
> crossing the sensitive area of the system at a minimum speed of 0.5
> feet per second, whether walking, crawling, or rolling. The system
> design shall employ techniques (e.g., electronic signal processing) to
> eliminate nuisance alarms from adverse environmental phenomena. The
> sensors shall be installed at a depth below the ground surface stated
> by the manufacturer. The sensors shall be in two separate parallel
> lines at a distance of 5 to 6-1/2 feet apart. The sensors and
> electronic circuitry buried in the ground shall be a durable,
> moisture-proof, rodent-resistant material.
>
> \(6\) [Magnetic Buried Line Sensors (Type VII)]{.underline}. This
> system shall be able to detect a 14-ounce ferrous material rod moving
> at a rate of 0.2 feet per second within a radius of 1 foot of a sensor
> cable. The detection system shall be equipped with inhibitor coils to
> minimize nuisance alarms due to electromagnetic interference. No more
> than six sensing loops per inhibitor coil shall be used in order to
> prevent simultaneous desensitizing of the entire system.
>
> \(a\) The sensing loops of a electrical cable shall be buried in the
> ground according to the manufacturer\'s stated depth. Multiple units
> (cable and amplifier) shall be used to protect a perimeter. All
> associated buried circuitry shall be buried within the protected zone
> and packaged in hermetically sealed containers. The cable shall be
> laid in accordance with the manufacturer\'s recommended geometrical
> configurations to reduce nuisance alarms from external sources. When
> cable is being installed in rocky soil, care shall be taken to remove
> sharp rocks during backfilling over the cable. Inhibitors shall be
> buried in the ground at least 20 feet from the cable inside the
> protected perimeter.
>
> \(b\) Continuous electromagnetic interference obstructs the detection
> of an intruder carrying metal over the buried cable by keeping the
> inhibitor activated, thereby preventing the alarm unit from responding
> to a change in flux caused by the intruder. The device shall therefore
> be used only where the environment is relatively free of severe
> manmade electromagnetic interference (e.g., overhead power cables,
> pole-mounted transformers, generators). The cable shall never be
> installed close to overhead power transmission lines. Moreover, the
> cable shall be placed at least 15 feet from parallel running metal
> fences, and at least 60 feet from public roads to minimize nuisance
> alarms.
>
> \(7\) [Seismic Buried Line Sensors (Type VIII)]{.underline}. This
> passive system that includes piezoelectric, pressure, geophone sensors
> or their equivalent. This system shall be capable of detecting an
> individual weighing more than 70 pounds crossing the sensitive area of
> the system at a minimum speed of 0.5 ft. per second, whether walking,
> crawling, or rolling. The system design shall employ techniques to
> eliminate nuisance alarms from adverse environmental phenomena. The
> sensors shall be installed at the depth below the ground surface
> stated by the manufacturer. Detection zones shall extend approximately
> 40 inches on each side of the buried transducers.
>
> \(8\) [Photoelectric Detector (Type IX).]{.underline} This system
> shall be a multibeam modulated type consisting of a minimum of three
> transmitters and three receivers per set. A photoelectric system shall
> be capable of detecting an individual weighing a minimum of 70 pounds
> passing between the transmitters and receivers at any velocity up to
> 30 feet per second, whether walking, running, jumping, crawling, or
> rolling, or detecting a vehicle 15 feet long traveling 60 mph.
> Furthermore, the systems shall be able to operate as above with an
> excess gain factor of 20 to compensate for loss due to atmospheric
> attenuation at maximum range.
>
> \(a\) A photoelectric system shall be installed so that, at any point,
> the lowest beam is no higher than 9 inches above grade and the highest
> beam at least 63 inches above ground. Sufficient overlap of beams
> shall exist such that an individual cannot intrude between the beams
> and remain undetected. The ground areas between the beams must be a
> constant grade and free of vegetation which could block the beam. A
> barrier to prevent tunneling under the lower beam is required to a
> depth of at least 6 inches below grade. This may be accomplished by
> using concrete, asphalt, or a similar material in a path at least 40
> inches wide and 6 inches deep or alternatively 6 inches wide and 40
> inches deep between the posts.
>
> \(b\) It is recommended that the photoelectric system be installed
> inside the physical perimeter barrier with the transmitter and
> receiver units positioned a minimum of 10 feet from the barrier to
> prevent intruders from jumping over the beams from the top of the
> fence into the protected area.
>
> \(9\) [Microwave Detector (Type X)]{.underline}. This system shall be
> capable of detecting an intruder weighing a minimum of 70 pounds
> passing between the transmitter and receiver at a rate between 0.5 and
> 15 feet per second, whether walking, running, jumping, crawling, or
> rolling. The beam shall be modulated and the receiver shall be
> frequently selective to decrease susceptibility to receiver
> \"capture.\"
>
> \(a\) The transmitter and receiver shall be installed on even terrain
> clear of trees, tall grass, and bushes. Each unit shall be mounted
> rigidly at a distance of about 40 inches above the ground. Because of
> variances in the antenna pattern of different microwave systems, this
> height may have to be varied slightly in order to obtain proper ground
> coverage. The distance between a transmitter and its receiver shall be
> in accordance with the manufacturer\'s specifications and
> site-specific requirements. Neither the transmitter nor the receiver
> shall be mounted on a fence. To prevent passage under the microwave
> beam in the shadow of an obstruction, hills shall be leveled, ditches
> filled, and obstructions removed so that the area between transmitter
> and receiver is clear of obstructions and free of rises or depressions
> of a height or depth greater than 6 inches. The clear areas shall be
> sufficiently wide to preclude generation of alarms by objects moving
> near the microwave link (e.g., personnel walking or vehicular
> traffic). Approximate dimensions of the microwave pattern shall be
> provided by the manufacturer.
>
> \(b\) If the microwave link is installed inside and roughly parallel
> to a perimeter fence or wall, the transmitter and receiver shall be
> positioned to prevent an intruder from jumping over the microwave beam
> into the protected area from atop the fence or wall. Typically, a
> chain link security fence with an overall height of 8 feet will
> require a minimum of 7 feet between the fence and the center of the
> microwave beam.
>
> \(c\) Provisions shall be made for adjusting the sensitivity to
> intruder motion, range, or both, to cover areas of various sizes and
> configurations.
>
> \(10\) [E-Field Detector (Type XI)]{.underline}. This sensor shall
> initiate an alarm with an individual weighing a minimum of 70 pounds
> and at least 20 inches from the sensing wire, whether crawling or
> rolling under the lower sensing wire, stepping and jumping between the
> field and sensing wires, or jumping over the top sensing wire of the
> system. The field and sensing wires should be supervised to prevent
> the undetected cutting or bypassing of the system. The system design
> shall employ techniques to minimize alarms caused by high winds,
> thunderstorm related electrical phenomena, high winds, and small
> animals.
>
> \(11\) [Video Motion Detector (Type XII)]{.underline}. This system
> shall detect the presence of an intruder by electronically comparing
> successive scenes for difference in images. An alarm shall be
> initiated when the compared images differ by more than 6.5 percent.
> The detector shall be capable of desensitizing portions of the viewed
> areas where naturally moving objects occur. Comparison of present
> video information with previous information shall occur at least twice
> per second to prevent high speed, undetected, pass through. Failure of
> the camera shall produce an alarm independent of any scene differences
> occurring in the secure area. The video motion processor shall be
> designed to operate with cameras which automatically compensate for
> scene illumination.
>
> \(12\) [Passive IR Detector (Type XIII).]{.underline} This detector
> shall initiate an alarm when a temperature differential between target
> and background of 2 degrees Celsius or greater occurs within the field
> of view. The sensor shall detect a person, 5 feet tall, weighing 70
> pounds, walking at the rate of 0.5 to 10 feet per second, out to a
> range of at least 50 feet. The system shall stabilize within 2 minutes
> after being turned on and shall not be capable of being defeated by
> the use of portable IR absorbent or reflective material placed between
> the sensor and a person moving in the protected area.
>
> \(13\) [Fiber Optic Sensor (Type XIV)]{.underline}. Laser Powered
> systems which use inteferometric sensing to disturbance of buried or
> non buried fiber optic sensing cable in order to detect intrusion
> within a zone of protection. Individual zones shall be determined by
> the object or area being protected. The system shall detect a person
> weighing 70 pounds or more passing through the sensitive area at
> speeds 0.5 feet per second or greater, whether walking, crawling,
> running or rolling. The system shall employ techniques which eliminate
> false alarms which are due to environmental phenomena and seismic
> vibrations from nearby vehicles or other sources. The system shall
> contain self-diagnostic reporting circuitry. The sensing fiber shall
> withstand normal vehicular drive over without damage or degradation of
> performance, whether used in clear zone applications or tactical
> deployment scenarios. When applied to fences, the fiber optic sensor
> shall detect a person attempting to climb out, or lift the fence
> fabric.

301.6 [CLOSED CIRCUIT TELEVISION (CCTV)]{.underline}

> a\. Unless specially warranted, CCTV systems should be monochrome.
>
> b\. CCTV components will be supervised and designed to resist or
> report tampering.
>
> c\. When appropriate and cost effective, CCTV should incorporate pan,
> tilt and zoom features to improve the security monitoring
> capabilities.
>
> d\. Appropriate illumination will be provided for the area under CCTV
> observation. This requires an examination of the CCTV system
> parameters and of the operational requirements.
>
> e\. Cameras will be installed to have an unobstructed view of the area
> under observation.
>
> f\. Topographic and environmental factors will be considered in
> designing CCTV systems.
>
> g\. In low light areas, where additional lighting is inappropriate or
> prohibited, special low light level cameras must be used.
>
> h\. When stipulated, CCTV should be recorded on a video cassette
> recorder (VCR).

301.7 [ACCESS CONTROL SYSTEMS (ACS)]{.underline}

a.  [Types]{.underline}: There are generally three types of access
    control systems: (1) manual, (2) machine-aided manual, and (3)
    automated. Although there can be a wide variation in technical
    complexity and cost, an equal level of security can be provided by
    each of these systems. The type of system used depends on a number
    of factors, such as:

> \(1\) Number of personnel requiring access.
>
> \(2\) Frequency of access.
>
> \(3\) Type of facility (research, development, production, or
> operations).
>
> \(4\) Classification of facility (critical, essential, support).
>
> \(5\) Types of additional safeguard measures utilized.
>
> \(6\) Compatibility with existing KSC-wide systems.
>
> \(7\) Operations and maintenance requirements.
>
> b\. Since these factors are site-specific considerations, no single
> system can be recommended for universal use. A system which is well
> suited for one facility may be totally unsuited for use at another or
> incompatible with existing Centerwide systems. An examination of all
> factors must be made before determination of the type of access
> controls best suited to a facility.

301.8 [SYSTEM UPGRADE]{.underline}

> Where existing systems do not meet the revised standards, there is no
> requirement or funding authorized to upgrade the systems solely to
> meet the new standards.

**CHAPTER 302**

**COMMUNICATION SECURITY**

302.1 [GENERAL]{.underline}

> This chapter establishes the responsibilities and provides guidelines
> for implementation of a comprehensive Communication Security (COMSEC)
> Program at KSC.

302.2 [RESPONSIBILITIES]{.underline}

> a\. The NASA/KSC COMSEC Officer is responsible for:
>
> \(1\) Managing development, implementation, and execution of the KSC
> COMSEC Program to include COMSEC configuration control.
>
> \(2\) Establishing all requirements for secure communications systems
> including Data Encryption Standard (DES) requirements and Public Key
> Cryptography (PKC).
>
> \(3\) Providing management oversight of the KSC STU-III system to
> include evaluating all requests for installation, periodic inspection
> and inventory of STU-III terminals to ensure that security
> requirements are being met. Function as STU-III user representative
> for KSC.
>
> \(4\) Requisitioning materials and establishing methods for design,
> test, inspection and evaluation of secure communications systems.
>
> \(5\) Approving all cryptographic systems (encryption devices,
> decryption devices, and keying material) including DES and PKC
> equipment and keying materials, prior to system installation and
> activation.
>
> \(6\) Ensuring compliance with this chapter\'s requirements as
> follows:
>
> \(a\) Review and approve Tier I/II and review Tier III/IV security
> plans, OMI\'s, and other documentation which covers installation and
> operation of secure communications systems prior to implementation of
> such systems.
>
> \(b\) Conduct scheduled and unscheduled inspections of secure
> communications systems, facilities, and areas where classified
> information is processed.
>
> \(c\) Appoint the NASA/KSC COMSEC Account Manager (CAM) and
> alternate(s).
>
> \(d\) Evaluate each secure communications system to ensure that COMSEC
> measures are correctly applied and to ensure that COMSEC plans,
> procedures, and operations are integrated with the KSC Security
> Program.
>
> \(e\) Review requests for waiver or exception to provisions of this
> chapter and submit them, with recommended course of action, to the
> Installation Security Officer.
>
> \(f\) Act as the interface between NASA/KSC, the NASA Central Office
> of Record (COR), the National Security Agency (NSA), and other
> Government departments and agencies for obtaining technical direction
> and guidance on all COMSEC matters, including procurement of COMSEC
> equipment and keying material.
>
> \(7\) Functioning as the Chairperson of the KSC COMSEC Requirements
> Group (KCRG); preparing and promulgating a KCRG charter; and
> coordinating appointment of other permanent KCRG members.
>
> \(8\) Overseeing all contractor COMSEC accounts under purview of KSC;
> conducting periodic inspections to ensure Government regulations are
> being complied with; and maintaining a master inventory of all COMSEC
> account holdings.
>
> \(9\) Appointing a cryptonet controlling authority, in writing, for
> each cryptonet under KSC purview.
>
> \(10\) Administering a COMSEC training program at KSC.
>
> b\. The NASA/KSC COMSEC Account Manager and Alternate(s) are
> responsible for:
>
> \(1\) Receiving, storing, shipping, and accounting for all COMSEC
> material issued to the NASA/KSC account, and maintaining accurate
> records of these transactions.
>
> \(2\) Preparing and submitting COMSEC Material Reports as required.
>
> \(3\) Conducting all required COMSEC inventories.
>
> \(4\) Ensuring that amendments, corrections, and changes to COMSEC
> publications are entered correctly without undue delay.
>
> \(5\) Ensuring that COMSEC material is available to properly cleared
> individuals who have a valid need to know. A record of material issued
> from the KSC COMSEC account shall be maintained.
>
> \(6\) Administering COMSEC briefings to individuals whose duties
> require access to COMSEC materials and maintaining associated records.
>
> \(7\) Performing routine destruction of superseded COMSEC material.
>
> \(8\) Reporting any known or suspected COMSEC insecurity as required
> by applicable directives.
>
> \(9\) Performing other COMSEC accounting duties as outlined in NHB
> 1600.6, and as directed by the NASA Central Office of Record.
>
> c\. Heads of Primary Organizations are responsible for:
>
> \(1\) Ensuring that secure communications systems are approved by the
> NASA KSC COMSEC Officer prior to commencing classified or unclassified
> sensitive operations.
>
> \(2\) Ensuring compliance with all security requirements, standards,
> and procedures applicable to secure communications systems; and
> ensuring that only COMSEC materials distributed through the COMSEC
> Material Control System, or as approved by the NASA KSC COMSEC
> Officer, are used.
>
> \(3\) Appointing a COMSEC representative who is appropriately cleared
> and briefed.
>
> \(a\) Ensuring that each COMSEC representative performs his or her
> duties effectively in accordance with applicable requirements and
> standards.
>
> \(b\) Ensuring that each COMSEC representative has written
> authorization to suspend COMSEC support or service to any user not
> adhering to security regulations and procedures.
>
> \(4\) Preparing and submitting cryptographic system requirements,
> security plans, operating procedures, and other secure communications
> system documentation to the NASA/KSC COMSEC Officer for review.
>
> **[Note:]{.underline}** Care must be taken to forecast cryptographic
> system requirements well in advance of the need date. COMSEC
> equipment, unlike other types of hardware, is produced and procured to
> match actual requirements, and is not bench stocked. The contracting
> and manufacturing process normally takes approximately 2 years from
> the date of funding. The length of this acquisition cycle shows the
> importance of forecasting COMSEC equipment requirements as early and
> as accurately as possible.
>
> \(5\) Providing technical assistance or resources to assist the
> NASA/KSC COMSEC Officer in managing the KSC COMSEC Program.
>
> \(6\) Ensuring that security requirements are considered from the
> conceptual stage for all new facilities, systems, and applications
> through which classified or sensitive information is to be processed.
>
> \(7\) Ensuring that the NASA/KSC COMSEC Officer\'s involvement and
> concurrence is obtained from the conceptual stage for all COMSEC
> systems.
>
> d\. COMSEC Representatives are responsible for:
>
> \(1\) Serving as focal points for all COMSEC matters within a
> particular facility, activity, or organization.
>
> \(2\) Preparing COMSEC plans, procedures, OMI\'s, and other
> documentation for installation and operation of secure communications
> facilities under their purview.
>
> \(3\) Conducting periodic inspection of communications facilities to
> ensure compliance with the requirements of this chapter and other
> applicable directives.
>
> \(4\) Preparing requests for waiver or exception to provisions of this
> chapter and submitting them to the NASA/KSC COMSEC Officer.
>
> \(5\) Assisting the COMSEC Officer, as required, in administering a
> COMSEC training program.

302.3 [OBJECTIVES]{.underline}

> a\. [National Policy]{.underline}. The National Communications
> Security Committee (NCSC) established broad policies for protection of
> national security information processed by communications systems. The
> Director, NSA, is the Federal Government\'s Executive Agent for
> COMSEC, and has published a series of documents designed to implement
> national policies. The objective of the U.S. COMSEC effort is
> effective and efficient application of security measures to all
> communications of the U.S. Government.
>
> b\. [STU-III Technology]{.underline}. The Federal Government has long
> recognized the most severe threat to the security of classified and
> sensitive information is our telecommunications habits and practices.
> Substantial amounts of classified and sensitive information are
> leaking to our adversaries over nonsecure telecommunications
> (telephone) circuits. The STU-III provides a low-cost, user-friendly
> system to protect both classified and sensitive unclassified
> Government information. KSC fully supports National policy, which
> encourages the widespread implementation and use of the STU-III.
>
> c\. [KSC Objectives]{.underline}. KSC shall support the national
> COMSEC effort through adherence to national policies and NSA doctrine.

302.4 [COMSEC PROGRAM]{.underline}

> There are a number of disciplines which, when combined, constitute a
> COMSEC program. The following elements and requirements constitute the
> COMSEC Program at KSC.
>
> a\. [Cryptographic Security]{.underline}. All communications networks,
> systems, and circuits (including voice, teletypewriter, data,
> telemetry, television, and facsimile) used to transmit national
> security and sensitive information will be secured with approved
> COMSEC equipment. All COMSEC equipment and keying materials, including
> DES and PKC, must be approved by the NASA/KSC COMSEC Officer prior to
> installation and use.
>
> b\. [Physical Security.]{.underline} COMSEC material requires physical
> protection over and above that provided to most other classified
> material. The loss of certain COMSEC materials could result in
> compromise of all classified or sensitive information transmitted over
> circuits protected by the material. All persons responsible for COMSEC
> material must comply with applicable physical security regulations.
>
> c\. [Transmission Security]{.underline}. Measures must be taken to
> protect transmissions from interception and exploitation, by means
> other than cryptanalysis. Examples of poor application of transmission
> security are:
>
> \(1\) A sudden activation or increase in communications activities
> just prior to an event.
>
> \(2\) Improper use of code systems or use of homemade codes.
>
> d\. [Emission Security]{.underline}. Control of compromising
> emanations (TEMPEST) is covered in detail in Chapter 303 of this
> handbook. TEMPEST is mentioned here since it is a basic element of
> COMSEC. The provisions of NSTISSAM TEMPEST 2-95 should be followed for
> facility design and equipment installation. However, due to ever
> changing Federal standards on TEMPEST guidelines, all TEMPEST
> discussions concerning equipment installation and facility design will
> include the KSC TEMPEST Officer.

302.5 [COMSEC EQUIPMENT MAINTENANCE]{.underline}

> COMSEC equipment is designed to provide security to communications.
> Maintenance of this equipment by certified technicians is accomplished
> within specified guidelines as authorized by interagency agreements,
> NSA instructions, and other applicable documents. Maintenance is
> defined as:
>
> a\. [Limited]{.underline}. Maintenance performed at KSC. Persons
> designated to perform limited maintenance must complete approved
> COMSEC maintenance training courses and be formally certified prior to
> assuming maintenance duties.
>
> b\. [Depot]{.underline}. Maintenance performed at an authorized crypto
> repair facility.

302.6 [COMSEC MATERIAL CONTROL SYSTEM]{.underline}

> COMSEC material is distributed to users through the COMSEC Material
> Control System. Only those materials distributed through the CMCC may
> be used to protect classified or unclassified sensitive information.

302.7 [EMERGENCY PLANNING AND ACTIONS]{.underline}

> All organizations conducting COMSEC operations or holding classified
> COMSEC material must consider the possibility of an emergency arising
> which would expose COMSEC materials to possible compromise. An
> emergency action plan must be made which will prevent entirely, or at
> least minimize, the extent and effect of compromise. The COMSEC
> Emergency Action Plan must be coordinated with the overall facility or
> activity emergency plan to ensure harmony of actions during
> emergencies. COMSEC Emergency Action Plans will be submitted to the
> NASA/KSC COMSEC Officer for review and approval prior to
> implementation.
>
> a\. [Emergency Action Plan.]{.underline}
>
> \(1\) When preparing an emergency action plan, there are two basic
> types of emergencies to consider: (1) accidental occurrences and (2)
> hostile action. The first includes natural disasters (such as,
> earthquake, flood, hurricane, and tornado) and manmade accidents (such
> as, explosion and fire). The second is hostile action of malcontents.
> The primary goal of an emergency action plan is to ensure that
> classified COMSEC material is safeguarded at all times through proper
> storage or through destruction.
>
> \(2\) All personnel involved with COMSEC operations must be
> indoctrinated in step-by-step emergency procedures. Routine training
> exercises should be conducted frequently (once each quarter is
> recommended) to ensure that all personnel are completely familiar with
> action to be taken during an emergency.
>
> \(3\) The emergency action plan shall designate specific facility
> management officials empowered to direct execution of the plan in an
> emergency.
>
> b\. [Notification]{.underline}. Immediately upon executing an
> emergency action plan, the person responsible shall notify the
> NASA/KSC COMSEC Officer and the CAM who issued the COMSEC material
> involved.
>
> c\. [Emergency Action]{.underline}. Plans for protecting COMSEC
> material during an emergency should include the following actions:
>
> \(1\) [Securing the material]{.underline}.
>
> \(a\) Zeroize all cryptographic equipment or remove keying material
> from equipment and store in a safe. Secure all other classified COMSEC
> material, except bulky equipment, in a safe. Lock the doors of all
> rooms or vaults containing COMSEC material, except in case of fire.
>
> \(b\) Secure all power within the COMSEC room or vault before leaving.
>
> \(c\) Post a guard in the area, if feasible.
>
> \(d\) Upon return, conduct an inventory of all COMSEC material.
> Missing material must be reported immediately to the NASA/KSC COMSEC
> Officer and the CAM who issued the material.
>
> \(e\) In the event of fire, life safety is the primary consideration.
> Every reasonable effort to properly secure all classified material,
> especially COMSEC material, should be made prior to permitting fire
> personnel to enter; however, inability to secure classified material
> must NOT preclude entry of fire personnel.
>
> \(2\) [Removing the Material]{.underline}. This course of action is
> preferred over destroying COMSEC material if time and conditions
> permit.
>
> \(3\) [Destroying the Material]{.underline}. Implements and methods
> for rapid destruction of equipment and material shall be available if
> the decision for destruction is made.
>
> d\. [Combining Actions.]{.underline} It may be desirable in certain
> situations to combine some or all actions listed above. For example,
> if it appears a civil uprising will be short lived and the COMSEC room
> is to be abandoned for a short period, superseded material may be
> destroyed, all other material removed, and the equipment made secure.
>
> e\. [Reducing COMSEC Inventory in Anticipation of an
> Emergency]{.underline}. It may be advisable to reduce the COMSEC
> inventory in anticipation of an emergency. This is accomplished by
> retaining current keying material (to ensure continued communications
> until the last moment) and destroying or relocating all other
> material. If destruction of future (reserve on board) keying material
> is directed, the issuing office must be advised so immediate
> replacement can be made after the danger has passed.

302.8 [COMSEC EVALUATIONS]{.underline}

> a\. A general inspection of each COMSEC facility and each COMSEC
> account will be conducted at least annually by the NASA/KSC COMSEC
> Officer or his/her designated representative. The inspection will
> include all aspects of COMSEC. A letter report which lists
> deficiencies requiring corrective action will be prepared and
> forwarded to the CAM and the COMSEC representative.
>
> b\. CAMs and users of COMSEC material may use the COMSEC Checklist, as
> a guide when conducting self-inspections. Self-inspections should be
> conducted periodically as an element of COMSEC account administration.
> The COMSEC Checklist, although comprehensive, is intended as a guide
> and may not include all aspects of the inspection.

302.9 [COMSEC AWARENESS]{.underline}

> a\. Each individual with access to COMSEC material must be made aware
> of the special sensitivity and handling COMSEC material requires.
> Prior to being granted access to COMSEC material, each individual must
> be fully briefed on all aspects of COMSEC sensitivity. At KSC, this is
> accomplished through a series of briefings arranged by the NASA/KSC
> COMSEC Officer and through the respective efforts of each organization
> to which this chapter applies.
>
> b\. It is not practical to identify COMSEC awareness requirements
> here. Rather, each organization will implement an awareness program
> commensurate with the COMSEC requirements under which it operates.

302.10 [COMSEC TRAINING]{.underline}

> a\. COMSEC training for all users of KSC communications systems may be
> scheduled by calling the NASA/KSC COMSEC Officer, 867-2452.
>
> b\. Maintenance training is provided for individuals working with
> COMSEC equipment. All personnel who maintain or install COMSEC
> equipment must have a current certification of training and
> proficiency. Submit written requests for formal training to the
> NASA/KSC COMSEC Officer.
>
> c\. Documentation of training will be maintained in accordance with
> applicable regulations. COMSEC training records will be a subject of
> inspection during various COMSEC evaluations.
>
> **CHAPTER 303**
>
> **TEMPEST\--CONTROL OF COMPROMISING EMANATIONS**

303.1 [GENERAL]{.underline}

> a\. This chapter provides requirements for establishing a special
> TEMPEST program for NASA and NASA contractor facilities located on KSC
> and at all other off-Center areas under the cognizance of KSC; i.e.,
> Cape Canaveral Air Force Station and Patrick Air Force Base.
>
> b\. All TEMPEST decisions covering equipment installation and facility
> design will include the KSC TEMPEST Officer.

303.2 [RESPONSIBILITIES]{.underline}

> The NASA/KSC TEMPEST Officer, a member of NASA Security, is
> responsible for:
>
> a\. Functioning as the primary point of contact on all matters
> relating to TEMPEST at KSC. This includes ensuring that the
> national-level TEMPEST policies are properly addressed and included in
> the overall TEMPEST program at KSC.
>
> b\. Coordinating KSC\'s TEMPEST efforts with appropriate U.S.
> Government agencies and with the security elements of KSC tenants,
> both Government and contractor, by participation in design reviews
> during the engineering phase of projects involving RED/BLACK
> systems/facilities/equipment.
>
> c\. Ensuring that equipment, systems, and facilities used for secure
> (RED) operations at KSC conform to the appropriate design,
> acquisition, construction, installation, modification, and/or
> relocation guidelines/criteria.
>
> d\. Determining the necessity of and arranging for all TEMPEST tests
> which involve KSC equipment, systems, and/or facilities.
>
> e\. Processing deviations to the TEMPEST standards established for
> KSC, recommending appropriate action and disposition of such
> deviations to the appropriate approval authority.
>
> [Note]{.underline}: Caution should be exercised with regard to
> deviations and waivers as they may constitute vulnerabilities and
> subsequently require classification. Coordination with the TEMPEST
> Officer prior to preparation of any documentation should result in the
> safeguarding of potentially damaging information. These subjects are
> not to be discussed telephonically unless it is done on a secure
> communications network.
>
> f\. Providing guidance and assistance to all KSC organizations on
> TEMPEST matters.
>
> g\. Investigating and making appropriate disposition of all instances
> of noncompliance with TEMPEST standards/instructions/procedures.
>
> h\. Participating in periodic examination of KSC facilities,
> equipment, systems, or components for compliance with TEMPEST
> standards.
>
> i\. Acting as the point of contact for coordination of formal TEMPEST
> training for NASA/KSC Employees and KSC contractors.

303.3 [TEMPEST]{.underline}

> a\. Compromising Emanations. Electronic and/or electromechanical
> equipment used for information processing may produce compromising
> emanations. These are defined as unintentional data-related and/or
> intelligence-bearing signals which, if intercepted and analyzed, would
> disclose classified information that is being transmitted, received,
> handled, or otherwise processed by the equipment. It has been
> established that such compromising signals can be propagated through
> space and along nearby conductors. TEMPEST is the unclassified name
> referring to investigations and studies of compromising emanations.
>
> IAW NSTISSI No. 7000, TEMPEST efforts to control compromising
> emanations must be incorporated into equipment design, facility
> construction, and system layout/installation.
>
> b\. No RED systems, equipment, or components may be placed in service
> or restored to service after repair/modification without the
> concurrence of the NASA/KSC TEMPEST officer. This is formally
> accomplished by the TEMPEST officer\'s assessment during the
> continuing security compliance/configuration management process. This
> applies to such items as:
>
> \(1\) Secure automated information processing systems.
>
> \(2\) Electric typewriters, word processors, and audio/video
> recording/playback devices used for RED processing and/or
> presentations.
>
> \(3\) Secure telephone, teleconference, communications equipment (such
> as, headsets and microphones), and facsimile systems used for RED
> processing.
>
> \(4\) Cryptographic systems and related equipment/components.
>
> c\. Once approved for secure (RED) processing, all
> systems/equipment/components must be properly protected/controlled to
> assure that security integrity is maintained. Access to controlled
> space containing RED processors will be strictly controlled. Access
> to, and work performed upon, RED systems equipment or components will
> be limited to cleared personnel having a valid need for such access.
> Modification, reconfiguration, or moving of any previously approved
> RED equipment will be handled with the NASA/KSC TEMPEST Officer\'s
> signature/concurrence.
>
> d\. Certain secure telephone systems, such as the Secure Telephone
> Unit, (STU-III), are capable of operation in both BLACK and RED modes.
> The following requirements apply to STU-III installations at KSC:
>
> \(1\) Only STU-III terminals meeting NSTISSAM TEMPEST 1-91
> requirements are approved for installation at KSC. Units for use on
> KSC will be authorized and controlled through the KSC COMSEC Officer.
>
> \(2\) STU-III terminals are connected to standard telephone lines.
> There are no requirements for conduit or other special materials for
> RED/BLACK separation.

**CHAPTER 304**

**TECHNICAL SURVEILLANCE COUNTERMEASURES**

304.1 [GENERAL]{.underline}

> a\. The primary objective of the Technical Surveillance
> Countermeasures (TSCM) program at KSC is to locate and neutralize
> technical surveillance devices that have been targeted against KSC
> facilities/interests. The secondary objective is to identify and
> enable the correction of vulnerabilities. TSCM services will be used
> to accomplish these objectives.
>
> b\. The purpose of TSCM services is to provide an extra level of
> protection to established security areas likely to be targets of
> technical surveillance penetrations. These surveys augment normally
> sound security practices and are not substitutes for other proper
> measures (access controls, physical security, etc.). They are not
> compliance-oriented administrative inspections and should not be
> considered as such. They are highly specialized counterintelligence
> investigations conducted by specially trained TSCM personnel only.

304.2 [RESPONSIBILITIES]{.underline}

> The TSCM Program Manager, a member of NASA/KSC Security, is
> responsible for:
>
> a\. Conducting TSCM services at facilities under the cognizance of
> KSC.
>
> b\. Investigating the discovery of actual and suspected technical
> surveillance devices in facilities under the cognizance of KSC.
> Coordinating such investigations with DoD, FBI, and other Government
> agencies. Rendering reports, as appropriate.
>
> c\. Ensuring that areas used for sensitive discussions/presentations
> conform to adequate and appropriate technical security standards.

304.3 [REQUIREMENTS]{.underline}

> a\. Secure Discussion/Presentation Areas. The generic NASA standards
> for secure conference rooms are contained in NHB 1620.3C, Chapter 20,
> NASA Physical Security Handbook. These standards apply to all KSC
> elements, including contractors, and should be used as guidelines in
> establishing any facility that may be subject to recurring TSCM
> surveys. The TSCM Program Manager will be contacted for any
> interpretation of the NASA standards, including protective measures
> for telephones.
>
> b\. TSCM services at KSC areas or areas under the cognizance of KSC
> will be coordinated and conducted by the TSCM Program Manager only.
>
> c\. Sponsors of classified/sensitive briefings, conferences, and
> symposia must make every effort to hold these gatherings in secure
> discussion areas. However, when the number of attendees exceeds the
> capabilities of any available secure areas, a limited TSCM service may
> be provided to protect the event to the maximum extent possible.
>
> d\. Radios, two-way transceivers, pagers, beepers, recording devices,
> laptop computers, and similar electronic devices represent technical
> security vulnerabilities by inherent design characteristics. They are,
> therefore, prohibited in those areas subjected to recurring TSCM
> surveys. Exceptions may be permitted on a case-by-case basis by the
> Installation Security Officer.
>
> e\. Requests for TSCM services should be treated as
> sensitive/proprietary information and handled in a secure manner.

304.4 [PROCEDURES]{.underline}

> The following procedures are intended for the use of those individuals
> responsible for a particular building/site, program, or activity in
> which classified and/or sensitive (i.e., proprietary) information is
> or will be used.
>
> a\. Identify those areas where the following information is or will be
> routinely discussed or presented in audible or visual format:
>
> \(1\) Classified information.
>
> \(2\) Certain unclassified proprietary information; such as,
> significant procurement actions and major contractual bids,
> negotiations, and awards.
>
> b\. Request the NASA TSCM Program Manager to arrange a TSCM survey or
> monitor. Since the request will be treated as a sensitive matter, it
> may not be made over an unsecure telephone. Even if an approved secure
> telephone is available in the area to be surveyed, do not use it to
> request a TSCM survey for that area.

304.5 [DISCOVERY OF DEVICES/SUSPECT DEVICES]{.underline}

> Whenever an actual or suspected device is discovered in any KSC
> facility or facility under the cognizance of KSC, it is imperative
> that the following actions be taken:

## WARNING

> a\. Do not touch or disturb the device in any manner. Leave this to
> electronics and explosives experts. Devices can and have been booby
> trapped.
>
> b\. Do not attempt to remove it or analyze it.
>
> c\. Immediately establish physical control over the area to prevent
> the removal of the device by those who installed it and to prevent
> access by the curious.
>
> d\. Allow no verbal comments in the area that would in any way
> disclose the fact that a device has been found. This could negate any
> further efforts to identify and prosecute those responsible.
>
> e\. Immediately notify the TSCM Program Manager by secure means.

**CHAPTER 401**

**LAW ENFORCEMENT**

401.1 [GENERAL]{.underline}

> This chapter is to describe the law enforcement functions, relations,
> duties, responsibilities, and jurisdictions which are in effect at the
> KSC.

401.2 [LAW ENFORCEMENT DUTIES]{.underline}

> Nothing within this handbook shall be construed to obviate the role,
> responsibilities, and authorities of the Office of the Inspector
> General as contained in appropriate NASA Management Instructions.
>
> a\. NASA Security will:
>
> \(1\) Be the initial focal point for all matters involving law
> enforcement for KSC.
>
> \(2\) Ensure in its oversight role to the security and law enforcement
> portion of the J-BOSC that the contractor provides sufficient
> qualified officers to perform the law enforcement function on KSC.
>
> \(3\) Establish and maintain liaison with the local, State, and
> Federal law enforcement community.
>
> \(4\) Formulate mutual aid agreements, letters of understanding, or
> other obligatory instruments affecting the disposition of KSC\'s
> security assets on KSC or within the local community, and the use of
> local assets on the Center.
>
> \(5\) Develop the strategy and philosophy for protection of assets on
> KSC and for the enforcement of laws pertaining to the Center.
>
> \(6\) Develop and implement a system to deal with violations or
> noncompliance by companies not under the jurisdiction of the J-BOSC.
>
> b\. The J-BOSC will, within the limits of its contract with NASA and,
> with the approval and coordination of NASA Security:
>
> \(1\) Provide sufficient officers qualified for deputization by the
> Brevard County Sheriff\'s Office, and cooperate with the Sheriff\'s
> Office in achieving deputy status for those officers.
>
> \(2\) Provide sufficient training to designated deputized officers so
> that traffic accidents may be investigated, traffic laws may be
> enforced, and analysis for intoxicants and drug use can be conducted.
> The J-BOSC will provide appropriate procedures, training,
> certification, and equipment for this testing.
>
> \(3\) Enforce all Florida statutes and laws on KSC through a procedure
> of investigations, apprehension/arrest, and prosecution by the State
> Attorney\'s Office.
>
> \(4\) Provide training for all officers assigned law enforcement
> duties, to include basic law enforcement training, the use of force,
> application of State laws, report writing, crime scene, evidence
> handling, etc.
>
> \(5\) Develop, with the concurrence of NASA Security, procedures for
> the application of law enforcement on KSC. These should include, but
> not be limited to:
>
> \(a\) Use of force.
>
> \(b\) General firearms policy.
>
> \(c\) Reporting, handling, and documentation of incidents.
>
> \(d\) Operation and maintenance of sobriety test equipment.
>
> \(e\) Crime scene procedures.
>
> \(f\) Traffic crash investigation.
>
> \(6\) Provide appropriate administrative support for the law
> enforcement function, including the storage and retrieval of arrest
> records, accident investigations, and traffic citation records. The
> offices conducting this administrative support will conduct liaison
> with State agencies as is required by state law.
>
> c\. Directors of first-line directorates and staff offices will
> appoint, as a minimum, a security officer or security point of contact
> for law-enforcement-related issues. This person will, as a minimum:
>
> \(1\) Interface with both NASA Security and J-BOSC Security.
>
> \(2\) Ensure that the directorate/office complies with the provisions
> of all security instructions/regulations applying to KSC.
>
> \(3\) Be the point of contact to both NASA Security and J-BOSC
> Security in the processing of traffic and criminal violations or
> incidents involving his/her organization\'s employees on KSC.
>
> \(4\) Coordinate, through the NASA Security Office, the development of
> a program of progressive sanctions to be taken in the event of
> criminal violations to include, if appropriate, termination.
>
> \(5\) Coordinate, through the NASA Security Office, the development of
> a program to observe, recognize, and deal with substance abuse within
> the organization. This may include clinical treatment or other
> measures, but must be able to demonstrate an effective end to the
> abuse and it\'s effects in the workplace.
>
> \(6\) Formulate a crime prevention program for his/her respective
> organization. This program will have as its objective the
> dissemination of information that will result in the reduction of
> crime through preventive measures. This program is primarily one of
> service to the employees and should serve to aid in the prevention of
> crime, both at work and in the home.
>
> \(7\) In conjunction with NASA Security and J-BOSC Security, develop
> and implement a program designed to educate the employees in what is
> expected of them as part of the law enforcement program for KSC. This
> should include basic security philosophy and information concerning
> topics such as theft, substance abuse, and driving while under the
> influence of intoxicants.
>
> d\. KSC contractors will, within the limits of their contracts or
> subcontracts, appoint, as a minimum, a company security officer or
> security point of contact for law-enforcement-related issues. This
> person will, as a minimum:
>
> \(1\) Interface with NASA Security and J-BOSC Security.
>
> \(2\) Ensure that the company complies with the provisions of all law
> enforcement instructions and regulations applying to KSC.
>
> \(3\) Be the point of contact for both NASA Security and J-BOSC
> Security in the processing of traffic and criminal violations or
> incidents involving his/her company\'s employees on KSC.
>
> \(4\) Develop a program of progressive sanctions to be taken in the
> event of criminal violations. The company must be prepared to take
> appropriate action against an employee, up to and including
> termination.
>
> \(5\) Formulate a crime prevention program. This program will have as
> its objective the dissemination of information that will result in the
> reduction of crime through preventive measures. This program is
> primarily one of service to the employees and should serve to aid in
> the prevention of crime, both at work and in the home.
>
> \(6\) In conjunction with NASA Security and J-BOSC Security, develop
> and execute a program designed to educate the employee in what is
> expected as part of the security program for KSC. This should include
> basic security philosophy and information concerning topics; such as,
> hostile intelligence-gathering techniques and the threats posed by
> terrorists.

(7) Develop a program to observe, recognize, and deal with substance
    abuse on KSC. This may include clinical treatment or other measures,
    but must be able to demonstrate an effective end to the abuse and
    its effects in the workplace.

> e\. [Individuals.]{.underline} All individuals on, and/or affiliated
> with, the Kennedy Space Center have the responsibility to prevent
> crime by immediately reporting incidents to the NASA Security, and/or
> to J-BOSC Security. Failure to report these incidents adversely
> affects the accomplishment of the mission of KSC and the morale of its
> employees and, in some cases, can be regarded as a violation of legal
> statutes. The recommended reporting point for suspicious or
> questionable acts is to one\'s company or organization security
> office.

401.3 [JURISDICTION]{.underline}

> The Florida Deeds of Dedication gives the National Aeronautics and
> Space Administration (NASA) a proprietorial interest in KSC property.
> This authority is based primarily upon State and Federal statutes.
> Similar to other land owners in the State of Florida, NASA must rely
> upon properly deputized officers of the State or county to enforce
> State laws and upon Federal officers to enforce Federal laws. In
> agreement with the Brevard County Sheriff\'s Office, the J-BOSC will
> obtain and maintain deputization for designated officers performing
> law enforcement duties on KSC. The deputized officers are empowered as
> J-BOSC Security/KSC Reserve Deputies and are authorized to conduct all
> law enforcement activities, including arrests on KSC, within the
> limits of the Florida State Statutes (see paragraph 401.3b.(1) below).
> NASA Federal Law Enforcement Officers may, under applicable law,
> intervene in the commission of a felony and may, within the confines
> of KSC, hold suspects until a deputized officer can respond to affect
> an arrest. At present, NASA officials have the authority to utilize
> both State and Federal officers to ensure that law and order are
> maintained in order that the mission of NASA is accomplished.
>
> a\. [Federal Agencies.]{.underline} The Federal agencies listed and
> described below have jurisdiction at KSC as indicated:
>
> \(1\) [Department of the Interior]{.underline}. Congress has granted
> the Secretary of the Interior authority to use, and administrative
> authority over, all land, submerged land, and waters within the
> perimeter of KSC. National Park Service, U.S. Fish and Wildlife
> Service, and Canaveral National Seashore officials have responsibility
> to control access to the National Seashore; to construct, alter,
> operate, and maintain dikes, impoundments, and water control; and to
> enforce all rules and regulations governing the use of land and the
> protection of natural resources and wildlife. These officers enforce
> Federal statutes regarding trespass, traffic, and criminal acts. The
> National Park Service enforces the provisions of Title 36 CFR, while
> the U.S. Fish and Wildlife Service enforces those found in Title 50
> CFR. Separate agreements have been promulgated between NASA and these
> agencies concerning lines of jurisdictional responsibility, mutual
> assistance, and coordination.
>
> \(2\) [Federal Bureau of Investigation (FBI)]{.underline}. FBI agents
> enforce the United States Criminal Codes. In addition, the Bureau
> provides investigatory support to NASA in cases of espionage,
> sabotage, and theft of government property. They also are available to
> support anti or counter-terrorist situations affecting the Center.
>
> \(3\) [United States Customs Service (USCS)]{.underline}. The primary
> interface KSC has with the Customs Service is in the area of recovered
> contraband. Contraband found on the Center or on the persons of
> individuals apprehended who are believed to be transporting it
> illegally from outside the continental United States is released to
> the USCS. Individual(s) apprehended under such circumstances are
> released to the Customs Service for their disposition. Additionally,
> hardware and other equipment associated with payload operations may be
> subject to inspection and/or review by USCS at KSC and other
> facilities under KSC cognizance.
>
> \(4\) [United States Secret Service]{.underline}. The Secret
> Service\'s two main areas of responsibility are the protection of
> selected high ranking government officials (both U.S. and foreign) and
> the investigation of crimes involving counterfeiting of U.S. currency.
> In both of these areas, KSC works closely with the Service. Close
> contact with the Orlando office of the Secret Service is accomplished
> by NASA Security.
>
> \(5\) [United States Department of State]{.underline}. Officials of
> the U.S. or foreign governments on official or unofficial state visits
> to this country come under the protection of the Department of State.
> The Department of State is also called upon to provide liaison with
> foreign governments for NASA at contingency landing sites worldwide.
>
> \(6\) [U.S. Coast Guard]{.underline}. The United States Coast Guard is
> responsible for providing security support during launch and landing
> operations. This includes enforcing the off coast Security Zone
> beginning upon rollout and continuing until a \"No Return to Launch
> Site\" is declared and resuming 3 hours prior to landing until
> released after a safe landing. They also patrol island waters (the
> Banana River south of the NASA Causeway and the Mosquito Lagoon north
> of Haulover Canal) using the Coast Guard Auxiliary.
>
> \(7\) [Other Federal Agencies.]{.underline} NASA Security, is the
> single point of contact for the agencies listed above and all other
> Federal agencies in matters pertaining to crime on the Kennedy Space
> Center or property under the cognizance of KSC worldwide. KSC
> employees may deal directly with these agencies in these matters, but
> are encouraged to contact NASA Security first to ensure that proper
> documentation may be accomplished and the responsible agency for each
> case is notified.
>
> \(8\) [NASA Inspector General]{.underline}. The NASA Inspector General
> is responsible to NASA Headquarters for investigating all allegations
> of fraud, waste, and abuse on KSC as contained in NASA Management
> Instructions.
>
> b\. [The Brevard County Sheriff's Office.]{.underline} As described
> below, has stated jurisdiction over the Kennedy Space Center:
>
> \(1\) The Brevard County Sheriff is required by law to enforce Florida
> State Statutes in Brevard County, which includes most of the Kennedy
> Space Center. (A small portion of the Center is in Volusia County. The
> Volusia County Sheriff has jurisdiction in this area.) Through an
> agreement between NASA and the Sheriff, the Sheriff will deputize
> selected members of the J-BOSC Security force who meet the minimum
> standards required by the State for law enforcement officers. These
> J-BOSC Security/KSC Reserve Deputies are empowered to enforce Florida
> law on KSC. The Brevard County Sheriff\'s Office (BCSO) works closely
> with NASA Security, and the J-BOSC, in enforcing Florida State
> Criminal Statutes on the Center, investigating capitol crimes, and
> arresting wanted persons on the Center.

401.4 [NASA AND J-BOSC POINTS OF CONTACT]{.underline}

> A listing of NASA and J-BOSC Points of Contact is found in Appendix C
> of this handbook.

## CHAPTER 402

**PROTECTIVE FORCES**

402.1 [GENERAL]{.underline}

> a\. This chapter establishes standards at KSC for protective forces
> under contract to NASA. Protective forces subject to this document are
> to protect NASA employees and security interests, primarily space
> vehicles, facilities, and associated hardware, on KSC. Assets will be
> protected against theft, sabotage, and other hostile acts that may
> cause adverse impact to the U.S. space program, national security, or
> the health and safety of employees or the public.
>
> b\. A protective force consisting of armed security officers and
> support personnel is required as provided by in the J-BOSC. This force
> will protect NASA/KSC assets as provided in this document, in the NASA
> Resource Protection (NRP) Plan, and as directed by the NASA
> Contracting Officer and the Contract Manager\'s Representative (CMR).
>
> c\. As a minimum, there will exist the following elements for KSC
> security:
>
> \(1\) Personnel to provide the armed security force including Plant
> Protection, Law Enforcement, and Special Response Team (SRT) officers
> to execute security plans and procedures.
>
> \(2\) Personnel to survey and audit the KSC security posture, and
> conduct long-range security planning.
>
> \(3\) Personnel to manage the technical aspect of traffic and law
> enforcement on KSC, provide K-9 support, and conduct investigations.
>
> \(4\) Personnel to conduct administrative tasks, administer traffic
> and reserve parking programs, develop short-to-mid range plans,
> develop special operational procedures, conduct training, and
> generally support the uniformed security operations.

402.2 [MANAGEMENT OF PROTECTIVE FORCES]{.underline}

> a\. [Plans and Orders.]{.underline}
>
> \(1\) [Development]{.underline}. The protective force management will
> develop plans, orders, and procedures. Plans and orders, in
> conjunction with supporting directives, instructions, manuals, and
> procedures, will provide direction to protective force personnel in
> the conduct of their duties. Written guidance will be prepared to
> cover routine operations, foreseeable contingencies, and emergency
> situations. Plans requiring participation by other agencies or KSC
> elements will be documented and coordinated. Where possible, a
> memorandum of understanding or other signed agreements will be
> obtained. The elements of security, safety and operational expediency
> will be addressed in all plans.
>
> \(2\) [Preparation.]{.underline} Written direction to protective force
> elements will be based on contractual obligation, CMR direction, NASA
> requirements, site-specific needs, threat assessments, plans, or
> procedures. A procedure for review and revision of all plans, orders,
> Standard Operating Procedures (SOP\'s), or other written directives
> will be developed and followed.
>
> b\. [Qualifications.]{.underline}
>
> \(1\) Personnel performing as security officers must meet medical and
> job performance standards as directed by NASA. Officers are also
> required to meet training and firearms proficiency standards as set by
> NASA. All officers must be eligible for, and be granted, a Secret
> clearance. Officers will be evaluated for compliance with NASA
> standards prior to job assignment, and for job performance during the
> first 90 days of employment. Records of all training, medical
> standards, job performance standards, and job performance evaluations
> will be maintained.
>
> \(2\) Personnel performing as law enforcement officers will meet
> standards specified for security officers and other standards as
> required by NASA or the contractor. In addition, these officers will
> meet the requirements specified by the State of Florida for law
> enforcement officers and will meet any standards set by the Brevard
> County Sheriff\'s Office (BCSO). In order to qualify as a law
> enforcement officer personnel must be deputized by the BCSO.
>
> \(3\) Personnel performing as SRT officers will meet basic
> requirements for training and security clearance. In addition, they
> will meet enhanced standards specified by NASA. This will include more
> stringent health and job performance standards, increased training
> requirements, and specialized weapons qualifications.
>
> \(4\) Personnel performing as security supervisors will meet the basic
> requirements for security officers and those increased standards for
> each listed category as appropriate. Assignment to supervisory status
> is contingent on qualifications agreed upon between the contractor and
> the CMR.
>
> \(5\) Authority to Carry Firearms.
>
> \(a\) The National Aeronautics and Space Act of 1958 (42 USC 2456)
> empowers NASA to authorize the arming of contractor security
> personnel. All NASA and J-BOSC security personnel so authorized will
> have met standards for training and performance as prescribed by the
> Installation Security Officer to include certification in the NASA
> Federal Law Enforcement Program. Each officer upon receiving the
> authority to carry firearms, and while doing so during the performance
> of duties, will carry a Certificate of Authority to Carry (Unconcealed
> or Concealed) Firearms. This certificate will state the individual\'s
> name, nature and location of duties, date of issue, date of
> expiration, and the signature of the Installation Security
> Officer/Chief, Protective Services Branch.

b.  Appropriate NASA forms will be prepared for personnel authorized to
    carry firearms. Copies of these forms will be retained by the
    certifying official and issued to the authorized bearer.

> c\. [Allocation of Personnel Resources.]{.underline}
>
> \(1\) [Location, Manning, and Scheduling.]{.underline} The location
> and manning of fixed and mobile posts will be determined by the NASA
> Security Office after it considers the approved threat level,
> characteristics of the assets to be protected, terrain, and
> environment. Work schedules for protective force personnel will be
> developed by the contractor based on contract obligations and current
> conditions to provide the maximum efficiency in the use of human
> resources for the protection of KSC assets.
>
> \(2\) [Law Enforcement Officers.]{.underline} A contingent of
> qualified and certified law-enforcement officers will be provided as
> required by contract in order to enforce the laws of the State of
> Florida and to investigate traffic accidents, as well as to support
> the security mission.
>
> \(3\) [Special Response Team.]{.underline} A contingent of SRT
> officers will be provided as required by contract in order to provide
> response and neutralization capabilities.
>
> \(4\) [Supervision.]{.underline} Supervision of protective personnel
> will be provided, as required, to ensure proper and adequate
> performance of duties.
>
> \(5\) [Manpower Baseline.]{.underline} A Manpower Baseline will be
> provided to the Lead, NASA, on a semi-annual basis. This document will
> detail available staffing and the disposition of forces. J-BOSC
> protective forces headcount will be determined by current budget
> limitations.
>
> 402.3 [PROTECTIVE FORCES DUTIES]{.underline}
>
> a\. [Officers]{.underline}. Patrol officers will perform duties, as
> required by KSC and the security contractor. These will include, but
> are not limited to, the following:
>
> \(1\) [Access Control]{.underline}. Officers will control access to
> the facility and designated areas throughout KSC according to criteria
> established by NASA.
>
> \(2\) [Mobile Patrol]{.underline}. Officers will patrol designated
> areas of KSC in order to observe activity and to respond to
> emergencies.
>
> \(3\) [Emergency Response]{.underline}. All officers, but particularly
> law enforcement and SRT officers, will respond to emergencies as
> required to effectively neutralize any threats or hazards, or to make
> appropriate reports.
>
> \(4\) [Post and Patrol Operations]{.underline}.
>
> \(a\) Officers will be trained and qualified to operate all vehicles,
> equipment, and weapons issued for normal job assignments.
>
> \(b\) Officers will be trained to recognize suspicious actions and
> contrary to regulations or to law applicable to KSC.
>
> \(c\) Officers will be trained in all access criteria applicable to
> KSC.
>
> b\. [Special Response Forces]{.underline}.
>
> \(1\) Law Enforcement officers will perform duties comparable to
> municipal law enforcement officers. They will enforce all State
> Statutes on KSC, investigate accidents, and perform general crime
> prevention/security patrols.
>
> \(2\) Special Response Team (SRT) officers will provide a ready
> response force capable of countering organized and trained
> adversaries. These officers will be trained and armed as directed by
> NASA.
>
> c\. [Supervisory Responsibilities]{.underline}. Supervisors and
> Managers will:
>
> \(1\) Meet all training and performance qualifications specified for
> officers in each appropriate category.
>
> \(2\) Be familiar with duties and responsibilities for all security
> posts.
>
> \(3\) Be familiar with all facilities, operations, and procedures
> associated with their duties.
>
> \(4\) Ensure that all security posts/personnel are performing assigned
> functions efficiently. This requires that each post be visited at
> least once during each shift.
>
> \(5\) Ensure that all logs, reports, or other required documents are
> maintained, completed, distributed, or complied with.
>
> \(6\) Obtain additional training and skills for management personnel,
> as determined by the contractor.

402.4 [PROTECTIVE FORCES TRAINING]{.underline}

> a\. [Purpose]{.underline}. The overall objective of the formal
> training program for the protective force is to develop and maintain,
> in an effective and efficient manner, the competencies essential by
> protective force personnel to perform the tasks required, in order to
> fulfill the security mission on KSC. The formal training program
> includes all organized, documented training activities which are the
> responsibility of the protective forces training element. This
> includes training activities conducted for pre-service employees, NASA
> Federal Law Enforcement Training, on-the-job training on each shift,
> and during annual recertification.
>
> b\. [Program Requirements.]{.underline} The training program will:
>
> \(1\) Be based on valid and complete analysis of job tasks.
>
> \(2\) Be clearly organized, with measurable criteria for objectives to
> be evaluated during training.
>
> \(3\) Accommodate the various levels of skills for each category of
> officer (i.e., pre-employment vs. Special Response Team) so that the
> maximum efficiency in training takes place.
>
> \(4\) Achieve a well defined, minimum level of competency to perform
> each required task.
>
> \(5\) Employ standardized lesson plans with clear performance
> objectives as a basis for instruction.
>
> \(6\) Be supported by adequate resources, including qualified
> instructors, adequate time, facilities and funding.
>
> \(7\) Be planned, organized, and directed to make optimum use of
> available resources.
>
> \(8\) Be documented so that individual and overall training status is
> easily accessible.
>
> c\. [Officers]{.underline}.
>
> \(1\) [Basic Training]{.underline}. Prior to initial assignment to
> duty, officers will successfully complete a basic training course, to
> include NASA Federal Law Enforcement certification. The basic training
> course will be approved by the Chief, Protective Services Branch. This
> course will equip officers with the necessary knowledge and skills to
> maintain minimum performance requirements on the job.
>
> \(2\) [Annual Training]{.underline}. Officers will receive annual
> refresher training as approved by the Chief, Protective Services
> Branch. This training will serve to recertify officers in required
> knowledge and skills or to impart new training as required.
>
> d\. [Special Response Team]{.underline}. SRT and law enforcement
> officers will receive additional training as required by the Chief,
> Protective Services Branch.
>
> e\. [Supervisors]{.underline}. All protective force supervisors will
> successfully complete basic and annual training for assigned
> categories as required for officers.
>
> f\. [Additional Training]{.underline}. Some officers and management
> personnel may be required to participate in specialized training;
> i.e., intoxilyzer, radar, gunsmith, physical security, canine
> handling, etc.

g.  [Refresher Training]{.underline}. All officers, who carry weapons,
    will complete NASA Federal Law Enforcement refresher training, once
    every two years.

402.5 [PROTECTIVE FORCES EQUIPMENT]{.underline}

> Protective force equipment will enhance the ability of the protective
> force to effectively, efficiently, and safely perform routine duties
> and to prevent adversaries from accomplishing their objectives.
>
> a\. [Individual and Special Equipment.]{.underline}
>
> \(1\) [Uniforms.]{.underline} Protective force personnel will be
> distinctively uniformed while on duty and identified with their
> function by appropriate variances in uniform. The uniform will be such
> as to enhance the efficient performance of routine and emergency
> duties, and will promote the image of professionalism.
>
> \(2\) [Duty Equipment]{.underline}. Certain items are to be assigned
> to each officer (either permanently or from on-shift supplies). These
> include the appropriate weapons, holster, ammunition, and radio.
> Additional equipment will be issued as required for specific
> assignments and current conditions.
>
> \(a\) [Primary Weapon.]{.underline} The 9-mm Glock semiautomatic
> pistol.
>
> \(b\) [Secondary Weapon.]{.underline} A 9-mm submachine gun, 12-gauge
> shotgun, or a HK-33 rifle is available and will be issued concurrent
> with the type of duty and level of protection to be afforded.
>
> \(c\) [Weapons Storage and Handling.]{.underline} Procedures will be
> developed to facilitate storage and accountability of weapons when
> maintained at Security Headquarters, Building K6-2496, and when
> assigned to officers.
>
> \(d\) [Ammunition, Pyrotechnics, and Explosives.]{.underline} The
> protective force will maintain sufficient ammunition, pyrotechnics,
> and explosives to accomplish the identified mission.
>
> \(3\) [Special Equipment.]{.underline} The protective force will
> maintain such specialized equipment as required to accomplish the
> security mission. This may include mobile command post, boats,
> explosives and nuclear material detectors, specialized radios, night
> observation devices, off road vehicles, and other equipment items.
>
> \(4\) [Equipment Inventory and Accountability]{.underline}. The
> protective force will establish NASA and J-BOSC approved procedures
> for maintaining inventory and accountability of all equipment.
>
> b\. [Protective Force Vehicles.]{.underline}
>
> \(1\) [Vehicle Type.]{.underline} Protective force vehicles shall
> exhibit a degree of reliability commensurate with their intended
> function. These vehicles will enhance the efficiency, speed, and
> safety of routine and emergency duties under all weather conditions.
> The vehicles are to be of a type and size suitable for the intended
> use.
>
> \(2\) [Vehicle Maintenance.]{.underline} Procedures will be developed
> to ensure that vehicles are maintained in a serviceable condition.
> Records of all maintenance will be maintained by GSA.
>
> c\. [Communications Equipment.]{.underline}
>
> Protective force communications equipment will provide multichannel
> capability with clear transmissions. Encoded transmission capabilities
> will be available when required. Communications equipment will be
> readily available in sufficient numbers to equip protective forces.

**CHAPTER 403**

**INCIDENT MANAGEMENT SYSTEM**

403.1 [GENERAL]{.underline}

> This chapter provides management instruction for all actual or
> suspected or probable crisis incidents that may occur requiring
> emergency planning, control, and resolution. Incident Management
> System (IMS) events for Security may result from either natural
> disaster, industrial accidents, and criminal or malicious intent.

403.2 [RESPONSIBILITIES]{.underline}

> a\. [The Chief, Protective Services Branch, is responsible
> for]{.underline}:
>
> \(1\) Managing command, control, and communications as the Incident
> Commander (IC) at the scene of an incident occurring on KSC.
>
> \(2\) Establishing requirements for planning, development, and
> coordination of detailed procedures by KSC organizational elements and
> their associated contractors.
>
> \(3\) Providing guidelines for establishing Incident Management Teams
> (IMT) for Security to ensure effective emergency operational
> performance and return of all elements to normal status.
>
> \(4\) Providing coordination of collateral support to other KSC
> elements or Government agencies.
>
> b\. [Heads of management support and heads of primary organizations
> are responsible for]{.underline}: Immediately, upon the request of the
> Chief, Protective Services Branch, or Lead, NASA Security, providing
> personnel under their control to assist in efforts concerning:
>
> \(1\) Protection of life and property.
>
> \(2\) Maintaining continuity of operations.
>
> \(3\) Evidence/data impoundment and/or control.
>
> \(4\) Damage assessment and repair.
>
> \(5\) Resumption of normal activities following emergency or crisis
> situations.
>
> c\. [The Lead, NASA Security, is responsible for:]{.underline}
>
> \(1\) Establishing requirements for reporting, investigating, and
> resolving all incidents involving criminal or malicious intent covered
> within the scope of this chapter.
>
> \(2\) Supporting collateral investigations by other Government
> agencies.
>
> \(3\) Ensuring that detailed plans and procedures are in effect
> identifying security measures applicable for various emergency or
> crisis incidents.

403.3 [SECURITY INCIDENT MANAGEMENT TEAM]{.underline}

> a\. The initial management response to any emergency or crisis
> situation is to establish a Security Incident Management Team (SIMT).
> Due to the diverse incidents which may present a crisis situation,
> various KSC organizations may be represented in comprising the IMT.
> Representatives from NASA Security will be part of the primary team
> structure because of their interrelationship in controlling emergency
> situations. Other Incident Management Team members may include, but
> not be limited to: Fire personnel, Safety personnel, KSC Senior
> Management, Public Affairs Office personnel, and personnel from other
> Government agencies.
>
> b\. The Chief, Protective Services Branch, or designee will identify
> initial IMT representation for Security and coordinate its activation.
>
> c\. Personnel comprising the IMT for Security must remain
> knowledgeable and current on plans, procedures, and capabilities of
> their respective organizations.

d.  The objective of Security's IMT is to ensure effective response,
    resolution, and return of all elements to normal status. Of primary
    concern will be the protection of life and property.

403.4 [PREPARATION AND PLANNING]{.underline}

> The incident management topics described in the subsequent paragraphs
> of this chapter require general and detailed preparation/planning for
> responding to an incident at KSC or to sites under KSC jurisdiction.
> Preparation will include identifying requirements for equipment and
> training necessary to ensure proficient performance in handling these
> situations. Planning must specify Incident Command responsibility
> pertaining to initial response and handling of any specific crisis
> situation.

403.5 [NATURAL DISASTERS.]{.underline}

> JHB 2000, and KHB 1710.2, both provide precautionary measures which
> will be performed in advance of a potential disaster, either a natural
> disaster, or as a result of a safety accident; i.e., hurricane,
> adverse weather, tornadoes, safety accidents, toxic vapors/hypergolic
> and cryogenic spills, emergency medical operations, fire, nuclear
> accident/radiological incident, inadvertent space vehicle/aircraft
> accidents, utility contingencies, etc.

403.6 [BOMBS AND BOMB THREATS]{.underline}

> a\. [Definitions:]{.underline}
>
> \(1\) [Bomb]{.underline}: A device capable of producing damage to
> material and injury or death to personnel when detonated or ignited.
> Bombs are classified as explosive or incendiary. An explosive bomb
> causes damage by fragmentation, heat, and blast wave. The heat
> produced often causes a secondary incendiary effect. An incendiary
> bomb generates fire-producing heat without substantial explosion when
> ignited. Bombing occurs when an explosive bomb detonates or an
> incendiary bomb ignites.
>
> \(2\) [Bomb Threat]{.underline}: A message, delivered by any means
> that may or may not specify the location of a bomb, time of
> detonation, ultimatum related to the detonation, or concealment of the
> bomb.
>
> \(3\) [Bomb Incident]{.underline}: Any event concerning the execution
> of a bomb threat, discovery of a bomb device, or detonation of a bomb
> on KSC.
>
> b\. [Policy]{.underline}: The primary mission will be protection of
> life, flight hardware, and government property. Actions to be taken
> will be based on an evaluation of all available information and
> circumstances present in each situation.
>
> c\. [Procedure]{.underline}: Bomb threats are usually received by
> either mail or telephone. It is important that the person receiving
> the threat knows what to do in each case.
>
> \(1\) [Threats by Mail]{.underline}:
>
> \(a\) Carefully preserve the letter, in plastic container if possible,
> handling it as little as possible until released to a security
> representative.
>
> \(b\) Note time and manner in which letter was received.
>
> \(c\) Report all incidents to the Joint Communications Control Center
> (JCCC), by calling 911, or 867-2121, immediately.
>
> \(2\) [Threats by Telephone:]{.underline} Most threats are received by
> telephone. Unlike a letter, a phone call leaves no physical evidence
> on which to base a plan of action. For this reason, security
> authorities must rely heavily on the information conveyed by the
> person taking the call. The form on the last page of the KSC Telephone
> Directory should be used as a guideline to record important
> information for investigating authorities. Upon receiving a bomb
> threat by phone:
>
> \(a\) Make a note of the exact time of the call.
>
> \(b\) Try to remember the exact message, word for word (take notes).
>
> \(c\) Obtain as much information from the caller as possible by
> listening to background noises, noting sex, age, accent, etc.
>
> \(d\) Report incident to the JCCC, 911/867-2121, immediately.
>
> \(3\) [Suspect Objects/Packages]{.underline}: If an object is visually
> detected and suspected of being an explosive device:
>
> \(a\) Do not touch or move object.
>
> \(b\) Do not operate radio transmitters or cellular telephones in the
> vicinity (minimum of 150 feet) of the device. They could detonate it.
>
> \(c\) Report incident to JCCC, 911/7-2121 immediately.
>
> \(d\) Stand by at a distance of at least 300 feet to warn approaching
> personnel until security personnel arrive.
>
> \(4\) [Execution]{.underline}:
>
> \(a\) The IMT, initially comprised of representatives from NASA
> Security and J-BOSC Security, will analyze the information received to
> determine the seriousness of the threat and the appropriate response.
>
> \(b\) The Incident Commander will decide if it is necessary to search
> or evacuate the area. Instructions for personnel will be coordinated
> with the affected site manager.

403.7 [HOSTAGE/TERRORIST INCIDENTS]{.underline}

> a\. [Definition]{.underline}: Terrorism is the unlawful use of force
> against persons or property to intimidate or coerce a government, the
> civilian population, or any segment thereof, in furtherance of
> political or social objectives.
>
> b\. [Policy]{.underline}: Presidential Decision Directive 39 (PDD-39),
> "United States Policy on Counterterrorism" directs a number of
> measures to reduce the Nation's vulnerability to terrorism, to deter
> and respond to terrorists acts, and to strengthen capabilities to
> prevent and manage the consequences of terrorist use of Nuclear,
> Biological, and Chemical (NBC) weapons including Weapons of Mass
> Destruction (WMD). PDD-39 discusses Crisis Management and Consequences
> Management.
>
> \(1\) [Crisis Management]{.underline}: Includes measures to identify,
> acquire, and plan the use of resources needed to anticipate, prevent,
> and/or resolve a threat or act of terrorism. The laws of the United
> States of America, assign primary authority to the Federal Government
> to prevent and respond to acts of terrorism; State and local
> governments provide support and assistance as required. Crisis
> Management is predominantly a Law Enforcement response.
>
> \(2\) [Consequence Management]{.underline}: Includes measures to
> protect public health and safety, restore essential government
> services, and provide emergency relief to governments, businesses and
> individuals affected by the consequences of terrorism. The laws of the
> United States, assign primary authority to the States to respond to
> the consequences of terrorism; the Federal Government provides
> assistance as required. The Federal Emergency Management Agency (FEMA)
> retains responsibility for consequence management throughout the
> Federal response, and acts in support of the FBI, as appropriate,
> until the Attorney General, in consultation with the FBI Director and
> the FEMA Director, determine that such support is no longer required.
>
> c\. [Lead Agency Responsibilities]{.underline}:
>
> KSC Security is capable of responding to a hostage/terrorist incident,
> however, PDD-39 validates and reaffirms existing Federal Lead Agency
> responsibilities for counterterrorism, which are assigned to the
> Department of Justice, as delegated to the FBI, for threats or acts of
> terrorism within the United States. For this reason, the FBI shall be
> notified immediately when KSC is confronted with a hostage/terrorist
> situation. As stated in the Federal Response Plan, it is FBI policy
> that Crisis Management will involve only those Federal agencies
> requested by the FBI to provide expert guidance and/or assistance, as
> described in the PDD-39 Domestic Guidelines (Classified) and FBI
> Incident Contingency Plans (Classified).
>
> When the FBI is summoned, the KSC Incident Commander should be
> prepared to brief the arriving team leader on the following items:
>
> \(1\) Actions already taken
>
> \(2\) Logistics of the situation
>
> \(3\) Human resources available, deployed
>
> \(4\) Special tools, equipment available
>
> \(5\) Staging areas
>
> \(6\) Supplies
>
> The KSC Incident Commander must understand that the FBI has it's own
> plans to implement. The FBI may use a Classified version of
> operational plans to run the operation, and many aspects may not be
> immediately shared. Time constraints may prevent the FBI from
> releasing information. In some instances, the FBI may already be aware
> of the threat and could cut the KSC Incident Commander's in-brief
> short.
>
> The KSC Incident Commander should be ready to adjust the action plan,
> if necessary. Roles and responsibilities may be altered. The key to a
> successful operation is to disturb as little as possible, provide the
> logistical support needed, and remember the common goal.
>
> d\. [Unified Command System (UCS):]{.underline}
>
> In all probability, a UCS will be established. The UCS establishes
> goals and objectives, develops a single action plan, allows shared
> resources, and establishes specific responsibilities for the emergency
> response. The primary features of the UCS are:
>
> \(1\) Single integrated incident organization
>
> \(2\) Co-allocated facilities
>
> \(3\) Shared planning, logistical, and finance/administration
>
> \(4\) Coordinated process for resources acquisition
>
> e\. [Shared Resources]{.underline}: Responders that may support the
> situation and should be a part of any training and exercises on
> terrorism are:
>
> \(1\) Fire Services; HazMat; Emergency Medical Personnel
>
> \(2\) Public Works; Electrical, Gas, Water
>
> \(3\) Law Enforcement
>
> \(4\) Media and Public Affairs
>
> \(5\) Local Community Emergency Management
>
> Further information concerning response to terrorist activities is
> contained in the Federal Response Plan, Terrorism Incident Annex, T-1.
>
> JHB 2000, Annex O - Security Operations, develops general and specific
> guidance pertaining to planning for, and responding to, incidents of a
> terrorist/sabotage nature that may threaten life or property;
> compromise classified operations/information or threaten the National
> Space Program; or result in adverse publicity for NASA or KSC. These
> documents ensure that specific policy guidance is provided identifying
> authority (as listed above and outlined below) to handle response,
> containment, and neutralization of any potential threat.
>
> f\. [Hostage/Barricaded Subjects.]{.underline}
>
> \(1\) [Definition]{.underline}: A hostage is a person held against
> his/her will as security for fulfillment of certain terms or demands.
>
> \(2\) [Policy:]{.underline} This chapter specifies measures for: (1)
> responding to a hostage/barricaded-subject situation where the threat
> against human life or the loss of Government property has been
> expressed, (2) actions for the safety and protection of persons who
> may be held hostage or be threatened with bodily harm, or (3)
> barricaded subjects. A hostage or barricaded-subject situation will be
> considered any time a person is held against his/her will by threat of
> violence, either to that person or others; or those situations where
> persons barricade or otherwise secure an area and refuse to leave or
> comply with directions given by security authorities. If the
> barricading subject threatens violence, the threat must be considered
> real. The goal is to neutralize the situation with the minimum amount
> of force necessary and without injury to suspects or innocent
> bystanders.
>
> \(3\) [Procedure:]{.underline}
>
> \(a\) [Reporting]{.underline}: If a hostage/barricaded-subject
> situation should occur, the person reporting the incident should
> notify JCCC immediately by calling 911 or 867-2121, giving as much
> detail as possible about the situation, including reporting the
> person\'s name, location, and phone number. Maintain telephone
> contact, if feasible, providing information as requested until
> security personnel arrive on the scene.
>
> \(b\) [Execution]{.underline}: Upon notification of a hostage or
> barricade situation, J-BOSC Security will notify the crisis
> negotiators. The Senior Security Supervisor will immediately respond
> to the area as the Incident Commander and:
>
> [1.]{.underline} Maintain a low profile, taking no overt or covert
> actions that may indicate an attempt to take control of the incident.
>
> [2.]{.underline} Establish an inner perimeter to isolate the area, an
> outer perimeter to maintain control, and a command post.
>
> [3.]{.underline} Evacuate nonessential personnel from the area.
>
> [4.]{.underline} Gather intelligence; such as, who is being held
> hostage, who is the suspect, what is the objective of the suspect,
> etc., taking extensive notes to brief the crisis negotiator upon
> arrival.
>
> [5.]{.underline} Keep conversation with suspect to a minimum, but when
> conversation is necessary, speak in a calm, slow voice, making no
> threats or promises. Keep in mind that time is the greatest tool of
> the negotiator, and any attempts to end the incident rapidly may cause
> the deterioration of the negotiation process.
>
> g\. [Sabotage.]{.underline}
>
> \(1\) [Definition:]{.underline} Acts or processes tending to hamper or
> hinder operations by unauthorized destruction of property or
> obstruction of operation and maintenance activities.
>
> \(2\) [Policy:]{.underline} KSC is vulnerable to acts of sabotage
> which may be committed at any time and without warning. Circumstances
> surrounding each threat/incident, including location, time, and
> previous countermeasures taken, will dictate action to be taken.
> Heightened security measures will be taken prior to all launches at
> launch-critical facilities/areas. J-BOSC Security will respond to all
> acts of sabotage. Fire, medical, safety, and other KSC elements will
> respond, as required.
>
> \(3\) [Procedure]{.underline}:
>
> \(a\) [Reporting]{.underline}: The reporting person will respond
> depending on how the information was received:
>
> [1.]{.underline} [By Observation]{.underline}: Should a person observe
> an act that is suspected of being sabotage, immediately notify JCCC,
> 911/867-2121.
>
> [2.]{.underline} [By Telephone]{.underline}: Security authorities must
> rely heavily on the information conveyed by the person taking the
> call. The form on the last page of the KSC Telephone Directory should
> be used as a guideline to record important information for the
> investigating authorities. Upon receiving information/threat by phone:
>
> [a.]{.underline} Make a note of the exact time of call.
>
> [b.]{.underline} Try and remember exact message, word for word (take
> notes).
>
> [c.]{.underline} Obtain as much information from caller as possible by
> listening to background noises, noting sex, age, accent, etc.
>
> [d.]{.underline} Report incident to JCCC, 911/867-2121, immediately.
>
> [3.]{.underline} [By Mail:]{.underline}
>
> [a.]{.underline} Carefully preserve letter, in plastic container if
> possible, handling as little as possible until released to a security
> representative.
>
> [b.]{.underline} Note time and manner in which letter was received.
>
> [c.]{.underline} Report incident to JCCC, 911/867-2121, immediately.
>
> [d.]{.underline} [Execution]{.underline}: The Security Incident
> Commander will coordinate all activities relative to evacuation,
> personnel control, and other regulatory and restrictive measures
> necessary to provide maximum protection to personnel and property,
> initiate investigations, and advise and coordinate with other elements
> involved in the incident. Provisions of KMI 1711.1 and KMI 1620.5 will
> be followed when applicable.

\* 403.8 [CRIMINAL ACTS]{.underline}

> JHB 2000, \"KSC Comprehensive Emergency Preparedness Plan," develops
> general and specific guidance which pertains to, planning for and
> responding to incidents of a criminal nature that may threaten life or
> property, compromise classified operations/information or threaten the
> National Space Program, or result in adverse publicity for NASA or
> KSC. JHB 2000, ensures that specific policy guidance is provided
> identifying authority pertaining to response, containment, and
> neutralization of any potential threat.
>
> a\. [Civil Disturbance.]{.underline}
>
> \(1\) [Definition:]{.underline} The act of disturbing normal
> activities by civilian personnel.
>
> \(2\) [Policy:]{.underline} It is NASA and KSC policy to comply to the
> fullest extent practical with the applicable guidelines regarding
> Civil Disturbances.
>
> \(a\) Disturbances in and around KSC controlled areas are prohibited.
> Participants should be advised that all persons entering controlled
> areas must be authorized/badged to enter or be subject to eviction or
> possible arrest.
>
> \(b\) All positive actions taken under this plan will be accomplished
> in the least provocative manner. Procedures most likely to elicit the
> cooperation of the demonstrators should be used where possible. KSC
> personnel, while acting in an official capacity to bring the
> disturbance under control, are not expected to endure abusive language
> or threats to their person or government property.
>
> \(c\) Information on civil disturbances will be released to the news
> media and KSC personnel by the NASA Workforce & Diversity Management
> Office only.
>
> \(3\) [Procedure for Outside Controlled Areas of KSC
> Property:]{.underline} Upon notification of a demonstration or
> anticipated civil disturbance:
>
> \(a\) [J-BOSC Security will:]{.underline}
>
> [1.]{.underline} Respond to the scene to ensure impact on
> ingressing/egressing traffic poses no threat to controlled area.
> Maintain a surveillance of the demonstration and immediately report
> any escalation.
>
> [2.]{.underline} Perform notification as shown in JHB 2000, Annex L,
> Emergency Support to Local Government.
>
> [3.]{.underline} Notify NASA Security immediately, who will determine
> need for further reporting of the situation.
>
> [4.]{.underline} Standby to form an Incident Response Team with
> sufficient vehicles to ensure mobility for instant positive response.
>
> [5.]{.underline} Open an incident response log, entering significant
> events and actions. At a minimum, hourly entries will be made.
>
> [6.]{.underline} Submit an After-Action Report to NASA Security within
> 30 days of the termination of the disturbance.
>
> \(b\) [NASA Security will:]{.underline}
>
> [1.]{.underline} Notify NASA Senior Management and assure notification
> of Center Operational activities (Shuttle, Payload, Center Support).
>
> [2.]{.underline} If it appears that the KSC controlled area may be
> threatened, direct the formation of a J-BOSC Incident Response Team.
> This group will stage at J-BOSC Security Headquarters with sufficient
> vehicles to ensure mobility for instant positive response.
>
> [3.]{.underline} Submit an After-Action Report to the Center Director
> through the Director of Spaceport Services.
>
> \(c\) [The KSC Installation Security Office (ISO), or Designated
> Representative, will:]{.underline}
>
> [1.]{.underline} If the KSC controlled area is threatened or civil
> authorities have not arrived in sufficient number to control the
> situation outside the controlled area; the ISO will take charge of the
> situation; may direct the dispatch of the Incident Response Team.
>
> [2.]{.underline} Should participants enter the controlled area and
> refuse to leave, their eviction or arrest may be requested of civil
> authorities. If civil authorities are not present in sufficient
> numbers, the J-BOSC Security Incident Response Team may be directed to
> employ required force to ensure the integrity of the controlled area.
>
> \(d\) KSC photographers will photograph the proceedings, in
> particular, evictions or arrests by J-BOSC Security.
>
> \(4\) [Procedure for Disturbances Within KSC Controlled
> Areas]{.underline}:
>
> \(a\) [J-BOSC Security will:]{.underline}
>
> [1.]{.underline} Respond to the scene to evaluate the situation and
> control the disturbance.
>
> [2.]{.underline} Perform notification as shown in JHB 2000, Annex L,
> Emergency Support to Local Government.
>
> [3.]{.underline} Notify NASA Security immediately, who will determine
> the need for further reporting of the situation.
>
> [4.]{.underline} Standby to form an Incident Response Team with
> sufficient vehicles to ensure mobility for instant positive response.
>
> [5.]{.underline} Open an incident response log, entering significant
> events and actions. At a minimum, hourly entries will be made.
>
> [6.]{.underline} If the crowd is non-violent/not unruly: may provide
> for the ISO or Director or representative to talk to the participants
> to resolve the matter through discussion. If the decision is to
> disperse the group, unauthorized/unbadged persons will be advised they
> are subject to eviction and possible arrest. They will be allowed to
> leave the controlled area in a peaceful manner or be arrested, if they
> refuse to leave. Properly badged employees will be advised of possible
> disciplinary action, if they fail to disperse.
>
> [7.]{.underline} If the crowd is unruly, threatening, or disruptive;
> may provide for the ISO or representative to advise the participants
> they are subject to eviction and possible arrest, determine course of
> action, and advise participants. If necessary, the Incident Response
> Team will evict or arrest participants.
>
> [8.]{.underline} Submit an After-Action Report to NASA Security within
> 30 days of the termination of the disturbance.
>
> \(b\) [NASA Security will]{.underline}:
>
> [1.]{.underline} Notify NASA Senior Management and assure notification
> of Center Operational activities (Shuttle, Payload, Center Support).
>
> [2.]{.underline} If it appears that the KSC controlled area may be
> threatened, direct the formation of a J-BOSC Security Incident
> Response Team. This group will stage at J-BOSC Security Headquarters
> Building K6-2496, with sufficient vehicles to ensure mobility for
> instant positive response.
>
> [3.]{.underline} Submit an After-Action Report to the Center Director
> through the Director of Spaceport Services.
>
> \(c\) The ISO, or designated representative, will take charge of the
> situation; determine course of action; and advise participants.
>
> \(d\) KSC photographers will photograph the proceedings, in
> particular, evictions or arrests effected by J-BOSC Security.
>
> b\. [Related Statutes and Directives]{.underline}:
>
> \(1\) Federal Personnel Manual 751-4, Enforced Leave.
>
> \(2\) Florida Statutes, Chapter 810, Burglary and Trespass.
>
> \(3\) Florida Statutes, Section 821.18, Trespasses.
>
> \(4\) Florida Statutes, Section 861.01, Obstructing Highways.
>
> \(5\) Florida Statutes, Section 877.03, Breach of Peace, Disorderly
> Conduct.

**CHAPTER 404**

## BADGES AND PASSES

404.1 [GENERAL]{.underline}

> This chapter establishes the procedures and details responsibilities
> for issuing and controlling identification badges, temporary passes,
> and special badges used at the KSC.

404.2 [RESPONSIBILITIES]{.underline}

> a\. The Director, External Relations and Business Development, is
> responsible for providing transportation, tours, and other NASA
> visitor\'s services, as required, in support of visits to KSC by
> persons invited by the Center Director or Deputy Director, or persons
> referred by NASA Headquarters.
>
> b\. The Deputy Director is responsible for managing the approval,
> control, and conduct of tours of Space Shuttle operational areas by
> visitors, guests, dignitaries using the Center Director\'s guest
> credential (Gold Badge).
>
> c\. The Installation Security Officer (ISO) is responsible for the
> issuing of badges and passes, to include those for contractors and
> other official visitors. To respond to real-time security
> requirements, unforeseen events, and operational deltas, the ISO may
> change or enhance, as required, the procedures and responsibilities
> for the issuance and control of identification badges, temporary
> passes, and special badges.

404.3 [ACCESS TO KSC/CAPE CANAVERAL AIR FORCE STATION
(CCAFS)]{.underline}

> a Entry to KSC property or into controlled areas on KSC or CCAFS is a
> privilege which can be denied, suspended, or revoked.
>
> b\. Access to KSC will be allowed only when it furthers the conduct of
> NASA business (hereafter referred to as \"official business\"). This
> applies to employees of NASA, its contractors, and tenants on KSC, as
> well as others with business to conduct at KSC. Approved guests,
> visitors, and participants in tours are included in the category of
> \"official business.\"
>
> c\. Access to KSC is normally controlled through use of KSC or CCAFS
> issued identification badges or passes. Other special badges may be
> issued for launches, tours, or other special occasions.
>
> d\. Access to security areas (limited or closed) on KSC or CCAFS is
> granted by the system or facility Office of Primary Responsibility
> (OPR) and is controlled by use of an Area Permit system, in addition
> to appropriate NASA, KSC, or CCAFS issued identification badges. When
> special operational safety or other conditions are in effect, special
> badges, access lists, or other devices authorized by the ISO may be
> used to grant access. NASA employees not duty-stationed at KSC may use
> their NASA identification badges for access to KSC/CCAFS. Access to
> security areas may be granted based on clearance information in the
> \"Installation Cleared Personnel Roster\" maintained at the Visitor
> Records Center (VRC).
>
> e\. The VRC will verbally verify a visitor\'s level of security
> clearance to NASA personnel or KSC organizational security
> representatives, if the visitor\'s clearance is on record and if the
> individual is making an official/classified visit.
>
> f\. Appropriately badged and qualified individuals will act as
> escorts, when required.
>
> g\. Individuals requesting access to KSC or NASA controlled areas on
> CCAFS must provide positive identification. Acceptable forms of
> identification include a driver\'s license; state-issued
> identification card; passport; company identification with photo;
> armed forces identification card; or federal, state, and local law
> enforcement credentials or identification. Identification must be
> presented before the individual will be issued a badge or pass.
>
> h\. Unless specifically approved by the ISO, no individual shall
> possess more than one NASA or KSC ID. This provision does not limit
> the possession of required Area Permits or special access badges.

404.4 [BADGE RECEIPTING]{.underline}

> a\. The computer-generated KSC Identification Badge is receipted for
> during its preparation. The Video Imaging Badging System Signature
> Slip, KSC Form 28-996, when signed and signature image is transferred
> to the computer-generated badge, constitutes receipt. Temporary Passes
> will be receipted for when the individual signs the badge.
>
> b\. The individual, by acceptance of the badge, agrees to abide by the
> regulations of KSC and CCAFS, and to subject themselves and any
> property in their possession or control, to any search or detention
> necessary for the protection of information and property.

404.5 [DISPLAY AND CONTROL OF THE BADGE]{.underline}

> a\. Each individual authorized access to KSC/CCAFS will adhere to the
> following rules concerning wearing and use of badges and passes:
>
> \(1\) On KSC/CCAFS, the badge/pass will be worn above the waist,
> plainly visible, face side out, unless operational
> considerations/requirements dictate the badge be removed because of
> special clothing requirements (clean room garments, SCAPE suits,
> etc.), placed on a badge board, or worn below the waist for safety
> reasons. Badges may be inserted into clear plastic holders. Necklace
> material must be approved for use by the KSC Safety Operations
> Division.
>
> \(2\) Individuals will comply with any request by security personnel,
> management, or authorized auditors to surrender the badge/pass for
> physical inspection.
>
> \(3\) Items such as tape, pins, clips, etc., will not be fastened to
> the badge/pass in any manner so as to obstruct, alter, or in any way
> change the appearance of the badge.
>
> \(4\) While it is permissible for companies to issue company badges,
> the primary badge used on KSC is the KSC issued identification badge.
> As mentioned above, while on KSC/CCAFS, the KSC badge will be worn
> above the waist, plainly visible and not behind the company badge.
>
> b\. Badges will be safeguarded when not being utilized. Vehicles are
> not recognized or authorized as a proper location for storage of the
> badge.
>
> c\. Badges that are faded, separated, or in otherwise poor condition
> will be replaced.
>
> d\. Badges will be replaced when physical appearance is changed; i.e.,
> beard growth or removal, plastic surgery, etc.
>
> e\. Use/Misuse.
>
> \(1\) The use of any KSC badge for other than KSC/CCAFS use is
> strictly prohibited. See paragraph 404.8, Violations.
>
> \(2\) The photocopying or photographing (duplication) of badges is not
> permitted. Badges are not authorized for use in the transaction of
> personal business. Merchants and financial institutions may not make
> copies of KSC badges.

404.6 [LOST BADGE/AREA PERMIT REPORTING]{.underline}

> a\. NASA employees who have lost their picture badges, Area Permits,
> PACAS cards, or any special badges or permits must submit within 2
> working days a \"Lost Badge Statement\" to the VRC explaining the
> circumstances (when and where lost, and what attempts were made to
> find it). The statement must also indicate that if the badge is found,
> it will be turned in to the VRC.
>
> b\. Contractor employees who have lost their picture badges, Area
> Permits, PACAS cards, or any special badges or permits must submit the
> above-mentioned \"Lost Badge Statement\" to their organization's
> badging official who will endorse and forward the statement to the
> VRC.
>
> c\. Employees who have lost their picture badges will be issued
> temporary passes valid for a 7-day period to allow the employee time
> to conduct a thorough search for the document. At the end of that
> time, if the badge has not been located, a new badge will be issued.
>
> d\. Report of a lost Temporary Pass may be submitted on KSC O/T Form
> 4392, Lost/Stolen Temporary Pass. This form is only available at Pass
> and Identification Station (PIDS) 1, 3, F-Gate, and the VRC.

404.7 [TERMINATION, LEAVE OF ABSENCE, VACATION, AND FOREIGN
TRAVEL]{.underline}

> a\. When authorization to possess a picture badge no longer exists
> (i.e., upon termination of employment, end of visit, leave of absence,
> or expiration of contract), the badge will be surrendered to the
> respective KSC or contractor security office. An Exit Pass, KSC Form
> 20-133, will be issued to the individual for departure from the
> installation, if necessary.
>
> Note: Disciplinary or administrative leave policy: As directed, badges
> will be turned in and held until expiration of the action. Vacation:
> KSC badges will not be taken on vacation. Foreign travel: Unless
> specifically authorized by the ISO, no badge or pass will be taken
> into a foreign country. Medical: An absence over 90 days requires that
> picture badges be turned in.
>
> b\. Contractor employees who are not permanently stationed at KSC or
> CCAFS and have been issued picture badges containing an expiration
> date are required to turn their badges in to their security office or
> representative when departing the area for a significant period of
> time (e.g., return to permanent home in another county or state). The
> badges will be held for those individuals until their subsequent
> return to KSC, or until expiration.

404.8 [VIOLATIONS]{.underline}

> Any individual having the knowledge or suspicion that badging
> regulations are or have been violated is required to report those
> violations to his/her security office.
>
> Note: Unauthorized use of a Government badge/pass, (including but not
> limited to the transfer, sale, gift, loan, use as collateral, or use
> to gain access to, or remain in an area or on the installation for
> other than official purposes) or any mutilation, destruction, or
> forgery (including alteration or duplication) thereof, may subject the
> person responsible to exclusion from KSC, punishment by law, and/or
> administrative action by his/her employer.

404.9 [PASS REQUESTS BY TELEPHONE]{.underline}

> Pass requests received at the VRC by telephone are subject to
> confirmation. VRC personnel may telephone or contact in person the
> requester or his/her supervisor when any question arises concerning
> the authenticity of the request.

404.10 [ADVERSE INFORMATION REPORTING]{.underline}

> a\. Immediate supervisors of NASA employees and supervisory personnel
> of other organizations will report to the appropriate NASA or
> contractor security office, any adverse or derogatory information
> concerning their employees as soon as that information becomes known
> to them.
>
> b\. Adverse information reporting will be consistent with KHB 1610.1,
> Chapters 204 and 412.
>
> c\. All individual employees at KSC have the responsibility to report
> adverse information, when it becomes known to them. Individuals who
> wish to remain anonymous may submit reports directly to NASA Security.

404.11 [RESIDENT BADGES]{.underline}

> a\. [NASA Civil Service Badge]{.underline}
>
> \(1\) The NASA Civil Service Badge is uniform throughout the agency
> and will be issued to NASA civil servants, NASA civil servant
> retirees, NASA non-appropriated fund employees, consultants, and other
> federal employees and military personnel detailed to NASA. Badge
> standards will be consistent with NPG 1620.1. The individual's
> security clearance will not be designated by any device, color, or
> code on the badge.
>
> \(2\) The NASA Personnel Office will process necessary forms and
> coordinate with NASA Security to obtain approval for the issuance of
> badges.
>
> \(3\) Color codes used to indicate individual status:
>
> White
>
> top and bottom - Active employee
>
> Blue
>
> top and bottom - NASA Retiree
>
> Silver/gray - Non-appropriated
>
> top and bottom fund
>
> Orange
>
> top and bottom - Consultant
>
> \(4\) [KSC Retirees]{.underline}
>
> The badge for NASA retirees may be used only during normal working
> hours, Monday through Friday, and it will not permit unescorted access
> to security areas. The badge will not be utilized for the purpose of
> soliciting or promoting activities which result in the retiree's
> personal gain, sales, services, or arranging job interviews.
>
> b\. [KSC Resident Contractor Badge]{.underline}
>
> \(1\) The KSC Resident Contractor Badge will be issued to NASA/KSC
> contractor employees, party to a NASA-related contract, whose normal
> work location is KSC or CCAFS. A Temporary Pass will be utilized until
> a picture badge is issued.
>
> \(2\) A Resident Contractor Badge is colored green to the left of the
> picture and the company's name will be imprinted in the green area.
>
> \(a\) A prime contractor may designate up to five persons as
> authorized badge-requesting officials for each prime contract and an
> additional eight persons for each subcontractor. The names will be
> furnished by correspondence to the VRC. A subcontractor requesting
> badging authority will submit the request through the prime
> contractor.
>
> \(b\) Correspondence showing delegation of badging authority should
> include the local company address and phone number, work phone numbers
> of authorizing personnel, areas of performance, contract number, and
> expiration date of contract or subcontract. Prime contractors will be
> responsible for badges issued under their own authority and those
> requested by their subcontractors.
>
> \(c\) Designated badging officials will submit badge requests to the
> VRC on KSC Form 20-162. The VRC will maintain names and identification
> of designated badging officials on file.

404.12 [NONRESIDENT BADGES]{.underline}

> a\. The Nonresident Badge will be issued to Government and contractor
> employees, party to a NASA-related contract, whose visits to KSC are
> for more than 180 consecutive days or are sufficiently repetitive
> within the visit year.
>
> \(1\) The Nonresident badge is colored yellow on both sides of the
> picture. The company's name is imprinted in the yellow on the left of
> the picture.
>
> \(2\) The Nonresident badge may be issued for varying lengths of time.
>
> b\. When required, the badge will be marked with a month and year to
> indicate the expiration date. The badge will expire the last day of
> the month indicated.
>
> c\. Sponsors of individuals holding Nonresident badges will be
> required to submit requests for new badges 14 to 30 days prior to
> expiration. Sponsors will submit badge requests in writing using KSC
> Form 20-162, Request for KSC Picture Badge, to the VRC.
>
> d\. The Nonresident badge will also be issued for the following
> categories of visitors to KSC:
>
> \(1\) [Construction]{.underline}.
>
> \(a\) Supervisory employees, party to a NASA-related contract, whose
> normal work location is KSC or CCAFS. The badge will be imprinted with
> the word "CONSTRUCTION" in the yellow to the right of the individual's
> picture.
>
> \(b\) Construction company personnel holding non-resident badges may
> interchange between construction projects at KSC or CCAFS by meeting
> the operating entities\' procedures. However, should all contracts
> with NASA/KSC or NASA contractors terminate, the KSC badge/pass must
> be returned even though a contractor may still hold a valid contract
> with the Air Force. Such employees would then be required to be
> rebadged with a CCAFS badge.
>
> \(2\) [Support Personnel]{.underline}.
>
> \(a\) Included in this category are those people whose services are
> required for activities; such as, installing or servicing machines, to
> persons; such as, safety or health inspectors, insurance
> investigators, vendors (not salespersons), truck drivers, and delivery
> persons who require frequent access to KSC/CCAFS. The badge will be
> imprinted with the word "SUPPORT" in the yellow to the right of the
> individual's picture.
>
> \(b\) Badging officials must ensure that the number of badges issued
> are kept to the absolute minimum necessary to accomplish the required
> tasks.
>
> \(3\) [Groves.]{.underline}
>
> Fruit grove lessees and their permanent personnel may be issued
> badges. Grove badges are only good to and from grove areas. Badges for
> grove personnel must be requested by U.S. Fish and Wildlife badging
> officials by submission of KSC Form 20-162. The badge will be
> imprinted with the word, \"GROVES\" in the yellow, to the right of the
> individual's picture.
>
> \(4\) [News Media Members]{.underline}
>
> \(a\) Media personnel, who are authorized to have frequent access to
> the LC-39 Press Site, and have approval of the NASA/NASA Workforce &
> Diversity Management Office, may be issued KSC identification badges.
> The KSC Public Affairs Officer (PAO) must coordinate with NASA
> Security prior to approving issuance of badges. Badge requests will be
> submitted to the VRC. The badge will be imprinted with the word "NEWS
> MEDIA" in the yellow, to the right of the individual's picture.
>
> \(b\) The badge will permit access to KSC through KSC access gates 2,
> 2C, 3, 4, 4TT, and 6TT only, during designated days, as approved by
> NASA Security, for travel by the shortest route to the LC-39 Press
> Site when it is in operation. Access to all other areas, except the
> LC-39, will be under PAO escort.
>
> \(5\) [Labor Union Representatives]{.underline}
>
> Union representatives who meet the requirements of KSC/CCAFS
> regulations may be issued KSC identification badges. Requests for
> badges may be approved only by the NASA Labor Relations Office. The
> badge will be imprinted with the words "LABOR UNION REP." in the
> yellow to the right of the individual's picture.
>
> \(6\) [Foreign Nationals]{.underline}
>
> Foreign Nationals (FN) and Foreign Representatives (FR) who have been
> accredited by the International Relations Division of NASA
> headquarters may be issued badges. This badge will be distinguished by
> the addition of a pale green transparent band extending horizontally
> across the width of the badge immediately above the picture and
> covering the badge number.

404.13 [TEMPORARY PASSES, KSC FORM 28-100]{.underline}

> a\. Temporary passes are paper passes that may be issued for temporary
> access to KSC and CCAFS. Paper passes are also issued at CCAFS and may
> be used to gain access to KSC.
>
> b\. Temporary passes may be issued for short-term visits not to exceed
> 180 days. They may be issued to:
>
> \(1\) NASA employees visiting KSC and/or NASA controlled areas at
> CCAFS, who have not been issued a NASA or KSC identification badge.
>
> \(a\) [Unclassified Visits]{.underline}. Arrangements for visits
> should be made sufficiently in advance with the person to be visited
> to allow badging to be arranged as required.
>
> \(b\) A prime contractor may designate up to five persons as
> authorized badge-requesting officials for each subcontractor. The
> names will be furnished by correspondence to the VRC through the prime
> contractor security office.
>
> \(c\) Delegation of badging authority correspondence should include
> the local company address and phone number, work phone numbers of
> authorizing personnel, areas of performance, contract number, and
> expiration date of subcontract.
>
> \(d\) Designated badging officials for construction contracts must
> contact the VRC to arrange for a briefing and assignment of a control
> number. This control number must be used each time a badge or pass is
> requested.
>
> \(e\) [Classified Visits]{.underline}. NASA employees will arrange for
> their installation security office to forward clearance information to
> the VRC as follows: Full name, Social Security Number (SSN), date of
> birth, place of birth, clearance level, date clearance granted, and
> name of organization granting clearance.
>
> \(2\) [Visitors from organizations holding a Facility Security
> Clearance]{.underline}. The visitor will have the security officer who
> maintains the original Letter of Consent, forward it to the VRC with
> the following information by telephone, teletype, FAX, or letter.
> Telephone messages must be confirmed immediately in writing.
>
> \(a\) Employee\'s full name.
>
> \(b\) Employer\'s complete name including, if applicable, department
> or division and address; also address of security officer, if
> different.
>
> \(c\) Employee\'s level of clearance.
>
> \(d\) Date clearance was granted.
>
> \(e\) Name and location of authority who granted the clearance.
>
> \(f\) Employee\'s SSN, date and place of birth and citizenship.
>
> \(g\) Dates covered by visit clearance, not to exceed the duration of
> the contract.
>
> \(h\) Name and telephone number of KSC contact or person to be
> visited.
>
> \(i\) Purpose of visit.
>
> \(j\) Applicable NASA contract number, if any.
>
> \(3\) [Non-NASA Government Employees]{.underline}. The employee will
> have his/her security office forward to the VRC by telephone,
> teletype, FAX, or letter the information required in the above
> paragraph (NASA contract number not required). Telephone messages must
> be confirmed in writing.
>
> \(4\) [Official Visitors]{.underline}. The pass must be authorized by
> a badging official employed by a firm or organization under contract
> or subcontract to NASA/KSC, by a badging official of a KSC tenant
> organization, or by a NASA/KSC official or his/her representative. The
> VRC will have on file a list of designated badging officials.
>
> \(5\) [Delivery Persons]{.underline}.
>
> \(a\) A Bill of Lading will suffice as proof of official need. If the
> individual does not have a Bill of Lading, he/she will call the
> consignee for verification of delivery. The consignee will call the
> appropriate security representative, who, in turn, will call the VRC
> to authorize issuance of the pass.
>
> \(b\) Individuals making deliveries or pickups after hours or on
> weekends will not be issued a temporary pass until coordination has
> been made to ensure that a representative is available at the delivery
> or pickup site.
>
> \(6\) [Salespersons]{.underline}.
>
> \(a\) The pass must be approved by a designated badging official of
> the organization requesting sales or by a NASA/KSC official or his/her
> representative.
>
> \(b\) Sales demonstrations for NASA organizations must be approved by
> NASA Procurement, prior to arrival of the individual presenting the
> demonstration.
>
> \(c\) Passes will be normally issued for one day only.
>
> \(7\) [Fruit Grove Employees.]{.underline}
>
> \(a\) A group pass may be issued upon request by a picture-badged
> grove employee. The request must include full names and Social
> Security Account Numbers of all persons to be included in the pass.
> The pass will be limited to citrus picking and grove maintenance crews
> and will be issued for 1 day only. The number of persons will be shown
> on the face of the pass.
>
> \(b\) An individual grove pass may be issued to other persons
> affiliated with the groves; such as, fruit buyers, salesmen, etc.,
> upon request by an authorized grove badging official through the VRC.
>
> \(c\) Citrus grove employees may enter and exit KSC through KSC gates
> only. Those employees who enter on a \"group\" temporary pass must be
> escorted at all times by a \"GROVES\" picture-badged employee.
>
> \(8\) [Personnel Attending Meetings, Conferences, or Employment
> Interviews.]{.underline} The pass must be authorized by a badging
> official employed by a firm or organization under contract or
> subcontract to NASA/KSC, by a badging official of a KSC tenant
> organization, or by a NASA/KSC official or his/her representative. The
> VRC will maintain a list of designated badging officials.
>
> \(9\) [KSC Employees Who Left Their Badges at Home.]{.underline} A
> pass can be requested at a Pass and Identification Station (PIDS) or,
> access gate when PIDS are closed. A pass will be issued upon
> verification of employment through the VRC Pass/Badge Information
> Management System, and with proper identification.
>
> \(10\) [News Media]{.underline}.
>
> \(a\) A temporary pass may be issued to news media members after
> approval has been received by the VRC from the NASA Workforce &
> Diversity Management Office.
>
> \(b\) During launch and landing activities, Public Affairs issues
> passes to news media members from the Gate 2, Pass and Identification
> Station.
>
> \(11\) [Foreign Nationals and Foreign Representatives.]{.underline}
> Visits by foreign nationals and foreign representatives to NASA
> installations require approval from the Office of International
> Relations Division, NASA Headquarters. The NASA Payloads, KSC Customer
> Service Office, has local approval authority for payload customers and
> potential payload customers. The VRC must be notified immediately upon
> receipt of information that a foreign national or representative is
> requesting a visit to NASA or NASA contractors at KSC or CCAFS, except
> Foreign Nationals and visitors as defined by KMI 1610.6 (See Chapter
> 406.)
>
> \(12\) [Construction Employees.]{.underline}
>
> \(a\) The pass must be requested by a designated badging official of
> the employee\'s organization or contractor organization to whom they
> are subcontracted. Passes may be issued for a period of 180 days or
> expiration of the contract, whichever is sooner.
>
> \(b\) Temporary passes issued to construction employees will be marked
> with the word **\"CONSTRUCTION\"** in bold letters across the top.
>
> \(13\) [Other Individuals who have been Authorized and Approved
> through the VRC.]{.underline}
>
> Temporary passes will not be issued through the VRC, to persons under
> the age of 16 years without approval of NASA Security.
>
> c\. [Information Required]{.underline}.
>
> \(1\) Personnel requesting temporary passes must provide the following
> information:
>
> \(a\) Full proper name of visitor. (i.e., Robert, not Bob)
>
> \(b\) Social Security Account Number.
>
> \(c\) Date(s) of visit.
>
> \(d\) Company or agency the visitor represents, street address, city,
> and state.
>
> \(e\) Area(s) to be visited.
>
> \(f\) Purpose of visit.
>
> \(g\) Approving company or NASA department.
>
> \(2\) The visitor will be asked to show proper identification, upon
> arrival at the Pass and ID Station. Upon confirmation that the pass
> has been approved, the pass will be issued.
>
> \(3\) After normal working hours and on weekends and holidays,
> temporary passes will be issued by the Security Officer at the gate
> after confirmation that the individual\'s visit authorization has been
> processed through the VRC.
>
> d\. [Description]{.underline}. The temporary pass may be
> completed/filled in by computer or hand and contain at least:
>
> \(1\) Name of individual.
>
> \(2\) Expiration date of approved visit.
>
> \(3\) PRP status, if authorized.
>
> \(4\) Organization/employer.
>
> \(5\) Areas authorized to visit on KSC or CCAFS.
>
> \(6\) Special identification (news media, delivery, grove, or
> construction), if applicable.
>
> e\. [Use]{.underline}.
>
> \(1\) The portion of the handwritten, paper pass containing
> identification will be inserted in a plastic holder and worn as a
> badge. The remaining portion of the pass contains instructions and
> requirements for access to KSC/CCAFS and will be signed and retained
> by the individual.
>
> \(2\) An escort will be required in secure areas (limited or closed)
> unless the individual has been issued an additional permit or badge
> requiring no escort.
>
> \(3\) Temporary passes are not required to be returned to security
> personnel at the end of an official visit, but should be destroyed as
> indicated on the reverse side of the badge portion of the pass.
>
> f\. [Advanced Temporary Pass]{.underline}
>
> \(1\) Designated badging officials may request advanced temporary
> passes from the VRC when it is necessary to accommodate personnel
> supporting operational activities.
>
> \(2\) After providing the information required in paragraph
> 404.13(b)(1-10), to the VRC, the requesting officials, when notified
> that the advanced passes are completed, will pick-up the completed
> advanced temporary passes.
>
> \(3\) The requesting official will be responsible for the delivery of
> the temporary passes to the visitors.
>
> \(4\) Temporary passes issued without the visitor's picture will not
> be issued for periods exceeding 5 days in duration. If duration is for
> a longer period of time, the individual should report to VRC or PIDS 1
> or 3, to renew the pass with a picture.

404.14 [GUEST BADGES]{.underline}

> a\. Guest badges may be issued to NASA/KSC Directorates and Chief
> Executive Officers (CEO\'s) of KSC\'s primary contractor organizations
> (J-BOSC, SFOC, and PGOC) for their convenience in badging important
> visitors on official business.
>
> b\. Guest badges, approved by a Director/CEO, may be issued to VIP
> visitors, when it is considered to be more appropriate than a
> temporary pass.
>
> c\. Guest badges may be issued by the NASA Workforce & Diversity
> Management Office to organizations that do not have guest badges on an
> as-requested basis for one-time use when the request is made directly
> from a Director/CEO.
>
> d\. KSC Directors and contractor CEO\'s, or their representatives who
> have been designated in writing, will be requested to sign for the
> Guest Badges assigned to their organization.
>
> Receipts provided by the VRC will contain the issued badges serial
> numbers and the instructions for issuing the badge. After receipt, the
> custodian will maintain a copy of the receipt with the badges.
> Together with the badges and receipt, a KSC Form 20-43,
> "Identification Log," will be maintained and used to log the use of
> the badges. The log sheet will be filled out as follows:
>
> \(1\) Serial Number: Enter badge number.
>
> \(2\) Issued to: Print name of individual requesting the badge.
>
> \(3\) Signature: Have requester sign the log.
>
> \(4\) Organization: Enter mail code and phone number of requester.
>
> \(5\) Date Issued: The date the badge leaves organizational custody.
>
> \(6\) Date Returned: The date the badge was returned to organizational
> custody.
>
> \(7\) Clearance
>
> Reference: The company or organization that the visitor represents.
>
> \(8\) Remarks: Print the visitor\'s name, indicate if the visitor is a
> minor. If the request for the visit was made via an AVO, the AVO
> should be referenced and a copy attached to the log.
>
> Log sheets will be forwarded to NASA Security on a monthly basis, but
> only after the badges have been returned. Badges are not intended for
> long-term issue, therefore, the log sheets should be completed by the
> end of the first work week of the month and forwarded. Negative
> reports are not required.
>
> Guest Badges will be securely maintained. Guest badges will be stored
> in locked desks, file cabinets, or secure storage containers (safes).
>
> e\. Guest badges will not allow access into operational or sensitive
> security areas.
>
> f\. Guest badges will not be issued for use by foreign nationals or
> representatives, unless specifically approved through the Office of
> International Affairs, Washington, D.C. and NASA Security.
>
> g\. Public Affairs personnel are responsible for conducting official
> tours. These responsibilities cannot be delegated to others;
> therefore, guest badges [will not]{.underline} be authorized for
> tours.
>
> h\. Guest badges must be returned to the sponsor upon completion of
> the visit. In case of loss, a \"lost badge\" memo (ref. paragraph
> 404.6) must be submitted to the VRC.
>
> i\. Upon expiration of contract, contractors must return all assigned
> guest badges to the VRC.
>
> j\. Guest badges [will not]{.underline} be issued to persons under the
> age of 16 years without approval of NASA Security.

404.15 [EXIT PASS]{.underline}

> a\. The Exit Pass, KSC Form 20-133, is authorized for use by both NASA
> personnel and KSC contractors, primarily for exit of terminated
> employees whose valid badges have been surrendered to designated
> badging officials. It may also be utilized for other purposes, as
> specifically authorized by NASA Security. This pass is valid for exit
> only from either KSC or CCAFS gates.
>
> b\. The exit pass will be issued by NASA or the contractor security
> office processing the terminated employee.
>
> c\. Exit passes are not required to be turned in to security
> personnel; however, they are valid only for the date of issuance and
> for the reason indicated.

404.16 [SPECIAL BADGES AND PLACARDS]{.underline}

> a\. [General]{.underline}. Special badges and placards are used to
> meet the special requirements of the KSC Director, visiting
> dignitaries, public affairs events, special meetings, conventions,
> operational considerations, landings, and launches. Most of the
> documentation for their specific use, issue, and control is
> fragmentary and provided to the security force as addendum to post
> orders. These special badges and placards are an adjunct to the
> established system; come in a variety of shapes, sizes, colors, and
> designs; provide personnel and vehicle access to KSC; and provide the
> attendee with a memento of some event associated with KSC.
>
> b\. [Request Procedures]{.underline}. Special badges may be requested
> from NASA Security by the NASA Workforce & Diversity Management Office
> and others, as required, for special events, ceremonies, meetings,
> etc., and should be coordinated in sufficient time to allow specific
> verbal or written access instructions to be conveyed to the
> guests/attendees prior to the special function.
>
> c\. [The Center Director\'s (CD) Guest Credential (Gold
> Badge)]{.underline}. The Center Director\'s Guest Credential was
> established to provide a means to handle distinguished visitors of the
> CD. It is the top-level credential for official visits and is
> controlled by CD letter dated January 21, 1998.

**CHAPTER 405**

**PERSONNEL CONTROL AND AREA PERMITS**

405.1 [GENERAL]{.underline}

> Kennedy Space Center Area Permits (KSCAP), Personnel Access Control
> and Accountability System (PACAS) cards and Temporary Area
> Authorizations (TAA\'s) are used to control access to operational,
> flight hardware, and restricted areas at KSC and at NASA-controlled
> facilities at CCAFS.
>
> Area Permits and TAA\'s will be issued only to individuals requiring
> access to controlled areas in conjunction with official duties and
> will not be requested for convenience or status purposes.
>
> The KSC Visitor Records Center (VRC), operated by the J-BOSC,
> maintains clearance and badging data, and processes, fabricates, and
> issues badges, permits, and identification cards for all KSC
> organizational elements, their contractors, and visitors, according to
> standards set by NASA Security.

405.2 [RESPONSIBILITIES]{.underline}

> a\. [The Installation Security Officer]{.underline} is responsible for
> establishing requirements for entry to KSC and its controlled access
> areas/facilities, and for managing and implementing the KSC Area
> Permit System for controlling access to those areas/facilities.
>
> b\. [Heads of KSC organizational elements]{.underline} are responsible
> for identifying and furnishing to NASA Security, a listing of all
> operational, flight hardware, and restricted areas requiring access
> controls by Area Permits/TAA\'s in which mission-related tasks or
> tests are being performed within their areas of responsibility.
>
> c\. [The Director, Safety, Health, and Independant
> Assessment]{.underline} is responsible for establishing training
> requirements which must be completed prior to issuance of a KSC Area
> Permit or TAA, authorizing unescorted access to controlled areas and
> approving and establishing manloading requirements at, or within each
> area designated as hazardous.
>
> d\. [Heads of primary organizations]{.underline} are responsible for
> ensuring the following:
>
> \(1\) Those personnel who do not require frequent access to controlled
> areas are issued TAA\'s rather than a KSC Area Permit.
>
> \(2\) That areas contained on the KSC Area Permit and TAA\'s are
> limited to those necessary in the performance of an individual\'s
> duties.

405.3 [DISPLAY AND SAFEGUARDING OF KSCAP AND TAA]{.underline}

> a\. The Area Permit or TAA will be worn above the waist, readily
> available for inspection, at all times while in a controlled area.
>
> \(1\) Area Permits may be inserted into clear plastic holders and worn
> on a necklace-type material.
>
> \(2\) TAA\'s may be attached directly to a necklace or to clothing by
> a clip or other fastener.
>
> \(3\) Necklace material must be of a type approved for use by the
> safety office.
>
> \(4\) Items; such as, tape, clips (except badge clips), pins, etc.,
> will not be fastened to Area Permits, PACAS cards, or TAA\'s in any
> manner. Area Permits, PACAS cards, and TAA\'s will be carried by the
> person to whom issued at all times while on KSC/CCAFS. While off duty,
> they must be safeguarded to prevent loss or use by unauthorized
> personnel. [Vehicles are not recognized or authorized as a proper
> location for storage]{.underline} of Area Permits, PACAS cards, or
> TAA\'s.
>
> b\. PACAS cards are not required to be displayed.
>
> c\. Individuals will comply with any request by security personnel, or
> access control personnel to surrender Area Permits, PACAS cards, or
> TAA\'s for physical inspection.

405.4 [ACCESS PROVISIONS]{.underline}

> a\. All personnel requiring access to KSC-controlled operational,
> flight hardware, and restricted access areas must possess (1) a NASA,
> KSC identification badge or Temporary Pass, or CCAFS identification
> badge or visitor\'s pass, and (2) a KSC Area Permit or TAA.
>
> b\. Area Permits and TAA\'s will be issued to essential personnel
> only. The sponsoring organization will be considered responsible for
> the essential nature of the access requirement, certification of
> required training, and the conduct of the employee within controlled
> areas. Each individual must meet one or more of the following criteria
> to be authorized access (issued an Area Permit or TAA) to a controlled
> area:
>
> \(1\) Operations personnel associated with STS/ELV assembly,
> processing, or testing.
>
> \(2\) Support personnel required for maintenance and operation of the
> facility and associated equipment.
>
> Note: An individual may be issued both an Area Permit and a TAA.
>
> c\. In addition to meeting one of the criteria listed in b.(1) or (2),
> an individual will [only be issued a KSCAP to those areas where a
> frequent access requirement has been clearly
> demonstrated]{.underline}. Otherwise, a TAA will be requested and used
> as the access credential.
>
> Refer to KHB 1610.2, Personnel Security Handbook, for personnel
> security clearance and investigation requirements.
>
> d\. Each KSC organization is issued, by the VRC, a copy of the \"KSC
> Area Access Authorization Matrices\" listing personnel who are
> authorized to approve access to controlled areas on KSC/CCAFS.
> Individuals listed in the matrices have the authority to approve
> access to specific areas under their operational jurisdiction.
>
> e\. Consultants, subcontractors, and miscellaneous service contractors
> with a limited number of personnel may be treated as part of the
> sponsoring NASA, Government agency, or contractor organization for
> Area Permit and TAA processing.
>
> f\. When authorization to possess an Area Permit or PACAS card no
> longer exists (i.e., upon termination of employment, end of visit,
> leave of absence, or expiration of contract), the Area Permit/PACAS
> card will be surrendered to the employee\'s organization Authorized
> Requester.
>
> Note: Foreign Travel: Generally, KSCAPS, TAA\'s, and PACAS credentials
> will not be taken into a foreign country. Personnel assigned TDY to
> non-CONUS Transatlantic Abort Landing (TAL) sites will take KSCAPS and
> TAA\'s to meet access requirements in the event that a Space Shuttle
> lands at one of the TAL sites.
>
> TAA\'s should be destroyed by the holder immediately after the TAA
> expiration date. When a TAA is still valid and determination is made
> the TAA is no longer required, it should be turned in to the VRC or
> Gate F Pass and ID personnel.
>
> g\. Should an area that is controlled under the Area Permit System
> have an emergency situation declared, all necessary emergency
> personnel (i.e., fire, medical, security, environmental health, etc.)
> responding to the area will be allowed access to the areas even though
> they may not possess an Area Permit or TAA.
>
> Note: NASA Security personnel may enter all areas on KSC upon
> presentation of their security credentials.
>
> h\. Any individual having the knowledge or suspicion that regulations
> regarding Area Permits, PACAS cards, and TAA\'s are or have been
> violated is required to report those violations to their security
> office. Unauthorized use of any Government-issued identification or
> access card or credential (including, but not limited to, the
> transfer, sale, gift, loan, use as collateral, or use to gain access
> to or remain in an area or on the installation for other than official
> purposes) or any mutilation, destruction, or forgery (including
> alteration or duplication) thereof, may subject the person responsible
> to exclusion from KSC, punishment by law, and/or administrative action
> by his/her employer.
>
> i\. New areas for coverage under the KSC Area Permit System may be
> added only after need and implementation criteria have been determined
> and approval received from NASA Security.

405.5 [SAFETY FAMILIARIZATION REQUIREMENTS]{.underline}

> a\. Personnel requiring access to certain designated operational areas
> require safety familiarization training before being granted
> unescorted access to those areas. Area safety training will be
> scheduled through the respective organization's training coordinator.
>
> Courses may be presented as video, film, or lecture courses in a
> classroom setting or as a physical \"walkdown\" at the designated
> location.
>
> b\. Forms certifying completion of safety training will be forwarded
> by the respective NASA and contractor organizations (except for the
> Shuttle Processing Contractors) to J-BOSC Training for inclusion into
> the KSC Training Certification Record System database.
>
> c\. Shuttle Flight Operations Contractor (SFOC) will forward forms
> certifying completion of safety training to SFOC Technical Training.
> Payload Ground Operations Contractor (PGOC) personnel and NASA Payload
> customers will forward forms certifying completion of safety training
> to PGOC Technical Training.

405.6 [TEMPORARY AREA AUTHORIZATIONS]{.underline}

> a\. [A Temporary Area Authorization (TAA)]{.underline} may be issued
> to an individual who requires access to controlled areas occasionally,
> but not often enough to justify possession of an Area Permit, or who
> does not meet both security and safety training requirements. TAA's
> are not issued to personnel who have Guest, Flight Crew, Barge Crew or
> "bullet badges".
>
> The TAA is a paper card with preprinted numbers on the front to
> indicate to which controlled areas the holder is authorized access,
> and the expiration date stamped in bold numbers/letters on the front.
>
> b\. [An Unescorted TAA,]{.underline} KSC Form 20-147, yellow in color,
> will be issued to individuals who meet both security and safety
> training requirements. Holders of KSC Form 20-147 will be allowed
> unescorted access to the areas indicated on the front.
>
> c\. [A \"To Be Escorted\" TAA]{.underline}, KSC Form 20-147A, pink in
> color, will be issued to individuals who do not meet both security and
> safety training requirements. Holders of \"To Be Escorted\" TAA\'s
> must be accompanied by an authorized individual at all times while in
> a controlled area. The \"To Be Escorted\" TAA will allow the holder
> access to the areas indicated on the front.
>
> d\. An [escort]{.underline}, when required for holders of \"To Be
> Escorted\" TAA\'s, may be provided by any person bearing a properly
> coded NASA badge, KSC identification badge, or CCAFS picture badge, in
> addition to a properly coded KSC Area Permit or Unescorted TAA.
> Escorts are responsible for maintaining physical control of personnel
> they are escorting. Normally, escorts are limited to escorting no more
> than five personnel at one time.
>
> e\. [Audits]{.underline} will be made to ensure that employees
> receiving TAA\'s have completed the proper safety training
> requirements. Personnel who do not have current area safety training
> may be requested to surrender their KSCAP, TAA, and/or PACAS cards.
> Falsification of any employee\'s training status may result in loss of
> an organization\'s authorization to request TAA\'s.

405.7 [REQUESTING AREA PERMITS, PACAS CARDS, TAA's]{.underline}

> Individual Area Permits, PACAS cards, and TAA\'s must be requested as
> follows:
>
> a\. Area Permits will be requested on Form 20-94, "Kennedy Space
> Center Area Permit Application." In addition to an original Area
> Permit request, a new KSC Form 20-94 must be submitted for each
> employee when:
>
> \(1\) An employee requires additional authorizations (numbers added to
> the Area Permit) to enter controlled areas.
>
> \(2\) An employee does not require access to some areas and requests
> numbers be deleted from the Area Permit.
>
> \(3\) An employee is reassigned to a function which requires a
> different access number(s) on the Area Permit.
>
> b\. Employees who require a [new Area Permit because of a name
> change]{.underline} (marriage or legal action) will be issued a new
> Area Permit in conjunction with their new picture badge request. An
> Area Permit application form is not necessary for this type action.
>
> c\. [TAA\'s may be requested]{.underline} by telephone or in person
> through the organization\'s Authorized Requester. The Authorized
> Requester will provide required information to the VRC or Gate F
> Badging Station, where the TAA will be issued.
>
> d\. [The PACAS card]{.underline} is a uniquely coded device used in
> conjunction with the Personnel Access Control and Accountability
> Subsystem (PACAS) to provide automated control and accountability of
> personnel into and out of selected areas through use of a card reader
> system. When a PACAS card is presented at a reader, the encoded signal
> is transmitted to the Electronic Security System (ESS) computer and is
> compared with the stored data for authorized access. If the entry or
> exit is authorized, the computer will generate a command to unlock the
> control device (turnstile) to permit unalarmed entry or exit.
> Unauthorized attempts will initiate an alarm in the KSC Joint
> Communications Control Center (JCCC). PACAS cards may also be used for
> entry/exit at facilities controlled by subsystems of the ESS.

405.8 [LOST AREA PERMIT, TAA, OR PACAS CARD]{.underline}

> a\. When an Area Permit, TAA, or PACAS card has been lost, the
> individual to whom the Area Permit, TAA, or PACAS Card was issued must
> immediately report the loss to the VRC, telephone 867-7763. Contractor
> employees should report the loss to their security office. This action
> may be by telephone, or in person.
>
> b\. A written or typed statement describing the loss must be forwarded
> by NASA personnel to the VRC. Contractor employees should forward the
> statement to their organization Authorized Requester. The statement
> must contain the following information:
>
> \(1\) Name.
>
> \(2\) Organization.
>
> \(3\) Area Permit, TAA, or PACAS card number, if known.
>
> \(4\) Type (Area Permit, TAA, or PACAS card).
>
> \(5\) Circumstances surrounding the loss (where, when, attempts to
> locate).
>
> \(6\) Statement indicating that if the Area Permit, TAA, or PACAS card
> is found, it will be turned in to the Visitor Records Center.
>
> c\. If the Area Permit or PACAS card is not found within 7 days, a
> replacement of the type originally issued may be obtained through the
> organization Authorized Requester where originally issued. A TAA may
> be issued immediately to allow access to authorized areas until a
> replacement Area Permit is issued. A replacement TAA for a lost TAA
> may be issued immediately after determination by the employee\'s
> Authorized Requester that the TAA requirement is still valid.
>
> d\. A defective KSC Area Permit and/or PACAS card can be turned in at
> the Visitor\'s Records Center, or at \"F\" Gate where a Temporary Area
> Authorization (TAA) will be issued for thirty (30) days. Replacement
> Area Permits and/or PACAS cards will be issued through the
> organization\'s Authorized Requester. Or, an appointment can be made
> with the Security Assistant working at the VRC Area Permit Desk,
> telephone 867-7083, to have the PACAS card and the Area Permit
> replaced during the appointment.

**\*CHAPTER 406**

**FOREIGN VISITORS**

406.1 [GENERAL]{.underline}

> This chapter provides NASA/KSC procedures for processing visit
> requests of foreign nationals and foreign representatives to KSC. It
> does not pertain to foreign nationals and foreign representatives
> associated with the public information media, and those visitors as
> defined by NPG 1371.2.

406.2 [RESPONSIBILITIES]{.underline}

> a\. [The Center Director]{.underline} is responsible for:
>
> \(1\) Implementing NASA standard procedures and guidelines for
> receiving, coordinating, reviewing, and approving/disapproving
> requests for visits from foreign nationals or representatives to KSC.
>
> \(2\) Designating a Center International Visit Coordinator.
>
> b\. [The Center International Visit Coordinator (IVC)]{.underline} is
> responsible for:
>
> \(1\) Ensuring that procedures and guidelines for coordination and
> control of foreign visitors are established and maintained.
>
> \(2\) Receiving, coordinating, reviewing and approving/disapproving,
> each request for foreign visitor access to KSC.
>
> \(3\) Forwarding to the Office of External Relations, NASA
> Headquarters, for coordination and decision, all requests for visits
> by foreign heads of state or government, ambassadors, and heads of
> foreign government ministries and space agencies, and nationals or
> representatives of countries on the Designated Areas List (NPG 1371.2,
> Appendix A).
>
> \(4\) Initiating a National Agency Check (NAC) for all foreign
> visitors working on accredited NASA-KSC programs or projects.
>
> \(5\) Collecting and compiling data on all foreign visits and access
> by foreign national employees of NASA, contractors or grantees to KSC.
>
> \(6\) Providing visit reports as necessary to the Office of External
> Relations, NASA Headquarters.
>
> c\. [The Export Control Officer]{.underline} is responsible for:
>
> \(1\) Reviewing the information provided by the IVC for foreign visits
> and making all appropriate contacts and/or inquiries to make a
> recommendation for or against the visit in question.
>
> \(2\) Approving Export Control Plans for long term visits.
>
> d\. [Heads of primary organizations and NASA Contractors]{.underline}
> are responsible for:
>
> Ensuring that personnel under their cognizance familiarize themselves
> and comply with the requirements of this chapter.

406.3 [VISITOR IDENTIFICATION/PROGRAM DEFINITIONS]{.underline}

> a\. [Foreign National (FN)]{.underline}. Any person who is not a
> citizen or permanent resident alien of the United States.
>
> b\. [Foreign Representative (FR) or Representative of a foreign
> entity]{.underline}. Any person, including a citizen, permanent
> resident alien or protected individual of the United States, who
> represents a government, business, organization, or person of a
> country other than the United States.
>
> c\. [Accredited FN/FR]{.underline}. Foreign nationals or
> representatives who have received the appropriate checks and
> credentials, and been approved for repeat visits to specific NASA
> Centers for the purpose of implementing an "agreed" NASA international
> cooperative or reimbursable program or project.
>
> d\. [Non-accredited FN/FR]{.underline}. These FNs/FRs are individuals
> who have been approved for access to KSC, for reasons other than the
> specific program/project involvement.
>
> e\. [Agreed international program or project]{.underline}. One that
> has a signed agreement between NASA Headquarters and a foreign agency
> or organization (international or U.S. with international membership).
>
> f\. [Accredited visitors]{.underline}. Foreign nationals and foreign
> representatives, regardless of nationality, who are approved by the
> various NASA Centers for repeat visits for the purpose of implementing
> an "agreed" NASA international cooperative or reimbursable program or
> project.

406.4 [VISIT TYPES AND DEFINITIONS]{.underline}

> a\. [Standard Foreign Visits]{.underline}. Any visit by a FN or FR of
> any country except countries identified as a designated area (see NPG
> 1371.2, Appendix A). The exception to this would be if the individual
> from the designated area is on a Center approved accreditation list
> working on an agreed international program or project for which the
> accreditation list was established. The international program or
> project must be with, or provide for participation by, that country in
> order for the individual to be on that accreditation list.
>
> b\. [Nonstandard Foreign Visit]{.underline}. A visit by a FN or FR of
> a country identified as a designated area in NPG 1371.2, Appendix A,
> unless they are on a Center approved accreditation list.
>
> c\. [VIP Tour]{.underline}. A visit by a senior foreign official,
> distinguished individual, or a high-ranking delegation that requires
> detailed, advance preparation and coordination on matters of protocol
> (i.e., foreign heads of state, government ministers, ambassadors, and
> heads of governmental agencies). The VIP tour may include a courtesy
> meeting with the Center Director or other senior management
> representative, a guided tour of the Center's major facilities, and
> possibly a detailed briefing on NASA's programs or projects.

d.  [Designated Area]{.underline}. A country of special concern or
    interest for the reasons identified in NPG 1371.2, Appendix A.

406.5 [VISIT REQUEST PROCEDURES]{.underline}

> a\. All requests for a standard visit, nonstandard visit, and/or VIP
> tour should be submitted, in writing, to the KSC IVC. Requests may be
> sent by e-mail, fax, or through the mail (e-mail is preferable).
>
> b\. Requests should be complete and contain the following information:
>
> \(1\) Full Name
>
> \(2\) Date and Place of Birth (City and Country)
>
> \(3\) Citizenship
>
> \(4\) Passport/Visa Number, Date and Place Issued
>
> \(5\) Passport/Visa Expiration Date
>
> \(6\) Visa Type (i.e., B-1, H1-B, etc.)
>
> \(7\) Social Security Number (if applicable)
>
> \(8\) Company Affiliation
>
> \(9\) Company Address
>
> \(10\) KSC Point of Contact and Telephone Number
>
> \(11\) Dates of Visit
>
> \(12\) Areas to be visited
>
> \(13\) Accreditation information, if known (i.e., international
> program or project, responsible accrediting Center).
>
> \(14\) Detailed justification for visit (include whether visitor will
> have access to computers, data to be disclosed, etc.).
>
> c\. An Export Control Plan is to be provided by the Requester for
> Center Export Authority (CEA) review and approval on all visits in
> excess of thirty (30) days or the individual is a frequent visitor,
> and when the visitor is from a Designated Country (regardless of visit
> duration).
>
> d\. The request will be reviewed by the IVC.
>
> \(1\) If the request is for an individual from a designated area and
> is not on an approved Center accreditation list, the request will be
> forwarded to the Office of External Relations, NASA Headquarters, for
> approval.
>
> \(2\) If the visitor is on an approved Center accreditation list, the
> IVC will continue processing the request. If/when the visit is
> approved, the IVC will inform the VRC to set up a Temporary Pass for
> the visit, and notify Requester of the approval and that a Temporary
> Pass has been set up. The IVC will also notify the Requester as to
> whether or not the visitor has to be escorted into controlled areas
> and any other pertinent information for the visit.
>
> \(3\) If the visitor is not on an approved Center accreditation list,
> the IVC will process the visit request through the Chief Export
> Administrator and the Center Export Counsel for review.
>
> e\. If the request is denied, the IVC will advise the Requester that
> the request was denied.
>
> f\. Requesters must allow sufficient time to permit processing of
> requests.
>
> \(1\) Short-term visit requests (1 to 30 days in duration) will be
> reviewed by the IVC and approved or disapproved within 10 working days
> (2 weeks).
>
> \(2\) Long-term visit requests (longer than 30 days) will be reviewed
> by the IVC and approved or disapproved within 20 working days (4
> weeks).
>
> \(3\) VIP tour requests will be handled as expeditiously as possible.
>
> \(4\) Short-notice visit requests will normally be denied. Emergency
> short-notice visits will be worked on a case by case basis.

406.6 [ACCESS AUTHORIZATIONS]{.underline}

> a\. Accredited FNs/FRs may receive a picture badge, or a Temporary
> Pass for up to one year. The picture badge must be retrieved each time
> the FN/FR leaves to return to their country. The Temporary Pass may be
> set up for short or long duration and may be renewed if an extension
> is necessary. The Accredited FNs/FRs may also have unescorted access
> to some controlled areas, providing safety training and operational
> needs are met and a KSC Form 20-181 (Foreign National Security
> Questionnaire) has been received by NASA Security.
>
> b\. FNs/FRs who are not accredited may be given a Temporary Pass for
> up to 180 days providing the visit has been approved.
>
> c\. The IVC, or designee, is the final approval authority on badging
> and access to KSC by FNs/FRs.
>
> d\. The IVC will notify the External Relations Office, NASA
> Headquarters, of the arrival and entry onto KSC of any
> accredited/non-accredited FN/FR visitor via an annual report.

406.7 [ACCREDITATION PROCESS]{.underline}

> a\. To establish an accreditation list, the KSC Program or Project
> manager for an agreed NASA international cooperative or reimbursable
> program or project must coordinate with the NASA/KSC IVC. The NASA/KSC
> IVC will ensure necessary coordination within the Center.
>
> b\. A satisfactory National Agency Check (NAC) must be completed for
> all individuals on an accreditation list. The KSC program or project
> manager will submit an accreditation list request to the NASA/KSC IVC.
>
> c\. The NASA/KSC IVC will coordinate with the other NASA Center
> (Security Offices) which may be required to host the listed visitors
> for program activities.

# 

# d. Accredited FNs/FRs may visit NASA/KSC as often and for such duration as the KSC program or project manager determines appropriate for the purpose of participating in the agreed program or project.

> e\. The number of foreign individuals to be accredited should be kept
> to a minimum, due to costs associated with the processing of a request
> and the cost of required investigations.
>
> f\. Visits and access must be conducted in accordance with the terms
> and conditions of the NASA international agreement that established
> the agreed program or project.
>
> g\. Program or Project Managers should inform the IVC if the
> accredited individuals may require access at any other NASA Center in
> order that the accreditation information may be used by other NASA
> Centers for the purpose of accrediting the same individual for other
> programs or projects.

406.8 [TOURS]{.underline}

> All tours with FN/FR participation will be processed through the KSC
> IVC. The KSC IVC will coordinate VIP tours (described in paragraph
> 406.4c) with the Office of External Relations, NASA Headquarters, and
> with the organization requesting the tour. The IVC will also
> coordinate any tours deemed appropriate with the CEA.
>
> This coordination should take place before the letter requesting tour
> credentials is processed through the Center Director's Office. It
> should be indicated in the credential request letter that coordination
> with the IVC has already taken place.
>
> The IVC will notify the Center Director's staff if a tour has been
> disapproved so credentials will not be issued.

406.9 [FOREIGN PUBLIC INFORMATION MEDIA]{.underline}

> Requests by, or on behalf of, foreign national members of the public
> information media to KSC or a component Facility must be forwarded
> promptly to the NASA Workforce & Diversity Management Office for
> coordination, as appropriate, with NASA Headquarters in accordance
> with 14 CFR Part 1213.

406.10 [DISCUSSIONS AND REQUESTS FOR MATERIALS]{.underline}

> Discussions with and documents provided to FN/FR visitors should be
> limited to information or documents authorized for public release, or
> specifically committed under an approved bilateral agreement. Outside
> presentations and papers for publication should have the approval of
> the Center Export Administrator.

406.11 [EXTENDING INVITATIONS TO VISIT NASA/KSC]{.underline}

NASA encourages visits by FNs/FRs of countries allied with/or friendly
to the United States. NASA employees may, with prior approval by NASA
Headquarters or the KSC IVC, extend invitations to FNs/FRs of countries
other than those identified as designated areas in Appendix A. No
invitation to visit NASA/KSC may be extended to FNs/FRs of any
designated areas without the prior written approval of the Office of
External Relations, NASA Headquarters.

406.12 [VISITS TO MERRITT ISLAND LAUNCH AREA (MILA) SPACECRAFT TRACKING
DATA NETWORK (STDN) STATION, FLORIDA]{.underline}

Foreign visit requests for this area will be processed in the same
manner as previously stated in this Chapter. When a visit is approved,
the IVC will notify the Station Director in addition to the Requester
and VRC.

**CHAPTER 407**

**SECURITY MEASURES**

407.1 [GENERAL]{.underline}

> a\. Security measures are instituted on KSC and at KSC-controlled
> facilities worldwide to control and protect assets from unauthorized
> access, damage, destruction, compromise, or theft, by the application
> of physical security measures and procedures. These measures are
> utilized to provide appropriate levels of protection to assets based
> upon their value, both by replacement or procurement cost or value to
> the Space Shuttle Program based upon an understanding of the
> postulated threat.
>
> b\. Other chapters of this handbook will deal specifically with
> security measures which are appropriate for controlling vehicles,
> transporting materials, port and harbor security, lock and key
> accountability, security forces, crisis management, and law
> enforcement liaisons. Accountability standards for Government and
> contractor property are contained in the KMI 4000 series. References
> to other documents are intended to provide the user with all the
> necessary information to make the best decisions.

407.2 [SECURITY AREAS]{.underline}

> a\. NASA, and NASA Security at KSC, recognize three levels of security
> (restricted, limited, and closed areas). Basic security measures
> appropriate for each security level are listed below:
>
> \(1\) [Restricted]{.underline}. This encompasses all areas within the
> Kennedy Space Center boundary including areas temporarily or
> permanently open to the public, limited areas, and closed areas. For
> example, the area inside the outermost gate is a restricted area (NASA
> has the authority to refuse admittance at that point), but no formal
> documentation is necessary to allow access. Access to this area does
> not constitute access to a security interest.
>
> \(2\) [Limited]{.underline}. These areas are ones which are within the
> restricted areas, are normally closed to the public, and may contain a
> closed area. These are areas for which some type of approval must be
> obtained for entry and this approval must be documented, either
> through recognition of an approved badge or through issuance of a
> temporary (machine or special event) pass. Access to these areas,
> which in some instances may be tenant controlled, may provide access
> to a security interest.
>
> \(3\) [Closed]{.underline}. These are areas which are within the
> limited areas and are a security interest. Access to these areas
> provides access to a security interest. Beyond mere approval for
> access, one must actually have a need to be in the area, as
> substantiated by appropriate authorities.
>
> b\. These classifications of security areas provide concentric circles
> of security around the security interests of NASA, payload customers,
> and other tenants of KSC.

407.3 [ACCESS CONTROLS]{.underline}

> a\. Access to KSC operational areas will be limited to the minimum
> number of required and properly cleared personnel. Personnel access
> will be controlled by one or more of the methods identified in Chapter
> 506 of this handbook.
>
> b\. [Normal Access to Security Areas]{.underline}. Chapter 404 and 405
> of this handbook details the NASA badging and KSC Area Permit systems.
>
> c\. [Access to Payloads.]{.underline} Access to payloads will be in
> accordance with procedures outlined in individual Payload Security
> Plans.

407.4 [PERIMETER AND AREA PROTECTION AND CONTROL]{.underline}

> a\. The security measures appropriate for the Center perimeter at KSC
> will generally be minimal in nature, realizing it's remoteness from
> identified security interests. At the Center perimeter, the purpose is
> to delineate the property boundary and to inform would-be intruders
> they are entering NASA-owned property. This may be accomplished by
> utilization of fencing and signs or just signs. (Standards for
> perimeter fencing and the posting of
>
> signs are contained in Chapter 408 of this handbook.) As a minimum,
> signs will conform to the State of Florida standard for trespass
> signs. In the case of the perimeter being formed by a shoreline, no
> signs are necessary.
>
> b\. Limited and closed areas, in which critical/essential assets
> within the Center are or may be further controlled by security
> measures implemented by the NASA Resource Protection Plan (K-SF
> 0005.7). Assets of lesser value/importance are protected by measures
> deemed appropriate by the NASA Security, based upon an onsite analysis
> of risks and threats to the security of the asset. Protection will
> include utilization of fencing; protective lighting; a sound lock and
> key control system; badging and temporary area authorization; package,
> material, and vehicle control; positive accountability procedures for
> all nonexpendable property (regardless of value); closed-circuit
> television; Physical Security Plan, and other means approved by NASA
> Security.

\* 407.5 [NASA RESOURCE PROTECTION PROGRAM]{.underline}

> The National Resource Protection (NRP) Program was initiated by NMI
> 8610.19, dated March 31, 1984. That NMI was superseded and replaced by
> NPG 1620.1, which establishes the Agency-wide NASA Resource Protection
> (NRP) Program. Implementation of that program at KSC is by separate
> documentation, the KSC NRP Plan.

407.6 [INSPECTION OF PERSONS AND PERSONAL EFFECTS ON NASA
PROPERTY]{.underline}

> a\. NASA will provide appropriate and adequate protection or security
> for facilities, property, and information in their custody or
> possession. In furtherance of this policy NASA/KSC reserves the right
> to conduct an inspection of any person, including any property in the
> person\'s possession or control, as a condition of admission to, or
> continued presence on any NASA installation.
>
> b\. Inspections pursuant to this paragraph will be conducted by
> NASA/KSC security personnel or by members of the installation's
> contracted security forces.
>
> c\. Inspections will be conducted in accordance with the provisions of
> 14 CFR Part 1205, Subpart 10. (See reference in Chapter 408, section
> 408.7c.)

**CHAPTER 408**

**PROTECTIVE BARRIERS AND OPENINGS**

408.1 [PROTECTIVE BARRIERS AND OPENINGS]{.underline}

> a\. [Purpose]{.underline}. To establish minimum criteria for physical
> security barriers and openings at KSC. However, Space Transportation
> System (STS) facilities, hardware, and operations when under the
> provisions of the NASA Resource Protection Program must meet specific
> criteria. Physical barrier requirements are designed to deny, impede,
> or discourage access to security areas by unauthorized personnel or
> groups. This is accomplished by one or more of the following:
>
> \(1\) Defining the perimeter of security areas.
>
> \(2\) Creating a physical and psychological deterrent to entry as well
> as \"making a legal statement\" that entry is not permitted.
>
> \(3\) Delaying intrusion into security areas, thus making more likely
> the detection and apprehension of intruders by protective forces.
>
> \(4\) Facilitating effective and economical utilization of protective
> forces.
>
> \(5\) In addition, physical barriers serve the purpose of directing
> the flow of personnel and vehicles through designated portals in a
> manner which permits efficient operation of the personnel
> identification and control system.
>
> b\. [Types of Barriers.]{.underline} Protective barriers are divided
> into two major categories: natural and structural.
>
> \(1\) Structural barriers are manmade devices such as fences, walls,
> floors, roofs, grilles, bars, road blocks, or other structures which
> deter penetration.
>
> \(2\) Natural barriers include forests, rivers, swamps, beaches, or
> other terrain difficult to traverse.
>
> c\. [General Consideration]{.underline}. Established physical security
> barriers at KSC are not designated to stop a determined intruder but
> rather to deter or delay. Therefore, such barriers, depending on area
> security, should be augmented by security personnel. When planning or
> in the establishing of security barriers at KSC, NASA Security shall
> be notified for assistance and advice. NASA Security shall consider
> the following prior to recommending security barriers:
>
> \(1\) Physical barriers, which are as personnel-proof as economically
> feasible, should be established around all security areas. The type of
> barrier used should be determined after a study of local conditions by
> NASA Security.
>
> \(2\) In some instances, the temporary nature of the security interest
> makes the construction of costly permanent physical barriers
> impracticable and unjustifiable. In such cases, the security interest
> must be protected by other means, such as use of temporary barriers,
> additional protective forces, patrols, and other compensating
> protective measures.
>
> \(3\) In cases of extreme criticality and vulnerability of KSC
> facilities, it may be necessary to establish two lines of physical
> barriers at the security area to be protected.
>
> \(4\) The immediate boundaries of KSC or a specific security area
> should be fenced and/or posted as a security area. As a minimum, two
> or more strands of barbed wire with \"No Trespassing\" signs with
> appropriate prosecution warnings attached not more than 500 feet apart
> along, and at each corner of, the boundaries of the land will suffice.
> This defines the perimeter, provides a buffer zone, facilitates
> control, and makes accidental intrusion unlikely.
>
> \(5\) In establishing any perimeter barrier at KSC, due consideration
> must be given to providing emergency entrances and exits in case of
> fire.
>
> \(6\) The size of a security area will depend on the degree of
> sensitivity required and the complexity of the area. As a rule, size
> should be kept to a minimum consistent with operational efficiency.
> Positive barriers at KSC shall be established for:
>
> \(a\) Controlling vehicular and pedestrian traffic flow.
>
> \(b\) Checking identification of personnel entering or departing.
>
> \(c\) Defining a buffer zone for more highly classified areas.
>
> \(7\) KSC\'s geographical and environmental characteristics,
> specifically water and swamp boundaries, present special security
> problems. Such areas at KSC should be defined by appropriate signs,
> buoys, booms, etc. Boat patrols may be required at KSC where
> mission-critical assets, essential facilities, or areas which are
> otherwise essential to the mission are located near inland or coastal
> waters. In inclement weather, such patrols may not provide an adequate
> degree of protection and must be supplemented by other means.
>
> \(8\) Construction of new security barriers and removal of existing
> barriers and related work must be approved by NASA Security and
> scheduled to provide a continuous level of security for the
> activity/program.
>
> d\. [Temporary Barriers]{.underline}. In some instances, the temporary
> nature or infrequent existence of a sensitive program/project
> requiring security constraints does not justify the construction of
> more permanent physical perimeter barriers. In such cases, a
> KSC-designated limited area or closed area of temporary nature and
> short duration may be established in which the reduction of security
> resulting from deficiencies in physical barriers is compensated for by
> additional security forces, patrols, and other security measures
> during the period of restriction. KSC barricade requirements are
> outlined in paragraph 408.2 below. In any case, a designated temporary
> security area will not exceed 30 days from date of installment without
> specific authorization from NASA Security. The use of wire barriers or
> similar construction for temporary enclosures is recommended as being
> both expeditious and effective with a minimum use of security forces
> required to control and safeguard the area.

408.2 [BARRICADE CLASSIFICATION AND SPECIFICATIONS]{.underline}

> a\. Barricades on KSC are permanently erected installations that
> control access through highways, trails, secondary roads, railways,
> construction sites, etc. Many barricades serve as a controlling
> barrier to the Impact Limit Line (ILL) or into critical operation
> areas. Barricade markings (i.e., traffic warning devices) vary
> depending on the location of the barricade.
>
> b\. In an attempt to ensure that proper barricade-marking and
> motorist-warning devices are installed on any barricade that is
> erected, the following barricade classifications and specifications
> are furnished.
>
> \(1\) [Class A is defined as]{.underline}: When a major arterial
> highway is temporarily closed to traffic because of operational
> requirements (i.e., emergency situations, disasters, etc.). The
> barrier will consist of:
>
> \(a\) Three rails marked in alternate red and white stripes sloping
> downward at a 45-degree angle in both directions toward the center of
> the barricade.
>
> \(b\) Red light rotating at 360 degrees.
>
> \(c\) Supplemental warning signs, reflecting: ROAD CLOSED 1000 FEET
> AHEAD and ROAD CLOSED 500 FEET AHEAD, placed at the appropriate
> distance preceding the barricade.
>
> \(d\) NASA RESTRICTED AREA/NO TRESPASSING sign.
>
> \(e\) Stop sign measuring 30 inches across.
>
> \(f\) Three red reflectors attached to the gate posts facing traffic.
>
> \(2\) [Class B is defined as]{.underline}: A road or street adjacent
> to a major arterial highway that is frequently traveled but may be
> temporarily or permanently closed. The barrier will consist of:
>
> \(a\) Two rails marked in alternate red and white stripes sloping
> downward at a 45-degree angle in both directions toward the center of
> the barricade.
>
> \(b\) Red light rotating at 360 degrees.
>
> \(c\) Supplemental warning signs, reflecting ROAD CLOSED, placed 500
> feet preceding the barricade or on the barricade, as appropriate.
>
> \(d\) NASA RESTRICTED AREA/NO TRESPASSING sign.
>
> \(e\) Stop sign measuring at least 30 inches across.
>
> \(f\) Three red reflectors attached to gate posts facing traffic.
>
> \(3\) [Class C is defined as:]{.underline} A secondary road, street,
> or trail that is normally open but may warrant temporary closure. The
> barrier will consist of:
>
> \(a\) Two rails marked in alternate red and white stripes sloping
> downward at a 45-degree angle in both directions toward the center of
> the barricade.
>
> \(b\) Supplemental warning sign, reflecting ROAD CLOSED, placed on the
> barricade.
>
> \(c\) NASA RESTRICTED AREA/NO TRESPASSING sign.
>
> \(d\) Stop sign measuring 30 inches across.
>
> \(e\) Three red reflectors attached to gate posts facing traffic.
>
> \(4\) [Class D is defined as:]{.underline} A secondary road, street,
> or trail that is normally closed to all traffic. The barrier will
> consist of:
>
> \(a\) One rail marked in alternate red and white stripes sloping
> downward at a 45-degree angle in both directions toward the center of
> the barricade.
>
> \(b\) NASA RESTRICTED AREA/NO TRESPASSING sign.
>
> \(c\) Stop sign measuring at least 30 inches across.
>
> \(d\) Three red reflectors attached to gate posts facing traffic.
>
> **[Note:]{.underline}** Individual barricade specifications may
> deviate due to frequency of roadway use, operational requirements, or
> other considerations.

408.3 [SECURITY FENCES]{.underline}

> a\. [Security Fences.]{.underline} Security fences at KSC should
> enclose all designated security areas and be constructed in such a
> manner that they should be reasonably impassable. The nature of the
> security area will determine the degree of restriction of movement of
> personnel, vehicles, and equipment necessary for adequate security.
> NASA Security must approve all security fence requirements and, prior
> to approval, will assess the permanency of the security area,
> availability of materials, presence of natural aids to security, KSC
> security personnel, security vulnerabilities, and the degree of
> security required.
>
> b\. [Security Fence Standards]{.underline}. Chain link fencing will be
> the type of structural barrier most commonly used and recommended for
> security purposes at KSC and should enclose all designated security
> areas. The following security fence standards apply.
>
> \(1\) [Fabric]{.underline}. The standard fence fabric will be at least
> 9-gauge zinc-or aluminum-coated steel-wire-chain link with mesh
> openings not larger than 2 inches per side and a twisted and barbed
> selvage at top and bottom.
>
> \(2\) [Fabric ties.]{.underline} Only 9-gauge-steel ties with coating
> compatible with the fabric will be used. In lieu of wire ties on fence
> posts, approved fabric clamps can be used. In lieu of wire ties on
> bottom and top taut wires, hog clamps may be used.
>
> \(3\) [Height.]{.underline} The standard height of a security fence is
> 8 feet. This includes a fabric height of 7 feet, plus a one-foot
> topguard. Building connections will need to be higher. Fencing 12 feet
> high from the connection point of the building out away 12 feet from
> the building is directed.
>
> \(4\) [Fencing Posts, Supports, and Hardware]{.underline}. All posts,
> supports, and hardware for security fencing will meet the requirements
> of Federal Specification RR-F-191K/GEN of May 14, 1992. All fastening
> and hinge hardware will be secured in place by peening or spot welding
> to allow proper operation of components, but prevent disassembly of
> fencing or removal of gates. Fence posts will be set in concrete and
> crowned for water runoff. All posts and structural supports will be
> located on the inner side of the fencing. Posts will be positively
> secured into the soil to prevent shifting, sagging, or collapse. Fence
> posts should be placed no more than 10 feet apart.
>
> \(5\) [Reinforcement.]{.underline} Taut reinforcing wires (at least 9
> gauge) will be woven through, or affixed with, the fabric along the
> top and bottom of the fence for stabilization of the fence fabric. For
> added resistance to climbing, top rails should not be used.
>
> \(6\) [Ground Clearance]{.underline}. The bottom of the fence fabric
> must be within 2 inches of firm soil or buried sufficiently (concrete
> footings or gravel may be used) in soft soil to compensate for
> shifting soil.
>
> \(7\) [Culverts and Openings]{.underline}. Culverts under or through a
> fence shall be of 10-inch pipe or of clusters of such pipe or
> equivalent. Openings under or through a fence will be secured with
> material equal or greater in strength than the overall barrier.
>
> \(8\) [Fence Placement]{.underline}. No fence will be located so that
> the features of the land (its topography) or structures (buildings,
> utility tunnels, light and telephone poles, fire escapes, ladders,
> etc.) defeat its purpose by allowing passage over, around, or under
> the fence.
>
> \(9\) [Topguards]{.underline}. Topguards are constructed on perimeter
> fences and may be added on interior enclosures for additional
> protection. A topguard is an overhang of barbed wire along the top of
> a fence, facing upward and inward, at approximately a 45-degree angle.
> Topguard supporting arms will be permanently affixed to the top of
> fence posts to increase the overall height of the fence at least 1
> foot. Three strands of 12-gauge barbed wire, spaced no more than 6
> inches apart, must be installed on the supporting arms. The topguard
> of fencing adjoining gates may range from a vertical height of 18
> inches to the normal 45-degree **inward** protection, but only for
> sufficient distance along the fence to open the gates adequately.
>
> \(10\) [Barriers]{.underline}. Buildings, structures, waterfronts, and
> other barriers used instead of (or as a part of) a fence line must
> provide equivalent protection to the fencing required for that area.
> Therefore, all windows, doors, and other openings or means of access
> must be guarded or properly secured.

408.4 [WALLS]{.underline}

> Where walls, floors, or roofs serve as barriers, they should be
> constructed and arranged to provide uniform protection equivalent to
> that provided by chain link fencing as specified. In this connection,
> windows and other openings in perimeters of security areas in any of
> the following categories should be protected by securely fastened
> bars, grills, or other equivalent structural means.
>
> a\. Openings less than 18 feet above uncontrolled ground, roofs,
> ledges, etc.
>
> b\. Openings less than 14 feet directly or diagonally opposite
> uncontrolled windows in other walls, fire escapes, roofs, etc.
>
> c\. Openings less than 6 feet from uncontrolled openings in the same
> wall.

408.5 [PERIMETER OPENINGS]{.underline}

> a\. Openings in KSC perimeter barriers will be kept to the minimum
> necessary for the safe and efficient operation of the Center. NASA
> Security will approve all openings. Authorized KSC barriers shall be
> constantly locked, controlled by authorized personnel, or otherwise
> secured to prevent unauthorized entry or exit. Those areas which
> cannot be secured because of safety/fire hazards may be secured
> utilizing lead seals. When locked and not under constant surveillance,
> they shall be subject to periodic checks by KSC protective forces or
> other designated personnel.
>
> b\. [Gates]{.underline}. Gates at KSC are designed to facilitate the
> entrance and exit of authorized traffic and to control its flow. NASA
> Security will approve gate operations and designations.
>
> \(1\) [Number and Location.]{.underline} Designated gates at KSC will
> be limited to the number consistent with efficient operations. Such
> factors as the centers of activity, and personnel and vehicular
> traffic flow inside and outside the area should be considered in
> locating gates. Alternative gates, which are closed except during peak
> movement hours, may be provided, so that heavy traffic flow can be
> expedited. When open or operating, all gates will be under continuous
> positive control. They will provide protection equivalent to the outer
> fences or barriers of which they are a part when not in use. These
> gates will be locked to form an integral part of the established
> perimeter when secured.
>
> \(2\) [Pedestrian Gates.]{.underline} Approved pedestrian gates and
> turnstiles will be channeled in such a manner that allows only one
> person entering or departing to approach the custodial sentry at a
> time. Some channels may be closed between rush hours. Where possible,
> pedestrian and vehicular gates should be clearly separated.
>
> \(3\) [Vehicular Gates]{.underline}. KSC-approved vehicular gates will
> be set well back from any public highway in order that temporary
> delays caused by identification control checks at the gate will not
> cause traffic hazards extending out onto a public highway. There will
> also be sufficient space at the gate to allow for spot checks,
> inspections, searches, and temporary parking of vehicles but not
> impede the flow of traffic.
>
> \(4\) [Inspection.]{.underline} When gates are not in active use and
> controlled by a KSC Patrol Officer, gates, turnstiles, and doors in
> the perimeter barrier will be locked and frequently inspected by
> J-BOSC Security patrols. Locks will be serviced and/or rotated at
> least annually. NASA Security will assure security and accountability
> for the keys to locks on these gates.
>
> c\. [Doors, Windows, and Skylights]{.underline}. Building or egress
> doors on KSC or secure area perimeter will provide the protection
> (e.g., metal doors, secure hinges, fastened pins, or inside heavy duty
> hasps and staple set) commensurate with the requirement for proper
> protection of the assets accessible through those doors. Windows,
> skylights, and other openings which penetrate the perimeter barrier
> and have a security mesh or grating area of 96 square inches or
> greater will be protected by securely fastened steel framed security
> mesh, framed and permanently bolted to the structure or other
> comparable measures. Such openings are inaccessible to personnel when
> they are 18 feet or more above ground level and 14 feet or more
> distant from buildings, structures, etc., outside the perimeter.
> Protective screens have the additional value of preventing missiles;
> such as, hand grenades, bombs and incendiaries, from being hurled
> through the windows from outside the perimeter.
>
> d\. [Sewers, Culverts, and Other Utility Openings.]{.underline}
> Sewers, air intakes, exhaust tunnels, and other utility openings which
> penetrate the perimeter or security area barrier and have cross
> section area of 96 square inches or greater will be protected by
> securely fastened bars, grilles, locked manhole covers, or other
> equivalent means which provide security commensurate to that of the
> perimeter or security area barrier. Bars and grilles across culverts,
> sewers, storm sewers, etc., are a hazard when susceptible to clogging.
> This hazard must be considered during planned construction of such
> bars and grilles. All such areas will be designed to permit rapid
> clearing or removal of grating when conditions require such action.
> Removable grates will normally be locked in place.
>
> e\. [Utility Poles and Trees]{.underline}. These obstructions located
> outside or inside of and within 10 feet of the perimeter barrier of
> the security area present a possible means of illegal entry. To reduce
> this possibility, the perimeter barrier will be staggered to increase
> the distance to more than 10 feet and heightened to the extent
> necessary to prevent entry. Otherwise, the hazard must be removed.
> Should these utility poles, signboards, trees, etc., also obstruct the
> visibility of the KSC security officer, they must be moved (or
> removed) at least 10 feet outside the perimeter barriers.
>
> f\. [Clear Zones]{.underline}.
>
> \(1\) Designated security areas and protective barriers at KSC shall
> maintain unobstructed areas or clear zones. The unobstructed areas or
> clear zones should be maintained on both sides of and between physical
> barriers. This shall be accomplished by removal of all trees, brush,
> rock piles, etc., within the designated zone and the frequent cutting
> of vegetation or the use of chemicals designed to control or kill such
> vegetation. Vegetation will not exceed 8 inches in height. These areas
> will be kept free of vehicles, structures, and debris.
>
> \(2\) Protective barriers inside a clear zone should be at least 10
> feet from the perimeter. Where possible and when the sensitivity of
> the activity requires a larger clear zone, it should be provided to
> preclude/minimize damage from thrown objects such as incendiaries or
> bombs.
>
> \(3\) Protective barriers outside clear zones will be 10 feet or
> greater from the perimeter fence/protective barrier and any exterior
> structures, vegetation, or any obstruction to visibility. Construction
> of any new protective barrier for KSC operations having a smaller
> clear zone must be approved by NASA Security. While 10 feet is the
> permissible criteria for KSC, every effort shall be made to establish
> a clear zone external to the protective barrier of 75 feet.
>
> \(4\) The minimum KSC standard clear zone for effective surveillance
> of the perimeter terrain in planning new activities or expansion of
> existing activities is 10 feet inside the barrier, 10 feet between
> barriers/fences, and 10 feet exterior to the boundary fence.
>
> \(5\) In addition to security, these clear zones also provide the
> safety feature of a 60-foot-wide fire break between KSC\'s operational
> areas, structures, or storage facilities and the adjoining areas. It
> is especially important to maintain clear zones during periods of high
> fire risk.

408.6 [INSPECTION OF BARRIERS]{.underline}

> J-BOSC Security or other designated personnel will periodically check
> designated barriers for defects that would facilitate unauthorized
> entry and report them to NASA Security. Both J-BOSC Security and KSC
> personnel must be alert to detect the following:
>
> a\. Damaged areas (cuts in fabric, broken posts).
>
> b\. Deterioration (corrosion).
>
> c\. Erosion of soil beneath the barrier.
>
> d\. Loose fitting barbed wire, outriggers, or fabric fasteners.
>
> e\. Growth in the clear zones that would afford cover for possible
> intruders.
>
> f\. Obstructions at or on the fence which would afford concealment or
> aid entry/exit for an intruder.
>
> g\. Evidence of illegal or improper entry.
>
> h\. Damaged or tampered lead seals in place.

408.7 [SIGNS AND POSTING OF BOUNDARIES]{.underline}

> The boundaries of KSC shall be posted with signs having the wording
> \"RESTRICTED AREA - NO TRESPASSING\" (NASA Form 1506) in 2-inch
> red/black letters. Signs will be located on the exterior side of KSC
> perimeter barrier or mounted on posts along the boundary line. The
> interval between signs will be adequate to permit at least one sign
> visible and legible during daylight hours to anyone approaching the
> boundary from outside KSC. All KSC designated security areas or spaces
> shall be plainly identified by signs reading \"RESTRICTED AREA,\"
> \"LIMITED AREA,\" or \"CLOSED AREA.\" These signs shall further bear
> in small lettering the words, \"Unauthorized Persons Who Enter May be
> Subject to Prosecution Under 18 U.S.C. 799.\" Signs will be placed on
> the outward edge of the clear zone or security areas and on the
> perimeter fence. The purpose of this placement is to prevent
> unintentional approach to the security area barrier through the clear
> zone. Spacing of signs shall be such that a sign will be visible and
> legible to anyone approaching the security area from any direction.
> All roads approaching the security area shall be clearly posted with
> restrictive entry signs. The requirements contained herein are
> considered the minimum acceptable; KSC elements may use additional
> signs to indicate restrictive entry so long as the following
> conditions are not violated.
>
> a\. At vehicle and pedestrian entry points at KSC, 4 feet by 4 feet
> signs will be posted with the following wording:
>
> **Warning**
>
> **Restricted**
>
> **By the Order of NASA**
>
> **Unauthorized Persons Who Enter May be Subject to Prosecution Under
> 18 U.S.C. 799.**
>
> The lettering size shall be proportional to the sign.
>
> b\. [Perimeter Barriers]{.underline} of all outdoor security areas
> will be posted with metal signs measuring 16 inches by 20 inches.
> Inside signs are cardboard, measuring 9 inches high by 12 inches wide
> with proportional lettering. On extended perimeters, signs will be
> posted every 300 feet. The signs will read: RESTRICTED AREA, LIMITED
> AREA, or CLOSED AREA by Order of NASA with appropriate prosecution
> statement as prescribed by 18 U.S.C. 799.
>
> \(1\) If the security area has a designated area authorization
> number/letter, then area authorization signs must be posted at every
> access point.
>
> \(2\) NASA Security, will procure and authorize the appropriate signs
> required for posting.
>
> c\. All entrances to NASA/KSC will be conspicuously posted with the
> following notice:
>
> **PURSUANT TO NASA REGULATIONS, THE ENTRANCE OF INDIVIDUALS TO, OR
> THEIR CONTINUED PRESENCE ON, THIS INSTALLATION IS CONDITIONED UPON
> THEIR CONSENT TO INSPECTION OF THEIR PERSONS, AND OF PROPERTY IN THEIR
> POSSESSION OR CONTROL.**
>
> **14 CFR Part 1205, Subpart 10**
>
> (See Chapter 407, Paragraph 407.6c)

**CHAPTER 409**

**PROTECTIVE LIGHTING**

409.1 [PROTECTIVE LIGHTING]{.underline}

> a\. [General]{.underline}. Protective lighting is to provide ample
> light during periods of darkness and low visibility to aid observation
> by security personnel. Lighting, generally, also has value as a
> deterrent to nondedicated intruders. Normally, security lighting
> utilizes less candle power than working area lighting, except at
> points of entry. Security lighting is utilized to increase
> effectiveness of guard systems and closed-circuit television (CCTV) by
> increasing the visual range of the guards and CCTV monitors during
> periods of darkness, or by increased illumination of an area where
> natural light does not reach or is insufficient. Exterior security
> lighting is advisable only to ensure a minimal level of visibility
> when guards are positioned to perform inspection duties properly
> around the exterior. Guards and CCTV monitors must be able to see
> people and badges at gates, inspect vehicles, stop attempts at illegal
> entry, detect intruders inside and outside buildings, and observe
> unusual or suspicious circumstances.
>
> b\. The Kennedy Space Center, due to it\'s physical layout, terrain,
> atmospheric conditions, mission, and the sensitivity of its
> operations, has specific security requirements with reference to
> protective lighting. NASA Security must approve all protective
> lighting requirements. Prior to the approval of such requests, a
> careful study of security requirements and energy conservation must be
> conducted by NASA Security and the Energy Management Office.
> Protective lighting should not be routinely specified for physical
> security, but should be considered as an option and compared to other
> interior lighting for detection and deterrence.
>
> The decision to utilize protective lighting must be based upon the
> following parameters:
>
> \(1\) Relative value of items being protected.
>
> \(2\) Significance of the items being protected in relation to
> accomplishment of the mission of the activity in general and it's role
> in the overall NASA structure.
>
> \(3\) Availability of security forces to patrol and observe
> illuminated areas.
>
> \(4\) Availability of fiscal resources (to procure and install
> lighting, and follow-on operating and maintenance costs).
>
> \(5\) Energy conservation.
>
> c\. [Protective Lighting Principles]{.underline}. When protective
> lighting is installed and utilized at KSC, the following basic
> principles will be applied to help its effectiveness:
>
> \(1\) Provide adequate illumination or compensating measures to
> discourage or detect illegal attempts to enter security areas and to
> reveal the presence of unauthorized persons within such areas.
>
> \(2\) Avoid glare which handicaps security force personnel or is
> objectionable to air, highway, or navigable water traffic or occupants
> of adjacent properties.
>
> \(3\) Locate light sources so that illumination is directed toward
> likely intruder avenues of approach and provides relative darkness for
> patrol roads, paths, and posts. To minimize exposure of security force
> personnel, lighting at entry points will be directed at the gate and
> the guard shall be in the shadows.
>
> \(4\) Illuminate shadowed areas caused by structures within or
> adjacent to security areas.
>
> \(5\) Design of the system should provide overlapping light
> distribution. Equipment selected will be designed to resist the
> effects of environmental conditions, and all components of the system
> should be located to provide maximum protection against intentional
> damage.
>
> \(6\) Should not draw unwanted attention to the security area.

409.2 [TYPES OF PROTECTIVE LIGHTING]{.underline}

> There are four types of lighting systems which may be approved for
> utilization at KSC. Specific requirements will depend on the overall
> security concerns. The four security lighting systems are:
>
> a\. [Continuous Lighting]{.underline}. Continuous lighting (stationary
> luminaries) is the most common security lighting system. It consists
> of a series of fixed luminaries arranged to flood a given area
> continuously during the hours of darkness with overlapping cones of
> light. The two primary methods of employing continuous lighting are
> glare protection and controlled lighting.
>
> \(1\) [Glare Projection Lighting]{.underline}. Glare lighting uses
> luminaries slightly inside a security perimeter and directed outward.
> The glare projection lighting method is useful where the glare of
> light directed across surrounding territory will neither annoy nor
> interfere with adjacent operations. It is considered a deterrent to a
> potential intruder because it makes it difficult for him to see the
> inside of the area being protected. It also protects the guard by
> keeping him in comparative darkness and enabling him to observe
> intruders at considerable distance beyond the perimeter.
>
> \(2\) [Controlled Lighting]{.underline}. The controlled lighting
> method is best used when it is necessary to limit the width of the
> lighted strip outside the perimeter because of adjoining property or
> nearby highways, railroads, navigable waters, or airports. In
> controlled lighting, the width of the lighted strip can be controlled
> and adjusted to fit a particular need; such as, illumination of a wide
> strip inside a fence and narrow strip outside, or floodlighting a wall
> or roof. Unfortunately, this method of lighting often illuminates or
> silhouettes security personnel as they patrol their routes.
>
> b\. [Standby Lighting.]{.underline} A standby lighting system is
> different from continuous lighting since its intent is to create an
> impression of activity. The luminaries are not continuously lighted,
> but are either automatically or manually turned on randomly or when
> suspicious activity is detected or suspected by the security force or
> IDS. Lamps with short restrike times are essential if this technique
> is chosen. This technique may offer significant deterrent value while
> also offering economy in power consumption.
>
> c\. [Movable Lighting]{.underline}. A movable lighting system
> (stationary or portable) consists of manually operated movable search
> lights which may be lighted during hours of darkness or lighted only
> as needed. This system normally is used to supplement continuous or
> standby lighting.
>
> d\. [Emergency Lighting]{.underline}. An emergency lighting system may
> duplicate any or all of the above systems. It's use is limited to
> times of power failure or other emergencies which render the normal
> system inoperative. It depends on an alternative power source such as
> installed or portable generators or batteries.

409.3 [SPECIFICATION OF ILLUMINATION]{.underline}

> The specific ways and means for illumination of security areas and
> other designated areas requiring protective lighting shall be under
> the provisions of the American National Standards Institute, Inc., and
> also in Appendix E of the NASA Resource Protection (NRP) Plan for KSC,
> as amended. The NRP Plan outlines specific security requirements for
> Space Transportation System facilities, hardware, and operations at
> KSC.

409.4 [EMERGENCY POWER]{.underline}

> KSC security areas provided with protective lighting should have an
> emergency power source located within that security area. The
> emergency power source should be adequate to sustain all security
> requirements and any other essential service required within the
> security area. The KSC security force will ensure the immediate
> availability of the emergency power in the event of the failure of the
> primary source. KSC security force personnel should be capable of
> starting emergency power equipment. If lack of technical knowledge
> prevents this, plans must provide for responsible personnel to respond
> immediately to start the equipment. In addition, battery-powered
> lights and essential communications should be available at all times
> at key locations within the security area in the event of a complete
> failure of both the primary and emergency sources of power.

409.5 [MAINTENANCE]{.underline}

> KSC-approved protective lighting systems should provide for simplicity
> and economy in maintenance and should require only a minimum of
> shutdown time, routine repairs, cleansing, and replacement.

409.6 [CONTROLS AND SWITCHES]{.underline}

> Controls and switches for protective lighting systems at KSC will be
> inside the protected area and locked and/or guarded at all times. High
> impact plastic shields will be installed over lights to prevent damage
> or destruction by stones, weapon fire, etc.

**CHAPTER 410**

**PORT AND HARBOR SECURITY**

410.1 [GENERAL]{.underline}

> This chapter provides protective measures, requirements, and guidance
> for all assets on terminals and waterways of KSC and other areas under
> KSC cognizance. It will be used to establish the minimum security
> protective measures but does not preclude unique or specific planning
> for individual or sensitive activities.

410.2 [RESPONSIBILITIES]{.underline}

> a\. [The Chief, Protective Services Branch is responsible
> for:]{.underline}
>
> \(1\) Approving protective measures to be used in the transportation
> of cargo under the cognizance of KSC to ensure appropriate safeguards
> are utilized.
>
> \(2\) Assuring that Resource Protection Surveys are conducted on each
> port, harbor, dock, boat, barge, or ship under KSC\'s cognizance, and
> that each is reevaluated in conjunction with critical operations, or
> under the direction of NASA Security.
>
> b\. [Heads of primary organizations are responsible for]{.underline}:
>
> \(1\) Ensuring that the provisions and recommendations of Resource
> Protection Surveys are implemented as policy as set forth in the
> surveys.
>
> \(2\) Ensuring that site managers, program managers, or contractor
> representatives provide notification to NASA Security of schedules,
> manifests, etc., pertaining to delivery of sensitive items or cargo.
>
> \(3\) Ensuring the assignment of a security point of contact for each
> port, harbor, or terminal.
>
> \(4\) Ensuring the development of a specific security plan for each
> port, harbor, dock, or vessel under KSC jurisdiction; and submitting
> this plan to NASA Security for review, and updated, if necessary,
> prior to each anticipated use of the location or vessel.
>
> \(5\) Ensuring that the following is accomplished as a minimum:
>
> \(a\) Document orders, manifests, requisitions, etc., detailing what
> has been ordered, how it is to be transported, and when and where it
> is to be delivered.
>
> \(b\) Maintain accountability and recording of disposition of cargo.
>
> \(c\) Document all receipt, storage, and maintenance of cargo.
>
> \(d\) Identify and report to the Joint Communications Control Center,
> 867-2121, NASA Security, 867-2455, and NASA management, any shortages
> or recovery at all levels of accountability.
>
> \(e\) Ensure the completion of scheduled and nonscheduled audits of
> all transportation records by cognizant offices.
>
> \(f\) Train cognizant personnel in loss prevention and security
> awareness.
>
> \(g\) Ensure that appropriate measures are taken for dealing with
> receipt or shipment of arms, munitions, pyrotechnics, or ordnance.
>
> \(h\) Ensure that vehicles, containers, shipping bins, etc., are
> properly marked (origin and destination), sealed, and locked where
> appropriate.
>
> \(i\) Ensure that proper physical security measures (including alarms,
> CCTV, etc.) are in place at receipt, shipping, and storage areas.
> Facilities will be designed so as to afford the required level of
> protection for the most sensitive operations that take place at the
> facility.
>
> \(j\) Protect sensitive information concerning sensitive shipments.

3.  [SENSITIVITY]{.underline}

> a\. The sensitivity of cargo/vessels encountered at the waterway
> terminals, vessels of KSC, and those under the jurisdiction of KSC
> will fall into categories as defined by the NASA Resource Protection
> Plan for KSC (NPG 1620.3).
>
> b\. Certain items, such as nuclear material or classified hardware,
> require safeguards specified by other agencies or by Federal law. When
> prioritizing and planning security measures for specific cargo items,
> care must be taken to ensure that all requirements are satisfied. A
> systems approach to the protection of assets on or under the
> jurisdiction of KSC requires that a security planner recognize the
> interaction of all assets and security measures with each other.
>
> c\. Important distinctions can be made in each category, and this
> requires an individual assessment of each cargo item. These
> distinctions involve the mission being supported, the sensitivity of
> the items, the monetary or replacement value of the items, and its
> attractiveness to theft. The security required for an area will be at
> least the minimum security required for the most sensitive item
> contained therein.

410.4 [SAFEGUARDS AND SECURITY MEASURES]{.underline}

> At the KSC terminal end of the waterway, security will be maintained
> as specified in this handbook. These specifically apply to levels of
> lighting, types and placement of physical barriers, and the use of
> CCTV, IDAS, lock and key control, and security forces. Chapter 413 of
> this handbook, Transportation and Material Security, provides
> additional minimum requirements which must be met while material is in
> transit. In addition, the security point of contact identified above
> in paragraph 410.2 will make an assessment, on an individual basis, of
> each expected arrival by water. In cases of a critical or essential
> shipment, access control points and other area security measures will
> be established. The security of items on a given vessel while in
> non-KSC areas is the responsibility of the owner and crew of the
> vessel or the cognizant responsible NASA Center/facility. Safeguards
> on KSC include controlling the terminal area until the cargo is either
> removed and put ashore (in the case of arriving shipments) or loaded,
> secured, inventoried, and departed the jurisdiction of the KSC.

410.5 [TRANSPORTATION, ACCOUNTABILITY, AND DOCUMENTATION]{.underline}

> All matters pertaining to security during transportation and for
> auditing will conform to the specifications listed in this handbook,
> Chapter 413, Transportation and Material Security.

410.6 [SECURITY FORCES]{.underline}

> Security forces provided by J-BOSC will supply appropriate assistance
> by ensuring that properly trained and equipped guards are prepared to
> support operations at harbor/waterway access areas.

410.7 [HARBOR AND WATERWAY PATROL]{.underline}

> a\. The J-BOSC will maintain vessels to patrol the waterways and
> harbor terminals of KSC. Where necessary to exclude unauthorized boat
> traffic, booms, patrols, nets, alarm systems, or similar obstacles and
> appropriate warning signs may be placed in the water. These will be
> constructed so that J-BOSC Security, USF&WS, USCG, and other
> authorized vessels can gain access when needed.
>
> b\. The patrol craft should be equipped with at least one searchlight,
> a public address system, special emergency equipment, be specifically
> designated as a security vehicle, be provided continuous two-way radio
> voice communications capability with individual units ashore, and be
> constructed to afford seaworthiness and protection against inclement
> weather and sea conditions. The use of sonar, radar, and night vision
> devices is encouraged.

### CHAPTER 411

**TRAFFIC AND PARKING CONTROL**

411.1 [PURPOSE]{.underline}

> This chapter establishes provisions and procedures for the supervision
> of motor vehicle traffic and the Reserved Parking Program at KSC. The
> Reserved Parking Program is also applicable to those areas of CCAFS
> occupied by NASA.

411.2 [GENERAL]{.underline}

> a\. This chapter covers all moving and non-moving traffic regulations,
> the required crash reporting procedure, and the issuance of traffic
> citations on Kennedy Space Center. It will provide guidelines for the
> movement of flight hardware and over dimensioned/overweight equipment,
> and movement against traffic.
>
> b\. This chapter directs the assessment of points against an
> individual\'s driving record in accordance with an established
> schedule. It also defines the procedure for appealing the issuance of
> a KSC citation or the suspension of driving privileges.
>
> c\. The \"Manual on Uniform Traffic Control Devices for Streets and
> Highways\" as published by the United States Department of
> Transportation (U.S. DOT) and the companion Florida DOT (FDOT) Manual
> are the documents governing all traffic control devices on Kennedy
> Space Center.
>
> d\. This chapter applies to civil service and contractor personnel
> (GS-15 or equivalent) requesting reserved parking spaces for private
> and/or government vehicles at KSC and in those areas of CCAFS occupied
> by NASA, and to designated contractor employees who are given duties
> and responsibilities relating to the issuance, control, and
> termination of such authority.

411.3 [MOVING/NON-MOVING TRAFFIC REGULATIONS]{.underline}

> a\. J-BOSC Security, under the direction and guidance of the Chief,
> Protective Services Branch, will be the single KSC organization
> responsible for the enforcement of all NASA and State of Florida
> Traffic Regulations. J-BOSC Security will also investigate all motor
> vehicle crashes and all matters related to the safe and efficient flow
> of motor vehicle traffic on KSC roadways. The J-BOSC will be
> responsible for the placement and maintenance of all official traffic
> control devices.
>
> Any KSC Organization which requires to detour, or deviation of
> standard traffic patterns on KSC, will be responsible for informing
> the Security Traffic Management Office, at least 30 days prior to the
> requirement.
>
> b\. Responsibilities:
>
> Heads of primary organizations, or their designees, will be
> responsible for:
>
> \(1\) Assuring that employees and their respective contract managers
> are cognizant of this handbook.
>
> \(2\) Assuring that all employees within their respective
> organizations adhere to the requirements contained in this handbook.
>
> \(3\) Upon notification from the Lead, NASA Security, taking
> appropriate administrative action against employees identified as
> habitual traffic offenders.
>
> c\. All personnel operating a motor vehicle upon the roadways of KSC
> must possess a motor vehicle driver\'s license recognized by the State
> of Florida as being a valid driver\'s license.
>
> d\. Drivers and owners of vehicles being operated on KSC will be in
> compliance with all Florida Statutes concerning licensing of drivers
> and Florida Financial Responsibility Laws at all times.
>
> e\. Persons committing a violation of a traffic regulation on KSC may
> be subject to the following:
>
> \(1\) They may be issued a Florida Uniform Traffic Citation (FUTC).
>
> \(2\) They may be issued a KSC Traffic Citation.
>
> \(3\) An Offense Incident Report, with supporting documents, may be
> filed with the State Attorney\'s Office requesting a warrant be issued
> for the arrest of the violator.
>
> \(4\) Suspension of driving privileges at the discretion of NASA
> Security.
>
> f\. Personnel with accumulated points against their driving record on
> KSC in accordance with the schedule shown in Figure 1, (page 411-5)
> will have their driving privileges suspended on KSC and by reciprocal
> agreement on CCAFS. The length of suspension time will be determined
> by the number of points accumulated during a particular time frame as
> defined in Figure 2, (page 411-6). Points accumulated as a result of a
> FUTC will be assessed in accordance with existing State law. Points
> assessed due to issuance of an FUTC may result in the suspension of
> state driving privileges.
>
> g\. Persons who witness a traffic violation on KSC when no law
> enforcement officer is present may file a written complaint with
> J-BOSC Security Operations.
>
> h\. Bicycles will be operated on KSC in compliance with Florida
> Statute Chapter 316.2065.
>
> i\. [Movement of Improperly Parked or Abandoned Vehicles to Impound
> Area]{.underline}
>
> \(1\) When a vehicle is improperly parked or abandoned
> [OR]{.underline} is creating a traffic hazard, the vehicle will be
> towed. If it is a GSA vehicle, a duplicate key may be obtained from
> GSA Motorpool.
>
> \(2\) The owner/driver is responsible for contacting J-BOSC Security
> to report their disabled/abandoned vehicle. A vehicle will be red
> tagged, defined as a "Red Tag" (KSC Form OT-2279), being placed on the
> owner's vehicle, by a Security Officer. The "Red Tag" explains to the
> owner that they have 72 hours to remove the vehicle or J-BOSC Security
> will have it towed.
>
> j\. [Parking Restrictions.]{.underline}
>
> Parking is not permitted on grassy areas, blocking driveways, adjacent
> to yellow marked curbs, in fire lanes, within 15 feet of a fire
> hydrant, posted \"No Parking\" areas, reserved spaces inscribed by
> name, position, permit, or organization, in spaces reserved for other
> types of vehicles, [or in any area on KSC not specifically designated
> for parking]{.underline}. Parking of vehicles is permitted on grassy
> areas when instructed by a J-BOSC Security Officer or if designated as
> overflow parking.
>
> Persons whose primary job assignments or offices are located within a
> building are not permitted to use that building's parking spaces
> reserved for visitors or Senior Management. Visitor and Senior
> Management parking spaces, are reserved for the use of persons
> visiting the building. Other persons using these spaces will be cited.

### TRAFFIC POINTS

Points against a person\'s driving record on KSC will be assessed in
accordance with the State of Florida, Department of Highway Safety and
Motor Vehicles guidelines. In addition, points will be assessed for the
following KSC violations:

[POINTS]{.underline}

\* 1. Moving violations resulting in a crash 4

\* 2. Reckless driving 4

\* 3. Speed in excess of 15 mph

over the posted speed limit 4

\* 4. Speed not in excess of 15 mph

over the posted speed limit 3

\* 5. All other moving violations 3

> 6\. Includes, but not limited to; failure to obey the directions of a
> Security Officer, or failure to
>
> obey an official KSC Traffic Regulatory sign 3

\* 7. Improper/defective equipment (brake lights,

headlights, reflectors, wiper blades, etc.) 2

> 8\. Includes, but not limited to; Violation of
>
> KSC parking regulation 1
>
> 9\. Failure to use seat restraints 1
>
> 10\. Includes, but not limited to; failure to properly process a KSC
> traffic citation 1

\* These violations are in accordance with Florida Statutes and are not
considered just a KSC violation. The violations not marked with an
asterisk (\*), are points assessed solely on KSC, and not Florida
Statutes.

FIGURE 1

**SUSPENSION**

Persons who accumulate sufficient points to cause their driving
privileges to be suspended will have their driving privileges suspended,
in accordance with the schedule below:

  -------------------------------- ---------- ---------------------------
  12 points accumulated within 12             30 days suspension
  months                                      

  18 points accumulated within 18             90 days suspension
  months                                      

  24 points accumulated within 36             1 year suspension
  months                                      

  Refusal to submit to an approved            12 months suspension
  breath alcohol test for a                   
  traffic-related offense                     

  Convicted of DUI by a Court of              1 year suspension (or the
  Law                                         Court-imposed suspension,
                                              whichever is greater)

  Driving while driving privileges            The Chief, Protective
  are suspended.                              Services, will request
                                              administrative action be
                                              taken against the defendant

  Failure to produce proof of                 KSC driving privileges will
  insurance                                   be suspended by the Chief,
                                              Protective Services Branch,
                                              until such proof is
                                              produced

  Reckless or careless operation              KSC driving privileges may
  of a Motor Vehicle                          be suspended, at the
                                              discretion of NASA Security
  -------------------------------- ---------- ---------------------------

FIGURE 2

411.4 [OVERWEIGHT/OVERDIMENSION EQUIPMENT/VEHICLES
AUTHORITY/ESCORT]{.underline}

> \* a. Movement of equipment/vehicles which exceed the maximum width,
> height, length, and weight criteria set forth in Chapter 316 of the
> Florida Statutes is authorized within the confines of KSC. The
> following criterion guidelines are to be observed for movement of over
> dimensional equipment/vehicles on KSC. (See Chapter 514, paragraph
> 514.3d(b).)
>
> \(1\) [Width]{.underline}:
>
> \(a\) All loads or vehicles that do not exceed the maximum height and
> length, but are between 8 feet, 6 inches (2.61 meters) and 10 feet
> (3.07 meters) wide will be flagged on each corner of the
> equipment/vehicle. No escort is required.
>
> \(b\) All loads or vehicles between 10 feet (3.07 meters) and 12 feet
> (3.69 meters) wide will be flagged on each corner of the
> equipment/vehicle and have \"Wide Load\" warning signs on the front
> and rear of the equipment/vehicle. No escort vehicle required.

c.  All loads or vehicles between 12 feet (3.69 meters) and 13 feet (4
    meters) wide will be flagged on each corner of the equipment/
    vehicle, have \"Wide Load\" warning signs on the front and rear of
    the equipment/vehicle, and will require one user escort vehicle. The
    escort vehicle will be in the front on a two-lane roadway and in the
    rear on a four-lane roadway. User escort vehicle must be equipped
    with an amber flashing light and an "Escort in Progress" sign
    visible to affected traffic. Lights will conform to Florida DOT
    trucking manual standards.

d.  All loads or vehicles over 13 feet (4 meters) wide will be flagged
    on each corner of the equipment/vehicle, have \"Wide Load\" warning
    signs on the front and

> rear of the equipment/vehicle, and will be escorted by two user escort
> vehicles. The escort vehicles will be in the front and rear of the
> load. User escort vehicle must be equipped with an amber flashing
> light and an "Escort in Progress" sign visible to affected traffic.
> Lights will conform to Florida DOT trucking manual standards.
>
> \(e\) All loads or vehicles that exceed 14 feet (4.3 meters) in width
> will be flagged on each corner of the equipment/vehicle, have \"Wide
> Load\" warning signs on the front and rear of the equipment/vehicle,
> and will be escorted by two (2) Security vehicles. Exemption to this
> requirement may be made on a case by case basis, or as specifically
> exempted in this handbook. Two-user escort vehicles may be used after
> approval by the J-BOSC Security Projects and Integration Office during
> normal working hours or the Shift Operations Office, after hours.
>
> \(f\) All loads or vehicles which oppose the flow of normal traffic
> will be flagged on each corner of the equipment/vehicle, and will be
> escorted by three Security vehicles. The Security escort vehicles will
> be in front and rear of the convoy.
>
> \(2\) [Height]{.underline}:
>
> \(a\) All loads or vehicles that exceed 13 feet, 6 inches (4.15
> meters) but are less than 16 feet (4.9 meters) in height will require
> one user escort vehicle. On a two-lane roadway, the escort vehicle
> will be in the front of the convoy. On a four-lane roadway, the escort
> vehicle will be in the rear of the convoy. User escort vehicle must be
> equipped with an amber flashing light and an "Escort in Progress" sign
> visible to affected traffic. Lights will conform to Florida DOT
> trucking manual standards.
>
> \(b\) All loads or vehicles that exceed 16 feet (4.9 meters) in height
> will require two user escort vehicles, one in front and one in the
> rear of the convoy. User escort vehicle must be equipped with an amber
> flashing light and an "Escort in Progress" sign visible to affected
> traffic. Lights will conform to Florida DOT trucking manual standards.
>
> \(c\) All loads or vehicles that exceed 13 feet, 6 inches (4.15
> meters) and must oppose traffic to bypass an overhead obstruction will
> be supported by two (2) Security vehicles for that portion of the
> convoy move.
>
> \(3\) [Overlength]{.underline}:
>
> \(a\) All loads or vehicles that exceed 60 feet (18.46 meters) in
> length but are less than 75 feet (23 meters) in length may travel on
> the KSC roadways system, but must be flagged on each corner of the
> equipment/vehicle and at the rearmost extension of the load. No escort
> required.
>
> \(b\) All loads or vehicles that are between 75 feet and 85 feet in
> length will be flagged at each corner of the vehicle and at the
> rearmost extension of the load. One user escort vehicle will be
> required. The escort vehicle will be in the rear of the convoy.
>
> \(c\) All loads or vehicles that exceed 85 feet in length will be
> flagged on each corner of the equipment/vehicle and at the rear-most
> extension of the load, and will require [two (2) Security escort
> vehicles or (2) user escort vehicles.]{.underline} Security
> concurrence must be obtained prior to user's escorting. The escort
> vehicles will be in front of and to the rear of the convoy.
>
> \(4\) [Weight:]{.underline}
>
> \(a\) The following gross weight limitation chart applies to the KSC
> roadway system for most loads/equipment:
>
> [1.]{.underline} NASA Causeway overpass - 80,000 lbs.
>
> [2.]{.underline} NASA Causeway Indian River Bridge - 80,000 lbs.
>
> [3.]{.underline} NASA Causeway Banana River Bridge - 80,000 lbs.
>
> [4.]{.underline} Kennedy Parkway (SR-3) Haulover Canal Bridge - 60,000
> lbs.
>
> \(b\) For all KSC operational support equipment that exceeds the above
> weight limits, a request must be submitted to the Facilities Division
> for a one-time move, or a blanket or permanent waiver.
>
> \(c\) Movement of overdimensional equipment/vehicles will not be
> permitted unless each movement is covered by a written authorization
> in the form of a Work Order, Support Request, Work Assignment,
> Shipping Order, etc. Each authorization shall constitute a \"special
> permit\" for the movement of such equipment/vehicles on KSC roads
> under Section 316.550 of the Florida Statutes. Prior to the actual
> move of such equipment/vehicles, J-BOSC Security (861-5657) will be
> contacted to ensure that the movement does not conflict with any other
> such movement. Movement during 0600-0800, 1500-1700 or 2300-2400,
> Monday through Friday, is prohibited. Exceptions will be reviewed on a
> case-by-case basis.
>
> b\. Other Escort Requirements:
>
> \(1\) Slow moving equipment/vehicles, as defined in FS 316.2045(1),
> must be in compliance with Florida Statutes while traveling on KSC
> roadways. Slow moving vehicles will have a "Slow Moving Vehicle" sign
> affixed to the rear of the equipment or vehicle. Slow moving vehicles
> will not be permitted on KSC roadways during the hours of 0600-0800,
> and 1500-1700, and 2300-2400 hours, Monday through Friday.
>
> \(2\) Escorting selected oversize items, flight hardware and mission
> critical astronauts on KSC roadways will be the responsibility of
> J-BOSC Security. Mission Critical astronauts will be escorted in the
> configuration outlined in J-BOSC Security mission unique Plans.
>
> \(3\) Flight hardware is defined as an item or piece of equipment
> which, when installed or attached, becomes an integral part of the
> Orbiter, external tank, SRBs, or cargo at launch. Flight hardware for
> the purpose of scheduling a security escort, will be that flight
> hardware (as defined) which is an element of the upcoming and the next
> subsequent launch. Security will normally escort Transcan/Strongback
> moves, satellite moves, explosive or hazardous material moves which
> present a danger if a mishap occurred, External Tanks (ETs), Space
> Shuttle Main Engines (SSMEs), Forward Reaction Control Systems (FRCS),
> Orbiter Maneuvering System (OMS) pods, APU/HPU carts, Solid Rocket
> Booster (SRB) aft skirts, Crew Transport Vehicle (CTV), Orbiter Tail
> Cone and SRB segments (except when transferring a segment between the
> RPSF and VAB). Spent SRB segments will be moved from CCAFS to KSC with
> 1 Lead J-BOSC Security Escort. Segments are transferred between the
> RPSF and VAB, by the user/contractor.
>
> \(4\) The user/contractor is expected to escort all other Shuttle
> Transportation System associated equipment, such as small payload
> elements or flight hardware that could fit into a standard size
> vehicle, non-oversize flown hardware, SRB segments between the RPSF
> and VAB, main chutes, forward skirts, nose caps, tail cone crates,
> 140, 250, and 300-ton cranes and Portable Purge Units (PPUs).
>
> \(5\) Satellites or oversize satellite equipment escorted off-center
> to the Astrotech or Spacehab facilities require three (3) Security
> units. Two positioned in front of the escort and one at the rear.
> Flight hardware escorted to Astrotech or Spacehab that is not oversize
> or does not need to travel against traffic shall be escorted by only
> two (2) Security units.
>
> \(6\) Late access experiments for STS missions will be escorted by the
> user or J-BOSC Security, if determined to be mission critical and time
> critical. Determination as to who will escort the late access
> experiments and the number of Escort Units will be made by J-BOSC
> Security, taking into consideration the time of day, amount of
> traffic, route taken, and threat assessment.

411.5 [CRASH REPORTING PROCEDURE]{.underline}

> a\. Any crash occurring on KSC property which involves a vehicle (as
> defined in this handbook) and property damage or injuries must be
> immediately reported to J-BOSC Security by the fastest means
> available, in accordance with Florida Statutes. The driver of a
> vehicle involved in a traffic crash should make every effect to move
> the vehicle to the side of the road to avoid blocking traffic.
>
> b\. A traffic crash investigator will conduct an investigation in
> accordance with Florida Statutes and submit a report as required by
> the State of Florida and/or NASA Security.
>
> c\. J-BOSC Security will maintain traffic crash and violation records
> in accordance with appropriate NASA and State directives.

411.6 [KSC TRAFFIC CITATION POINT ASSESSMENT SYSTEM]{.underline}

> a\. Any person who is charged with a violation of NASA and/or Florida
> Traffic Regulations will be assessed points against his/her driving
> record in accordance with State of Florida Department of Highway
> Safety and Motor Vehicle Guidelines. [KSC Traffic Citations issued for
> \"Non-moving Violations\" must have all the driver/owner information
> recorded by the driver/owner and signed by the driver\'s supervisor in
> the space provided on the reverse of the form]{.underline}, before it
> is returned to J-BOSC Security. Failure to complete and return the
> citation within 72 hours as specified in this handbook will constitute
> a separate violation, and an additional point will be assessed against
> the owner\'s driving record.
>
> b\. Points will be automatically assessed by the J-BOSC Projects &
> Integration Office upon completion of the processing procedure for KSC
> Traffic Citations.
>
> c\. Points assessed as a result of the issuance of a KSC Traffic
> Citation will be removed from a person\'s driving record, if an appeal
> is upheld in accordance with paragraph 411.7 below.
>
> d\. Points will be assessed as a result of the issuance of a Florida
> Uniform Traffic Citation only after receipt of documentation from the
> Clerk of the Court showing that the person was found guilty during
> Court proceedings. No point will be assessed if the charges are
> dismissed, or if found not guilty by the Court.

411.7 [TRAFFIC APPEALS]{.underline}

> a\. Appeals of KSC Traffic Citations will be the responsibility of the
> J-BOSC Security, Traffic Management Office. Appeals will be reviewed
> by the KSC Traffic Appeals Board which is comprised of the following
> persons and will convene the first week of each month:
>
> \(1\) CHAIRPERSON - A permanent position to be held by the J-BOSC
> Security Traffic Management Administrator.
>
> \(2\) MEMBER - A 6-month position to be held by a Security
> Representative from another contractor at KSC. Appointment will be
> made by NASA Security.
>
> \(3\) MEMBER - A 6-month position to be held by a KSC Civil Service
> employee outside the Security Field. Appointment will be made by NASA
> Security.
>
> \(4\) RECORDER/ADVISOR - A permanent position to be held by a
> Representative from the Projects and Integration Office. The position
> will not have a vote, but will act as Technical Advisor to the Board.
>
> b\. The KSC Traffic Appeals Board will adjudicate all appeals which
> are based upon the issuance of a KSC Traffic Citation. The decision of
> the Board will be final.
>
> c\. Persons who wish to appeal a KSC Traffic Citation issued to them
> must, within 10 days of the citation issue date, initiate a letter of
> appeal.
>
> d\. The letter will state the facts of the incident (as seen by the
> appellant) and the reasons why the appellant feels the assessed points
> should be stricken from the record. Maps, diagrams, and pictures may
> be included. The letter will be forwarded to the KSC Traffic Appeals
> Board, J-BOSC Security. The KSC Traffic Appeals Board will notify the
> appellant in writing of the action taken by the Appeals Board. [The
> KSC Traffic Appeals Board will not consider those KSC Traffic
> Citations which are not completed by the appellant as outlined by this
> handbook.]{.underline} No personal appearances or video tapes are
> allowed.

411.8 [ASSIGNMENT OF RESERVED PARKING SPACES]{.underline}

> a\. Criteria for the assignment of reserved parking spaces are as
> follows:
>
> \(1\) [Civil Service Personnel]{.underline}: Each employee in grade
> GS-15 or above, or each Division Chief, is authorized a reserved
> parking space for his/her privately owned vehicle in the vicinity of
> his/her primary assigned office. An individual will only be authorized
> one reserved parking space.
>
> \(2\) [Contractor Personnel]{.underline}: Each contractor employee
> located at the KSC who is at the management level in the local company
> organization that is equivalent to civil service grade GS-15 or above,
> as determined by the NASA Contracting Officer, is authorized a
> reserved parking space for his/her privately owned vehicle in the
> vicinity of his/her primary assigned office. An individual will only
> be authorized one reserved parking space.
>
> \(3\) [Handicapped Personnel]{.underline}: Each handicapped civil
> service and contractor employee who has the proper KSC or State
> handicapped hang tag, may park in designated handicapped spaces. A
> temporary KSC handicapped parking permit may be requested through the
> Occupational Health Facility (OHF).
>
> \(4\) [Government-Owned/Leased Vehicles]{.underline}: Reserved parking
> space is authorized for Government-owned/leased vehicles, including
> those assigned to an organization, subject to the approval of the NASA
> Site Manager of the facility where the reserved space is requested.
>
> \(5\) [Vanpool Vehicles]{.underline}: Each civil service and
> contractor employee operating an authorized vanpool may be assigned a
> reserved parking space for the van in the vicinity of his/her primary
> assigned office.
>
> b\. Use and Identification of Reserved Parking Spaces.
>
> \(1\) All reserved spaces will be marked as identified below. The
> location of marking (i.e. pavement, bumper block, curb, etc.) will be
> determined by the J-BOSC Security Traffic Management Office.
>
> \(2\) Spaces reserved for Government vehicles will normally be marked
> using a numbered parking permit system. An alternate method of marking
> the space by identifying the specific vehicle or category of vehicle
> (e.g., Government vehicle, mail truck, etc.) may be used at the
> discretion of J-BOSC Security Traffic Management Office.
>
> \(3\) Vehicles with visible markings which identify them as KSC
> contractor-owned/leased vehicles may utilize spaces reserved for
> Government vehicles subject to the limitations imposed on Government
> vehicles in subparagraph (2) above.

411.9 [ASSIGNMENT RESPONSIBILITIES FOR RESERVED PARKING]{.underline}

> a\. [The J-BOSC, Security Traffic Management Office, or
> designee,]{.underline} is responsible for:
>
> \(1\) Managing existing vehicle parking facilities on KSC.
>
> \(2\) Approving requests for reserved parking.
>
> \(3\) Assigning reserved spaces/zones to authorized employees and
> offices.
>
> \(4\) Preparing (prior to the parking facility\'s beneficial occupancy
> date) and maintaining a plan showing utilization of all parking areas.
> The plan will show the following:
>
> \(a\) Visitor parking spaces.
>
> \(b\) Spaces reserved for privately owned vehicles.
>
> \(c\) Spaces reserved for Government vehicles.
>
> \(d\) Loading zones.
>
> \(e\) Spaces reserved for special-purpose vehicles.
>
> \(f\) Parking spaces for the handicapped.
>
> \(5\) Implementing the parking area utilization plan including traffic
> flow markings, reserved space markings, and erection of signs.
>
> b\. [NASA Contracting Officers or their designated
> representatives]{.underline} are responsible for reviewing parking
> requests submitted by contractor personnel for reserved parking spaces
> for their privately owned vehicles (except those requests based on
> physical handicap) to determine whether the contractor employee meets
> the criteria established for a reserved parking space.
>
> c\. [Heads of primary organizations]{.underline} to which
> Government-owned/leased vehicles are assigned are responsible for
> submitting a request to the J-BOSC Security Traffic Management Office
> for reserved parking space for assigned Government-owned/leased
> vehicles, and for assuring that their respective contractors submit
> requests as indicated. **NOTE:** This type request is normally limited
> to emergency or special-purpose vehicles.
>
> d\. [The Director, Spaceport Services]{.underline} is responsible for
> reviewing requests submitted by handicapped personnel for a temporary
> KSC handicapped hang tag which authorizes parking in handicapped
> parking spaces. A determination will be made whether the employee's
> physical condition justifies a hang tag and if so, the length of time
> assigned.
>
> e\. [The Director, Spaceport Services]{.underline} is responsible for
> the approval of parking requests and the assignment of reserved
> parking spaces for the parking area located in front of the KSC
> Headquarters Building; and approval of Senior Management Permits and
> hang tags for reserved parking spaces. Both temporary and permanent
> Senior Management permits are processed by this office.
>
> f\. [NASA Site Management Personnel]{.underline} are responsible for
> identifying and approving reserve parking spaces at their facilities.

\* 411.10 [PROCEDURES FOR REQUESTING RESERVED PARKING
PERMIT/HANGTAG]{.underline}

> a\. [Handicapped Personnel]{.underline}
>
> \(1\) Requests for a temporary KSC handicapped hang tag by temporarily
> handicapped personnel shall be submitted on KSC Form 13-116 (Physical
> Examination Request/Report) to the OHF.
>
> \(2\) The OHF will verify the handicap and issue a handicapped hang
> tag which authorizes parking in handicapped parking spaces. Hangtag
> may be issued for a period of up to one year.
>
> \(3\) Handicapped personnel with State-issued parking permits are
> authorized to park in designated handicapped parking spaces.
> Application procedures listed above do not apply.
>
> b\. [Civil Service Personnel - Privately Owned Vehicle
> (POV)]{.underline}.
>
> \(1\) Requests by authorized civil service personnel shall be
> submitted on KSC Form 28-128 (Request for Reserved Parking /Hang Tag
> Request Form), to the J-BOSC Security Traffic Management Office.
>
> \(2\) The J-BOSC Security, Traffic Management Office will process the
> request and notify the requester of status and/or assignment upon
> completion of processing.
>
> c\. [Contractor Personnel - Privately Owned Vehicle
> (POV)]{.underline}.
>
> \(1\) Requests by authorized contractor personnel shall be submitted
> on KSC Form 28-128 (Request for Reserved Parking Hang Tag Request
> Form).
>
> \(2\) Requester\'s NASA Contracting Officer or designated
> representative will show approval by signing the form and forwarding
> it to J-BOSC Security Traffic Management Office.
>
> \(3\) The Reserve Parking Coordinator, J-BOSC Security Traffic
> Management Office, will process the request and notify the requester
> of status and/or assignment upon completion of processing.
>
> d\. [Vanpools.]{.underline}
>
> \(1\) Requests for reserved parking space for a vanpool van will be
> submitted on KSC Form 28-128, KSC Form 28-128 (Request for Reserved
> Parking Hang Tag Request Form) and forwarded to J-BOSC Security,
> Traffic Management Office for processing.
>
> \(2\) Upon the completion of processing, the Reserve Parking
> Coordinator, J-BOSC Security Traffic Management Office, will process
> the request and notify the requester of status and/or assignment.
>
> e\. The requester will notify J-BOSC Security, Traffic Management
> Office, in writing, when a parking space is no longer required (i.e.,
> termination, retirement, transfer from KSC or within KSC). This will
> allow J-BOSC Security to delete, reassign or move the reserved parking
> space.
>
> f\. [Special Requirements.]{.underline}
>
> \(1\) Requests for assignment of reserved or temporary parking space
> for the parking area located in the front of the KSC Headquarters
> Building should be submitted to the Deputy Director for Business
> Operations for approval. It will then be forwarded to the J-BOSC
> Security, Traffic Management Office for processing.
>
> \(2\) Requests for assignment of reserved or temporary parking space
> only for the parking area located inside the fence line of the LCC
> Building fence should be submitted to the NASA/Director, Process
> Integration for coordination and processing. [Requester must meet the
> criteria for assignment of reserved parking as stated in paragraph
> 411.8.a.]{.underline}
>
> \(3\) Requests for assignment of a reserved or temporary parking space
> for those spaces located next to the OPF Annex and on the Space
> Shuttle tow route in the vicinity of the OPF should be submitted to
> the OPF NASA Site Manager for review and approval. Personnel approved
> for a reserved (by permit) space [do not necessarily]{.underline} meet
> the criteria stated in paragraph 411.8.a. These spaces are controlled
> (reserved) for operational, safety, fire, and security purposes so
> that owners of POVs/GOVs are able to be identified and located
> quickly.
>
> \(4\) Other requests not covered by paragraphs a. through e. above
> will be submitted by the requester to the J-BOSC Security Traffic
> Management Office for coordination.
>
> g\. [Specialized Parking Permits/Hang Tags]{.underline}
>
> \(1\) Senior Management Permits/Hang Tags are authorized for Senior
> Management personnel to allow them to park in designated parking
> spaces at facilities other than their primary work location.
>
> \(a\) Requests shall be submitted on KSC Form 28-128 (Request for
> Reserved Parking Hang Tag Request Form), outlining the individual\'s
> management position and primary work location to Spaceport Services
> for approval.
>
> \(b\) Upon approval, Spaceport Services will forward the request to
> J-BOSC Security Traffic Management Office, for issuance.
>
> \(c\) These permits will be renewed annually; however, when the need
> for the permit no longer exists, it should be forwarded to the J-BOSC
> Security Traffic Management Office for disposition.
>
> \(2\) Temporary Senior Management Permits will be maintained and
> issued by the Director, Spaceport Services to those individuals who
> require a parking permit for a short duration.
>
> \(3\) LCC Parking Permits are authorized for individuals who have a
> need for parking access to the inner perimeter of the LCC as
> determined by the Director, Process Integration.
>
> \(a\) Requests for these permits should be sent to the Director,
> Process Integration for approval and issuance.
>
> \(b\) The expiration of these permits will be at the discretion of the
> Director, Process Integration; however, when the need for this permit
> no longer exist, it should then be returned to the Process Integration
> Office, for proper disposition.
>
> \(4\) Temporary LCC Parking Permits will be maintained and issued by
> the Director, Process Integration, for those individuals requiring a
> parking permit for a short duration.
>
> \(5\) OPF Parking permits (as described in 411.10.f.(3)) may be issued
> to personnel for parking next to the OPF Annex or for those spaces
> near the OPF that are located on the Space Shuttle tow route.
>
> \(a\) Requests for issuance of these permits should be sent to the
> NASA OPF Site Manager for approval and issuance.
>
> \(b\) The NASA OPF Site Manager will maintain a current listing of
> assignments by name, function, telephone number, and space number.
>
> \(c\) Upon approval, the NASA OPF Site Manager will forward the
> request to J-BOSC Security Traffic Management Office, for issuance.
>
> \(d\) Permits will be returned to the J-BOSC Security, Traffic
> Management Office when the need no longer exists.
>
> \(6\) Official Vehicle Hang Tags are authorized when private, leased,
> and/or rental vehicles are utilized as Government vehicles, provided
> that proper justification is submitted. This hang tag authorizes
> personnel to park their personal vehicle in a generic parking space
> marked "Government Vehicle".
>
> \(a\) Hang Tags may be requested by submitting KSC Form 28-128,
> Reserve Parking/Hang Tag Request Form to J-BOSC Security, Traffic
> Management Office for processing.
>
> \(b\) Upon approval, the J-BOSC Security Traffic Management Office,
> will issue the permit to the requesting individual.
>
> \(c\) Official vehicle hang tags are valid for one year. Upon
> expiration, justification must be resubmitted for renewal as outlined
> in paragraph a. above.
>
> \(d\) When the need for this permit no longer exists, or at the time
> of expiration, it must be forwarded to J-BOSC Security Traffic
> Management Office for disposition.
>
> \(7\) Service Vehicle Hang Tags are authorized when Government
> vehicles or private vehicles are utilized as Government Vehicles and
> used as mobile workshops.
>
> \(a\) Service Vehicle Hang Tags may be requested by submitting a KSC
> Form 28-128 (Reserve Parking/Hang Tag Request Form) to the J-BOSC
> Security Traffic Management Office.
>
> \(b\) Upon approval, the J-BOSC Security Traffic Management Office,
> will issue a hang tag to the individual requester.
>
> \(c\) Service Vehicle Hang Tags are valid for one year. Upon
> expiration, the hang tag must be returned to J-BOSC Security.
>
> \(8\) Intentional misuse of any of the specialized parking hang tags
> may cause loss of privileges, confiscation, and disciplinary action.

411.11 [TRAFFIC MANAGEMENT REVIEW BOARD]{.underline}

> a\. [Purpose]{.underline}. The KSC Traffic Management Review Board
> (TMRB) will review proposals, plans, design engineering and
> specifications, and/or suggestions to modify and expand KSC\'s roads,
> parking areas, and automated and manual traffic control devices. The
> TMRB will also review contracts that could impact the movement of any
> vehicular traffic on KSC, or areas under KSC jurisdiction.
>
> b\. [Policy]{.underline}. It is KSC policy to establish and maintain
> the necessary capabilities to ensure that the management of traffic
> and traffic impacting activities on KSC affords all personnel the
> optimum level of service. This will be accomplished by the KSC Traffic
> Management Review Board which will evaluate and/or adjudicate new or
> existing situations arising from changes, modifications, or any
> activity identified as having the potential to impact KSC\'s traffic,
> roads, parking areas, etc.
>
> c\. The TMRB will consist of:
>
> Chairperson: NASA Security
>
> Vice-chair: NASA Safety
>
> Members: NASA Facilities Representative
>
> SFOC Safety Representative
>
> J-BOSC Traffic Management, Administrator
>
> J-BOSC Security Engineer (Signalization)
>
> J-BOSC Roads & Grounds Representative
>
> J-BOSC Security Operations Representative
>
> J-BOSC Secretariat/Recorder
>
> Others: Representative from organizations identifying the situation.
>
> Other KSC organizations as required.
>
> The TMRB will consist of designated NASA/KSC representatives from the
> organizations having TMRB responsibilities. The member\'s
> organizations shall be identified in writing and be authorized to
> speak for their organizations regarding TMRB activity. The TMRB may
> limit participation to only those individuals having a proprietary
> interest in the matter under discussion.
>
> d\. The TMRB will:
>
> \(1\) Convene when traffic management issues are identified.
>
> \(2\) Review the issue/concern and provide requirements and/or
> recommendations for action/corrections.
>
> \(3\) Resolve organizational interface problems.
>
> \(4\) Provide recommendations for advanced planning on traffic
> management changes.
>
> e\. Traffic Management Issues:
>
> \(1\) Traffic management issues may be presented in writing to any
> Board member by any employee having a traffic related concern.
>
> \(2\) All design engineering involving traffic management issues will
> be reviewed by the Board for impacts.
>
> \(3\) Traffic Management issues include, but are not limited to, the
> following situations:
>
> \(a\) New roadway or facility construction (Plans and Specifications).
>
> \(b\) Site Plan Reviews.
>
> \(c\) Intersection configuration changes.
>
> \(d\) Employee suggestions (traffic related).
>
> \(e\) Pedestrian or vehicle safety issues.
>
> \(f\) Roadway operations and maintenance programs.
>
> \(g\) WAP reviews.

**CHAPTER 412**

**VIOLATIONS OF LAW INCIDENT REPORTING**

412.1 [GENERAL]{.underline}

> a\. The Office of the Inspector General investigates all crimes
> concerning fraud against the U.S. Government, waste of Government
> resources, and abuse of Government authority or privilege. To report
> crimes of fraud, waste, and abuse, phone 321-867-4714 or
> 1-800-424-9183.
>
> b\. The J-BOSC investigators and J-BOSC Security Patrol, under the
> technical direction of NASA Security, investigate criminal matters
> normally handled by local police including trespass, theft, drugs, and
> assault. In emergencies, dial 911. In all other cases, phone
> 321-867-2121. See also Chapter 401.
>
> c\. Because time is critical when reporting and investigating
> incidents, all organizations to which this chapter applies will take
> steps to ensure the timely reporting of the incidents covered by this
> chapter.
>
> \(1\) In cases where a physical examination of a particular item or
> site is likely during the course of an investigation, the item or site
> will be preserved exactly as found, provided that this does not
> jeopardize safety or disclose classified information.
>
> \(2\) When an incident may gravely affect the national security or
> preservation of critical national resources, the Installation Security
> Officer or the NASA/KSC Investigator may, as long as safety is not
> jeopardized, initiate the following:
>
> \(a\) Order that the scene of the incident be protected to assure the
> preservation of evidence.
>
> \(b\) Freeze conditions and configurations.
>
> \(c\) Impound material.
>
> \(d\) Conduct interviews.
>
> \(e\) Order persons who are knowledgeable of the incident or
> investigation not to discuss it except as directed by the Installation
> Security Officer or NASA/KSC Investigator.

412.2 [BEHAVIOR OF CLEARED PERSONS]{.underline}

> a\. Organizations to which this chapter applies will report to NASA
> Security, any incident which indicates that a person who is cleared
> for access to classified information or unescorted access to
> controlled areas may not be trustworthy or reliable. NASA Security
> will make a preliminary assessment of the information and may suspend
> access pending the completion of a thorough investigation and
> resolution of the matter.
>
> b\. Guidelines on what constitutes evidence of unreliability are
> contained in KHB 1610.2.
>
> c\. Examples of reportable behavior include:
>
> \(1\) Financial irresponsibility.
>
> \(2\) Criminal conduct.
>
> \(3\) Sexual misconduct.
>
> \(4\) Mental or emotional illness.
>
> \(5\) Alcohol abuse.
>
> \(6\) Drug abuse.
>
> \(7\) Security violations.
>
> \(8\) Subversive activity.

412.3 [OTHER REPORTABLE INCIDENTS]{.underline}

> The protection of critical Government resources and the ability to
> maintain a secure environment for classified information or material
> is dependent on the identification and reporting of incidents. The
> following list of incidents will be reported to NASA Security or
> contractor security in a timely manner.
>
> a\. Evidence or suspicion of penetration of a security area.
>
> b\. Failure or unauthorized manipulation of an access control system
> (e.g., Electronic Security System).
>
> c\. Equipment malfunctions of a suspicious or unusual nature.
>
> d\. Damage to critical hardware or unapproved configuration changes.
>
> e\. Unplanned equipment activity.
>
> f\. Circumvention of approved Secure Configuration Management change
> procedures.
>
> g\. Incidents/activities as described in Appendix B, \"Miscellaneous
> Controlled Activities.\"

412.4 [PENALTIES]{.underline}

> See Paragraph 204.5.

**CHAPTER 413**

**TRANSPORTATION AND MATERIAL SECURITY**

413.1 [GENERAL]{.underline}

> This chapter of the KSC Security Handbook specifies the minimum
> safeguards and security measures to be taken in the protection of NASA
> and contractor assets during their storage and movement. These minimum
> standards do not limit users from instituting more stringent controls
> since hands-on operators often are aware of problems which may not be
> obvious to outsiders.

413.2 [TYPES OF CARGO/MATERIAL]{.underline}

> a\. All Government and contractor assets while being stored,
> transported, or while in use require some level of protection.
> Priorities are established in accordance with importance to the
> mission, value, and specific nature of any item. The following list
> depicts levels of priorities:
>
> [Priority]{.underline} [Cargo/Material Item]{.underline}

1 Operationally critical Space Shuttle flight hardware; Space Shuttle
flight hardware designated for a mission undergoing processing
(including payloads).

Other Space Shuttle manned flight hardware/payloads.

Expendable vehicle flight hardware/payloads.

Sensitive/classified items.

Hazardous cargo/material.

2 High-value/pilferable items; medical supplies (drugs listed as
controlled substances); cash/check-handling activities.

3 Other cargo or material items, or the transportation or storage assets
used with or by these items.

> b\. Some items are classified/prioritized by others. These items, such
> as nuclear material or classified hardware, require safeguards
> specified by the originator of the item. When prioritizing and
> planning utilization of security assets for these items, ensure that
> all requirements of the other authority are satisfied.
>
> c\. The transportation and storage of hazardous matter require special
> security support. Those items identified as hazardous or potentially
> hazardous will be given special attention. All parties involved in the
> transportation or storage of hazardous material (or in response to
> emergencies) must be fully cognizant of the nature of the hazard.

413.3 [RESPONSIBILITIES]{.underline}

> a\. [The Chief, Protective Services Branch]{.underline} is responsible
> for overall management of the security efforts involved in
> transportation and material security.
>
> b\. [The Lead, NASA Security]{.underline} is responsible for:
>
> \(1\) Establishing and ensuring the implementation of all security
> measures for activities/operations under the cognizance of KSC.
>
> \(2\) Delegating certain security planning and implementing functions
> to other NASA and contractor elements. Chapter 401, \"Law
> Enforcement,\" requires directors of first line directorates or
> offices and contractors to appoint \"Security/Law Enforcement points
> of contact\" (Appendix C).
>
> \(3\) Providing guidance and assistance to NASA organizations and
> contractor points of contact (POCs) in designing certain security
> plans for all items.
>
> \(4\) Maintaining liaison with all NASA and contractor organization
> POCs, keeping them informed of all security measures in use and
> providing guidance when necessary.
>
> c\. [Heads of primary organizations]{.underline} are responsible for
> ensuring that NASA and contractor organizations appoint a security/law
> enforcement POC to be responsible for the security of facilities,
> operations, and assets under their responsibility; and in addition to
> the responsibilities listed in Chapter 401, will, as a minimum:
>
> \(1\) Ensure that Standard Operating Procedures (SOPs) are developed
> and implemented for the following:
>
> \(a\) Documentation of orders, manifests, and requisitions detailing
> what has been ordered, how items are to be transported, and where
> delivery will be made.
>
> \(b\) Maintenance of accountability and recording of disposition of
> cargo.
>
> \(c\) Receipt, storage, and maintenance of cargo.
>
> \(d\) Identifying and reporting shortages.
>
> \(e\) Scheduled and nonscheduled audits of all transportation and
> supply accountability records.
>
> \(f\) Training or arranging for training of personnel in loss
> prevention.
>
> \(g\) Receipt for shipment of arms, munitions, pyrotechnics, ordnance,
> or other sensitive items.
>
> \(h\) Security of items in shipment and storage.
>
> \(2\) Ensure that vehicles, containers, shipping bins, etc., are
> properly marked (origin and destination), sealed, and locked where
> appropriate.
>
> \(3\) Ensure that proper physical security measures are in place at
> receipt, shipping, and storage areas.
>
> \(4\) Ensure the security of sensitive information concerning
> shipments.
>
> \(5\) Coordinate with NASA Security and J-BOSC Security for support
> when required.
>
> d\. [J-BOSC Security will]{.underline}:
>
> \(1\) Provide assistance to NASA Security and other organizations in
> fulfilling their storage and transportation security obligations.
>
> \(2\) Provide uniformed, armed, security officers and security escorts
> when required.
>
> \(a\) The storage and/or transportation of sensitive or classified
> items may require an armed security escort. The officers and
> supporting equipment for the security protection will be supplied by
> J-BOSC Security at the direction of NASA Security. As requirements
> vary with each situation, specific plans will be developed by the
> coordinated efforts of NASA Security and J-BOSC Security.
>
> \(b\) Certain unusual or oversized items will require traffic escorts
> from marked security vehicles in order to travel safely on the
> roadways. These will be provided by J-BOSC Security within the
> provisions of the following regulatory documents:
>
> [1.]{.underline} 45th Space Wing #15E-3-50, Joint Operating Procedure
> Between ESMC and KSC for Responsibilities and Interfaces for
> Scheduling, Transportation, and Convoying of Oversized Loads Between
> CCAFS and KSC.
>
> [2.]{.underline} KMI 6200.1, \"Movement of Overweight/Overdimensional
> Loads at KSC.\"

413.4 [MINIMUM STANDARDS]{.underline}

> a\. Accountability for and protection of items in storage or in
> transit, in addition to those listed below, will be maintained in
> accordance with procedures established by each cognizant NASA or
> contractor organization and approved by NASA Security. These
> procedures will comply with NASA regulatory documents, the provisions
> of this handbook, and any special accountability requirements levied
> for special controlled items, such as nuclear material. As a minimum,
> the following will be complied with to prevent pilferage, theft,
> damage, destruction, or loss:
>
> \(1\) [Packing for Shipment.]{.underline}
>
> \(a\) [Physical Construction of Containers.]{.underline} Shipping
> containers must be strong enough to protect the load from damage and
> to hold together without breaking open under stress or rough handling.
> They must be constructed to show signs of any attempted forced entry.
>
> \(b\) [Physical Size of Containers]{.underline}. Small packages, which
> could be easily concealed, will be packed in larger, master cartons.
>
> \(c\) [Sealing of Containers]{.underline}. Containers will be securely
> sealed with tape, glue, and/or staples, and/or metal/steel straps and
> seals. Tape will be at least 3 inches wide. Tape will not be used if
> it can be lifted without creating noticeable damage. Tape will be
> distinctively marked to permit quick detection of tampering.
> Appropriate warnings, similar to \"IF TAPE IS BROKEN, DO NOT GIVE
> RECEIPT WITHOUT EXAMINATION\" will be placed on containers.
>
> \(d\) [Package Markings]{.underline}. Consistent with current
> Department of Transportation rules, packages will not be marked with
> the contents of the item being shipped. No indications as to the item
> or value will appear on the outside of the shipping container.
> Packages will be properly marked with any special handling
> requirements, such as \"FRAGILE.\"
>
> \(e\) [Origin/Destination Markings]{.underline}. Packages will be
> marked with the name and address of the consignee and the shipper\'s
> telephone number and name. All old or confusing handling and
> cautionary marks and symbols will be removed or obliterated on
> reusable containers.
>
> \(f\) [Palletizing/Unitizing]{.underline}. Items which are susceptible
> to pilferage will be palletized or unitized whenever possible. Boxes
> will be stacked neatly and tightly. Supporting strapping, netting, or
> shrink-wrap plastic will be utilized.
>
> \(g\) [Carriers]{.underline}. The loading and unloading of items to or
> from carrier trucks will be observed. The bill of lading will be
> checked for accuracy and completeness. A NASA/KSC provided seal will
> be used for sealing containers.
>
> \(h\) [Sensitive Information]{.underline}. Only those persons who need
> to know will have access to information concerning shipments,
> schedules, routes, and destinations of cargo.
>
> \(i\) [Documentation Checks.]{.underline} Procedures to double-check
> documentation for errors will be developed.
>
> \(j\) [Two-Person Rule]{.underline}. Two workers will always be
> employed for packaging sensitive or easily pilfered items.
>
> \(2\) [Receiving Procedures]{.underline}. Persons receiving shipments
> will, as a minimum, accomplish the following:
>
> \(a\) When receiving items, ensure that a bill of lading is properly
> completed with full addresses of shipper and consignee.
>
> \(b\) Inspect cargo for proper address and markings. Remove or
> obliterate old or confusing markings.
>
> \(c\) Inspect cargo for damage, abnormally light cartons, cartons
> which appear to have been repaired/rebuilt, etc., and note any
> discrepancies on the bill of lading.
>
> \(d\) Count the number of pieces and ensure that the number agrees
> with the number called for on the bill of lading.
>
> \(e\) Have the carrier sign the bill of lading with full last name and
> initial any notations of exception.
>
> \(f\) Record the company name or carrier abbreviation, record and
> circle the number of pieces received, and sign and record the date on
> all copies of the bill of lading.
>
> \(g\) Conduct spot checks on the loading docks. Monitor unloading
> procedures. Randomly select crews to unload cargo. Do not use the same
> crew to unload the same carrier time after time. Rotate supervisors on
> the docks. Do not let crew have their lunch or breaks in the unloading
> areas. Always have at least two persons on each crew.
>
> \(h\) The driver of inbound loads should not be allowed in the
> unloading area. Inbound vehicles will not park at the unloading area
> until ready to unload.
>
> \(i\) Inspect all seals.
>
> \(j\) Close and lock any partially loaded trucks at the close of
> business. Do not use a carrier-supplied lock.
>
> \(k\) Inspect the interior of the truck before loading or unloading.
>
> \(l\) Make periodic inspections of trash bins in the loading/unloading
> areas for concealed items.
>
> \(3\) [Seals.]{.underline}
>
> \(a\) [Use of Seals.]{.underline} Seals are not locks. Seals are
> intended to discourage theft, maintain accountability, and indicate
> tampering. Do not rely on a seal if a lock is needed.
>
> \(b\) [Storage of Seals]{.underline}. Unissued seals will be secured
> in a locked storage area, accessible only to designated supervisors
> and accounted for.
>
> \(c\) [Application of Seals.]{.underline} After verifying the contents
> of the containers, seals will be applied by supervisory personnel.
>
> \(d\) [Recording of Seals]{.underline}. A log of all seals applied to
> loads or removed from inbound loads will be maintained. This log will
> show, as a minimum:
>
> [1.]{.underline} Seal number.
>
> [2.]{.underline} Date applied.
>
> [3.]{.underline} Unit applied to.
>
> [4.]{.underline} Person applying seal.
>
> [5.]{.underline} Load destination/origin.
>
> \(e\) [Discrepancies]{.underline}. If a seal is found to be broken,
> tampered with, or switched, a report will be made and forwarded to the
> contractor and NASA Security. All details of the discrepancy,
> including the date and time discovered, location discovered, and
> person finding the problem, will be included.
>
> \(f\) [Seal Removal]{.underline}. Seals on inbound shipments will be
> checked by a supervisor before removal.
>
> \(g\) [Legal Considerations.]{.underline} Title 18, U.S. Code, Section
> 2117, states: \"Whoever breaks the seal or lock of any railway car,
> vessel, aircraft, motor truck, wagon or other vehicle . . . containing
> interstate or foreign shipments of freight or express, or other
> property, or enters any such vehicle with intent in either case to
> commit larceny therein, shall be fined not more than \$5,000, or
> imprisoned not more than 10 years, or both . . . .\"
>
> b\. [Physical Security Measures for Storage
> Areas/Structures.]{.underline} All standards for physical security as
> established in this handbook apply to facilities involved in the
> shipment and storage of Government cargo and material. Buildings and
> rooms used for the storage of Government property on the Kennedy Space
> Center and at off-Center KSC facilities worldwide must meet the
> following standards:
>
> \(1\) Doors provide a degree of security comparable to that provided
> by the walls of the basic structure.
>
> \(2\) Door hinge mounting screws are not exposed to the exterior of
> the facility. If screws are exposed, they will be spot welded, peened,
> covered, or filled with material in a way so as to prevent easy
> removal. Nails will not be used to mount hinges.
>
> \(3\) Door hinge pins exposed to the exterior of the facility are
> designed or modified to prevent easy removal. If these hinge pins
> cannot be so modified, safety stud hinge pins will be used.
>
> \(4\) Doors to the exterior locked from the inside are secured with a
> deadbolt locking device, crossbar, or similar locking device resistant
> to jimmying and manipulation from the outside as opposed to a
> latch-style door lock.
>
> \(5\) Windows have individual locking devices, and protected as
> described in paragraph b.6 below.
>
> \(6\) All first-floor openings, except doors, in excess of 96 square
> inches (619.4 square centimeters) that are located less than 12 feet
> (3.7 meters) from the ground level are barred, grill, or covered with
> chain link material in a way to preclude easy removal. Long, narrow
> openings with the shortest dimension measuring less than 6 inches
> (15.2 centimeters) are exempt from this requirement.
>
> \(7\) Doors secured from the outside will have locking devices
> conforming to the requirements of this handbook and will be part of
> the KSC lock system. In-door locks and pin-tumbler-type, key- operated
> padlocks and hasps will be of a size and strength to provide proper
> security. Hasps will not be mounted with nails.
>
> \(8\) Walls, floors, and ceilings are constructed of at least 1/2-
> inch plywood, 1-inch tongue-in-groove wall boards, or equivalent.
>
> c\. [Personnel Security.]{.underline}
>
> \(1\) The two-person rule applies to all loading/unloading operations
> and to the handling of sensitive cargo.
>
> \(2\) Persons handling or having access to classified, sensitive, or
> otherwise secured items will be cleared by appropriate authority prior
> to having access to these items.
>
> \(3\) Knowledge of details concerning security planning, schedules,
> etc., will be available only on a need-to-know basis.
>
> d\. [Procedural Measures.]{.underline} Utilizing the requirements of
> this handbook and other NASA and Government documents, each
> organization involved in the transportation and storage of assets and
> each facility handling cargo, will develop procedures to maintain
> accountability and to facilitate accurate auditing of all aspects of
> cargo processing.
>
> e\. [Overseas Shipping and Receiving Areas.]{.underline} Special
> security plans for KSC controlled areas outside the continental U.S.
> will be developed following detailed site surveys for each area by
> NASA Security and/or by the J-BOSC.
>
> f\. [During Shipment.]{.underline}
>
> \(1\) [Route Selection]{.underline}. Route selection will normally be
> made to accommodate safe, cost-effective transportation of a given
> item. If a specific threat against an item is known, then the route
> will be selected to maximize the available protection and to diminish
> the adversaries\' possible access.
>
> \(2\) [Alarm Devices]{.underline}. When appropriate, electronic
> surveillance of articles in shipment will be made. The manner or
> devices utilized and the application of it will depend upon the
> specific cargo, the carrier, and any known threat. NASA Security will
> be notified whenever electronic surveillance or other alarm devices
> are utilized on shipments.
>
> \(3\) [Use of Seals]{.underline}. See paragraph 413.4.a.(3) above.
>
> \(4\) [Use of Escorts]{.underline}.
>
> \(a\) [Shipper Escorts.]{.underline} Use of carrier-supplied security
> escorts for NASA/KSC shipments will be made only at the direction of,
> or with the approval of, NASA Security. All procedures and
> specifications for the operation of the carrier-supplied escorts will
> be approved by NASA Security.
>
> \(b\) [J-BOSC Patrol Officers]{.underline}. J-BOSC Patrol Officers
> will provide escort for Government property on KSC within the
> provisions of the J-BOSC contract and as specified in this handbook.
> Their escort of items outside the confines of KSC will be made only
> upon the direction of NASA Security.
>
> \(c\) [Legal Considerations]{.underline}. Escort procedures will
> consider the legal considerations present in a specific transportation
> operation. Some of these are jurisdiction, Department of
> Transportation regulations, and use of force limitations.
>
> \(d\) [Instructions for Guards/Escorts]{.underline}. Instructions for
> guards for shipments made under NASA cognizance will be developed by
> the J-BOSC and approved by NASA Security.
>
> g\. [Transit/Temporary Holding Areas.]{.underline}
>
> \(1\) [On KSC]{.underline}. The transit/holding areas on KSC are
> governed by the provisions of this handbook and other NASA and
> Government publications.
>
> \(2\) [Off KSC.]{.underline} Security during temporary stops off KSC
> are the responsibility of the consignee for normal,
> noncritical/sensitive items. For critical/sensitive items for which
> KSC has assumed security responsibility while the items are in transit
> off the Center, contingency plans will be developed by NASA Security
> for temporary holding areas while the shipment is in transit. In these
> cases when KSC retains security responsibility, the NASA Security
> developed shipment security plan will include provisions for, as a
> minimum:
>
> \(a\) Primary and alternate routes of travel.
>
> \(b\) Possible holding areas in route.
>
> \(c\) Contacts within each community (country, state, county,
> municipality) law enforcement authorities who would be notified,
> should the shipment be temporarily held within their area.
>
> \(d\) Local area threat situation.
>
> h\. [Temporary Removal of Government Property From KSC]{.underline}.
> All handling and removal of government property from KSC will be in
> accordance with the provisions of KHB 4000.1. As a minimum, NASA Form
> 892, \"Property Pass Request and Removal Permit,\" or other
> appropriate documentation, will be utilized.
>
> i\. [Lost and Found.]{.underline} J-BOSC Security will maintain a lost
> and found service in accordance with appropriate Government
> regulations and as directed by NASA Security.

413.5 [NON-OFFICIAL DELIVERIES]{.underline}

> Non-official deliveries (i.e., food, flowers, greetings, etc.) are not
> permitted on KSC. Only those delivery service organizations recognized
> by NASA as requiring official access to the restricted area in support
> of the Space Center, are permitted on the Center.

**\* CHAPTER 414**

**REGISTERED KEY AND LOCK SYSTEM (RKLS)**

**LOCKSMITH SERVICES**

414.1 [PURPOSE]{.underline}

> This chapter explains the responsibilities and services, and
> establishes requirements for obtaining and controlling registered
> locks, padlocks, and keys. It covers KSC\'s implementation of the KSC
> Key Accountability System (KKAS), the Registered Lock and Key System
> control procedures, Key Custodian responsibilities training, and
> supplemental locksmith services.

414.2 [RESPONSIBILITIES]{.underline}

> a\. [The Lead, NASA Security]{.underline} is responsible for
> appointing a KSC Key Control Officer.
>
> b\. [The Key Control Officer]{.underline} is responsible for:
>
> \(1\) Representing the Protective Services Branch in all matters
> regarding Registered Key Control.
>
> \(2\) Identifying training requirements and concurring in training
> programs established to support the KCCs and alternates.
>
> \(3\) Evaluating lost key incidents and reviewing investigations
> involving the Registered Key Control System.
>
> \(4\) Coordinating security requirements for changes, modifications,
> additions, and deletions of lock requirements that are outside the
> responsibility of the organizational KCC.
>
> \(5\) Directing actions to be taken after the review of incident
> reports/investigations.
>
> c\. [Heads of primary organizations]{.underline} are responsible for:
>
> \(1\) Ensuring compliance with the provisions of this chapter.

2.  Appointing, in writing, primary and (as determined) alternate Key
    Control Custodians (KCCs) and providing them with the authority to
    approve and/or disapprove key and lock requests.

> d\. [KCCs (Primary)]{.underline} are responsible for:
>
> \(1\) Reviewing and approving all key/lock requests.
>
> \(2\) Forwarding requests to the J-BOSC Locksmith Office.
>
> \(3\) Turning in all keys and locks to the J-BOSC Locksmith Office
> when no longer required.
>
> \(4\) Reporting all lost or misplaced keys and locks to the
> appropriate organizational security office.
>
> \(5\) Acting as the central point-of-contact for the
> organization/facility with the J-BOSC Locksmith Office.
>
> \(6\) Assisting in surveys and audits of the Registered Key Control
> System under their cognizance.
>
> \(7\) Being cognizant of all key and lock activities in their area of
> control.
>
> e\. [KCCs (Alternates)]{.underline} are responsible for:
>
> \(1\) Assisting the requester in filling out key and lock requests.
>
> \(2\) Forwarding properly completed requests to the primary KCC.
>
> \(3\) Turning in keys and locks to the Primary KCC.
>
> \(4\) Reporting lost keys and locks to the Primary KCC.
>
> \(5\) Assisting in surveys and audits of the Registered Key Control
> System under their control.
>
> \(6\) Interfacing with the J-BOSC Locksmith in the absence of the
> Primary KCC.
>
> f\. [The Director, Procurement Office]{.underline} is responsible for
> incorporating this chapter into applicable contracts.

414.3 [GENERAL]{.underline}

> a\. It is a KSC policy to protect Government property in the most
> practical and economic manner. Unless specifically exempted by the
> Installation Security Officer, all lockable facilities/areas
> containing Government or other high value property will be equipped
> with approved locks. These facilities/areas will be locked during any
> period that they are unoccupied.
>
> b\. The \"KSC Registered Lock and Key System\" is a master key system
> utilizing registered locks and padlocks with removable and
> interchangeable cores. Each lock or padlock core is stamped to include
> the series to which it is assigned. The location is maintained by the
> J-BOSC Locksmith Office.
>
> c\. A \"KSC Registered Key\" is a key marked \"U.S. Government, Do Not
> Duplicate.\" It is stamped to indicate the lock series and key number.
>
> d\. The \"KSC Key Accountability System\" (KKAS) is an automated data
> processing (ADP) program, maintained by the J-BOSC Locksmith Office,
> and is designed to maintain control and accountability of the KSC
> Registered Key and Lock System.
>
> e\. The J-BOSC Locksmith Office will:
>
> \(1\) Service and repair vaults, safes, door locks, and padlocks with
> three-position combination locks.
>
> \(2\) Provide \"BEST\" Lock Company seven-pin padlock cores,
> cylindrical locksets, mortise locksets, rim locksets, and tubular
> locks.
>
> \(3\) Cut keys and replacements (vehicle, desk, file, storage,
> cabinet, control panel, etc.).
>
> \(4\) Combinate and recombinate lock cores.
>
> \(5\) Activate and deactivate storage containers and assist in
> changing safe combinations.
>
> \(6\) Provide preventive maintenance and real-time response to the
> aforementioned hardware.
>
> \(7\) Maintain the automated KKAS.
>
> \(8\) Support audits and surveys of KCCs, holders of keys/locks, and
> the KKAS, as required.
>
> \(9\) Maintain a listing of certified/trained KCCs.

414.4 [KEY CONTROL CUSTODIANS (KCC) AND ALTERNATES]{.underline}

> a\. The KCC, also commonly known as a Key Coordinator, is the central
> point-of-contact within the organization or facility, who will
> authenticate the need for key or lock service (change, addition,
> deletion, etc.). The Primary KCC (PKCC) serves as the official
> point-of-contact with the J-BOSC Locksmith Office. Alternates
> (assistants) are designated based upon organizational needs. The
> alternates will interface with the PKCC, who will be cognizant of the
> organizational needs. Only in the absence of the PKCC, will the KCC
> contact the Locksmith Office.
>
> b\. Assignment of KCCs and alternates shall be in writing from the
> cognizant contractor or KSC directorate (head of organization). At a
> minimum, the KCC and alternates will be Personnel Reliability Program
> (PRP) certified when controlling access to facilities/assets requiring
> personnel to be PRP certified. Written notification will be provided
> to NASA Security which will, in turn, provide the J-BOSC Locksmith
> Office with the notification. Notification will include:
>
> \(1\) Full name.
>
> \(2\) Primary or alternate custodian.
>
> \(3\) Office symbol/building/room number.
>
> \(4\) Phone number/alternate.
>
> \(5\) Areas of responsibility.
>
> \(6\) PRP areas controlled.
>
> \(7\) PRP approved/pending date.

414.5 [KEY AND LOCK ACCOUNTABILITY/CONTROL]{.underline}

> a\. [Key and Lock Issue]{.underline}.
>
> \(1\) Requests for issue of registered locks, padlocks, or keys must
> be presented on KSC Form 20-36, "Locksmith Services Request," to the
> organizational/facility KCC/Alternate.
>
> **[Note:]{.underline}** These keys are Government property; and
> therefore, each individual must sign the 20-36 noting issuance. These
> keys will not be loaned, transferred, thrown away, or given away.
>  When no longer required, the proper procedure for turning in a key is
> detailed in paragraph b. below.
>
> \(2\) Upon verifying that the request is authentic, and if approved,
> the KCC signs the Form 20-36 and forwards it to the J-BOSC Locksmith
> Office for processing.
>
> \(3\) After processing the request, the Locksmith Office notifies the
> individual who will accept receipt for the key that is ready for
> pickup. At the time the individual picks up the key, KKAS is updated
> reflecting the assignment of that key. Note: Under normal
> circumstances the Primary/Alternate KCCs will not receipt or pick up
> keys that will be assigned to other individuals. Special circumstances
> may warrant this from time to time, but must be approved by the KSC
> Key Control Officer.
>
> b\. [Key and Lock Turn-in]{.underline}.
>
> \(1\) All registered keys and padlocks no longer required will be
> returned to the J-BOSC Locksmith Office through the
> organizational/facility KCC.
>
> \(2\) All registered key or locks must be surrendered to the KCC upon
> termination or transfer of the individual key holder.
>
> \(3\) All turn-ins are required to be transferred to the J-BOSC
> Locksmith Office within 5 working days.
>
> \(4\) The J-BOSC Locksmith and KCC will maintain a permanent record of
> turn-ins for a period of 3 years.
>
> c\. [Lost and/or Misplaced Keys or Locks.]{.underline} The
> unauthorized tampering with, removal or damaging of a KSC registered
> lock or padlock, and/or the tampering with, loss, or duplication of a
> registered key will be investigated and referred to the proper
> authority for administrative or disciplinary action.
>
> \(1\) Loss of registered keys, locks, etc., will be verbally reported
> to the KCC immediately, but not later than the first duty hour of the
> day, if the loss occurred during nonduty hours. In all cases, after
> the verbal report, a written report of the lost key incident will be
> provided to the KCC.
>
> \(2\) The KCC will insure that KSC Form 20-174 (reporting a lost
> registered key) is completed on all lost keys and will provide the
> organizational security office with full details concerning the loss.
> The KSC Form 20-174 will be provided to the security office along with
> a request for an inquiry or investigation into the loss.
>
> \(3\) The organizational security element will investigate each lost
> key report and forward the results to the KSC Key Control Officer for
> review. In addition to determining pertinent facts surrounding the
> loss, the inquiry must determine the estimated value of equipment,
> property, and valuables being protected by the lock/key series
> involved. The organizational security office must then make a
> recommendation to the KSC KCO concerning whether or not a recore is
> warranted.
>
> \(4\) When the loss of keys issued under a particular series exceeds
> 10 percent of the number issued, a key/lock change or recore will be
> directed. Key and lock changes may be directed at any time, if
> investigation determines the need.

414.6 [KSC LOCKSMITH SERVICES]{.underline}

> a\. [Requesting Routine Access.]{.underline} Neither the KSC Patrol
> nor the J-BOSC Locksmith routinely unlocks areas/rooms because someone
> has forgotten their key. Individuals requiring access must first
> contact the area occupants or the KCC. Those names, if not known, are
> available from the J-BOSC Locksmith Office, by providing the lock
> series number that is stamped on the core.
>
> b\. [Emergency Access.]{.underline}
>
> \(1\) Master keys for registered locks are maintained by the KSC
> Patrol for use when an emergency condition exists. The Joint
> Communications Control Center, through whom the request should be
> made, can be contacted at 867-2121.
>
> \(2\) Master keys for registered locks in KSC facilities located on
> Cape Canaveral Air Force Station (CCAFS) are maintained by J-BOSC JCCC
> and are for use only during an emergency. The JCCC can be contacted at
> 853-2121.
>
> c\. [Routine and Emergency Locksmith Shop Service]{.underline}. The
> J-BOSC Locksmith Office is available for routine telephone and walk-in
> service, Monday through Friday. Emergency support will be given
> appropriate response and attention, as required by circumstance.

414.7 [KEY SECURITY/CONTROL]{.underline}

> Master keys constitute the greatest vulnerability to the KSC
> Registered Key Control Program. The loss of any one jeopardizes the
> total system. Therefore, the following restrictions are placed on
> master keys:
>
> a\. Master keys will be limited to minimum numbers.
>
> b\. Master keys are subject to audit/inventory at any time.
>
> c\. Master keys will not be issued for convenience. All requests for
> master keys (except sub-masters) will require KSC Key Control
> Officer\'s approval.

414.8 [AUDITS/ACCOUNTABILITY]{.underline}

> All Registered Key Control accounts are subject to audit periodically
> or as an independent action directed by the Key Control Officer.
> Audits may take place as an adjunct to other scheduled security
> inspections or as a stand-alone audit.

414.9 [KSC KEY ACCOUNTABILITY SYSTEM (KKAS)]{.underline}

> a\. The KKAS is an automated data processing system which will be
> operated by the J-BOSC Locksmith Office. It will contain all key
> assignments for NASA/KSC and those NASA facilities at other locations
> such as CCAFS and PAFB. Personnel data and individual\'s facility
> access (by key) information will be contained in the database. It is
> essential that access to the information be strictly controlled to
> those having a need-to-know. Although not classified, the intelligence
> value of the information, if compromised, could cause a potential
> impact to the safety and security of KSC personnel and resources.
>
> b\. Access to the database will be limited to:
>
> \(1\) J-BOSC Locksmith Office personnel.
>
> \(2\) KSC Key Control Officer or the designated representative.
>
> \(3\) Those individuals identified in writing by the Key Control
> Officer who have an official need for access.
>
> c\. Requests for information from the database will be limited to:
>
> \(1\) J-BOSC Locksmith Office personnel.
>
> \(2\) NASA Security personnel.
>
> \(3\) KCCs.
>
> \(4\) Security personnel conducting inquiries or investigations, or
> responding to emergencies where such information is required.
>
> \(5\) Those individuals identified in writing by the Key Control
> Officer who have an official need for the requested information.

414.10 [TRAINING]{.underline}

> a\. [Locksmith Certification]{.underline}: Each Locksmith employed by
> the J-BOSC Locksmith Office will participate in a formal training
> program designed to maintain his/her proficiency. This training
> program will include keeping pace with \"state-of-the-art\" lock/key
> hardware and maintaining proficiency in both installation and by-pass
> techniques. The training must also include all phases of classified
> container service, drilling and by-pass techniques. This training will
> be on-going and will be recertified to the KSC Key Control Officer
> every 3 years.
>
> b\. [KCC Training]{.underline}: Each Primary/Alternate KCC, upon
> assignment, will receive certification training as conducted by the
> J-BOSC. Training will include, but not be limited to, the following:
>
> \(1\) KCC authority/responsibility.
>
> \(2\) Documentation (requests, trouble calls, etc.).
>
> \(3\) KKAS operation.
>
> \(4\) Investigations.
>
> \(5\) Audits.
>
> \(6\) Criteria for issue/turn-in.
>
> \(7\) Lost/misplaced locks/keys.
>
> \(8\) NASA Security responsibilities.
>
> \(9\) Organizational responsibilities.
>
> \(10\) Locksmith support.

414.11 [KEY AUDIT AGENT]{.underline}

> A Key Audit Agent shall be appointed, in writing, by the Joint-Base
> Operations Support Contractor, Resource Protection Branch Manager. The
> appointed person will be responsible to the KSC Key Control Office for
> the operation and general function of the KSC Lock and Key System.
> Specific functions will include, but not be limited to, the following:
>
> a\. Determining location and accountability procedures of all locks
> and keys given a facility or key account.
>
> b\. Determining the status of all keys currently in use.
>
> c\. Ensuring that all key storage containers are used properly, in
> accordance with all directives and instructions.
>
> d\. Inspection of key retention devices and key rings and key tags for
> serviceability.
>
> e\. Publishing a quarterly KEY NEWS bulletin for Key Custodian
> distribution.
>
> f\. Conduct quarterly Key Custodian certification classes.
>
> g\. Work closely with the Locksmith Services Office in developing lock
> and key procedures for KSC.
>
> h\. Covering all other assignments relating to key control as
> designated by the KSC Key Control Officer.

**CHAPTER 415**

**CONTROL OF WEAPONS**

415.1 [GENERAL]{.underline}

> This chapter establishes control over the introduction and possession
> of weapons on KSC. It also prescribes the qualifications necessary
> before any individual is authorized to possess/use a weapon (firearm)
> on KSC or areas under KSC jurisdiction.

415.2 [APPLICABILITY]{.underline}

> This chapter applies to all individuals possessing or introducing
> weapons on the KSC, except Law Enforcement Officers (city, county,
> state, or federal, departments or agencies); military members in the
> performance of their duties, Cape Canaveral Air Force Station contract
> guard force in the performance of their duties, and individuals,
> groups, or representatives of agencies specifically authorized by the
> Installation Security Officer.

415.3 [POLICY]{.underline}

> The introduction and possession of weapons on KSC is prohibited.

415.4 [DEFINITIONS]{.underline}

> a\. [Weapons:]{.underline}
>
> \(1\) Authorized: Government issued firearms and ammunition, as
> approved by the Installation Security Officer.
>
> \(2\) Unauthorized: Items listed in paragraph 415.9 and any privately
> owned firearms, with the exception of those firearms granted a waiver
> in accordance with paragraph 415.8.
>
> b\. [Concealed Firearms]{.underline}: A firearm carried in such a
> manner as to preclude knowledge of its presence by direct observation.
> Concealed weapons are usually covered by a coat or jacket at all
> times.
>
> c\. [Unconcealed Firearms]{.underline}: A firearm carried in such a
> manner that knowledge of its presence can be obtained by casual or
> direct observation.

415.5 [AUTHORITY TO CARRY FIREARMS]{.underline}

> The authority to carry firearms is granted under the National
> Aeronautics and Space Act of 1958, (42 U.S. Code 2456).

415.6 [RESPONSIBILITIES]{.underline}

> a\. [The Installation Security Officer (ISO)]{.underline} is
> responsible for the control of weapons on KSC. Specific
> responsibilities are:
>
> \(1\) Providing guidance to the KSC Protective Services for the proper
> enforcement of this Instruction.
>
> \(2\) Appointing a NASA KSC Firearms Custodian (government employee)
> and one or more Firearms Instructors.
>
> \(3\) Approving the appointment of the J-BOSC Firearms
> Instructor/Rangemaster.
>
> \(4\) Ensuring that all KSC personnel that have been identified to
> carry weapons in the performance of their duties receive and pass an
> approved course of training.
>
> \(5\) Ensuring that all KSC Protective Services (J-BOSC) personnel
> that have been identified to carry weapons in the performance of their
> duties receive and pass an approved course of training.
>
> \(6\) Issuing NASA Forms 699a, "Certification to Carry Concealed
> Weapons;" or NASA Form 699b, \"Certification to Carry Unconcealed
> Weapons,\" to individuals that have been certified by the Firearms
> Instructor/Rangemaster.
>
> \(7\) Identify the prescribed course of fire that will be used for
> firearms qualification and the intervals when that training will take
> place.
>
> \(8\) Ensuring a training program for all security force personnel
> assigned to NASA STS recovery operations, to include firearms
> requirements in foreign countries, is available.
>
> b\. [The Procurement Officer]{.underline} is responsible for ensuring
> that any contract entered into, wherein the requirement for the use of
> weapons exists, will contain a statement of work which includes the
> requirements established by this Issuance.
>
> c\. [NASA KSC Employees and Employees of NASA Contractors]{.underline}
> will comply with the provisions, conditions, and limitations, of this
> chapter regarding the carrying, use, and storage of weapons.
>
> d\. [KSC Security Personnel]{.underline} authorized to carry firearms
> on KSC will:
>
> \(1\) Qualify on a recognized course of fire prescribed by the
> Installation Security Officer.
>
> \(2\) Have in their immediate possession NASA Form 699a or 699b when
> carrying firearms.
>
> \(3\) Only possess firearms on KSC while on actual hours of duty.
>
> \(4\) Be knowledgeable of the \"Rules of Engagement, and the USE OF
> DEADLY FORCE and deadly force criteria."
>
> \(5\) Never have been convicted of a misdemeanor charge of Domestic
> Violence.
>
> e\. [The Firearms Instructor/Rangemaster]{.underline} (NASA KSC
> government employee or contractor employee) will:
>
> \(1\) Train personnel in the safe handling of firearms.
>
> \(2\) Supervise firing range operations.
>
> \(3\) Supervise all firing for qualification.
>
> \(4\) Prepare written certification for each employee successfully
> completing the required training, and qualification, with their
> assigned weapon(s).
>
> \(5\) Maintain the training and firearms qualification historical
> records on applicable personnel.
>
> \(6\) Forward firearm certifications to the Installation Security
> Officer.
>
> \(7\) Remain proficient, while assigned to the position of Firearms
> Instructor/Rangemaster, by obtaining continuing professional education
> in the firearms/weapons discipline.
>
> \(8\) Be certified as a Weapons Armorer, for all assigned Government
> weapons.
>
> f\. [The Firearms Custodian will:]{.underline}
>
> \(1\) Keep current records on all firearms in the custody of NASA/KSC
> and/or NASA/KSC Contractors. These records include the date and method
> of acquisition and complete identifying data (manufacturer, caliber,
> model, serial number, etc.).
>
> \(2\) Provide storage for all firearms and ammunition in containers
> meeting NASA requirements for confidential material.
>
> \(3\) Ensure all weapons are unloaded prior to storage.
>
> **[NOTE:]{.underline}** Weapons will never be stored in the same
> receptacle as money, drugs, or classified material.
>
> \(4\) Maintain a receipting system for the issue, transfer, and
> return, of firearms to the custodian.

415.7 [CONTROL, ISSUANCE, AND CARRYING OF FIREARMS BY KSC SECURITY
PERSONNEL]{.underline}

> a\. Protective force equipment will enhance the ability of KSC\'s
> security personnel to effectively, efficiently, and safely perform
> routine duties, and to prevent adversaries from accomplishing their
> objectives. Duty weapons are:
>
> \(1\) Primary Weapon: The 9-mm Glock semiautomatic pistol.
>
> \(2\) Secondary Weapon: A 9-mm submachine gun, 12-gauge shotgun, or a
> HK-33 rifle is available and will be issued concurrent with the type
> of duty and level of protection to be afforded.
>
> b\. Procedures for issuance, transfer, and return of weapons and
> ammunition to the Firearms Custodian will incorporate reasonable and
> prudent safety standards for the protection of all personnel.
>
> Only weapons and ammunition approved for use on KSC will be used in
> the performance of official duties.
>
> \* c. NPG 1620.1, "Security Procedures and Guidelines," provides the
> direction and authorization to the Installation Security Officer and
> designated security personnel of that office, and to employees of NASA
> contractors and subcontractors engaged in the protection of property
> owned by the United States or contracted to the United States, to
> carry firearms while in the conduct of their official duty.
>
> d\. KSC Security Personnel are required to successfully complete a
> designated course of fire. The course of fire is derived from federal
> and state requirements, (security personnel on KSC, depending upon
> their law enforcement/security status, are required to meet different
> firearms qualifications). A custom tailored course of fire is
> developed by the Rangemaster to accommodate all mandatory firearms
> requirements and is subsequently approved by the Installation Security
> Officer. This course of fire is reviewed on an annual basis to ensure
> any change in requirements are reflected in the qualifications.

415.8 [POSSESSION OF WEAPONS BY KSC EMPLOYEES AND REQUESTS FOR
WAIVERS]{.underline}

> a\. Possession of unauthorized weapons by KSC employees is prohibited.
> The possession of personal firearms on KSC is allowable if the KSC
> employee complies with paragraphs b, c, and d, below.
>
> b\. NASA Security, under the direction of the Installation Security
> Officer, may provide a waiver to this chapter for Spaceport Gun Club
> activities. Spaceport Gun Club members may request a waiver from NASA
> Security, to transport personal firearms and ammunition through KSC
> property to KARS Park. This waiver will allow the requester to have
> the weapon(s) and ammunition stored in the locked trunk of a vehicle,
> during duty hours.
>
> c\. To request a waiver, submit an AVO with the following information
> to NASA Security.
>
> **Note: All applicants will be subject to a complete background check
> to ensure eligibility under state and federal law to transport
> firearms.**
>
> \(1\) Name.
>
> \(2\) Complete home address.
>
> \(3\) Complete company address.
>
> \(4\) Organizational code and mail stop.
>
> \(5\) Office telephone number.
>
> \(6\) Social Security Number.
>
> \(7\) Spaceport Gun Club membership number with expiration date.
>
> \(8\) State the reasons for bringing the personal weapon and
> ammunition onto KSC (e.g. resides in Titusville; shoots at the gun
> club on Wednesday evenings, and does not want to make an additional
> round trip to pick up weapons; needs to travel through KSC property to
> save time and mileage, etc.).
>
> d\. Waivers are subject to the following conditions:
>
> \(1\) Firearms will be used **only** at the Spaceport Gun Club for
> practice and competition, during normal operating hours of the club.
>
> \(2\) Firearms are to be transported on KSC **only** on days they will
> be used at the club.
>
> \(3\) Firearms and ammunition must remain in the locked trunk of the
> vehicle and will not be shown, handled, displayed, or removed from the
> vehicle while on KSC.
>
> \(4\) No loaded firearms will be transported.
>
> \(5\) Any incidents relating to transported firearms must be reported
> immediately to NASA Security, at 867-2455.
>
> \(6\) Waivers are granted for a period of 12 months, and are not
> automatically renewable. Termination of active participation and/or
> membership in the Spaceport Gun Club will terminate the waiver.
>
> \(7\) Waivers are subject to cancellation at any time by NASA
> Security. Individuals will be notified in writing if a waiver is
> canceled.
>
> \(8\) Waivers are for KSC only. They **DO NOT** grant permission for
> transportation of weapons/ammunition on CCAFS.
>
> \(9\) If the waiver is granted, a letter of approval to transport
> firearms and ammunition will be issued by the Installation Security
> Officer. This letter will be kept with the weapons/ammunition while on
> KSC, and will be provided to KSC Security Forces or Law Enforcement
> Officers if you are stopped.

415.9 [PROHIBITED WEAPONS AND ITEMS]{.underline}

> a\. All KSC employees are prohibited from possessing or introducing
> unauthorized weapons onto KSC property.
>
> b\. KSC employees observing violations of the weapons (firearms)
> policy, or becoming aware of the presence of unauthorized and/or
> prohibited weapons, on KSC, should notify the Joint Communications
> Control Center (JCCC), at 867-2121.
>
> c\. J-BOSC Security Forces (contractor) and NASA Security credentialed
> Agents will take the necessary action to bar, intercept, remove,
> neutralize, confiscate, or otherwise eliminate unauthorized weapons
> from KSC.
>
> \(1\) Weapons or ammunition found in vehicles during spot checks
> inside the perimeter of KSC or found in parked vehicles, shall be
> confiscated. The owners shall be advised that privately owned weapons
> and ammunition are not permitted on KSC and may be picked up upon
> exiting. A property receipt will be filled out on all confiscations.
> All weapons shall be held at Patrol Headquarters (K6-2496) until
> returned to the owner.
>
> \(2\) If an individual voluntarily surrenders a weapon while
> attempting to enter KSC, he or she will be denied access until the
> following steps can be completed:
>
> \(a\) The weapon will be taken, and safed, by a Security Supervisor.
>
> \(b\) A property receipt will be issued to the owner.
>
> \(c\) The weapon will be transported to the Equipment Room at Patrol
> Headquarters.
>
> \(d\) The property receipt will be destroyed once the weapon is
> returned to the owner.
>
> d\. The following items are prohibited on KSC:
>
> \(1\) Personal firearms, other than as authorized by this Issuance.
>
> \(2\) Personal ammunition, other than as authorized by this Issuance.
>
> \(3\) Air rifles or pistols.
>
> \(4\) Switch blade knives.
>
> \(5\) Throwing knives.
>
> \(6\) Black jacks or saps.
>
> \(7\) Metal knuckles.
>
> \(8\) Martial arts offensive or defensive weapons.
>
> \(9\) Incendiary or pyrotechnic devices.
>
> \(10\) Explosives (including fireworks).
>
> \(11\) Any device/item known, or intended, to inflict injury or death
> or cause property damage, or any device/item specifically prohibited
> by city, county, state, or federal, law, statute, or regulation, etc.
>
> e\. If the status of an unlisted weapon or item is questionable, it
> will be referred to the Installation Security Officer for a further
> analysis and determination.

**CHAPTER 416**

**KSC FLAG POLICY**

416.1 [GENERAL]{.underline}

> The purpose of this chapter is to provide the guidance necessary to
> implement and maintain a consistent policy governing the flying of the
> United States flag on KSC.

416.2 [SCOPE]{.underline}

> This chapter applies to NASA, contractors and tenants on KSC which
> display the National Colors on exterior staffs. It establishes the KSC
> National Flag Retirement Program. It also provides a procedure by
> which deceased active, resident employees may be honored by the
> Center's flags being flown at half-staff and the employees next of kin
> receiving a flag flown at KSC, at or following the funeral. Deceased
> retired employees may be honored as described herein only if
> specifically approved by the Center Director.

416.3 [AUTHORITY]{.underline}

> The authority for this policy is derived from Public Law 94-344, "Flag
> of United States - Display Rules," Presidential Proclamation 3044,
> "Display of the Flag of the United States of America at Half-Staff
> Upon the Death of Certain Officials and Formal Officials (as
> amended)," and NPD 1020.2, "Displaying the United States Flag at
> Half-Staff."

416.4 [RESPONSIBILITIES]{.underline}

> a\. The Center Director , under the authority of NPD 1020.2, will
> appoint the KSC Flag Protocol Officer (FPO).
>
> b\. The Director of Spaceport Services under the authority of the
> Associate Administrator for Management Systems and Facilities (NASA
> Headquarters) will:
>
> 1\. Approve, or disapprove, the Center's honoring deceased active
> employees.
>
> 2\. Direct the Flag Protocol Officer (FPO) to implement the policy and
> procedures contained herein.

3.  Inform the Center Director when a deceased active employee is so
    honored.

> c\. Senior Managers for NASA, contractors and tenants will notify the
> FPO in case of the death of a active KSC employee. Notification may be
> made by calling either the Joint Communications Control Center at
> 867-2121, or NASA Security at 867-4612.
>
> d\. The FPO will coordinate all matters involving the flags of the
> United States on KSC. This includes, but is not limited to:
>
> 1\. Direct the J-BOSC Protective Services, Projects and Integration
> Office, 861-5657, to coordinate with KSC contractors and tenants to
> have the United States flag flown at half-staff at their respective
> facilities.
>
> 2\. Request publication of weekly KSC Bulletin notices, to inform the
> Center's employees for whom, and when the flag was flown at
> half-staff.
>
> 3\. Notify the Associate Administrator for Management Systems and
> Facilities, when and for whom the KSC flags were flown at half-staff.
>
> 4\. Manage the KSC National Flag Retirement Program.
>
> e\. J-BOSC Security will maintain a supply of flags of the United
> States, previously flown over KSC, to be cleaned, folded, and
> presented to the next of kin of deceased active KSC employees, or as
> directed by the FPO. The Property Custodian will ensure that with each
> flag, are the exclusive dates when the flag flew, and what missions
> were launched/landed during the flag's service.
>
> f\. NASA KSC welcomes tenants of KSC who fly the National Colors
> outside their facilities to participate in the KSC National Flag
> Retirement Program. Under this voluntary program, the tenant will
> provide their worn/tattered flags to the J-BOSC Security Property
> Custodian, who processes them as in the proceeding paragraph, thus
> ensuring the dignified and honorable disposition of the flag.

416.5 [PROCEDURES]{.underline}

> a\. The documents listed above in Section 416.3 - Authority, contains
> the procedures which KSC will follow in flying the flag of the United
> States, with the following additional provisions:
>
> 1\. The flag of the United States may also be flown at half-staff on
> the day of a deceased active KSC employee's funeral, or as directed by
> the Center Director.
>
> 2\. When the flag of the United States is flown at half-staff, no
> other flag will be flown on it's or adjacent flag poles.
>
> 3\. At KSC, all flags of the United States will be flown at either
> full staff or half-staff, simultaneously.
>
> 4\. Whenever the flag of the United States is flown at full staff,
> flags below it will be positioned so that when the flag of the United
> States lies fallow, it will not touch the flag below it.
>
> b\. The sequence of events for honoring deceased active KSC employees
> is:
>
> 1\. The deceased employees management notifies the J-BOSC Security or
> the FPO of the death of an active KSC employee.
>
> 2\. The FPO briefs the Director of Spaceport Services on the death and
> receives permission to honor the employee with the KSC flags being
> flown at half-staff on the day of the funeral, or as directed by the
> Center Director.
>
> 3\. The FPO procures a KSC flown flag, along with it's history, from
> the J-BOSC Security, Property Custodian and gives it to the employee's
> Senior Manager.
>
> 4\. Normally, the presentation of the flag to the next of kin will be
> made by the employee's Senior Manager, or their representative.
>
> 5\. The FPO ensures that an entry is made as soon as it is possible in
> the KSC Weekly Bulletin, when and for whom the flag of the United
> States was flown at half-staff at KSC.

**CHAPTER 501**

**KSC CHILD CARE DEVELOPMENT CENTER PROGRAM**

501.1 [GENERAL]{.underline}

> This document establishes KSC's policy and guidelines for the
> development and implementation of a Child Care Program in compliance
> with the Crime Control Act of 1990 with respect to the KSC Child Care
> Development Center (KSC-CDC) and screening of current and prospective
> Child Care Service Providers.

501.2 [RESPONSIBILITIES]{.underline}

> a\. The Protective Service Branch will be responsible for:
>
> \(1\) Serving as the point of contact with the Procurement Office for
> policies and procedures relating to personnel security investigations
> of Child Care Service Providers at the KSC-CDC.
>
> \(2\) Ensuring that all existing and newly hired Child Care Service
> Providers are the subject of a National Agency Check (NAC)(FBI
> Fingerprints and Name Check).
>
> \(3\) Local Law Enforcement checks will be conducted by the Personnel
> Security Support Office (PSSO) and will cover areas of residence for
> the past 5 years. Law Enforcement checks will also be conducted on any
> residences outside of the local area.
>
> \(4\) Evaluating the results of the NAC and local records check.
>
> \(5\) Maintaining a security file on all Child Care Service Providers.
> Placing all Child Care Service Providers in a "Monitored" status.
>
> \(6\) Annually, based on Child Care Service Provider's hire date,
> local Law Enforcement, Brevard County Court records, and drivers
> license checks will be conducted.
>
> \(7\) Providing any adverse information resulting from the NAC or
> Local Law Enforcement checks, in writing, concerning Child Care
> Service Providers to the Director, Procurement/KSC-Exchange Operations
> Manager for a determination of suitability for employment.
>
> \(8\) Providing KSC-CDC with required forms (SF85P, "Questionnaire for
> Public Trust Positions," SF87s, "Fingerprint Cards," and the NASA 531,
> "Name Check Request").
>
> \(9\) Routing all correspondence and information pertaining to and for
> KSC-CDC through KSC-Exchange Operations Manager.
>
> b\. The Procurement Office is responsible for:

1.  Acting as point of contact between KSC-CDC and NASA Protective
    Services.

> \(2\) Making suitability for employment determinations concerning
> adverse information obtained on Child Care Service Providers.
>
> c\. The Director of the Child Care facility (KSC-CDC) is responsible
> for:
>
> \(1\) Notifying Protective Services when hiring Child Care Service
> Providers and initiating security investigations.
>
> \(2\) Maintaining a current listing of all individuals who come in
> contact with the children at the KSC-CDC either in a teaching or
> non-teaching capacity.
>
> \(3\) Providing in accordance with the Draft NASA Federal Personnel
> Manual (FPM) Supplement to implement the "Crime Control Act of 1990,"
> direct line-of-sight supervision to those Child Care Service Providers
> whose background investigations have not been completed.
>
> \(4\) Annually, submitting (5 days prior to the employment anniversary
> "Date of Hire") for each Child Care Service Provider, a KSC Form 4-649
> NS and the EHS-14, "Caretaker Background Screening Information" form.
>
> \(5\) Notifying Protective Services of the termination of any Child
> Care Service Provider.

501.3 [INITIATING INVESTIGATIONS FOR NEW CHILD CARE SERVICE
PROVIDERS]{.underline}

> a\. The Director of the Child Care Development Center initiates the
> investigation process on a new Child Care Service Provider by
> submitting, within 3 days of hire to Protective Services, Form CHS-48
> "Request for Local Law Enforcement Check for Applicants/Employer," and
> EHS-14, "Caretaker Background Screening Information" Form.
>
> b\. KSC-CDC will provide the Child Care Service Provider with all the
> required security forms prior to his/her entering on duty (EOD).
>
> c\. The Child Care Service Provider has 5 working days to submit
> his/her completed forms (SF 85P, "Questionnaire for Public Trust
> Position," 2 SF 87s, "Fingerprint Cards," and a NASA Form 531, "Name
> Check Request") to Protective Services through KSC-CDC.
>
> d\. KSC Picture Badge will not be issued to a new Child Care Service
> Provider until completed security forms are submitted to Protective
> Services.
>
> e\. Forms which are incomplete, or improperly executed will be
> returned to the Child Care Service Provider for completion.
>
> f\. KSC-CDC will furnish to Protective Services a copy of all forms
> submitted to the State of Florida ("Affidavit of Compliance with
> Fingerprint Requirements," and the "Affidavit of Good Moral
> Character") on each employee. A copy of the results of the report will
> also be furnished to Protective Services.

501.4 [DISQUALIFYING CRITERIA]{.underline}

> a\. Mandatory Disqualifying Criteria:
>
> The following findings shall result in a determination that the
> individual is not qualified for employment as a Child Care Service
> Provider. Any conviction for a sexual offense, a drug felony, or a
> criminal offense involving a child or children. Examples of specific
> conduct which will be considered a basis for disqualification include:

1.  Conviction of the crime of abuse or neglect of a child or other
    dependent person entrusted to their care; child molestation.

> \(2\) Found negligent in a mishap causing death or serious injury to a
> child or other dependent person entrusted to their care.
>
> \(3\) In the absence of convictions, when the examination of the
> circumstance involved is a pattern of arrests, or an arrest for a
> single serious crime, indicates that an employee is unsuitable for a
> position.
>
> \(4\) Use, possession and sale of narcotics and dangerous drugs,
> arson, forcible or statutory rape, murder, kidnapping, robbery,
> burglary, larceny, theft, aggravated assault, buying, receiving, or
> possessing stolen property, embezzlement, forgery, counterfeiting, and
> fraud.
>
> \(5\) Committed voluntarily or involuntarily to a mental hospital or
> institution, unless the employee can present medical certification of
> recovery.
>
> \(6\) Been acquitted of any criminal charge by reason of insanity or
> being found to be a chronic alcoholic by any court, unless the
> employee can present medical certification that he/she has recovered.
>
> \(7\) Is a fugitive from justice.
>
> \(8\) Is an illegal alien in the U.S. or is an alien who is not
> entitled to accept gainful employment.

(8) Serious misconduct while in the military service which is indicative
    of conduct unsuitable for the position.

> b\. Discretionary Criteria:
>
> The following findings may be considered as a basis for not employing
> an individual in a position as a Child Care Provider:
>
> \(1\) Acts that may tend to indicate poor judgment, unreliability, or
> untrustworthiness in working with children.
>
> \(2\) Any behavior, illness, mental, physical, or emotional condition,
> that in the opinion of a competent medical authority, may cause a
> defect in judgment, or reliability.
>
> \(3\) Offenses involving assault, battery, or other abuse of a victim,
> regardless of age of the victim.
>
> \(4\) Evidence or documentation of substance abuse dependency.
>
> \(5\) Illegal or improper use, possession, or addiction to any
> controlled or psychoactive substances, narcotic, cannabis, or other
> dangerous drug.
>
> \(6\) Sexual acts, conduct or behavior that, because of the
> circumstances in which they occur, may indicate untrustworthiness,
> unreliability, lack of judgment, or irresponsibility in working with
> children.

501.5 [ADVERSE INFORMATION]{.underline}

> a\. Adverse or derogatory information resulting from criminal history
> background checks will be summarized by PSSO and evaluated by
> Protective Services.
>
> b\. A copy of adverse information along with a copy of the Subject
> Interview will be sent to Director of Procurement/KSC-Exchange
> Operations Manager for a determination of suitability for employment.
>
> c\. OP will notify Protective Services, in writing within 30 days of
> their final determination of suitability for employment.

501.6 [PERIODIC REINVESTIGATIONS]{.underline}

> a\. On an annual basis, local records checks will be conducted by the
> PSSO. These checks will include Brevard County Court records, and
> State of Florida Driver's License check.
>
> b\. These checks will be conducted on the anniversary of the "Date of
> Hire" for a Child Care Service Provider. Five (5) working days prior
> to a Child Care Service Provider's anniversary date the Child Care
> Director will submit to Protective Services a "Request for Agency
> Checks" (Form KSC 4-649 NS), and the "Caretaker Background Screening
> Information" (Form EHS-14).

**CHAPTER 502**

**FEDERAL EMPLOYEE SECURITY PROGRAM**

**(FESP)**

502.1 [GENERAL]{.underline}

> The Center Director delegates to the CCS authority to grant security
> clearances to employees under his jurisdiction subject to the
> eligibility standards.
>
> The Federal Employees Security Program insures that:
>
> a\. All new civil service employees are the subject of a Personnel
> Security Investigation.
>
> b\. All civil service employees requiring access to classified
> information are investigated and adjudicated to the appropriate
> security clearance level (Top Secret, Secret, or Confidential) and
> that their position sensitivity level reflects their level of access
> to classified information. Investigations are updated in accordance
> with Office of Personnel Management (OPM) guidelines.
>
> c\. All civil service employees are investigated based on their
> position sensitivity level as it relates to their job functions and
> responsibilities. This position sensitivity designation is dependent
> of any requirement for access to classified information.
> Investigations are updated in accordance with OPM guidelines.

502.2 [POSITION SENSITVITY LEVELS]{.underline}

> All civil service positions are designated at one of four position
> sensitivity levels. They are Nonsensitive (NS), Noncritical Sensitive
> (NCS), Critical Sensitive (CS), and Special Sensitive (SS). The
> position sensitivity level is a reflection of the security clearance
> (Confidential, Secret, Top Secret) required by a position and/or the
> duties and responsibilities (positions of trust, potential damage to
> efficiency of the service) associated with the position. As an
> example, a civil servant granted a Top Secret clearance to work on a
> special project would have a CS position sensitivity level. That same
> person, based on his duties and responsibilities, may have a position
> sensitivity level of NCS. In such a case, the individual is
> investigated at the higher level. As another example, a civil servant
> could have no security clearance, but be designated at the CS level
> based solely on his duties and responsibilities and the potential harm
> he/she could cause to the Government. The investigative requirements
> for each of the four position sensitivity levels are as follows:
>
> **[Position]{.underline} [Type of Investigation]{.underline}
> [Forms]{.underline}**
>
> a\. Nonsensitive National Agency Check w/ SF85,SF87,
>
> Written Inquires (NACI) OF306,OF612
>
> b\. Noncritical Limited Background SF86, SF87
>
> Sensitive Investigation(LBI)
>
> c\. Critical Single Scope Background SF86, SF87
>
> Sensitive Investigation (SBI)
>
> d\. Special Single Scope Background SF86, SF87
>
> Sensitive Investigation (SBI)

502.3 [RESPONSIBILITIES]{.underline}

> a\. The FESP Manager, Protective Service Branch, is responsible for:
>
> \(1\) Ensuring that civil employees are investigated and adjudicated
> in accordance with the Government issuance's referenced in the list of
> references.
>
> \(2\) Receiving and approving requests for security clearances and
> reviewing and changing, as necessary, the position sensitivity level
> to ensure that it adequately reflects the level of approved access to
> classified information.
>
> \(3\) Serving as primary point of contact with the Workforce &
> Diversity Management Office for policies and procedures relating to
> the FESP.

b\. The Director, Workforce & Diversity Management Office is responsible
for:

> \(1\) Coordinating investigative requirements for new hire civil
> service employees with the FESP Manager.
>
> \(2\) Designating position sensitivity levels for each civil service
> position based on duties and responsibilities (not involving access to
> classified information).
>
> \(3\) Making suitability determinations for all civil service
> employees.
>
> **[Note:]{.underline}** Review and disposition of adverse OPM reports
> of investigation will be completed within ninety days in accordance
> with OPM guidelines. The FESP Manager will be advised of disposition
> in order to forward a response to OPM.

502.4 [NASA PRE-EMPLOYMENT SCREENING]{.underline}

> The Protective Services Branch conducts pre-employment screening on
> potential NASA new hires. The pre-employment screening may include
> criminal, education, credit, driving record checks, employment
> verifications, and reference checks. The results of re-employment
> screenings are provided to the Personnel Office.

502.5 [INITIATING INVESTIGATIONS FOR NEW NASA EMPLOYEES]{.underline}

> a\. The Workforce & Diversity Management Office (W&DMO) initiates the
> investigative process by submitting required forms (KSC Form 20-14NS,
> "Personnel Security Worksheet" and two copies of employee's OF306,
> "Declaration for Federal Employment") to Protective Services for
> review and determination of investigative requirements. The original
> KSC Form 20-14NS, annotated with the type of investigation required,
> is returned to W&DMO. W&DMO provides the employee with the appropriate
> security forms either prior to his/her entering on duty date (EOD) or
> on the first day of employment. The employee has 5 working days to
> submit his/her completed security forms to Protective Services.
>
> b\. Three days prior to a new employee's EOD, W&DMO will submit to
> Protective Services, requests for a 5-day Temporary Pass and a NASA
> Identification Badge. A NASA Identification Badge will not be issued
> to a new employee until he/she submits the completed security forms to
> Protective Services.

502.6 [PERIODIC REINVESTIGATIONS]{.underline}

> a\. Special Sensitive and Critical Sensitive Positions. Civil service
> employees in these positions will be subject to reinvestigation 5
> years after placement, and every succeeding 5 years.
>
> b\. Noncritical Sensitive Position. Civil service employees in these
> positions will be subject to reinvestigation 10 years after placement
> and every succeeding 10 years.
>
> c\. Nonsensitive Positions. Civil service employees in these positions
> are not subject to reinvestigation.
>
> d\. Protective Services will furnish appropriate security forms to
> civil service employees due for reinvestigation. Employees have 30
> calendar days to complete the forms and return them to Protective
> Services. If the employee cannot complete forms because of extended
> TDY or emergency leave, the employee should contact Protective
> Services and request additional time to complete the forms. Failure to
> complete the forms by the requested date may result in loss of
> security clearance or other certification with an investigative basis.

502.7 [SECURITY CLEARANCES]{.underline}

> a\. A security clearance is an approval for access to classified
> national security information. Security clearance are granted by
> authorized federal organizations based on an appropriate level of
> investigation of an individual. Security clearances grant access to a
> level of classified information
>
> (Confidential, Secret, or Top Secret) for a specific purpose.
>
> b\. A security clearance is terminated when an employee no longer
> requires access to classified information or ends his/her employment
> with the issuing Federal agency. For example, when a civil service
> employee leaves another government agency and joins NASA his/her
> security clearance with the other agency is no longer active and the
> individual is not authorized access to classified information. If the
> employee requires access to classified information as part of his/her
> new job at NASA, NASA will take appropriate action to grant a security
> clearance.
>
> c\. KSC will not honor a security clearance granted by another agency
> for access to classified information under KSC's control, unless there
> is a relationship between that agency and NASA and a basis for doing
> so. For example, an employee may be cleared for an assignment in the
> military reserves; but the clearance is invalid at KSC because there
> is no relationship between the reserve unit and KSC. On the other
> hand, KSC has a relationship with the Defense Industrial Security
> Clearance Office (DISCO) and frequently honors clearances of defense
> contractors. However, if the individual's work for KSC is not under a
> classified contract, the clearance will not be accepted since there is
> no basis for doing so.
>
> d\. While security clearances do not transfer from one agency to
> another, the results of background investigations, which are the basis
> for granting clearances, are available to all federal agencies. If the
> investigation is adequate in scope and is not outdated, a previous
> investigation may be used for granting a security clearance by NASA.

502.8 [SECURITY CLEARANCES FOR CIVIL SERVANTS]{.underline}

> a\. NASA employees will be granted security clearances only when a
> demonstrated need exists for the performance of their duties.
>
> b\. A NASA Form 1630, "Request for Access to Classified National
> Security Information," will be submitted to the Protective Service
> Office/NASA Security (Protective Services), and used to document the
> justification of each security clearance request. The form must be
> prepared and certified by the employee's immediate supervisor,
> reviewed by a designated management official (division chief, or
> higher, depending on the employee's organizational position), and
> approved by the Installation Security Officer (Chief, Protective
> Services Branch).
>
> c\. If an employee's personnel security folder does not contain the
> results of an adequate previous background investigation commensurate
> with the level of clearance requested, the employee will be provided
> with security forms to complete and submit to Protective Services.
>
> d\. The granting of a security clearance will be documented on NASA
> Form 346, "Notification of Completion of Investigation Under EO 10450,
> and/or Certificate of Clearance."
>
> e\. When clearances are no longer required, employees will be notified
> through their supervisors that their security clearances are being
> administratively withdrawn without prejudice to the individual.
>
> f\. A security clearance recertification must be submitted annually,
> or whenever a person changes positions. Failure to provide an annual
> recertification to Protective Services will result in administrative
> withdrawal of an employee's security clearance.
>
> g\. Before a clearance is granted, the employee must attend required
> security education courses. He/she must also sign a Standard Form 312,
> "Classified Information Nondisclosure Agreement." At the time the
> employee receives the security clearance his/her supervisor will brief
> the employee on his/her specific classified duties. The briefing will
> be documented on NASA Form 838, "Employee Security
> Orientation/Indoctrination Record," which the supervisor will sign as
> the Orientation Officer and forward to Protective Services.

502.9 [CERTIFYING SECURITY CLEARANCES FROM KSC]{.underline}

> NASA personnel on travel status who require access to classified
> information at a defense contractor or other Government agency may
> have their security clearance certified to that organization. A KSC
> Form 20-21NS, "Clearance Verification, Telegram Format," should be
> prepared by the employee's office an forwarded to Protective Services
> for processing.

502.10 [CERTIFYING SECURITY CLEARANCES TO KSC]{.underline}

> a\. NASA participates in the National Industrial Security Program. The
> Defense Industrial Security Clearance Office (DISCO) grants personnel
> security clearances to defense contractors which will be honored at
> KSC when contractor employees are working under a classified contract
> and have classified work to perform at KSC. Contractor employees
> should consult their respective company security offices for guidance
> and instruction regarding clearances.

b.  KSC will honor clearances of employees of other Government agencies
    who are conducting classified work at KSC.

> c\. Cleared employees of defense contractors and other federal
> agencies should send their visit notices and clearance verification
> to:

NASA Visitor Record Center

ATTN: VRC

Kennedy Space Center, FL 32899

> d\. Security clearances granted by NASA Headquarters and other NASA
> Centers, will be honored and accepted at KSC. NASA Centers exchange a
> monthly listing of employees who have been granted clearances. If the
>
> employee has a NASA badge/identification card, it will not be
> necessary for NASA Headquarters or other NASA Center employees to send
> clearance verification to KSC.

502.11 [CO-OPERATIVE (CO-OP) EDUCATION STUDENTS]{.underline}

> a\. Initially, Co-op students entering on duty will be processed in by
> Personnel and Security in the same manner as new NASA employees.
>
> b\. When a Co-op student goes on Leave Without Pay (LWOP) status to
> return to school, he/she will return his/her KSC badge to W&DMO at the
> Headquarters Building, Room 1218. W&DMO will return the badge to
> Protective Services.
>
> c\. When a Co-op student returns to duty, the Policy & Special Program
> Branch will request in writing, prior to the student's return, his/her
> badge from Protective Services. The Co-op will obtain his/her badge
> from Policy & Special Program Branch at the Headquarters Building.

CHAPTER 503

PERSONNEL RELIABILITY PROGRAM

(PRP)

503.1 [GENERAL]{.underline}

> The NASA Personnel Reliability Program (PRP) ensures that personnel
> assigned to mission critical positions/duties relating to the Space
> Shuttle and other critical space systems, including the Space Station,
> designated Expendable Launch Vehicles (ELV's), designated payloads,
> Shuttle Carrier Aircraft and other designated resources that provide
> access to space meet suitability screening requirements prior to
> unescorted access to areas where the Space Shuttle and/or any of the
> other systems are located. The Space Shuttle and other systems are
> "mission critical space system". "Mission critical positions/duties"
> are those positions/duties which if performed in a faulty, negligent
> or malicious manner, could jeopardize these systems or delay a
> mission.

503.2 [RESPONSIBILITIES]{.underline}

> The Center Director is responsible for designating KSC mission
> critical system areas, and designating the following management
> officials responsible with the following tasks:
>
> a\. The KSC PRP Manager, Protective Services Branch, is responsible
> for:
>
> \(1\) Administering the KSC Personnel Reliability Program.
>
> \(2\) Approving PRP certification of civilian and contractor
> employees.
>
> \(3\) Referring cases to the Installation Security Officer (ISO),
> Protective Services Branch, which based on the Adjudication Guidelines
> contain unreasonable issues, thus requiring temporary suspension of
> PRP until further investigation can be conducted and issues resolved.
>
> \(4\) Referring cases to the Personnel Reliability Board (PRB) which
> contain significant issues that were unable to be resolved by the PRP
> Manager or ISO.
>
> \(5\) Ensuring that the individuals certified under the PRP remain
> current in their update screening and withdrawing PRP certifications
> from those individuals who fail to submit their forms by the date
> instructed or who no longer have a requirement for unescorted access
> to mission critical space systems areas.
>
> \(6\) Serving as primary point of contact with the KSC civilian and
> contractor personnel offices for policies and procedures relating to
> the PRP.
>
> b\. The Personnel Security Support Office (PSSO) is responsible for:
>
> \(1\) Notifying employees, appropriate contractor security offices, or
> administration offices when an employee's certification for PRP
> requires reinvestigation. Appropriate forms and instructions are
> provided for the reinvestigation.
>
> \(2\) Reviewing forms submitted for Interim PRP, PRP, or
> recertification for accuracy and completeness and comparing submitted
> forms with previous forms submitted for any new information revealed,
> or information which may have been omitted. Any discrepant or
> derogatory information revealed at this time is brought to the
> attention of the PRP Manager for guidance concerning interviews,
> medical, employer's evaluation, etc. Forms are then suspended and
> inquires made of the appropriate agencies (e.g., FBI, state and local
> law enforcement, Motor Vehicles) and files are suspension until
> response are received.
>
> \(3\) Summarizing investigative data mentioned in 503.2a(2) and
> bringing cases with discrepant or derogatory to the PRP Manager for
> final adjudication.
>
> \(4\) Acting for the KSC PRP Manager in approving PRP certification or
> recertification on any employee's case which is clear of discrepant or
> derogatory information.
>
> \(5\) PSSO has direct accountability to the NASA Protective Services
> Branch. Due to the sensitive nature of the information dealt with on a
> daily basis, the employees staffing the PSSO have met the minimum
> requirements of a favorable Background Investigation (BI).
> Dissemination of any of this information to anyone outside of the NASA
> Protective Service Office is ground for immediate dismissal.
>
> c\. The Chief, Medical and Environmental Health Office, is responsible
> for reviewing case files involving medical issues and rendering
> medical opinions regarding mental stability and/or physical
> reliability for consideration by the Board.
>
> d\. The Director, Procurement, is responsible for taking necessary
> action to direct heads of prime contractor organizations to:
>
> \(1\) Establish internal administrative procedures which ensure that
> all contractor and subcontractor personnel occupying Mission Critical
> Positions as defined in this Handbook, or who require unescorted
> access to Mission Critical Space Systems Areas (all areas controlled
> under the KSC Area Permit System and other designated facilities,
> areas, operations, or flight hardware) are identified and submitted
> for investigation and certification under the NASA Personnel
> Reliability Program.
>
> \(2\) Conduct periodic reviews at least annually of contractor and
> subcontractor positions and make certain that all Mission Critical
> Positions have been identified under the NASA Personnel Reliability
> Program. To aid contractor organizations in these reviews, Protective
> Services will provide each primary contractor organization with a
> listing of personnel who are badged for access to KSC but who do not
> possess a certification under the NASA PRP Program. Contractor
> organizations should carefully review these listings to ensure that
> none of the personnel identified are in Mission Critical Positions.
> These listings will be provided to contractor organizations on a
> semi-annual basis. The contractor organizations review should include
> all persons employed under NASA contract including those persons who
> do not require access to KSC.
>
> \(3\) Provide information, as requested by NASA, on any matter
> pertaining to the contractor organizations implementation of the
> requirements and procedures contained in this KHB.
>
> \(4\) Indicate on adverse reports provided to Protective Services, in
> accordance with the requirements of this KHB, whether the individual
> occupies a Mission Critical Position.
>
> \(5\) Assign, employ, or retain personnel in Mission Critical
> Positions, or use personnel to perform any mission critical duty, only
> if the individuals have been certified under Mission Critical Space
> Systems Personnel Reliability Program. (Note: Real-time operational
> situations may require non PRP certified "expert technicians" to visit
> KSC and perform mission critical work. Other situations may require
> the real-time delivery, installation and checkout of computer or test
> equipment. It is recognized that in an operational environment it is
> impossible to anticipate all situations. As a rule, every effort
> should be made to identify in advance, persons who may be required to
> perform the duties of a mission critical position and submit these
> persons for PRP certification. In real-time situations where visiting
> technicians are not PRP certified, work controls, to include escort
> and observation by technically knowledgeable KSC personnel, proper
> work authorizations, review and sign-off by quality assurance
> personnel, etc., will have to suffice. The need for real-time
> expediencies and the utilization of non-PRP certified to perform
> mission critical work should be understood and approved by
> management.)
>
> \(6\) Provide requested information when submitting individuals for
> certification to a Mission Critical Position and when requesting
> unescorted access.
>
> \(7\) Require that supervisors brief PRP candidates and re-brief PRP
> personnel on the needs and intent of PRP.
>
> e\. The PRP Board is responsible for:
>
> \(1\) Reviewing individual cases referred to the Board for
> certification under the Mission Critical Space System Personnel
> Reliability Program and/or for authorizing or denying unescorted
> access to KSCAP areas.
>
> \(2\) Reviewing and designation of positions as mission critical and
> designating, or removing the designation of, a position as mission
> critical for cases that come before the Board.
>
> \(3\) Policies, procedures, and membership information relating to the
> PRP Board are provided in KMI 1150.24.
>
> f\. Supervisors are responsible for:
>
> \(1\) Identifying and designating those positions, and the incumbent
> employee for each, within their organization which meet the definition
> of a mission critical position.
>
> \(2\) Ensuring that only personnel who have been certified under
> Mission Critical Space Systems Personnel Reliability Program are
> assigned to mission critical positions/duties within their
>
> organization.
>
> \(3\) Reviewing for reliability and nominating personnel whose duties
> require certification under the PRP.
>
> \(4\) Certifying that the PRP Candidate holds current licenses, skill
> training certificates, and other documentation issued as required by
> applicable
>
> directives.
>
> \(5\) Monitoring and continually evaluating personnel for steady,
> reliable performance and notifying the certifying official if changes
> occur which may compromise the safety and reliability of mission
> critical space systems.
>
> \(6\) Briefing PRP candidates and rebriefing PRP personnel on the
> needs and intent of the PRP.

503.3 [MISSION CRITICAL SPACE SYSTEMS AREAS (MCSSA)]{.underline}

> "Director of each NASA Installation will designate mission critical
> space systems areas." At KSC, Protective Services is responsible for
> preparing and submitting to the Center Director, a listing of proposed
> MCSSAs. Protective Services is responsible for maintaining a current
> listing of KSC MCSSA's, as approved by the Center Director, is
> provided in Appendix C to this Handbook.

503.4 [OTHER AREA DESIGNATION PERSONNEL SCREENING
REQUIREMENTS]{.underline}

> a\. NASA SECURITY AREAS. NHB 1620.3 authorizes the Center Director to
> designate Security Areas (Restricted, Limited and Closed Areas) for
> the protection of government property and classified national security
> information. Facilities designated as Limited Areas for protection of
> flight hardware and/or other NASA resources require personnel with
> unescorted access to such areas, to be the subject of a favorably
> completed National Agency Check. At KSC, all Limited Areas identified
> for the protection of flight hardware will be designated as "mission
> critical space system areas" under the PRP and certification under the
> PRP will meet the personnel screening requirements for Limited Areas.
> Limited and Closed Areas created for the protection of classified
> national security information will require the appropriate security
> clearance level for unescorted access.
>
> b\. NASA RESOURCE PROTECTION (NRP) PROGRAM CATEGORY A & B ASSETS. NHB
> 1620.3 requires KSC to designate NRP Category A (Mission Critical) and
> Category B (Mission Essential) Assets. Personnel requiring unescorted
> access to NRP Category A and/or B facilities must be the subject of a
> favorably completed National Agency Check. At KSC, all NRP Category A
> & B Assets will be designated by the Center Director, KSC, as "mission
> critical space systems areas" under the PRP and certification under
> the PRP will meet the personnel screening requirements for NRP
> Category A & B Assets.
>
> c\. KSC AREA PERMIT SYSTEM. All areas and flight hardware proximity
> codes identified under the KSC Area Permit System will be designated
> as "mission critical space systems areas" by the Center Director.
> Issuance of a KSC Area Permit or a non-escorted Temporary Area
> Authorization to an individual is evidence of favorable certification
> under the NASA PRP.

503.5 [AUTHORIZED REQUESTERS]{.underline}

> Initially, PRP certification must be requested by one of the persons
> or organizations identified below. Thereafter, the same requester will
> be notified when rescreening is required for recertification of PRP.
> The requesters are expected to submit the forms or information
> identified in paragraph 503.8 below, both for initial PRP requests and
> for subsequent recertification. The following are authorized to
> request PRP certifications:
>
> a\. NASA KSC civil service supervisors for their employees, or their
> designated civil service administrative office.
>
> b\. Authorized badging officials for employees of their organizations,
> contractors, and subcontractors.
>
> c\. Contacts for other visitors to KSC.

503.6 [ACCEPTANCE OF OTHER PROGRAMS]{.underline}

> a\. Usually, the following will be considered to have met the
> screening and evaluation requirements of this chapter:
>
> \(1\) Flight crews and payload specialists who are covered by other
> regulations which require screening and evaluation commensurate with,
> or exceeding, that required by this chapter.
>
> \(2\) Persons certified by NASA Headquarters, other NASA centers, or
> other agencies under the NASA Mission Critical Space Systems Personnel
> Reliability Program.
>
> \(3\) Others who can prove screening under federal law or regulation
> commensurate with, or exceeding, that required by this chapter. In
> addition, they must prove the results of the screening have been
> evaluated with the same intent and considerations as set forth in this
> chapter. Clearance for access to classified material is not deemed to
> be adequate.
>
> \(4\) Foreign Representatives who have been accredited by the Office
> of International Affairs, NASA
>
> Headquarters, may be authorized unescorted access to mission critical
> space systems areas, but only to those areas for which they have
> operational
>
> need, and excluding those areas which protect the Space Shuttle or
> classified national defense information.
>
> b\. Persons who are given PRP certification pursuant to this paragraph
> do not need to submit forms required by paragraph 503.5. Instead, the
> organization which has screened and evaluated them, and which has the
> approval of the Protective Service Office, must provide the following
> information, in writing, for each person:
>
> \(1\) Full name.
>
> \(2\) Date and place of birth.
>
> \(3\) Social security number. Passport, visa or alien registration
> numbers may be used in lieu of a social security number for aliens.
>
> \(4\) The name of the screening program and a certification that the
> results of screening have been favorably evaluated.
>
> \(5\) An expiration for the certification, not to exceed one year.
>
> c\. This information must be sent to the PSSO at the address in
> paragraph 503.8b below.
>
> d\. The organization will be notified when the certification is about
> to expire. It will be given an opportunity to renew it by rescreening
> and re-evaluating the person and providing a new certification.

503.7 [VERIFYING PRP CERTIFICATIONS TO OTHER INSTALLATIONS]{.underline}

> a\. Every person who has unescorted access to KSC mission critical
> space systems areas is certified under the PRP. With the exception of
> those who are given unescorted access pursuant to paragraph 503.4 the
> PRP certifications have been granted KSC. KSC's PRP certifications are
> acceptable to other NASA centers and to some other Government
> installations, such as, Vandenberg AFB, and may be required for other
> access privileges there. Personnel who are PRP-certified by KSC and
> who need their certification verified to another installation must use
> the following procedure:
>
> \(1\) Prepare a letter to the installation on your organization's
> letterhead stationery.
>
> \(2\) Address the letter to the office which maintains the
> installation's records of PRP certifications. Your point of contact at
> the installation should be able to provide the address.
>
> \(3\) In the correspondence, include the full names, dates of birth,
> places of birth, and social security numbers of those individuals
> whose certifications need to be transmitted.
>
> \(4\) Send the letter to PSSO Personnel Security Support Office. When
> time is short, the letter may be hand-carried to Room 1503, KSC
> Headquarters Building.
>
> b\. The PSSO will verify the certifications, add their expiration
> dates, endorse your letter, and mail it to the other installation.
>
> c\. Once a person's certification has been verified, it should not be
> necessary to send it again to the same installation until it is
> renewed. Certifications that require renewal should be re-sent as
> needed.

503.8 [FORMS AND PROCEDURES]{.underline}

> a\. The following forms are routinely used in the PRP for conducting a
> National Agency Check and/or rescreening. Samples and instructions for
> filling out these forms are provided by PSSO:
>
> \(1\) KSC Form 20-87, "Request for Investigation and Unescorted Access
> Badge."
>
> \(2\) KSC Form 20-90, "KSC Badge & Area Permit Investigative Data
> Badge."
>
> \(3\) NASA Form 531, "Name Check Request."
>
> \(4\) SF-87, "Fingerprint Chart for Federal Employees" or FD-258,
> "Fingerprint Chart for Federal Employees" or SF-87, Fingerprint Chart
> for Non-Federal Employees.
>
> b\. Forms should be mailed or hand carried to:
>
> Personnel Security Support Office
>
> PSSO
>
> Rm. 1503, HQ Bldg.
>
> Kennedy Space Center, FL 32899
>
> c\. Forms which are incomplete, incorrect, or improperly executed will
> not be processed and will be returned. For initial submissions, the
> requester will be notified when the forms have been accepted for
> processing. He/she will be informed when unescorted access to mission
> critical space systems areas is initially authorized but will not,
> when it is renewed.
>
> d\. PRP will be administratively revoked on those individuals whose
> forms for renewal are not submitted within the given time frame. The
> requester will be notified of the revocation and a request made to
> return the KSC Area Permit and PACAS badges by that date since the
> badges will become inactive on the revocation date. If renewal forms
> are turned in after the revocation date an additional form will be
> required for the Visitor Records Center, a new KSC Form 20-94, Kennedy
> Space Center Area Permit Application (KMI 1610.5). This form can be
> mailed or hand-carried to:
>
> Visitor Record Center
>
> VRC
>
> Rm. 1470, HQ Bldg.
>
> Kennedy Space Center, FL 32899

503.9 [SPECIFIC CRITERIA]{.underline}

> Results of screening will be evaluated to determine if authorizing
> unescorted access to mission critical space systems areas is clearly
> consistent with the preservation of national resources, government
> property and facilities, and a safe working environment. In addition
> to the guidelines of Appendix A, evidence of any of the following
> conditions is reason to question a person's reliability and may be
> used to deny unescorted access to mission critical space system areas:
>
> a\. Negligence, inadequacy, or delinquency in duty performance.
>
> b\. Any significant physical or mental impairment, character disorder,
> or aberrant behavior substantiated by medical authority that might
> jeopardize national resources, government property and facilities, or
> a safe working environment.
>
> c\. Behavior patterns that demonstrate or suggest a contemptuous
> attitude toward the law or Federal, State or local regulations.
>
> d\. Behavior that indicates a disregard for national resources,
> government property and facilities, and a safe working environment.

503.10 [DISPOSITION OF CASES WITH ADVERSE INFOMATION]{.underline}

> a\. In those cases where evaluation fails to clearly support the
> granting of PRP certification, the PRP Manager will take appropriate
> investigative, or other actions to resolve the adverse issues
> involved. If the adverse issues are of such a nature that they cannot
> be resolved, the PRP Manger will prepare the case for submission to
> the Personnel Reliability Board. The PRP Board may deny or approve PRP
> certification and may set conditions on any area or system accesses
> which it approves.
>
> b\. If a case has potentially disqualifying information and the person
> has unescorted access to mission critical space systems areas, the PRP
> Manager, with concurrence of the Installation Security Officer, may
> temporarily suspend PRP certification.

503.11 [EMPLOYMENT STATUS]{.underline}

> Individuals who surrender their badge due to a change in employment,
> the unescorted access authorizations will continue for 30 days. If the
> person returns within the 30 days, the authorization will be
> automatically continued until its normal expiration; no forms are
> required. After 30 days, the authorization may be reinstated upon
> submission of the KSC Form 20-87 and KSC Form 20-90 to the PSSO. Once
> the normal expiration date has passed, application for unescorted
> access must be according to the provisions in paragraph 503.8

503.12 [INTERIM PRP]{.underline}

> a\. Interim PRP can be granted to new civil service employees who have
> had a favorable pre-employment screening; or are transferring from
> another federal agency in which a favorable investigation was
> completed within the last five years.
>
> b\. Resident contractor organizations can request Interim PRP for new
> employees after the company has performed a contractor pre-employment
> screening. The pre-employment screening will include all of the checks
> required by the NASA Internal Security Office (i.e., a check of the
> criminal history records, previous employment, residences, education,
> verification of professional licenses (if applicable), and a DD 214).
> The contractor will then forward the completed pre-employment
> screening, NAC forms (see paragraph 503.8) and KSC Form 20-182NS,
> "Request for Interim Unescorted Access," to the PSSO. After a review
> of all information received a determination for Interim PRP will be
> made. The contractor organization will be notified if IUA cannot be
> granted.
>
> c\. Construction employees performing working in limited areas can
> provide NAC form (see paragraph 503.8) to the Contracting Officer for
> submission to the NASA Internal Security Office. Investigation
> activities will take approximately 7-10 days.
>
> **[Note:]{.underline}** In addition to the routine information
> requested on the NAC forms, the driver's license number is required on
> the top of the KSC Form 20-90, and the contract number and "Request
> for IUA" is needed on the KSC Form 20-87. The Contracting Officer will
> be notified if Interim PRP cannot be granted.

**CHAPTER 504**

**AUTOMATED INFORMATION PERSONNEL SECURITY PROGRAM**

504.1 [GENERAL]{.underline}

> To ensure that Government and contractor personnel associated with
> NASA Automated Information Resources are investigated to the level
> required by their position.

504.2 [RESPONSIBILITIES]{.underline}

> a\. The Information Management Office is responsible for
> implementation of the NASA Automated Information Security (AIS)
> Program at KSC, to include identification of the criteria for
> determining which positions require investigation under the AIS
> Program and the level of investigation required.
>
> b\. The Protective Services Branch is responsible for conducting
> personnel security investigations in support of the AIS Program.
>
> NOTE: As of the date of publication of this Handbook, Information
> Management Office implementation guidelines for the AIS Personnel
> Screening Program had not been released. Upon publication of
> implementing instructions by Information Management Office, Protective
> Services will revise this chapter to reflect our supporting
> procedures.

**APPENDIX A**

**DEFINITIONS & ACRONYMS**

**[45th SPACE WING]{.underline}.** An area encompassing Cape Canaveral
Air Force Station, Patrick Air Force Base, mainland sites, downrange
stations, and other locations under the jurisdiction of the Commander,
Eastern Range, 45th Space Wing. Formerly referred to as the Eastern
Space and Missile Command (ESMC).

**[AGENCY]{.underline}.** Any department or agency of the Federal
Government.

**[AUTHORIZED BADGING OFFICIAL]{.underline}.** A non-NASA employee
officially designated by proper authority (e.g., Contract Technical
Manager or Contracting Officer) to request badges or passes for persons
on official business.

**[AUTHORIZED REQUESTER]{.underline}.** Individuals designated by their
respective NASA or contractor organization to process requests for Area
Permits and Temporary Area Authorizations (TAA\'s).

**[BLACK]{.underline}.** (NACSIM 5203) A term applied to wire lines,
components, equipment, and systems which do not handle national security
signals, and to areas in which no national security signals occur.
(Black signals: (NACSEM 5100) Any signal (e.g., control signal or
enciphered signal) which will not divulge classified information if
recovered and analyzed by an unauthorized interception.)

**[CLASSIFIED VISIT]{.underline}.** A visit involving the authorized
disclosure of classified information, either by the visitor or by the
person visited.

**[CLOSED AREA]{.underline}.** An area wherein security measures are
applied primarily for the purpose of safeguarding classified information
and material, entry to the area being equivalent, for all practical
purposes, to access to such classified information and material.

**[CMCC]{.underline}.** Classified Material Control Center.

**[CMCS]{.underline}.** Classified Material Control System.

**[COMMUNICATIONS SECURITY]{.underline}.** The materials and procedures
used to protect sensitive information and data during transmission.

**[COMPROMISE]{.underline}.** Any occurrence which results or can be
presumed to result in unauthorized persons gaining access to classified
or other sensitive information.

**[COMPROMISING EMANATIONS]{.underline}.** Unintentional
intelligence-bearing signals which, if intercepted and analyzed,
disclose the classified information transmitted, received, handled, or
otherwise processed by any information-processing equipment.

**[COMSEC.]{.underline}** Communications Security.

**[CONTACT]{.underline}.** A NASA employee, duty-stationed at KSC,
authorized to approve or request approval for a visit to KSC and CCAFS
and/or approve or request approval for appropriate badging for the
visitor.

**[CONTRABAND DRUGS]{.underline}.** Drugs and other controlled
substances which are regulated, by Federal, State, or local law,
according to their potential for abuse.

**[CONTROLLED AREA]{.underline}.** Any area that is maintained to
protect classified information, or to protect the integrity of systems
and equipment used in the support of secure operations. Controlled areas
are usually within a Physical Control Zone (PCZ).

**[DESIGNATED BADGING OFFICIAL]{.underline}.** NASA/KSC Government
agency or contractor personnel specifically designated by proper
authority (e.g., NASA/KSC branch chief or Contracting Officer) to
request badges and machine passes for personnel under their cognizance.

**[DISQUALIFYING INFORMATION]{.underline}.** Data which reasonably
indicates that a person may not be reliable and that authorizing or
continuing his or her unescorted access may not be clearly consistent
with the preservation of national resources, Government property and
facilities, and a safe working environment.

**[DoD]{.underline}.** Department of Defense.

**[ELV]{.underline}.** Expendable launch vehicle.

**[ESCORT]{.underline}.** An authorized, properly badged individual
designated to maintain control and surveillance of visitors in the area
where an escort is to be provided.

**[FIRE LANE]{.underline}.** A posted area designated as such where
parking would unduly interfere with the free movement of firefighting
equipment.

**[FLIGHT HARDWARE AREA]{.underline}.** A security-protected area,
designated as containing items of flight hardware which are vital to
mission assignments. Access controls may be by physical means (i.e.,
fences, lock and key, or by electronic devices). Flight hardware areas
may contain an Orbiter, External Tank (ET), or Solid Rocket Booster
(SRB).

**[FOREIGN NATIONAL]{.underline}.** Any person who is not a citizen,
national, permanent resident alien, or immigrant alien of the United
States.

**[FOREIGN REPRESENTATIVE]{.underline}.** A citizen or national of the
United States or an immigrant alien (permanent resident alien) who is
acting as a representative, official, or employee of a foreign
government, firm, corporation, or person.

**[FLORIDA UNIFORM TRAFFIC CITATION (FUTC)]{.underline}**. A citation
issued by J-BOSC Security and all other law enforcement agencies in the
State of Florida to individuals committing violations of Florida
Traffic/Regulations. \[Issuance of this citation will result in points
being assessed against a person\'s driving privileges on KSC and may
result in points being assessed against the state license of the
offender, as directed by Florida State Statutes.\]

**[GOVERNMENT MOTOR VEHICLE]{.underline}.** Any NASA-tagged government
vehicle or any government motor vehicle issued by the GSA Interagency
Motor Vehicle Pool at the Kennedy Space Center. Also,
contractor-identified vehicles (i.e., vehicles bearing a company name or
trademark, or vehicles with large supplemental markings, decals, or
official vehicle placard identifying them as vehicles leased by a
company or corporation for official company business) may utilize
parking spaces for Government vehicles. Leased vehicles without an
identifying marking or decal do not qualify as contractor-identified
vehicles.

**[GROUND/GROUNDING]{.underline}.** Generally, a deliberate or
accidental conducting connection between an electrical circuit or
equipment and the earth, or some conducting body which serves as the
common zero potential reference for electrical or electronic circuits.

**[GSA]{.underline}.** General Services Administration.

**[ID BADGE]{.underline}.** NASA identification (ID), KSC
identification, machine passes, and CCAFS badges that can be used to
gain access to KSC.

**[INDICATORS]{.underline}.** Actions or information, classified or
unclassified, obtainable by an adversary that would result in adversary
appreciations, plans, and actions harmful to achieving friendly
intentions and preserving friendly military capabilities.

**[INTELLIGENCE INDICATORS]{.underline}.** See INDICATORS.

**[KKAS]{.underline}.** Kennedy Key Accountability System.

**[KSC]{.underline}.** Kennedy Space Center. A Federally controlled area
located on Merritt Island and under the jurisdiction of the Director,
KSC. This area is bounded as follows: by the federal property line on
the south; the Indian River on the west; the federal property line on
the north; the Atlantic Ocean on the east to the CCAFS north boundary;
and the Indian River and Banana River causeways beginning at the
federally controlled approaches on the west bank of the Indian River,
extending to the east bank of the Banana River.

**[KSC EMPLOYEE]{.underline}.** Any person employed by a contractor that
is party to a contract with NASA/KSC, whose primary work location is at
KSC.

**[KSC-FURNISHED GOVERNMENT MOTOR VEHICLES]{.underline}.** Any
Government motor vehicle issued by the GSA Interagency Motor Vehicle
Pool at the Kennedy Space Center.

**[KSC TRAFFIC CITATION (KSC FORM 20-109)]{.underline}.** A citation
issued by J-BOSC Security, to individuals who commit a violation of
Florida or NASA traffic regulations; i.e., speeding, defective
equipment, improper backing, failure to obey the directions of a
Security Officer. Issuance of this citation will result in points being
assessed against a person\'s driving privilege on KSC.

**[KSCAP]{.underline}.** Kennedy Space Center Area Permit. A card issued
to a person after screening and training requirements have been met and
operational need has been verified. It allows access to certain security
areas.

**[LIMITED AREA]{.underline}.** An area wherein security measures are
applied for the safeguarding of classified information or material, or
unclassified property warranting special protection and in which
uncontrolled movement of visitors or other unauthorized persons would
permit access to such information, material, or property, but within
which such access may be prevented by appropriate visitor escort or
other internal restrictions and controls.

**[LIMITED-CLEARANCE AREA]{.underline}.** An area primarily established
to protect classified information and equipment. Unescorted access to a
limited clearance area requires that the individual possess a security
clearance equal to the level of classified information involved, have a
need-to-know, and must be authorized unescorted access under the KSC
Unescorted Access and Personnel Reliability Program. This term is not an
official area designation but rather a description of a LIMITED AREA.

**[LIMITED-NAC AREA]{.underline}.** An area primarily established for
the purpose of resource protection. Access to a limited-NAC area
requires that the individual be authorized unescorted access under the
KSC Unescorted Access and Personnel Reliability Program. This term is
not an official area designation but rather a further description of a
LIMITED AREA.

**[MOTOR VEHICLE]{.underline}.** A vehicle primarily used to transport
persons or property and propelled by power other than muscular power;
such as, an automobile, motorcycle, truck, truck-tractor, semi-trailer
combination, recreational travel-trailers, truck campers, and motor
homes.

**[MOTORIZED VEHICLE]{.underline}.** A vehicle propelled by power other
than muscular power and used primarily to load/unload cargo, move other
pieces of equipment or material, earth moving equipment, road rollers,
vehicles that run only upon tracks, and agricultural-type
tractor-mowers.

**[MOTORIZED VEHICLE INCIDENT]{.underline}.** When a motorized vehicle
is involved in an incident which results in damage to another vehicle or
object, or injury to a person or animal.

**[NASA EMPLOYEE]{.underline}.** Any civil service employee or military
detailee assigned directly to the National Aeronautics and Space
Administration.

**[NEED-TO-KNOW]{.underline}.** The requirement for access to classified
material in the performance of official duties.

**[NISPOM]{.underline}.** The National Industrial Security Program
Operating Manual. Document (DoD 5220.22-M, appendix XIV) which contains
the equivalent Foreign and International Pact Organization Security
Classifications.

**[NONACCOUNTABLE CLASSIFIED MATERIALS]{.underline}.** All CONFIDENTIAL
material except CONFIDENTIAL Restricted Data and formerly Restricted
Data.

**[NSA]{.underline}.** National Security Agency. It has overall
responsibility within the U.S. Government for communications security.

**[OADR]{.underline}.** Originating Agency Determination Required.

**[OPERATIONAL AREA]{.underline}.** A physically defined area designated
as a security area in which mission-related tasks or tests are being
performed. Access will be controlled for security and safety reasons,
primarily for safeguarding and protection of life, property, and
accomplishment of mission requirements. These controls may be by
physical means (i.e., fences, lock and key, or electronic devices).
Examples of operational areas are: Launch Complex 39 Pads A and B,
Orbiter Processing Facility (OPF), Vehicle Assembly Building (VAB),
Complex 17, etc.

**[OPERATIONS SECURITY]{.underline}.** The process of denying
adversaries information about friendly capabilities and intentions by
identifying, controlling, and protecting indicators associated with
planning and conducting government operations and other activities.

**[OPERATOR\'S REPORT OF MOTOR VEHICLE ACCIDENT (STANDARD FORM
91)]{.underline}.**

A form used to record the details and facts of an accident or damage
involving a Government vehicle (GSA or USAF). This form is required in
addition to the Highway Safety & Motor Vehicle (HSMV) Form 90006 or
90003.

**[OPR]{.underline}.** Office/Organization of Primary Responsibility.

**[OPSEC]{.underline}.** Operations Security.

**[PHYSICAL COMPROMISE]{.underline}**. The compromise of information
through loss, theft, capture, or recovery by salvage, defection of
individuals, unauthorized viewing, photography, or by any other physical
means.

**[PHYSICAL CONTROL ZONE]{.underline}.** A defined area with sufficient
technical and physical control to ensure the safeguarding of classified
information and material contained therein.

**[PERMANENT PICTURE BADGE]{.underline}.** A NASA or KSC identification
badge issued with no expiration date.

**[PHYSICAL SECURITY WEAKNESS]{.underline}.** A defect in the physical
security of an area which would permit either access to the area by
uncleared or unauthorized personnel or the installation of a technical
surveillance device.

**[PIN]{.underline}.** Personal identification number. A unique
four-digit identification code which is used in conjunction with a
specific PACAS card.

**[PLAIN TEXT]{.underline}.** Intelligible text or signals which have
meaning and which can be read or acted upon without the application of
decryption.

**[PORTAL]{.underline}.** A point where access to, or egress from, a
controlled or security area, is made. A portal may contain one or more
electronic devices for controlling access/egress, and may include the
capability to track or log (or both) the number of personnel
transienting, staying within, and departing the controlled or security
area. A portal may be a door, double door, gate, turnstile or physical
barrier capable of controlling access to an area.

**[PROTECTED DISTRIBUTION SYSTEMS (PDS)]{.underline}.** A
telecommunications system to which electromagnetic and physical
safeguards have been applied to permit the secure transmission of
unencrypted classified information.

**[RED]{.underline}.** A term applied to wire lines, components,
equipment, and systems which handle classified signals, and to areas in
which classified signals occur.

**[RED/BLACK CONCEPT]{.underline}.** The concept that wire lines,
electrical and electronic concepts, components, equipment, and systems
which handle classified plain text information in electrical signal form
(RED) be separated from those which handle encrypted or unclassified
information (BLACK).

**[RESTRICTED AREA]{.underline}.** An area wherein security measures are
applied for the safeguarding or the administrative control of property
or to protect operations and functions which are vital or essential to
the accomplishment of the mission assigned to a NASA installation or
component installation.

**[SCG]{.underline}.** Security Classification Guide. A document
identifying specific information requiring protection in the interest of
national security.

**[SECURITY (SECURE) AREA]{.underline}.** A physically defined area
established for the protection or security of facilities, property, or
classified information and material in the possession or custody of NASA
or a NASA contractor located at a NASA installation or component
installation, entry to which is subject to security measures,
procedures, or controls. The three types of security areas are
RESTRICTED AREA, LIMITED AREA, and CLOSED AREA.

**[SECURITY AWARENESS]{.underline}.** Cognizance of the need for and
benefits of security measures. Its aim is to motivate people to remember
and apply good security practices.

**[SECURITY TRAINING]{.underline}.** Instruction in the practices and
procedures of security. It includes identification of the materials or
information that require protection, explanation of the location and use
of security equipment, instruction in routine and exceptional security
procedures, and other security requirements.

**[SECURITY VULNERABILITY]{.underline}.** A deficiency in the physical
or technical security safeguards of an area that could permit access to
the area by uncleared or unauthorized personnel, facilitate the
installation of a technical surveillance device, or facilitate the
exploitation of existing equipment characteristics to conduct a covert
surveillance.

**[SENIOR MANAGEMENT]{.underline}.** Designated members of the Center
Director's immediate staff, persons in Senior Executive Service (SES)
positions and heads of organizations who report directly to the Center
Director. Heads of major contractor organizations and contractor
personnel in positions equivalent to the SES as justified by the senior
contract official.

**[SENSITIVE INFORMATION]{.underline}.** Information that requires
protection. It includes, but is not necessarily limited to, information
that is classified, proprietary, or private.

**[SFOC]{.underline}**. Shuttle Flight Operations Contractor.

**[SHIELDED ENCLOSURE]{.underline}.** An area specifically designed to
attenuate electromagnetic radiation or acoustic emanations.

**[SPECIAL BADGE]{.underline}.** A badge used primarily for internal
access control during prelaunch, visits by dignitaries, classified
conferences, and other events as specifically authorized by the
Installation Security Officer or the CCAFS Security Office.

**[STS]{.underline}.** Space Transportation System.

**[STS SCG]{.underline}.** Space Transportation System Security
Classification Guide.

**[SURREPTITIOUS LISTENING DEVICE]{.underline}.** Apparatus or equipment
used to obtain information clandestinely. Examples include hidden
microphones, modified telephones and telephone lines, and radio
frequency transmitters. A surreptitious listening device is a kind of
technical surveillance device.

**[SURVEY]{.underline}.** An evaluation of performance through a
comprehensive review of systems, procedures, and actions. It may include
one or more audits.

**[TECHNICAL SECURITY HAZARD]{.underline}.** A condition which could
permit the technical penetration of an area through equipment which, by
reason of its normal design, installation, operation, maintenance, or
damaged condition, allows the unintentional transmission of classified
information.

**[TECHNICAL SURVEILLANCE]{.underline}.** The use of technical
surveillance devices.

**[TECHNICAL SURVEILLANCE DEVICE]{.underline}.** A device covertly
installed to visually or audibly monitor activities within an area.

**[TECHNICAL SURVEILLANCE PENETRATION]{.underline}.** A deliberate,
unauthorized, covert employment of a device, or the covert employment of
a technique, which allows the monitoring of activities within an area
for the purpose of gaining information.

**[TEMPEST]{.underline}.** A short name referring to investigations and
studies of compromising emanations. It is sometimes used synonymously
for the term compromising emanation; e.g., TEMPEST tests, TEMPEST
inspections.

**[TEMPEST-APPROVED EQUIPMENT/SYSTEMS]{.underline}.** Equipment or
systems which have been certified with the requirements of the effective
edition of NACSIM 5100.

**[TEMPORARY SECURITY AREA]{.underline}.** A security area established
for a period not to exceed 30 days. It may be established pending its
approval as a permanent security area.

**[TENANT ORGANIZATION]{.underline}.** The NASA and/or contractor
organization responsible for ensuring that security procedures are
followed within a specific room, area, or facility. The tenant
organization is the KSC Protective Services Branch point of contact for
matters relating to access control, Electronic Security System (ESS),
and other administrative security matters.

**[TRAFFIC CONTROL DEVICES]{.underline}.** Any device utilized in
regulating the flow of traffic such as signals, signs, and markings
which are placed on, or adjacent to, streets and highways.

**[TRAFFIC CRASH]{.underline}.** When a motor vehicle operated upon the
roadway comes into contact with another motor vehicle, object, person,
or animal, causing damage to the motor vehicle or object, or injury to
the person or animal.

**[TRAFFIC SUPERVISION]{.underline}.** Direction of an orderly flow of
motor vehicles on roadways, enforcement of laws relating to motor
vehicle operation, and motor vehicle accident investigation.

**[TSCM]{.underline}.** Technical surveillance countermeasures.

**[TSCM MONITOR]{.underline}.** A limited TSCM survey that may be
provided at sensitive briefings, conferences, or symposia. It is
primarily an examination of parts of the electromagnetic spectrum and
includes a limited physical examination of the facility. A TSCM monitor
is not a substitute for proper physical security measures designed to
protect sensitive information.

**[TSCM SURVEY]{.underline}.** A thorough physical, electronic, and
visual examination by TSCM-qualified personnel in and about an area to
detect technical surveillance devices, technical security hazards, and
physical security weaknesses.

**[UA.]{.underline}** Unescorted Access. The privilege of being in a
KSCAP-controlled security area without being under the continuous
observation and responsibility of a person who is authorized unescorted
access. Persons allowed unescorted access are certified under the Space
Transportation System Personnel Reliability Program.

**[UAPRP]{.underline}.** Unescorted Access and Personnel Reliability
Program.

**[UAPRP BOARD]{.underline}.** The body which may deny or conditionally
approve unescorted access to KSC\'s KSCAP-controlled areas.

**[UNCLASSIFIED VISIT]{.underline}.** A visit which does not involve the
disclosure of classified information and, therefore, does not require a
security clearance.

**[VANPOOL]{.underline}.** A 14-15 passenger van with a minimum of 8
passengers and 1 driver.

**[VISITOR]{.underline}.** Defined as:

> a\. Any person who is admitted to the Kennedy Space Center other than
> a NASA, USAF, or contractor employee stationed at KSC/CCAFS.
>
> b\. Any KSC employee visiting any Center, agency, or entity.

**[VISITOR RECORDS CENTER]{.underline}.** KSC office responsible for
receiving and maintaining clearance and badge information on individuals
affiliated with KSC, as well as the fabrication, issue, and control of
badges and permits.

[NOTE]{.underline}: All definitions contained in Florida Statutes and
NASA regulations will apply to the roadways and the operation of
vehicles upon the roadways of KSC.

**APPENDIX B**

**MISCELLANEOUS CONTROLLED ACTIVITIES**

The following miscellaneous activities are controlled, as stated:

a\. [Alcohol]{.underline}. The possession or consumption of alcohol in
areas under KSC cognizance, is restricted, except those areas approved
by Senior Management. Employees and their guests may not consume
alcoholic beverages (except at official functions sponsored by NASA)
within the controlled area of KSC. Employees and their guests may
possess and consume alcohol at KARS Park I and II, and also at KSC
Visitor's Center when they are not on duty.

b\. [Contraband Drugs]{.underline}. All illegal drugs are prohibited
from introduction onto the KSC.

c\. [Illegal Activity]{.underline}. All activities defined as illegal
through local ordinance. State statute, or by Federal legislation are
prohibited on KSC.

d\. [Personal Trailers, Recreational Vehicles, and Trailered
Boats]{.underline}. Personal trailers, recreational vehicles, and
trailered boats are prohibited from access onto KSC. Exceptions to this
may be made on a case-by-case basis by the Installation Security
Officer. Badged employees who use their badges to transverse the
controlled area while towing a personal trailer, towing or driving a
recreational vehicle, or towing a trailered boat are misusing their
badge.

**APPENDIX C**

**NASA AND J-BOSC POINTS OF CONTACT**

Deleted due to organizational changes.

**APPENDIX D**

### KSC BARRICADE LOCATIONS

BARRICADE

BARRICADE CLASSIFICATION

[NUMBER CODE LOCATION]{.underline}

1 C NORTH KENNEDY PARKWAY, EAST OF OLD FISH AND WILDLIFE (FWS)
BIOLOGICAL LAB ON DIKE TRAIL.

2 B NORTH CAPE ROAD, SOUTH OF CAMERA PAD 10. Note: This barricade is
jointly owned with National Park Services (NPS). NPS maintains it to
ensure conformity of the aesthetics at Playalinda Beach.

3 N/A

4 N/A

5 B GATE #5, SOUTH SIDE OF BEACH ROAD.

6 B GATE #6, JUNCTION OF NORTH CAPE AND BEACH ROAD.

7 C END OF HAPPY CREEK ROAD, SOUTH SIDE OF BEACH ROAD.

8 C EAST OF Kennedy Parkway (KP), NORTH OF BEACH ROAD AND KP, PARALLEL
TO R/R GATE AT WILSON INTERCHANGE.

9 D PARALLEL TO BARRICADE #8, R/R GATE AT WILSON INTERCHANGE.

10 N/A

11 D WISCONSIN ROAD AT BEACH ROAD.

12 D TAYLOR GROVE OFF SOUTH SIDE OF BEACH ROAD.

13 N/A

14 N/A

15 N/A

16 D PLAYALINDA R/R GATE, PARALLEL TO BARRICADE #6, DIRECTLY WEST OF
EAGLE 4 OBSERVATION TOWER.

17 N/A

BARRICADE

BARRICADE CLASSIFICATION

[NUMBER CODE LOCATION]{.underline}

18 N/A

19 D ENTRANCE TO SOUTH PAPI LIGHT AREA, WEST SIDE OF KP, ACROSS FROM
LC-39 COMPLEX, SOUTH SIDE OF CULVERT AT BANANA CREEK.

20 D FAR END OF WEST RANSOM ROAD, AT PROPERTY LINE.

21 B ENTRANCE TO KARS PARK AREA, SOUTH BANANA RIVER DRIVE.

22 D NORTH GATE ACCESS TO KARS PARK, COMING FROM KSC SIDE ON NORTH
BANANA RIVER DRIVE.

23 B HALL ROAD ON SOUTHERN BOUNDARY LINE.

24 C ENTRANCE GATE TO AIR FORCE RADAR STATION, RADAR SITE 19.14.

25 C GATE ON BANANA RIVER DRIVE, DIRECTLY SOUTHEAST OF AIR FORCE RADAR
STATION, SITE 19.14.

26 D R/R TRACK NORTHWEST OF COMPLEX #41.

27 D .6 MILES OFF BEACH ROAD, ON OLD PEACOCK POCKET ROAD.

28 N/A

29 D NORTH OF NASA CAUSEWAY BY WILDLIFE SIGN ON DIKE ROAD, ON EAST BANK
OF INDIAN RIVER.

30 D SOUTH SIDE OF NASA CAUSEWAY, DIRECTLY ACROSS FROM BARRICADE #29, ON
EAST BANK OF INDIAN RIVER.

31 A GATE 6T, ON BEACH ROAD.

32 B GATE ACROSS STATIC TEST ROAD, JUST NORTH OF FIRE TRAINING AREA,
(OLD R/B-AB-13).

BARRICADE

BARRICADE CLASSIFICATION

[NUMBER CODE LOCATION]{.underline}

33 C ENTRANCE TO FIRE TRAINING AREA ON STATIC TEST ROAD.

34 D ACCESS ROAD TO KARS PARK SHOOTING RANGE AREA, OFF OF NORTH BANANA
RIVER DRIVE.

35 N/A

36 N/A

37 N/A

38 D END OF PEACOCK POCKET ROAD, AT WATERLINE.

39 N/A

40 C ENTRANCE TO S-BAND, OFF NASA CAUSEWAY.

41 N/A

42 N/A

43 D NORTH SIDE OF NASA CAUSEWAY, EAST OF OLD PISTOL RANGE.

44 A GATE #4, ON KENNEDY PARKWAY, JUST SOUTH OF WILSON'S INTERCHANGE.

45 N/A

46 C RANSOM ROAD, EAST OF KP.

47 C JEROME ROAD, EAST OF KP.

48 N/A

49 D OFF PAD B ACCESS ROAD, BY WATER PLANT, WEST OF PAD A.

50 D WEST OF GATE 2, BORDER PROPERTY LINE.

51 D .3 MILE SOUTH OF WEATHER TOWER #6 ON WEST SCHWARTZ ROAD.

52 A GATE 2 / ROADBLOCK AB-34.

53 A GATE 3 / ROADBLOCK AB-35.

BARRICADE

BARRICADE CLASSIFICATION

[NUMBER CODE LOCATION]{.underline}

54 N/A

55 D SOUTH SIDE OF 10TH STREET, ADJACENT TO BLDG. M6-1408.

56 D GATE LEADING TO NORTH PAPI LIGHTS, OFF KP.

57 D ACCESS TO RAILROAD TRACKS DIRECTLY SOUTH OF GATE 6T ON BEACH ROAD.

58 N/A

59 B ENTRANCE/EXIT GATE TO PIDS-2 (N6-1009), ADJACENT TO GATE 2.

60 B ENTRANCE/EXIT GATE TO PIDS-3, (M3-2) ADJACENT TO GATE 3.

61 B GATE 2A / ROADBLOCK AB-36.

62 N/A

63 N/A

64 N/A

65 N/A

66 B ENTRANCE TO LANDFILL AREA, SOUTH OF SCHWARTZ ROAD EAST.

67 D ENTRANCE GATE TO BALL FIELD AT KARS PARK, OFF HALL ROAD,
APPROXIMATELY .6 MILES EAST OF BARRICADE #23.

68 N/A

69 N/A

70 D ENTRANCE TO NEW MARL PIT AREA. SOUTH OFF WEST SCHWARTZ ROAD (DIRT
ROAD INTERSECTING ROBERTS ROAD AND SCHWARTZ ROAD).

71 N/A

72 N/A

73 N/A

74 N/A

75 N/A

BARRICADE

BARRICADE CLASSIFICATION

[NUMBER CODE LOCATION]{.underline}

76 N/A

77 N/A

78 N/A

79 N/A

80 N/A

81 N/A

82 N/A

83 N/A

84 D NORTH LINE OF GOMEZ GRANT, MICROWAVE TOWER, EAST OF KENNEDY
PARKWAY.

85 N/A

86 D EAST OF KP, SOUTH OF 5TH STREET, NEAR GATE 2A.

87 N/A

88 N/A

89 N/A

90 N/A

91 N/A

92 N/A

93 N/A

94 D ENTRANCE TO JAY JAY RAIL YARD (OWNED BY FLORIDA EAST COAST
RAILROAD). AT END OF PARRISH ROAD, OFF U.S. 1, NORTH TITUSVILLE.

95 N/A

96 D WEST OF KARS PARK II, OFF KP & NASA CSWY.

97 D WEST SIDE OF A AVENUE AT THE INTERSECTION OF 3RD STREET AND A
AVENUE.

98 D NORTHWEST CORNER OF CD&SC, ON TRAIL.

99 D EAST OF KP, AT 5TH STREET, NORTH OF BARRICADE #86.

100 N/A

101 D SOUTH OF 5TH STREET, JUST EAST OF GATE 2A.

BARRICADE

BARRICADE CLASSIFICATION

[NUMBER CODE LOCATION]{.underline}

102 N/A

103 N/A

104 N/A

105 N/A

106 N/A

107 N/A

108 N/A

109 N/A

110 D EAST OF GUARD OBSERVATION TOWER, LOCATED ON BEACH. Note: This
barricade is jointly owned with Fish & Wildlife (F&WL). It is necessary
for their personnel to get through, with their ATV's for turtle counts,
etc. They are responsible for maintaining it.

111 D NORTHWEST CORNER OF GSA SEIZED PROPERTY.

112 A GATE 2 B / ROADBLOCK AB-37.

113 A GATE 2C / ROADBLOCK AB-21.

113E D ACCESS GATE EAST OF KP AND GATE 2C. Note: This gate has been
provided a barricade number for identification and/or tracking purposes
only and is not an official "barricade" that must meet KSC standards and
specifications.

113W D ACCESS GATE WEST OF KP AND GATE 2C. Note: This gate has been
provided a barricade number for identification and/or tracking purposes
only and is not an official "barricade" that must meet KSC standards and
specifications.

114 D ENTRANCE TO SECURITY FIRING RANGE, OFF WEST SCHWARTZ ROAD, ON
NORTH SIDE.

114A D EAST OF ENTRANCE TO SECURITY FIRING RANGE/BARR 114.

> BARRICADE

BARRICADE CLASSIFICATION

[NUMBER CODE LOCATION]{.underline}

127 D DIRECTLY IN CENTER OF KP; PART OF TOW WAY EAST OF SHUTTLE LANDING
FACILITY (SLF), AND WEST OF Orbiter Processing Facility (OPF) (NO LOCK).

134 D SOUTHEAST OF CAMERA PAD 7, OFF NORTH CAPE ROAD.

143 C SAFETY BARRICADE -- Hypergolic Maintenance Facility (HMF) AREA -
ACROSS 5TH STREET, AT "E" AVENUE (NO LOCK).

144 C SAFETY BARRICADE - HMF AREA - ACROSS 6TH STREET, AT "E" AVENUE (NO
LOCK).

145 D SAFETY BARRICADE - HMF AREA - ENTRANCE TO PARKING LOT ACROSS FROM
M7-1061 ON 6TH STREET (NO LOCK).

146 C SAFETY BARRICADE - HMF AREA - ACROSS "G" AVENUE, JUST NORTH OF 6TH
STREET (NO LOCK).

147 C SAFETY BARRICADE - HMF AREA - ACROSS "G" AVENUE, JUST SOUTH OF 6TH
STREET (NO LOCK).

148 C SAFETY BARRICADE - HMF AREA - ACROSS "G" AVENUE, BETWEEN 8TH AND
9TH STREETS.

149 C SAFETY BARRICADE - HMF AREA - ACROSS "F" AVENUE, JUST NORTH OF 9TH
STREET.

150 D SECURITY BARRICADE - SLF AREA - AT ENTRANCE TO WEATHER TOWER
TRAIL, BETWEEN ASTRONAUT AND SHARKEY ROADS. USED DURING LAUNCH/LANDING
OPERATIONS WHEN SECURITY SWEEPS OF THE SLF ARE CONDUCTED.

151 C SECURITY BARRICADE - (OLD R/B AB-14) ACROSS DIRT PORTION OF
SCHWARTZ ROAD, EAST OF ENTRANCE TO SANITARY LAND FILL. USED DURING
LAUNCH OPERATIONS FOR FINAL ILL SECURITY SWEEPS.

BARRICADE

BARRICADE CLASSIFICATION

[NUMBER CODE LOCATION]{.underline}

152 C SECURITY BARRICADE - (OLD R/B AB-18) ACROSS HAPPY CREEK ROAD, AT
KP. USED DURING FINAL ILL SECURITY SWEEPS FOR LAUNCH OPERATIONS.

153 C SECURITY BARRICADE - (OLD R/B AB-29) ACROSS SR 406, AT JUNCTION
WITH BEACH ROAD (SR 402). USED FOR FINAL Impact Limit Line (ILL)
SECURITY SWEEPS DURING LAUNCH OPERATIONS.

154 A SECURITY BARRICADE - (OLD R/B AB-28) ACROSS KENNEDY PARKWAY, JUST
NORTH OF BEACH ROAD (WILSON INTERCHANGE). USED FOR FINAL ILL SECURITY
SWEEP DURING LAUNCH OPERATIONS.

155 N/A

156 N/A

157 D ENTRANCE GATE INTO KARS PARK WEST BASEBALL FIELD, WEST OF
BARRICADE 67. Note: This gate has been assigned a barricade number for
identification and tracking purposes only and is not an official
"barricade" that must meet KSC standards and specifications.

158 N/A

159 N/A

160 N/A

161 N/A

162 N/A

163 N/A

164 N/A

165 N/A

166 N/A

167 N/A

168 C EAST OF VAB, GOING INTO THE ORDINANCE STORAGE AREA (NO LOCK).

BARRICADE

BARRICADE CLASSIFICATION

[NUMBER CODE LOCATION]{.underline}

169 C ENTRANCE TO OLD HOBBY SHOP, JUST PAST CURVE ON WEST SCHWARTZ ROAD
(NO LOCK).

170 D SOUTHEAST SIDE OF BANANA RIVER BRIDGE.

171 D SOUTHWEST OF 10TH STREET AND E-AVENUE ON THE SOUTHWEST CORNER OF
HOLDING POND/BORROW PIT.

A-1 D DIRECTLY EAST OF ROADBLOCK B5, NORTH OF CRAWLER TRACKS.

A-2 D NORTH OF PAD A, ON DIKE ROAD .1 MILE WEST OFF NORTH CAPE ROAD.

A-3 D SOUTHWEST OF ROADBLOCK A/B 30, .2 MILES NORTHWEST OF MOSQUITO PUMP
STATION #4 ON DIKE ROAD.

A-4 N/A

A-5 N/A

A-6 N/A

A-7 D NEXT TO PAD-A, R/R TRACKS JUST OFF NORTH CAPE ROAD.

A-8 N/A

A-9 N/A

A-10 N/A

A-11 D EAST OF PAD-A, JUST OFF BYPASS ROAD ALONG PAD-A FENCE LINE.

B-1 C 150 WEST OF PAD-B ACCESS GATE.

B-2 N/A

B-3 D WEST OF PAD-B, OLD SLIDE WIRE AREA.

B-4 N/A

B-5 D WEST OF PAD-B, ON GATE 5 ACCESS ROAD.

B-6 N/A

BARRICADE

BARRICADE CLASSIFICATION

[NUMBER CODE LOCATION]{.underline}

B-7 D NEXT TO PAD-B R/R TRACKS, OFF NORTH CAPE ROAD.

B-8 N/A

B-9 D SOUTHEAST OF PAD-B, NORTH OF PAD-B BYPASS ROAD ON DIKE TRAIL.

B-10 N/A

B-11

D B-11 D SOUTHEAST SIDE OF PAD-B, ALONG FENCE

LINE, NORTH OF PAD-B BYPASS ROAD.

NORTH OF PAD-B BYPASS