Initial DD Form 254_2025.03.06.pdf

PDF 2 MB Posted

Attached to
AFTAC Data Operations (Data Ops) Federal contract opportunity
Solicitation number
FA702225R0002
Issued by
Department of the Air Force Air Combat Command

About this file

This document is a Sources Sought Notice for the Air Force Technical Applications Center (AFTAC) Data Operations opportunity. The procurement seeks industry white papers through the AFTAC Commercial Solutions Opening (CSO) 2024, Topic 6 for Enterprise Wide Integration and Architecture Modernization. The anticipated contract is a Firm Fixed Price (FFP) Indefinite Delivery Indefinite Quantity (IDIQ) with a base 5-year ordering period, estimated to award in November 2025. Potential contract CLINs include on-cloud development (R&D), on-premise and on-cloud data operations (O&M), travel, and technical data deliverables.

The requirement involves transitioning AFTAC's cross-domain data operations from on-premises to Amazon Web Services (AWS) cloud environment, enabling secure data exchange between SECRET and TOP SECRET domains. Contractor requirements include a TOP SECRET facility clearance, eligibility for personnel working in sensitive compartmented information facilities, and capability to handle mission data from various sources. The current incumbent is Leidos, Inc., but this is not a follow-on procurement. The effort focuses on creating an efficient, maintainable cloud-based cross-domain data operations system with priorities on cost-minimization, using current software languages, and maintaining security compliance with Air Force guidance.

View the file

Other files for this federal contract opportunity

Other files attached to AFTAC Data Operations (Data Ops), newest first.
File Type Posted
NIFI Software Inventory_2025.03.04.xlsx XLSX spreadsheet
SECDEF MEMO_DIRECTING-MODERN-SOFTWARE-ACQUISITION-TO-MAXIMIZE-LETHALITY_2025.03.06.pdf PDF
DRAFT_BASIC Data Ops SOO_2025.03.17.pdf PDF
Data Ops CDRLS_Signed_2025.03.06.pdf PDF

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Please wait...

If this message is not eventually replaced by the proper contents of the document, your PDF viewer may not be able to display this type of document.

You can upgrade to the latest version of Adobe Reader for Windows®, Mac, or Linux® by visiting http://www.adobe.com/go/reader_download.

For more assistance with Adobe Reader visit http://www.adobe.com/go/acrreader.

Windows is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries. Mac is a trademark of Apple Inc., registered in the United States and other countries. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

(U) ADDENDUM FOR CONTRACT: ##

(U) CONTRACT COMPLETION DATE: 05 Mar 2025

(U) NETWORK ACCESS REQUIRED: NIPR, SIPR, JWICS

(U) PRIVILEGED USERS SUPPORT THIS CONTRACT: YES

Block 13 DD Form 254

10.b,c,d: Government Contracting Agency (GCS) approval is required prior to granting CNWDI to a subcontractor. The Secretary of Energy and the Chairman of the Nuclear Regulatory Commission retain authority over access to information that is under their respective cognizance as directed by the Atomic Energy Act of 1954. The Secretary of Energy may inspect and monitor contractor programs or facilities that involve access to such information or may enter written agreement with the DoD to inspect and monitor these programs or facilities. A special briefing is required for access to CNWDI, and a final security clearance is required for access to CNWDI and RD information. Only contractors approved by the AFTAC RD Manager may classify RD and FRD documents.

10.e.: (1): See attached SCI Addendum for additional security requirements. Access to intelligence information requires a final Top Secret U.S. Government clearance and SCI indoctrination. Personnel are required to sign an SCI Non-Disclosure Agreement. The contractor must provide individuals who are able to achieve and maintain the eligibility standards for access to SCI and other controlled access program information as set forth in the Intelligence Community Directive (ICD) 704 Personnel Security Standards and Procedures Governing Eligibility for Access to Sensitive Compartmented Information and Other Controlled Access Program Information, for continued employment. The GCA must provide prior approval before a subcontract involving access to intelligence information can be issued.

10.e.(2): Contractor will require access to ICD 710 Classification Management and Control Markings System. For Non-SCI Requirements: All contractor personnel assigned under this contract must possess a current Top Secret security clearance. Personnel are required to sign a non-disclosure agreement. The GCA must provide prior approval before a subcontract involving access to non-intelligence information can be issued. Access to intelligence information will be handled in accordance with Attachment entitled Release of Non-SCI Intelligence Information to U.S. Contractors.

