Standards body drafts guide on preventing data breaches
- By Heather Greenfield
- June 11, 2007
- Comments
The 387-page guide is designed to help agency technical teams evaluate whether the security controls they have actually work as intended to protect information systems from being compromised.
It is designed as a companion to an earlier publication on minimum security controls for federal information systems. That guide, according to lead author Ron Ross, defines the different security controls required by the federal government -- including encryption, identification and authentication of users, access control to systems, personnel security and physical security.
The latest publication lists the different security measures and explains how to test them. For example, for continuity of operation requirements, the report outlines how to determine if an agency really has developed a plan, if people understand it and if it has been distributed to the right people within the organization.
The 2002 Federal Information Security Management Act instructs NIST to prepare minimum computer-security requirements for all systems other than those connected to national security, which have separate rules.
"The assessment requirements presented in this latest draft are intended to make compliance with FISMA easier, more efficient, and ultimately to produce better computer and information security for the federal government," said Ross, who is the FISMA implementation project leader at NIST.
Ross said the report is the last in a series since 2003 and is designed o make security procedures more cost-effective and easier to implement. NIST is asking for comments through the end of next month. The guidelines could help federal agencies, which received a grade of C-minus for FISMA compliance for 2006.
Sen. Norm Coleman, R-Minn., has introduced legislation that would amend FISMA rules to broaden the definition of sensitive personal data and direct the White House Office of Management and Budget to establish policies that agencies should follow after data breaches.
In addition to names, Social Security numbers, birth dates and places, mother's maiden names, and biometric records, the bill would include education, criminal, medical and employment history. The measure, S. 1558, also would give agency chief information officers more power to enforce compliance with security rules.
"In the wake of data breaches at the Departments of Veterans Affairs, Commerce, Agriculture, the [Transportation Security Administration] and IRS, we must ensure that federal agencies are taking the necessary preventative security measures to protect our citizens' personal information," Coleman said. "In addition to establishing a new protocol, this legislation will also create a system for notifying victims in the event of a security breach."
The Senate bill is designed as a companion to a House bill, H.R. 2124. Unlike broader data-protection measures drafted or being drafted by other committees, the bills would apply to just personal data stored by the federal government.
By using this service you agree not to post material that is obscene, harassing, defamatory, or otherwise objectionable. Although GovExec.com does not monitor comments posted to this site (and has no obligation to), it reserves the right to delete, edit, or move any material that it deems to be in violation of this rule.
Tangherlini Tapped to Stay On at GSA
Video: Stephen Colbert on the Census Bureau
Lawmaker: Don't Furlough Weather Service Now
Making Government 'Simpler'
OK Senators Leery of Unfunded Tornado Relief
Boldly Go Where No Fed's Gone Before
Need to Know Memo: Big Data
Research Report: Powering Continuous Monitoring Through Big Data
Addressing the 3 Biggest BYOD Security Threats
Continuous Monitoring As a Service: A Shift in the Way Government Does Business
