The third agency rule says that information one agency gives another cannot be passed onward to a third agency without the originator's consent. It's a confidentiality principle within executive government, not a statute — and in the United States it appears mainly in executive orders governing classified national security information and in agency-to-agency agreements, which is why it binds federal agencies far more predictably than it binds anyone else.
What the Rule Actually Requires and Who It Binds
Start with the mechanics. Agency A gives Agency B a document or dataset, usually under a classification marking or a written agreement that says "no third-agency dissemination." Agency B's analysts can use it, but the moment the material reaches someone outside B, that's a dissemination event the rule governs. If B works with Agency C, B must obtain A's permission first.
The rule is administrative, not constitutional. It traces to executive branch information-handling directives — principally the series of executive orders on classified national security information, from Executive Order 12356 in 1982 forward — which instruct agencies to protect information received from other agencies the same way the originating agency protects it. Those orders sit on the Office of the Information Security Oversight Office in the National Archives to interpret.
Who's bound: executive departments and agencies, their contractors, and personnel holding security clearances. Congress and the courts operate outside the executive branch's control regime, which creates the friction the rule's critics point to. State governments have their own analogues, and interagency memoranda of understanding routinely restate the third agency principle as a contract term even where the executive order technically doesn't reach.
The scope is broader than classified material. A Census Bureau record shared with another statistical agency, a law enforcement database accessed through a joint task force, a Suspicious Activity Report passed to a partner agency — each carries some flavor of the same originator-consent principle. The exact legal hook varies, but the operational behavior is consistent: ask before you forward.
Where the Term Comes From and Why It's Often Traced to FinCEN
Search for the phrase and you'll hit FinCEN guidance repeatedly, and that's not an accident. The Financial Crimes Enforcement Network's regulations at 31 CFR 1010.930 govern how suspicious activity reports and related information may be shared, and the framework is explicitly built on the idea that information the bureau releases to one regulator, law enforcement body, or foreign counterpart stays under distribution control.
FinCEN's guidance on SAR confidentiality tells recipients that the information is the bureau's and that further sharing requires the originator's authorization. That is the third agency concept in operational dress. Financial institutions themselves don't get to forward what a regulator handed them, and the receiving agency doesn't get to pass it to a partner without sign-off.
If you're building a compliance program, the practical takeaway is to find the sharing authority — 31 CFR 1010.930 for SARs, the relevant executive order for classified material, the specific memorandum of understanding for task-force data — rather than relying on the phrase alone. Download the current text from FinCEN's site before citing it in a policy.
| Setting | Governing authority | Originating agency's role | Consequence of forwarding without consent |
|---|---|---|---|
| Classified national security information | Executive orders on classified information, administered by the Information Security Oversight Office | Sets classification, controls declassification and re-release | Potential security violation; referral for investigation |
| SARs and BSA data | 31 CFR 1010.930 and FinCEN guidance | Authorizes recipient categories and onward sharing | Regulatory referral; audit finding |
| Census and statistical microdata | Title 13 confidentiality provisions; agency sharing agreements | Approves each release and its terms | Civil and criminal penalty exposure for the receiving agency |
| Joint task-force criminal intelligence | The task-force MOU, often criminal-intelligence-system rules | Named in the MOU as the data steward | Removal from the task force; intelligence sharing cut off |
| Contractor-held federal data | FAR 52.204-21 and related clauses | Flows down the originator's restrictions | Contract cure or termination |
How the Rule Operates Inside a Real Interagency Request
Picture a state environmental regulator that receives sampling data from a federal agency under a cooperator agreement. The agreement says the federal agency's field notes can't be released to third parties. Six weeks later, a county health department asks for those field notes. The state analyst can't forward them.
That's the everyday shape of the rule. It isn't a dramatic national security problem. It's a request that sits in somebody's inbox until the originator is asked. The Illinois attorney general's Public Access Bureau addressed exactly this in a binding opinion — state open-records law can require disclosure of records a public body holds, but federal agency records in its hands may fall outside that obligation depending on the agreement. "It depends on the agreement" is the honest answer, and it's the one the opinion reaches.
The operational discipline is to log the originator on every incoming package. A one-line field in your records system — originator, date received, dissemination restrictions, contact for consent requests — is worth more than a policy binder. When a request comes, you check the field, and if the restriction exists you route the ask to the originator instead of answering the requester.
Failure handling matters here. If you've already forwarded material, the standard remedy is prompt notification to the originator, a pull-back request to whoever received it, and documentation of the breach. Waiting to see whether anyone notices is the failure mode that turns an administrative slip into a finding of bad faith.
The 1982 Order and How the Rule Tightened Across Four Decades
Executive Order 12356, signed in 1982, established the pattern most agencies still follow: information received from another agency is safeguarded according to the originator's designation, not the recipient's judgment. The rule wasn't new in 1982, but the order made it explicit and uniform.
Later orders shifted the boundaries. Executive Order 12958 in 1995 created the automatic 25-year declassification framework and required agencies to refer foreign-government information back to the originating agency for a declassification decision — a direct application of the third agency idea to records management. Educational material from the Information Security Oversight Office walks through how referrals work and what a receiving agency does when it can't make the call itself.
The 2009 order and the current framework have kept that referral mechanism. This is where the rule gets interesting for anyone doing archival research: a document's classification isn't determined by which agency's file cabinet it's in. The originator controls the decision. Researchers regularly wait months while one agency asks another whether a 40-year-old cable can be released.
What changed over time is the volume and specificity. Each iteration added timelines, referral tracking requirements, and reporting obligations. The 1982 version assumed a modicum of mutual trust. The current version expects documentation.
Three Scenarios Where the Rule Triggers — and One Where It Doesn't
Three realistic cases. First, a contractor holding an unclassified but restricted database from a federal customer receives a public-records request forwarded by a state agency. The contractor must route the decision to the federal originator, not to the state.
Second, a joint terrorism task force officer wants to put intelligence from one partner agency into a district attorney's case file. The intelligence isn't releasable to a prosecutor without the originating agency's consent, and "the DA has clearances too" isn't the test.
Third, a statistical research center receives microdata from a federal statistical agency under a licensing agreement. It cannot share the microdata with a university research team outside the license without written approval from the statistical agency.
The non-trigger is important. If Agency A publishes something publicly — a press release, a rulemaking docket, a mandated annual report — there's nothing left to protect. The rule governs protected information, not every document that happens to sit in a federal inbox. An agency cannot invoke the third agency principle to withhold information the originator has already released.
That distinction generates most of the litigation. Requesters argue the material is public; agencies argue the originator still controls it. Courts tend to ask whether the originator has actually released the specific content, not whether the general subject area is public.
Why Information-Sharing Agreements Rarely Say the Words "Third Agency"
Open a current information-sharing agreement between two federal agencies and you may not find the phrase. You'll find clauses instead: "Recipient shall not disseminate without prior written approval," "Information remains the property of the originator," "Recipient shall refer all requests to the originating agency." These are the third agency rule translated into contract language.
That translation matters because agreements are enforceable between parties in a way that executive orders mostly aren't enforced by third parties. A contractor who violates a data-restriction clause faces a breach claim. A cleared employee who violates an executive-order directive faces an administrative security process. Same principle, different machinery.
The variety across agreements is real, and anyone relying on "the third agency rule" needs the specific contract. Some agreements permit onward sharing within a defined set of agencies. Some require notification rather than consent — a meaningfully lower bar. Some define "agency" to include contractors, some don't. Read the definitions section first; that's where the practical scope lives.
If you're drafting an agreement, specify the consent mechanism. An email from a named point of contact within five business days is a workable standard. "Reasonable efforts to obtain originator approval" is not, and it becomes the clause everyone argues about later.
Under Secrecy Law, the Forwarded Document Doesn't Become the Recipient's Record
Here's the distinction people miss. The rule governs whether Agency B may pass material to Agency C. It does not determine whether the material becomes Agency B's record if it lands there under other authority. Those are separate questions, and confusing them produces bad advice in both directions.
Under the executive order framework, classification authority stays with the originator, but derivative classification can occur — a receiving analyst can classify a new document incorporating originator information. The restricted-content obligation flows forward regardless.
This is the practical reason to track the third agency taint through derivative products. If your analyst writes a briefing that incorporates protected material from another agency, the briefing carries the restriction. Many inadvertent third-agency violations happen at this step, not at the obvious forwarding step. The analyst doesn't realize their own product inherited the restriction.
When you're dealing with a FOIA request for a derivative product, you assess the restriction on the source material, not the product's author. That's the audit trail question, and it's why records managers want originator fields populated at intake.
If you're on the requesting side, ask which agency originated the content before you accept "we can't release that" as final. Sometimes the answer is that the receiving agency can release it after checking with the originator, and the check takes a day.
Balancing the Rule Against Transparency and the Public Interest
The rule's critics have a straightforward argument. If Agency B can't release Agency A's material, and Agency A isn't subject to the same request, the requester hits a wall not because the content is sensitive but because of which building holds the file. That's a coordination problem dressed up as a confidentiality doctrine.
The counterargument is equally straightforward. Joint work requires candor, and analysts won't share raw assessments with partners if the material will be repackaged to whoever asks. The ISOO framework puts the tradeoff in writing with the referral process — a request routes to the originator, who decides on the merits.
The practical resolution for requesters is to name the originator in the request. If you're asking a state agency for data that came from a federal statistical agency, request it from the federal agency too. Parallel requests close the loop faster than appeals.
For journalists and researchers, the referral trail is often more interesting than the document. A referral letter from one agency to another tells you who originated the material, which tells you where next to ask. Treat the referral as a routing instruction.
What a Compliance Program Needs on Paper
Build the program around five artifacts. First, an intake register: originator, date, restriction, consent contact. Second, a decision log: who asked to share what, with whom, and what the originator said. Third, a training module that uses real examples from your own agency, not generic slides. Fourth, an annual audit sample of outgoing sharing to check that consent is documented. Fifth, a breach protocol naming who notifies the originator and within what window.
The audit step is where most programs fail. Consent exists in email threads, the log doesn't get updated, and the next auditor finds the gap. Make the log the only place that counts; unresolved email-based approvals are the discrepancy.
Training should be role-specific. Analysts who produce derivative work need the taint lesson. Records managers need the referral lesson. Contracting officers need the contract-clause lesson. One general session for everyone wastes the hour.
Test your own program by picking three recent outgoing transfers and asking who approved each. If the answer is "we think it was fine," the log isn't working. The point of the artifacts is that the answer takes five minutes to find.
FAQ
Is the third agency rule a federal statute with criminal penalties?
No — it's an executive branch information-handling principle, typically expressed through executive orders and agency agreements rather than a standalone criminal statute. The penalties come from the underlying authority: a security violation under the classified-information framework, a regulatory referral under FinCEN's SAR rules, or breach of contract under a data-sharing agreement. Check the specific instrument for the specific consequence.
Can a contractor with a security clearance forward information between agencies?
Not on the basis of clearance alone. Clearance establishes eligibility to access; it doesn't authorize dissemination. A contractor holding restricted material from one agency must obtain that agency's consent before passing it to another, even if everyone involved holds a clearance. The relevant test is the restriction on the material, not the clearance level of the person handling it.
Does this rule apply to someone filing a FOIA request for records one agency got from another?
It shapes how the request is processed, but doesn't create an automatic exemption. Under the referral process in the executive-order framework, an agency typically routes a request for another agency's classified material to the originator for a release decision. If the material isn't classified or otherwise protected, the receiving agency can often release it directly. Ask which agency originated the content — that's the routing question.
If a state agency receives federal data, can it withhold it under state open-records law?
Sometimes, and it depends on the specific agreement plus the state's open-records statute — the Illinois attorney general's Public Access Bureau reached that outcome in a binding opinion. Some agreements explicitly restrict onward disclosure; others don't. Consult the state public-records authority and the actual agreement text before deciding.
Does the rule block sharing information the originating agency has already made public?
No. The restriction protects information that's still under the originator's control. If the originating agency has published the material — press release, docket, annual report — the confidentiality justification largely evaporates. The dispute usually becomes whether the specific content was actually published, not whether the general subject matter is public.
Does derivative work inherit the restriction?
Yes, frequently. If an analyst produces a briefing or report incorporating protected information from another agency, the product generally carries the same dissemination restriction at the point of incorporation. Many inadvertent violations occur at this derivative step rather than at the obvious forwarding step, which is why originator tracking belongs at intake.
What happens if an agency forwards material without consent?
The standard response is prompt notification to the originator and a request to the recipient to pull back or restrict further use, documented in writing. The consequence for the forwarding agency depends on the underlying authority: a security incident referral for classified material, a regulatory finding for SAR data, or a breach claim under an agreement. Waiting to see whether the recipient notices is the failure mode to avoid.
Can a receiving agency rely on "we didn't know" as a defense?
Rarely a full defense, because the burden is on the receiving agency to record the restriction when it takes in the material. A robust intake register — originator, date, restriction, consent contact — is the practical safeguard. If your program can't produce the restriction at the moment of a disclosure question, that's the finding.
This article is general educational information about a government information-handling principle, not legal advice. Agency agreements, executive orders, and statutory frameworks vary by jurisdiction and change over time, so consult a qualified attorney in your jurisdiction and the current text issued by the authority controlling your specific information before acting on any sharing decision.