10.g: The COR has determined that the contractor will have access to NATO classified and restricted information in order to accomplish daily duties. “Special briefings are required for access to NATO IAW DoDM5200.01V1_DAFMAN16-1404V1, Air Force Information Security Program, or as amended. Contractors requiring access to JWICS and SIPRNet will be briefed NATO SECRET access and sign the appropriate NATO Briefing Acknowledgment Form. Prior approval of the contracting activity is required for subcontracting. Access to classified NATO information requires a final U. S. government clearance at the appropriate level.

10.h: FGI must be protected at the equivalent level provided to similar categories of U.S. Government information or as specified by the foreign Government in written Government-to-Government agreements. Access to classified FGI requires a final U.S. Government clearance at the appropriate level. Prior approval from the COR is required prior to subcontracting. The contractor must adhere to the requirements of 32 CFR Part 117.

10.j.: Controlled Unclassified Information provided under this contract shall be safeguarded as specified in the Attachment, ‘Protecting Controlled Unclassified Information.’”

ITEM 11:

11.c: The contractor requires access classified source data up to and including SECRET in support of the work effort. SCI information will NOT be received, stored, or generated at the contractor’s facility

11i: The contractor shall abide by the TEMPEST security standards in accordance with CNSSP 300 (National Policy on Control of Compromising Emanations) Air Force Manual 17-1301 and CNSSI 7000 (TEMPEST Countermeasures for Facilities).

11j: The contractor will apply Operations Security (OPSEC) to enhance protection for classified and unclassified critical information. While the documents identified in references below provide details on the development of OPSEC programs and implementation of OPSEC analyses, the requirements below provide the minimum standards for OPSEC application directed in this contract. The contractor manager or a delegated OPSEC coordinator will be familiar with Operations Security (OPSEC) as described in Air Force instruction 10-701, National Security Decision Directive Number 298, DoD Directive 5205.02, and DoD Manual 5205.02-M.

Ref Item 11l: Contractor will refer to DoDI 5200.48 and Protecting Controlled Unclassified Information addendum when receiving, storing, or generating CUI.

ACCESS TO SENSITIVE COMPARTMENTED INFORMATION (SCI)

1. Inquiries pertaining to classification guidance on SCI will be directed to the responsible AFTAC Contracting Officer’s Representative (COR), or Program Manager (PM) and the AFTAC Special Security Officer (SSO) as identified under Item 13 of the DD Form 254. (The term PM refers to PM and COR, in this document). SCI access is limited to the executable term of the contract which is identified in Item 13 of the DD Form 254. Upon expiration of the SCI contract, all contractors with SCI accesses must be withdrawn and all SCI materials must be recovered.

2. All SCI access required in the performance of this contract will be justified through the PM and maintained/approved by AFTAC SSO. The PM will provide the contractor Facility Security Officer (FSO) or contractor Special Security Officer (CSSO) with written approval of personnel and the necessary data to submit request(s) for Tier 5 (T5), Tier 5 Reinvestigation (T5R) or continuous evaluation. Term certifications from any other government agencies for contractors working SCI portions of the AFTAC contracts are acceptable for the time between submission and approval of the contractor SCI access request. FSO/CSSO will be required to pass Personal Identifying Information (PII) to the AFTAC SSO; contractor must make provisions for approved electronic encryption methods to communicate required information. The AFTAC SSO is the final authority for approval of contractor personnel SCI access. The COR is responsible to ensure the SCI access nomination letter is properly completed and sent to the AFTAC SSO for approval.

3. The FSO/CSSO is responsible to establish and maintain an SCI personnel access list of those employees working on the contract to include sub-contractors. FSO/CSSO will provide a copy of this list at least yearly to the PM/COR and SSO.

4. The FSO/CSSO will advise the PM and AFTAC SSO immediately upon reassignment, dismissal, termination, or revocation of need-to-know for SCI cleared personnel on contract. A formal notice to the AFTAC SSO is required for processing debrief action. FSO/CSSOs will notify the PM and AFTAC SSO immediately when there is a change in status of SCI indoctrinated contractor personnel.

FSO/CSSOs report potentially derogatory information as outlined in Security Executive Agent Directives (SEAD) 3 and 4 without applying any mitigation. FSO/CSSO's are not authorized to restrict reporting of information based on its source. FSO/CSSO and all contract personnel must report any concerns that applies to the DoD Insider Threat Management Analysis Center (DITMAC) 13 Reporting Thresholds.

5. FSO/CSSO must coordinate approval prior to subcontracting any portion of SCI efforts involved in the contract. The prime contractor will get approval from the COR/CO before a contract can be sub contracted. The subcontractor DD Form 254 must be signed by the AFTAC SSO prior to administered.

