Home Agencies NASA

Agencies · NASA

NASA CUI obligations, translated from the agreement you signed.

NPR 2810.7 directs NASA to apply NIST SP 800-171 in agreements protecting NASA CUI on nonfederal systems. What that means for you is set by your contract's clauses, and that's where our work starts.

What the NASA lane involves

Questions contractors ask us

Does every NASA contract require NIST SP 800-171?

No. NPR 2810.7 directs NASA to apply NIST SP 800-171 in agreements that protect NASA CUI on nonfederal systems, but the obligation that binds you is the one written into your specific contract, grant, or agreement. Step one is always reading the instrument.

We're a research institution, not a defense contractor. Does this still apply?

If your agreement involves NASA CUI on your systems, yes. The framework applies the same way to a manufacturer, a university, or a software shop. Research environments often have the hardest boundary problems (shared infrastructure, collaboration tools, student access), so discovery and scoping are the most useful first step.

Can our existing DoD-oriented 800-171 program cover NASA work?

Largely, yes. The controls come from the same standard. The deltas are the instrument's specific terms, any NASA-specific reporting or marking expectations, and how the agreement expects you to demonstrate implementation. The same control system then serves NASA as another assurance lane.

NASA lane

Turn the clause into a program.

Tell us what your NASA agreement says, or send the clause list, and a practitioner will map the obligation and the shortest path to meeting it. Or email rj@indirectit.com directly.