Understanding Security Classification Guide States
The Security Classification Guide (SCG) is a foundational document in the classification system. It tells you what information is classified, at what level, and for how long. States matter because they define when and why classification applies in different jurisdictions or operational contexts. Classification states are not optional categories. They are binding directives. When an SCG lists a state, it usually refers to whether information is classified under federal law, state law, or both. Getting this wrong can lead to over-classification or, worse, unauthorized disclosure.
The Security Classification Guide Scg States
The exact term you are looking for is The Security Classification Guide Scg States. It covers the intersection of federal classification policy and state-level classification requirements. This matters most in joint operations, multi-agency projects, and contractor work that touches state-specific data. Classification is not one-size-fits-all. Federal classification comes from Executive Order 13526 and implementing directives. State classification comes from individual state statutes, executive orders, or administrative rules. These two systems do not always align. An SCG must address both when the program involves mixed jurisdiction. The guide should specify which classification markings apply in which context. It should also address declassification and downgrading rules that may differ between federal and state frameworks.
I have seen SCGs that only addressed federal classification. When those documents were used in state-specific programs, analysts would either classify too aggressively or miss state-required markings entirely. The fix was straightforward: add a state classification annex to the SCG that cross-references the applicable state statutes and executive orders.
Get the Full Details
Practical Steps for Writing or Using an SCG With State Provisions
Start by identifying all jurisdictions involved. This includes federal programs, state programs, and any local or tribal jurisdictions that may have classification authority. Document each jurisdiction's classification rules separately before merging them into the SCG. Next, map the information types to their respective classification authorities. Some information may be federally classified but not state classified. Other information may be classified under state law but unclassified at the federal level. The SCG needs to reflect both realities without creating contradictory guidance. Include clear declassification provisions for each jurisdiction. Federal declassification schedules do not always match state schedules. If you apply a federal 10-year automatic declassification rule to state-classified information, you may inadvertently violate state law. Verify the applicable state declassification period and incorporate it into the guide.
Common Pitfalls I Have Encountered
One recurring issue involves source marking. Analysts sometimes mark information as SECRET//NOFORN based on federal guidance and then forget to apply state-specific derivative markings. The result is incomplete marking that fails to convey the full classification scope. Another problem is outdated state references. State classification rules change more frequently than federal rules because state legislatures amend statutes without coordinating with federal classification policy. If your SCG cites a superseded state code section, the guidance is legally invalid even if the federal portion remains correct. I ran into a case where an SCG referenced a state executive order that had been revoked. The guide was used for eight months before anyone noticed. The workaround was to establish a routine review cycle tied to the state legislature's session schedule. Classification guides that touch state authority should be reviewed at least once per legislative session, or whenever the relevant state statute is amended.
When SCG State Guidance Falls Short
Classification guides are not foolproof. An SCG cannot anticipate every edge case. When information does not fit neatly into an existing classification category, the guide will not save you. In those situations, you need a classification determination from the appropriate classification authority. That authority is usually the originating agency or the agency with primary stewardship over the information type. If you find yourself in a gap, do not guess. Send a formal classification advisory request. The response may take time, but it creates a documented trail that protects everyone involved. Guessing classification levels is how mishaps happen.
What You Should Do Next
Review your existing SCGs for state classification provisions. If your guide only addresses federal classification, it is incomplete for any program that touches state-level information. Add a state annex that references current statutes and executive orders. Schedule regular reviews tied to legislative cycles. Train your personnel on the difference between federal and state classification requirements. The Security Classification Guide Scg States is not just terminology. It is a practical requirement that affects how you mark, protect, and eventually declassify information. Treat it with the same rigor you give the federal portion, and you will avoid most of the mistakes I have seen over the years.