6. Release of Information: Before releasing SCI information to a contractor facility, the COR will get approval from the AFTAC SSO.

7. SCI documentation, or other material concerning this contract will not be discussed with or released to any individual, subcontractor, agency (including Federal Government agencies and employees), and contractor employees not working on the contract without prior written approval from the PM.

8. Any SCI-derived material generated under this contract will be reviewed by the PM and AFTAC SSO for proper classification prior to final publication and distribution. All non-SCI documents and publications developed by the contractor under this contract require mandatory review by the AFTAC SSO and PM prior to public release authorization. Final Technical Reports must be sent to the AFTAC SSO via approved shipping/handling methods at the address below.

9. Any SCI data released to or generated by the contractor in support of this contract remains the property of the DoD Department, agency, or command that released it. The contractor will maintain a record of all SCI released to contractor custody under this contract and must return all such material to the AFTAC SSO upon completion/cancellation of the contract. This applies to all data and materials, including working papers and notes. SCI data furnished to or generated by the contractor will require special security handling and controls beyond those in the 32 CFR Part 117, “National Industrial Security Program Operating Manual (NISPOM).

10. Access to SCI is limited to U.S. Government, AFTAC sponsored SCIF locations identified under Item 8.a. or within a Government or Contractor approved SCI facility (SCIF) identified through an approved Memorandum of Agreement (MOA) or Co-Utilization Agreement (CUA).

SCI level work may be approved at a contractor SCIF accredited by an agency other than DIA after CUA approval.

11. If this contract requires electronic processing of SCI, the PM must determine and request a SCIF requirement through the AFTAC SSO in which DIA is the accrediting authority for AF sponsored SCIFs. Operational accreditation of AIS at the SCI level must be obtained through the ICD 503 A&A process.

12. This contract requires additional security requirements established for SCI in accordance with DoDM 5105.21, Volumes 1, 2, and 3; Intelligence Community Directives (ICD); ICD 503, ICD 704, ICD 705, and AFMAN 14-403.

13. The designated security management and oversight authority for SCI under this contract is:

PHONE: COMM: (321) 494-8851

DSN: 854-8851

SCI VOIP 987-2937

Hours of Operation: 0700-1600 Mon-Fri

Defense Courier Service (DCS) 3-Line Address:

SPECIAL SECURITY OFFICE

SSO Patrick 1020 South Patrick Drive

PSFB, FL 32925-3516

DISS SCI-SMO: SSO PATRICK

PLA for M3 Messaging: SSO PATRK

416115-JA25 HKJ

184 NIP JA 023 023

SSO PATRICK

PROTECTING CONTROLLED UNCLASSIFIED INFORMATION

EXTRACTED FROM DODM 5400.07_AFMAN 33-302 AND DODI 5200.48

1. CONTROLLED UNCLASSIFIED INFORMATION (CUI):

In addition to classified information, certain types of unclassified information also require application of access and distribution controls and protective measures for a variety of reasons.

In accordance with Reference DoDI 5200.48, such information is referred to collectively as CUI.

DoDI 5200.48 identifies the controls and protective measures developed for DoD CUI, Law

Enforcement Sensitive (LES), DoD Unclassified Nuclear Information (DoD UCNI), and Limited

Distribution) as well as some of those developed by other Executive Branch agencies.

2. CUI MARKINGS:

a. The CUI marking is assigned to information at the time of its creation by a DoD User

Agency. It is not authorized as a substitute for a security classification marking, but is used on official government information that may be withheld from the public under exemptions

2 through 9 of the Freedom of Information Act (FOIA) and an agency's Critical Information

Indicators List (CIIL) referred to as OPSEC information.

b. Use of the above markings does not mean that the information cannot be released to the public, only that it must be reviewed by the Government prior to its release to determine whether a significant and legitimate government purpose is served by withholding the information or portions of it.

3. IDENTIFICATION MARKINGS:

a. An unclassified document containing CUI will be marked "CUI" at the top and bottom of the front cover (if any), on the first page, on each page containing CUI, on the back page, and on the outside of the back cover (if any).

b. All DAF material containing CUI, including a document with comingled classified information, will include a CUI designation indicator IAW DoDI 5200.48, Figure 2. (Note:

place in bottom right-hand corner of first page).

c. Within a classified document, an individual page that contains CUI 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 CUI, but no classified information, the portion will be marked CUI.

Controlled by: [Name of DoD Component] (Only if not on letterhead)

