Senior official with authority to formally assume responsibility for operating a system at an acceptable level of risk.
+This party prepared the SSP.
+The organization for which this SSP was prepared. Typically the CSP.
+The highest level manager who is responsible for system operation on behalf of the System Owner.
+The individual or individuals leading the technical operation of the system.
+A general point of contact for the system, designated by the system owner.
+This SSP is an example for demonstration purposes.
+This is an enhanced example system for demonstration purposes, incorporating more FedRAMP-specific elements.
+Remarks are required if deployment model is "hybrid-cloud" or "other". Optional otherwise.
+Remarks are required if service model is "other". Optional otherwise.
+Contains sensitive financial data related to organizational operations.
+Required if the base and selected values do not match.
+Required if the base and selected values do not match.
+The authorization boundary includes all components within the main data center and the disaster recovery site.
+A diagram-specific explanation.
+A diagram-specific explanation.
+A holistic, top-level explanation of the network architecture.
+A diagram-specific explanation.
+A diagram-specific explanation.
+A holistic, top-level explanation of the system's data flows.
+A diagram-specific explanation.
+A diagram-specific explanation.
+Use one leveraged-authorization assembly for each underlying system. In the legacy world, these may be general support systems.
+The link fields are optional, but preferred when known. Often, a leveraging system's SSP author will not have access to the leveraged system's SSP, but should have access to the leveraged system's CRM.
+admin user
Main application server hosting the core system functionality.
+This is the primary application server for the system.
+An external leveraged system.
+Secure connection to an external API for data enrichment.
+Some description of the authentication method.
+This connection is used for secure data exchange with external systems.
+Primary database server
+Secondary database server
+Implementation of controls for the Enhanced Example System
+Access Control Policy and Procedures (AC-1) is fully implemented in our system.
+Information System Component Inventory (CM-8) is partially implemented.
+Detailed access control policy document
+User's Guide
+Table 12-1 Attachments: User's Guide Attachment
+May use rlink with a relative path, or embedded as base64.
Rules of Behavior
+Table 12-1 Attachments: Rules of Behavior (ROB)
+May use rlink with a relative path, or embedded as base64.
Contingency Plan (CP)
+Table 12-1 Attachments: Contingency Plan (CP) Attachment
+May use rlink with a relative path, or embedded as base64.
Configuration Management (CM) Plan
+Table 12-1 Attachments: Configuration Management (CM) Plan Attachment
+May use rlink with a relative path, or embedded as base64.
Incident Response (IR) Plan
+Table 12-1 Attachments: Incident Response (IR) Plan Attachment
+May use rlink with a relative path, or embedded as base64.
Separation of Duties Matrix
+May use rlink with a relative path, or embedded as base64.
The primary authorization boundary diagram.
+May use rlink with a relative path, or embedded as base64.
The primary authorization boundary diagram.
+May use rlink with a relative path, or embedded as base64.
The primary network diagram.
+May use rlink with a relative path, or embedded as base64.
The primary network diagram.
+May use rlink with a relative path, or embedded as base64.
The primary data flow diagram.
+May use rlink with a relative path, or embedded as base64.
The primary data flow diagram.
+May use rlink with a relative path, or embedded as base64.