Jump to content

User:Rapidking/sandbox

From Wikipedia, the free encyclopedia
Risk Management Framework (RMF) Rev. 2 seven step process

The Risk Management Framework (RMF) is a United States federal government guideline, standard and process to help secure information systems (computers and networks) developed by National Institute of Standards and Technology.

The main document that describes the details of RMF is NIST Special Publication 800-37, "Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy" [1]. This is the second revision of this document and supersedes the first revision "Guide for Applying the Risk Management Framework to Federal Information Systems" [2].

The various steps of the RMF link to several other NIST standards and guidelines, including NIST Special Publication 800-53, "Security and Privacy Controls for Information Systems and Organizations" [3].

The Risk Management Framework (RMF), illustrated at right, provides a disciplined and structured process that integrates information security, privacy and risk management activities into the system development life cycle.[2]

The RMF steps include:

  • Prepare to execute the RMF by establishing a context and priorities for managing security and privacy risk at organizational and system levels [4][5].
  • Categorize the information system and the information processed, stored, and transmitted by that system based on an impact analysis [6][7][8].
  • Select an initial set of baseline security controls for the information system based on the security categorization; tailoring and supplementing the security control baseline as needed based on an organizational assessment of risk and local conditions. If any overlays apply to the system they will be added in this step [3][9].
  • Implement the security controls identified in step 2 [3].
  • Assess: a third party assesses the controls and verifies that the controls are properly applied to the system [10].
  • Authorize: the information system is granted or denied an Authorization to Operate (ATO), in some cases it may be postponed while certain items are fixed. The ATO is based on the report from the Assessment phase. ATO is typically granted up to 3 years and the process needs to be repeated at the end of the period [1].
  • Monitor the security controls in the information system continuously in a pre-planned fashion as documented earlier in the process [5].

History

[edit]

The E-Government Act of 2002 (Public Law 107-347) entitled FISMA 2002 (Federal Information Security Management Act) was a law passed in 2002 to protect the economic and national security interests of the United States related to information security [11].

Congress later passed FISMA 2014 (Federal Information Security Modernization Act) to provide improvements over FISMA 2002 by:

  • Codifying Department of Homeland Security (DHS) authority to administer the implementation of information security policies for non-national security federal Executive Branch systems, including providing technical assistance and deploying technologies to such systems;
  • Amending and clarifying the Office of Management and Budget's (OMB) oversight authority over federal agency information security practices; and by
  • Requiring OMB to amend or revise OMB A-130 to "eliminate inefficient and wasteful reporting."[12]

FISMA required the protecting information and information systems from unauthorized access, use, disclosure, disruption, modification, or destruction in order to provide Confidentiality, Integrity and Availability [13]. Title III of FISMA 2002 tasked NIST with responsibilities for standards and guidelines, including the development of:

  • Standards to be used by all federal agencies to categorize all information and information systems collected or maintained by or on behalf of each agency based on the objectives of providing appropriate levels of information security according to a range of risk levels. This task was satisfied by FIPS Publication 199 [14];
  • Guidelines recommending the types of information and information systems to be included in each category. This task was satisfied by NIST Special Publication 800-60, Volumes 1 and 2 [15][16]; and
  • Minimum information security requirements (i.e., management, operational, and technical controls), for information and information systems in each such category. This task was satisfied by the development of FIPS Publication 200 [17].

NIST 800-37 (Risk Management Framework or RMF) was developed to help organizations manage security and privacy risk, and to satisfy the requirements in the Federal Information Security Modernization Act of 2014 (FISMA), the Privacy Act of 1974, OMB policies, and Federal Information Processing Standards, among other laws, regulations, and policies [1].

Risks

[edit]

During its lifecycle, an information system will encounter many types of risk that affect the overall security posture of the system and the security controls that must be implemented. The RMF process supports early detection and resolution of risks. Risk can be categorized at high level as infrastructure risks, project risks, application risks, information asset risks, business continuity risks, outsourcing risks, external risks and strategic risks. Infrastructure risks focus on the reliability of computers and networking equipment. Project risks focus on budget, timeline and system quality. Application risks focus on performance and overall system capacity. Information asset risks focus on the damage, loss or disclosure to an unauthorized part of information assets. Business continuity risks focus on maintaining a reliable system with maximum up-time. Outsourcing risks focus on the impact of 3rd party supplier meeting their requirements. [18] External risks are items outside the information system control that impact the security of the system. Strategic risks focuses on the need of information system functions to align with the business strategy that the system supports [19].

