security

Derivative Classification Guide: Rules, Marking, And Examples

Derivative classification is the act of incorporating, paraphrasing, restating, or generating in a new form information that's already classified. Instead of originating new secrets, you're taking exi

Derivative Classification Guide: Rules, Marking, And Examples
In this story

Derivative classification is the act of incorporating, paraphrasing, restating, or generating in a new form information that's already classified. Instead of originating new secrets, you're taking existing classified source material and carrying that protection over into a new document. If you hold a security clearance, understanding how this process works keeps you compliant and protects sensitive government assets.

Unlike original classification—which is reserved for authorized officials who determine that information requires protection because unauthorized disclosure could damage national security—derivative classification is something many cleared professionals handle daily. You're building on established foundations rather than creating new ones. Getting it right demands strict adherence to source documents, accurate marking practices, and an understanding of your legal responsibilities.

Understanding the Core Concepts

When you create derivative content, you aren't guessing at sensitivity levels. You're relying entirely on existing source material. Three foundational elements govern this process: the source document, the Security Classification Guide (SCG), and the original classification authority.

The source document contains the classified information you're using. It could be an intelligence report, a technical manual, or an operational briefing. The Security Classification Guide serves as your primary roadmap. It's a carefully vetted document issued by an original classification authority that outlines what specific elements of a program, project, or topic are classified, at what level, and why.

You must trace every piece of derivative information back to an authorized source. If you include a fact in your report, you need to know precisely where that fact came from and whether it remains classified. Guessing isn't an option.

The Derivative Classification Process

Executing derivative classification correctly follows a precise sequence. Skipping steps or taking shortcuts leads to unauthorized disclosures or improper marking, both of which trigger security violations.

First, you analyze your source material. You isolate the specific facts, figures, or concepts you intend to use. Next, you consult the applicable Security Classification Guide to confirm the current classification level. Classifications change, and an older document might contain outdated instructions.

Once you verify the classification, you draft your new content. You incorporate the information through paraphrasing, summarizing, or direct quoting. Even when you completely rewrite a paragraph in your own words, the underlying classified fact remains classified. Changing the sentence structure doesn't strip away the classification requirement.

Finally, you apply proper markings. Every newly created document or product containing derivative information must clearly display what is classified, who authorized the original classification, and where the information came from.

Proper Marking and Attribution Requirements

Markings are the most visible part of derivative classification. If markings are missing or incorrect, readers won't know how to handle the material safely.

Every derivatively classified document requires a Classified By line. This doesn't name you as the person who wrote the report; it identifies the original classification authority or points to the primary source document. You also need a Reason line if you're pulling from an older source, though modern guides often streamline this by referencing the specific SCG item number.

The Declassify On line tells handlers when the information loses its sensitive status. You pull this date directly from your source document or the governing security guide. Never make up a declassification date or leave it blank when source data dictates a specific timeline.

Internal markings matter just as much as cover pages. Paragraphs containing classified information need proper portion markings—such as (C) for Confidential, (S) for Secret, or (TS) for Top Secret—placed directly at the beginning of the relevant paragraph or heading. Unclassified paragraphs get marked with a clear (U).

Common Mistakes to Avoid

Even experienced cleared personnel make errors when handling derivative materials. Recognizing these pitfalls helps you maintain compliance.

  • Classification by association: Combining several unclassified facts doesn't automatically create classified information unless an SCG explicitly states that the specific combination is sensitive. Don't over-classify out of an abundance of caution.
  • Using outdated sources: Relying on a five-year-old report without checking the current security guide often results in using incorrect classification levels or carrying forward information that has already been declassified.
  • Missing portion markings: Forgetting to mark individual paragraphs leaves downstream readers guessing which parts of a document require protection and which parts are open.
  • Failing to cite the source: Every derivative statement must tie back to an identifiable source document or guide. Vague references like "sources tell us" have no place in classified environments.

Frequently Asked Questions

What is the difference between original and derivative classification?

Original classification is the initial determination by authorized government officials that specific information requires protection in the interest of national security. Derivative classification involves taking that already classified information, incorporating it into a new document, and ensuring it retains its protected status based on existing guides.

Can unclassified information become classified derivatively?

Yes, under specific circumstances known as compilation or aggregation. If an SCG states that bringing several unclassified items together reveals a new, sensitive vulnerability or capability, the resulting compilation becomes classified.

What should I do if my source document lacks proper markings?

Stop immediately and contact your security officer or the document's point of contact. You cannot derivatively classify information from a poorly marked or ambiguous source until you verify its exact status through official channels.

Do I need special training to perform derivative classification?

Yes. Anyone who handles classified information and generates derivative products must complete formal training, such as the CDSE Derivative Classification training provided by the Defense Counterintelligence and Security Agency, typically required every two years.

SB

Written by

Samuel Baker

Samuel Baker approaches each story with intellectual curiosity and a commitment to fairness, earning the trust of readers and sources alike.

More from security