home/glossary/interconnected system

interconnected system

nounid 163539·updated Aug 30, 2026
verified

A configuration of two or more distinct IT systems—spanning organizational, network, or authorization boundaries—that are directly linked for the purpose of sharing data, resources, or services. What distinguishes it from a single system with internal components is the presence of a cross-boundary connection that introduces shared risk: each party's security and privacy posture can affect the other's, which is why authority documents treat the connection itself as a security object requiring its own governance instruments (interconnection security agreements, architectural controls, and joint authorization). In practice, standards bodies use the term to frame obligations such as mandating specific architectural constraints, documenting mutual protection requirements, and maintaining the confidentiality, integrity, and availability of information as it moves across the join.

MWE

Source

document
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systems
found in
proposed during MWE review
element
e0180
proposed by
dorianc@moxywolf.com
discovery
ManualCuration
between interconnected systems. Organizations consider mandating specific architectural solutions when required to enforce specificthe sentence this term was read in
Where the definition came fromawaiting curator confirmation

generalized from a web lookup of the quoted expression at proposal time Verdict: term of art.

A definition generalized from search results is a draft to react to, not provenance. Confirm it against an authority document before this term is verified.

A web lookup ran when this term was proposed

A configuration of two or more distinct IT systems—spanning organizational, network, or authorization boundaries—that are directly linked for the purpose of sharing data, resources, or services. What distinguishes it from a single system with internal components is the presence of a cross-boundary connection that introduces shared risk: each party's security and privacy posture can affect the other's, which is why authority documents treat the connection itself as a security object requiring its own governance instruments (interconnection security agreements, architectural controls, and joint authorization). In practice, standards bodies use the term to frame obligations such as mandating specific architectural constraints, documenting mutual protection requirements, and maintaining the confidentiality, integrity, and availability of information as it moves across the join.

Advisory only. A term this product ships is defined by an authority document, not by a search result.

Proposed during multiword review of this document in the CKI mapping queue.

Attested in

NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systems3 citations · 3 confirmed by a reviewer · observed 2026-09-01 under anchor/0.9/36451/2026-09-01
03.01.03 ¶ 303.01.03 ¶ 43.2.2 ¶ 82

Classifications

Entity Type

System92%llm-generatedllm:claude-haiku-4-5

Sensitivity

Regulated85%llm-generatedllm:claude-haiku-4-5

Information Class

Cui72%llm-generatedllm:claude-haiku-4-5

Variants

plural
interconnected systems
possessive
interconnected system's
pluralpossessive
interconnected systems'

Framework definitions

NIST SP 800-171r31 senseview framework →
§1 · attested_usage_reviewer_confirmed
No definition is given in NIST SP 800-171r3. The term is attested in use at 3 citations in that document; a definition is pending curation.
Increment 2: attested in 800-171r3 without a glossary definition.
Legacy lexicon import1 senseview framework →
§1 · web_lookup_draft
A configuration of two or more distinct IT systems—spanning organizational, network, or authorization boundaries—that are directly linked for the purpose of sharing data, resources, or services. What distinguishes it from a single system with internal components is the presence of a cross-boundary connection that introduces shared risk: each party's security and privacy posture can affect the other's, which is why authority documents treat the connection itself as a security object requiring its own governance instruments (interconnection security agreements, architectural controls, and joint authorization). In practice, standards bodies use the term to frame obligations such as mandating specific architectural constraints, documenting mutual protection requirements, and maintaining the confidentiality, integrity, and availability of information as it moves across the join.
DR-088 backfill from the noun definition column

Outgoing relationships

No outgoing triples
This term is not the subject of any RDF-style relationship yet.

Incoming relationships

No incoming triples
No other term currently asserts a relationship to this one.