to move, Enter to open, Esc to close. Try 3.5.3, AC.L2-3.1.1, MFA or unmarked.

03.12.05Information Exchange in Rev. 3

New in Revision 3 — no Revision 2 equivalent. Nothing in NIST SP 800-171 Rev. 2 maps onto this number, so it has no Rev. 2 page and no side-by-side; the Rev. 3 text is below in full. It carries organization-defined parameters.

Status as of 2026-09-08

Rev. 2 is what a contract requires today. DFARS 252.204-7012 and the CMMC rule at 32 CFR 170 point at NIST SP 800-171 Rev. 2, and a standing DoD class deviation keeps it there. NIST has published Rev. 3, but publishing a revision does not change an obligation. A move to Rev. 3 would arrive through the Department's reform process and formal rulemaking, a change to that deviation or an amendment to the rule, not through publication. The Department has published its organization-defined parameter values for Rev. 3 in preparation; that is groundwork, not adoption.

The requirement

Rev. 3 · not adopted 03.12.05 Information Exchange

a. Approve and manage the exchange of CUI between the system and other systems using [Selection (one or more): interconnection security agreements; information exchange security agreements; memoranda of understanding or agreement; service-level agreements; user agreements; non-disclosure agreements; other types of agreements].

b. Document interface characteristics, security requirements, and responsibilities for each system as part of the exchange agreements.

c. Review and update the exchange agreements [Assignment: organization-defined frequency].

NIST SP 800-171 Rev. 3, verbatim, with organization-defined blanks highlighted. Rev. 2 has no counterpart to place beside it.

Determination statements

What an assessor would check under NIST SP 800-171A Rev. 3. 7 statements, each one answered yes or no.

  1. 03.12.05.a[01] the exchange of CUI between the system and other systems is approved using <A.03.12.05.ODP[01]: SELECTED PARAMETER VALUES>.
  2. 03.12.05.a[02] the exchange of CUI between the system and other systems is managed using <A.03.12.05.ODP[01]: SELECTED PARAMETER VALUES>.
  3. 03.12.05.b[01] interface characteristics for each system are documented as part of the exchange agreements.
  4. 03.12.05.b[02] security requirements for each system are documented as part of the exchange agreements.
  5. 03.12.05.b[03] responsibilities for each system are documented as part of the exchange agreements.
  6. 03.12.05.c[01] exchange agreements are reviewed <A.03.12.05.ODP[02]: frequency>.
  7. 03.12.05.c[02] exchange agreements are updated <A.03.12.05.ODP[02]: frequency>.

NIST SP 800-171A Rev. 3, verbatim.

Organization-defined parameters

Blanks the organization fills in. Defining each value is itself a determination in 800-171A Rev. 3.

  • A.03.12.05.ODP[01] one or more of the following PARAMETER VALUES are selected: {interconnection security agreements; information exchange security agreements; memoranda of understanding or agreement; service-level agreements; user agreements; non-disclosure agreements; other types of agreements}.
  • A.03.12.05.ODP[02] the frequency at which to review and update agreements is defined.

What NIST says

  • New security requirement based on CA-02(01) (SP 800-53, Revision 5)
  • Added new ODP: selection of one or more (interconnection security agreements, information exchange agreements, memoranda of understanding or agreement, service-level agreements, user agreements, non-disclosure agreements, or other types of agreements)
  • Added new ODP: frequency to review and update agreements

NIST, SP 800-171 Rev. 2 to Rev. 3 change analysis, class “New requirement”. At adoption, Bedrock files this under “New”.

NIST's Rev. 3 discussion for 03.12.05

Information exchange applies to information exchanges between two or more systems, both internal and external to the organization. Organizations consider the risks related to new or increased threats that may be introduced when systems exchange information with other systems that may have different security requirements or policies. The types of agreements selected are based on factors such as the relationship between the organizations exchanging information (e.g., government to government, business to business, government to business, government or business, or government or business to individual) and the level of access to the organizational system by users of the other system. The types of agreements can include information exchange security agreements, interconnection security agreements, memoranda of understanding or agreement, service-level agreements, or other types of agreements. Organizations may incorporate agreement information into formal contracts, especially for information exchanges established between federal agencies and nonfederal organizations (e.g., service providers, contractors, system developers, and system integrators). The types of information contained in exchange agreements include the interface characteristics, security requirements, controls, and responsibilities for each system.

Security Assessment and Monitoring in Rev. 3

The active CA requirements in Rev. 3. Those with a Rev. 2 predecessor link to that comparison; those marked new have their own page.

All Security Assessment and Monitoring requirements in Rev. 2

What this means for you now

Nothing. Until a class deviation or a published rule adopts Rev. 3, no assessor asks about 03.12.05 and SPRS has no score for it. If you already do what it describes, note where the evidence lives and what value you use for the parameters above; that costs nothing and answers the question later.

Bedrock CMMC carries the Rev. 3 catalog beside your Rev. 2 package, so the day adoption lands the new requirements are a to-do list, not a surprise.

Where this page's facts come from
Rev. 3 03.12.05 text, determination statements, parameters, class and note
bedrock-cmmc-api@89b8e8e:docs/reference/nist-800-171-rev3/normalized/rev3.json#requirements[]