The statement is true under U.S. controlled unclassified information policy. Labeling CUI is mandatory, and the banner at the top of every page is the baseline control—the 32 CFR Part 2002 rule and the ISOO CUI Registry's marking guidance both treat it as required, not optional decoration. One boundary matters immediately: CUI marking is a government-wide standard anchored in an executive order and federal regulation, and it is enforced for agencies and for contractors and other parties operating under agreements that incorporate CUI marking terms. If you handle CUI, the banner is not a judgment call.

What the CUI marking rule actually mandates

The phrase most people are searching for comes from the standardized marking structure that agencies must apply to CUI. Executive Order 13556 established the CUI program in November 2010, and the National Archives and Records Administration's Information Security Oversight Office (ISOO) issues the implementing directives. The rule appears in Title 32 of the Code of Federal Regulations, Part 2002, which sets out how agencies designate, mark, and handle controlled unclassified information.

The marking requirement is operationally simple. CUI must carry the banner "CUI" at the top of the page so that a person holding the document cannot mistake it for ordinary unclassified material. The ISOO CUI mark is a multi-line marking that always includes the CUI banner line plus required category, limited dissemination, and classification (for material that is also classified) lines. The banner is the first and most visible element of that marking.

You can confirm the current specifics at the official ISOO CUI Registry and the eCFR text of 32 CFR Part 2002. Those sources are authoritative and change only rarely. Anything on a third-party blog, including specific option menus in a particular software product, should be checked against them before you rely on it.

Why the banner is not optional for any CUI category

The banner is not an optional decoration that can be replaced by a footer marking, a cover sheet, or a stamp. The rule applies to the whole page because the purpose is to give any reader an immediate, unambiguous indicator that the page contains controlled unclassified information. A marking scheme that only appears on the first page or only in a document heading is insufficient.

The reason is not bureaucratic. CUI spans a wide range of categories—law enforcement data, export-controlled technical information, personal privacy information, critical infrastructure data—and the handling rules differ by category. The banner tells a reader to stop and look for the specific category marking below it. Without the banner, the category marking is easy to miss.

You should treat "banner at top of page" as an absolute baseline. If your policy or enforceable contract incorporates the standard, the minimum you must do is put "CUI" at the top of every page of an authorized CUI document. If you are not sure whether a document carries CUI, ask the designating agency or your contracting officer.

The full CUI marking stack: banner, category, and dissemination controls

The CUI banner is the first line of a three-part marking stack. Once you see the banner, the document should also specify which CUI category applies (for example, export control, critical infrastructure, or privacy) and any limited dissemination controls the designating agency has applied. Each line serves a different function, and none can substitute for the banner.

Marking element Where it appears What it must say What it tells the reader Common failure
CUI banner Top of every page of the document "CUI" (per ISOO CUI marking standard) Stop: this page is controlled Banner only on page one
CUI category Under the banner or in a cover block The specific category name from the CUI Registry What rule set applies Wrong category selected
Limited dissemination Under the banner or category line A dissemination control (e.g., NOFORN, FEDCON) Who may receive it Omitted
Classification marking Top and bottom, if the document is also classified The classification level Handling under the classified system Missing overlap marking

The table is a diagnostic tool. If you spot a CUI document with a banner but no category line, that is not a compliant marking—it is a partial marking. If you spot a document with category markings but no banner, the safest correction is to add the banner and consult the designating agency.

Which formats and systems the rule actually covers

The banner requirement applies to the physical and electronic document formats that carry CUI—paper printouts, PDFs, word-processing files, email bodies with CUI content, and the covered systems in which CUI is stored or transmitted. The practical question is where you need to put the banner to keep the page compliant when it is viewed on screen or printed.

For paper, a header or top-of-page stamp works. For PDFs and word-processing documents, the header or top-of-page text field is the standard mechanism. For email, the banner appears at the top of the body text of the message. For chat and collaboration systems, treat the message or channel content the same way: the CUI marker should be visible to the reader at the top of the content they are reading.

