HQDA G-2 DD 254 Handbook
HQDA G-2 DD 254 Handbook
DD FORM 254
Preparation Guide
FY-10
FOREWORD
The purpose of this guide is to provide guidance in the preparation of a DD Form 254,
Contract Security Classification Specification. This guide contains step-by-step
procedures for completing the DD Form 254. The instructions in this guide correspond
to the numbered items on the form.
2
TABLE OF CONTENTS
Page
DD Form 254 Preparation
Chapter 1. Introduction...........................................................................................4
Chapter 4. Instructions............................................................................................9
Chapter 5. Acronyms....................................................................................…. 35
Chapter 6. Definitions..........................................................................................37
3
Chapter 1
INTRODUCTION:
The Federal Acquisition Regulation (FAR) requires that a DD Form 254, Contract Security
Classification Specification, be integrated in each classified contract. The DD Form 254
provides the contractor (or a subcontractor) security requirements and the classification
guidance that is necessary to execute a classified contract. This handbook has been
prepared from the Defense Security Service (DSS) guide, Federal Acquisition
Regulations (FAR), Defense Federal Acquisition Regulations Supplement (DFARS), Army
Federal Acquisition Regulations Supplement (AFARS), and National Industrial Security
Program Operating Manual (NISPOM).
The Security Agreement (DD Form 441), executed between the government and all
cleared facilities under the NISP, obligates the Government to provide the contractor
appropriate classification guidance for the protection of the classified information,
furnished to or generated by, the contractor in the performance of a classified contract.
The Government fulfills this obligation by incorporating a “Security Requirements
Clause” (“clause”) and a DD Form 254 in each classified contract. The “clause”
identifies the contract as a “classified contract” and the DD Form 254 provides
classification guidance and the specific security requirements.
The key personnel in the preparation of the DD Form 254 are the program and
Industrial Security Specialist (ISS), technical/subject matter expert personnel, and
contracting personnel. The program and ISS recognizes the security requirements that
the contractor will need to follow. The technical/subject matter expert personnel
understand what information or equipment in the program requires protection, and the
technical aspects of the requirements, the KO must ensure the contractor complies with
the DD Form 254 and any special clauses into the contract.
The DD Form 254 is required to be reviewed every two years. The program and ISS
should conduct this review in coordination with the program manager of the requiring
4
activity and KO to ensure that existing security requirements are consistent with the
contract requirements.
If the review is performed and no changes are required, the program and ISS will
provide the KO with a copy of the review. The KO will then send to the contractor, in
writing, notification that the DD Form 254 remains valid until the next review or a change
occurs in the program.
If the review is performed and changes are required the program and ISS must provide
the KO with a revised copy. The KO will then prepare a bi-lateral modification to the
contract incorporating the new DD Form 254.
The Defense Security Service (DSS) is designated by DoD Directive 5220.22, National
Industrial Security Program (NISP), as the Cognizant Security Office (CSO) to
administer industrial security on behalf of the Cognizant Security Agency (CSA). The
CSAs are: the Department of Defense (DoD), Department of Energy (DOE), Central
Intelligence Agency (CIA), and the Nuclear Regulatory Commission (NRC). The
designation of DSS as the CSO for the Department of Defense does not relieve the
Government Contracting Activity (GCA) of the responsibility to protect and safeguard
classified information disclosed to or generated by contractors under the NISP or from
visiting the cleared contractor to review the security aspects/requirements of the
contract.
Revisions to the DD Form 254 will be completed whenever the security guidance or
pertinent information changes, when a change in mission occurs impacting the contract,
when a contract is modified or an option year is utilized, to ensure security requirements
remain current and relevant throughout the contract lifecycle. This includes contractor
address changes if they are performing classified work at their facility.
5
Chapter 2
POINTS OF CONTACT:
* HQDA, G-2
Industrial Security
Lisa Gearhart
703-601-1565
Or
HQDA, G-2
Industrial Security
Pamela Y. Spilman
703-601-1567
Website: [Link]
6
* U.S. Army Intelligence and Security Command (INSCOM)/Contractor Support
Element (For all Army SCI contracts)
7
Chapter 3
Pre-Award Considerations
If any of the prospective contractors do not have the appropriate facility clearance, contact
DSS and furnish, in writing, the information needed to sponsor the clearance. See the DSS
website for additional sponsorship guidance:
[Link]
8
9
Chapter 4
INSTRUCTIONS:
1a. Facility Clearance Required: Insert the highest level of facility clearance required for
the contractor to perform on the contract. Only one of three classification levels should
be listed in this field: Confidential, Secret or Top Secret. The contractor must have a
valid Facility Clearance at least as high as the classification indicated in this item. It is
critical that the correct security level is established. Setting the security level too high
may create undue costs and delay contract award.
(1) Do not cite special categories of classified such as Restricted Data, COMSEC,
SCI, etc.
(2) Contractors must meet the facility clearance and safeguarding requirements of
the DD Form 254. To verify the contractor’s facility clearance and safeguarding
capability, contact the DSS Central Verification Activity at 1-888-282-7682 or log
on to the DSS web site ([Link]) find the application tab in the upper right-
hand corner, click on ISFD, then follow the instructions to either login or request
access.
1b. Level of Safeguarding Required: Insert the highest level of safeguarding capability
required for the contractor to perform on the contract. Safeguarding refers to the ability
to store and/or generate classified materials at the contractor facility.
(1) If the contractor is working in the contractor facility the classification level may not
be higher than Item 1a.
(2) If the contractor will NOT possess or store classified information at the contractor’s
facility, enter “Not Applicable” or “None.” (If this is the case, Item 11a. must be
marked “YES” and 11b and 11d must be marked “NO”). Block 8 “Actual
Performance” will indicate the location where the classified work will be
accomplished. If classified work will occur at multiple locations mark “multiple
locations” in Block 8a and list the locations in Block 13 or an attached Appendix, as
applicable.
10
Item 2. This Specification is for:
Information for Blocks 2a and 2c are obtained from the government KO. Block 2a is
completed upon contract award. Block 2b is completed by the contractor when a
subcontract is awarded. Block 2c is completed prior to the release of the solicitation.
Insert an “X” into the appropriate box. Although information may be entered into more
than one box, only one “X” should appear in item 2 (a, b or c) depending what phase the
acquisition is in.
2a. Prime Contract Number: Used when the KO issues the contract to the Prime
Contractor. The contracting activity enters the contract number upon award.
2c. Solicitation or other number: Used for an RFP, RFQ, IFB, or other solicitation,
regardless of whether or not the bid package will contain classified information. The
contracting activity enters the solicitation number and the date by which bids are due.
b. SUBCONTRACT NUMBER
c. SOLICITATION OR OTHER NUMBER Due Date (YYYYMMDD)
Insert an “X” into the appropriate box. Although information may be entered in more
than one box, only one “X” should appear in Item 3.
3a. Original
(1) For a solicitation for a classified contract, whether or not the actual bid package
contains classified information.
11
The ‘Original date’ refers to the release date of the DD Form 254. This date will not
change over the period of the contract.
(1) Revisions to the DD Form 254 will be completed whenever the security guidance
or pertinent information changes, when a change in mission occurs impacting the
contract, when a contract is modified or an option year is utilized, to ensure
security requirements remain current and relevant throughout the contract
lifecycle. Give a sequential number to each revision and enter the date of the
revised DD Form 254.
Revised DD Form 254s should be numbered sequentially starting with “1”. A revised
DD Form 254 is generated any time there is a change to the security requirements or to
the classification guidance. A revised DD Form 254 is also required if the contractor
has safeguarding requirements and there is a change of location of their facility.
Revised DD Form 254s should be prepared and reviewed by the program and ISS and
the KO. It is recommended that all the reviewers sign as certifying officials in block 13
(see Item 13 for more details on signatures). A revised DD Form 254 MUST be
incorporated into the contract by modification.
(1) When a contract is closed out, the contractor may request additional retention
authority that may result in a Final DD Form 254. If an extension of retention
authority is approved by the KO, a final DD Form 254 may be issued to reflect
this approval. (See NISPOM Chapter 5, Section 7 for more information on
disposition and retention.)
(2) Enter the date the final DD Form 254 is issued. Complete Item 5.
A final DD Form 254 is ONLY used to authorize retention of classified materials beyond
2 years from the end of the contract as allowed by the NISPOM. If section 3c is marked
“YES”, Line 5 must also be completed.
12
NOTE: Item 5 is always marked “YES” when a final DD Form 254 is issued. Additional
retention authorization may also be granted through email or a letter to the contractor.
b. REVISED (Supersedes Revision No. Date (YYYYMMDD)
all previous specs)
Ref 4: The classified portion of work has been completed on the contract
cited in this block. The processing of classified will no longer be done
under this contract. All classified material/ information associated with this
contract is authorized to be transferred to the contract number cited in
block 2a.
Classified material received or generated under (Preceding Contract Number) is transferred to this follow-on contract
13
Item 5. Final DD Form 254
If this is a FINAL DD Form 254, mark “YES”. Enter the date of the contractor’s request
for retention and the authorized period of retention in the spaces provided. If this is not
a FINAL DD Form 254, mark “NO.” The KO will inform the program and ISS of pending
contract closure. This notification will prompt the program and ISS to provide the KO
with close out/destruction instructions. Upon contractor notification to the KO that all
classified information under the contract has been removed, destroyed, or designated
for retention in accordance with the instructions provided, the Final DD Form 254 is
prepared.
A final DD Form 254 is used only if the contractor requests the right to retain any project
related documents beyond NISPOM permitted timeframe (See Item 3c.). Permission for
extended retention of contract material/information must be requested in writing from
the KO. It is recommended that the contractor maintains a copy of the formal request
until retention authorization is received from the KO. The KO will determine if the
designated material/information should be destroyed, returned or retained by the
contractor.
5. IS THIS A FINAL DD FORM 254? YES NO. If Yes complete the following
In response to the contractor's request dated , retention of the identified classified material is authorized for the period of .
Item 6. Contractor:
Used when the KO issues guidance to a prime contractor. Enter the required
information once the clearance information has been verified and the contractor meets
the requirement of the contract:
The CAGE code is a Government issued unique identifier required for all companies who
do business with the Government. CAGE codes can be verified through the Defense
Logistics Information Service website at [Link] It is
important to note that not all facilities with CAGE codes are cleared facilities. To verify a
contractor’s facility clearance see item 1a.
14
6c. The appropriate CSO and address
The local DSS Cognizant Security Office (CSO) and Field office locations can be
found by going to [Link]
Item 7. Subcontractor:
The prime contractor will fill in this information and provide the DD Form 254 to the KO
upon determination that the subcontract meets the security requirements;
NOTE:
All DD Form 254s prepared for subcontracts involving access to SCI must be
forwarded to the Contract Monitor for approval. Upon Contract Monitor approval,
forward the DD Form 254 to Contractor Support Element (CSE) for review and
concurrence prior to award of the subcontract.
15
Item 8. Actual Performance:
List ALL locations where classified performance is required under the contract (i.e.
contractor, subcontractor, and Government facilities).
(1) If the place of performance is the same as 6a (or 7a), either enter the facility’s
name or enter “Same as Item 6a (or 7a) in block 8a. If the place of performance
is different from 6a (or 7a), include the facility name, address and CAGE code.
(2) If there is more than one place of performance, enter “multiple locations - see
Item 13 (or Attachment xxx)” in item 8a, and identify each performance location
accordingly.
8. ACTUAL PERFORMANCE
a. LOCATION b. CAGE CODE c. COGNIZANT SECURITY OFFICE (Name, Address, and Zip Code)
Enter a concise and unclassified description of the procurement action. Some examples
could be research, development, production, study or services, etc. Do not use
classified information such as project names or descriptive information. Keep this field
short but informative.
16
Item 10. This Contract Will Require Access To:
Mark all items “YES” or “NO,” as appropriate to the requirements of the contract.
(Coordinate with the appropriate program and other security offices to ensure the proper
types of access are imposed on the contractor or subcontractor.) An explanation of
each item follows.
IMPORTANT: These are access requirements for the contractor and their
employees. It does not refer to safeguarding.
(2) Prior approval from the KO is required in order for a prime contractor to grant
COMSEC access to a subcontractor. The prime contractor must notify the NSA
Central Office of Record before negotiating or awarding subcontracts.
When this item is marked “YES”, enter the following statement in Item 13:
When this item is marked “YES”, enter the following statement in Item 13:
17
10c. Critical Nuclear Weapon Design Information (CNWDI): Mark “YES” if access to
CNWDI is required under the contract.
When this item is marked “YES”, enter the following statement in Item 13:
10d. Formerly Restricted Data (FRD): Mark “YES” if access to FRD is required.
10e. Intelligence Information: The Director of National Intelligence (DNI) has jurisdiction
and control of intelligence information. If the contract requires access to intelligence
information, the KO is responsible for ensuring that the additional security requirements
outlined in the DNI Directives are incorporated in the guidance provided to the
contractor. If the contract requires Sensitive Compartmented Information (SCI) access,
a SCI Addendum is required and MUST be coordinated with the Contractor Support
Element (CSE). SCI is very expensive for the contractor to maintain. This block should
not be marked unless there is a current SCI requirement.
18
(2) Mark Item 14 “YES”
When item 10e(1) is marked “YES”, enter the following statement in Item 13:
When item 10e(2) is marked “YES”, enter the following statement in Item 13:
NOTE: DSS does not conduct security reviews for Sensitive Compartmented
Information (SCI) but is still responsible for security reviews involving Non-SCI
(collateral classified information) in the possession of a contractor or subcontractor.
10f. Special Access Information: Special Access Programs (SAP) imposes security
requirements on the contractor that exceed the NISPOM. When SAP information is
involved, the cognizant SAP security office is responsible for providing the contractor
with the additional security requirements needed to ensure adequate protection of SAP
information.
19
(3) Complete Item 15 as appropriate. (Some SAPs qualify as carve-outs, but not all
SAPs are carve-outs – see AR 380-381 for additional guidance.)
The additional requirements can be included in the contract document itself or Item 13
only if the requirements are unclassified IAW the program security classification guide.
Classified requirements shall be included in a separate SAP Addendum. (Block 13
should reference a Program Security Guide and Program Classification Guide. The
guides should not be older than 5 years. If the Program Security Guide and Program
Classification Guide are older or approaching their 5 year threshold, request updated
guides from the cognizant SAP security office.)
A SAP Addendum is required for all contracts that require SAP access. Additional
clarification should be addressed in either Item 13 or the SAP Addendum and are as follows:
20
are under the cognizance of the SAPCO, as appropriate. Additional SAP
security requirements may apply at alternate locations/facilities based on
service/component Command requirements. The KO for these
locations/facilities will provide specific guidance as required. SAP inspections
conducted at contractor facilities are under the security oversight of the
Defense Security Service (DSS) unless officially relieved of their oversight
responsibilities.
10g. NATO Information: Mark “YES” if the contract requires access to information or
documents belonging to the NATO. The prime contractor must receive approval from
the KO to grant NATO access to a subcontractor.
Note: If the contractor does not require access to NATO information, requires
access to the SIPRNET, mark 10g “No” but mark 10k “Yes” (SIPRNET access)
and add the statement below in item 13 that the contractor requires access to
the SIPRNET and a NATO awareness brief is required. The SIPRNET
contains NATO information and a NATO awareness briefing is required for
everyone who needs access to the SIPRNET. The purpose of providing a
NATO awareness briefing is to inform personnel how to protect NATO
information in the event they come across it while on the SIPRNET. See 10k
below for additional information.
21
Enter the following statement in Item 13:
10j. For Official Use Only Information: This item is linked directly to the Freedom of
Information Act (FOIA) and the appropriate exemptions are in accordance with 5
U.S.C.§ 552(b), and should only be marked if the information the contract company will
be accessing is protected under the FOIA. The NISPOM does not provide guidance
concerning FOUO; the DD Form 254 must provide guidance on protection procedures
in Item 13.
Ref 10j: For Official Use Only (FOUO) Information generated and/or
provided under this contract shall be safeguarded and marked as specified in
DoD 5200.1-R, Appendix 3 (attached).
Sample Attachment
22
b. Within a classified document, an individual page that contains both FOUO and classified
information will be marked at the top and bottom with the highest security classification of
information appearing on the page. If an individual portion contains FOUO information but no
classified information, the portion will be marked, "FOUO."
c. Any "'For Official Use Only" information released to a contractor by a DoD User Agency is required
to be marked with the following statement prior to transfer.
“This document contains information EXEMPT FROM MANDATORY DISCLOSURE UNDER THE
FOIA. Exemptions apply.”
d. Removal of the "For Official Use Only" marking can only be accomplished by the originator or other
competent authority. When the "For Official Use Only" status is terminated, all known holders will
be notified to the extent practical.
3. DISSEMINATION: Contractors may disseminate "For Official Use Only" information to their employees
and subcontractors who have a need for the information in connection with a classified contract.
Contractors must ensure employees and subcontractors are aware of the special handling instructions
detailed below.
4. STORAGE: During working hours, "For Official Use Only" information shall be placed in an out-of-sight
location if the work area is accessible to persons who do not have a need for the information. During
nonworking hours, the information shall be stored to preclude unauthorized access. Filing such material
with other unclassified records in unlocked files or desks, is adequate when internal building security is
provided during nonworking hours. When such internal security control is not exercised, locked buildings
or rooms will provide adequate after- hours protection or the material can be stored in locked receptacles
such as file cabinets, desks, or bookcases.
5. TRANSMISSION: "For Official Use Only" information may be sent via first-class mail or parcel post.
Bulky shipments may be sent by fourth-class mail. DoD components, officials of DoD components, and
authorized DoD contractors, consultants, and grantees send FOUO information to each other to conduct
official DoD business. Tell recipients the status of such information, and send the material in a way that
prevents unauthorized public disclosure. Make sure documents that transmit FOUO material call attention
to any FOUO attachments. Normally, you may send FOUO records over facsimile equipment. To prevent
unauthorized disclosure, consider attaching special cover sheets, the location of sending and receiving
machines, and whether authorized personnel are around to receive FOUO information. FOUO information
may be passed to officials in other departments and agencies of the executive and judicial branches to
fulfill a government function. Mark the records "For Official Use Only" and tell the recipient the information
is exempt from public disclosure under the FOIA and requires special handling.
6. DISPOSITION: When no longer needed, FOUO information must be shredded.
7. UNAUTHORIZED DISCLOSURE: Unauthorized disclosure of "For Official Use Only" information does
not constitute a security violation but the releasing agency should be informed of any unauthorized
disclosure. The unauthorized disclosure of FOUO information protected by the Privacy Act may result in
criminal sanctions and disciplinary action may be taken against those responsible.
10k. Other: This item may be used for any other information not included in items 10a
through 10j. Specify the type of information and include any additional remarks in item 13.
If the requirement is for SIPRnet only, the following statement must also appear
in block 13:
Ref 10k: Secret Internet Protocol Network (SIPRNET) access required. The
contractor shall not access, download or further disseminate any special
access data (i.e. intelligence, NATO, COMSEC, etc.) outside the execution of
the defined contract requirements and without the guidance and written
23
permission of the KO. In the event that any special access is required, the
KO must modify the requirements for the DD Form 254.
Note: Once the KO has modified the requirements for the DD Form 254, the
Contractor must complete the SIPRNET Access Request Form, along with
the modified DD Form 254, and forward to the KO prior to receiving access.
A NATO awareness brief will also be required for all Contractors prior to
access to the SIPRNET.
24
Enter the following statement in Item 13:
Ref 11a: Contractor performance is restricted to (enter name and address of
contractor facility or government activity). Government agency or activity will
provide security classification guidance for performance of this contract.
Submit visit request to the KO and/or Security Management Office for need-
to-know verification.
11b. Receive classified documents only: “ONLY” is the keyword. Mark “YES” when the
contractor will receive classified documents, (instead of classification guides), to
perform on the contract, but is not expected to generate classified information. The
classification markings shown on the documents received will provide the classification
guidance necessary.
(1) If the volume or configuration of the documents is such that specialized storage
requirements are necessary, contact DSS to verify storage capacity at the
contracting facility.
(2) If this item is marked “YES”, items 11a, 11c and 11d must be marked “NO”.
If material is received and or stored at the contractor site for reference purposes only
but the work is done on a government site or other cleared facility site, mark “YES”. This
item applies if there is no generation of classified materials (i.e. derivative classification).
Ref 11b: Contractor will receive classified documents for reference only;
however, if any classified information is generated in performance of this
contract, it shall be derivatively classified and marked consistent with the
source material.
11c. Receive and generate classified information: Mark “YES” when the contractor is
expected to receive and generate classified material at the contractors’ facility
(documents and/or hardware) and will require detailed security classification guidance in
order to perform on the contract. If this item is marked “YES,” detailed security
classification guidance must be provided. The guidance may be:
25
(5) If item 11c is marked “YES”, items 11a, 11b an 11e must be marked “NO”.
If the volume or configuration of the documents is such that specialized storage
requirements are necessary, contact DSS to verify storage capacity at the contracting
facility. Any applicable or additional guidance to the contractor should be included in
Item 13
11d. Fabricate, modify, or store classified hardware: Mark “YES” if the contractor is
expected to generate or utilize hardware which is classified due to its existence,
uniqueness, appearance, application, capability, or product produced. Include as much
information as possible (additional information can be added in Item 13) to describe the
nature and extent of the storage that will be required.
(2) Is hardware involved and how much? How large is the hardware and can it be
stored or will Open Storage be required?
(3) If item 11d is “YES”, items 11a, 11b and 11e must be marked “NO”.
If more than 2 cubic feet of storage is required, contact DSS to verify storage capacity at
the contracting facility.
Ref 11d: Contractor must provide adequate storage at their facility for
classified hardware to the level of (enter one: Top Secret, Secret, or
Confidential).
11e. Perform services only: Mark “YES” if the contractor is performing a service only
and is not expected to produce a deliverable item in accordance with the contract.
Enter a statement in Item 13 that explains the services provided and appropriate
security guidance. Some examples are provided below:
26
Graphic Arts Services
“Reproduction services only. Classification markings on the material to be furnished
will provide the classification guidance necessary for performance of this contract.”
Engineering Services
“Contract is for engineering services. Classification markings on the material to be
furnished will provide the classification guidance necessary for the performance of
this contract.”
Guard Services
“Contract is for guard services. Cleared personnel are required by the NISPOM to
provide supplemental protection.”
11f. Have access to U.S. classified information outside the U.S., Puerto Rico, U.S.
Possessions and Trust Territories: If “YES,” indicate in Item 13 the Army/U.S. activity,
to include the city and country where the overseas performance will occur.
(2) DSS does not provide oversight for contractors performing classified work
outside of the U.S., Puerto Rico, U.S. Possessions and Trust Territories;
therefore, any security reviews/inspections will have to be conducted by the
supporting security office and Item 15 must be completed, designating the
inspecting organization.
(3) For DoD contractors performing on overseas contracts, provide a copy of the
DD Form 254 to the appropriate DSS Office of Industrial Security, International
(See NISPOM Appendix A or contact DSS.)
(4) See NISPOM paragraph 10-204 for suggested “Security Clauses for
International Contracts” for classified contracts involving foreign contractors.
11g. Be authorized to use the services of the Defense Technical Information Center
(DTIC) or other secondary distribution center: Mark “YES” if the contractor is to be
27
authorized use of DTIC services. DD Form 1540 and DD Form 2345 must be completed
for registration with DTIC.
(1) The sponsoring KO must submit DD Form 1540 “Registration for Scientific and
Technical Information Services” to DTIC on behalf of the contractor. For
subcontractors, the prime contractor submits the DD Form 1540 with the KO
verifying the need-to-know.
(2) The contractor may also submit DD Form 2345 “Militarily Critical Technical Data
Agreement” (after registration with DTIC) to the Defense Logistics Services
Center for access to unclassified, militarily critical technical data from other DoD
sources. The KO must certify the need-to-know to DTIC.
11h. Require a COMSEC account: Mark this item “YES” if the contractor is to be held
accountable for COMSEC information. If non-accountable COMSEC information is
involved, mark this item “NO.”
NOTE: Within the Army, COMSEC custodians are either DA civilians or military
members. Contractors are considered hand receipt holders. See AR 380-40 for further
guidance on COMSEC.
11i. Have TEMPEST Requirements: Mark “YES” if the contractor is required to impose
TEMPEST countermeasures for information processing equipment after vulnerability
assessments are completed. TEMPEST requirements are additional to the
requirements of the NISPOM. The prime contractors may not impose TEMPEST
requirements on their subcontractors without the KO approval.
(1) If marked “YES,” Item 14 must also be marked “YES” and pertinent contract
clauses identified or added to Item 13.
28
Enter the following statement in Item 13:
(1) 11j. Operations Security (OPSEC): Mark “YES” if the contractor must impose
certain countermeasures directed to protect intelligence indicators. OPSEC
requirements are additional to the requirements of the NISPOM. The prime
contractors may not impose OPSEC requirements on their subcontractors unless
the KO approves the OPSEC requirements. If marked “YES,” Item 14 must also
be marked “YES” and pertinent contract clauses identified or added to Item 13.
(2) If marked “YES”, the pertinent OPSEC guidance must be listed in Item 13, if
applicable.
Check if any special security guidance is required. It may require checking 10k as well.
OPSEC requirements apply to National Industrial Security Program (NISP) contractors
when it is determined that additional safeguards are essential for specific contracts; they
are imposed in addition to the standard requirements of the NISP.
11k. Be authorized to use the Defense Courier Service (DCS): A “YES” in this block
authorizes the contractor to use the services of DCS. The KO must obtain written
approval from the Commander, Defense Courier Service, Attn: Operations Division, Fort
George G. Meade, MD. 20755-5370. Only certain classified information qualifies for
shipment by DCS. Prior approval of the KO is required before a prime contractor can
authorize a subcontractor to use the services of DCS.
If the contractor is receiving materials through DCS then 1b should be marked “YES” to
the appropriate safeguarding level (TS, S, or C). If this is marked “NO” then using DCS
is not an option for the contractor.
11l. Other (Specify): Use this item to add any additional performance requirements not
covered above. Annotate item 13 to provide any necessary remarks.
29
f. HAVE ACCESS TO U.S. CLASSIFIED INFORMATION
OUTSIDE THE U.S., PUERTO RICO, U.S. POSSESSIONS AND
TRUST TERRITORIES
g. BE AUTHORIZED TO USE THE SERVICES OF DEFENSE
TECHNICAL INFORMATION CENTER (DTIC) OR OTHER
SECONDARY DISTRIBUTION CENTER
h. REQUIRE A COMSEC ACCOUNT
i. HAVE A TEMPEST REQUIREMENT
j. HAVE OPERATIONS SECURITY (OPSEC)
REQUIREMENTS
k. BE AUTHORIZED TO USE THE DEFENSE COURIER
SERVICE
l. OTHER (Specify).
The contractor is responsible for obtaining the approval of the KO prior to release of any
information received or generated under the contract. The KO should complete this item
as required by internal agency directives to direct the prime contractor to the appropriate
office that has public release authority. Prime contractors should refer their
subcontractors to the KO that was referenced in the prime contract DD Form 254.
12. PUBLIC RELEASE. Any information (classified or unclassified) pertaining to this contract shall not be released for public
dissemination except as provided by the industrial Security Manual or unless it has been approved for public release by appropriate U.S.
Government authority. Proposed public release shall be submitted for approval prior to release
Through (Specify):
To the Directorate for Freedom of Information and Security Review, Office of the Assistant Secretary of Defense (Public Affairs)* (Office of Freedom of Information; 1155 Defense Pentagon, Room 2C757;
Washington, DC 20301-1155) for review. * In the case of non-DoD User Agencies, requests for disclosure shall be submitted to that agency.
Use this block to expand or explain information marked “Yes” in blocks 10 and 11 of the
DD Form 254. If the information does not fit into Block 13, annotate “See Attached
Addendum” and provide all additional information accordingly. Be sure to: Identify the
specific information to be classified; provide appropriate downgrading or declassification
instructions; Security Classification Guidance; and provide any special instructions,
explanations, comments, or statements necessary to clarify other items identified in the
DD Form 254. The information provided should be unclassified. When completing
Item 13 consider the following questions. In this case, more information is better.
These questions should be asked when preparing guidance for a contractor:
(1) What classified information will the contractor need in the performance of this
contract?
30
(2) Is there an existing Security Classification Guide for the Program?
(3) If subcontracting, is the guidance in the Prime Contract DD Form 254 adequate?
Does the entire Prime Contract DD Form 254 apply to the subcontract or do you
only need to provide applicable portions?
(4) Will classified source documents be used? If so, do they contain all the guidance
the contractor needs?
(5) What will the contractor’s actual performance be? (e.g., R&D, Test, Production,
Study, etc.?)
(6) What unique characteristics are involved that need protection? Are there design
features which require protection? Is there technical information which will
require protection?
(7) What breakthroughs would be significant if achieved in an R&D effort?
(8) Are there performance limitations that require protection?
(9) Will classified hardware be furnished to or generated by the contractor?
(10) What information makes the hardware/services classified?
(11) Will hardware/data being generated require classification?
(12) At what stage in its production does hardware/data become classified?
Factors to consider when completing Item 13 include:
31
(5) Encourage participation by the contractor in the preparation of the guidance and
submission of comments and/or recommendations for changes in the guidance
that has been provided.
Provide the points of contact information in Block 13 (Program Manager,
COR/CM/COTR and those individuals who play a significant role in the contract). The
COR/CM must sign in block 13 acknowledging they have reviewed the DD Form 254
and are in agreement and provide the following statement: “The undersigned has
reviewed this Security Specification, understands the provisions and will ensure that it is
complied with within the limits of his/her responsibility, and that any violations are
brought to the attention of the KO and supporting Security Manager."
Use this section to explain anything that might be unclear, confusing, or particularly
important. Be careful not to include anything that could be interpreted as a contradiction
to information elsewhere on this form. This section can extend to additional pages if
needed. There is no set page limit.
Provide any training requirements for contractors relating to the mission and/or
contractual duties (i.e., COMSEC hand receipt holders, Information Assurance, AT/FP,
etc.).
The DD Form 254 is a legal document and part of the contract. It is the source of
security requirements and guidance that the contractor receives from the Army. Include
names of pertinent manuals, page numbers, and other helpful designations (be sure to
attach all referenced materials).
If additional space is required for Item 13, note the attachment(s) at the end of Item 13.
The contract number must be placed at the top of each Attachment page to ensure
proper identification if inadvertently separated from the DD Form 254. Number the
pages as needed.
When providing additional guidance in Item 13 or the Attachment, identify the item
number being expanded upon. (i.e., Item 10j: FOUO…)
List the Security Classification Guides (SCGs) applicable to the performance of the
contract.
Additional “Actual Performance Locations” (items 8a, 8b and 8c) should be listed in Item
13. For SCI contracts, list all performance locations in item 11 of the SCI Addendum.
32
If there are additional “required distributions” (Item 17f), list in item 13 or add an
Attachment page.
13. SECURITY GUIDANCE. The security classification guidance needed for this effort is identified below. If any difficulty is
encountered in applying this guidance or if any other contributing factor indicates a need for changes in this guidance, the contractor is authorized
and encouraged to provide recommended changes: to challenge the guidance or classification assigned to any information or material furnished
or generated under this contract; and to submit any questions for interpretation of this guidance to the official identified below. Pending final
decision, the information involved shall be handled and protected at the highest level of classification assigned or recommended. (Fill in as
appropriate for the classified effort. Attach, or forward under separate correspondence, any document/guides/extracts referenced herein. Add
additional pages as needed to provide complete guidance.
Complete this item when security requirements are imposed on a contractor in addition
to the requirements of the NISPOM or its supplements.
(1) A “YES” in this item requires the KO or prime contractor to incorporate the
additional requirements in the contract itself or to incorporate the additional
requirements by statements or reference in Item 13.
(2) Costs incurred due to additional security requirements are subject to negotiation
between the contractor and the KO.
(3) Prior approval of the KO is required before a prime contractor can impose
additional security requirements on a subcontractor.
(4) A copy of the DD Form 254 containing the additional security requirements will
be provided to the KO.
SAP or SCI are examples of programs and information that would require additional
security requirements.
14. ADDITIONAL SECURITY REQUIREMENTS. Requirements, in addition to ISM requirements, are Yes No
established for this contract. (If Yes, identify the pertinent contractual clauses in the contract document itself, or
provide an appropriate statement which identifies the additional requirements. Provide a copy of the requirements
to the cognizant security office. Use Item 13 if additional space is needed.)
33
Item 15. Inspections
Mark “YES” if DSS is relieved, in whole or in part, of the responsibility to conduct
security reviews and provide security oversight to the contractor. Information should be
provided regarding the specific areas from which DSS is excluded and the agency that
will assume the responsibility.
DSS is relieved of the responsibility to inspect:
(1) SCI material. When access to SCI is required (Item 10e (l)), the following
statement must be added: “(Enter appropriate Agency/Military Department
Senior Intelligence Officer) has exclusive security responsibility for SCI classified
material released or developed under this contract and held within the
contractor’s SCIF.” DSS will inspect SCI if there is an agreement with the
program office and CSE. (2) Special Access Programs where DSS is “carved
out” from inspection responsibility. Not all Army SAPs are “carve outs”. In some
instances, the cognizant SAP security office will allow DSS to retain inspection
responsibility. If Block 15 is checked “YES” the KO must provide the approval
and reporting of the “carve-out”.
(3) Contractor facilities operating on military installations when the installation
Commander has elected to retain security cognizance. It is the responsibility of
the supporting ISS to maintain copies of all inspections performed on the
program during the life of the DD Form 254. The ISS will ensure the KO receives
copies of the inspection reports.
In all cases, provide DSS a copy of the DD Form 254.
If inspections will be conducted by an organization other than DSS, complete Item 15.
An inspection by an agency other than DSS does not change DSS’ designation as CSO
and does not relieve the KO from the responsibility of providing a copy of the DD Form
254 to DSS.
When an Army Commander has determined to retain oversight and inspection of a
cleared contractor facility, the supporting ISS, who is responsible for the inspections and
oversight of the cleared facility, will brief key DA, KO and the PM/PEO on the status of the
cleared contractor security program. The ISS will retain copies of the inspections and
provide a copy of reviews and other related assessments to the KO. A copy of the
inspection report is normally not provided to DSS unless extenuating circumstances exist.
The POC, supporting security office and the organization responsible for inspections
must be listed in block 15. Use block 13 on an Attachment page if additional space is
needed.
15. INSPECTIONS. Elements of this contract are outside the inspection responsibility of the Yes No
cognizant security office. (If Yes, explain and identify specific areas or elements carved out and the
activity responsible for inspections. Use Item 13 if additional space is needed.
34
Item 16. Certification and Signature
Enter the name, title, telephone number, address and signature of the Security
Manager. The Security Manager is the official certifying that the security requirements
are complete and adequate for performance of the classified contract. The Army
Federal Acquisition Regulation Supplement (AFARS) designates the Security Manager
sign in block 16.
The KO must ensure that the DD Form 254 has been adequately staffed among the
appropriate contracting, program and security personnel.
16. CERTIFICATION AND SIGNATURE. Security requirements stated herein are complete and adequate for safeguarding the
classified information to be released or generated under this classified effort. All questions shall be referred to the official named below .
a. TYPED NAME OF CERTIFYING OFFICIAL b. TITLE c. TELEPHONE (Include Area Code)
Date Signed:
IAW AFAR , Paragraph 5104.403 (22 May 2007)
d. ADDRESS (Include ZIP Code)
b. SUBCONTRACTOR
c. COGNIZANT SECURITY OFFICE FOR PRIME AND SUBCONTRACTOR
e. ADMINISTRATIVE KOR
f. OTHERS AS NECESSARY
35
Chapter 5
ACRONYMS: Security related acronyms, abbreviations and basic terms used in this guide.
36
NISPOM - National Industrial Security Program Operating Manual
OISI - Office of Industrial Security International
OPSEC - Operations Security
PSO - Program Security Officer
RD - Restricted Data
RFP - Request for Proposal
RFQ - Request for Quote
SAP - Special Access Program
SCI - Sensitive Compartmented Information
TCAR - TEMPEST Countermeasure Assessment Request
TMO – Technology Management Office
37
Chapter 6
Definitions:
Classified Information - Any information that is owned by, produced by or for, or under
the control of the U.S. Government, and determined pursuant to Executive Order
12958, or prior orders, to require protection against unauthorized disclosure, and is
designated as TOP SECRET, SECRET or CONFIDENTIAL.
CNWDI - Critical Nuclear Weapon Design Information. A DoD category of weapon data
designating TOP SECRET Restricted Data or SECRET Restricted Data revealing the
theory of operation or design of the components of a thermonuclear or implosion-type
fission bomb, warhead, demolition munitions, or test device.
Cognizant Security Agency - Agencies of the Executive Branch that have been
authorized to establish and industrial security program to safeguard classified
information under the jurisdiction of those agencies when disclosed or released to U.S.
industry. These agencies are: The Department of Defense, Department of Energy,
Central Intelligence Agency and the Nuclear Regulatory Commission.
38
Cognizant Security Office – The office or offices delegated by the Head of a Cognizant
Security Agency to administer industrial security on behalf of the Cognizant Security Agency.
Contractor – Any industrial, educational, commercial, or other entity that has been
granted a facility clearance (FCL) by a CSA.
b. Produced by the U.S pursuant to, or as a result of, a joint arrangement with a
20governments or any element thereof requiring that the information, the arrangement,
or both are to be held in confidence.
Formerly Restricted Data - Classified information jointly determined by the DoE and its
predecessors and the DoD to be related primarily to the military utilization of atomic
weapons and removed by the DOE from the Restricted Data category pursuant to
section 142(d) of the Atomic Energy Act of 1954, as amended, and safeguarded as
National Security Information, subject to the restrictions on transmission to other
countries and regional defense organizations that apply to Restricted Data.
39
For Official Use Only - Information that has not been given a security classification pursuant
to the criteria of an Executive Order, but which may be withheld from public disclosure
under the criteria of the Freedom of Information Act, Title 5, U.S.C., Section 552.
Industrial Security - That portion of internal security that is concerned with the protection
of classified information in the hands of U.S. industry.
NATO Classified Information - The term “NATO classified information” embraces all
classified information, military, political and economic that is circulated within an by
NATO whether such information originates in the organization itself or is received from
member nations or from other international organizations.
NATO Information - Information bearing NATO markings, indicating the information is the
property of NATO, access to which is limited to representatives of NATO and its member
nations unless proper NATO authority has been obtained to release outside of NATO.
Prime Contractor - Any contractor who has received a prime contract from a
Government Agency. For purposes of subcontracting, a subcontractor shall be
considered to be a prime contractor in relation to its subcontractor.
40
Restricted Data - All data concerning the design, manufacture, or utilization of atomic
weapons; the production of special nuclear material; or the use of special nuclear material
in the production of energy, but shall not include data declassified or removed from the RD
category pursuant to section 142 of the Atomic Energy Act of 1954, as amended.
SAP - Special Access Program - Any program that is established to control access,
distribution, and to provide protection for particularly sensitive classified information
beyond that normally required for TOP SECRET, SECRET OR CONFIDENTIAL
information. A special Access Program can be created or continued only as authorized
by the Deputy Secretary of Defense pursuant to E.0. 13526.
41
Chapter 7
Additional Information
CAGE CODE: All cage codes are five (5) digits long and begin and end with a number.
Additional Performance Locations: Some contractor facilities have off-site locations that
handle and store classified information but do not possess a unique cage code. These
off site locations fall under the security umbrella of the prime contractor and must be
within a 60-minute drive from the primary facility. The primary Facility Security Officer
(FSO) has security over site of these locations. The User Agency will communicate with
the primary facility only. The off-site location will not be cited on the DD Form 254.
If the COMSEC material is accountable but the contractor only has access to it
at the User Agency, then item 10a is marked “YES” and 11h is marked “NO”.
If the COMSEC material is accountable and the contractor has access to it at
the contracting facility, then item 10a is marked “YES” and item 11h is marked
“YES”.
NOTE: Contractors are hand receipt holders and not COMSEC Custodians. See AR
380-40 for further clarification.
42
Secure telephones (STEs):
43
APPENDIX A
EXAMPLE OF US ARMY SAP ADDENDUM TO DD FORM 254
XXX (1) This contract requires access to Special Access Program information (SAPI).
The Commander, US Army Training and Doctrine Command (TRADOC)(Fill in the
name of the contracting command or activity), as the Cognizant Security Authority
(CSA) for the US Army for this contract, has security oversight and management
responsibility for all SAPI released to the contractor or developed under this contract,
held within the Contractor's SAP Facility (SAPF) or in SCIF or SAPF under a Co-
utilization Agreement (CUA). TRADOC is acting on behalf of the Technology
Management Office (TMO), the Army Special Access Program Coordination Office
(SAPCO) which is responsible for security oversight and management for Army SAPs.
Under this contract, the Defense Security Service (DSS) is responsible for security
compliance inspections of contractor SAP facilities. DSS retains responsibility for all
collateral information released or developed under the contract. The contracting
organization will assist the government when conducting threat and vulnerability
surveys. The manuals, regulations and directives checked below provide the necessary
guidance for physical, personnel, and information security for safeguarding SAPI, and
are part of the security classification specification for this contract:
XXX DoD 5220.22-M-1, NISPOM, with DoD overprint and NISPOMSUB
XXX JAFAN 6/3, Protecting Special Access Program Information within Information
Systems
XXX JAFAN 6/4, Special Access Program Tier Review Process
XXX JAFAN 6/9, Physical Security Standards for Special Access Program Facilities, w/
change 2
XXX AR 25-2, Information Assurance
XXX AR 380-28, DA Special Security System
XXX AR 380-381, Special Access Programs (SAPS) and Sensitive Activities.
XXX Other
XXX (2) Contract estimated completion date: TBD by prime contract
XXX (3) The name, telephone number, email address and mailing address of the
Contract Monitor (CM) for the SAP portion of this contract is: John Smith, Program
Security Manager (PSM), 757-555-5555. NIPR: [Link]@[Link] / SIPR:
[Link]@[Link]. (The Contract Monitor and the contractor security officer
must be registered in the Army Contractor Automated Verification System (ACAVS) in
order to process SAP actions)
XXX (4) All DD Forms 254 prepared for subcontracts involving access to SAP under this
contract must be forwarded to the PSM for approval and then to the Contracting Officer
and Program Manager for review and concurrence prior to award of the subcontract.
44
XXX (5) The contractor will submit the request for SAP visit certifications through the
PSM for approval of the visit. The certification request must arrive at the PSM at least
ten (10) working days prior to the visit. Visit certification requests will be processed
through ACAVS.
XXX (6) The contractor will not reproduce any SAPI related material without prior written
permission of the CM.
XXX (7) Security Classification Guides or extracts are attached or will be provided under
separate cover.
XXX (8) Electronic processing of SAP requires accreditation of the equipment in
accordance with JAFAN 6/3 and AR 25-2. (Note: Check only if item 11l indicates that a
requirement exists for SAP AIS processing.)
XXX (9) This contract requires a contractor SAPF.
XXX (10) This contract requires indoctrination to ZGD(U) Special Access Program.
XXX (11) The contractor will perform SAPI work under this contract at the following
locations: (list all locations)
45
APPENDIX B
INSTRUCTIONS FOR THE US ARMY SCI ADDENDUM TO DD FORM 254
General: This section contains specific instructions for preparation of the “SCI
Addendum," used in conjunction with the DD Form 254, for all Army SCI contracts and
their related SCI subcontracts.
a. The SCI addendum is designed for use with the DD Form 254 on all Army SCI
contractual efforts and their related subcontracts. The User Agency and the appointed
CM are responsible for coordinating with HQ INSCOM, ACofS Security, G2, Contractor
Support Element (CSE) for developing and incorporating the SCI addendum with an
appropriate DD Form 254 for the prime contract.
b. Based on the guidance provided in the DD Form 254 and SCI addendum for the
prime contract, the contractor (prime) is responsible for coordinating with the CM and
the CSE for developing and incorporating the SCI addendum with an appropriate DD
Form 254 for all related subcontracts.
This document must be executed and accompany all DD Forms 254 issued for Request
for BID (RFB), Request for Proposal (RFP), Request for Quotation (RFQ), etc., and
forwarded with the DD Form 254 to the CSE prior to award of an Army SCI contract.
Those items that are pre “X’d”, apply to all Army SCI contracts/subcontracts.
Item 1: Regulations listed that are not marked, are to be marked with an “X “when they
apply.
Imagery Policy Series (Available from the CM): Applies when the contract/subcontract
requires TK level SCI (i.e. access, documents etc.)
DIAM 50-24, Security for Using Communication Equipment in a SCIF: Applies when and
if a contractor/subcontractor intends the use of a modem connected to an unencrypted
black telephone line and/or the use of secure telephone unit data port within an
accredited SCIF.
AR 25-2, Information Assurance: Applies when item 11l of the DD Form 254 is marked “Yes”.
46
AR 380-381, Special Access Programs (SAPS): Applies when item 10f of the DD Form
254 is marked “Yes”.
Item 3: The name, official organization address, email address and telephone number
of the designated Contract Monitor (CM) by the User Agency (contracting agency/
office). NOTE: The CM designated must be either military or a DA civilian, who
possess the appropriate SCI access to the levels required by the contract. Further, the
CM for the prime contract is always the CM for all related subcontracts. Additionally, in
this item, identify the Security POC, with telephone number and email address, at the
company to be awarded the contract/subcontract.
Item 4: When a subcontract for a portion of the SCI contract is to be authorized, prior to
award of the subcontract, the prime contractor must execute and forward a DD Form
254 for the proposed subcontract through the prime contract CM, for his/her approval, to
the CSE for concurrence.
Item 6: Identifies the requirement for prior written authority to reproduce SCI and all
related material.
Item 7: Identifies whether or not classification guide(s) or extract(s) exist for this specific
contract and how they are to be obtained by the contractor.
Item 9: Identifies the requirement for the contractor to have their own accredited SCIF
or co-utilized SCIF to execute the SCI portion of the contract.
Item 10: Cites the accesses required for execution of the contract, mark what accesses
are required for performance on the contract/subcontract. Further, allows the option of
citing an estimated number of accesses required
Item 11: Requires identification, in addition to Item 8 of the DD Form 254, of any
additional locations where SCI work for this specific contract will be conducted.
47
CONTRACT # TBD
SOLICITATION #
EXAMPLE OF US ARMY SCI ADDENDUM TO DD FORM 254, (date)
XXX (1) This contract requires access to Sensitive Compartmented Information (SCI).
The Commander, US Army Intelligence and Security Command (INSCOM), acting on
behalf of the DA Deputy Chief of Staff (DCS), G-2 as the Cognizant Security Authority
(CSA) for the US Army, has exclusive security responsibility for all SCI released to the
contractor or developed under the contract and held within the Contractor's SCI Facility
(SCIF) or Co-utilization Agreement (CUA) SCIF. The Defense Intelligence Agency
(DIA) has security inspection responsibility for SCI and the Defense Security Service
(DSS) retains responsibility for all collateral information released or developed under the
contract and held within the DoD Contractor's SCIF. The manuals, regulations and
directives checked below provide the necessary guidance for physical, personnel, and
information security for safeguarding SCI, and are part of the security classification
specification for this contract:
XXX (2) Contract estimated completion date: TBD (NOTE: Section “F” of the contract
normally provides the Period of Performance. Option years are not to be included, as
an option is not valid until exercised by the government.)
XXX (3) The name, telephone number, email address and mailing address of the
Contract Monitor (CM) for the SCI portion of this contract is:
SCTY POC: TBD (Identify the Security POC & phone number and email address at the
contractor’s/subcontractor’s location)
(The Contract Monitor and the contractor security officer must be registered in the Army
Contractor Automated Verification System (ACAVS) in order to process SCI actions)
48
XXX (4) All DD Forms 254 prepared for subcontracts involving access to SCI under this
contract must be forwarded to the CM for approval and then to HQ INSCOM, ACofS
Security, G2, Contractor Support Element (CSE) for review and concurrence prior to
award of the subcontract.
XXX (5) The contractor will submit the request for SCI visit certifications through the CM
for approval of the visit. The certification request must arrive at the Contractor Support
Element at least ten (10) working days prior to the visit. Visit certification requests will
be processed through ACAVS.
XXX (6) The contractor will not reproduce any SCI related material without prior written
permission of the CM.
XXX (7) Security Classification Guides or extracts are attached or will be provided under
separate cover.
XXX (10) This contract requires XX (SI) ___ (TK) ___ (G) ___ (HCS) (Add others as
required)
XXX (11) The contractor will perform SCI work under this contract at the following
locations: TBD (Identify the location and CAGE code)
49
Electronic processing of SCI demands accreditation of the equipment in line with DCID 6/3, and AR 25-2 standards. Contractors must ensure the equipment used is properly certified and secure to manage SCI, reflecting stringent adherence to safeguarding measures. This includes maintaining a SCIF environment or co-utilizing a SCIF to handle SCI securely, necessitating thorough preparation, accreditation, and compliance checks .
The Contract Monitor (CM) oversees security compliance for contracts involving SAPs. They provide initial approval for DD Forms 254 related to SAPs, ensuring alignment with security protocols. The CM facilitates coordination between contractors, HQ INSCOM, and the CSE for creating a compliant security addendum and manages the SAP visit certifications process. They act as the primary point of contact for any permissions related to SAP reproduction or security breaches .
Marking 'YES' for OPSEC indicates that additional countermeasures are needed to protect intelligence indicators, enhancing security above standard NISPOM requirements. The contractor must receive specific OPSEC guidance, authorized by the KO, potentially affecting multiple elements of contract management and execution. These requirements may also extend to subcontractors, necessitating thorough security oversight and compliance documentation .
When a contractor is marked to receive classified documents only, they are expected to use these documents for reference without generating additional classified material. Classification marks on the documents provide necessary guidance. If classified materials are stored, but the work is performed at a government site, the contractor must ensure that derivative classification aligns with the source material, and appropriate storage security measures are in place .
Contractors authorized to use the Defense Courier Service (DCS) must obtain written approval from the Defense Courier Service Operations Division before use. Approval by the KO is mandatory, ensuring that only eligible classified information is shipped through this service. If approved, adherence to all procedures and security protocols is essential, ensuring that security measures for transit are consistent with strict military standards .
While the DIA handles security inspections specific to SCI, the DSS is responsible for collateral information released in conjunction with SCI. The DIA focuses on the internal mechanisms ensuring SCI's security integrity, while the DSS oversees collateral adherence, ensuring cohesive compliance with all non-SCI related information, demanding coordination between agencies .
Public release management involves seeking KO approval before any information dissemination. Contractors are directed by internal agency directives, and any potential public releases must be submitted for review to the Directorate for Freedom of Information and Security Review under the Assistant Secretary of Defense. This control ensures handling aligns with national security interests and contractual confidentiality commitments .
When TEMPEST requirements are marked 'YES', the contractor must ensure vulnerability assessments are completed and implement necessary countermeasures for information processing equipment. TEMPEST requirements supplement NISPOM standards, requiring KO approval before imposition on subcontractors. Relevant contract clauses should be included and approved TEMPEST Countermeasure Assessment Requests may be appended to DD Form 254 . Additionally, only employees with appropriate security clearance are given access to TEMPEST information .
Accreditation for processing SAPI electronically means ensuring the equipment meets specific physical and system security standards laid out in JAFAN and AR protocols. Compliance involves extensive checks to prevent unauthorized data access, preventing leaks through unintentional emissions (e.g., TEMPEST concerns). The process underscores the significance of controlled environments like SCIFs, enforcing strict standards for data handling, system validation, and system integrity .
Contractors need to submit SAP visit certifications through the Program Security Manager (PSM) for approval. The request must reach the PSM at least ten working days prior to the scheduled visit. These requests are processed through the Army Contractor Automated Verification System (ACAVS) for validation, ensuring appropriate security measures and compliance are met before task execution .