Author name: Bruce

Dod 8140 DoD 8140, Cyberspace workforce will supersede DoD 8570 as the guide for selecting the personnel with the correct certifications, skills and experience. DoDD 8140, Cyberspace workforce has 7 high level categories under a National Initiative for Cybersecurity Education (NICE) framework: Security Provision, Maintain and Operate, Protect & Defend, Analyze, operate & collect, Oversight & Development and Investigate. These categories are broken down further into a sum total of 31 tasks.  It was supposed to be released in 2013, but there is actually no telling when it will come out.     Security Provision IA Assurance Compliance, Software, Enterprise Architecture, Technology Demonstration, System Requirement Planning, Test & Evaluation, System Development Operate & Maintenance Data Administration, Information System Security Management, Knowledge management, Customer & Tech Support, Network Services, System Administration, Systems Security Analysis Protect & Defend Computer Network Device (CND), Incident Response, CND Infrastructure Support, Security Program Management, Vulnerability Assessment & Management Analyze Cyber Threat Analysis, Exploitation Analysis, All-source Analysis, Targets Operate & collect Collection Operations, Cyber Operational Planning, Cyber Operations Oversight & Development Legal Advice & Advocacy, Strategic Planning & Policy, Education & Training Investigate Investigation, Digital Forensics The categories with the “cyberspace workfore” of DoD 8140 are broken up finer and in more detail than that of the IA Workforce. http://csrc.nist.gov/nice/ Also, notice that they have included some fields of IT and engineering that were passed over in the DoD 8570 Chart.  Areas such as Architect and Software Developer have been added. So what Certs do we need..  THAT is the real question.  I am still looking for that.  I have not found it yet.  I guess that is still in draft.  Here is some of what I found: http://csrc.nist.gov/nice/documents/the_path_towards_cybersecurity_professionalization_100312_draft_nice_branded.pdf Cybersecurity Workforce Training and Professional Development is led by the Department of Defense (DoD), Office of the Director of National Intelligence (ODNI), and the Department of Homeland Security (DHS). The Component, in coordination with academia, industry, and State, Local, and Tribal governments, will identify the cybersecurity training and professional development required for the nation’s cybersecurity workforce. This team will be broken into four functional areas: Functional Area 1: General IT Use (Co-Leads: DHS, Federal CIO Council) Functional Area 2: IT Infrastructure, Operations, Maintenance, and Information Assurance (Co-Leads: DoD, DHS) Functional Area 3: Domestic Law Enforcement and Counterintelligence (Co-Leads: DOD/DC3; NCIX; DHS/USSS; DoJ) Functional Area 4: Specialized Cybersecurity Operations (Lead: NSA)

