Secure Tasking of Commercial Assets

# Q&A Changes Summary **New Answer Added:** - **Q1 (Direct-to-Phase II):** Clarified that this topic does NOT support Direct-to-Phase II; proposers must complete standard Phase I→Phase II process. **Status:** Q7 appears truncated in both versions (cuts off mid-question), suggesting it remains pending or incomplete in the updated Q&A. **No substantive changes** to Q2–Q6; all other answers remain identical.

**Summary of Q&A Changes:** **New Question Added:** - Q1: "Direct to Phase II" eligibility path for companies with existing global infrastructure matching topic requirements (answer not provided in update). **Renumbering:** All previous questions shifted down by one number (Q1→Q2, Q2→Q3, etc.) due to new Q1 insertion. **Key Clarifications Retained:** - Blockchain not required; non-ledger cryptographic solutions acceptable (Q2) - Ground/cloud endpoint focus; in-orbit modifications not feasible (Q3) - DoD PKI integration expected; multiple Phase II awards possible (Q4) - 90% metric covers full order-to-delivery pipeline; direct-to-satellite tasking is Phase III goal (Q5) - No named commercial provider preferences; performers fund own commercial relationships (Q5) **Incomplete Answer:** - Q7 (technical constraints: OS, memory, CPU, bandwidth; E2E data return expectations) appears truncated with no substantive answer provided.

No material changes detected. The PREVIOUS and UPDATED Q&A sections are identical across all six questions and answers. All content, including Q1–Q6 and their corresponding responses, remains unchanged.

**Summary of Q&A Changes:** One new question added (Q1) addressing hardware-rooted device identity with ML-DSA signatures as a non-blockchain alternative for tasking authenticity/integrity integrated with DoD PKI. Previous Q&As (Q2-Q6) were renumbered but answers remain substantively unchanged. No new budget details, timeline clarifications, or technical constraint specifications were added beyond the existing guidance on NIST/DoD security standards compliance.

# Q&A Changes Summary **Major additions:** - **Q1 answered:** Clarified tasking APIs (REST, HTTPS, SFTP); confirmed satellites cannot be modified in-orbit; security must focus on ground/cloud endpoints; Navy may use both direct access and commercial/cloud interfaces. - **Q2 answered:** Navy IL-5/IL-6 ATO path confirmed; Phase I/II should analyze (not implement) post-quantum cryptography with CNSA 2.0 alignment; compliance baselines set (NIST SP 800-171 for CUI, 800-53/CNSSI 1253 for Secret, FIPS 140-3); multiple Phase II awards possible; MTC-A/X transition engagement expected in Phase I/II. - **Q3 answered:** Blockchain not required; DoD PKI integration preferred; 90% reduction measured against full 14-day pipeline (not just handshake); direct-to-satellite tasking is Phase III stretch goal; no preferred vendors specified; no guaranteed Government API access in Phase II.

**Changes to Q&A:** New Q1 added asking about current commercial satellite tasking network architecture, vulnerable points, whether in-orbit equipment updates are possible, and whether Navy access is direct or via commercial cloud interfaces—fundamentally clarifying the technical and operational baseline for the solution. All other questions (previously Q1-Q4) renumbered to Q2-Q5 with no answer changes.

Added 2 new detailed Q&As with 5 sub-questions each. Q1 addresses cloud/ATO requirements, post-quantum cryptography implementation scope, security compliance baselines, award quantities, and Phase III transition sponsor identification. Q2 clarifies blockchain requirement status, 90% reduction metric definition, direct-to-satellite tasking scope, commercial provider integration, and Government support for Phase II commercial access.

Status changed from Pre-Release to Open

Added Q1 on Phase 1 funding limits with link to DON submission instructions. Updated Q2 (previously unanswered) with technical constraints: DoD/NIST security standards required, efficient CPU/memory/bandwidth needed for low latency, E2E channel must securely transmit tasking requests and satellite data bidirectionally to Navy, operator, and satellite.

# Summary This Q&A addresses technical constraints and system architecture for a satellite tasking operation, specifically clarifying hardware/software limitations and whether the end-to-end channel handles both data transmission and downlink, and whether it operates ground-to-ground or extends to the satellite itself.

New opportunity: Secure Tasking of Commercial Assets