DoD Directive 2000.12 and the 1999 Map of Bureaucratic Blame
By Desmond Okafor ·
Following the 1998 embassy bombings, the Pentagon spent months drafting a manual on who was responsible for protection, a blueprint that prioritized paper trails over the lives of personnel on the ground.
The blood on the pavement in Nairobi and Dar es Salaam in August 1998 was the price of a systemic failure in American foresight. Two hundred and twenty-four people died because the United States government viewed its overseas outposts as safe harbors rather than targets, leaving diplomats and support staff to pay for the arrogance of a security apparatus that ignored the warnings.
By the time the Department of Defense—the Pentagon-based executive department that coordinates the U.S. Armed Forces—decided to formalize its response, the casualties had already been counted. The result was DoD Directive 2000.12, titled the "DoD Antiterrorism/Force Protection (AF/FP) Program," issued on April 13, 1999. The history of this failure is reconstructed here from an archival description of the record, as the full pages of the directive have not been released for this specific review.
The Paper Shield of April 1999
Eight months after the embassy bombs leveled buildings in East Africa, the DoD focused its energy not on the tactical agility of its security forces, but on the distribution of paperwork. The record establishes that the directive provides a "detailed description of responsibilities for those officials," as well as "enumerating the responsibilities of a number of other DoD officials" (DoD Directive 2000.12).
Among those placed under the microscope was the Under Secretary of Defense for Policy, the high-level civilian official who serves as the principal adviser to the Secretary of Defense on all matters of national security and defense policy. The directive did not ask the Under Secretary to find better intelligence on Al-Qaeda; it asked him to be the name attached to the policy of protection.
The timing is the tell. The gap between the August 1998 attacks and the April 1999 directive is the time it takes for a bureaucracy to realize it is legally exposed. The record shows a preoccupation with "enumerating responsibilities" precisely when it should have been enumerating vulnerabilities. When the state focuses on who is responsible for the program rather than how the program protects the person, the goal is no longer security—it is liability management.
Document imagery from nsarchive.gwu.edu From the files: nsarchive.gwu.edu
The Gap Between Policy and Neutralization
To understand the hollow nature of Directive 2000.12, one must look at the tools the DoD already possessed. The public record points to the Air Force Office of Special Investigations (OSI), the federal law enforcement agency reporting to the Secretary of the Air Force that is tasked with neutralizing espionage and terrorist threats to DoD personnel worldwide. The OSI operates outside the traditional military chain of command, giving it the flexibility to conduct counterintelligence in the shadows.
There is a stark contradiction between the OSI's operational mandate and the administrative posture of Directive 2000.12. While the OSI was built to proactively "neutralize" threats, the directive was built to "enumerate" roles. The line drawn here is one of institutional detachment. The DoD created a world where the people identifying the bombs—the investigators and the counterintelligence officers—were decoupled from the people signing the policy memos in the Pentagon.
This separation ensures that the Under Secretary of Defense for Policy can claim the program was "implemented" according to the directive, even if the OSI's tactical intelligence never reached the people guarding the gates in Nairobi. The directive creates a loop of accountability that never actually touches the ground. It establishes a chain of command for the paperwork, not a chain of survival for the personnel.
The Silo of the Pentagon
If the goal of the AF/FP Program was actual protection, it would have required a seamless integration with the State Department and the CIA. Force protection in a foreign capital is not a military exercise; it is a diplomatic and intelligence exercise. Yet, the record focuses exclusively on the internal hierarchy of the DoD. It treats the security of American assets as a closed-loop military problem to be solved by DoD officials.
The public record shows that the DoD is an umbrella for the Army, Navy, Marines, Air Force, and Space Force, but Directive 2000.12 reads as an internal memo to the club. By centering the program on the Under Secretary of Defense for Policy and other internal DoD figures, the directive effectively siloed the protection of personnel. It turned the AF/FP Program into a Department of Defense project rather than a national security imperative.
This is the irony of the post-1998 era: the U.S. government responded to a transnational terror threat by reinforcing the walls of its own bureaucracy. The directive did not build a bridge to the analysts at the CIA or the regional experts at the State Department; it built a more complex org chart within the Pentagon. It ensured that if another embassy fell, the DoD could point to a specific official and say, "The responsibility was clearly enumerated."
The Reading of the Pattern
When the evidence is laid bare, the desk's reading is that DoD Directive 2000.12 functions as an institutional defensive measure designed to formalize a chain of responsibility after the 1998 embassy bombings. This was not a manual for saving lives; it was a manual for surviving an Inspector General's audit. The emphasis on the Under Secretary of Defense for Policy suggests a drive to move the burden of failure from the tactical level to the policy level, where it can be buried in committees and amendments.
The pattern suggests that operational triggers—the actual signs that a bomb is being prepared or a perimeter is being scouted—were relegated to classified annexes, far removed from the administrative duties listed in the main directive. This decoupling allowed the DoD to maintain a facade of "comprehensive protection" while the actual criteria for triggering a lockdown or an evacuation remained hidden or non-existent.
Furthermore, the desk's reading is that the absence of any funding mechanisms or resource priority mandates within these enumerated duties proves that the responsibilities were symbolic. The DoD assigned the duty of protection to the Under Secretary without assigning the budgetary authority to actually implement it on the ground. It gave the official the responsibility for the failure, but not the resources for the success.
If the full, unredacted pages of this directive and its subsequent annexes were released, they would show a void where the tactical intelligence should be. They would reveal a system that prioritized the clerical correctness of the AF/FP Program over the physical safety of the people it claimed to protect. The pattern seen here is the same one the DoD would employ for years to come: creating a paper trail of responsibility to mask a vacuum of action. In the end, the only people protected by Directive 2000.12 were the officials whose names were enumerated within it; the personnel in the field remained, as they always were, an afterthought in the Pentagon's ledger.