Controlled by: [Name of Office]

CUI Category: [List category or categories of CUI]

Distribution/Dissemination Control:

d. Within a classified document, an individual page that contains CUI, but no classified information will be marked CUI at the top and bottom of the page, as well as each paragraph that contains CUI.

e. A warning box must be added to the first page of multi-page documents to alert readers to the presence of CUI in a classified DoD document.

f. Any CUI released to a contractor by a DoD User Agency is required to be marked with the following statement prior to transfer:

g. Removal of the CUI marking can only be accomplished by the originator or other competent authority. When the CUI status is terminated, all known holders will be notified to the extent practical.

4. DISSEMINATION: Contractors may disseminate CUI to their employees and subcontractors who have a need for the information in connection with a classified contract.

Recipients shall be made aware of the status of such information, and transmission will be by means that preclude unauthorized public disclosure. Transmittal documents will call attention to the presence of CUI attachments.

5. STORAGE: During working hours, CUI 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 non-working 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 non-working hours. When such internal security control is not exercised, locked buildings or rooms will provide adequate after-hours protection of the material; can be stored in locked receptacles such as file cabinets, desks, or bookcases.

This content is classified at the [insert highest classification level of the source data] level and may contain elements of controlled unclassified information (CUI), unclassified, or information classified at a lower level than the overall classification displayed. This content shall not be used as a source of derivative classification; refer instead to [cite specific reference, where possible, or state “the applicable classification guide(s)”]. This content must be reviewed for both Classified National Security Information (CNSI) and CUI in accordance with DODI 5230.09 prior to public release. [Add a point of contact when needed.]

This document contains information EXEMPT FROM MANDATORY DISCLOSURE under the FOIA. Exemption(s) __________ applies/apply.

6. TRANSPORTATION: CUI may be sent via first-class mail or parcel post. Bulky shipments may be sent by fourth-class mail.

7. DISPOSITION & DISCLOSURE: When no longer needed, record copies of CUI may be disposed of by shredding. Unauthorized disclosure of CUI does not constitute a security violation, but the releasing agency must be informed of any unauthorized disclosure. Appropriate administrative action will be taken to fix responsibility for unauthorized disclosure whenever feasible, and appropriate disciplinary action will be taken against those responsible. The unauthorized disclosure of CUI protected by the Privacy Act may also result in civil and criminal sanctions.

a. The CUI marking is assigned to information at the time of its creation by a DoD User

Agency. It is not authorized as a substitute for a security classification marking, but is used on official government information that may be withheld from the public under exemptions 2 through 9 of the Freedom of Information Act (FOIA).

b. Use of the above markings does not mean that the information cannot be released to the public, only that it must be reviewed by the Government prior to its release to determine whether a significant and legitimate purpose is served by withholding the information or portions of it.

RELEASE OF NON-SENSITIVE COMPARTMENTED INFORMATION (NON-SCI)

INTELLIGENCE INFORMATION TO U.S. CONTRACTORS

1. Requirements for access to non-SCI intelligence:

a. All intelligence material released to the contractor remains the property of the U.S.

Government and may be withdrawn at any time. Contractors must maintain accountability for all classified intelligence released into their custody.

b. The contractor must not reproduce intelligence material without the written permission of the originating agency through the Intelligence Support Office. If permission is granted, each copy shall be controlled in the same manner as the original.

c. The contractor must not destroy any intelligence material without advance approval or as specified by the Program Manager identified under Block 16 of the DD Form 254.

d. The contractor must restrict access to only those individuals who possess the necessary security clearance and who are actually providing services under the contract with a valid need to know. Further dissemination to other contractors, subcontractors, other government agencies, private individuals or organizations is prohibited unless authorized in writing by the originating agency through the Program Manager identified under Item 13 of the DD Form 254.

e. The contractor must ensure each employee having access to intelligence material is fully aware of the special security requirements for this material and shall maintain records in a manner that will permit the contractor to furnish, on demand, the names of individuals who have had access to this material in their custody.

f. Intelligence material must not be released to foreign nationals or immigrant aliens whether they are consultants, U.S. contractors, or employees of the contractor and regardless of the level of their security clearance, except with advance written permission from the originator.

Requests for release to foreign nationals shall be initially forwarded to the contract monitor and shall include:

(1) A copy of the proposed disclosure.

(2) Full justification reflecting the benefits to U.S. interests.

(3) Name, nationality, particulars of clearance, and current access authorization of each proposed foreign national recipient.

