Component approach. This links to a component representing the Identity Management and Access Control Policy.
That component contains a link to the policy, so it does not have to be linked here too.
-Describe how Part b-1 is satisfied.
Describe how Part b-2 is satisfied.
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 holistic, top-level explanation of the network architecture.
-A diagram-specific explanation.
-A holistic, top-level explanation of the system's data flows.
-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.
-CLI for updating firebase 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.
-An external leveraged system.
-Some description of the external authentication method.
-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.
-Briefly describe the external system.
-Some description of the authentication method.
-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.
-Section 8.1, Figure 8-1 Authorization Boundary Diagram (graphic)
-This should be referenced in the system-characteristics/authorization-boundary/diagram/link/@href flag using a value of "#11111111-2222-4000-8000-001000000054"
-May use rlink with a relative path, or embedded as base64.
FedRAMP prefers base64 for images and diagrams.
Images must be in sufficient resolution to read all detail when rendered in a browser via HTML5.
-The primary network diagram.
-Section 8.1, Figure 8-2 Network Diagram (graphic)
-This should be referenced in the system-characteristics/network-architecture/diagram/link/@href flag using a value of "#11111111-2222-4000-8000-001000000055"
-May use rlink with a relative path, or embedded as base64.
FedRAMP prefers base64 for images and diagrams.
Images must be in sufficient resolution to read all detail when rendered in a browser via HTML5.
-The primary data flow diagram.
-Section 8.1, Figure 8-3 Data Flow Diagram (graphic)
-This should be referenced in the system-characteristics/data-flow/diagram/link/@href flag using a value of "#11111111-2222-4000-8000-001000000056"
-May use rlink with a relative path, or embedded as base64.
FedRAMP prefers base64 for images and diagrams.
Images must be in sufficient resolution to read all detail when rendered in a browser via HTML5.
-