Derivative classification is the process of incorporating, paraphrasing, restating, or generating in a new form information that is already classified. Instead of originating a new security classification, you rely on an existing authorized source document or classification guide to protect sensitive government or defense information.
If you handle national security data, defense contracts, or federal agency records, understanding this process is essential. Failing to follow correct protocols can lead to security infractions, compromised operations, and severe professional penalties.
What Is Derivative Classification?
At its core, derivative classification extends the protection of existing secrets to new documents. When you write a report, build a briefing, or draft a memo that uses classified source material, you don't get to decide the security level on your own. You must trace the information back to an authorized classification authority.
The foundational rule is simple: if it comes from a classified source, it stays classified. Every fact, figure, and assertion pulled from a classified document carries its protection requirements over to your new work. To understand the bigger picture, we recommend the detailed report by The New York Times.
- Original Classification: The initial decision by an authorized official that specific information warrants protection against unauthorized disclosure because it could damage national security.
- Derivative Classification: The subsequent act of identifying, marking, and protecting new material that incorporates, paraphrases, or restates that originally classified data.
You can learn more about federal accountability and information controls through oversight bodies like the Government Accountability Office.
Core Responsibilities of a Derogatory Classifier
When you generate derivative materials, you take on specific legal and operational responsibilities. You aren't just writing content; you act as a steward of protected data.
Identifying Source Material
You must accurately identify every piece of classified information you pull into your draft. This requires keeping detailed notes on your research sources. If you cannot point to an authorized document or security classification guide (SCG) that justifies the classification, you cannot include that material.
Carrying Forward Markings
Your primary job is transmission of context. When you pull data from a source, you must ensure your new product reflects:
- The correct classification level (Confidential, Secret, or Top Secret).
- The identity of the original classification authority.
- Clear downgrading and declassification instructions based on the source guide.
Avoiding "Classification by Association"
A common error involves grouping unclassified facts in a way that accidentally reveals a classified whole. For example, listing individual unclassified parts suppliers might be harmless, but publishing a comprehensive schedule linking all suppliers to a specific sensitive delivery date creates a classified vulnerability. You must evaluate the context of your combined statements.
Step-by-Step Derivative Process
Executing this workflow correctly requires a disciplined, repeatable routine. Follow these steps whenever you draft documents containing sensitive material.
- Consult Authorized Sources: Open your project's approved Security Classification Guide (SCG) or gather your authorized source documents before you write a single sentence.
- Extract and Verify: As you write, verify that every sensitive detail maps directly to an explicit entry in your source documentation. Don't guess or extrapolate.
- Draft with Precision: Paraphrase or incorporate facts accurately while maintaining their original meaning without embellishing or exaggerating the scope.
- Apply Required Markings: Insert proper banner markings at the top and bottom of pages, portion marks ([C], [S], [TS]) at the beginning of paragraphs, and a complete derivative authority block on the cover or first page.
- Conduct Final Review: Have a trained security representative or peer review your draft to confirm that all markings match the source guidance.
Common Mistakes to Avoid
Even experienced professionals stumble when managing sensitive information under tight deadlines. Watch out for these frequent pitfalls.
- Over-Classification: Marking unclassified information as classified just to be safe. This wastes resources and violates federal guidelines.
- Vague Authority Citations: Writing "Derived from Multiple Sources" without listing specific document titles, dates, and agencies in your reference block.
- Ignoring Portion Markings: Forgetting to label individual paragraphs, leaving reviewers guessing which specific sentences contain protected data.
- Relying on Memory: Drafting sections from memory rather than verifying facts against current classification guides, which leads to outdated or incorrect security markings.
Frequently Asked Questions
Who is authorized to perform derivative classification?
Any cleared federal employee, contractor, or military personnel who has completed mandatory training and has direct access to valid source documents or security classification guides can create derivative products. You don't need original classification authority to do this.
What is a Security Classification Guide (SCG)?
An SCG is an administrative policy document issued by an original classification authority. It provides specific instructions on what elements of a particular program, project, or system must be protected, what classification level applies, and when the information can be declassified.
What happens if I make a mistake on classification markings?
Errors can lead to security infractions or security violations depending on the severity. Minor administrative mistakes require correction and retraining, while unauthorized disclosures of classified data can trigger formal investigations, loss of security clearances, and potential legal action.
Can unclassified information become classified through derivative work?
Yes. If you combine several unclassified items of information in a way that reveals a new classified vulnerability or operational capability, the resulting compilation must be protected at the appropriate classification level.
