question
stringlengths 13
90
| context
stringclasses 1
value | answer
stringlengths 1
5.37k
|
|---|---|---|
SC-7 (3) Control Enhancement (M) (H) | Refer to the specific section and subsections for details. | The organization limits the number external network connections to the information system.
|SC-7 (3)|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|SC-7 (3) What is the solution and how is it implemented?|
|---|
|Part a
# |
SC-7 (4) Control Enhancement (M) | Refer to the specific section and subsections for details. | The organization:
<ol type="a">
<li>Implements a managed interface for each external telecommunication service;</li>
<li>Establishes a traffic flow policy for each managed interface;</li>
<li>Protects the confidentiality and integrity of the information being transmitted across each interface;</li>
<li>Documents each exception to the traffic flow policy with a supporting mission/business need and duration of that need; and</li>
<li>Reviews exceptions to the traffic flow policy [FedRAMP Assignment: at least at least annually] and removes exceptions that are no longer supported by an explicit mission/business need.</li>
</ol>
|SC-7 (4)|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter SC-7(4)(e):
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|SC-7 (4) What is the solution and how is it implemented?|
|---|
|Part a
|Part b
|Part c
|Part d
|Part e
# |
SC-7 (5) Control Enhancement (M) (H) | Refer to the specific section and subsections for details. | The information system at managed interfaces denies network traffic by default and allows network communications traffic by exception (i.e., deny all, permit by exception).
|SC-7 (5)|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|SC-7 (5) What is the solution and how is it implemented?|
|---|
|Part a
# |
SC-7 (7) Control Enhancement (M) (H) | Refer to the specific section and subsections for details. | The information system, in conjunction with a remote device, prevents the device from simultaneously establishing non-remote connections with the system and communicating via some other connection to resources in external networks.
|SC-7 (7)|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|SC-7 (7) What is the solution and how is it implemented?|
|---|
||
# |
SC-7 (8) Control Enhancement (M) (H) | Refer to the specific section and subsections for details. | The information system routes [Assignment: organization-defined internal communications traffic] to [Assignment: organization-defined external networks] through authenticated proxy servers at managed interfaces.
|SC-7 (8)|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter SC-7(8)-1:
|Parameter SC-7(8)-2:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|SC-7 (8) What is the solution and how is it implemented?|
|---|
||
# |
SC-7 (12) Control Enhancement (M) | Refer to the specific section and subsections for details. | The organization implements [Assignment: organization-defined host-based boundary protection mechanisms] at [Assignment: organization-defined information system components].
|SC-7 (12)|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter SC-7(12)-1:
|Parameter SC-7(12)-2:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|SC-7 (12) What is the solution and how is it implemented?|
|---|
||
# |
SC-7 (13) Control Enhancement (M) | Refer to the specific section and subsections for details. | The organization isolates [FedRAMP Assignment: See SC-7 (13) additional FedRAMP Requirements and Guidance] from other internal information system components by implementing physically separate subnetworks with managed interfaces to other components of the system.<br>
<b>SC-7 (13) Additional FedRAMP Requirements and Guidance:</b><br>
<b>Requirement:</b> The service provider defines key information security tools, mechanisms, and support components associated with system and security administration and isolates those tools, mechanisms, and support components from other internal information system components via physically or logically separate subnets.
|SC-7 (13)|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter SC-7(13):
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|SC-7 (13) What is the solution and how is it implemented?|
|---|
||
# |
SC-7 (18) Control Enhancement (M) (H) | Refer to the specific section and subsections for details. | The information system fails securely in the event of an operational failure of a boundary protection device.
|SC-7 (18)|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|SC-7 (18) What is the solution and how is it implemented?|
|---|
||
# |
SC-8 Transmission confidentiality and Integrity (M) (H) | Refer to the specific section and subsections for details. | The information system protects the [FedRAMP Assignment: confidentiality AND integrity] of transmitted information.
|SC-8|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|SC-8 What is the solution and how is it implemented?|
|---|
||
# |
SC-8 (1) Control Enhancement (M) (H) | Refer to the specific section and subsections for details. | The information system implements cryptographic mechanisms to [FedRAMP Assignment: prevent unauthorized disclosure of information AND detect changes to information] during transmission unless otherwise protected by [FedRAMP Assignment: a hardened or alarmed carrier Protective Distribution System (PDS)].
|SC-8 (1)|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter SC-8 (1)-1:
|Parameter SC-8 (1)-2:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|SC-8 (1) What is the solution and how is it implemented?|
|---|
||
# |
SC-10 Network Disconnect (M) | Refer to the specific section and subsections for details. | The information system terminates the network connection associated with a communications session at the end of the session or after [FedRAMP Assignment: no longer than thirty (30) minutes for RAS-based sessions and no longer than sixty (60) minutes for non-interactive user sessions] of inactivity.
|SC-10|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter SC-10:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|SC-10 What is the solution and how is it implemented?|
|---|
||
# |
SC-12 Cryptographic Key Establishment & Management (L) (M) (H) | Refer to the specific section and subsections for details. | The organization establishes and manages cryptographic keys for required cryptography employed within the information system in accordance with [Assignment: organization-defined requirements for key generation, distribution, storage, access, and destruction].<br>
<b>SC-12 Additional FedRAMP Requirements and Guidance:</b><br>
<b>Guidance:</b> Federally approved and validated cryptography.
|SC-12|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter SC-12:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|SC-12 What is the solution and how is it implemented?|
|---|
||
# |
SC-12 (2) Control Enhancement (M) (H) | Refer to the specific section and subsections for details. | The organization produces, controls, and distributes symmetric cryptographic keys using [FedRAMP Selection: NIST FIPS-compliant] key management technology and processes.
|SC-12 (2)|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter SC-12 (2):
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|SC-12 (2) What is the solution and how is it implemented?|
|---|
||
# |
SC-12 (3) Control Enhancement (M) (H) | Refer to the specific section and subsections for details. | The organization produces, controls, and distributes asymmetric cryptographic keys using [Selection: NSA-approved key management technology and processes; approved PKI Class 3 certificates or prepositioned keying material; approved PKI Class 3 or Class 4 certificates and hardware security tokens that protect the user’s private key].
|SC-12 (3)|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter SC-12 (3):
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|SC-12 (3) What is the solution and how is it implemented?|
|---|
||
# |
SC-13 Use of Cryptography (L) (M) (H) | Refer to the specific section and subsections for details. | The information system implements [FedRAMP Assignment: FIPS-validated or NSA-approved cryptography] in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards.
|SC-13|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter SC-13:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|SC-13 What is the solution and how is it implemented?|
|---|
||
# |
SC-15 Collaborative Computing Devices (M) (H) | Refer to the specific section and subsections for details. | The information system:
<ol type="a">
<li>Prohibits remote activation of collaborative computing devices with the following exceptions:[FedRAMP Assignment: no exceptions]; and</li>
<li>Provides an explicit indication of use to users physically present at the devices.</li>
<b>SC-15 Additional FedRAMP Requirements and Guidance:</b><br>
<b>Requirement:</b> The information system provides disablement (instead of physical disconnect) of collaborative computing devices in a manner that supports ease of use.
</ol>
|SC-15|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter SC-15(a):
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|SC-15 What is the solution and how is it implemented?|
|---|
|Part a
|Part b
<b>SC-15 Additional FedRAMP Requirements and Guidance: </b><br>
<b>Requirement:</b> The information system provides disablement (instead of physical disconnect) of collaborative computing devices in a manner that supports ease of use.
|SC-15 req.|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter SC-15(a):
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|SC-15 What is the solution and how is it implemented?|
|---|
|Req. 1|
# |
SC-17 Public Key Infrastructure Certificates (M) (H) | Refer to the specific section and subsections for details. | The organization issues public key certificates under an [Assignment: organization-defined certificate policy] or obtains public key certificates from an approved service provider.
|SC-17|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter SC-17:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|SC-17 What is the solution and how is it implemented?|
|---|
||
# |
SC-18 Mobile Code (M) (H) | Refer to the specific section and subsections for details. | The organization:
<ol type="a">
<li>Defines acceptable and unacceptable mobile code and mobile code technologies;</li>
<li>Establishes usage restrictions and implementation guidance for acceptable mobile code and mobile code technologies; and</li>
<li>Authorizes, monitors, and controls the use of mobile code within the information system.</li>
</ol>
|SC-18|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|SC-18 What is the solution and how is it implemented?|
|---|
|Part a
|Part b
|Part c
## |
SC-19 Voice Over Internet Protocol (M) (H) | Refer to the specific section and subsections for details. | The organization:
<ol type="a">
<li>Establishes usage restrictions and implementation guidance for Voice over Internet Protocol (VoIP) technologies based on the potential to cause damage to the information system if used maliciously; and</li>
<li>Authorizes, monitors, and controls the use of VoIP within the information system.</li>
</ol>
|SC-19|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|SC-19 What is the solution and how is it implemented?|
|---|
|Part a
|Part b
# |
SC-20 Secure Name / Address Resolution Service (Authoritative Source) (L) (M) (H) | Refer to the specific section and subsections for details. | The information system:
<ol type="a">
<li>Provides additional data origin authentication and integrity verification artifacts along with the authoritative name resolution data the system returns in response to external name/address resolution queries; and</li>
<li>Provides the means to indicate the security status of child zones and (if the child supports secure resolution services) to enable verification of a chain of trust among parent and child domains, when operating as part of a distributed, hierarchical namespace.</li>
</ol>
|SC-20|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|SC-20 What is the solution and how is it implemented?|
|---|
|Part a
|Part b
# |
SC-21 Secure Name / Address Resolution Service (Recursive or Caching Resolver) (L) (M) (H) | Refer to the specific section and subsections for details. | The information system requests and performs data origin authentication and data integrity verification on the name/address resolution responses the system receives from authoritative sources.
|SC-21|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|SC-21|Control Summary Information|
|---|---|
|//date|
|SC-21 What is the solution and how is it implemented?|
|---|
||
# |
SC-22 Architecture and Provisioning for Name / Address Resolution Service (L) (M) (H) | Refer to the specific section and subsections for details. | The information systems that collectively provide name/address resolution service for an organization are fault-tolerant and implement internal/external role separation.
|SC-22|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
SC-22 What is the solution and how is it implemented?|
|---|
||
# |
SC-23 Session Authenticity (M) (H) | Refer to the specific section and subsections for details. | The information system protects the authenticity of communications sessions.
|SC-23|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|SC-23 What is the solution and how is it implemented|
|---|
||
# |
SC-28 Protection of Information at Rest (M) (H) | Refer to the specific section and subsections for details. | The information system protects the [FedRAMP Selection: confidentiality AND integrity]] of [Assignment: organization-defined information at rest].
<b>SC-28 Additional FedRAMP Requirements and Guidance:</b><br>
<b>Guidance:</b> The organization supports the capability to use cryptographic mechanisms to protect information at rest.
|SC-28|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter SC-28-1:
|Parameter SC-28-2:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|SC-28 What is the solution and how is it implemented?|
|---|
||
# |
SC-28 (1) Control Enhancement (M) | Refer to the specific section and subsections for details. | The information system implements cryptographic mechanisms to prevent unauthorized disclosure and modification of [Assignment: organization-defined information] on [Assignment: organization-defined information system components]
|SC-28 (1)|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter SC-28(1)-1:
|Parameter SC-28(1)-2:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|SC-28 (1) What is the solution and how is it implemented?|
|---|
||
# |
SC-39 Process Isolation (L) (M) (H) | Refer to the specific section and subsections for details. | The information system maintains a separate execution domain for each executing process.
|SC-39|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|SC-39 What is the solution and how is it implemented?|
|---|
|| |
Maintenance (MA) | Refer to the specific section and subsections for details. | # |
MA-1 System Maintenance Policy and Procedures (L) (M) | Refer to the specific section and subsections for details. | The organization:
<ol type="a">
<li>Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]:</li>
<ol type="1">
<li>A system maintenance policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and</li>
<li>Procedures to facilitate the implementation of the system maintenance policy and associated system maintenance controls; and</li>
</ol>
<li>Reviews and updates the current:</li>
<ol type="1">
<li>System maintenance policy [FedRAMP Assignment: at least every three (3) years]; and</li>
<li>System maintenance procedures [FedRAMP Assignment: at least annually].</li>
</ol>
</ol>
|MA-1|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter MA-1(a):
|Parameter MA-1(b)(1):
|Parameter MA-1(b)(2):
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)
|MA-1 What is the solution and how is it implemented?|
|---|
|Part a
|Part b
# |
MA-2 Controlled Maintenance (L) (M) (H) | Refer to the specific section and subsections for details. | The organization:
<ol type="a">
<li>Schedules, performs, documents, and reviews records of maintenance and repairs on information system components in accordance with manufacturer or vendor specifications and/or organizational requirements;</li>
<li>Approves and monitors all maintenance activities, whether performed on site or remotely and whether the equipment is serviced on site or removed to another location;</li>
<li>Requires that [Assignment: organization-defined personnel or roles] explicitly approve the removal of the information system or system components from organizational facilities for off-site maintenance or repairs;</li>
<li>Sanitizes equipment to remove all information from associated media prior to removal from organizational facilities for off-site maintenance or repairs;</li>
<li>Checks all potentially impacted security controls to verify that the controls are still functioning properly following maintenance or repair actions; and</li>
<li>Includes [Assignment: organization-defined maintenance-related information] in organizational maintenance records.</li>
</ol>
|MA-2|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter MA-2(c):
|Parameter MA-2(f):
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|MA-2 What is the solution and how is it implemented?|
|---|
|Part a
|Part b
|Part c
|Part d
|Part e
|Part f
# |
MA-3 Maintenance Tools (M) (H) | Refer to the specific section and subsections for details. | The organization approves, controls, and monitors information system maintenance tools.
|MA-3|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|MA-3 What is the solution and how is it implemented?|
|---|
||
# |
MA-3 (1) Control Enhancement (M) (H) | Refer to the specific section and subsections for details. | The organization inspects the maintenance tools carried into a facility by maintenance personnel for improper or unauthorized modifications.
|MA-3 (1)|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|MA-3 (1) What is the solution and how is it implemented?|
|---|
||
# |
MA-3 (2) Control Enhancement (M) (H) | Refer to the specific section and subsections for details. | The organization checks media containing diagnostic and test programs for malicious code before the media are used in the information system.
|MA-3 (2)|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|MA-3 (2) What is the solution and how is it implemented?|
|---|
||
# |
MA-3 (3) Control Enhancement (M) (H) | Refer to the specific section and subsections for details. | The organization prevents the unauthorized removal of maintenance equipment containing organizational information by:
<ol type="a">
<li>Verifying that there is no organizational information contained on the equipment;</li>
<li>Sanitizing or destroying the equipment;</li>
<li>Retaining the equipment within the facility; or</li>
<li>Obtaining an exemption from [FedRAMP Assignment: the information owner explicitly authorizes removal of the equipment from the facility].</li>
</ol>
|MA-3 (3)|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter MA-3(3)(d):
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|MA-3 (3) What is the solution and how is it implemented?|
|---|
|Part a
|Part b
|Part c
|Part d
# |
MA-4 Remote Maintenance (L) (M) (H) | Refer to the specific section and subsections for details. | The organization:
<ol type="a">
<li>Approves and monitors nonlocal maintenance and diagnostic activities;</li>
<li>Allows the use of nonlocal maintenance and diagnostic tools only as consistent with organizational policy and documented in the security plan for the information system;</li>
<li>Employs strong authenticators in the establishment of nonlocal maintenance and diagnostic sessions;</li>
<li>Maintains records for nonlocal maintenance and diagnostic activities; and</li>
<li>Terminates session and network connections when nonlocal maintenance is completed.</li>
</ol>
|MA-4|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|MA-4 What is the solution and how is it implemented?|
|---|
|Part a
|Part b
|Part c
|Part d
|Part e
# |
MA-4 (2) Control Enhancement (M) (H) | Refer to the specific section and subsections for details. | The organization documents in the security plan for the information system, the policies and procedures for the establishment and use of nonlocal maintenance and diagnostic connections.
|MA-4 (2)|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|MA-4 (2) What is the solution and how is it implemented?|
|---|
||
# |
MA-5 Maintenance Personnel (L) (M) (H) | Refer to the specific section and subsections for details. | The organization:
<ol type="a">
<li>Establishes a process for maintenance personnel authorization and maintains a list of authorized maintenance organizations or personnel;</li>
<li>Ensures that non-escorted personnel performing maintenance on the information system have required access authorizations; and</li>
<li>Designates organizational personnel with required access authorizations and technical competence to supervise the maintenance activities of personnel who do not possess the required access authorizations.</li>
</ol>
|MA-5|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|MA-5 What is the solution and how is it implemented?|
|---|
|Part a
|Part b
|Part c
# |
MA-5 (1) Control Enhancement (L) (M) | Refer to the specific section and subsections for details. | The organization:
<ol type="a">
<li>Implements procedures for the use of maintenance personnel that lack appropriate security clearances or are not U.S. citizens, that include the following requirements:</li>
<ol type="1">
<li>Maintenance personnel who do not have needed access authorizations, clearances, or formal access approvals are escorted and supervised during the performance of maintenance and diagnostic activities on the information system by approved organizational personnel who are fully cleared, have appropriate access authorizations, and are technically qualified;</li>
<li>Prior to initiating maintenance or diagnostic activities by personnel who do not have needed access authorizations, clearances or formal access approvals, all volatile information storage components within the information system are sanitized and all nonvolatile storage media are removed or physically disconnected from the system and secured; and</li>
</ol>
<li>Develops and implements alternate security safeguards in the event an information system component cannot be sanitized, removed, or disconnected from the system.</li>
<b>MA-5 (1) Additional FedRAMP Requirements and Guidance:</b><br>
<b>Requirement:</b> Only MA-5 (1) (a) (1) is required by FedRAMP
</ol>
|MA-5 (1)|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|MA-5 (1) What is the solution and how is it implemented?|
|---|
|Part a
|Part b
# |
MA-6 Timely Maintenance (M) (H) | Refer to the specific section and subsections for details. | The organization obtains maintenance support and/or spare parts for [Assignment: organization-defined information system components] within [Assignment: organization-defined time period] of failure.
|MA-6|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter MA-6(1):
|Parameter MA-6(2):
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|MA-6 What is the solution and how is it implemented?|
|---|
|Part a
|Part b |
Identification and Authentication (IA) | Refer to the specific section and subsections for details. | # |
IA-1 Identification and Authentication Policy and Procedures (L) (M) | Refer to the specific section and subsections for details. | The organization:
<ol type="a">
<li>Develops, documents, and disseminates to [Assignment: organization-defined personnel or roles]:</li>
<ol type="1">
<li>An identification and authentication policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and</li>
<li>Procedures to facilitate the implementation of the identification and authentication policy and associated identification and authentication controls; and</li>
</ol>
<li>Reviews and updates the current:</li>
<ol type="1">
<li>Identification and authentication policy [FedRAMP Assignment: at least every three (3) years]; and</li>
<li>Identification and authentication procedures [FedRAMP Assignment: at least annually].</li>
</ol>
</ol>
|IA-1|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter IA-1(a):
|Parameter IA-1(a):
|Parameter IA-1(b)(1):
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)
|IA-1 What is the solution and how is it implemented?|
|---|
|Part a|
|Part b|
# |
IA-2 User Identification and Authentication (L) (M) (H) | Refer to the specific section and subsections for details. | The information system uniquely identifies and authenticates organizational users (or processes acting on behalf of organizational users).
|IA-2|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|IA-2 What is the solution and how is it implemented?|
|---
||
# |
IA-2 (1) Control Enhancement (L) (M) (H) | Refer to the specific section and subsections for details. | The information system implements multifactor authentication for network access to privileged accounts.
|IA-2 (1)|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|IA-2 (1) What is the solution and how is it implemented?|
|---
||
# |
IA-2 (2) Control Enhancement (M) (H) | Refer to the specific section and subsections for details. | The information system implements multifactor authentication for network access to non-privileged accounts.
|IA-2 (2)|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|IA-2 (2) What is the solution and how is it implemented?|
|---
||
# |
IA-2 (3) Control Enhancement (M) (H) | Refer to the specific section and subsections for details. | The information system implements multifactor authentication for local access to privileged accounts.
|IA-2 (3)|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|IA-2 (3) What is the solution and how is it implemented?|
|---
||
# |
IA-2 (5) Control Enhancement (M) (H) | Refer to the specific section and subsections for details. | The organization requires individuals to be authenticated with an individual authenticator when a group authenticator is employed.
|IA-2 (5)|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|IA-2 (5) What is the solution and how is it implemented?|
|---
||
# |
IA-2 (8) Control Enhancement (M) (H) | Refer to the specific section and subsections for details. | The information system implements replay-resistant authentication mechanisms for network access to privileged accounts.
# |
IA-2 (5) Control Enhancement (M) (H) | Refer to the specific section and subsections for details. | The organization requires individuals to be authenticated with an individual authenticator when a group authenticator is employed.
|IA-2 (8)|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|IA-2 (8) What is the solution and how is it implemented?|
|---
||
# |
IA-2 (11) Control Enhancement (M) (H) | Refer to the specific section and subsections for details. | The information system implements multifactor authentication for remote access to privileged and non-privileged accounts such that one of the factors is provided by a device separate from the system gaining access and the device meets [FedRAMP Assignment: FIPS 140-2, NIAP* Certification, or NSA approval].
*National Information Assurance Partnership (NIAP)<br>
<b>Additional FedRAMP Requirements and Guidance:</b><br>
<b>Guidance:</b> PIV = separate device. Please refer to NIST SP 800-157 Guidelines for Derived Personal Identity Verification (PIV) Credentials. FIPS 140-2 means validated by the Cryptographic Module Validation Program (CMVP).
|IA-2 (11)|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter IA-2(11):
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|IA-2 (11) What is the solution and how is it implemented?|
|---
||
# |
IA-2 (12) Control Enhancement (L) (M) (H) | Refer to the specific section and subsections for details. | The information system accepts and electronically verifies Personal Identity Verification (PIV) credentials.
<b>IA-2 (12) Additional FedRAMP Requirements and Guidance:</b><br>
<b>Guidance:</b> Include Common Access Card (CAC), i.e., the DoD technical implementation of PIV/FIPS 201/HSPD-12.
|IA-2 (12)|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|IA-2 (12) What is the solution and how is it implemented?|
|---
||
# |
IA-3 Device Identification and Authentication (M) (H) | Refer to the specific section and subsections for details. | The information system uniquely identifies and authenticates [Assignment: organization-defined specific and/or types of devices] before establishing a [Selection (one or more): local; remote; network] connection.
|IA-3|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter IA-3-1:
|Parameter IA-3-2:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|IA-3 What is the solution and how is it implemented?|
|---
||
# |
IA-4 Identifier Management (L) (M) | Refer to the specific section and subsections for details. | The organization manages information system identifiers for users and devices by:
<ol type="a">
<li>Receiving authorization from [Assignment: organization-defined personnel or roles] to assign an individual, group, role, or device identifier;</li>
<li>Selecting an identifier that identifies an individual, group, role, or device;</li>
<li>Assigning the identifier to the intended individual, group, role, or device;</li>
<li>Preventing reuse of identifiers for [FedRAMP Assignment: at least two (2) years]; and</li>
<li>Disabling the identifier after [FedRAMP Assignment: ninety days for user identifiers (see additional requirements and guidance)]</li>
<b>IA-4e Additional FedRAMP Requirements and Guidance:</b><br>
<b>Requirement:</b> The service provider defines the time period of inactivity for device identifiers.
<b>Guidance:</b> For DoD clouds, see DoD cloud website for specific DoD requirements that go above and beyond FedRAMP http://iase.disa.mil/cloud_security/Pages/index.aspx.
</ol>
|IA-4|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter IA-4(a):
|Parameter IA-4(d):
|Parameter IA-4(e):
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|IA-4 What is the solution and how is it implemented?|
|---
|Part a
|Part b
|Part c
|Part d
|Part e
# |
IA-4 (4) Control Enhancement (M) (H) | Refer to the specific section and subsections for details. | The organization manages individual identifiers by uniquely identifying each individual as [FedRAMP Assignment: contractors; foreign nationals].
|IA-4 (4)|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter IA-4 (4):
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|IA-4 (4) What is the solution and how is it implemented?|
|---|
||
# |
IA-5 Authenticator Management (L) (M) | Refer to the specific section and subsections for details. | The organization manages information system authenticators by:
<ol type="a">
<li>Verifying, as part of the initial authenticator distribution, the identity of the individual, group, role, or device receiving the authenticator;</li>
<li>Establishing initial authenticator content for authenticators defined by the organization;</li>
<li>Ensuring that authenticators have sufficient strength of mechanism for their intended use;</li>
<li>Establishing and implementing administrative procedures for initial authenticator distribution, for lost/compromised or damaged authenticators, and for revoking authenticators;</li>
<li>Changing default content of authenticators prior to information system installation;</li>
<li>Establishing minimum and maximum lifetime restrictions and reuse conditions for authenticators;</li>
<li>Changing/refreshing authenticators [Assignment: organization-defined time period by authenticator type].</li>
<li>Protecting authenticator content from unauthorized disclosure and modification;</li>
<li>Requiring individuals to take, and having devices implement, specific security safeguards to protect authenticators; and</li>
<li>Changing authenticators for group/role accounts when membership to those accounts changes.</li>
<b>IA-5 Additional FedRAMP Requirements and Guidance:</b><br>
<b>Requirement:</b> Authenticators must be compliant with NIST SP 800-63-3 Digital Identity Guidelines IAL, AAL, FAL level 2. Link https://pages.nist.gov/800-63-3.
</ol>
|IA-5|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter IA-5(g):
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|IA-5 What is the solution and how is it implemented?|
|---|
|Part a
|Part b|
|Part c|
|Part d|
|Part e|
|Part f|
|Part g|
|Part h|
|Part i|
|Part j|
# |
IA-5 (1) Control Enhancement (L) (M) | Refer to the specific section and subsections for details. | The information system, for password-based authentication:
<ol type="a">
<li>Enforces minimum password complexity of [Assignment: organization-defined requirements for case sensitivity, number of characters, mix of upper-case letters, lower-case letters, numbers, and special characters, including minimum requirements for each type];</li>
<li>Enforces at least the following number of changed characters when new passwords are created: [FedRAMP Assignment: at least one (1)];</li>
<li>Stores and transmits only cryptographically-protected passwords;</li>
<li>Enforces password minimum and maximum lifetime restrictions of [Assignment: organization- defined numbers for lifetime minimum, lifetime maximum];</li>
<li>Prohibits password reuse for [FedRAMP Assignment: twenty-four (24)] generations; and</li>
<li>Allows the use of a temporary password for system logons with an immediate change to a permanent password.</li>
<b>IA-5 (1) a and d Additional FedRAMP Requirements and Guidance:</b><br>
<b>Guidance:</b> If password policies are compliant with NIST SP 800-63B Memorized Secret (Section 5.1.1) Guidance, the control may be considered compliant.
</ol>
|IA-5 (1)|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter IA-5(1)(a):
|Parameter IA-5(1)(b):
|Parameter IA-5(1)(d):
|Parameter IA-5(1)(e):
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|IA-5 (1) What is the solution and how is it implemented?|
|---|
|Part a
|Part b|
|Part c|
|Part d|
|Part e|
|Part f|
# |
IA-5 (2) Control Enhancement (M) (H) | Refer to the specific section and subsections for details. | The information system, for PKI-based authentication:
<ol type="a">
<li>Validates certifications by constructing and verifying a certification path to an accepted trust anchor including checking certificate status information;</li>
<li>Enforces authorized access to the corresponding private key;</li>
<li>Maps the authenticated identity to the account of the individual or group; and</li>
<li>Implements a local cache of revocation data to support path discovery and validation in case of inability to access revocation information via the network.</li>
</ol>
|IA-5 (2)|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|IA-5 (2) What is the solution and how is it implemented?|
|---|
|Part a
|Part b|
|Part c|
|Part d|
# |
IA-5 (3) Control Enhancement (M) (H) | Refer to the specific section and subsections for details. | The organization requires that the registration process to receive [FedRAMP Assignment: All hardware/biometric (multifactor authenticators] be conducted [FedRAMP Selection: in person] before [Assignment: organization-defined registration authority] with authorization by [Assignment: organization-defined personnel or roles].
|IA-5 (3)|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter IA-5(3)-1:
|Parameter IA-5(3)-2:
|Parameter IA-5(3)-3:
|Parameter IA-5(3)-4:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|IA-5 (3) What is the solution and how is it implemented?|
|---|
||
# |
IA-5 (4) Control Enhancement (M) | Refer to the specific section and subsections for details. | The organization employs automated tools to determine if password authenticators are sufficiently strong to satisfy [Assignment: organization-defined requirements].
<b>IA-5 (4) Additional FedRAMP Requirements and Guidance:</b><br>
<b>Guidance:</b> If automated mechanisms which enforce password authenticator strength at creation are not used, automated mechanisms must be used to audit strength of created password authenticators.
|IA-5 (4)|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter IA-5(4):
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|IA-5 (4) What is the solution and how is it implemented?|
|---|
||
# |
IA-5 (6) Control Enhancement (M) (H) | Refer to the specific section and subsections for details. | The organization protects authenticators commensurate with the security category of the information to which use of the authenticator permits access.
|IA-5 (6)|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|IA-5 (6) What is the solution and how is it implemented?|
|---|
||
# |
IA-5 (7) Control Enhancement (M) (H) | Refer to the specific section and subsections for details. | The organization ensures that unencrypted static authenticators are not embedded in applications or access scripts or stored on function keys.
|IA-5 (7)|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|IA-5 (7) What is the solution and how is it implemented?|
|---|
||
# |
IA-5 (11) Control Enhancement (L) (M) (H) | Refer to the specific section and subsections for details. | The information system, for hardware token-based authentication, employs mechanisms that satisfy [Assignment: organization-defined token quality requirements].
|IA-5 (11)|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter IA-5(11):
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|IA-5 (11) What is the solution and how is it implemented?|
|---|
||
# |
IA-6 Authenticator Feedback (L) (M) (H) | Refer to the specific section and subsections for details. | The information system obscures feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals.
|IA-6|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|IA-6 What is the solution and how is it implemented?|
|---|
||
# |
IA-7 Cryptographic Module Authentication (L) (M) (H) | Refer to the specific section and subsections for details. | The information system implements mechanisms for authentication to a cryptographic module that meet the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance for such authentication.
|IA-7|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|IA-7 What is the solution and how is it implemented?|
|---|
||
# |
IA-8 Identification and Authentication (Non-Organizational Users) (L) (M) (H) | Refer to the specific section and subsections for details. | The information system uniquely identifies and authenticates non-organizational users (or processes acting on behalf of non-organizational users).
|IA-8|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|IA-8 What is the solution and how is it implemented?|
|---|
||
# |
IA-8 (1) Control Enhancement (L) (M) (H) | Refer to the specific section and subsections for details. | The information system accepts and electronically verifies Personal Identity Verification (PIV) credentials from other federal agencies.
|IA-8 (1)|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|IA-8 (1) What is the solution and how is it implemented?|
|---|
||
# |
IA-8 (2) Control Enhancement (L) (M) (H) | Refer to the specific section and subsections for details. | The information system accepts only FICAM-approved third-party credentials.
|IA-8 (2)|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|IA-8 (2) What is the solution and how is it implemented?|
|---|
||
# |
IA-8 (3) Control Enhancement (L) (M) (H) | Refer to the specific section and subsections for details. | The organization employs only FICAM-approved information system components in [Assignment: organization-defined information systems] to accept third-party credentials.
|IA-8 (3)|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter IA-8(3):
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|IA-8 (3) What is the solution and how is it implemented?|
|---|
||
# |
IA-8 (4) Control Enhancement (L) (M) (H) | Refer to the specific section and subsections for details. | The information system conforms to FICAM-issued profiles.
|IA-8 (4)|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|IA-8 (4) What is the solution and how is it implemented?|
|---|
|| |
Access Control (AC) | Refer to the specific section and subsections for details. | # |
AC-1 Access Control Policy and Procedures Requirements (L) (M) | Refer to the specific section and subsections for details. | The organization:
<ol type="a">
<li>Develops, documents and disseminates to [Assignment: organization-defined personnel or roles]:</li>
<ol type="1">
<li>An access control policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and</li>
<li>Procedures to facilitate the implementation of the access control policy and associated access controls; and</li>
</ol>
<li>Reviews and updates the current:</li>
<ol type="1">
<li>Access control policy [FedRAMP Assignment: at least every 3 years]; and</li>
<li>Access control procedures [FedRAMP Assignment: at least annually].</li>
</ol>
</ol>
|AC-1|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter AC-1(a):
|Parameter AC-1(b)(1):
|Parameter AC-1(b)(2):
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)
|AC-1 What is the solution and how is it implemented?|
|---|
|Part a|
|Part b1|
|Part b2|
# |
AC-2 Account Management (L) (M) | Refer to the specific section and subsections for details. | The organization:
<ol type="a">
<li>Identifies and selects the following types of information system accounts to support organizational missions/business functions: [Assignment: organization-defined information system account types];</li>
<li>Assigns account managers for information system accounts;</li>
<li>Establishes conditions for group and role membership;</li>
<li>Specifies authorized users of the information system, group and role membership, and access authorizations (i.e., privileges) and other attributes (as required) for each account;</li>
<li>Requires approvals by [Assignment: organization-defined personnel or roles] for requests to create information system accounts;</li>
<li>Creates, enables, modifies, disables, and removes information system accounts in accordance with [Assignment: organization-defined procedures or conditions];</li>
<li>Monitors the use of information system accounts;</li>
<li>Notifies account managers:</li>
<ol type="1">
<li>When accounts are no longer required;</li>
<li>When users are terminated or transferred; and</li>
<li>When individual information system usage or need-to-know changes;</li>
</ol>
<li>Authorizes access to the information system based on:</li>
<ol type="1">
<li>A valid access authorization;</li>
<li>Intended system usage; and</li>
<li>Other attributes as required by the organization or associated missions/business functions;</li>
</ol>
<li>Reviews accounts for compliance with account management requirements [FedRAMP Assignment: at least annually]; and</li>
<li>Establishes a process for reissuing shared/group account credentials (if deployed) when individuals are removed from the group.</li>
</ol>
|AC-2|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter AC-2(a):
|Parameter AC-2(e):
|Parameter AC-2(f):
|Parameter AC-2(j):
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|AC-2 What is the solution and how is it implemented?|
|---|
|Part a
|Part b
|Part c
|Part d
|Part e
|Part f
|Part g
|Part h
|Part i
|Part j
|Part k
# |
AC-2 (1) Control Enhancement (M) (H) | Refer to the specific section and subsections for details. | The organization employs automated mechanisms to support the management of information system accounts.
|AC-2 (1)|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|AC-2 (1) What is the solution and how is it implemented?|
|---|
||
# |
AC-2 (2) Control Enhancement (M) | Refer to the specific section and subsections for details. | The information system automatically [Selection: removes; disables] temporary and emergency accounts after [FedRAMP Assignment: no more than 30 days for temporary and emergency account types].
|AC-2 (2)|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter AC-2(2)1:
|Parameter AC-2(2)2:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|AC-2 (2) What is the solution and how is it implemented?|
|---|
||
# |
AC-2 (3) Control Enhancement (M) | Refer to the specific section and subsections for details. | The information system automatically disables inactive accounts after [FedRAMP Assignment: ninety (90) days for user accounts].<br>
<b>AC-2 (3) Additional FedRAMP Requirements and Guidance:</b><br>
<b>Requirement:</b> The service provider defines the time period for non-user accounts (e.g., accounts associated with devices). The time periods are approved and accepted by the Joint Authorization Board (JAB)/AO. Where user management is a function of the service, reports of activity of consumer users shall be made available.
|AC-2 (3)|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter AC-2(3):
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|AC-2 (3) What is the solution and how is it implemented?|
|---|
||
# |
AC-2 (4) Control Enhancement (M) | Refer to the specific section and subsections for details. | The information system automatically audits account creation, modification, enabling, disabling, and removal actions, and notifies [Assignment: organization-defined personnel or roles].
|AC-2 (4)|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter AC-2(4):
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|AC-2 (4) What is the solution and how is it implemented?|
|---|
||
# |
AC-2 (5) Control Enhancement (M) | Refer to the specific section and subsections for details. | The organization requires that users log out when [Assignment: organization-defined time-period of expected inactivity or description of when to log out].<br>
<b>AC-2 (5) Additional FedRAMP Requirements and Guidance:</b><br>
<b>Guidance</b>: Should use a shorter timeframe than AC-12
|AC-2 (5)|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter AC-2(5):
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|AC-2 (5) What is the solution and how is it implemented?|
|---|
||
# |
AC-2 (7) Control Enhancement (M) | Refer to the specific section and subsections for details. | The organization:
<ol type="a">
<li>Establishes and administers privileged user accounts in accordance with a role-based access scheme that organizes allowed information system access and privileges into roles;</li>
<li>Monitors privileged role assignments; and</li>
<li>Takes [Assignment: organization-defined actions] when privileged role assignments are no longer appropriate.</li>
</ol>
|AC-2 (7)|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter AC-2(7):
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|AC-2 (7) What is the solution and how is it implemented?|
|---|
|Part a
|Part b
|Part c
# |
AC-2 (9) Control Enhancement (M) | Refer to the specific section and subsections for details. | The organization only permits the use of shared/group accounts that meet [Assignment: organization-defined conditions for establishing shared/group accounts].<br>
<b>AC-2 (9) Additional FedRAMP Requirements and Guidance:</b> Required if shared/group accounts are deployed.
|AC-2 (9)|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter AC-2(9):
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|AC-2 (9) What is the solution and how is it implemented?|
|---|
||
# |
AC-2 (10) Control Enhancement (M) (H) | Refer to the specific section and subsections for details. | The information system terminates shared/group account credentials when members leave the group.<br>
<b>AC-2 (10) Additional FedRAMP Requirements and Guidance:</b><br>
Required if shared/group accounts are deployed.
|AC-2 (10)|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter AC-2(10):
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|AC-2 (10) What is the solution and how is it implemented?|
|---|
||
# |
AC-2 (12) Control Enhancement (M) | Refer to the specific section and subsections for details. | The organization:
<ol type="a">
<li>Monitors information system accounts for [Assignment: organization-defined atypical use]; and</li>
<li>Reports atypical usage of information system accounts to [Assignment: organization-defined personnel or roles].</li>
<b>AC-2 (12) (a) and AC-2 (12) (b) Additional FedRAMP Requirements and Guidance:</b> Required for privileged accounts.
</ol>
|AC-2 (12)|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter AC-2(12)(a):
|Parameter AC-2(12)(b):
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|AC-2 (12) What is the solution and how is it implemented?|
|---|
|Part a
|Part b |
AC-3 Access Enforcement (L) (M) (H) | Refer to the specific section and subsections for details. | The information system enforces approved authorizations for logical access to information and system resources in accordance with applicable access control policies.
|AC-3|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|AC-3 What is the solution and how is it implemented?|
|---|
|Part a |
AC-4 Information Flow Enforcement (M) (H) | Refer to the specific section and subsections for details. | The information system enforces approved authorizations for controlling the flow of information within the system and between interconnected systems based on [Assignment: organization-defined information flow control policies].
|AC-4|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter AC-4
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|AC-4 What is the solution and how is it implemented?|
|---|
||
# |
AC-4 (21) Control Enhancement (M) (H) | Refer to the specific section and subsections for details. | The information system separates information flows logically or physically using [Assignment: organization-defined mechanisms and/or techniques] to accomplish [Assignment: organization-defined required separations by types of information].
|AC-4 (21)|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter AC-4(21)-1
|Parameter AC-4(21)-2
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|AC-4 What is the solution and how is it implemented?|
|---|
|| |
AC-5 Separation of Duties (M) (H) | Refer to the specific section and subsections for details. | The organization:
<ol type="a">
<li>Separates [Assignment: organization-defined duties of individuals];</li>
<li>Documents separation of duties of individuals; and </li>
<li>Defines information system access authorizations to support separation of duties.</li>
<b>AC-5 Additional FedRAMP Requirements and Guidance:</b><br>
<b>Guidance:</b> CSPs have the option to provide a separation of duties matrix as an attachment to the SSP. Directions for attaching the Separation of Duties Matrix document may be found in Section Error: Reference source not found Error: Reference source not found.
</ol>
|AC-5|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter AC-5(a)
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|AC-5 What is the solution and how is it implemented?|
|---|
|Part a
|Part b
|Part c |
AC-6 Least Privilege (M) (H) | Refer to the specific section and subsections for details. | The organization employs the principle of least privilege, allowing only authorized accesses for users (or processes acting on behalf of users) which are necessary to accomplish assigned tasks in accordance with organizational missions and business functions.
|AC-6|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|AC-6 What is the solution and how is it implemented?|
|---|
||
# |
AC-6 (1) Control Enhancement (M) | Refer to the specific section and subsections for details. | The organization explicitly authorizes access to [Assignment: organization-defined security functions (deployed in hardware, software, and firmware) and security-relevant information].
|AC-6 (1)|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter AC-6(1)
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|AC-6 (1) What is the solution and how is it implemented?|
|---|
||
# |
AC-6 (2) Control Enhancement (M) (H) | Refer to the specific section and subsections for details. | The organization requires that users of information system accounts, or roles, with access to [FedRAMP Assignment: all security functions], use non-privileged accounts or roles, when accessing non-security functions.<br>
<b>AC-6 (2) Additional FedRAMP Requirements and Guidance:</b><br>
Examples of security functions include but are not limited to: establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters, system programming, system and security administration, other privileged functions.
|AC-6 (2)|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter AC-6(2)
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|AC-6 (2) What is the solution and how is it implemented?|
|---|
||
# |
AC 6 (5) Control Enhancement (M) (H) | Refer to the specific section and subsections for details. | The organization restricts privileged accounts on the information system to [Assignment: organization-defined personnel or roles].
|AC-6 (5)|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter AC-6(5)
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|AC-6 (5) What is the solution and how is it implemented?|
|---|
||
# |
AC-6 (9) Control Enhancement (M) (H) | Refer to the specific section and subsections for details. | The information system audits the execution of privileged functions.
|AC-6 (9)|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|AC-6 (9) What is the solution and how is it implemented?|
|---|
||
# |
AC-6 (10) Control Enhancement (M) (H) | Refer to the specific section and subsections for details. | The information system prevents non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures.
|AC-6 (10)|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|AC-6 (10) What is the solution and how is it implemented?|
|---|
|| |
AC-7 Unsuccessful Login Attempts (L) (M) | Refer to the specific section and subsections for details. | The organization:
<ol type="a">
<li>Enforces a limit of [FedRAMP Assignment: not more than three (3)] consecutive invalid logon attempts by a user during a [FedRAMP Assignment: fifteen (15) minutes]; and</li>
<li>Automatically [Selection: locks the account/node for a [FedRAMP Assignment: thirty (30) minutes]; delays next logon prompt according to [Assignment: organization-defined delay algorithm]] when the maximum number of unsuccessful attempts is exceeded.</li>
</ol>
|AC-7|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter AC-7(a)-1:
|Parameter AC-7(a)-2:
|Parameter AC-7(b)-1:
|Parameter AC-7(b)-2:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|AC-7 What is the solution and how is it implemented?|
|---|
|Part a
|Part b |
AC-8 System Use Notification (L) (M) (H) | Refer to the specific section and subsections for details. | The information system:
<ol type="a">
<li>Displays to users [Assignment: organization-defined system use notification message or banner (FedRAMP Assignment: see additional Requirements and Guidance)] before granting access to the system that provides privacy and security notices consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance and states that:</li>
<ol type="1">
<li>Users are accessing a U.S. Government information system;</li>
<li>Information system usage may be monitored, recorded, and subject to audit;</li>
<li>Unauthorized use of the information system is prohibited and subject to criminal and civil penalties; and</li>
<li>Use of the information system indicates consent to monitoring and recording;</li>
</ol>
<li>Retains the notification message or banner on the screen until users acknowledge the usage conditions and take explicit actions to log on to or further access the information system; and</li>
<li>For publicly accessible systems:</li>
<ol type="1">
<li>Displays system use information [Assignment: organization-defined conditions (FedRAMP Assignment: see additional Requirements and Guidance)], before granting further access;</li>
<li>Displays references, if any, to monitoring, recording, or auditing that are consistent with privacy accommodations for such systems that generally prohibit those activities; and</li>
<li>Includes a description of the authorized uses of the system.</li>
</ol>
</ol>
<b>AC-8 Additional FedRAMP Requirements and Guidance:</b><br>
<b>Requirement:</b> The service provider shall determine elements of the cloud environment that require the System Use Notification control. The elements of the cloud environment that require System Use Notification are approved and accepted by the JAB/AO.<br>
<b>Requirement:</b> The service provider shall determine how System Use Notification is going to be verified and provide appropriate periodicity of the check. The System Use Notification verification and periodicity are approved and accepted by the JAB/AO.<br>
<b>Guidance:</b> If performed as part of a Configuration Baseline check, then the % of items requiring setting that are checked and that pass (or fail) check can be provided.<br>
<b>Requirement:</b> If not performed as part of a Configuration Baseline check, then there must be documented agreement on how to provide results of verification and the necessary periodicity of the verification by the service provider. The documented agreement on how to provide verification of the results are approved and accepted by the JAB/AO.
|AC-8|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter AC-8(a)-1:
|Parameter AC-8(c)-1:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|AC-8 What is the solution and how is it implemented?|
|---|
|Part a
|Part b
|Part c
<b>Additional FedRAMP Requirements and Guidance</b><br>
<b>Requirement 1:</b> The service provider shall determine elements of the cloud environment that require the System Use Notification control. The elements of the cloud environment that require System Use Notification are approved and accepted by the JAB/AO.<br>
<b>Requirement 2:</b> The service provider shall determine how System Use Notification is going to be verified and provide appropriate periodicity of the check. The System Use Notification verification and periodicity are approved and accepted by the JAB/AO. If performed as part of a Configuration Baseline check, then the % of items requiring setting that are checked and that pass (or fail) check can be provided.<br>
<b>Requirement 3:</b> If not performed as part of a Configuration Baseline check, then there must be documented agreement on how to provide results of verification and the necessary periodicity of the verification by the service provider. The documented agreement on how to provide verification of the results are approved and accepted by the JAB/AO.
|AC-8 Req.|Control Summary Information|
|---|---|
|Responsible Role:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|AC-8 What is the solution and how is it implemented?|
|---|
|Req 1
|Req 2
|Req 3 |
AC-10 Concurrent Session Control (M) (H) | Refer to the specific section and subsections for details. | The information system limits the number of concurrent sessions for each [Assignment: organization-defined account and/or account type] to [FedRAMP Assignment: three (3) sessions for privileged access and two (2) sessions for non-privileged access].
|AC-10|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter AC-10-1:
|Parameter AC-10-2:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|AC-10 What is the solution and how is it implemented?|
|---|
|| |
AC-11 Session Lock (M) (H) | Refer to the specific section and subsections for details. | The information system:
<ol type="a">
<li>Prevents further access to the system by initiating a session lock after [FedRAMP Assignment: fifteen (15) minutes] of inactivity or upon receiving a request from a user; and</li>
<li>Retains the session lock until the user reestablishes access using established identification and authentication procedures.</li>
</ol>
|AC-11|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter AC-11(a)
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|AC-11 What is the solution and how is it implemented?|
|---|
|Part a
|Part b
# |
AC-11 (1) Control Enhancement (M) (H) | Refer to the specific section and subsections for details. | The information system conceals, via the session lock, information previously visible on the display with a publicly viewable image.
|AC-11 (1)|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter AC-11(a)
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|AC-11 (1) What is the solution and how is it implemented?|
|---|
|| |
AC-12 Session Termination (M) (H) | Refer to the specific section and subsections for details. | The information system automatically terminates a user session after [Assignment: organization-defined conditions or trigger events requiring session disconnect].
|AC-12|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter AC-12:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|AC-12 What is the solution and how is it implemented?|
|---|
|| |
AC-14 Permitted Actions without Identification or Authentication (L) (M) (H) | Refer to the specific section and subsections for details. | The organization:
<ol type="a">
<li>Identifies [Assignment: organization-defined user actions] that can be performed on the information system without identification or authentication consistent with organizational missions/business functions; and</li>
<li>Documents and provides supporting rationale in the security plan for the information system, user actions not requiring identification or authentication.</li>
</ol>
|AC-14|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter AC-12:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|AC-14 What is the solution and how is it implemented?|
|---|
|Part a
|Part b |
AC-17 Remote Access (L) (M) (H) | Refer to the specific section and subsections for details. | The organization:
<ol type="a">
<li>Establishes and documents usage restrictions, configuration/connection requirements, and implementation guidance for each type of remote access allowed; and</li>
<li>Authorizes remote access to the information system prior to allowing such connections.</li>
</ol>
|AC-17|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter AC-17:
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|AC-17 What is the solution and how is it implemented?|
|---|
|Part a
|Part b
# |
AC-17 (1) Control Enhancement (M) (H) | Refer to the specific section and subsections for details. | The information system monitors and controls remote access methods.
|AC-17 (1)|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter AC-17 (1):
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|AC-17 (1) What is the solution and how is it implemented?|
|---|
||
# |
AC-17 (2) Control Enhancement (M) (H) | Refer to the specific section and subsections for details. | The information system implements cryptographic mechanisms to protect the confidentiality and integrity of remote access sessions.
|AC-17 (2)|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter AC-17 (2):
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|AC-17 (2) What is the solution and how is it implemented?|
|---|
||
# |
AC-17 (3) Control Enhancement (M) (H) | Refer to the specific section and subsections for details. | The information system routes all remote accesses through [Assignment: organization-defined number] managed network access control points.
|AC-17 (3)|Control Summary Information|
|---|---|
|Responsible Role:
|Parameter AC-17(3):
|Implementation Status (check all that apply):|☐ Implemented<br/>☐ Partially implemented<br/>☐ Planned<br/>☐ Alternative implementation<br/>☐ Not applicable
|Control Origination (check all that apply):|☐ Service Provider Corporate<br/>☐ Service Provider System Specific<br/>☐ Service Provider Hybrid (Corporate and System Specific)<br/>☐ Configured by Customer (Customer System Specific)<br/>☐ Provided by Customer (Customer System Specific)<br/>☐ Shared (Service Provider and Customer Responsibility)<br/>☐ Inherited from pre-existing FedRAMP Authorization for _insert text here_.
|AC-17 (3) What is the solution and how is it implemented?|
|---|
||
# |
Subsets and Splits