NIST prepares due diligence standards for cybersecurity

As initiative moves into its second phase, some industry officials question whether improvements are real

The National Institute of Standards and Technology is taking new steps to help federal agencies develop a more realistic approach to cybersecurity. In collaboration with the Defense Department and the Office of the Director of National Intelligence, NIST will create a common foundation for risk management, officials said.

Ron Ross, senior computer scientist at NIST, said that because agencies cannot avoid risk, officials should approach cybersecurity by weighing the consequences of a data breach on their agency’s mission. NIST is developing a foundation of standards and guidelines to help officials find a balance between protecting information systems and achieving their agencies’ missions.

“You’re not going to have the same answer across the federal government,” Ross said at an industry event sponsored by GTSI last month. “This is all about having to think about the problem.”

For about five years, agencies have been working to comply with the security provisions of the Federal Information Security Management Act.

“FISMA is good legislation, and we’re making outstanding progress in implementing these policies,” Ross said, but now agencies have to rethink how they fulfill those provisions.

“You’ve got to deploy a sufficient set of security controls to protect every mission that the system is supporting,” Ross said. “We’ve never before had a standard of security due diligence that we’ve been able to define and hold agencies to.” Security due diligence must be the foundation for sharing information securely with other agencies, he added.

“You have to trust your partner to do the right thing,” Ross said. “You’ve got to understand the security state of not only your system but the system of your partner that you’re going to be sharing with.”

The emphasis on sharing data among agencies is still relatively new and not ingrained in agencies’ cultures, said Mark Kagan, research manager at IDC Government Insights and a former intelligence analyst at the National Security Agency.

Agencies are still working to implement the basics of information technology security, he added.

“After they share [information] with one person in another agency, they don’t have any control over it,” Kagan said.

Late this year, the national security community will issue its catalog ofsecurity controls, which will be similar to those in NIST’s Special Publication 800-53, said Sharon Ehlers, the lead for the system certification and accreditation effort.

Dale Meyerrose, ODNI’s chief information officer, and DOD CIO John Grimes initiated the effort last year. Likewise, the catalog for the national security community will suggest some revisions to NIST’s SP 800-53, which NIST would incorporate in its next release.

“We’re hoping in a year or 18 months to have one federal standard for all security controls and risk management,” Ehlers said.

About the Author

Mary Mosquera is a reporter for Federal Computer Week.


  • Workforce
    Shutterstock image 1658927440 By Deliris masks in office coronavirus covid19

    White House orders federal contractors vaccinated by Dec. 8

    New COVID-19 guidance directs federal contractors and subcontractors to make sure their employees are vaccinated — the latest in a series of new vaccine requirements the White House has been rolling out in recent weeks.

  • FCW Perspectives
    remote workers (elenabsl/

    Post-pandemic IT leadership

    The rush to maximum telework did more than showcase the importance of IT -- it also forced them to rethink their own operations.

Stay Connected