g. Upon completion or termination of the classified contract, or sooner when the purpose of the release has been served, the contractor will return all classified intelligence (furnished or generated) to the source from which received unless retention or other disposition instructions (see AFI 33-322) are authorized in writing by the Program Manager identified under Item 16 of the DD Form 254.

h. The contractor must designate an individual who is working on the contract as custodian. The designated custodian shall be responsible for receipting and accounting for all classified material. The inner wrapper of all classified material dispatched should be marked for the attention of a designated custodian and must not be opened by anyone not working directly on the contract.

i. Within 30 days after the final product is received and accepted by the procuring agency, classified intelligence materials released to or generated by the contractor, must be returned to the originating agency, through the Program Manager identified under block 16 of the DD Form 254, unless written instructions authorizing destruction or retention are issued.

Requests to retain material shall be directed to the Program Manager identified under block 16 of the DD Form 254 for this contract in writing and clearly indicate the justification for retention and identity of the specific document to be retained.

j. Classification, regrading, or declassification markings of documentation produced by the contractor shall be consistent with that applied to the information or documentation from which the new document was prepared. If a compilation of information or a complete analysis of subject appears to require a security classification other than that of the source documentation, the contractor shall assign the tentative security classification and request instructions from the contract monitor. Pending final determination, the material shall be safeguarded as required for its assigned or proposed classification, whichever is higher, until the classification is changed or otherwise verified.

2. Intelligence material carries special markings. The following is a list of the authorized control markings of intelligence material:

a. “Dissemination and Extraction of Information Controlled by Originator (ORCON).”

This marking is used, with a security classification, to enable a continuing knowledge and supervision by the originator of the use made of the information involved. This marking may be used on intelligence which clearly identifies, or would reasonably permit ready identification of an intelligence source or method which is particularly susceptible to countermeasures that would nullify or measurably reduce its effectiveness. This marking may not be used when an item or information will reasonably be protected by the use of other markings specified herein, or by the application of the “need-to-know” principle and the safeguarding procedures of the security classification system.

b. Authorized for Release to (Name of the Country(ies)/International Organization).”

The above is abbreviated “REL _________________________.” This marking must be used when it is necessary to identify classified intelligence material the U.S. Government originator has predetermined to be releasable or has been released through established foreign disclosure channels to the indicated country(ies) or organization.

3. The following procedures govern the use of control markings.

a. Any recipient desiring to use intelligence in a manner contrary to restrictions established by the control markings set forth above shall obtain the advance permission of the originating agency through the Program Manager identified under block 16 of the DD Form 254.

Such permission applies only to the specific purposes agreed to by the originator and does not automatically apply to all recipients. Originators shall ensure that prompt consideration is given to recipients’ requests in these regards, with particular attention to reviewing and editing, if necessary, sanitized or paraphrased versions to derive a text suitable for release subject to lesser or no control markings.

