diarmf - authorize

security risk

February 6, 2014 by Bruce Brown Leave a Comment

NIST SP 800-39, Manage Information Security Risk

NIST SP 800-39 deals entirely with fixing the challenge of security risk in an organization. Chapter 2 of 800-39 discusses the basics of security risk management & chapter 3 goes into the process of applying security risk management across and organization.

The Fundamentals of Security Risk Management (Chapter 2, 800-39)
The philosophy security risks and how to manage information security at multiple levels of an organization are discussed in Chpt 2 of NIST SP 800-39. The three layers of security risk are:

Tier 1: Organization level
Tier 2: Mission/Business Process level
Tier 3: Information System level

Tier 1: Organization Level security risk management
Tier 1 addresses security risk from the organizations perspective. This include the implementation of the first component of security risk management which is called risk framing.

In tier 1 or security risk management, the management of the organization establishes governance structure that are in compliance with laws, regulations and policies. Tier 1 activities include establishment of the Risk Executive Function, establishment of the risk management strategy and determination of the risk tolerance.

Security Risk framing provides context for all the security risk activities within an organization, which affects the risk tasks of tier 1 & 2. The result of risk framing is Security Risk Management Strategy.

Security Risk Management Tier 2: Mission/Business Process

Tier 2 Security risk management tasks include: 1) defining the mission processes. 2) Prioritize the mission process with respect to the long term goals of the organization. 3) Define the type of information needed to successfully execute the mission/business processes, critical/sensitivity of the information and the information flows both internal and external of the information.

Tier 3: Information System Security Risk management

From the information system perspective, tier 3 addresses the following tasks:

Categorization of the information system
Allocating the organizational security control
Selection, implementation, assessment, authorization, and ongoing

Chapter 3 focuses on the step to have a comprehensive security risk management program. The tasks discussed include:

Risk Framing
Risk Assessing
Risk Response
Risk Monitoring

Risk Assessment

NIST 800-30 goes into Risk Assessment process. 800-39 covers from a high level. Risk assessment is threat & vulnerability identification and risk determination. Organizational risk framing is a prerequisite to risk assessments, because methods of risk assessment must be established by the contexts of the organizations risk.

Risk Response
Risk response identifies, evaluates, decides on, and implements appropriate courses of action to accept, avoid, mitigate, share, or transfer risk to organizational operations and assets, individuals, other organizations, and the Nation, resulting from the operation and use of information systems.

Risk identification is key to risk response. Risk types include:
Risk accept- is the appropriate risk response when the identified risk is within the organizational risk tolerance. Organizations can accept risk deemed to be low, moderate, or high depending on particular situations or conditions.

Risk avoidance– Organizations may conduct certain types of activities or employ certain types of information technologies that result in risk that is unacceptable. In such situations, risk avoidance involves taking specific actions to eliminate the activities or technologies that are the basis for the risk or to revise or reposition these activities or technologies in the organizational mission/business processes to avoid the potential for unacceptable risk.

Risk mitigation-adding management, technical, administrative safeguards to minimize identified risks to the system.
Risk share & transfer- Risk sharing or risk transfer is the appropriate risk response when organizations desire and have the means to shift risk liability and responsibility to other organizations. Risk transfer shifts the entire risk responsibility or liability from one organization to another organization (e.g., using insurance to transfer risk from particular organizations to insurance
companies).

Risk Monitoring Risk changes with each modification of the system. It’s important to monitor the changes of the risk of a system. Changes to threats can also change risk. This is where Continuous monitoring comes in.

risk management framework steps

January 19, 2014 by Bruce Brown Leave a Comment

The risk management framework steps are detailed in NIST SP 800-37, Guide for Applying the Risk Management Framework to Federal Information Systems.

The DoD has recently adopted the Risk Management Framework steps (called the DIARMF process). There are 6 step: Categorize, Select, Implement, Assess, Authorize and Continuous Monitor.

risk management framework – Step 1. Categorize

The first risk management framework step is categorization. This step consists of classifying the importance of the information system. This is done by the system owner with FIPS 199 and NIST 800-60.

Categorization is based on how much negative impact the organization will receive if the information system lost is confidentiality, integrity or availability.

risk management framework – Step 2. Select

With FIPS 200 and NIST SP 800-53, the organization responsible for the systems security will select the security controls required to limit the risk to their organization. The selection of the controls is based on the categorization of your system. A system security plan is created as a guide to what will be installed and/or configured on the system.

risk management framework – Step 3. Implement

Using the System Security Plan, the organization responsible for the categorized system can begin risk management framework step 3. This step is implementation which is installation and configuration of security patches, hotfixes and security devices where necessary. Guidance for actual implantation has to come from technical manuals, system administrators, system engineers and others technically competent enough to do the work.

risk management framework – Step 4. Assess

