Now we know how President Richard Nixon really viewed the role of secretary of Defense, thanks to riveting excerpts of Oval Office conversations (those tapes again!) in the August issue of Vanity Fair.

In April 1972, as the U.S. was stepping up the air campaign against the North Vietnamese communists, Nixon was growing increasingly frustrated with what he perceived as the military's slow response to the requirements of the day, both in Indochina and Washington. When a briefing he ordered for 7 a.m. on April 3 wasn't delivered until 8:30 a.m., the earliest Secretary of Defense Melvin Laird himself could get to the White House (presumably Laird was busy running the war), Nixon wasn't having it.

Later that day, Nixon shared his frustrations with Thomas Moorer, the chairman of the Joint Chiefs of Staff:

Nixon: I'm not going to have that kind of crap anymore. From now on, that man is to have his ass over here in this office at seven o-clock every morning. Is that clear?

Moorer: Yes, sir. He'll be here.

Nixon went on to criticize the air campaign, questioning the number of sorties the Air Force was flying against targets in North Vietnam ("And good God! In the Battle of the Bulge they were able to fly even in a snowstorm. Now what in the hell is the matter with the Air Force that they are unable to, to conduct offensive operations in this area? . . . They're to knock off all the parties, is that clear?")

Before Moorer left, Nixon had a message for his boss.

Nixon: When an order goes out, it's got to go from me. The secretary of Defense is not commander in chief. The secretary of Defense does not make decisions on these kinds of things.

Moorer: I understand that, Mr. President.

Nixon: He's a procurement officer. That's what he is and not another goddamn thing.

Katherine is deputy editor of Government Executive Media Group, a division of Atlantic Media, where she oversees editorial coverage for GovExec.com and Government Executive magazine. She previously was executive editor of Nextgov.

By using this service you agree not to post material that is obscene, harassing, defamatory, or
otherwise objectionable. Although GovExec.com does not monitor comments posted to this site (and
has no obligation to), it reserves the right to delete, edit, or move any material that it deems
to be in violation of this rule.

Database-level encryption had its origins in the 1990s and early 2000s in response to very basic risks which largely revolved around the theft of servers, backup tapes and other physical-layer assets. As noted in Verizon’s 2014, Data Breach Investigations Report (DBIR)1, threats today are far more advanced and dangerous.

In order to better understand the current state of external and internal-facing agency workplace applications, Government Business Council (GBC) and Riverbed undertook an in-depth research study of federal employees. Overall, survey findings indicate that federal IT applications still face a gamut of challenges with regard to quality, reliability, and performance management.

PIV- I And Multifactor Authentication: The Best Defense for Federal Government Contractors

This white paper explores NIST SP 800-171 and why compliance is critical to federal government contractors, especially those that work with the Department of Defense, as well as how leveraging PIV-I credentialing with multifactor authentication can be used as a defense against cyberattacks

This research study aims to understand how state and local leaders regard their agency’s innovation efforts and what they are doing to overcome the challenges they face in successfully implementing these efforts.

The U.S. healthcare industry is rapidly moving away from traditional fee-for-service models and towards value-based purchasing that reimburses physicians for quality of care in place of frequency of care.