Executive Order 12829: National Industrial Security Program
Summary
EO 12829 established the National Industrial Security Program to protect classified information released to industry and other covered nonfederal organizations. Bush signed it January 6, 1993. The order organizes policy, oversight and operating requirements; it also amended the earlier clearance-procedure order EO 10865. Its program and advisory committee need separate status explanations.
Status: In effect. Yes. As amended, NISP continues through current industrial security rules. The listed continuations concern its advisory committee, not an expiry date for the entire program.
Key facts at a glance
| Signed | January 6, 1993 |
|---|---|
| President | George H. W. Bush |
| Federal Register | 58 FR 3479; published January 8, 1993 |
| Current label | In effect |
| Amended by | EO 12885, EO 13708 |
| Related orders | EO 10865, EO 12885, EO 13708, EO 13652, EO 14354 |
| Checked | October 25, 2026 |
What it requires today
NISP coordinates safeguarding of classified information held by covered contractors and other participants. Agency responsibilities include using the program’s operating framework, security requirements and oversight mechanisms. An organization’s participation does not authorize unrestricted access to all classified information.
The order assigns an executive-agent role and calls for an operating manual. Current implementation is the NISPOM rule in 32 CFR part 117. The rule, applicable contracts and agency instructions supply practical requirements; the original 1993 text alone is not a complete compliance handbook.
Section 103 established the National Industrial Security Program Policy Advisory Committee. Later continuation orders concerning that committee should not be mistaken for a periodic expiration and renewal of all NISP obligations. The committee’s current charter has its own duration and duties.
Who it affects
Cleared contractors, grantees and other covered industrial organizations, employees with classified access and participating agencies are affected. Program oversight, an individual’s eligibility and a specific need to know are related but distinct. A facility clearance is not a waiver of personnel or information-handling requirements.
How it came about
The 1993 order sought more consistent industrial security across agencies while preserving statutory authorities such as the Atomic Energy Act. It amended EO 10865 to align the earlier industrial access framework with the new program. Signature preceded the change of administration on January 20, despite the same calendar year as Clinton’s inauguration.
What agencies did under it
DCSA’s current materials identify 32 CFR part 117 as the NISPOM rule. FAR subpart 4.4 likewise places classified-contract work in the industrial security setting. These current implementation records positively support the continuing amended program.
NARA’s current NISPPAC charter, filed November 26, 2025, identifies section 103 of EO 12829 and continuation through EO 14354. It specifies committee termination on September 30, 2027 unless continued. That date belongs to the advisory body; it is not stated here as a sunset of the program or the NISPOM rule.
The committee advises on industrial security policy; it is not the body that grants every facility or personnel clearance. Its charter describes membership, meetings, support and duration. The operational program has separate authorities and administrators. This division explains why a committee can require periodic continuation while the underlying safeguarding duties remain applicable.
The current charter also identifies NARA and ISOO support and the designated federal officer. These administrative arrangements help explain the committee’s current institutional home. They should not be used to imply that NARA takes over every contractor’s day-to-day security administration or that committee advice overrides a binding regulation.
For a covered contractor, compliance involves the information and activities actually entrusted to it. Handling, reporting, subcontracting and access requirements arise under the applicable current rule and contractual terms. A general statement that a facility participates in NISP does not establish that every employee is cleared or every system is approved to process classified information.
The program’s interaction with EO 10865 matters when an individual faces an adverse access decision. Program oversight and procedural protections answer different questions: one organizes safeguarding across organizations, while the other addresses specified decisions affecting individuals. Reading the two together avoids treating a broad program-management order as either a complete hearing code or a reason to ignore the hearing safeguards that remain applicable.
The original order also accounts for statutory programs whose classified information has special legal treatment. A government-wide coordinating program does not repeal those statutes. For a contractor working with several agencies, the correct answer is therefore not necessarily to apply whichever instruction seems least burdensome. The applicable security agreement, current rule and responsible agency determine the requirements for the information concerned. If an advisory committee recommends a change, the recommendation itself is not the same as an amended binding rule. This distinction between advice, program administration and legal requirements explains why the charter is useful evidence for the committee’s status while the CFR and agency implementation materials remain necessary for operational compliance. None of those records establishes a private organization’s actual compliance without examining its conduct.
Implementation records: Current NISPOM rule; Current advisory committee charter; FAR classified industrial safeguards.
Amendments and family tree
EO 12885 and EO 13708 amended the order. EOs 13652 and 14354 continued the advisory committee. EO 13708 also changed the program framework, so a reference to committee continuation is not a complete description of that instrument. The EO 10865 guide covers the related individual access safeguards.
Related guides: EO 10865, EO 12885, EO 13708, EO 13652, EO 14354.
Court cases
No court ruling specifically on EO 12829 was found in the official presidential, disposition and agency sources examined as of October 25, 2026. The status assessment for this instrument is: Yes. As amended, NISP continues through current industrial security rules. The listed continuations concern its advisory committee, not an expiry date for the entire program.
Common questions
Does NISP expire in September 2027?
The date in the current charter concerns NISPPAC, the advisory committee. It should not be used as an expiry date for the entire program or the NISPOM rule.
Is the 1993 manual the current rule?
Use current 32 CFR part 117 and applicable agency instructions. The original presidential framework and current detailed requirements are different documents.
Does the order cover individual clearance safeguards?
It amended EO 10865 and fits within the wider access-decision framework. The two guides explain connected but distinct aspects of industrial security.
Who signed it?
George H. W. Bush, on January 6, 1993. Publication and calendar-year grouping do not change that attribution.
Legal basis
The program operates within presidential national-security administration and applicable statutes. It preserves distinct statutory authorities rather than merging all classified-information powers into one unrestricted rule. Current agency rules and contractual requirements remain essential to applying the framework.
Further reading
Sources
Cite this page
EO Explained, “Executive Order 12829: National Industrial Security Program”, checked October 25, 2026. https://eoexplained.com/historic-orders/historic-12829-national-industrial-security-program. Include an access date when citing this dated account. For the presidential instrument itself, cite 58 FR 3479 and the official text.
Last checked
. EO 12829 was checked against its signed record, current disposition and cited implementation sources for the status and scope described above. Report an error or a later official source.