The dod 8570 chart is designed to provide guidance for government agencies (mainly in defense) to categorize and identify certification of personnel conducting Information Assurance (IA) functions. Defense Information Assurance workforce is broken up into category, specialty, level, and function to for better protection of confidentiality, integrity and availability of DoD information, information systems, and networks. Information Assurance Profiles DoD 8570:   IA Management Level I IAM Level I personnel are responsible for the implementation and operation of an Information System (IS) within their CE. Personnel ensure that IA related IS are functional and secure within the CE. IA Management Level II IAM Level II personnel are responsible for the IA program of an IS within the NE. Personnel in these positions perform a variety of security related tasks, including the development and implementation of system information security standards and procedures. They ensure that IS are functional and secure within the NE. IA Management Level III IAM Level III personnel are responsible for ensuring that all enclave IS are functional and secure. They determine the enclaves’ long term IA systems needs and acquisition requirements to accomplish operational objectives. They also develop and implement information security standards and procedures through the certification and accreditation process. IA Technical Level I IAT Level I personnel make the CE less vulnerable by correcting flaws and implementing IAT controls in the hardware or software installed within their operational systems. IA Technical Level II IAT Level II personnel provide network environment (NE) and advanced level CE support. They pay special attention to intrusion detection, finding and fixing unprotected vulnerabilities, and ensuring that remote access points are well secured. These positions focus on threats and vulnerabilities and improve the security of systems. IAT Level II personnel have mastery of the functions of the IAT Level I position. IA Technical Level III PIAT Level III personnel focus on the enclave environment and support, monitor, test, and troubleshoot hardware and software IA problems pertaining to the CE, NE, and enclave environments. IAT Level III personnel have mastery of the functions of both the IAT Level I and Level II positions. CND-SP Analyst (CND-A) CND-A personnel use data collected from a variety of CND tools (including intrusion detection system alerts, firewall and network traffic logs, and host system logs) to analyze events that occur with their environment. CND-SP Infrastructure Support (CND-IS) CND-IS personnel test, implement, deploy, maintain, and administer the infrastructure systems which are required to effectively manage the CND-SP network and resources. This may include, but is not limited to routers, firewalls, intrusion detection/prevention systems, and other CND tools as deployed within the NE or enclave. CND-SP Incident Responder (CND-IR) CND-IR personnel investigate and analyze all response activities related to cyber incidents within the NE or Enclave. These tasks include, but are not limited to: creating and maintaining incident tracking information; planning, coordinating, and directing recovery activities; and incident analysis tasks, including examining all available information and supporting evidence or artifacts related to an incident or event. CND-SP Auditor (CND-AU) CND-AU personnel perform assessments of systems and networks within the NE or enclave and identify where those systems/networks deviate from acceptable configurations, enclave policy, or local policy. CND-AUs achieve this through passive evaluations (compliance audits) and active evaluations (penetration tests and/or vulnerability assessments). CND-SP Manager (CND-SPM) CND-SPMs oversee the CND-SP operations within their organization. CND-SPMs are responsible for producing guidance for their NE or enclave, assisting with risk assessments and risk management for organizations within their NE or enclave, and are responsible for managing the technical classifications within their organization. IASAE I Applies knowledge of IA policy, procedures, and structure to design, develop, and implement CE system(s), system components, or system architectures. IASAE II Applies knowledge of IA policy, procedures, and workforce structure to design, develop, and implement a secure NE. IASAE III Responsible for the design, development, implementation, and/or integration of a DoD IA architecture, system or system component for use within CE, NE, and enclave environments General User A user who is granted use of Government Information Systems (IS) and access to Government networks. This is not an IA position. Power User Personnel with limited administrative privileges to their PC only. This is not an IA position. DoD 8570 Chart is being replaced soon with DoDD 8140, Cyberspace workforce which will have 7 high level categories under a National Initiative for Cybersecurity Education framework: Security Provision, Maintain and Operate, Protect & Defend, Analyze, operate & collect, Oversight & Development and Investigate. These categories are broken down further into a sum total of 31 tasks.  It was supposed to be released in 2013, but there is actually no telling when it will come out.  

One of the most unavoidable rituals of getting an account on any Defense network is getting a “information assurance awareness certificate”. Information Assurance Awareness Certificate Pages: iase.disa.mil/index2.html Army: ia.signal.army.mil/DoDIAA The test is about 20 knowledge based questions that are fairly easy.  Even if you are not familiar with the way Defense does things, you can just take the test a few times until you pass it. Here are some examples of the information assurance awareness certificate:    

A risk evaluation from a system security perspective is known as a risk assessment (or security assessment).  The process of the risk evaluation is detailed in NIST SP 800-30, Guide for Risk Assessments and NIST SP 800-39, Risk Management. Risk evaluation means risk identification.  Risk identification has 7 mains steps  (two additional steps dedicated to recommendation and documentation): 1)  System characterization –  a System Security Plan (SSP).  Evaluate the Asset information covers the following: Hardware Software System interfaces (e.g., internal and external connectivity) Data and information Persons who support and use the IT system System mission (e.g., the processes performed by the IT system) System and data critical (e.g., the system’s value or importance to an organization) System and data sensitivity 2)  Threat Evaluation – Evaluate possible threat sources by looking at what negative activities are likely to happen to the system. 3)  Vulnerability Evaluation – Look at the vulnerabilities and evaluate the biggest weakness in the systems. 4)  Security Control Evaluation – Examine what controls the system already has applied. 5)  Likelihood of occurrence evaluation – The probability that your asset will be exploited is based on the threat source motivation, threat capability, your vulnerability and the security controls you have in place.   Based on all these factors you can calculated the likelihood of an attack or disaster. 6)  Impact Evaluation – This where you gather all the data from asset identification, threat source, vulnerability identification, security controls, likelihood of attack and figure you what would happen if something really did happen.  How important is your system and its data?  What would happen to the mission or bottom line or profits if the system went down for a few hours?  a few days? a few weeks?  Some system are so important that they cannot be down for even a minute.  Impact is very important to the level of risk.  The more important the system is, the high the risk. 7)  Risk Determination / Risk Evaluation – Based on all the data gathered you can make a pretty good risk determination.  You should have defined the systems components and what data is important, made a pretty good conclusion on threat sources and likelihood of the vulnerability exploits and know exactly what kind of impact there will be if the system goes down.  