See also

[edit]

References

[edit]
  1. ^ a b c Force, Joint Task (2018-12-20). "Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy". {{cite journal}}: Cite journal requires |journal= (help)
  2. ^ a b Guide for Applying the Risk Management Framework to Federal Information Systems
  3. ^ a b c Force, Joint Task (2020-12-10). "Security and Privacy Controls for Information Systems and Organizations". {{cite journal}}: Cite journal requires |journal= (help)
  4. ^ Initiative, Joint Task Force Transformation (2012-09-17). "Guide for Conducting Risk Assessments". {{cite journal}}: Cite journal requires |journal= (help)
  5. ^ a b Dempsey, Kelley; Chawla, Nirali; Johnson, L.; Johnston, Ronald; Jones, Alicia; Orebaugh, Angela; Scholl, Matthew; Stine, Kevin (2011-09-30). "Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations". {{cite journal}}: Cite journal requires |journal= (help)
  6. ^ Stine, Kevin; Kissel, Richard; Barker, William; Fahlsing, Jim; Gulick, Jessica (2008-08-01). "Guide for Mapping Types of Information and Information Systems to Security Categories". {{cite journal}}: Cite journal requires |journal= (help)
  7. ^ Stine, Kevin; Kissel, Richard; Barker, William; Lee, Annabelle; Fahlsing, Jim (2008-08-01). "Guide for Mapping Types of Information and Information Systems to Security Categories: Appendices". {{cite journal}}: Cite journal requires |journal= (help)
  8. ^ Technology, National Institute of Standards and (2004-02-01). "Standards for Security Categorization of Federal Information and Information Systems". {{cite journal}}: Cite journal requires |journal= (help)
  9. ^ Technology, National Institute of Standards and (2006-03-01). "Minimum Security Requirements for Federal Information and Information Systems". {{cite journal}}: Cite journal requires |journal= (help)
  10. ^ Initiative, Joint Task Force Transformation (2014-12-18). "Assessing Security and Privacy Controls in Federal Information Systems and Organizations: Building Effective Assessment Plans". {{cite journal}}: Cite journal requires |journal= (help)
  11. ^ "govinfo". www.govinfo.gov. Retrieved 2021-07-18.
  12. ^ "Federal Information Security Modernization Act | CISA". www.cisa.gov. Retrieved 2021-07-18.
  13. ^ Carper, Thomas R. (2014-12-18). "Text - S.2521 - 113th Congress (2013-2014): Federal Information Security Modernization Act of 2014". www.congress.gov. Retrieved 2021-07-18.
  14. ^ Technology, National Institute of Standards and (2004-02-01). "Standards for Security Categorization of Federal Information and Information Systems". {{cite journal}}: Cite journal requires |journal= (help)
  15. ^ Stine, Kevin; Kissel, Richard; Barker, William; Fahlsing, Jim; Gulick, Jessica (2008-08-01). "Guide for Mapping Types of Information and Information Systems to Security Categories". {{cite journal}}: Cite journal requires |journal= (help)
  16. ^ Stine, Kevin; Kissel, Richard; Barker, William; Lee, Annabelle; Fahlsing, Jim (2008-08-01). "Guide for Mapping Types of Information and Information Systems to Security Categories: Appendices". {{cite journal}}: Cite journal requires |journal= (help)
  17. ^ Technology, National Institute of Standards and (2006-03-01). "Minimum Security Requirements for Federal Information and Information Systems". {{cite journal}}: Cite journal requires |journal= (help)
  18. ^ IT Risk Management Framework for Business Continuity by Change Analysis of Information System
  19. ^ An Empirical Study on the Risk Framework Based on the Enterprise Information System
[edit]

Category:Risk management Information Assurance Certification and Accreditation Program Category:Computer security procedures

Retrieved from "https://wiki.riteme.site/w/index.php?title=User:Rapidking/sandbox&oldid=1035097470"