The organization has to make sure that the security controls are implemented properly. This is done in risk management step 4, assess. Using NIST SP 800-53A, Guide for Assessing the Security Controls in Federal Information Systems and Organizations is used to determine which controls have been fully implemented to limit the risks to the organization.

risk management framework – Step 5. Authorize

Even after implementation and assessment of the security controls that limits the over all risk to the organization, there is some remaining (residual) risk. The organization must have someone who has enough authority of over the system to accept the residual risk. This person is known as the Authorizing Official.

In risk management framework step 5, an Authorizing Official makes a formal, written acceptance of the risks. The AO makes a decision on whether or not to accept the risk based on the authorization package. The authorization package consists of the system security plan, plan of action and milestone, security/risk assessment report and any other supporting documents.

DIARMF A&A – Assessment Authorization

January 17, 2014 by Bruce Brown Leave a Comment

DIARMF A&A – Assessment Authorization

Defense Information Assurance Risk Management Framework Assessment & Authorization is similar to what certification and accreditation (C&A).

With DIACAP transition comes some new terms but essentially the same kinds of work. Risk management framework still does the comprehensive evaluation of security features but calls it assessment instead of ceritification. Where DIACAP had the Designating Authorizing Authority (DAA) to formally accredit a system, DIARMF has an Authorizing Official (AO) to authorize a system.

So essentially, the terms “C&A” certification and accreditation is superseded by “A&A” assessment and authorization. Another term that has changed with the transition from DIACAP to DIARMF is “information assurance (IA) controls” which is now called “security controls”. The security controls mark one of the biggest differences between DIACAP and DIARMF since there are so many more security controls in NIST SP 800-53 than there are in DIACAP’s DOD 8500.2.

Certification (NIST Assessment) – Comprehensive evaluation of an information system assessment of IA Controls/Security Controls to determine the extent to which the controls are implemented correctly and operating as intended. That means when evaluated, they produce the desired outcome. An assessment is about gathering information to providing the factual basis for an authorizing official (Designated Accrediting Authority) to render a security accreditation decision

Accreditation (NIST Authorization) – Security accreditation is the official management decision to operate (DAA – Formal approval of the system). Authorization is given by a senior agency official (upper-management/higher head quarters/combat commander). The official should have the authority to oversee the budget and business operations of the information system explicitly accept the risk to operations, assets, individuals. They accept responsibility for the security of the system and are fully accountable for the security of the system.

“The official management decision given by a senior organization“The official management decision given by a senior organizational official to authorize operation of an information system and to explicitly accept the risk to organizational operations (including mission, functions, image, or reputation), organizational assets, individuals, other organizations, and the Nation based on the implementation of an agreed-upon set of security controls.” – NIST SP 800-37 rev 1

DIARMF Authorization

January 16, 2014 by Bruce Brown 2 Comments

What is Step 5 – Authorization?

DIARMF Step 5 is similar to Phase 4 of DIACAP, Make Certification Determination & Authorization Decision. In fact, the major difference between the two system in this part of the process are the names. DIARMF Step 5 Authorization is where the Authorizing Official Accept the residual risks of the systems. The residual risks are the remaining risks that could not be fixed with security controls for one reason or another. Perhaps the organization did not have enough money to implement a specific kind of web proxy or the physical location of a base at the foot of key terrain owned by a private civilian has made it so the vulnerability to the asset cannot be fully mitigated at this time. The residual risks are addressed in the findings and recommendation are addressed in a Security Assessment Report (SAR). The SAR highlights the residual risks and what can be done about them. It is meant to give the decision makers some idea where the biggest risks are to the Asset. In DIACAP, the equivalent would be the DIACAP Scorecard, similarly the SAR is supposed to give a quick assessment that will help decision maker and/or the Authorizing Official know what kind of risk he or she is expected to accept. How the findings and recommendations will be handled and when are addressed in the Plan of Action and Milestone (POA&M). These documents (SAR and POA&M) are the primary responsibility of Information System Owner or Common Control Provider, but supported by Information Owner/Steward and Information System Security Officer, meaning its DONE by the ISSO and delegated by the Information system Owner. The POA&M addressed the problem, what tasks are needed get to a solution (if any), a date of completion with milestones on the way to accomplishing the solution and resources required. References: OMB Memorandum 02-01; NIST Special Publications 800-30, 800-53A, 800-37. Authorization Decision and Authorization Package The Authorization Decision is based on supporting evidence that comes from content of the authorization package. The Authorization package consists of the following:

• System Security plan – Provides a comprehensive view of all security controls and the overall security posture of the system (see NIST SP 800-18)

• Security Assessment Report – a report and addresses the residual risk, remaining weakness of the system.

• Plan of action and milestones – a breakdown of how and when the remaining vulnerabilities will be addressed.

Once the AO is ready to accept the risk, he or she must formally accept the risks of the system and grant it an Authorization to Operate in writing.