b. The control marking authorized above shall be shown on the title page, front cover, and other applicable pages of documents, incorporated in the text of electrical communications, shown on graphics, and associated (in full or abbreviated form‚ with data stored or processed in automatic data processing systems. The control marking also shall be indicated by parenthetical use of the marking abbreviations at the beginning or end of the appropriate portions. If the control marking applies to several or all portions, the document must be marked with a statement to this effect rather than marking each portion individually.

c. The control markings shall be individually assigned at the time of preparation of products and used in conjunction with security classifications and other marking specified by E.O. 13526 and its implementing security directives, in addition to previous Executive Orders.

The marking shall be carried forward to any new format in which the same information is incorporated including oral and visual presentations.

4. Request for release of intelligence material to a contractor not working on an AFTAC contract must be prepared by the Program Manager identified under block 16 of the DD Form 254 and submitted through the AFTAC/SO designated in Item 15 of the DD Form 254. This should be accomplished as soon as possible after the contract has been awarded. The request must include a copy of the DD Form 254 and the Statement of Work.

This marking must be used:

CUI

DEPARTMENT OF THE AIR FORCE

AIR FORCE TECHNICAL APPLICATIONS CENTER

SPECIAL SECURITY OFFICE

CUI

21 October 2024

MEMORANDUM FOR AFTAC CLEARED CONTRACTORS

THROUGH: AFTAC CORS

FROM: AFTAC SPECIAL SECURITY OFFICE

1020 SOUTH PATRICK DRIVE

PATRICK, AFB FL, 32925

SUBJECT: Incident Reports, Counter Insider Threat Reporting And Access Verification in Defense Information System for Security

1. As required by 32 CFR, part 117.8, contractors are required to report all adverse information meeting Security Executive Agent Directive (SEAD) 3 or 4 concerning any of their cleared employees. To ensure communication between Air Force Technical Applications Center (AFTAC) and our industry partners, we must ensure this requirement and AFTAC’s expectations for reporting adverse information are clear. In that vein, the following actions concerning the notification of adverse information to AFTAC must be taken for any contractor employees working on an AFTAC contract with access to classified information. All contracting companies who hold a contract with AFTAC with a requirement for access to classified information or AFTAC facilities must notify AFTAC Personnel Security Office (AFTAC/SOP) of all adverse information or subsequent incident reports within 24 hours of the contractor being aware of such information. Send all notifications to aftac.personnelsecurity@us.af.mil.

AFTAC/SOP will then notify the AFTAC Industrial Security Office and Contracting Officer’s Representative for that effort.

2. Additionally, contractors must report any incidents that meet thresholds in the attached DITMAC Threshold Desk Reference Guide. Such incidents must be reported directly to the AFTAC Counter Insider Threat Liaisons via email address aftac.InTLiaison.mailbox@us.af.mil within 20 days of discovery. This includes adverse information, security violations, personnel security issues, and suspicious contacts.

3. These requirements are to ensure timely notifications to the government authorities granting access to information and facilities, enabling access determinations.

4. Direct any questions you may have to the AFTAC Personnel Security Office at 321-494-6149.

PATRICK L. REAGAN, GG-14, DAF

Special Security Officer

The information herein is FOR OFFICIAL USE ONLY (FOUO) information which must be protected under the Freedom of

Information Act (5 U.S.C. 552) and/or Privacy Act of 1974 (5 U.S.C. 552a). Unauthorized disclosure of misuse of this PERSONAL INFORMATION may result in disciplinary action, criminal, and/or civil penalties.

mailto:aftac.InTLiaison.mailbox@us.af.mil

2024-10-21T09:22:15-0400

REAGAN.PATRICK.LEE.1146160863

PREVIOUS EDITION IS OBSOLETE.

Page of

DD FORM 254, APR 2018

NEEDS DD67

DEPARTMENT OF DEFENSE

CONTRACT SECURITY CLASSIFICATION SPECIFICATION

(The requirements of the National Industrial Security Program (NISP) apply to all security aspects of this effort involving classified information.)

OMB No. 0704-0567 OMB approval expires:

June 30, 2025 The public reporting burden for this collection of information, 0704-0567, is estimated to average 70 minutes per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Washington Headquarters Services, at whs.mc-alex.esd.mbx.dd-dod-information-collections@mail.mil. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number.

RETURN COMPLETED FORM AS DIRECTED IN THE INSTRUCTIONS.

1. CLEARANCE AND SAFEGUARDING

2. THIS SPECIFICATION IS FOR: (X and complete as applicable.)

3. THIS SPECIFICATION IS: (X and complete as applicable.)

a. ORIGINAL (Complete date in all cases.)

b. REVISED (Supersedes all previous specifications.)

4. IS THIS A FOLLOW-ON CONTRACT?

If yes, complete the following:

Classified material received or generated under

5. IS THIS A FINAL DD FORM 254?

If yes, complete the following:

6. CONTRACTOR (Include Commercial and Government Entity (CAGE) Code)

7. SUBCONTRACTOR(S) (Click button if you choose to add or list the subcontractors -- but will still require a separate DD Form 254 issued by a prime contractor to each subcontractor)

8. ACTUAL PERFORMANCE (Click button to add more locations.)

10. CONTRACTOR WILL REQUIRE ACCESS TO: (X all that apply. Provide details in Blocks 13 or 14 as set forth in the instructions.)

e. NATIONAL INTELLIGENCE INFORMATION:

11. IN PERFORMING THIS CONTRACT, THE CONTRACTOR WILL: (X all that apply. See instructions. Provide details in Blocks 13 or 14 as set forth in the instructions.)

12. PUBLIC RELEASE

Any information (classified or unclassified) pertaining to this contract shall not be released for public dissemination except as provided by the National Industrial Security Program Operating Manual (NISPOM) or unless it has been approved for public release by appropriate U.S. Government authority. Proposed public releases shall be submitted for review and approval prior to release to the appropriate government approval authority identified here with at least office and phone contact information and if available, an e-mail address. (See instructions)

13. SECURITY GUIDANCE

The security classification guidance for classified information 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 the 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 documents/guides/extracts referenced herein. The field will expand as text is added. When removing any expanded text area, use delete key or backspace key, then click out of the text field for it to shrink after the text has been deleted. Also allows for up to 6 internal reviewers to digitally sign. See instructions for additional guidance or use of the fillable PDF.)

