DOD Dials Back Contractor Rule For Protecting Data

By Dietrich Knauth

Law360, New York (November 18, 2013, 8:35 PM EST) — The U.S. Department of Defense issued on Monday a final rule on contractors’ responsibilities for safeguarding unclassified technical data, paring down a cybersecurity rule that was criticized as being too broad when proposed in 2011.

The new rule requires contractors to take enhanced cybersecurity measures to protect DOD technical data. The cybersecurity measures are drawn from commonly used practices codified by the National Institute of Standards and Technology, including access control, awareness and training, contingency planning, and maintenance.

While the 2011 proposed rule would have required enhanced cybersecurity for a broader range of unclassified information provided by or developed for the DOD, the final rule is limited to unclassified technical documents related to DOD-funded research and development — including computer software and documents like engineering drawings, technical manuals, blueprints, data sets, studies and analyses — and to other technical information that could be used to produce, repair or modify any military or space equipment.

“After comments were received on the proposed rule it was decided that the scope of the rule would be modified to reduce the categories of information covered,” the DOD said. “This final rule addresses safeguarding requirements that cover only unclassified controlled technical information and reporting the compromise of unclassified controlled technical information.”

The change should be a welcome one for contractors, according to Elizabeth Ferrell, a partner in McKenna Long & Aldridge LLP’s government contracts practice.

“What we have now is just one small sliver of what was proposed in 2011,” Ferrell said. “It’s not a perfect rule, but it’s not as controversial as it was before.”

Some concerns remain for contractors, including the lack of a safe harbor for contractors who report breaches despite complying with the NIST standards, and some ambiguity in the definition of a cyberevent that must be reported, Ferrell said.

“Even though they’ve really narrowed this down, there are certain things that are still troubling from a contractor’s perspective,” Ferrell said.

The DOD said in the final rule that reported cyberincidents will not, by themselves, be considered evidence that a contractor had inadequate security, but flatly denied any safe harbor requests in the comments to the proposed rule, saying “the government does not intend to provide any safe harbor statements.”

While some commenters emphasized the costs of complying with additional cybersecurity steps, the DOD said that the NIST controls “represent mainstream industry practices” and that the DOD is willing to accept reasonable additional costs in exchange for better protection of its unclassified technical information.

In light of the new rule, contractors and subcontractors should quickly determine what data needs to be protected and asses their own compliance with the rule’s NIST standards, Ferrell said.

If contractors do not comply with the NIST standards, they should take steps to become compliant, or prepare to explain why the standards do not apply or why other protections provide adequate security, as allowed by the rule, according to Ferrell.

Published by Law360

3 Key Contractor Suspension Cases To Watch

By Dietrich Knauth

Law360, New York (November 6, 2013, 9:22 PM EST) — Agency decisions to suspend a company from federal contracting are rarely litigated in court, but three cases from 2013 have the chance to shape policy in areas like the treatment of contractor affiliates, the timing of a suspension and the due process rights of suspended contractors.

Suspension and debarment — suspension’s longer-term counterpart — are intended to protect the government from dealing with risky or unscrupulous businesses. But attorneys say that some recent government decisions have blurred the line between protection and punishment and raised questions about how far the government can legally go in cutting ties with disfavored companies.

“I know all the players on the government side personally, and I know their intentions are good,” David Robbins said, who heads the government contracts group at Shulman Rogers Gandal Pordy & Ecker PA and was a top U.S. Air Force suspension and debarment attorney until Nov. 1. “The challenge, however, is knowing where the edges are in what is appropriate. At least in some cases, judicial guidance could help the system.”

Here are three cases that could impact contractors in future suspension and debarment disputes:

BP Exploration & Production Co. Inc. et al. v. McCarthy et al., U.S. District Court for the Southern District of Texas.

BP PLC, along with a host of its affiliates, was suspended from government contracts in November 2012, after pleading guilty to felony misconduct and reaching a $4.5 billion settlement related to the Deepwater Horizon oil spill. BP sued the U.S. Environmental Protection Agency over the suspension in August, arguing that the EPA’s action ignored “the overwhelming evidence and record of BP’s present responsibility as a government contractor” and that the timing of the suspension was both arbitrary and punitive.

The decision to suspend BP more than two years after the spill shows some of the difficulties the government faces when balancing the need to protect itself from unethical contractors, with the need to give accused companies time to explain and address deficiencies.

Suspension is intended to protect the government from unscrupulous contractors, not to punish companies — so the timing of BP’s suspension seemed strange to some, even within the government’s suspension and debarment community, according to Robbins.

“Frankly, its probably very good for the community to have this discussion about when should these actions be kicked off, to ensure that they’re not used to punish,” Robbins said. “The EPA case, I understand there’s some tension about the timing of this, and I think it’s healthy to have the courts take a look at this.”

