What Is a Security Classification Guide: The Derivative-Classification Engine

A security classification guide is an official document that tells cleared personnel exactly what information in a specific program, system, or weapon is classified, at what level, and why—so derivative classifiers can mark new documents consistently without re-adjudicating the original decision. It converts a single original classification authority's judgment into repeatable rules for everyone downstream. The guide is the mechanism that keeps classification uniform across thousands of pages produced by people who never met the original classifier.

The mechanism: how a guide turns one decision into thousands

Original classification happens once. A designated official with authority decides that specific information, if disclosed, could damage national security, and records that decision. A classification guide is the durable output of that decision, engineered for reuse. Every derivative classifier who later quotes, summarizes, or restructures the underlying information inherits the classification from the guide rather than making a fresh judgment.

The guide works by decomposing a program into discrete elements and assigning each element a level, a reason, and a declassification trigger. A typical entry carries a level (Confidential, Secret, or Top Secret), a category, a reason tied to a damage criterion, a declassify-on date or event, and a guide identifier. That structure lets a writer working on an unrelated document find the relevant entry and apply the mark without understanding the full original rationale—the guide carries the rationale for them.

The downstream logic is derivatively applying classification by the "revealing" test. If a new document incorporates a guide entry, the new document inherits that entry's level. If it combines several entries, it inherits the highest level among them, plus any classification added by compilation. Compilation matters because aggregating unclassified or low-level fragments can reveal a sensitive whole—a detail most thin explainers omit.

Governance runs through a chain: the original classification authority approves the guide, a classification management office tracks it, and derivative classifiers are trained and audited against it. The guide is a controlled document with a version, an owner, and a review cycle, so it functions more like a specification than a memo.

The levels and their consequences, quantified

US classification rests on three levels plus a controlled-unclassified tier, and the guide must state which applies. The levels track the severity of expected damage, not the sensitivity of the topic. A guide entry is only as good as its reason line.

The counterintuitive detail: a lower level is not "less classified." Confidential still carries criminal penalties for unauthorized disclosure, and controlled-unclassified material can be legally restricted without a classification mark at all. A guide that says "Unclassified" is making an affirmative judgment, not declining to judge.

One professional caveat: a guide entry does not license a derivative classifier to downgrade or declassify. Only the original authority, or an automatic declassification rule, changes the level. The guide tells you what to mark, not whether to release.

Timeline: from original decision to declassification

Classification guides have a life cycle, and the clock matters because most classified records are subject to automatic declassification at fixed intervals.

The 25-year figure is the standard automatic-declassification threshold for permanently valuable records, and it is the number most often misapplied. It does not mean everything becomes public at 25 years—exemptions and referrals can extend protection well beyond it. A guide entry that says "declassify on a specific event" can override the default clock for that element.

Edge cases: where guides strain

Compilation is the first edge case. A writer assembling five Secret fragments into one document may produce a Top Secret product if the aggregate reveals a capability none of the fragments reveals alone. Good guides include a compilation warning; thin ones do not, and that gap is where leaks originate.

The second edge case is foreign disclosure. A guide can mark information Secret for domestic purposes but note that release to a specific ally is permitted under a separate agreement. A derivative classifier who applies only the level and ignores the release caveat will over-classify, slowing legitimate sharing.

The third edge case is the "legacy" document. A guide written for a retired system may still govern records in an archive, and its declassify-on dates may have passed silently. Reviewers must reconcile the guide against current policy rather than assume the old text is still operative.

The fourth edge case is over-classification. The incentive structure favors marking up, because marking down risks penalty while marking up rarely does. A guide is only a control if its entries are specific enough to restrain that drift—vague entries ("technical data") invite maximum marking.

Red-flag warnings for anyone using a guide:

A guide entry with no reason line or no declassify trigger is incomplete; escalate it before relying on it. "Unclassified" on a guide is a decision, not a default—do not treat it as permission to publish. A guide that has not been reviewed within its stated cycle may be stale; verify with the classification management office. Applying a higher level than the guide requires is still an error and can be audited. Never declassify or downgrade based on a guide; that authority sits elsewhere.

Misconceptions that explain most errors

The most common misconception is that the guide is a reference the classifier consults occasionally. In practice it is mandatory: derivative classifiers are expected to mark from the guide, and a document that ignores an applicable entry is noncompliant even if the level happens to match.

The second misconception is that the guide and the original classification decision are the same thing. The original decision is the judgment; the guide is its operational translation. If they diverge—because the guide is outdated—the original authority's current intent controls, and the guide should be corrected.

The third is that classification is about secrecy of topics. It is about damage from disclosure. The same topic can be Unclassified in one program and Top Secret in another depending on what the program's disclosure would reveal. That is why guides are program-specific, not topic-general.

The fourth is that a guide covers everything. It covers what the authority chose to enumerate. Information outside the guide is not automatically unclassified—it may require a fresh classification determination, which is exactly why the guide's scope statement matters.

A plain-language way to hold this: the guide is a recipe, the original classifier is the chef, and the derivative classifier is a line cook who must follow the recipe exactly but cannot change it.

Practical actions: working with a guide correctly

Start by confirming scope. Check that the guide actually covers the program your document belongs to, and read its scope and exclusions before applying any entry. A guide for a related but distinct system may not govern your material.

Then map each piece of information to a guide entry. For each element you intend to include, locate the matching entry and record its level, reason, and declassify trigger. If you cannot find an entry, do not default to unclassified—route the question to the classification management office.

Apply the highest applicable level and check for compilation. Mark the document at the highest level among the entries you used, then ask whether the combination reveals more than any single entry. If it does, mark up and note the compilation rationale.

Handle ambiguities in writing. When an entry is vague or conflicts with another, document the question and get a written determination rather than guessing. A written record protects both the classifier and the program.

Review before release and reconcile dates. Verify that no entry's declassify trigger has passed, and that your marking matches the current guide version. Reconcile multiple clocks explicitly: an event-based date in an entry overrides the automatic threshold for that element, so do not apply the 25-year default where a specific trigger exists.

The specific thresholds to hold together are the three damage standards for level, the entry-level declassify trigger, and the automatic-declassification default. When they conflict, the more specific and more recent authority controls—and when in doubt, the original classification authority resolves it.

Limits of what a guide can tell you

A guide cannot substitute for judgment about a novel document. It enumerates known elements, and genuinely new information may fall outside every entry. It also cannot keep pace with a program that changes faster than its review cycle, which is why the cycle length is itself a risk factor.

Most importantly, the guide is a domestic classification instrument. It does not resolve export-control, privacy, or contractual restrictions that may apply on top of classification, and it does not authorize release to anyone, foreign or domestic, without the separate disclosure process.

This article is general educational information about how classification guidance works, not legal advice or an authorization to classify, declassify, or release any information. Classification decisions are governed by agency policy and the original classification authority; consult your local classification management office or qualified counsel for any specific determination.