Federal Information Security Management Act of 2002: Difference between revisions

From Citizendium
Jump to navigation Jump to search
imported>Howard C. Berkowitz
No edit summary
imported>Howard C. Berkowitz
No edit summary
Line 2: Line 2:
{{TOC|right}}
{{TOC|right}}
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.
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==
==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".<ref name=FIPS199>{{citation
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".<ref name=FIPS199>{{citation
Line 52: Line 54:
*The processes used to collect the information are cumbersome, labor‐intensive, and take time away from meaningful analysis, and;
*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
*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.<ref>{{citation
| author =Margaret H. Graves. Acting Chief Information Officer, [[U.S. Department of Homeland Security]]
|  title = The State of Federal Information Security
| publisher = [[Subcommittee on Government Management, Organization and Procurement]],  [[U.S. House Commitee on Oversight and Government Reform]]
| date = May 19, 2009
| url = http://governmentmanagement.oversight.house.gov/documents/20090519083111.pdf}}</ref>
==Criticism==  
==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.<ref name=FCW2009-07-01>{{citation
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.<ref name=FCW2009-07-01>{{citation

Revision as of 08:27, 14 September 2009

This article is developing and not approved.
Main Article
Discussion
Related Articles  [?]
Bibliography  [?]
External Links  [?]
Citable Version  [?]
Catalogs [?]
 
This editable Main Article is under development and subject to a disclaimer.

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

Status

On May 19, 2009, the House took testimony at the required 60-day reporting interval after start of FISMA implementation.[2] 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:[3]

  • 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.[4]

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.[5]

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.[6] 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