Agility Defense & Government Services Inc. et al. v. U.S. Department of Defense et al., U.S. Court of Appeals for the 11th Circuit.

The 11th Circuit is poised to rule on ambiguous regulations for suspending contractors that are affiliated with indicted companies, in a case that challenges the government’s effort to keep a suspension alive beyond an 18-month limit written into the Federal Acquisition Regulation.

An Alabama federal judge had lifted the suspensions of two U.S.-based affiliates of Kuwait-based Agility Public Warehousing Co. KSC, which is accused of providing false invoices defrauding the U.S. military on food supply contracts worth $8.5 billion. The U.S. could suspend the companies from receiving contracts as a protective measure, the judge found, but couldn’t keep them suspended for nearly three years without attempting to prove any wrongdoing beyond their affiliation with Agility.

The appeal could clear up an ambiguity in the FAR’s language on suspending affiliates of a company suspected of wrongdoing. The FAR rule clearly allows agencies to suspend affiliates of a suspect contractor for up to 18 months before legal proceedings are initiated, but it is less clear about whether affiliates can remain suspended once legal proceedings have been brought only against the parent company.

“The DLA case is a fascinating question about how long you can continue to have a suspension in effect,” Robbins said. “There’s some room for clarification in the regulatory language.”

In its appeal, the government argues that it needs to maintain the suspensions to prevent prime contractors from shifting business to their affiliates to avoid the consequences of suspension from government contracting. Contracting experts are divided on the lower court ruling, with some supporting the government’s position and others saying it raises serious questions about contractors’ due process rights.

The attorney overseeing Agility’s defenses, Richard Marmaro of Skadden Arps Slate Meagher & Flom LLP, said that Agility’s 128 affiliates have been suspended for too long — even longer than the three-year debarment period typical for companies that have been convicted of wrongdoing.

The affiliates in this case, and other affiliates that aren’t actively litigating their suspensions, have never even been accused of complicity with their parent company’s alleged misconduct, Marmaro said. The DLA and outside critics who say Agility could shift business to its affiliates to get around its suspension have no evidence to back up their allegations, he added.

“The affiliates are not alleged to have done anything wrong. Nor is there any allegations that the affiliates were involved in any way in the charges in the indictment against [Agility],” Marmaro said.

The 11th Circuit has a chance to set an important precedent that will protect innocent affiliates of indicted companies from being suspended for more than 18 months without any evidence being presented against them, Marmaro said.

“The purpose of the 18-month period is to give the government time to determine whether a contractor is responsible,” Marmaro said. “If, during that time period, the government’s investigation shows that the affiliate is complicit with the parent’s alleged misconduct, then the government must initiate legal proceedings against the affiliate in order to maintain the suspension.”

The DLA has lifted the suspensions of two affiliates, but those companies were forced to essentially sever all ties to the company, Marmaro said. And another affiliate, Gulf Catering Company for General Trade and Contracting WLL, has launched a separate lawsuit in Georgia federal court to challenge its suspension.

MG Altus Apache Co. v. U.S., U.S. Court of Federal Claims.

A case decided in May could impact contractors that believe suspensions or debarments violate their rights to due process.

In MG Altus Apache Co. v. U.S., the U.S. Court of Federal Claims rejected a contractor’s challenge to a secret vendor vetting blacklist that effectively debarred a trucking contractor in Afghanistan without its knowledge. The contractor, unaware it had been placed on a vendor vetting blacklist, wasted time and money submitting contract bids that had no chance of success, and eventually sued, arguing that the U.S. Army had violated its due process rights by secretly debarring it.

Agencies are not generally allowed to use de facto debarments, like the secret vendor blacklist, to get around the rules regarding notice and due process, according to Todd Canni, an attorney at McKenna Long & Aldridge LLP and a former Air Force suspension and debarment attorney.

The court found the Army had used a de facto debarment against MG Altus Apache but had been justified in doing so because of national security concerns. According to Canni, this finding risks encouraging other contracting personnel to use similar “blacklists,” rather than formally referring matters to their agency suspension and debarment official.

Steven Shaw, a senior of counsel at Covington & Burling LLP and a former debarment official for the Air Force, says secret blacklists not only are unfair to contractors, but also raise the risk that the government will continue to do business with unethical companies. A formal debarment or suspension excludes the company from contracting with any federal agency, but secret lists create a risk that the company will continue to get contracts if the blacklisting agency doesn’t share its information within the government.

“This concept of secret lists is something that always bothered me at the Air Force,” Shaw said. “If you keep it quiet, you are protecting one agency on one program, and meanwhile you’re allowing the entire federal government to be at risk of contracting with this particular company. It’s a huge disservice to the government and the taxpayers.”

The Army said it couldn’t tell MG Altus Apache about the blacklisting because its evidence was classified, but that doesn’t mean the debarment decision must be classified too, Shaw says.

