recommended reading

Feds may weigh changes to information security requirements

Before a military employee allegedly leaked a mountain of classified documents to WikiLeaks, reportedly by downloading data to a music CD, the White House had been in the middle of updating rules on reporting agency network weaknesses. Obama officials have not said whether they will revise the reporting guidelines further after agencies complete self-evaluations of their classified information protections.

Under Office of Management and Budget rules issued in April 2010, chief information officers have been working within the confines of the 2002 Federal Information Security Management Act to shift to an automated process for complying with the law's paperwork requirements. Instead of requiring managers to check boxes in reports to indicate compliance with security protocols, special software will continuously collect metrics on the status of controls so that CIOs have a more accurate and comprehensive view of vulnerabilities. Starting this month, CIOs must update the Homeland Security Department monthly, rather than quarterly, on their overall security postures by feeding summaries of these assessments to a central, governmentwide inbox called CyberScope.

Allan Paller, director of research at the SANS Institute, a computer security think tank, suggested OMB refine the April FISMA guidance by directing CIOs to first automate and monitor what a consortium of nonprofit and agency specialists have defined as the 20 most critical FISMA controls.

The top 20 include hardware and software configurations, wireless device control, and data leakage protection. Attempting to tackle the nearly 150 standard controls all at once could dilute agencies' time, money and ultimately security, Paller said. "The 20 critical controls make the defense against that type of attack extremely high priority," he added.

OMB on Monday issued separate guidelines to agency heads on safeguarding classified information that require a one-time report on compliance with information assurance controls, as well as adherence to other existing policies, such as steps to evaluate the trustworthiness of personnel. Agencies were told to conduct similar inspections regularly but, as of now, are not required to continue reporting on these self-assessments. White House officials on Wednesday said they have not yet announced if they will call for additional reports on the ongoing self-evaluations.

Other security specialists discouraged the government from rushing to change the current OMB requirements for reporting on computer security in response to the WikiLeaks breach.

"There are pieces in [FISMA] that if properly followed by the letter of the law, and the regulations, greatly minimize the risk of things like this happening," said Hord Tipton, executive director of (ISC)2, a nonprofit group that certifies and trains information security professionals. "I think we have quite adequate hardware and technology to deal with it."

But the government must evaluate more closely the people it tasks to follow the rules, cautioned Tipton, who served for five years as the Interior Department's chief information officer.

"All of this depends upon people and people that we trust. We have to take an introspective look at how much we should trust people," he said. Also, "We might not have enough capable people to configure the technology. . . . You've got to recognize that all data is not the same and we're drowning in it. If we're going to live in a sea of data like this, we have to hire people who know how to deal with it."

Threatwatch Alert

Thousands of cyber attacks occur each day

See the latest threats


Close [ x ] More from Nextgov

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

  • Featured Content from RSA Conference: Dissed by NIST

    Learn more about the latest draft of the U.S. National Institute of Standards and Technology guidance document on authentication and lifecycle 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

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


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