Pentagon lays out detailed regulations for security contractors

The Defense Department released an interim final rule Friday laying out policy regarding the use of private security contractors in war zones.

The interim rule, which is effective immediately, modifies the Code of Federal Regulations to include policies and procedures for selecting, training, equipping and overseeing private security contractors.

The Office of the Undersecretary of Defense for Acquisition, Technology and Logistics, which filed the rule, wrote that it is "of critical importance" to address insufficient policy and guidance regulating the actions of security contractors working for Defense and other agencies in war zones.

"It will procedurally close existing gaps in the oversight of private security contractors, ensure compliance with laws and regulations pertaining to inherently governmental functions, and ensure proper performance by armed contractors," the rule stated.

The rule requires combatant commanders to develop detailed guidance for security contractors operating in their geographic area of responsibility. The guidance must address a range of specific issues, from ensuring private security contractors have the proper training and certification to carry weapons to coordinating communication between PSCs and military forces.

The rule, which is open for comment until Aug. 13, states that private security contractors must document and report incidents involving weapons discharges, attacks, deaths or injuries of PSCs or as a result of action by PSCs, or destruction of property. The contractors must also report any active, nonlethal countermeasures taken in response to a perceived threat if that incident "could significantly affect U.S. objectives with regard to the military mission or international relations."

In filing the rule, Defense officials said the timing was critical, as the increase of troops in Afghanistan will result in a corresponding rise in the number of private security contractors there.

Doug Brooks, president of the International Peace Operations Association, which represents private security firms, said the rule codifies practices Defense has been implementing for awhile. It makes sense to formalize lessons learned in Iraq so they can apply in Afghanistan, he said. Until now those lessons have been addressed piecemeal through amendments to contracts with security firms.

"A lot of the contractual issues have been largely sorted out in Iraq, but we're seeing them pop up again in Afghanistan," Brooks said. "They're going to have to be sorted out in Afghanistan, which can be a little bit of a painful process, so this is good."

Erik Quist, general counsel for EOD Technology Inc., a Tennessee-based firm providing security and ordnance disposal services, agreed that most of the rule's requirements mirror what Defense has been writing into security service contracts.

"It's not new, it's not burdensome and the fact that there is now, at this level of government, an official articulation and direction of the process, that's very important," Quist said. "If we know what the process should be we don't have to fret that if something's absent from our contract, we won't know what to do. Institutionalizing these requirements under the pending new rule is an important part of the overall effort to protect the taxpayer's best interests while at the same time establish a process to utilize the very valuable role private security companies can play in supporting the government."

Stay up-to-date with federal news alerts and analysis — Sign up for GovExec's email newsletters.
Close [ x ] More from GovExec

Thank you for subscribing to newsletters from
We think these reports might interest you:

  • Sponsored by G Suite

    Cross-Agency Teamwork, Anytime and Anywhere

    Dan McCrae, director of IT service delivery division, National Oceanic and Atmospheric Administration (NOAA)

  • Data-Centric Security vs. Database-Level Security

    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.

  • Sponsored by One Identity

    One Nation Under Guard: Securing User Identities Across State and Local Government

    In 2016, the government can expect even more sophisticated threats on the horizon, making it all the more imperative that agencies enforce proper identity and access management (IAM) practices. In order to better measure the current state of IAM at the state and local level, Government Business Council (GBC) conducted an in-depth research study of state and local employees.

  • Sponsored by Aquilent

    The Next Federal Evolution of Cloud

    This GBC report explains the evolution of cloud computing in federal government, and provides an outlook for the future of the cloud in government IT.

  • Sponsored by LTC Partners, administrators of the Federal Long Term Care Insurance Program

    Approaching the Brink of Federal Retirement

    Approximately 10,000 baby boomers are reaching retirement age per day, and a growing number of federal employees are preparing themselves for the next chapter of their lives. Learn how to tackle the challenges that today's workforce faces in laying the groundwork for a smooth and secure retirement.

  • Sponsored by Hewlett Packard Enterprise

    Cyber Defense 101: Arming the Next Generation of Government Employees

    Read this issue brief to learn about the sector's most potent challenges in the new cyber landscape and how government organizations are building a robust, threat-aware infrastructure

  • Sponsored by Aquilent

    GBC Issue Brief: Cultivating Digital Services in the Federal Landscape

    Read this GBC issue brief to learn more about the current state of digital services in the government, and how key players are pushing enhancements towards a user-centric approach.


When you download a report, your information may be shared with the underwriters of that document.