A clear Derived From line connects classified information to the exact guidance that supports its classification. Learn how source citations and, when applicable, an RFC create a reliable trail for review—because a document title alone may not show which guidance applies.

Multiple Choice

What should be included in the Derived From line for a fact sourced from guidance?

In derivative classification, the Derived From line is all about linking the fact to the exact guidance that justifies its classification. It should provide a citation to the source and, if applicable, reference the RFC that ties the fact to that guidance. This creates a clear trail showing which document and which part of its guidance were used to derive the classification, so others can verify the basis for the decision. Including only the document title or just the classification level or date won’t establish that link to the governing guidance, so they don’t meet the requirement. By adding the citation and, when relevant, the RFC, you ensure proper traceability and justification for the derivative.

Why the “Derived From” Line Needs a Clear Citation

A classification decision should be traceable. When information is marked as classified because it comes from guidance, the “Derived From” line needs to show which source supports that decision—not merely name a document or repeat a classification level. A clear citation connects the information to the specific guidance used and, when applicable, to the related RFC.

That link matters because classification markings are not guesses. They reflect decisions made under established authority. Anyone reviewing a marked document should be able to follow the trail: from the information, to the guidance that applies, and to the citation that identifies where the guidance can be found.

A short line with a serious job

Derivative classification occurs when someone applies existing classification guidance to information in a new document or material. The person marking the new material doesn’t create a new classification decision. Instead, they rely on an existing source, such as a security classification guide or a previously classified document, and apply the relevant instructions.

The “Derived From” line records that source. Its job is more specific than simply naming a file or publication. It should provide a citation that ties the information to the source’s guidance. If an RFC applies to that guidance, the line should refer to it as well.

Think of the line as a map reference. “The map is in the office” won’t help much when someone needs to find a particular road. A useful reference points to the right map and the relevant location on it. In the same way, a citation should make it possible to locate the guidance that supports the classification.

What a citation adds

A document title identifies a source, but it may not show which portion of that source governs a particular fact. A citation can provide that extra detail—for example, by identifying the relevant section, paragraph, page, or other locator used by the source. The precise format depends on the applicable instructions and the source itself.

That detail helps reviewers confirm that the classification was derived from the right guidance. It also helps people who later update or reuse the material. If the source changes, they can check whether the original guidance still applies. If a question arises about a marking, the citation gives them a concrete place to start.

This isn’t paperwork for its own sake. A strong reference supports accountability. It shows the basis for a decision without requiring every reader to reconstruct it from scratch.

Where the RFC fits

When applicable, the Derived From line should also refer to the RFC that connects the information to the governing guidance. The citation and the RFC serve the same larger purpose: they help establish the basis for the classification. They are not interchangeable with a bare document title or a classification label.

The term “RFC” may have a defined meaning and format within the governing process or system. Follow the applicable instructions rather than guessing at an expansion or creating a reference that isn’t supported by the source. The important point is functional: where an RFC is required or relevant, include it so the reader can trace the fact to the guidance behind its classification.

A useful reference answers a practical question: What guidance was used to classify this information, and where can that guidance be found? If the line cannot help answer that, it may not provide enough traceability.

Why a title alone falls short

Suppose a source document contains several sections, each covering different types of information. Listing only the title may leave a reviewer wondering which section supports the classification of the fact at hand. The title points to the document, but not necessarily to the rule that applies.

The same problem arises when a document has multiple versions or when guidance is updated over time. A precise citation helps distinguish the relevant passage from other material. It reduces guesswork and makes it easier to verify that the classification was derived from current, applicable guidance.

A date alone has a similar limitation. It can help identify a source version, but it doesn’t explain which guidance supports the classification. And a classification level alone tells the reader how the information is marked—not why that marking was assigned. Each detail can be useful in context, but none replaces the source citation and, when applicable, the RFC.

Traceability supports sound decisions

Clear sourcing matters throughout the life of classified information. A document may be copied, combined with other material, excerpted into a briefing, or used as the basis for a later product. Each transfer can create opportunities for errors: a marking may be lost, a citation may be shortened too far, or a source may be mistaken for a different one.

A complete Derived From line gives later reviewers a way to check the chain of authority. They can compare the marked information with the cited guidance and confirm that the classification remains supported. That’s especially useful when information appears in a new context, where its meaning or level of detail may differ from the original source.

Good traceability also supports careful handling. People need to know not only that information is classified, but which guidance governs it. When that basis is visible, decisions are easier to review and less likely to depend on memory or assumption.

Keep the source trail intact

When writing or reviewing a Derived From line, focus on whether it points clearly to the guidance used. Check that the citation identifies the source and the relevant location, and include the related RFC when it applies. Then make sure the reference follows the marking instructions for the document or system in use.

If the source is unclear, incomplete, or difficult to locate, don’t fill the gaps with a guess. Consult the applicable classification guidance or the appropriate authority. A tidy-looking line is not enough if it fails to support verification.

The principle is simple: a derivative classification should carry its basis with it. A citation makes the connection visible; an applicable RFC helps preserve that connection to the governing guidance. Together, they give reviewers a clear trail from the classified fact back to the source that justifies its marking.