Federal Information Security Management Act of 2002: Difference between revisions
imported>Howard C. Berkowitz No edit summary |
imported>Howard C. Berkowitz |
||
Line 17: | Line 17: | ||
|- | |- | ||
! Factor | ! Factor | ||
! | ! | ||
! | ! | ||
! | ! | ||
Line 41: | Line 41: | ||
| | | | ||
|} | |} | ||
==Solution architecture== | |||
For designing FISMA implementations, the primary reference is NIST Special Publication 800-53, Revision 3, "Recommended Security Controls for Federal Information Systems and Organizations"<ref name=>{{citation | |||
| title = Recommended Security Controls for Federal Information Systems and Organizations | |||
| id = NIST Special Publication 800-53 | |||
| edition = Revision 3 | |||
| date = August 2009 | |||
| publisher = [[National Institute of Standards and Technology]] | |||
| url = http://csrc.nist.gov/publications/nistpubs/800-53-Rev3/sp800-53-rev3-final.pdf}}</ref> | |||
==Status== | ==Status== | ||
On May 19, 2009, the House took testimony at the required 60-day reporting interval after start of FISMA implementation.<ref name=SCGMOP-2009-05-09>{{citation | On May 19, 2009, the House took testimony at the required 60-day reporting interval after start of FISMA implementation.<ref name=SCGMOP-2009-05-09>{{citation |
Revision as of 08:36, 14 September 2009
Enacted in 2002, the Federal Information Security Management Act (FISMA), was passed to support the E-Government Act of 2002. Without information security, it is impossible for government to deliver reliable services through electronic means. The advent of Internet delivery and cloud computing immensely complicates the security problem.
Nevertheless, there may well be solutions for these new environments, if proper perspective is kept. In any security context, there is acceptance of responsibility, as well as acceptance of risk. An approach to security purely in the network has long been endpoint security, leaving the network encrypted. When the servers are outsourced, it may be that endpoint encryption will remain under control of the owning agency, but audit is the main tool for checking on the server operator.
Framework
Technical definitions and framework are in Federal Information Processing Standard (FIPS) FIPS PUB 199, "Standards for the Security Categorization of Federal Information and Information Systems".[1] While the detailed guidance is in additional guidance, FIPS 199 interprets FISMA as having three dimensions of security categorization:
and matrixes these against potential impact characterized as low, medium and high:
Factor | |||
---|---|---|---|
Low | Medium | High | |
Confidentiality | row 1, cell 2 | row 1, cell 3 | |
Integrity | row 2, cell 2 | row 2, cell 3 | |
Availability | row 2, cell 2 | row 2, cell 3 |
Solution architecture
For designing FISMA implementations, the primary reference is NIST Special Publication 800-53, Revision 3, "Recommended Security Controls for Federal Information Systems and Organizations"[2]
Status
On May 19, 2009, the House took testimony at the required 60-day reporting interval after start of FISMA implementation.[3] Vivek Kundra, the Federal Chief Information Officer, summarized the overall status: "recent successful breaches at the Federal Aviation Administration and at the vendor that hosts USAjobs.gov demonstrate that the current state of information security at Federal agencies is not what the American people have the right to expect. The Federal Information Security Management Act (FISMA) has been in place for 7 years. It has raised the level of awareness in the agencies and in the country at large, but we are not where we need to be." OMB identified the following key issues:[4]
- The performance information currently collected under FISMA does not fully reflect the security posture of Federal agencies;
- The processes used to collect the information are cumbersome, labor‐intensive, and take time away from meaningful analysis, and;
- The Federal community is focused on compliance, not outcomes
At the same hearing, Margaret Graves, CIO of the U.S Department of Homeland Security, spoke more specifically about implementation in a real agency.[5]
Criticism
FISMA has been criticized, by legislators and legislative agencies, for being too dependent on manual paper procedures and not enough on specific enforcement technologies and procedures.[6]
In April 2009, Senator Thomas Carper (D-Delaware) introduced two pieces of legislation to force more actual compliance and less paper reporting of hypothetical compliance.[7] Hearings also were held in May by Subcommittee on Government Management, Organization and Procurement of the U.S. House Committee on Oversight and Government Reform.
References
- ↑ Standards for the Security Categorization of Federal Information and Information Systems, Computer Security Division, Information Technology Laboratory, National Institute for Standards and Technology, February 2004, FIPS PUB 199
- ↑ Recommended Security Controls for Federal Information Systems and Organizations (Revision 3 ed.), National Institute of Standards and Technology, August 2009, NIST Special Publication 800-53
- ↑ Hearing Testimony and Witness list for the Subcommittee Hearing on: "The State of Federal Information Security.", Subcommittee on Government Management, Organization and Procurement, U.S. House Committee on Oversight and Government Reform, 19 May 2009
- ↑ Vivek Kundra, Federal Chief Information Officer, Office of Management and Budget (May 19, 2009), The State of Federal Information Security, Subcommittee on Government Management, Organization and Procurement, U.S. House Committee on Oversight and Government Reform
- ↑ Margaret H. Graves. Acting Chief Information Officer, U.S. Department of Homeland Security (May 19, 2009), The State of Federal Information Security, Subcommittee on Government Management, Organization and Procurement, U.S. House Commitee on Oversight and Government Reform
- ↑ Ben Bain (1 July 2009), "GAO urges improvements to FISMA: An auditor recommends steps to improve information security at agencies", Federal Computer Week
- ↑ Ben Bain (28 April 2009), "Carper introduces bills to reform IT procurement, FISMA", Federal Computer Week