List of Attachments (All Files Must be attached Prior to Signing, i.e., for any digital signature on the form)

14. ADDITIONAL SECURITY REQUIREMENTS

Requirements, in addition to NISPOM requirements for classified information, are 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 CSO. The field will expand as text is added or you can also use item 13. When removing any expanded text area, use delete key or backspace key, then click out of the text field for it to shrink after the text has been deleted. (See instructions for additional guidance or use of the fillable PDF.)

15. INSPECTIONS

Elements of this contract are outside the inspection responsibility of the CSO.

If Yes, explain and identify specific areas and government activity responsible for inspections. The field will expand as text is added or you can also use item 13. When removing any expanded text area, use delete key or backspace key, then click out of the text field for it to shrink after the text has been deleted. (See instructions for additional guidance or use of the fillable PDF.)

16. GOVERNMENT CONTRACTING ACTIVITY (GCA) AND POINT OF CONTACT (POC)

17. CERTIFICATION AND SIGNATURES

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. Upon digitally signing Item 17h, no changes can be made as the form will be locked.

18. REQUIRED DISTRIBUTION BY THE CERTIFYING OFFICIAL

9.0.0.2.20120627.2.874785 DD 254, "DoD Contract Security Classification Specification"

CurrentPage:
PageCount:
Select classification from drop-down list.: CUI
SerialNum:
a. Facility clearance level. Select one.: 1
b. Level of safeguarding for classified information/material required at contractor facility. Select one.: 4
Select for "original.": 0
Select for "original.": 0
Enter prime contract number.:
Select for "revised.": 0
Select for "revised.": 0
Enter subcontract number.:
Select for "final.": 0
Select for "final.": 0
Enter solicitation or other number.:
Enter due date in format YYYYMMDD.:
Enter date in format YYYYMMDD.: 20250115
Enter revision number.:
Enter date in format YYYYMMDD.:
Enter final specification.:
Enter date in format YYYYMMDD.:
Select for "no.": 1
Select for "no.": 1
Select for "no.": 0
Select for "no.": 0
Select for "yes.": 0
Select for "yes.": 0
Select for "yes.": 1
Select for "yes.": 1
Enter preceding contract number.:
Enter contractor's request date in format YYYYMMDD.:
Enter period.:
Enter typed name of certifying official (last, first, middle initial).:
Enter CAGE code of the prime contractor.: N/A
Enter cognizant security office(s) (Name, Address, ZIP Code, Telephone required; Email Address optional).: SSO PATRICK, Building 10989

1020 South Patrick Drive Patrick SFB, FL 32925-3516

Select to add row to locations.:
Select to remove last row from locations.:
Select to delete all signatures.:
Enter location(s).: AFTAC/HQ, Building 10989

1020 South Patrick Drive Patrick SFB, FL 32925-3516

Enter general unclassified description of this procurement.: FY26 R&D effort for the development and transfer of the on-premise cross domain system to an AWS cloud environment.
Select for "a. CONTRACTOR.": 0
Select for "a. CONTRACTOR.": 1
Select for "a. CONTRACTOR.": 1
Select for "f. OTHER AS NECESSARY.": 0
Select for "f. OTHER AS NECESSARY.": 0
Select for "f. OTHER AS NECESSARY.": 1
Select for "b. SUBCONTRACTOR.": 1
Select for "b. SUBCONTRACTOR.": 0
Select for "b. SUBCONTRACTOR.": 0
Select for "g. BE AUTHORIZED TO USE THE SERVICES OF DEFENSE TECHNICAL INFORMATION CENTER (DTIC) OR OTHER SECONDARY DISTRIBUTION CENTER.": 1
Select for "g. BE AUTHORIZED TO USE THE SERVICES OF DEFENSE TECHNICAL INFORMATION CENTER (DTIC) OR OTHER SECONDARY DISTRIBUTION CENTER.": 0
Select for "c. COGNIZANT SECURITY OFFICE FOR PRIME AND SUBCONTRACTOR.": 1
Select for "c. COGNIZANT SECURITY OFFICE FOR PRIME AND SUBCONTRACTOR.": 1
Select for "c. COGNIZANT SECURITY OFFICE FOR PRIME AND SUBCONTRACTOR.": 1
Select for "h. REQUIRE A COMSEC ACCOUNT.": 1
Select for "h. REQUIRE A COMSEC ACCOUNT.": 0
Select for "d. U.S. ACTIVITY RESPONSIBLE FOR OVERSEAS SECURITY ADMINISTRATION.": 1
Select for "d. U.S. ACTIVITY RESPONSIBLE FOR OVERSEAS SECURITY ADMINISTRATION.": 0
Select for "d. U.S. ACTIVITY RESPONSIBLE FOR OVERSEAS SECURITY ADMINISTRATION.": 0
Select for "i. HAVE A TEMPEST REQUIREMENT.": 0
Select for "i. HAVE A TEMPEST REQUIREMENT.": 1
Select for "e. NATIONAL INTELLIGENCE INFORMATION: - (1) Sensitive Compartmented Information (SCI).": 1
Select for "e. NATIONAL INTELLIGENCE INFORMATION: - (2) Non-SCI.": 1
Select for "j. HAVE OPERATIONS SECURITY (OPSEC) REQUIREMENTS.": 1
Select for "j. HAVE OPERATIONS SECURITY (OPSEC) REQUIREMENTS.": 1
Select for "k. BE AUTHORIZED TO USE DEFENSE COURIER SERVICE.": 0
Select for "k. BE AUTHORIZED TO USE DEFENSE COURIER SERVICE.": 0
Enter infomration for "other.": AFTAC Security/SOP