A common question is whether the banner must be visible when a document is printed only. The answer is no—the requirement is a visible marking that travels with the content. If a system reliably displays the banner while the record is accessed, that is material to whether you are compliant; a system that strips the header on export can create a gap. Confirm export behavior in your environment rather than assuming it.

Who must comply: agencies, contractors, and the self-marking trap

Agencies are directly bound by 32 CFR Part 2002. Contractors, grantees, and other parties who handle CUI are bound through the terms of their agreements, which typically incorporate the CUI marking and handling rules; the DoD acquisition context adds the DFARS 252.204-7012 clause and its Safeguarding Covered Defense Information requirements. The practical effect is the same: once your agreement says the data is CUI, the banner and category markings apply to documents you generate, forward, and store.

A frequent trap is self-marking. A company that believes it holds CUI may mark a document with a CUI banner before the designating agency has told it that the data qualifies. The regulation does allow a party who generates information it believes is CUI to mark it, but a self-applied marking does not give the document legal status or change the underlying designation. If in doubt, confirm with the designating agency or your contracting officer.

A second trap is under-marking. Contracting officers sometimes hand over documents that are not marked even though the contract terms impose CUI handling. Do not assume the absence of a banner means the data is unrestricted—check your contract and the category list, and ask the contracting officer to clarify in writing.

Labeling versus handling: where the CUI banner fits in practice

"Labeling CUI" and "handling CUI" are often confused. The banner is a labeling control. It does not, by itself, satisfy the handling requirements—storage, transmission, access control, encryption, and incident reporting—that apply based on the specific CUI category and your agreement. You can have a perfectly marked document and still be non-compliant on handling, and you can have compliant handling on an internally marked draft that never leaves your network.

The practical hierarchy is labeling first because it drives everything else. Without a visible banner, downstream users cannot know to apply the right handling. So the sequence is: identify the CUI category, apply the full marking stack (banner plus category plus dissemination), then apply handling controls consistent with that category and your contract.

A good rule of thumb is that if a document is marked CUI, the handling rules you owe the designating agency apply to every copy, every extract, and every transmitted version. The banner is the flag that makes that obligation visible to each reader. A common failure mode is a correctly marked original with an unmarked working copy, which is why policy ownership should sit with a named role.

What the top results get wrong about the CUI banner

The most common error in online explanations is treating the banner as a discretionary "good practice" rather than a required element. It is a required element under the standardized marking, and the practical consequence is that an unmarked document can trigger the exact handling failure the rule is designed to prevent: a reader who does not know the document is controlled.

A second error is confusing the CUI banner with the classified marking. A classified document has top and bottom classification markings and also carries a CUI banner if its content is CUI—the markings overlap. If a classified document carries no CUI banner because its contents are not CUI, that is correct, not a markup mistake. The CUI banner is for CUI content, not for every document that crosses your desk.

A third error is treating the CUI banner as equivalent to the classification "SECRET" banner. They are different systems with different authorities. CUI is not a classification level; it is a category of unclassified information that requires safeguarding. If you are working with both, confirm each marking against the appropriate authority rather than copying one system's banner into the other.

A fourth trap is assuming that marking guidance is static. The CUI Registry changes infrequently but does change, and your organization's contractor agreements reference specific dates. Check the eCFR and the ISOO Registry for the current text and confirm your organization's contract language against the current standards.

Frequency of change and the date to check your program against

The federal CUI marking requirements are stable, and there is no monthly or annual change cycle that you need to track for the core banner requirement. The eCFR text of 32 CFR Part 2002 is the codified rule, and the ISOO CUI Registry is the current authoritative source for categories and dissemination control markings. The prudent approach is to review those sources when you begin a new agreement, when you onboard a new system that touches CUI, and at a defined internal interval set by your compliance team.

A worked example makes the cost of a gap clear. If a program office sends a single unmarked page of CUI to five recipients outside the intended distribution, that triggers an incident review, a notification chain, and a documentation effort that easily runs into dozens of hours of compliance staff time. The banner costs pennies and a few seconds. The trade is obviously worth it.