“The evidence itself can be classified, but you can design the administrative record in such as way as to support a suspension or debarment on a classified program. … It’s cumbersome, but you can do it,” he said.

4 Tips For Navigating Bid Protests Outside The US

By Dietrich Knauth

Law360, New York (September 27, 2013, 7:32 PM EDT) — As U.S. defense companies ramp up their search for opportunities abroad, getting familiar other nations’ evolving bid protest practices can be a helpful step in ensuring they are treated fairly in competitions, experts say.

The U.S. procurement system is unique in its long history of allowing prospective contractors to challenge government contract decisions, and despite domestic criticism of the delays and litigiousness that sometimes result, other nations continue to look to the U.S. as they establish or amend their own versions of bid protests.

Protest systems are increasingly seen as essential to a good public procurement framework, and are encouraged by the United Nations Commission on International Trade Law, the World Trade Organization and the U.S., which insists that partners in free trade agreements, including the North Atlantic Free Trade Agreement, have some kind of bid protest system.

“Bid protests are a standard part of procurement reform all around the world now,” said Daniel Gordon, associate dean for government procurement law at George Washington University. “A bid protest mechanism is typically an unusually efficient way of attaining both transparency and accountability in government contracting.”

Advocates of the U.S. system say allowing private companies to enforce procurement rules increases transparency, reduces corruption and encourages competition, allowing governments to get better value for their purchases. But to take advantage of bid protests in other nations, U.S. companies will have to keep in mind that the rules and culture surrounding bid protests can vary significantly.

Here are four tips for U.S. defense companies looking to take advantage of bid protests abroad:

Recruit Local Counsel

As they adjust to decreased U.S. military spending, American defense companies will have to do business in nations where bid protests are not as ingrained in the procurement process.

Although many countries seem to model their protest systems on the U.S., the rules won’t be the same everywhere. In the U.K., for example, protests are handled in court. In Germany, procurement protests go to specialized administrative bodies.

“Every country is different, and even within the E.U., the 28 member countries have different laws, including different protest laws,” Gordon said. “They have 28 different ways of solving problems.”

Contractors should partner with local counsel to help them navigate the different rules, according to Allen Green, a partner at McKenna Long & Aldridge LLP.

“As you move outside the U.S., E.U. and Canada, you’re really entering into public procurements that are much less transparent. They’re going to have, to varying degrees, some form of protest procedures, but the likelihood of success is something that companies are going to have to think about and work through with knowledgeable local counsel,” Green said.

Adjust Your Expectations

The U.S. bid protest system is stronger in many ways than other nations’, and U.S. companies will have to adjust their expectations when getting involved in protests abroad.

The U.S. allows protests to negate or overturn contract decisions, even after the signing of a contract, and offers an automatic stay that halts work on procurements that are protested at the U.S. Government Accountability Office, which handles most U.S. bid protests and is generally seen as a fast and cheap option for protesters.

American contractors can also protest in the U.S. Court of Federal Claims, which offers legally binding rulings through more extensive litigation and can serve as a backup if a GAO protest fails. Such a system is rarely present in other nations.

In growing markets like China, India, Korea, the United Arab Emirates and Saudi Arabia, U.S. companies will have to temper expectations that bid protests will be as effective as they are in the U.S., Green said.

“If all goes south and you’ve been badly treated, there’s going to be a much narrower spectrum and much less done than  there is the U.S.,” Green said.

In places with less transparent governments, protests could be a dicey proposition even when procedures are in place. University of Maryland law professor Daniel Mitterhoff recently studied a Chinese bid protest that was ignored by the Chinese government for nearly seven years because it fell into a legal grey area between two of China’s multiple bid protest systems.

“In some countries it doesn’t look like there’s a lot of progress toward a meaningful, effective protest system even when they exist on paper,” Gordon said.

Monitor Developing Bid Protest Regimes

Companies should keep an eye on markets that are developing or have recently developed bid protest regimes. Bid protests are growing at an uneven pace across the globe, according to Gordon, who has witnessed the rise of bid protests firsthand.

As the former head of the bid protest division at the GAO, he was consulted by foreign governments interested in setting up their own protest mechanisms, including Norway, Turkey and Tanzania, all of which have protest systems now. He has continued that outreach as an academic, recently working with officials from Vietnam, Morocco, Algeria, Libya and Tunisia — and says international interest in bid protests remains strong.

“Besides an interest in improving legal systems abroad, American companies want to export, and you want to have a solid procurement system overseas to ensure that American companies are treated fairly,” Gordon said of the Commerce Department’s interest in promoting bid protests overseas. “You don’t want to have corruption and you don’t want to have favoritism.”