1020 South Patrick Drive, Bldg 10989 Patrick SFB, FL 32925-3516

Select for "e. ADMINISTRATIVE CONTRACTING OFFICER.": 0
Select for "e. ADMINISTRATIVE CONTRACTING OFFICER.": 1
Select for "l. RECEIVE, STORE, OR GENERATE CONTROLLED UNCLASSIFIED INFORMATION (CUI). .": 1
Select for "m.OTHER.": 0
Select for "direct.": 0
Select for ": 1
Enter specification for "through".: AFTAC/OPSEC, 1020 South Patrick Drive, Patrick SFB, FL 32940
Enter public release authority.: Contractor is to submit requests through the contracting officer for OPSEC program manager review and public release authorization.
Select to add signature.:
Select to remove last signature.:
text: Only applicable Annexes and revisions from AFTAC SCG Dated 14 Jun 24 when working in AFTAC Bldg. 10989.

Level of Access Required: SCI

ACCESS TO SENSITIVE COMPARTMENTED INFORMATION INSTRUCTIONS ATTACHMENT-30_Jan_24.PDF

PROTECTING FOR CONTROLLED UNCLASSIFIED INFORMATION.PDF

RELEASE OF NON-SENSITIVE COMPARTMENTED INFORMATION (NON-SCI) INTELLIGENCE_Apr24....PDF

BLOCK 13 DD FORM254 (MUST HAVE).PDF

(CUI) Contractor Incident Report Policy.PDF text:

Security Specialist text:

SSO

Click on this button to attach a file(s).:
rep: John S. Rose

Security Specialist rep: Patrick L. Reagan Special Security Officer

Enter signature.:
Explain and identify specific areas and government activity responsible for inspections.: Prior approval of the contracting activity is required for subcontracting. All DD FMs 254 prepared for a subcontract by the prime contract will be forwarded to the government contracting monitor and SSO Patrick for signature prior to award of the subcontract. Access to intelligence information will require special briefings and final U.S. Government Top Secret eligibility clearance with ICD 704 eligibility. Report adverse information as required by 32 CFR part 117.8.
Explain and identify specific areas and government activity responsible for inspections.: While operating on an Air Force installations, Industrial Security Reviews for collateral classified information will be conducted by AFTAC/IPO. SSO Patrick has exclusive security responsibility for all sensitive compartmented information and material under this contract and held at the government facility. Defense Counterintelligence and Security Agency retains cognizance over non-SCI material released to or developed under the contract and held at the contractor’s cleared facility.
Enter GCA name.: AFTAC/SDA
Enter AAC of the contracting office.: FA7022
Enter AAC of the contracting office.: FA7022
Enter address (include zip code).: AFTAC/SDA

1020 South Patrick Drive, Bldg. 10989 Patrick SFB, FL 32925-3516 Enter address (include zip code).: AMIC Det 2 OL/PKA (Patrick SFB) 1020 South Patrick Drive, Bldg. 10989 Patrick SFB, FL 32925-3516

Enter POC name.: Thomas E. Sedlock
Enter telephone number (include area code).: 3214948676
Enter email address.: thomas.sedlock.1@us.af.mil
Enter title.: Contracting Officer
Enter the date signed in format YYYYMMDD.:

File details come from the government source that posted it. Updated .