Should Commissary Clerk Jobs be Classified as 'Sensitive' National Security Positions?

Sen. Jon Tester, D-Mont., focused Wednesday’s hearing on proposed rules to specify which federal positions are deemed “sensitive." Sen. Jon Tester, D-Mont., focused Wednesday’s hearing on proposed rules to specify which federal positions are deemed “sensitive." Charles Dharapak/AP file photo

Lawmakers on Wednesday called for greater specificity in determining which information and federal jobs are designated as sensitive, saying over-classification damages national security.

Sen. Jon Tester, D-Mont., chairman of the Homeland Security and Governmental Affairs subcommittee with oversight of the federal workforce, focused Wednesday’s hearing on proposed rules to specify which federal positions are deemed “sensitive,” as well as a legal ruling that stripped employees in these positions of their right to appeal firings and suspensions with the Merit Systems Protection Board. Tester attempted to pinpoint, without success, whether the new regulations would limit the designation to only positions that truly required it.

If agencies can “arbitrarily determine which positions are sensitive,” Tester asked “are we going to end up with another [Edward] Snowden incident or end up with another Navy Yard shooter incident because there’s too much to do and people are going to cut corners?”

Sen. Rob Portman, R-Ohio, said the same logic applied to classified data. “If everything is classified, then nothing is classified,” he said.

The issue of designating positions as sensitive -- and employees occupying those positions being stripped of their appeals rights -- made waves over the summer with federal employee and good government groups, which claimed guidelines spelling out which positions are sensitive were far too broad and could therefore apply to the entire Defense Department, for example.

The Office of Personnel Management and the Office of the Director of National Intelligence, which issued the proposed guidance, defended their rule Wednesday, saying designation of positions as “sensitive” is nothing new and they were only attempting to bring clarity and governmentwide standardization.

“The proposed rule is not intended to increase or decrease the number of positions designated as national security sensitive,” Tim Curry, an OPM official, told the panel, “but is intended to provide more specific guidance to agencies, in order to enhance the efficiency, accuracy and consistency with which agencies make position designations.”

Tester pointed to an example of a Defense employee, however, who worked as a clerk in a commissary and was terminated because his position was sensitive and he held personal debt.

“It escapes me how a grocery store clerk could be put at the same level as someone at the Defense Department who has access to really important classified information,” Tester said.

Curry said because the employee had access to food, he could have an impact on national security, hence the sensitive designation. He added that while OPM and ODNI set the general standards, each agency is ultimately responsible for determining its own sensitive positions.

These positions do not necessarily overlap with positions that require security clearances. Federal employee groups warned supervisors in national security roles have unilateral power to both designate a position as sensitive and dismiss the employee in that position without offering an explanation, as the employee would not be able to appeal the decision to MSPB.

“That, senators,” said David Borer, general counsel at the American Federation of Government Employees, “is likely to be an irresistible invitation to abuse.” 

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.

  • Federal IT Applications: Assessing Government's Core Drivers

    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

  • Toward A More Innovative Government

    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.

  • From Volume to Value: UK’s NHS Digital Provides U.S. Healthcare Agencies A Roadmap For Value-Based Payment Models

    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.

  • GBC Flash Poll: Is Your Agency Safe?

    Federal leaders weigh in on the state of information security


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