Congress creates conundrum: What's 'sensitive'?

In its rush to straighten out security problems at Energy Department nuclear labs last year, Congress ended up creating more confusion for contractors who work for the agency, according to a recent DOE memo.

Section 3147 of the National Defense Authorization Act for fiscal 2000 included a provision penalizing Energy contractors who violate any rules "relating to the safeguarding or security of restricted data or other classified or sensitive information."

Under the law, DOE contractors can be fined up to $100,000 for releasing such data. But one small hitch was discovered after the new regulations were approved- legally, there is no such thing as "sensitive information."

In effect, Congress created a new classification category.

The department has received a number of inquiries from contractors concerning the implementation of the provision, according to a Jan. 5 memo from DOE general counsel Mary Anne Sullivan. To keep things fair, DOE won't impose any penalties until new regulations are issued that define the term "sensitive information," the memo said.

Steven Aftergood, director of the Project on Government Secrecy at the Federation of American Scientists, said the muddled provision is a "good illustration of the excess zeal that overcame Congress last year" while it tried to improve security at the Energy Department.

"This is sloppy legislating. You don't impose severe penalties for an action without describing that action with some precision," Aftergood said.

Sensitive information may not need to be classified, he said. For example, information about alarm systems at DOE nuclear weapons labs isn't classified, because it needs to be shared with emergency response personnel. But it's also not something you would want to disclose to potential enemies, Aftergood said.

DOE already has a classification for such information regarding nuclear weapons called "unclassified controlled nuclear information." Penalties already exist for disclosure of such information. But the new provisions will likely include different types of information, Aftergood said.

While the term "sensitive information" is used by the Defense Department and appears in the Computer Security Act, it does not appear in the Atomic Energy Act where the new amendment is placed.

Until new regulations are issued that define "sensitive," DOE contractors will likely err on the side of caution, Aftergood said.

"To be on the safe side, the contractors are likely to withhold more, rather than less, information. It becomes a problem in terms of cost-effective security and accountability to the public because information gets withheld indiscriminately," he said.

According to Sullivan's memo, a process is underway to develop regulations regarding the new law.

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 Brocade

    Best of 2016 Federal Forum eBook

    Earlier this summer, Federal and tech industry leaders convened to talk security, machine learning, network modernization, DevOps, and much more at the 2016 Federal Forum. This eBook includes a useful summary highlighting the best content shared at the 2016 Federal Forum to help agencies modernize their network infrastructure.

  • Sponsored by CDW-G

    GBC Flash Poll Series: Merger & Acquisitions

    Download this GBC Flash Poll to learn more about federal perspectives on the impact of industry consolidation.

  • 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 Aquilent

    A DevOps Roadmap for the Federal Government

    This GBC Report discusses how DevOps is steadily gaining traction among some of government's leading IT developers and agencies.

  • 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.

  • Sponsored by CDW-G

    Joint Enterprise Licensing Agreements

    Read this eBook to learn how defense agencies can achieve savings and efficiencies with an Enterprise Software Agreement.

  • Sponsored by Cloudera

    Government Forum Content Library

    Get all the essential resources needed for effective technology strategies in the federal landscape.


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