Ralph White, who currently heads the GAO’s bid protest team, said foreign visitors continue to ask GAO about its protest policies. Not only does the U.S. have the longest tradition of hearing bid protests — a system that began informally in the 1920s and was codified by regulations in the 1970s and the Competition in Contracting Act in 1986 — the U.S. also spends far more on contracts than any other nation, making it a natural source of best practices for protests, White said.

“We end up with visitors from all over the world coming to Washington from other governments. Invariably, they want to talk about bid protests and they are fascinated and amazed that the U.S. government will put itself through this process,” White said. “The idea that you could challenge who it is the Defense Department is giving contracts for missile defense, they’re just amazed by it.”

For governments challenged by corruption and bribery, bid protests are seen as a crime-fighting tool, in a way that they aren’t in the U.S., which will help spur more countries to adopt them, Gordon said.

“Why exactly does having a police car on the side on the side of the road prevent people from driving 80 miles per hour? At least on the margins it causes people to be somewhat more careful,” Gordon said. “Crime hates sunshine, and [protests] provide sunshine to the contracting process. It provides vitamin T, it provides transparency.”

Prepare for Backlash and Reforms

While governments value the transparency and accountability that protests bring, they also struggle with the delays and litigiousness that are part of the package. The U.S. has seen frequent calls for reform, including ideas like charging a fee for “frivolous” protests, raising the dollar-value threshold for which contracts can be protested, and a U.S. Department of Defense proposal that would force contractors to choose between the GAO and the Court of Federal Claims, rather than allowing them to retain the court as a backup plan.

As protests rise across the globe, other governments will face similar pushback, Gordon said. Ten years ago, while Gordon was at GAO, the government of Norway invited him to give advice on setting up a protest forum. It was successful, but after the forum was in place, Gordon said he began to hear familiar complaints out of Norway’s government.

“Within the first two or three years of setting up the bid protest forum there was criticism that there were too many bid protests being filed, and I had to chuckle to myself, because I’d been hearing the same criticism back at home,” Gordon said. “Government officials will always tell you that there are too many protests.”

 

Published by Law360

 

SBA Rule Will Boost Prosecution of Small-Biz Contract Fraud

A Small Business Administration rule finalized Friday says that fraudulently obtained small business contracts provide no value to the federal government, a change that will increase the number of enforcement actions by clearing the government to seek repayment for the entire contract.

The rule implements part of the Small Business Jobs Act of 2010, which says that when a company wins a contract by willfully misrepresenting its small business status, the government’s presumed loss is the value of the contract.

While the law already provided for criminal and civil penalties, including False Claims Act liability, the government had a hard time winning these cases because rulings like the one in Ab-Tech Construction v. United States had made it difficult to establish damages. In that 1994 case, the Court of Federal Claims limited the government’s recoverable damages because the contractor had provided the agreed-on services.

But the SBA regulation, which takes effect Aug. 27, will allow prosecutors and private relators to pursue fraud much more easily, under the assumption that contracts obtained through misrepresentation have no value to the government. This puts the entire value of the contract at stake.

“I expect to see a substantial uptick in prosecutions,” said Richard Oliver, a partner with McKenna Long & Aldridge LLP. “There have been very few prosecutions for false size certifications over the last 20 years. The only prosecutions we’ve seen have been extremely blatant situations.”

Read the full article on Law360: https://bit.ly/2Kwp4hO

DC Circ. Deals Another Blow To Rumsfeld Torture Suits

By Dietrich Knauth

Law360, New York (June 15, 2012, 7:47 PM EDT) — The D.C. Circuit ruled Friday that a former U.S. government contractor could not sue former Defense Secretary Donald Rumsfeld for monetary damages arising from his alleged torture in Iraq, dealing another blow to a damages theory that has stumbled in two other appeals courts.

The circuit court ruled that the Supreme Court’s 1971 decision in Bivens v. Six Unknown Named Agents of Federal Bureau of Narcotics — a decision allowing a citizen to sue for monetary damages where no other federal remedy was provided for the protection of a Constitutional right — had never been applied “in a case involving the military, national security, or intelligence.”

Chief Judge David Sentelle pointed out that the Supreme Court very rarely applies Bivens to new causes of action — only twice in the past 41 years, in fact.

“The implications of a Bivens action…is not something to be undertaken lightly,” Judge Sentelle wrote.

U.S. citizens working under Iraq contracts have alleged in the D.C. and Seventh circuits that they were detained and tortured in Iraq and sought damages under Bivens. The Seventh Circuit case is awaiting an en banc ruling.

The theory has also has failed in the Fourth Circuit, which ruled that convicted terrorism conspirator Jose Padilla could not pursue Bivens remedies against Rumsfeld. The Supreme Court declined to take up an appeal of Padilla’s case on June 11, leaving the Fourth Circuit decision untouched.

The Seventh Circuit went the furthest with the theory, ruling in August that Rumsfeld did not have immunity in a suit brought by contractors Donald Vance and Nathan Ertel. That ruling, however, was vacated in October, when the entire Seventh Circuit decided to rehear the case en banc. No ruling has yet been reached by the full Seventh Circuit.

There is no disagreement among the circuit courts, because the Seventh Circuit rehearing means the original split decision, which was the subject of a contentious dissent, might as well have not happened, said David B. Rivkin of Baker Hostetler LLP, who represents Rumsfeld in the Seventh Circuit.

“I’m very comfortable predicting that we’ll do well and that the balance of the Seventh Circuit will come to the right decision,” Rivkin said.

The anonymous plaintiff, John Doe in court filings, alleged that Rumsfeld personally approved torture techniques, including isolation and sleep and sensory deprivation, and later ordered those practices to be used at Camp Cropper in Baghdad, where Doe was held.

But the D.C. Circuit ruled that the judicial branch should not interfere in the prosecution of wars, which are the province of the political branches of government.

“Military detainee cases implicate similar concerns regarding the conduct of war, the separation of powers and the public scrutiny of sensitive information,” Judge Sentelle wrote.

Jesselyn Radack of the Government Accountability Project, one of Doe’s attorneys, said Doe would take the fight to the Supreme Court if need be.

“It’s a disappointing decision, and we’ll either ask the full circuit to rehear the case en banc or file a petition of certiorari to the Supreme Court,” Radack said.

Radack said her client’s suit seeks an expansion of Bivens but argued that “these are pretty horrific circumstances that maybe warrant an expansion.”

“The Supreme Court has never applied a Bivens remedy to a military or intelligence situation, but we’ve never been in this kind of situation where we’ve tortured our own people in the guise of national security,” Radack said. “This is a scary holding that our military can capture a U.S. citizen and hold them for months and months without trial counsel and judicial review and torture them and they have no redress.”

The courts must be able to protect the constitutional rights of U.S. citizens, even in war zones, Radack added, saying that the D.C. Circuit’s military exception could be an enormous loophole during a period of “indefinite war” that seems to involve many areas of the world at once.

Doe claims he was blindfolded, handcuffed and repeatedly kicked in the back during an initial interrogation in November 2005, then taken to Camp Cropper, a U.S. military prison where he was repeatedly choked, exposed to extreme cold and continuous artificial light, and interrupted whenever he tried to sleep by guards who banged on his door or blasted heavy metal and country music into his cell. He later was moved into a cell with suspected terrorists who knew about his military ties, leaving him in constant fear for his life, according to the complaint.

The U.S. Department of Justice, which represents Rumsfeld, says Doe was detained on suspicion that he accepted bribes from Iraqi customs officials to allow insurgents, weapons and other contraband to pass through the border between Syria and Iraq, as well as for possible collaboration with Syrian or Iranian intelligence services, according to court filings.

But Doe says he was a translator for a U.S. Marines intelligence gathering team, and that he was detained because the U.S. military wanted to keep him quiet about secret negotiations with with Abdul Sattar Abu Risha, a Sunni sheik who became a key U.S. ally and led an uprising against al-Qaida before being assassinated in 2007.

Doe is represented by Michael Kanovitz and Gayle Horn of Loevy & Loevy and Jesselyn Alicia Radack of the Government Accountability Project.

The case is Doe v. Rumsfeld et al., case number 11-5209, in the U.S. Court of Appeals for the District of Columbia Circuit.

Published by Law360

US Fails To Shield Contractors From $920M In Afghan Taxes

By Dietrich Knauth

Law360, New York (May 14, 2013, 9:09 PM EDT) — The U.S.’ failure to enforce nontaxation agreements has allowed Afghanistan to collect more than $920 million in improper taxes from U.S. contractors, according to a new report that experts say highlights the persistent challenge of coordinating federal agencies to ensure war spending isn’t wasted.

The Special Inspector General for Afghanistan Reconstruction, or SIGAR, reported Tuesday that his office examined $921 million in business taxes and penalties levied against 43 contractors supporting U.S. rebuilding efforts in Afghanistan, in spite of agreements meant to ensure that U.S. contractors aren’t taxed. Those agreements “appear to be failing in their purpose,” in part because the U.S. Department of Defense, Department of State and the U.S. Agency for International Development have failed to make a coordinated effort to push back against improper taxes, often leaving contractors to fend for themselves.

“It’s disturbing that the Afghan government is targeting American contractors with unjust taxes and intimidation,” Special Inspector General John F. Sopko said. “It’s even more disturbing that U.S. agencies are letting it happen — all at the expense of American taxpayers, who have already shouldered a heavy burden on Afghan reconstruction. This needs to end.”

Of the $921 million examined by SIGAR, $93 million falls clearly under a tax category that both the U.S. and the Afghan government agreed should be exempt, and SIGAR believes that many of the remaining taxes are also illegitimate.

Congress took quick notice of SIGAR’s report, and Rep. Peter Welch, D-Vt., on Tuesday reintroduced legislation that would block all U.S. taxpayer assistance to Afghanistan until a new bilateral agreement on taxes is reached.

“It is incomprehensible that the government of Afghanistan, with its abysmal track record of corruption, would actually think it is a good idea to tax assistance provided by the American taxpayer,” Welch said. “We shouldn’t give another dime to the Afghan government until they agree to stop ripping off the American taxpayer.”

Experts say that SIGAR’s report is just further evidence of the difficulties that the U.S. faces in getting USAID, DOD and the State Department on the same page when it comes to wartime contracting issues. The recently closed office of Sopko’s counterpart in Iraq, the Special Inspector General for Iraq Reconstruction, has recommended creating a new federal agency to oversee rebuilding efforts in future contingency operations, but the agencies have resisted those recommendations, and some contractors have also opposed the plan as creating another layer of bureaucracy.

Charles Tiefer, a law professor at the University of Baltimore and a former member of the Commission on Wartime Contracting, said the U.S. agencies need to present a more unified front on wartime contracting, whether or not a new agency is introduced.

“There needs to be some structural change,” Tiefer said. “If the agencies coordinated and presented a strong and unified stance to the Afghan government, they could at least reduce the scale of improper Afghan taxing of American efforts.”

Fragmented planning for rebuilding contracts greatly increases the risk of waste and fraud, and that’s especially true in Afghanistan, where corruption is part of the culture, and where President Hamid Karzai’s government has tried to maximize its share of the U.S. and international cash that supports its institutions, Tiefer said. Afghanistan’s tax collectors don’t respect the tax exemption agreements signed by its diplomats, and the tax issues seem to be an echo of previous efforts to force contractors to hire a new Afghan security force in place of private guards, Tiefer said.

“The strategy here on the Afghan side may appear chaotic but in fact comes from the Karzai administration, which treats American contract funding in several ways as its very own piggy bank,” Tiefer said. “The U.S. taxpayer puts up money to build schools and infrastructure in Afghanistan, and the Afghan government turns around and engages in double dipping, getting both the U.S. funded project and skimming extorted taxes as well.”

Contractors say the report simply adds concrete data to the reality they’ve been facing for some time. The Professional Services Council, a contractor trade group, agreed with SIGAR’s calls for better coordination between agencies and more training on the tax exemption agreements for U.S. contracting officers, to prevent representatives of the Afghan government from exploiting inconsistencies in an effort to “shake down” contractors.

“The report confirms what PSC has long argued in letters, white papers and meetings with government officials: The U.S. government’s lack of a unified position in resolving the Afghan government’s inappropriate taxation of U.S.-funded contracts has hindered contractors’ efforts to support the U.S. government in Afghanistan,” said Alan Chvotkin, general counsel and executive vice president of PSC. “As the IG found, the lack of response increases the costs of U.S. government projects in Afghanistan and diverts U.S. funding from program objectives specifically defined by Congress and the contracting agencies.”

Because of tax disputes, the Afghan Ministry of Finance has restricted contractors’ freedom of movement, hurting the ability of contractors to support U.S. missions, and has even arrested at least one contractor because of unresolved tax issues, SIGAR reported.

Some U.S. agencies’ contracting officers do not appear to understand Afghanistan’s tax laws and have improperly reimbursed contractors for taxes paid to the Afghan government, and contractors have begun billing the U.S. government for the tax costs, or adjusting their bids to account for increased costs due to the Afghan taxes, according to SIGAR. The U.S. agencies have paid improper taxes, through contractor reimbursement, without helping contractors fight the taxes or helping contractors obtain tax-exemption certification ahead of time, the report found.

The contractors caught in the middle may face additional trouble down the road, since billing the government for improper taxes may go against federal regulations, Tiefer said.

“These contractors may be violating the rules on reimbursement when they pass on taxes that they shouldn’t have paid,” Tiefer said. “They’re getting away with it now, and that means that in some ways they’re happier avoiding friction with the Afghan government, at the cost of milking the American taxpayer through reimbursement.”

SIGAR recommends that the secretary of state take the lead in developing a consistent, unified position on what the U.S. government deems appropriate taxation of contractors, and make efforts to recover any improper tax payouts. But while the DOD concurred with SIGAR’s recommendations, State resisted, saying it “did not explicitly agree or disagree,” while arguing that the agencies already have a unified position. State also said it “neither agreed nor disagreed” on recommendations to recover tax payments.

The State Department also questioned SIGAR’s authority to examine issues related to the tax treatment of contracts, causing SIGAR to write that it is “concerned that State chose to focus initially on the bureaucratic question of which oversight agency is the appropriate one to examine this issue, rather than turning its attention to devising solutions to the problems we identified in this report.”

While the tax issue is serious on its own, it also points to a larger pattern of the Afghan government trying to maximize what it can take from U.S. and internationally funded rebuilding efforts, Tiefer said. Afghanistan previously banned contractors from hiring foreign-owned private security companies, forcing them to hire a new Afghan government agency, the Afghan Public Protection Force, at a higher price than the contractors were originally paying.

The focus on maximizing short-term payouts doesn’t bode well for the future, Tiefer said, especially as U.S. forces plan to exit Afghanistan and turn over the country’s security to its fledgling armed forces in 2014.

“Supplying their treasury by extorting tax payments from the US treasury is a very short-term strategy, and they are materially diminishing their country’s prospect for surviving after American troops pull out and some of the reconstruction effort drops off,” Tiefer said. “This report shows that the Afghan government is sucking only too much from the teat of the American treasury, and needs to be weaned off its rich diet.”

Foreign aid projects make up an enormous part of Afghanistan’s economy — 97 percent, according to a Senate Foreign Relations Committee report from 2011. Since 2002, Congress has appropriated over $89 billion to U.S. government agencies, including DOD, State and USAID, for humanitarian and reconstruction programs and projects in Afghanistan, according to SIGAR.

Published by Law360

US Agencies Get Major Update To Cybersecurity Guidelines

Under the Information Security Management Act, the Office of Management and Budget and the NIST take the lead in setting minimum security requirements used across the federal government, such as giving tips for secure passwords or requiring physical security for sensitive computer systems. The NIST standards have governed federal cybersecurity steps in the absence of federal legislation, and the overhaul is the first such update since 2005.

“This update was motivated by the expanding threats we all face,” project leader and NIST fellow Ron Ross said in a statement. “These include the increasing sophistication of cyberattacks and the fact that we are being challenged more frequently and more persistently.”

The revision’s new assurance controls will help agencies have confidence in the security of their systems and give guidance to contractors that develop information systems, information technology component products and services for the government, according to Ross, who said the focus on trustworthiness in the federal information systems supported the NIST’s slogan of “Build it right, then continuously monitor.”

Contractors may welcome the update as an improvement over ad hoc rules pursued separately by separate agencies. In comments submitted to the NIST on April 8, the Professional Services Council urged the government to halt ongoing efforts to create cybersecurity contract requirements until the NIST framework was in place.

“We strongly believe that the NIST cybersecurity framework should be developed prior to the further development or implementation of new acquisition-specific cybersecurity requirements,” PSC President and CEO Stan Soloway said. “To ensure that consistency is achievable by agencies in both the cybersecurity framework and the federal acquisition arena, PSC recommends that the [Federal Acquisition Regulation] and [Defense Federal Acquisition Regulatory Supplement] initiatives be suspended until the initial NIST framework is completed.”

The new guidelines promote cutting-edge security controls aimed at addressing evolving threats — particularly issues related to mobile and cloud computing, insider threats, supply chain risks, advanced persistent threats, and other areas that have evolved greatly over the past eight years, the NIST said.

To address supply chain risks — an area that has been the focus of recent reports from the Senate Armed Services Committee and House Intelligence Committee — the guidelines recommend that the government sometimes use “blind or filtered buys” to withhold the ultimate purpose of electronic parts from the contractors who supply them.

The guidelines also encourage agencies to offer incentives to contractors that are open about their procedures for vetting the security of their electronic parts and subcontract suppliers, something the U.S. Department of Defense is addressing as it implements the 2013 National Defense Authorization Act. The NDAA provided a safe harbor for contractors who have DOD-approved vetting procedures, while requiring other contractors to pay for the cost of replacing counterfeit electronics that supply to a military system.

Previous NIST guidelines, as well as a change in the 2013 National Defense Authorization Act, have pushed contractors to report data breaches affecting government systems. The 2013 NDAA included a last-minute amendment added by Senate Armed Services Committee Chairman Carl Levin, D-Mich., that required cleared contractors to report on cyberattacks and grant the DOD access to information systems for security checks.

Contractors complained that the amendment’s initial language would have provided the DOD with open-ended access to data — even to the point of long-term confiscation of computer servers — with very few controls on how that information would be used or safeguarded. While the final version of the NDAA limits the amendment in a few key ways, requiring the DOD to safeguard trade secrets and commercial information and preventing the DOD from sharing the information outside of the agency, some said the change didn’t go far enough toward addressing contractors’ concerns.

Published on Law360

Obama’s Cybersecurity Order Could Squeeze Contractors

By Dietrich Knauth

Law360, New York (February 26, 2013, 8:01 PM EST) — President Barack Obama’s recent cybersecurity executive order envisions a more centralized approach to protecting the government from hackers, but contractors worry a slew of new costs and burdensome information-sharing requirements could also accompany the well-intentioned move.

Government contractors, already a target for hackers because of their closeness to government data, are among the biggest groups affected by Obama’s Feb. 12 cybersecurity executive order, which pushes federal agencies to work more closely with defense contractors, banks, electric power companies, communications providers and other critical infrastructure operators through voluntary security standards and increased dialog about cyberthreats. The order and an accompanying policy directive also direct the agencies to consider changing the Federal Acquisition Regulation to include cybersecurity concerns in new government contracts.

But the government’s effort to incorporate cybersecurity standards into acquisition planning, and to harmonize existing procurement requirements could be a mixed bag for contractors. While the new standards will likely carry new compliance costs, those additional costs could be offset by smoothing out a “Tower of Babel” of conflicting agency-by-agency and even contract-by-contract approaches, according to Crowell & Moring LLP partner David Bodenheimer.

“It is not all downside. An upside to a FAR regulatory scheme for cybersecurity would be greater uniformity and less compliance burden on contractors,” Bodenheimer said. “One of the problems right now, for federal contractors, is having to comply with a host of changing federal regulations at the agency level.”

But many are concerned that new regulations arising out of the executive order will ask too much of contractors, especially because the government will have to frequently update its standards in order to combat rapidly evolving cyberattacks and new techniques employed by hackers.

“The goal sounds like a good idea, but we’ll have to wait and see what’s proposed,” said Elizabeth Ferrell, a partner at McKenna Long & Aldridge LLP. “Consistency would be helpful but there’s always concerns that the standards will be too strict and too much of a burden on contractors.”

Contractors will also be asked to take part in the executive order’s voluntary information sharing program, which is based on a pilot program already underway between the DOD and some defense contractors. As long as the information sharing remains voluntary, contractors, as with other companies affected by the order, will closely watch as the government settles on a mix of incentives and penalties to encourage the cooperation they’re seeking.

Many companies are worried that reporting on cyberthreats and data breaches will open them to new liability, from exposure of trade secrets and proprietary data, to liability for inadvertently disclosed personal information, to damaged corporate reputations. Contractor groups, including the Professional Services Council and TechAmerica, have already called for granting indemnification to companies that meet cybersecurity standards or exempting their disclosures from Freedom of Information Act requests, steps that would assure contractors, but would require legislative action.

In addition to the reporting risks faced by other companies affected by the order, contractors face a few unique risks when reporting data breaches or cyberattacks — particularly if they lead the government to see the contractor as a less secure partner than potential competitors. Many federal agencies now include information security and safeguards as an element of past performance and experience during a contract competition, according to Bodenheimer.

“That breach may be used against it in other contexts as well, such as being penalized in a competitive source selection,” Bodenheimer said.

Information also carries more risk for contractors than most private sector companies, because government contractors are subject to a number of additional statutory, regulatory and contractual reporting requirements. Noncompliance with one of those additional reporting requirements could open up government contractors to accusations of procurement fraud or whistleblower suits under the False Claims Act.

“Government contractors, by nature, are very cautious because there are a lot of potential liabilities associated with any kind of noncompliance,” Ferrell said. “False Claims Act liability certainly is one of those, so I think that would be on a list of potential lawsuits that a company might face that might originate from voluntary disclosures.”

There is also the fear, perhaps well-grounded, that the voluntary information sharing framework in the executive order will be a mere stepping stone to a mandatory reporting requirement in the future.

Defense contractors, whose early efforts provided a framework for the executive order’s information sharing program, experienced something similar in December, when the 2013 National Defense Authorization Act required contractors with security clearances to report cyberattacks and system breaches.

“If I was an industry member, I would wonder if we’ll see a broader mandatory disclosure requirement that will apply to non-cleared contractors,” said Jon Burd, a government contracts attorney at Wiley Rein LLP. “None of that is on the immediate horizon, but  it’s reasonable to wonder out loud whether that is a path that we may head down in the not too distant future.”

Published by Law360

Gov’t Contracting Slump Could Spark PE Feeding Frenzy

With federal contracting budgets on the wane, private equity firms are looking to snatch up bargains as contractors streamline their businesses and sell off divisions that could see reduced profits or contribute to organizational conflicts of interest.

This should be a busy year for mergers and acquisitions in the government contractor market, experts said, attributing part of the change to declining budgets and the uncertainty around sequestration, a series of automatic budget cuts set to slash about $52 billion from 2013 federal spending unless Congress agrees on an alternative deficit reduction package by March 1. Private equity firms will look to profit from contractors’ belt-tightening, while also seeking to purchase smaller companies in hot areas that will continue to see government investments, such as cybersecurity.

“Government contractors are looking to shed some of their businesses and divisions that are not going to give them the returns they had captured in previous years,” said Scott M. Heimberg, a partner with Akin Gump Strauss Hauer & Feld LLP. “I think that gives some opportunities to private equity companies who are looking for bargains out there.”

Check out the full article, published by Law360: https://bit.ly/2XskO9d