Risk Assessment Reports (RAR) also known as the Security Assessment Report (SAR) is an essential part of the DIARMF Authorization Package.  This document can be done at anytime after the system is implemented (DIARMF Process step 3) but must be done during DIARMF step 4, Assess for the risk identification of the system.  The Authorization Package consists of the following (but is not limited to): System Security Plan (SSP) – “Formal document that provides an overview of the security requirements for the information system and describes the security controls in place or planned for meeting those requirements.”  — NIST SP 800-18.  This document provides over all system characterization and control analysis for the system.  More on Security Plan  – NIST SP 800-18, Guide for Developing Security Plans for Federal Information Systems Plan of Action and Milestone (POA&M pronounced PO’AM) – “A document that identifies tasks needing to be accomplished. It details resources required to accomplish the elements of the plan, any milestones in meeting the tasks, and scheduled completion dates for the milestones.” — NIST SP 800-18.  After the DIARMF Assessment the POA&M is accomplished to address the residual risks that could not be properly mitigated. Risk Assessment Report / Security Assessment Report (RAR/SAR) – “The process of identifying risks to agency operations (including mission, functions, image, or reputation), agency assets, or individuals by determining the probability of occurrence, the resulting impact, and additional security controls that would mitigate this impact.”  — NIST SP 800-18.  Form more see NIST SP 800-30, Guide for Conducting Risk Assessments. Artifacts – Supporting documents that provide evidence that certain security feature and/or programs exist. NIST SP 800-30, guide on risk assessment, breaks down what should be in a risk assessment report / security assessment report in appendix K, RISK ASSESSMENT REPORTS ESSENTIAL ELEMENTS OF INFORMATION The  risk assessment report / security assessment report results provide decision makers (system owners & authorization officers) with some idea of the risks that will be imposed upon the organization, asset, individuals in the organization, associates of the organization and in some cases the Nation.   The  risk assessment report / security assessment report is broken into three parts:  Executive Summary (audience Managers)  – the executive summary gives a brief high-level view of the overall risk assessment.  It lists the dates of the risk assessment, summarized the purpose and scope and gives a quick idea of the finding. Body of the Report (audience Security Practitioners) – fills out the details of the findings.  In addition to detailing the who, what, when, where and how of the risk assessment, it goes int specific information technology issues.  Since it is mentions specific IP addresses and associated vulnerabilities, it must be considered confidential.  The RAR/SAR may describe how vulnerabilities can be exploited and what was done to fix the weakness to limit the risk. Supporting Appendices – may include actual raw network vulnerability scans.  References & glossary. Template of Risk Assessment Report/Security Assessment: Risk assessment report_Example

risk identification Risk identification is done with a risk assessment.  NIST SP 800-30, Guide for Conducting Risk Assessments breaks down the entire process of risk determination, risk identification. As described in the earlier post DIACAP Process: Risk = ((Vulnerability * Threat) / Countermeasure) * Asset Value at Risk IT Risk Risk is the likelihood that a threat will compromise the weakness of an asset.  So risk identification is based on knowing the threat, the vulnerability and the asset. The better you understand these factors, the better your chances of risk determination and risk identification. NIST SP 800-39, Managing Information Security Risk is a document that defines risk management as the process of not only identifying risk but also, assessing risk, and taking steps to mitigate risks for fit within one of the types or risk, risk acceptance. Risk identification starts off with identification of the asset. 1)  System characterization – Gather information into a System Security Plan (SSP).  Identifying risk requires a deep understanding of the asset and its environment.  Asset information for the SSP will cover the following: Hardware Software System interfaces (e.g., internal and external connectivity) Data and information Persons who support and use the IT system System mission (e.g., the processes performed by the IT system) System and data critical (e.g., the system’s value or importance to an organization) System and data sensitivity 2)  Threat Identification – Without a defined threat, there is no way to quantify or identify a threat.  Threat identification starts with looking at the threat sources and events.  An example to look for threat sources historical data.  When has the asset or similar assets from other related organizations in the same industry been attacked or suffered disaster.  Remember a threat source is not just criminal-hackers and malware, it can be a natural disaster or unintentional destruction of data or a power outage. 3)  Vulnerability Identification – Once the asset and threat are identified, you can more easily determine if your system has a weakness for that particular disaster or exploit.  Again, you can look at historical evidence that suggest weakness.  You can use scanners to find open ports that are exposed to the Internet. 4)  Security Control Analysis – If your system already has security controls in place, you must take that into account because this may lower your risk. 5)  Likelihood determination – The probability that your asset will be exploited is based on the threat source motivation, threat capability, your vulnerability and the security controls you have in place.   Based on all these factors you can calculated the likelihood of an attack or disaster. 6)  Impact Analysis – This where you gather all the data from asset identification, threat source, vulnerability identification, security controls, likelihood of attack and figure you what would happen if something really did happen.  How important is your system and its data?  What would happen to the mission or bottom line or profits if the system went down for a few hours?  a few days? a few weeks?  Some system are so important that they cannot be down for even a minute.  Impact is very important to the level of risk.  The more important the system is, the high the risk. 7)  Risk Determination / Risk Identification – Based on all the data gathered you can make a pretty good risk determination.  You should have defined the systems components and what data is important, made a pretty good conclusion on threat sources and likelihood of the vulnerability exploits and know exactly what kind of impact there will be if the system goes down. Who does risk identification: Ultimately it is the information system owner and authorizing official that must make a determination on what kind of risk they will accept, but they rely heavily on the expertise of an information security engineer, information system security manager,  information system security officer and technical professionals to articulate what is happening on the ground. The ISSO/ISSM/ISSE typically document the process mentioned above or the DIARMF process.  Security professionals coordinate with IT professionals to “get into the weeds” of technical security controls and vulnerabilities.    

The Risk Management Framework steps are designed to minimize, and control the risks to the organization.  The DIARMF process fully adopted many aspects of RMF. NIST SP 800-39, Risk Management Guide for Information Technology Systems is one of the main documents of the RMF process.  It describes types of risk in the chapter on Risk Mitigation: Risk Assumption.  To accept the potential risk and continue operating the IT system or to implement controls to lower the risk to an acceptable level Risk Avoidance.  To avoid the risk by eliminating the risk cause and/or consequence (e.g., forgo certain functions of the system or shut down the system when risks are identified) Risk Limitation.  To limit the risk by implementing controls that minimize the adverse impact of a threat’s exercising a vulnerability (e.g., use of supporting, preventive, detective controls) Risk Planning.  To manage risk by developing a risk mitigation plan that prioritizes, implements, and maintains controls Research and Acknowledgment.  To lower the risk of loss by acknowledging the vulnerability or flaw and researching controls to correct the vulnerability Risk Transference.  To transfer the risk by using other options to compensate for the loss, such as purchasing insurance.  

what is risk The formal definition of “risk” is:  Exposure of someone (or some object) to harm, damage or loss.  In Information Assurance, information security and IT, risk has a pseudo equation to put value on the risk. Risk = ((Vulnerability * Threat) / Countermeasure) * Asset Value at Risk IT Risk Risk is the likelihood that a threat will exploit the vulnerability of an assets value. So in IT, the question what is risk?  is defined with a “threat”, a “vulnerability” and a “asset”.  If any one of these factor is missing, you cannot define or quantify the risk at all.

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. More on DIARMF – Select 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. More on DIARMF – Implement 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. More on DIARMF – Assess 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.   More on DIARMF – Authorization risk management framework – Step 6. Continuous Monitoring After acceptance of risk by the organization, they must develop a program that monitors the ongoing changes to the systems security posture.   They take a proactive approach to watching for advanced persistent threats, configuration changes and new vulnerabilities. Risk management framework step 6 handles all of this.  More on DIARMF – Continuous Monitoring

DITSCAP Supersedes DIACAP? No.  FALSE!! In fact DIACAP replaced (superseded)  by the DIARMF process.  DIACAP replaced DITSCAP 7 years ago.  Now DIACAP is being replaced.   So it was the other way around (7 years ago).  DIACAP superseded DITSCAP.  DIACAP was released about November 2007 and at that time was replaced by DIACAP by most of the Department of Defense. As a system security engineering contractor, I can tell you that MANY organizations clung to DITSCAP for many years after 2007.  Some local government units even made it policy to NOT go to DIACAP.  I think this was out of ignorance or great resistance to change.  The government attracts very conservative, traditionalist that are highly resistant to change.  If you are into doing things faster and smarter and keeping up with the break neck speed of information technology, you will have a frustrating time in the government… ESPECIALLY, if you care. Since DIACAP is now being replaced (circa 2014), its amazing to me that people still even know what DIACAP is!!   What is more amazing to me is people insisting that, “ditscap supersedes diacap”.  That is so wrong that it makes me speechless.  Its like someone insisting that the sun revolved around the Earth.  I cannot use logic against religious belief.  In some cases, its really just that they don’t know any better and are new to C&A/RMF and so its just a matter of giving a quick look at the history of C&A. When I meet DITSCAP fundamentalist, I don’t waste ANYTIME debating regulations.  I mean, its written in black and white.   If they are too lazy to pay attentions to 10 years of C&A evolution, there is nothing to talk about.   I have no intention of changing their beliefs.  I just talk directly to the system owner, if it is within my responsibility and authority to do so.