The date to anchor your program against is the effective date of your agreement or the date your organization last validated its markings. If your policy references a 2019 or 2020 version of the marking standards and you have not checked since, that is the gap to close before your next audit.

Edge cases: draft documents, email attachments, and print-to-PDF export

The edge cases matter because they are where compliance breaks. A draft document that you plan to mark before distribution but circulate internally without a banner is still unmarked CUI if it contains CUI content. The safe approach is to mark the draft from the first version that contains CUI content, so no version exists without the marking.

Email attachments are a frequent failure point. If the attachment is a CUI file, the file itself carries the banner, and the email body should carry a CUI banner too if its body content is CUI. An attachment that loses its header when downloaded from a webmail or collaboration tool is a real problem; test the export path and confirm the marking survives.

Print-to-PDF export deserves separate attention. Some tools preserve the header and some do not. A PDF that arrives with the banner stripped is effectively an unmarked document to the recipient. Confirm the export behavior on the system you use, and where you cannot confirm it, add a manual page-one banner before sending.

FAQ

Is the CUI banner always "CUI" in capital letters?

Yes, the ISOO CUI marking uses "CUI" as the banner text, and the rest of the marking stack follows beneath it. The banner is intentionally short so it is instantly recognizable at the top of a page. Do not substitute a descriptive phrase like "Controlled Unclassified Information" in place of the banner if your policy references the standardized marking.

What is the minimum marking if I only handle a single page of CUI?

The minimum is still the full marking stack for that page: the CUI banner plus the applicable category line and any limited dissemination control the designating agency has applied. A single-page document is not exempt. If you cannot determine the category, ask the designating agency or your contracting officer before sending.

Can I mark a document as CUI before anyone has told me it is CUI?

You can mark information you generate that you believe qualifies, but a self-applied marking does not create legal status or change the underlying designation. Confirm with the designating agency or your contracting officer. A self-applied banner is defensible as a protective measure but is not a substitute for the proper designation.

How is this different from a classified document marking?

CUI is unclassified information that requires safeguarding, not a classification level. A classified document carries classification markings at top and bottom and also a CUI banner if its content is CUI. If you are handling a document in both systems, confirm each marking against its own authority; the CUI banner is not a substitute for the classification marking, and vice versa.

Does the banner requirement change if the CUI is stored on a contractor's system?

No. The marking obligation follows the content through the contractor's system, and the contract terms typically incorporate the CUI marking rules. The contractor's own internal policy does not relax the requirement. Confirm the specific contract language and the ISOO CUI Registry for the current standard.

What should I do if I receive a CUI document with no banner?

Treat it as a potential marking failure and do not silently forward it. Ask the sender to confirm the category and intended handling, and add the banner if your policy and the applicable agreement require it before further distribution. Keep a record of the exchange with the sender, and check the eCFR and ISOO Registry for the current rule text.

Is there a cost or audit consequence to a missing CUI banner?

The banner costs essentially nothing to add, while a missing banner can trigger an incident review, notification obligations, and compliance documentation effort that runs into substantial staff time. In regulated environments, unmarked CUI is also the kind of finding that shows up in contract and audit reviews, which is why the marking sits in most compliance checklists.

Where can I verify the current rule text?

The authoritative sources are the eCFR text of 32 CFR Part 2002 and the ISOO CUI Registry. Both are stable and rarely change, so checking them at the start of a program or before signing a new agreement is sufficient for most organizations. When in doubt, confirm the current standard directly against those sources rather than relying on secondary summaries.

This article is general educational information about the CUI marking standard and is not legal advice or a compliance determination. It does not promise any audit or contractual outcome, and the rules and your obligations can vary by agreement, agency, and jurisdiction. Consult a qualified professional and the official ISOO CUI Registry and eCFR text for your specific situation. If you have immediate safety or security concerns involving controlled information, contact your organization's security or emergency services.