<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<?xml-stylesheet type="text/xsl" href="../part2stratml.xsl"?><PerformancePlanOrReport><Name>About OSCAL</Name><Description>NIST, in collaboration with industry, is developing the Open Security Controls Assessment Language (OSCAL). OSCAL is a set of formats expressed in XML, JSON, and YAML. These formats provide machine-readable representations of control catalogs, control baselines, system security plans, and assessment plans and results...Control-based information expressed using OSCAL formats allows you to:* Easily access control information from security and privacy control catalogs* Establish and share machine-readable control baselines* Maintain and share actionable, up-to-date information about how controls are implemented in your systems* Automate the monitoring and assessment of your system control implementation effectiveness</Description><OtherInformation>Automated Control-Based Assessment Supporting Control-Based Risk Management with Standardized Formats --  NIST is developing the Open Security Controls Assessment Language (OSCAL) as a standardized, data-centric framework that can be applied to an information system for documenting and assessing its security controls. Today, security controls and control baselines are represented in proprietary formats, requiring data conversion and manual effort to describe their implementation. An important goal of OSCAL is to move the security controls and control baselines from a text-based and manual approach (using word processors or spreadsheets) to a set of standardized and machine-readable formats.</OtherInformation><StrategicPlanCore><Organization><Name>National Institute of Standards and Technology</Name><Acronym>NIST</Acronym><Identifier>_36a9a026-66b6-11e0-86fc-e93d7a64ea2a</Identifier><Description/><Stakeholder StakeholderTypeType="Generic_Group"><Name>Security Professionals</Name><Description>You are responsible for documenting security controls and how they are applied within a system. -- With systems security information represented in OSCAL, security professionals will be able to automate security assessment, auditing, and continuous monitoring processes...There are a number of complicating factors contributing to the challenges faced by information system security professionals today.* Multiple regulatory standards and frameworks, which change over time;* Regulatory standards and frameworks overlap in scope and can often conflict or be difficult to manage together; and* Information systems are increasing in size and complexity. ^To address information security and privacy risks, the implementation of selected controls need to be verified and shown to be effective. To provide assurance of a system's security and privacy posture, the control implementation of a system must be both correctly described, assessed, and authorized. These tasks are resource-intensive, and often challenging to perform within budget constraints given the complexity of the problem.The standardized formats provided by the OSCAL project help to streamline and standardize the processes of documenting, implementing and assessing security controls. The automation enabled by the OSCAL formats will reduce complexity, decrease implementation costs, and enable the simultaneous, continuous assessment of a system's security against multiple sets of requirements. Additionally, paperwork will be significantly reduced.</Description></Stakeholder><Stakeholder StakeholderTypeType="Generic_Group"><Name>Security-Related Information Assessors</Name><Description>You are responsible for assessing security-related information produced by others.</Description></Stakeholder><Stakeholder StakeholderTypeType="Generic_Group"><Name>Security-Related Tool Developers</Name><Description>You build tools and utilities to help other players, enabling them to do more work more consistently, thoroughly, accurately and easily.</Description></Stakeholder><Stakeholder StakeholderTypeType="Generic_Group"><Name>Policy Authors</Name><Description>You write policy documents (catalogs or profiles/baselines/overlays) defining, characterizing and customizing security controls for others to use.</Description></Stakeholder></Organization><Vision><Description>Standardized and machine-readable security controls</Description><Identifier>_94f46014-ba38-11ea-a5e2-d1710283ea00</Identifier></Vision><Mission><Description>To provide security control information in machine-readable formats.</Description><Identifier>_94f461c2-ba38-11ea-a5e2-d1710283ea00</Identifier></Mission><Value><Name>Data-Centricity</Name><Description>Transitions the legacy approach to security plan generation and management (Word and Excel documents) to a data-centric approach based on common data standards such as XML/JSON.</Description></Value><Value><Name>Extensibility</Name><Description>Puts security compliance data to work by allowing an extensible architecture that expresses security controls in both machine and human readable formats.</Description></Value><Value><Name>Integration</Name><Description>Allows tool developers to implement APIs and provide a standards-based foundation for next generation compliance tools.</Description></Value><Value><Name>Automation</Name><Description>Apply the benefits of the data-centric approach to automate existing processes that are resource intensive.</Description></Value><Value><Name>Principles</Name><Description>OSCAL Design Principles -- To address these goals, the OSCAL project is guided by the following design principles.</Description></Value><Value><Name>Interoperability</Name><Description>Interoperable Data Formats -- Produce a set of interoperable, extensible, machine-readable formats through a community-focused effort that supports a broad range of control-based risk management processes.</Description></Value><Value><Name>Translation</Name><Description>Provide XML-, JSON-, and YAML-based formats that allow for lossless translations between XML, JSON, and YAML representations.</Description></Value><Value><Name>Identification</Name><Description>Provide a common means to identify and version shared resources.</Description></Value><Value><Name>Standardization</Name><Description>Standardize the expression of assessment artifacts, driving crowd-sourced development and improvement across profile and implementation layers.</Description></Value><Value><Name>Relevance</Name><Description>Be Relevant Now, Enable a Better Future -- Align OSCAL models with current, practical information, and support advanced structures that provide for greater automation and verification.</Description></Value><Value><Name>Traceability</Name><Description>Ensure security controls, implementation, and assessment processes have full traceability to the selected control baseline and across system boundaries for interconnected systems and common control providers.</Description></Value><Value><Name>Adoption</Name><Description>Provide a path for early adoption and ongoing evolution around how OSCAL will be used.</Description></Value><Value><Name>Evolution</Name><Description/></Value><Goal><Name>Paperwork</Name><Description>Decrease Paperwork</Description><Identifier>_94f462b2-ba38-11ea-a5e2-d1710283ea00</Identifier><SequenceIndicator>1</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name>Information Security Professionals</Name><Description/></Stakeholder><Stakeholder StakeholderTypeType="Generic_Group"><Name>Information Security Vendors</Name><Description/></Stakeholder><OtherInformation>Drive a large decrease in the paperwork burden for both information security professionals and vendors.</OtherInformation><Objective><Name>Catalogs, Frameworks &amp; Information</Name><Description>Normalize the representation of security control catalogs, regulatory frameworks, and system information using precise, machine readable formats.</Description><Identifier>_94f463fc-ba38-11ea-a5e2-d1710283ea00</Identifier><SequenceIndicator>1.1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Information Sharing</Name><Description>Allow the sharing of control implementation information across communities.</Description><Identifier>_94f464ec-ba38-11ea-a5e2-d1710283ea00</Identifier><SequenceIndicator>1.2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Security Assessments</Name><Description>Improve System Security Assessments</Description><Identifier>_94f465c8-ba38-11ea-a5e2-d1710283ea00</Identifier><SequenceIndicator>2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>Improve the efficiency, accuracy, and consistency of system security assessments.</OtherInformation><Objective><Name>Requirements &amp; Traceability</Name><Description>Assess a system's security control implementation against several sets of requirements simultaneously and ensure traceability between the requirements.</Description><Identifier>_94f466b8-ba38-11ea-a5e2-d1710283ea00</Identifier><SequenceIndicator>2.1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Consistency</Name><Description>Enable assessments to be performed consistently, regardless of system type.</Description><Identifier>_94f4679e-ba38-11ea-a5e2-d1710283ea00</Identifier><SequenceIndicator>2.2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Continuity</Name><Description>Enable Continuous Assessment</Description><Identifier>_94f46884-ba38-11ea-a5e2-d1710283ea00</Identifier><SequenceIndicator>3</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>Allow a system's security state to be assessed more often, ideally continuously, driving continuous assurance.</OtherInformation><Objective><Name>Labor &amp; Time</Name><Description>Drive a large decrease in assessment-related labor, decreasing assessment and authorization time.</Description><Identifier>_94f46974-ba38-11ea-a5e2-d1710283ea00</Identifier><SequenceIndicator>3.1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Effectiveness</Name><Description>Support the assessment of control implementation effectiveness based on data collected using a continuous monitoring capability.</Description><Identifier>_94f46a5a-ba38-11ea-a5e2-d1710283ea00</Identifier><SequenceIndicator>3.2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal></StrategicPlanCore><AdministrativeInformation><StartDate>2020-06-03</StartDate><EndDate/><PublicationDate>2020-06-29</PublicationDate><Source>https://pages.nist.gov/OSCAL/</Source><Submitter><GivenName>Owen</GivenName><Surname>Ambur</Surname><PhoneNumber/><EmailAddress>Owen.Ambur@verizon.net</EmailAddress></Submitter></AdministrativeInformation></PerformancePlanOrReport>
