Sunday, April 3, 2011

Disclaimer from Upcoming DoD Security Clearances And Contracts Guidebook

Get it here

Here is the disclaimer from our upcoming book. Just a little flavor of what you can expect. Please forward for others who might be interested

This book is designed to give defense contractors insight into the National Industrial Security Program. Our intention is to help defense contractors understand what is required of them should they become cleared facilities working on classified contracts. Any security and compliance related issues that an organization may face should be pursued with the Cognizant Security Agency (CSA), Government Contracting Activity (GCA) or other Federal agencies and legal activities.

This book is meant to compliment the federal regulations and executive orders bringing about the National Industrial Security Program. It is also designed to help the reader draw from experience and suggests ways to improve security programs. Those who are new to the field can use this as a guide, but should consult their CSA. We have made every effort to make this book as accurate and complete as possible. It has been written by an ISP Certified author and has been reviewed and edited by some of the most experienced Facility Security Officers , defense contractors and ISP’s in the business.

Not every defense contractor is the same. Classified contracts further differentiate requirements. Each contractor may have a unique mission based on skill sets and core competencies. Each contract has unique requirements based on product and service needs. Defense contractors working on classified contracts will have further defined roles based on requirements listed in the Contract Security Classification Specification (DD Form 254) and contract clauses and language. Specifically, cleared contractors have unique security requirements based on the DD Form 254 identifying the clearance level and classified storage level. The following are two examples out of many possible scenarios:

Example 1: A defense contractor is required to have a Facility Security Clearance (FCL) of TOP SECRET while having a classified storage level of TOP SECRET. In this case they can expect to have employees with TOP SECRET security clearances supporting contracts on site with TOP SECRET work and TOP SECRET information. In the course of their work they will store tens of thousands of classified items. Their security requirements are complex depending on the amount of classified items, level of classified information, amount of international contracts, and etc.

Example 2: In another example a contractor has a SECRET FCL and no authorization to store or perform classified work on site. They require the SECRET FCL for the sole purpose of providing employees with security clearances to perform work off site at a customer location. They will have no requirement for security containers or in-depth security to protect classified information on site.

The purpose of this book is not to provide exact solutions for each of thousands of possible scenarios. There are too many variables to be contained in any one book. It is written to inform and provide resources that the defense contractor can use to either seek additional expert help from the CSA, GCA, Prime Contractor or competent consultant. This book is written to reflect guidance from the National Industrial Security Program Operating Manual (NISPOM), but is not written to be used instead of the NISPOM. Additionally, there is guidance in the NISPOM not covered in this book. This book is written to familiarize and inform defense contractors with NISPOM requirements. The NISPOM is the manual cleared contractors should use to build their security programs to protect classified information. This book covers general areas most cleared contractors may encounter. It is meant to help the reader determine which parts of NISPOM apply, direct the reader to available resources and suggest general ways of implementing the NISPOM. The reader should always consult NISPOM, GCA, Prime Contractor and the CSO concerning policy and contract requirements.

No comments: