RTP_SEC_AttchC-8_Security_Test_Plan_TemplateV2.0.docx

DOCX document 2 MB Posted

Attached to
NGA - Boosting Innovative GEOINT - Science & Technology Broad Agency Announcement (BIG-ST BAA)
Solicitation number
HM047623BAA0001
Issued by

About this file

This is a Security Test Plan Template document for use in federal contracting proposals submitted to the National Geospatial Intelligence Agency (NGA) under the Boosting Innovative GEOINT-Science & Technology (BIG-ST) Broad Agency Announcement.

The template provides a standardized framework for proposers to develop comprehensive security testing plans as part of their technical submissions. It is designed to guide contractors in documenting security testing methodologies, procedures, and validation approaches for GEOINT-related research and technology solutions. The template serves as an appendix or attachment reference within the broader BIG-ST BAA solicitation, which encompasses multiple technical domains including Foundational GEOINT, Advanced Phenomenologies, and Analytic Technologies. This document does not specify particular products or services required, response deadlines, or pricing terms; rather, it functions as a planning tool to ensure proposers address security considerations systematically in their proposals. Contractors responding to active or future Topic Calls under the BIG-ST BAA (Solicitation Number HM047623BAA0001) would utilize this template to demonstrate their approach to security testing and validation of proposed solutions.

View the file

Other files

File Type Posted
LASER_CDRL_A004_Technical Plans.pdf PDF
LASER_CDRL_A003_Software Deliverables.pdf PDF
BIGST-BAA_T7_LASER_20260730.pdf PDF
Research and Technology Plan_20260730.pdf PDF
RTP_SEC_AttchC-5-PWS_SOW Unclass only no CUI Security Language vSep 2025.docx DOCX document
Provisions and Clauses_HM047623BAA0001_20260622.pdf PDF
BIGST_BAA_HM047623BAA00001_GeneralSolicitation_REV4_20260730.pdf PDF
LASER_CDRL_A002_Technical_Reports.pdf PDF
LASER_CDRL_A001_Kick-off.pdf PDF
RTP_SEC_AttchC-7_PPIP_Template.docx DOCX document
RTP_SEC_AttchC-4-PWS_SOW Top Secret Security Language vSep 2025.docx DOCX document
RTP_SEC_AttchC-6-PWS_SOW Unclass w CUI Security Language vSep 2025.docx DOCX document
RTP_SEC_AttchC-3-PWS_SOW Secret Security Language vSep 2025.docx DOCX document
RTP_SEC_AttchC-2-PWS_SOW SCI Security Language vSep 2025.docx DOCX document
RTP_SEC_AttchC-1-PWS_SOW SCI Security Language vSep 2025 w Special_corrected.docx DOCX document
APPENDIX 5 Grants Coops_version3.pdf PDF
APPENDIX 5 Grants Coops_version2.pdf PDF
BIGST_BAA_HM047623BAA0001_GeneralSolicitation_REV2_20250402.pdf PDF
BIGST_BAA_HM047623BAA0001_Provisions_Clauses_20231115.pdf PDF
NGAI 8400.4.pdf PDF
APPENDIX 5 Grants Coops.docx DOCX document
APPENDIX 2 Proposal Template.docx DOCX document
APPENDIX 1 Abstract Template.docx DOCX document
BIGST_BAA_HM047623BAA00001_GeneralSolicitation_REV3_20250425.pdf PDF
BIGST_BAA_HM047623BAA0001_Provisions_Clauses_20250402.pdf PDF
BIGST_BAA_HM047623BAA0001_GeneralSolicitation_REV2_20250402.pdf PDF
Provisions_Clauses_BIGST BAA_HM047623BAA0001_20241220.pdf PDF
BIGST_BAA_GeneralSolicitation_REV1_20241220.docx DOCX document
Research and Technology Protection_BIG-ST BAA_20241220.docx DOCX document
BIGST-BAA_Topic_3_VLBIG_Rev1_20240522.docx DOCX document
BIGST-BAA_Topic_3_VLBIG_20240508.docx DOCX document
BIGST_BAA_GeneralSolicitation.docx DOCX document
BIGST_BAA_Topic 01_GFM_Rev1_20240124.docx DOCX document
BIGST_BAA_GeneralSolicitation.docx DOCX document
BIGST_BAA_GeneralSolicitation.docx DOCX document
BIGST_BAA_Topic 01_GFM.docx DOCX document
Provisions_Clauses_BIGST BAA_HM047623BAA0001.pdf PDF
Show all 37

On GovTribe

Work with this file

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

Text version

UNCLASSIFIED

CLASSIFY or CONTROL and MARK APPROPRIATELY WHEN FILLED OUT/COMPLETED If classified, plan MUST be created & transmitted on a Classified Information System.

(U) TEST EVENT NAME

Date of Experiment:

Research & Development Division:

Program Manager:

Prepared by:

(U) This sample Test Plan template is intended to inform Program Managers of example best practices that may be tailored for program-specific testing requirements. These specific requirements will dictate which topics and questions are applicable and potentially introduce new ones. This document is not a checklist, but rather is intended to account for a wide range of scenarios in order to formulate appropriate research and technology protection during the testing process.

Contents

1.(U) Introduction3
1.0.1 (U) Background3
1.0.2 (U) Goals3
1.0.3 (U) Testing and Evaluation (T&E) Event Overview3
1.0.4 (U) Execution Schedule3
1.0.5 (U) Personnel3
2.(U) Logistics4
2.0.1 (U) Test Site Location and Set-up4
2.0.2 (U) Field Communications4
2.0.3 (U) Test Equipment and Instrumentation4
3.(U) Security Considerations4
3.0.1 (U) Operational Security (OPSEC)4
3.0.2 (U) Safety Considerations4
3.0.3 (U) Data Classification5
3.0.4 (U) Security Classification Guides5
3.0.5 (U) Data Protection and Delivery5
3.0.6 (U) Data Dissemination5
3.0.7 (U) Personal Electronic Device Policy5
3.0.8 (U) Physical Access to Systems and Information5
3.0.9 (U) Security Points of Contacts5
3.0.10 (U) Document and Media Destruction5

1. (U) Introduction

1.0.1 (U) Background Enter Text Here Guidance: What is your program seeking to accomplish and how will the findings be beneficial to NGA’s overall goals?

1.0.2 (U) Goals Enter Text Here Guidance: What are the objectives for this testing event?

1.0.3 (U) Testing and Evaluation (T&E) Event Overview Enter Text Here Guidance: Provide a brief description about what is being evaluated, when and where the testing will occur, and whether any sub-experiments will be performed. Provide title and overall classification of the T&E event

1.0.4 (U) Execution Schedule Enter Text Here Guidance: Provide a test event schedule that includes travel, logistics, set-up, execution, and tear-down of activities by task and location.

1.0.5 (U) Personnel

Guidance: Identify key personnel associated with the testing event in Table 1.0.5-1

(U) Table 1.0.5-1 Testing Event Personnel

Title/Role
Name
Contact Info
Citizenship

2. (U) Logistics

2.0.1 (U) Test Site Location and Set-up Enter Text Here Guidance: Please provide a description of the test site and all supporting documentation (e.g., maps, equipment details, access rosters, surrounding areas of interest) surrounding test site)

2.0.2 (U) Field Communications Enter Text Here Guidance: Provide all communications plans relevant to the event.

2.0.3 (U) Test Equipment and Instrumentation Enter Text Here Guidance: Identify equipment that will be used, along with the correlated mode of transfer, custodial POC, and storage location during testing in Table 3.0.4-1

(U) Table 2.0.3-1 Testing Event Equipment

Category
Name
Transfer Method
Custodial POC
Storage Location

2.0.4 (U) Contingency Planning

Guidance: Provide emergency action plans to include contacts and procedures relevant to the testing event.

3. (U) Security Considerations

3.0.1 (U) Operational Security (OPSEC) Enter Text Here Guidance: Describe how OPSEC best practices will be integrated at the testing site. Identify all of the essential technology elements being tested and evaluated (e.g., Critical Technology Information, Critical Program Information, and Critical Technology Elements), and the safeguarding measures that will be implemented.

3.0.2 (U) Safety Considerations Enter Text Here Guidance: Describe safety instructions for participants.

3.0.3 (U) Data Classification Enter Text Here Guidance: Please provide the data sets and security classification that will be utilized in this event.

3.0.4 (U) Security Classification Guides Enter Text Here Guidance: Please list all relevant security classification guidance associated with the program and T&E event.

3.0.5 (U) Data Protection and Delivery Enter Text Here Guidance: Discuss your program data protection requirements – how will program data will be transferred to and from the testing site? By what means will the data be stored? Where will it be stored?

3.0.6 (U) Data Dissemination Enter Text Here Guidance: Describe where and how the data utilized and collected will be stored, processed, and transmitted to relevant stakeholders for the event.

3.0.7 (U) Personal Electronic Device Policy Enter Text Here Guidance: Describe what policies are in place regarding the use of personal electronic devices in the vicinity of test sites, if any.

3.0.8 (U) Physical Access to Systems and Information Enter Text Here Guidance: Describe the measures that are in place to prevent physical access to information and systems by unauthorized personnel, including physical document and electronic media storage, container type, and access controls.

3.0.9 (U) Security Points of Contacts Enter Text Here Guidance: Please provide security point of contacts for the security and counterintelligence personnel embedded at the test site.

3.0.10 (U) Document and Media Destruction

Guidance: Describe the measures that will be implemented regarding physical document and media destruction (reference DoDI 5200.48, NIST SP 800-88, and Section 2002.14 of Title 32, CFR).

Other considerations:

LOGISTICS:

Transportation planning (law enforcement coordination, routes, drivers, courier letters, courier procedures, airline procedures, as applicable)

Site map?

OPSEC:

OPSEC Statement/Cover Story (what do you tell the media when they show up at your test site)?

What are the critical indicators associated with the test?

COMMUNICATIONS: Maybe under 3.0.6 or 2.0.2?

Is there a description (or better yet, a network diagram/OV-1 of communication links involved in testing, will data be transmitted over GWAN, commercial, satellite, encrypted, unencrypted, etc.)

COUNTERINTELLIGENCE:

Which MDCO is responsible? Will organic CI be available? What support is provided/required?

TRAINING, BRIEFINGS, ETC. Who gives security, safety, CI, etc.

PLATFORMS: (maybe under 2.0.03?)

What platforms/vehicles?

AIRWORTHINESS -who is responsible?

UNCLASSIFIED

image1.png

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