OSCAL System Security Plan (SSP)
1.0.5Schema URL
Properties
Definitions
A system security plan, such as those described in NIST SP 800-18
A type 4 ('random' or 'pseudorandom') or type 5 UUID per RFC 4122.
Used to import the OSCAL profile representing the system's control baseline.
Contains the characteristics of the system, such as its name, purpose, and security impact level.
A summary of the system.
Contains details about all information types that are stored, processed, or transmitted by the system, such as privacy information, and those defined in NIST SP 800-60.
If the selected security level is different from the base security level, this contains the justification for the change.
The overall level of expected impact resulting from unauthorized disclosure, modification, or loss of access to information.
Describes the operational status of the system.
A description of this system's authorization boundary, optionally supplemented by diagrams that illustrate the authorization boundary.
A summary of the system's authorization boundary.
A graphic that provides a visual representation the system, or some aspect of it.
A type 4 ('random' or 'pseudorandom') or type 5 UUID per RFC 4122.
A summary of the diagram.
A brief caption to annotate the diagram.
A description of the system's network architecture, optionally supplemented by diagrams that illustrate the network architecture.
A summary of the system's network architecture.
A description of the logical flow of information within the system and across its boundaries, optionally supplemented by diagrams that illustrate these flows.
A summary of the system's data flow.
Provides information as to how the system is implemented.
Describes how the system satisfies a set of controls.
A statement describing important things to know about how this set of control satisfaction documentation is approached.
Describes how the system satisfies the requirements of an individual control.
A type 4 ('random' or 'pseudorandom') or type 5 UUID per RFC 4122.
Identifies which statements within a control are addressed.
A type 4 ('random' or 'pseudorandom') or type 5 UUID per RFC 4122.
Defines how the referenced component implements a set of controls.
A type 4 ('random' or 'pseudorandom') or type 5 UUID per RFC 4122.
A type 4 ('random' or 'pseudorandom') or type 5 UUID per RFC 4122.
An implementation statement that describes how a control or a control statement is implemented within the referenced system component.
Identifies content intended for external consumption, such as with leveraged organizations.
6 nested properties
An implementation statement that describes the aspects of the control or control statement implementation that can be available to another system leveraging this system.
Provides information about the publication and availability of the containing document.
A name given to the document, which may be used by a tool for display and navigation.
An entry in a sequential list of revisions to the containing document in reverse chronological order (i.e., most recent previous revision first).
A name given to the document revision, which may be used by a tool for display and navigation.
A location, with associated metadata that can be referenced.
A type 4 ('random' or 'pseudorandom') or type 5 UUID per RFC 4122.
A name given to the location, which may be used by a tool for display and navigation.
A type 4 ('random' or 'pseudorandom') or type 5 UUID per RFC 4122.
A responsible entity which is either a person or an organization.
A type 4 ('random' or 'pseudorandom') or type 5 UUID per RFC 4122.
A category describing the kind of party the object describes.
A type 4 ('random' or 'pseudorandom') or type 5 UUID per RFC 4122.
Defines a function assumed or expected to be assumed by a party in a specific situation.
A name given to the role, which may be used by a tool for display and navigation.
A summary of the role's purpose and associated responsibilities.
A collection of resources, which may be included directly or by reference.
An attribute, characteristic, or quality of the containing object expressed as a namespace qualified name/value pair. The value of a property is a simple scalar value, which may be expressed as a list of values.
A textual label that uniquely identifies a specific attribute, characteristic, or quality of the property's containing object.
A type 4 ('random' or 'pseudorandom') or type 5 UUID per RFC 4122.
A reference to a local or remote resource
Describes the type of relationship provided by the link. This can be an indicator of the link's purpose.
A textual label to associate with the link, which may be used for presentation in a tool.
A reference to a set of organizations or persons that have responsibility for performing a referenced role in the context of the containing object.
A reference to one or more roles with responsibility for performing a function relative to the containing object.
A representation of a cryptographic digest generated over a resource using a specified hash algorithm.
Additional commentary on the containing object.
Contact number by telephone.
A document identifier qualified by an identifier scheme. A document identifier provides a globally unique identifier with a cross-instance scope that is used for a group of documents that are to be treated as different versions of the same document. If this element does not appear, or if the value of this element is empty, the value of "document-id" is equal to the value of the "uuid" flag of the top-level root element.
Qualifies the kind of document identifier using a URI. If the scheme is not provided the value of the element will be interpreted as a string of characters.
A defined component that can be part of an implemented system.
A type 4 ('random' or 'pseudorandom') or type 5 UUID per RFC 4122.
A human readable name for the system component.
A description of the component, including information about its function.
Describes the operational status of the system component.
2 nested properties
A summary of the technological or business purpose of the component.
Information about the protocol used to provide a service.
A type 4 ('random' or 'pseudorandom') or type 5 UUID per RFC 4122.
A human readable name for the protocol (e.g., Transport Layer Security).
Where applicable this is the IPv4 port range on which the service operates.
Indicates the degree to which the a given control is implemented.
Identifies the implementation status of the control or control objective.
A type of user that interacts with the system based on an associated role.
A type 4 ('random' or 'pseudorandom') or type 5 UUID per RFC 4122.
A name given to the user, which may be used by a tool for display and navigation.
A summary of the user's purpose within the system.
Identifies a specific system privilege held by the user, along with an associated description and/or rationale for the privilege.
A human readable name for the privilege.
A summary of the privilege's purpose within the system.
A single managed inventory item within the system.
A type 4 ('random' or 'pseudorandom') or type 5 UUID per RFC 4122.
A summary of the inventory item stating its purpose within the system.
Identifies the parameter that will be set by the enclosed value.
A human-oriented, globally unique identifier with cross-instance scope that can be used to reference this system identification property elsewhere in this or other OSCAL instances. When referencing an externally defined system identification, the system identification must be used in the context of the external / imported OSCAL instance (e.g., uri-reference). This string should be assigned per-subject, which means it should be consistently used to identify the same system across revisions of the document.
Identifies the identification system from which the provided identifier was assigned.
A partition of a control's definition or a child of another part.
A name given to the part, which may be used by a tool for display and navigation.
Permits multiple paragraphs, lists, tables etc.
Parameters provide a mechanism for the dynamic assignment of value(s) in a control.
A short, placeholder name for the parameter, which can be used as a substitute for a value if no value is assigned.
Describes the purpose and use of a parameter
A formal or informal expression of a constraint or test
A textual summary of the constraint to be applied.
A prose statement that provides a recommendation for the use of a parameter.
Prose permits multiple paragraphs, lists, tables etc.
Presenting a choice among alternatives
Describes the number of selections that must occur. Without this setting, only one value should be assumed to be permitted.
Include all controls from the imported catalog or profile resources.
A type 4 ('random' or 'pseudorandom') or type 5 UUID per RFC 4122.