Blog Archives

What are the Steps in the Risk Management Framework Process?

Posted by:Admin | Posted on: April 22nd, 2014 | 0 Comments

Risk Management Framework (RMF) Training, NIST Training

Read More

Risk Management Framework Training Locations Added!

Posted by:Admin | Posted on: April 21st, 2014 | 0 Comments

ITdojo has added a few new training locations for our Risk Management Framework (RMF) related training courses to accommodate our DoD and Federal Civil Agency clients across the country. Our RMF for DoD IT, RMF for FISMA IT, and our Information Security Continuous Monitoring courses are available as instructor-led offerings in Virginia Beach, VA, Colorado Springs, CO, Huntsville, AL or Washington DC.  If you are out of those areas, training can also be brought to your location.  Contact us for details. Also, keep in mind that these classes are available frequently as Live Remote Online training sessions if traveling for training is not in your budget.

Read More

Cloud Security and FedRAMP. Are you Ready for it?

Posted by:Admin | Posted on: April 16th, 2014 | 0 Comments

A deadline for federal agencies to adhere to the government’s baseline cloud security standards and changes to the standards themselves are coming up very soon. The deadline for agencies to have their existing cloud computing solutions assessed against the Federal Risk and Authorization Management Program, or FedRAMP is June 5, 2014 Read more about this in this article on NextGov. ( To help you with your preparations for FedRAMP, ITdojo has courses running in Northern, VA every other month. To learn more about this Cloud Security and FedRAMP course, visit this page.

Read More

DoD (Finally) Begins Transition to RMF

Posted by:Admin | Posted on: April 11th, 2014 | 0 Comments

By Lon J. Berman, CISSP The wait is over! RIP DIACAP!! At long last, DoD has announced the start of transition from the legacy DIACAP Certification and Accreditation (C&A) Program to the Risk Management Framework (RMF). This transition is part of a broader effort to bring all Executive Branch departments and agencies … including DoD, the intelligence community and all “civil” departments/agencies … into a “unified information security framework.” Two key documents were signed and released by DoD Chief Information Officer Teresa Takai in March, 2014:
  • New DoD Instruction (DoDI) 8500.01, replacing DoD Directive (DoDD) 8500.1. The title has been changed from Information Assurance to Cybersecurity.
  • Revised DoD Instruction (DoDI) 8510.01; title changed from DIACAP to Risk Management Framework (RMF) for DoD Information Technology (IT).
So far, so good ... but wait a minute! What about DoDI 8500.2? For those new to the process, that’s the document that contains all the “IA Controls” (security requirements) with which DoD systems are required to comply. Wouldn’t that also need to be revised to fit into the new process? Well, the short answer is there will be no revised DoDI 8500.2 — DoD has decided to simply rescind it. So how exactly is DoD going to implement a brand new information security framework without specifying requirements? It’s easy—they’ve decided not to try and reinvent the wheel, but rather to leverage the extensive work of NIST, the National Institute of Standards and Technology, and CNSS, the Committee on National Security Systems. A few of the key NIST and CNSS publications that are being “adopted” by DoD are:
  • NIST Special Publication (SP) 800-53, Revision 4. This document contains an extensive “catalog” of Security Controls (requirements).
  • NIST SP 800-37, Revision 1. This is the definitive Risk Management Framework document, describing the roles and responsibilities, life cycle process, etc.
  • CNSS Instruction (CNSSI) 1253. This publication describes the methodology that DoD will use for categorizing systems and selecting security controls.
  • NIST SP 800-53A Revision 2 . This document contains recommended assessment objectives and procedures for each of the Security Controls.
The change from DIACAP to RMF will eventually affect every DoD information system, including “DoD owned and operated” systems as well as processes and systems operated by industry partners on behalf of DoD. A phased approach is being adopted, such that every system will be fully transitioned in time for its next re-authorization (reaccreditation) date. Now that the official publications are on the ground, there is plenty of work still to be done by DoD to support the transition. The Knowledge Service website is in the process of being updated with RMF information, including the all-important assessment procedures for evaluating compliance with each of the controls. Also on the horizon is a major overhaul of the eMass tool to support the RMF workflow, NIST security control set, etc. ITdojo now has three courses to help with the transition if your organization has not already made it.  They are: Risk Management Framework (RMF) for DoD IT Training Risk Management Framework (RMF) for FISMA IT Training Information Security Continuous Monitoring (ISCM) Training  

Read More

Top 10 Things that Will Be Staying the Same with RMF

Posted by:Admin | Posted on: April 10th, 2014 | 0 Comments

By Lon J. Berman, CISSP As DoD begins its transition from DIACAP to Risk Management Framework for DoD IT, everyone is naturally focused on all the things that will be changing—everything from terminology to documentation to security controls. Thankfully, not everything is changing! We thought it would be interesting to take a look at some of the things that will not be changing with the advent of RMF in DoD. 1. DoDI 8510.01. DoD Instruction 8510.01 will remain the governing document for the security life cycle process. It is currently being revised to reflect RMF rather than DIACAP as the “official” DoD process. 2. DIACAP Knowledge Service. The DIACAP Knowledge Service will remain the authoritative source for security-related information and guidance. RMF-oriented content is currently being added. 3. Major Change. Systems will still need to be reauthorized (reaccredited) when a "major change" to the system takes place. The individual who signed the Authority to Operate (ATO) will still have the final say on whether or not a proposed change is "major". 4. Contractor owned/Operated Systems. IT-based processes "outsourced" to contractor-owned systems will still require ATO. 5. Independent Assessment. DoD systems will still require independent assessment (in accordance with DoD Component policies and procedures) in order to receive ATO. 6. System Registration. Information systems will be still need to be registered with the IA program, in accordance with DoD Component policies and procedures. 7. Plan of Action and Milestones (POA&M). POA&Ms will continue to be used to report and track security weaknesses of information systems, and to manage corrective actions. 8. Configuration Standards. DISA Security Technical Implementation Guides (STIGs) will continue to be the official DoD standards for configuring operating systems, databases, web servers, network devices, etc.. 9. Training and Certification. DoD Instruction 8570.1 (or its planned successor) will still be in force. DoD employees and contractors having any sort of IA responsibility will still be required to hold appropriate professional certification. 10. Approval to Operate (ATO). All information systems owned by DoD, or operated on behalf of DoD, will still need ATO from a senior DoD official.The process leading to ATO will be changing (RMF rather than DIACAP). Even the title of the person signing it will change (Authorizing Official rather than DAA), but the fundamental concept of risk-based decision (“balancing” or residual risk against mission need) will be unchanged. If you are interested in learning more about our RMF for DoD IT training course, please click here.

Read More

RMF Documents and Resources

Posted by:Admin | Posted on: April 9th, 2014 | 0 Comments

For your convenience, ITdojo has assembled the following collection of RMF-related government publications. Please note these are UNCLASSIFIED documents with no restrictions on usage or distribution.

Laws and Executive Branch Policies

Federal Information Security Management Act (FISMA)  OMB Circular A-130 Appendix III (Security of Federal Information Systems) 

Federal Information Processing Standard (FIPS) Publications

FIPS 199 (Security Categorization)  FIPS 200 (Minimum Security Controls) 

NIST Special Publications (SP)

SP 800-18 (Security Plans)  SP 800-30 (Risk Assessment)  SP 800-34 (Contingency Planning)  SP 800-37 (Risk Management Framework)  SP 800-39 (Organizational Risk Management)  SP 800-53 (Security Controls)  SP 800-53A (Security Controls Assessment)  SP 800-59 (National Security Systems)  SP 800-60 (Security Categorization), Volume 1  SP 800-60 (Security Categorization), Volume 2  SP 800-61 (Incident Response Planning)  SP 800-137 (Continuous Monitoring) 

Committee on National Security Systems (CNSS) Publications

CNSSP 22 (Risk Management Policy for NSS)  CNSSI 1253 (Security Categorization and Control Selection for NSS)  CNSSI 4009 (Information Assurance Glossary) 

Department of Defense Instructions (DoDI)

DoDI 8500.01 (Cybersecurity) New DoDI 8510.01 (RMF for DoD IT) New

Intelligence Community (IC) Publications

ICD 503 (Risk Management, Certification and Accreditation) 

Read More