diff --git a/src/content/rev5/baselines/xml/FedRAMP_rev5_HIGH-baseline_profile.xml b/src/content/rev5/baselines/xml/FedRAMP_rev5_HIGH-baseline_profile.xml index 6df08ba80..f4783909d 100644 --- a/src/content/rev5/baselines/xml/FedRAMP_rev5_HIGH-baseline_profile.xml +++ b/src/content/rev5/baselines/xml/FedRAMP_rev5_HIGH-baseline_profile.xml @@ -1787,7 +1787,7 @@ -

personnel screening criteria – as required by specific information

+

personnel screening criteria - as required by specific information

 @@ -2402,6 +2402,475 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

This response must address all control sub-statement requirements.

 + + + + + + + +

This response must address all control sub-statement requirements.

 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2420,6 +2889,54 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2431,6 +2948,54 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2442,6 +3007,17 @@ + + + + + + + + + + + @@ -2457,6 +3033,138 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2468,6 +3176,14 @@ + + + + + + + + @@ -2479,6 +3195,64 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2490,6 +3264,88 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2501,6 +3357,22 @@ + + + + + + + + + + + + + + + + @@ -2524,6 +3396,45 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2538,8 +3449,323 @@ + + + + + + + + + + + + + + + + - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

This response must address all control sub-statement requirements.

 + + + + + + + +

This response must address all control sub-statement requirements.

 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

This response must address all control sub-statement requirements.

 + + + + + + + +

This response must address all control sub-statement requirements.

 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + AU-2 Additional FedRAMP Requirements and Guidance @@ -2553,6 +3779,80 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2564,6 +3864,77 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2575,6 +3946,85 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2586,6 +4036,108 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2597,6 +4149,14 @@ + + + + + + + + @@ -2616,6 +4176,83 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

This response must address all control sub-statement requirements.

 + + + + + + + +

This response must address all control sub-statement requirements.

 + + @@ -2627,6 +4264,61 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2638,6 +4330,14 @@ + + + + + + + + @@ -2649,6 +4349,59 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2664,6 +4417,22 @@ + + + + + + + + + + + + + + + + @@ -2675,6 +4444,50 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2694,29 +4507,305 @@ - - - - - CA-8 Additional FedRAMP Requirements and Guidance - - -

Reference the FedRAMP Penetration Test Guidance.

- - + + + + - - - - - CM-2 Additional FedRAMP Requirements and Guidance - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + CA-8 Additional FedRAMP Requirements and Guidance + + +

Reference the FedRAMP Penetration Test Guidance.

+ + + + + + + + + + + + + + + + + + + + + + + + + + CM-2 Additional FedRAMP Requirements and Guidance +

See the FedRAMP Documents page> Penetration Test Guidance

https://www.FedRAMP.gov/documents/

 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

This response must address all control sub-statement requirements.

 + + + + + + + +

This response must address all control sub-statement requirements.

 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2728,6 +4817,68 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2743,6 +4894,262 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2758,11 +5165,70 @@ -

Compliance checks are used to evaluate configuration settings and provide general insight into the overall effectiveness of configuration management activities. CSPs and 3PAOs typically combine compliance check findings into a single CM-6 finding, which is acceptable. However, for initial assessments, annual assessments, and significant change requests, FedRAMP requires a clear understanding, on a per-control basis, where risks exist. Therefore, 3PAOs must also analyze compliance check findings as part of the controls assessment. Where a direct mapping exists, the 3PAO must document additional findings per control in the corresponding SAR Risk Exposure Table (RET), which are then documented in the CSP’s Plan of Action and Milestones (POA&M). This will likely result in the details of individual control findings overlapping with those in the combined CM-6 finding, which is acceptable.

+

Compliance checks are used to evaluate configuration settings and provide general insight into the overall effectiveness of configuration management activities. CSPs and 3PAOs typically combine compliance check findings into a single CM-6 finding, which is acceptable. However, for initial assessments, annual assessments, and significant change requests, FedRAMP requires a clear understanding, on a per-control basis, where risks exist. Therefore, 3PAOs must also analyze compliance check findings as part of the controls assessment. Where a direct mapping exists, the 3PAO must document additional findings per control in the corresponding SAR Risk Exposure Table (RET), which are then documented in the CSP's Plan of Action and Milestones (POA&M). This will likely result in the details of individual control findings overlapping with those in the combined CM-6 finding, which is acceptable.

During monthly continuous monitoring, new findings from CSP compliance checks may be combined into a single CM-6 POA&M item. CSPs are not required to map the findings to specific controls because controls are only assessed during initial assessments, annual assessments, and significant change requests.

 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2774,6 +5240,45 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2785,6 +5290,44 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2796,6 +5339,91 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2804,6 +5432,55 @@

FedRAMP does not provide a template for the Configuration Management Plan. However, NIST SP 800-128, Guide for Security-Focused Configuration Management of Information Systems, provides guidelines for the implementation of CM controls as well as a sample CMP outline in Appendix D of the Guide

 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2815,6 +5492,40 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2826,7 +5537,14 @@ - + + + + + + + + @@ -2834,6 +5552,103 @@

If digital signatures/certificates are unavailable, alternative cryptographic integrity checks (hashes, self-signed certs, etc.) can be utilized.

 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

This response must address all control sub-statement requirements.

 + + + + + + + +

This response must address all control sub-statement requirements.

 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2849,6 +5664,163 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2860,6 +5832,48 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2875,6 +5889,140 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2886,6 +6034,39 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2897,6 +6078,50 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2908,6 +6133,81 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2931,6 +6231,90 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2942,6 +6326,102 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

This response must address all control sub-statement requirements.

 + + + + + + + +

This response must address all control sub-statement requirements.

 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2961,10 +6441,28 @@ -

"Phishing-resistant" authentication refers to authentication processes designed to detect and prevent disclosure of authentication secrets and outputs to a website or application masquerading as a legitimate system.

+

"Phishing-resistant" authentication refers to authentication processes designed to detect and prevent disclosure of authentication secrets and outputs to a website or application masquerading as a legitimate system.

 + + + + + + + + + + + + + + + + + + @@ -2984,6 +6482,16 @@ + + + + + + + + + + @@ -3003,6 +6511,28 @@ + + + + + + + + + + + + + + + + + + + + + + @@ -3018,6 +6548,25 @@ + + + + + + + + + + + + + + + + + + + @@ -3029,6 +6578,87 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -3044,6 +6674,86 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -3055,7 +6765,7 @@ -

For cases where technology doesn’t allow multi-factor authentication, these rules should be enforced: must have a minimum length of 14 characters and must support all printable ASCII characters.

+

For cases where technology doesn't allow multi-factor authentication, these rules should be enforced: must have a minimum length of 14 characters and must support all printable ASCII characters.

For emergency use accounts, these rules should be enforced: must have a minimum length of 14 characters, must support all printable ASCII characters, and passwords must be changed if used.

 @@ -3064,6 +6774,98 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -3075,6 +6877,13 @@ + + + + + + + @@ -3086,6 +6895,14 @@ + + + + + + + + @@ -3097,6 +6914,14 @@ + + + + + + + + @@ -3115,6 +6940,15 @@ + + + + + + + + + @@ -3126,6 +6960,31 @@ + + + + + + + + + + + + + + + + + + + + + + + + + @@ -3137,6 +6996,188 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

This response must address all control sub-statement requirements.

 + + + + + + + +

This response must address all control sub-statement requirements.

 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -3148,6 +7189,27 @@ + + + + + + + + + + + + + + + + + + + + + @@ -3155,7 +7217,7 @@ IR-4 Additional FedRAMP Requirements and Guidance -

The FISMA definition of "incident" shall be used: "An occurrence that actually or imminently jeopardizes, without lawful authority, the confidentiality, integrity, or availability of information or an information system; or constitutes a violation or imminent threat of violation of law, security policies, security procedures, or acceptable use policies."

+

The FISMA definition of "incident" shall be used: "An occurrence that actually or imminently jeopardizes, without lawful authority, the confidentiality, integrity, or availability of information or an information system; or constitutes a violation or imminent threat of violation of law, security policies, security procedures, or acceptable use policies."

 @@ -3163,6 +7225,139 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -3174,6 +7369,69 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -3189,93 +7447,1714 @@ - - - - - MP-3 Additional FedRAMP Requirements and Guidance - - -

Second parameter not-applicable

- - + + + - - - - - MP-4 Additional FedRAMP Requirements and Guidance - - -

The service provider defines controlled areas within facilities where the information and information system reside.

- - + + + - - - - - MP-5 Additional FedRAMP Requirements and Guidance - - -

The service provider defines security measures to protect digital and non-digital media in transport. The security measures are approved and accepted by the JAB/AO.

- - + + + - - - - - MP-6 (1) Additional FedRAMP Requirements and Guidance - - -

Must comply with NIST SP 800-88

- - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - - - MP-6 (2) Additional FedRAMP Requirements and Guidance - - -

Equipment and procedures may be tested or validated for effectiveness

- - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - - - MP-6 (3) Additional FedRAMP Requirements and Guidance - - -

Must comply with NIST SP 800-88

- - + + + + + + + - - - - PE-14 Additional FedRAMP Requirements and Guidance - - -

The service provider measures temperature at server inlets and humidity levels by dew point.

- - + + + + + + + - - - - PL-8 Additional FedRAMP Requirements and Guidance - - -

Significant change is defined in NIST Special Publication 800-37 Revision 2, Appendix F.

- - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

This response must address all control sub-statement requirements.

 + + + + + + + +

This response must address all control sub-statement requirements.

 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

This response must address all control sub-statement requirements.

 + + + + + + + +

This response must address all control sub-statement requirements.

 + + + + + + + + + + + + + + + + + + + + + + + + MP-3 Additional FedRAMP Requirements and Guidance + + +

Second parameter not-applicable

+ + + + + + + + + + + + + + + + + + + + + + MP-4 Additional FedRAMP Requirements and Guidance + + +

The service provider defines controlled areas within facilities where the information and information system reside.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + MP-5 Additional FedRAMP Requirements and Guidance + + +

The service provider defines security measures to protect digital and non-digital media in transport. The security measures are approved and accepted by the JAB/AO.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + MP-6 (1) Additional FedRAMP Requirements and Guidance + + +

Must comply with NIST SP 800-88

+ + + + + + + + + + + + + + + MP-6 (2) Additional FedRAMP Requirements and Guidance + + +

Equipment and procedures may be tested or validated for effectiveness

+ + + + + + + + + + + + + + + MP-6 (3) Additional FedRAMP Requirements and Guidance + + +

Must comply with NIST SP 800-88

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

This response must address all control sub-statement requirements.

 + + + + + + + +

This response must address all control sub-statement requirements.

 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + PE-14 Additional FedRAMP Requirements and Guidance + + +

The service provider measures temperature at server inlets and humidity levels by dew point.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

This response must address all control sub-statement requirements.

 + + + + + + + +

This response must address all control sub-statement requirements.

 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + PL-8 Additional FedRAMP Requirements and Guidance + + +

Significant change is defined in NIST Special Publication 800-37 Revision 2, Appendix F.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -3288,6 +9167,392 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

This response must address all control sub-statement requirements.

 + + + + + + + +

This response must address all control sub-statement requirements.

 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

This response must address all control sub-statement requirements.

 + + + + + + + +

This response must address all control sub-statement requirements.

 + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -3303,6 +9568,81 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -3328,10 +9668,137 @@

Informational findings from a scanner are detailed as a returned result that holds no vulnerability risk or severity and for FedRAMP does not require an entry onto the POA&M or entry onto the RET during any assessment phase.

Warning findings, on the other hand, are given a risk rating (low, moderate, high or critical) by the scanning solution and should be treated like any other finding with a risk or severity rating for tracking purposes onto either the POA&M or RET depending on when the findings originated (during assessments or during monthly continuous monitoring). If a warning is received during scanning, but further validation turns up no actual issue then this item should be categorized as a false positive. If this situation presents itself during an assessment phase (initial assessment, annual assessment or any SCR), follow guidance on how to report false positives in the Security Assessment Report (SAR). If this situation happens during monthly continuous monitoring, a deviation request will need to be submitted per the FedRAMP Vulnerability Deviation Request Form.

-

Warnings are commonly associated with scanning solutions that also perform compliance scans, and if the scanner reports a “warning” as part of the compliance scanning of a CSO, follow guidance surrounding the tracking of compliance findings during either the assessment phases (initial assessment, annual assessment or any SCR) or monthly continuous monitoring as it applies. Guidance on compliance scan findings can be found by searching on “Tracking of Compliance Scans” in FAQs.

+

Warnings are commonly associated with scanning solutions that also perform compliance scans, and if the scanner reports a "warning" as part of the compliance scanning of a CSO, follow guidance surrounding the tracking of compliance findings during either the assessment phases (initial assessment, annual assessment or any SCR) or monthly continuous monitoring as it applies. Guidance on compliance scan findings can be found by searching on "Tracking of Compliance Scans" in FAQs.

 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -3343,6 +9810,474 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

This response must address all control sub-statement requirements.

 + + + + + + + +

This response must address all control sub-statement requirements.

 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -3359,6 +10294,93 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -3370,6 +10392,47 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -3382,6 +10445,523 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

This response must address all control sub-statement requirements.

 + + + + + + + +

This response must address all control sub-statement requirements.

 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -3393,6 +10973,212 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -3404,6 +11190,46 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -3412,7 +11238,7 @@

For each instance of data in transit, confidentiality AND integrity should be through cryptography as specified in SC-8 (1), physical means as specified in SC-8 (5), or in combination.

-

+

For clarity, this control applies to all data in transit. Examples include the following data flows:

  • Crossing the system boundary
    • @@ -3421,9 +11247,9 @@
  • Replication between availability zones
  • Transmission of backups to storage
  • From a load balancer to a compute instance
    • -
  • Flows from management tools required for their work – e.g. log collection, scanning, etc.
    • +
  • Flows from management tools required for their work - e.g. log collection, scanning, etc.
-

+

The following applies only when choosing SC-8 (5) in lieu of SC-8 (1).

FedRAMP-Defined Assignment / Selection Parameters

SC-8 (5)-1 [a hardened or alarmed carrier Protective Distribution System (PDS) when outside of Controlled Access Area (CAA)]

@@ -3432,21 +11258,33 @@

SC-8 (5) applies when physical protection has been selected as the method to protect confidentiality and integrity. For physical protection, data in transit must be in either a Controlled Access Area (CAA), or a Hardened or alarmed PDS.

-

+

Hardened or alarmed PDS: Shall be as defined in SECTION X - CATEGORY 2 PDS INSTALLATION GUIDANCE of CNSSI No.7003, titled PROTECTED DISTRIBUTION SYSTEMS (PDS). Per the CNSSI No. 7003 Section VIII, PDS must originate and terminate in a Controlled Access Area (CAA).

-

-

Controlled Access Area (CAA): Data will be considered physically protected, and in a CAA if it meets Section 2.3 of the DHS’s Recommended Practice: Improving Industrial Control System Cybersecurity with Defense-in-Depth Strategies. CSPs can meet Section 2.3 of the DHS’ recommended practice by satisfactory implementation of the following controls PE-2 (1), PE-2 (2), PE-2 (3), PE-3 (2), PE-3 (3), PE-6 (2), and PE-6 (3).

-

+

+

Controlled Access Area (CAA): Data will be considered physically protected, and in a CAA if it meets Section 2.3 of the DHS's Recommended Practice: Improving Industrial Control System Cybersecurity with Defense-in-Depth Strategies. CSPs can meet Section 2.3 of the DHS' recommended practice by satisfactory implementation of the following controls PE-2 (1), PE-2 (2), PE-2 (3), PE-3 (2), PE-3 (3), PE-6 (2), and PE-6 (3).

+

Note: When selecting SC-8 (5), the above SC-8(5), and the above referenced PE controls must be added to the SSP.

-

+

CNSSI No.7003 can be accessed here:

https://www.dcsa.mil/Portals/91/documents/ctp/nao/CNSSI_7003_PDS_September_2015.pdf

-

+

DHS Recommended Practice: Improving Industrial Control System Cybersecurity with Defense-in-Depth Strategies can be accessed here:

https://us-cert.cisa.gov/sites/default/files/FactSheets/NCCIC%20ICS_FactSheet_Defense_in_Depth_Strategies_S508C.pdf

 + + + + + + + + + + + + @@ -3458,7 +11296,7 @@ -

See M-22-09, including "Agencies encrypt all DNS requests and HTTP traffic within their environment"

+

See M-22-09, including "Agencies encrypt all DNS requests and HTTP traffic within their environment"

SC-8 (1) applies when encryption has been selected as the method to protect confidentiality and integrity. Otherwise refer to SC-8 (5). SC-8 (1) is strongly encouraged.

 @@ -3471,6 +11309,15 @@ + + + + + + + + + @@ -3490,6 +11337,18 @@ + + + + + + + + + + + + @@ -3505,7 +11364,7 @@
  • Generation of one time passwords (OTPs) for MFA
  • Protocols such as TLS, SSH, and HTTPS
    • -

    +

    The requirement for FIPS 140 validation, as well as timelines for acceptance of FIPS 140-2, and 140-3 can be found at the NIST Cryptographic Module Validation Program (CMVP).

    https://csrc.nist.gov/projects/cryptographic-module-validation-program

    @@ -3535,6 +11394,26 @@     + + + + + + + + + + + + + + + + + + + +     @@ -3546,6 +11425,23 @@ + + + + + + + + + + + + + + + + + @@ -3573,6 +11469,30 @@ + + + + + + + + + + + + + + + + + + + + + + + + @@ -3604,6 +11524,18 @@ + + + + + + + + + + + + @@ -3623,6 +11555,18 @@ + + + + + + + + + + + + @@ -3638,6 +11582,15 @@ + + + + + + + + + @@ -3657,6 +11610,233 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

    This response must address all control sub-statement requirements.

     +     +     + + + + + +

    This response must address all control sub-statement requirements.

     +     +     +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -3668,6 +11848,243 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -3679,6 +12096,15 @@ + + + + + + + + + @@ -3690,6 +12116,17 @@ + + + + + + + + + + + @@ -3699,6 +12136,164 @@

    Service Providers must address the CISA Emergency and Binding Operational Directives applicable to their cloud service offering per FedRAMP guidance. This includes listing the applicable directives and stating compliance status.

     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -3715,6 +12310,22 @@ + + + + + + + + + + + + + + + + @@ -3726,6 +12337,190 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

    This response must address all control sub-statement requirements.

     +     +     + + + + + +

    This response must address all control sub-statement requirements.

     +     +     +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -3737,6 +12532,46 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -3748,6 +12583,14 @@ + + + + + + + + @@ -3759,6 +12602,14 @@ + + + + + + + + @@ -3770,6 +12621,24 @@ + + + + + + + + + + + + + + + + + + @@ -3781,14 +12650,38 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - diff --git a/src/content/rev5/baselines/xml/FedRAMP_rev5_LI-SaaS-baseline_profile.xml b/src/content/rev5/baselines/xml/FedRAMP_rev5_LI-SaaS-baseline_profile.xml index e8e100ac2..2a9e79210 100644 --- a/src/content/rev5/baselines/xml/FedRAMP_rev5_LI-SaaS-baseline_profile.xml +++ b/src/content/rev5/baselines/xml/FedRAMP_rev5_LI-SaaS-baseline_profile.xml @@ -1316,7 +1316,7 @@ - +     @@ -1336,28 +1336,28 @@     - + - - - + + +

    Determine if the organization defines information system account types to be identified and selected to support organizational missions/business functions.

     - +

    Access control policy; procedures addressing account management; security plan; information system design documentation; information system configuration settings and associated documentation; list of active system accounts along with the name of the individual associated with each account; list of conditions for group and role membership; notifications or records of recently transferred, separated, or terminated employees; list of recently disabled information system accounts along with the name of the individual associated with each account; access authorization records; account management compliance reviews; information system monitoring records; information system audit records; other relevant documents or records.

         - +

    Organizational personnel with account management responsibilities; system/network administrators; organizational personnel with information security responsibilities.

         - +

    Organizational processes for account management on the information system; automated mechanisms for implementing account management.

     @@ -1370,7 +1370,7 @@     - +     @@ -1380,8 +1380,8 @@     - - + +

    NSO for non-privileged users. Attestation for privileged users related to multi-factor identification and authentication.

     @@ -1392,7 +1392,7 @@ - +

    FED - This is related to agency data and agency policy solution.

     @@ -1403,7 +1403,7 @@ - +

    FED - This is related to agency data and agency policy solution.

     @@ -1415,7 +1415,7 @@     - +     @@ -1424,7 +1424,7 @@ - +

    NSO - All access to Cloud SaaS are via web services and/or API. The device accessed from or whether via wired or wireless connection is out of scope. Regardless of device accessed from, must utilize approved remote access methods (AC-17), secure communication with strong encryption (SC-13), key management (SC-12), and multi-factor authentication for privileged access (IA-2[1]).

     @@ -1436,7 +1436,7 @@ - +

    NSO - All access to Cloud SaaS are via web service and/or API. The device accessed from is out of the scope. Regardless of device accessed from, must utilize approved remote access methods (AC-17), secure communication with strong encryption (SC-13), key management (SC-12), and multi-factor authentication for privileged access (IA-2 [1]).

     @@ -1447,7 +1447,7 @@ - + @@ -1457,7 +1457,7 @@     - + @@ -1466,7 +1466,7 @@ - + @@ -1475,7 +1475,7 @@ - + @@ -1484,7 +1484,7 @@ - + @@ -1493,7 +1493,7 @@ - + @@ -1502,7 +1502,7 @@ - + @@ -1511,7 +1511,7 @@ - + @@ -1520,7 +1520,7 @@ - + @@ -1529,7 +1529,7 @@     - + @@ -1537,7 +1537,7 @@ - +

    NSO - Loss of availability of the audit data has been determined to have little or no impact to government business/mission needs.

     @@ -1549,7 +1549,7 @@     - + @@ -1559,7 +1559,7 @@ - + @@ -1567,7 +1567,7 @@ - + @@ -1575,7 +1575,7 @@ - + @@ -1584,7 +1584,7 @@ - +

    NSO - Loss of availability of the audit data has been determined as little or no impact to government business/mission needs.

     @@ -1595,7 +1595,7 @@ - + @@ -1604,7 +1604,7 @@ - + @@ -1614,7 +1614,7 @@     - + @@ -1622,7 +1622,7 @@ - + @@ -1632,8 +1632,8 @@ - - + +

    Condition: There are connection(s) to external systems. Connections (if any) shall be authorized and must: 1) Identify the interface/connection. 2) Detail what data is involved and its sensitivity. 3) Determine whether the connection is one-way or bi-directional. 4) Identify how the connection is secured.

     @@ -1645,7 +1645,7 @@ - +

    Attestation - for compliance with FedRAMP Tailored LI-SaaS Continuous Monitoring Requirements.

     @@ -1657,7 +1657,7 @@     - + @@ -1667,7 +1667,7 @@     - + @@ -1677,7 +1677,7 @@ - + @@ -1687,7 +1687,7 @@ - + @@ -1697,8 +1697,8 @@ - - + +

    Condition: There are connection(s) to external systems. Connections (if any) shall be authorized and must: 1) Identify the interface/connection. 2) Detail what data is involved and its sensitivity. 3) Determine whether the connection is one-way or bi-directional. 4) Identify how the connection is secured.

     @@ -1710,7 +1710,7 @@ - + @@ -1718,7 +1718,7 @@ - + @@ -1727,7 +1727,7 @@     - + @@ -1737,7 +1737,7 @@ - + @@ -1747,7 +1747,7 @@ - +

    Required - Specifically include details of least functionality.

     @@ -1773,7 +1773,7 @@ - + @@ -1783,7 +1783,7 @@     - + @@ -1791,7 +1791,7 @@ - +

    NSO- Not directly related to protection of the data.

     @@ -1802,7 +1802,7 @@ - +

    NSO - Boundary is specific to SaaS environment; all access is via web services; users' machine or internal network are not contemplated. External services (SA-9), internal connection (CA-9), remote access (AC-17), and secure access (SC-12 and SC-13), and privileged authentication (IA-2[1]) are considerations.

     @@ -1814,7 +1814,7 @@ - + @@ -1823,7 +1823,7 @@ - +

    NSO - Loss of availability of the SaaS has been determined as little or no impact to government business/mission needs.

     @@ -1835,7 +1835,7 @@ - +

    NSO - Loss of availability of the SaaS has been determined as little or no impact to government business/mission needs.

     @@ -1847,7 +1847,7 @@ - +

    NSO - Loss of availability of the SaaS has been determined as little or no impact to government business/mission needs.

     @@ -1859,7 +1859,7 @@     - + @@ -1867,7 +1867,7 @@ - +

    NSO - Loss of availability of the SaaS has been determined as little or no impact to government business/mission needs.

     @@ -1879,7 +1879,7 @@ - + @@ -1887,8 +1887,8 @@ - - + +

    NSO for non-privileged users. Attestation for privileged users related to multi-factor identification and authentication - specifically include description of management of service accounts.

     @@ -1900,7 +1900,7 @@     - + IA-2(1) Additional FedRAMP Requirements and Guidance @@ -1913,9 +1913,12 @@ - + + + + - + @@ -1925,7 +1928,7 @@ - + @@ -1934,13 +1937,13 @@     - - + + - - - + + +

    Determine if the information system:

    • Accepts PIV credentials.
      • @@ -1955,7 +1958,7 @@ - + @@ -1964,7 +1967,7 @@ - + @@ -1973,7 +1976,7 @@ - + @@ -1982,15 +1985,18 @@ - + + + + - + @@ -1998,7 +2004,7 @@ - + @@ -2007,8 +2013,8 @@ - - + +

      Condition: Must document and assess for privileged users. May attest to this control for non-privileged users. FedRAMP requires a minimum of multi-factor authentication for all Federal privileged users, if acceptance of PIV credentials is not supported. The implementation status and details of how this control is implemented must be clearly defined by the CSP.

       @@ -2020,8 +2026,8 @@       - - + +

      Condition: Must document and assess for privileged users. May attest to this control for non-privileged users. FedRAMP requires a minimum of multi-factor authentication for all Federal privileged users, if acceptance of PIV credentials is not supported. The implementation status and details of how this control is implemented must be clearly defined by the CSP.

       @@ -2032,7 +2038,7 @@ - + @@ -2041,7 +2047,7 @@ - + @@ -2050,7 +2056,7 @@ - + @@ -2059,7 +2065,7 @@ - + @@ -2068,7 +2074,7 @@       - + @@ -2076,7 +2082,7 @@ - + @@ -2086,7 +2092,7 @@ - + @@ -2094,7 +2100,7 @@ - + @@ -2103,7 +2109,7 @@ - +

      Attestation - Specifically attest to US-CERT compliance.

       @@ -2115,7 +2121,7 @@ - + @@ -2124,8 +2130,8 @@       - - + +

      Condition: Control is not inherited from a FedRAMP-authorized PaaS or IaaS.

       @@ -2137,7 +2143,7 @@ - + @@ -2146,8 +2152,8 @@       - - + +

      Condition: Control is not inherited from a FedRAMP-authorized PaaS or IaaS.

       @@ -2159,7 +2165,7 @@ - + @@ -2168,8 +2174,8 @@       - - + +

      Condition: Control is not inherited from a FedRAMP-authorized PaaS or IaaS.

       @@ -2181,8 +2187,8 @@       - - + +

      Condition: Control is not inherited from a FedRAMP-authorized PaaS or IaaS.

       @@ -2194,8 +2200,8 @@       - - + +

      Condition: Control is not inherited from a FedRAMP-authorized PaaS or IaaS.

       @@ -2207,7 +2213,7 @@ - + @@ -2217,8 +2223,8 @@       - - + +

      Condition: Control is not inherited from a FedRAMP-authorized PaaS or IaaS.

       @@ -2231,8 +2237,8 @@       - - + +

      Condition: Control is not inherited from a FedRAMP-authorized PaaS or IaaS.

       @@ -2245,8 +2251,8 @@       - - + +

      Condition: Control is not inherited from a FedRAMP-authorized PaaS or IaaS.

       @@ -2259,8 +2265,8 @@       - - + +

      Condition: Control is not inherited from a FedRAMP-authorized PaaS or IaaS.

       @@ -2272,8 +2278,8 @@       - - + +

      Condition: Control is not inherited from a FedRAMP-authorized PaaS or IaaS.

       @@ -2285,8 +2291,8 @@       - - + +

      Condition: Control is not inherited from a FedRAMP-authorized PaaS or IaaS.

       @@ -2298,8 +2304,8 @@       - - + +

      Condition: Control is not inherited from a FedRAMP-authorized PaaS or IaaS.

       @@ -2320,8 +2326,8 @@       - - + +

      Condition: Control is not inherited from a FedRAMP-authorized PaaS or IaaS.

       @@ -2333,8 +2339,8 @@       - - + +

      Condition: Control is not inherited from a FedRAMP-authorized PaaS or IaaS.

       @@ -2346,7 +2352,7 @@ - + @@ -2356,7 +2362,7 @@       - + @@ -2364,7 +2370,7 @@ - + @@ -2373,7 +2379,7 @@ - + @@ -2383,7 +2389,7 @@ - + @@ -2392,7 +2398,7 @@ - + @@ -2401,7 +2407,7 @@ - + @@ -2410,7 +2416,7 @@ - + @@ -2418,7 +2424,7 @@ - + @@ -2427,7 +2433,7 @@ - + @@ -2436,7 +2442,7 @@ - + @@ -2445,7 +2451,7 @@ - + @@ -2454,7 +2460,7 @@ - + @@ -2463,7 +2469,7 @@ - +

      Attestation - Specifically stating that any third-party security personnel are treated as CSP employees.

       @@ -2474,7 +2480,7 @@ - + @@ -2483,7 +2489,7 @@ - + @@ -2492,7 +2498,7 @@ - + @@ -2503,7 +2509,7 @@       - + @@ -2512,7 +2518,7 @@ - + @@ -2521,7 +2527,7 @@ - + @@ -2531,7 +2537,7 @@ - + @@ -2541,7 +2547,7 @@ - + @@ -2551,7 +2557,7 @@ - + @@ -2561,7 +2567,7 @@ - + @@ -2570,7 +2576,7 @@ - + @@ -2578,7 +2584,7 @@ - + @@ -2586,7 +2592,7 @@ - + @@ -2594,7 +2600,7 @@ - + @@ -2603,7 +2609,7 @@ - + @@ -2611,7 +2617,7 @@ - + @@ -2620,7 +2626,7 @@ - + @@ -2629,7 +2635,7 @@ - + @@ -2639,7 +2645,7 @@ - + @@ -2648,7 +2654,7 @@ - + @@ -2657,8 +2663,8 @@ - - + +

      Condition: If availability is a requirement, define protections in place as per control requirement.

       @@ -2670,7 +2676,7 @@       - + @@ -2680,7 +2686,7 @@ - + @@ -2690,7 +2696,7 @@ - + @@ -2699,7 +2705,7 @@ - + @@ -2709,8 +2715,8 @@ - - + +

      Condition: If implementing need to detail how they meet it or don't meet it.

       @@ -2721,7 +2727,7 @@ - +

      NSO - Not directly related to the security of the SaaS.

       @@ -2732,7 +2738,7 @@ - + @@ -2740,7 +2746,7 @@ - + @@ -2748,7 +2754,7 @@ - + @@ -2758,7 +2764,7 @@       - + @@ -2768,7 +2774,7 @@       - + @@ -2776,7 +2782,7 @@ - + @@ -2785,7 +2791,7 @@ - + @@ -2795,7 +2801,7 @@ - + @@ -2805,7 +2811,7 @@ - + @@ -2815,7 +2821,7 @@ - + @@ -2823,7 +2829,7 @@ - + @@ -2831,7 +2837,7 @@ - +

      Attestation - Specifically related to US-CERT and FedRAMP communications procedures.

       @@ -2843,7 +2849,7 @@ - + @@ -2852,7 +2858,7 @@ - + @@ -2861,7 +2867,7 @@ - + @@ -2870,7 +2876,7 @@ - + @@ -2879,7 +2885,7 @@ - + @@ -2888,7 +2894,7 @@ - + @@ -2897,7 +2903,7 @@ - + @@ -2906,7 +2912,7 @@ - + @@ -2915,7 +2921,7 @@ - + @@ -2924,7 +2930,7 @@ - + @@ -2933,7 +2939,7 @@ - + diff --git a/src/content/rev5/baselines/xml/FedRAMP_rev5_LOW-baseline_profile.xml b/src/content/rev5/baselines/xml/FedRAMP_rev5_LOW-baseline_profile.xml index 1b73644ba..dcde518af 100644 --- a/src/content/rev5/baselines/xml/FedRAMP_rev5_LOW-baseline_profile.xml +++ b/src/content/rev5/baselines/xml/FedRAMP_rev5_LOW-baseline_profile.xml @@ -1310,8 +1310,298 @@ - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

      This response must address all control sub-statement requirements.

       +       +       + + + + + +

      This response must address all control sub-statement requirements.

       +       +       +       + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -1323,6 +1613,22 @@ + + + + + + + + + + + + + + + + @@ -1346,6 +1652,45 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -1362,6 +1707,22 @@       + + + + + + + + + + + + + + + + @@ -1370,6 +1731,256 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

      This response must address all control sub-statement requirements.

       +       +       + + + + + +

      This response must address all control sub-statement requirements.

       +       +       +       + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

      This response must address all control sub-statement requirements.

       +       +       + + + + + +

      This response must address all control sub-statement requirements.

       +       +       +       + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -1385,6 +1996,114 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -1397,6 +2116,33 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -1417,8 +2163,114 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

      This response must address all control sub-statement requirements.

       +       +       + + + + + +

      This response must address all control sub-statement requirements.

       +       +       +       @@ -1430,9 +2282,99 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -1448,6 +2390,22 @@ + + + + + + + + + + + + + + + + @@ -1459,10 +2417,54 @@ - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + CA-7 Additional FedRAMP Requirements and Guidance @@ -1479,8 +2481,105 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -1491,9 +2590,157 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

      This response must address all control sub-statement requirements.

       +       +       + + + + + +

      This response must address all control sub-statement requirements.

       +       +       +       + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -1504,8 +2751,56 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -1521,11 +2816,45 @@ -

      Compliance checks are used to evaluate configuration settings and provide general insight into the overall effectiveness of configuration management activities. CSPs and 3PAOs typically combine compliance check findings into a single CM-6 finding, which is acceptable. However, for initial assessments, annual assessments, and significant change requests, FedRAMP requires a clear understanding, on a per-control basis, where risks exist. Therefore, 3PAOs must also analyze compliance check findings as part of the controls assessment. Where a direct mapping exists, the 3PAO must document additional findings per control in the corresponding SAR Risk Exposure Table (RET), which are then documented in the CSP’s Plan of Action and Milestones (POA&M). This will likely result in the details of individual control findings overlapping with those in the combined CM-6 finding, which is acceptable.

      +

      Compliance checks are used to evaluate configuration settings and provide general insight into the overall effectiveness of configuration management activities. CSPs and 3PAOs typically combine compliance check findings into a single CM-6 finding, which is acceptable. However, for initial assessments, annual assessments, and significant change requests, FedRAMP requires a clear understanding, on a per-control basis, where risks exist. Therefore, 3PAOs must also analyze compliance check findings as part of the controls assessment. Where a direct mapping exists, the 3PAO must document additional findings per control in the corresponding SAR Risk Exposure Table (RET), which are then documented in the CSP's Plan of Action and Milestones (POA&M). This will likely result in the details of individual control findings overlapping with those in the combined CM-6 finding, which is acceptable.

      During monthly continuous monitoring, new findings from CSP compliance checks may be combined into a single CM-6 POA&M item. CSPs are not required to map the findings to specific controls because controls are only assessed during initial assessments, annual assessments, and significant change requests.

             + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +       @@ -1537,6 +2866,24 @@ + + + + + + + + + + + + + + + + + + @@ -1549,8 +2896,114 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

      This response must address all control sub-statement requirements.

       +       +       + + + + + +

      This response must address all control sub-statement requirements.

       +       +       +       + + + + + + + + + + + @@ -1566,6 +3019,104 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -1578,6 +3129,37 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -1594,6 +3176,46 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -1617,8 +3239,99 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

      This response must address all control sub-statement requirements.

       +       +       + + + + + +

      This response must address all control sub-statement requirements.

       +       +       +       @@ -1633,7 +3346,7 @@ -

      "Phishing-resistant" authentication refers to authentication processes designed to detect and prevent disclosure of authentication secrets and outputs to a website or application masquerading as a legitimate system.

      +

      "Phishing-resistant" authentication refers to authentication processes designed to detect and prevent disclosure of authentication secrets and outputs to a website or application masquerading as a legitimate system.

       @@ -1641,6 +3354,24 @@       + + + + + + + + + + + + + + + + + +       @@ -1660,6 +3391,16 @@ + + + + + + + + + + @@ -1679,6 +3420,16 @@ + + + + + + + + + + @@ -1691,8 +3442,69 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -1708,6 +3520,86 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -1719,7 +3611,7 @@ -

      For cases where technology doesn’t allow multi-factor authentication, these rules should be enforced: must have a minimum length of 14 characters and must support all printable ASCII characters.

      +

      For cases where technology doesn't allow multi-factor authentication, these rules should be enforced: must have a minimum length of 14 characters and must support all printable ASCII characters.

      For emergency use accounts, these rules should be enforced: must have a minimum length of 14 characters, must support all printable ASCII characters, and passwords must be changed if used.

       @@ -1728,6 +3620,65 @@       + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +       @@ -1747,16 +3698,180 @@ + + + + + + + + + - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

      This response must address all control sub-statement requirements.

       +       +       + + + + + +

      This response must address all control sub-statement requirements.

       +       +       +       + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + IR-4 Additional FedRAMP Requirements and Guidance -

      The FISMA definition of "incident" shall be used: "An occurrence that actually or imminently jeopardizes, without lawful authority, the confidentiality, integrity, or availability of information or an information system; or constitutes a violation or imminent threat of violation of law, security policies, security procedures, or acceptable use policies."

      +

      The FISMA definition of "incident" shall be used: "An occurrence that actually or imminently jeopardizes, without lawful authority, the confidentiality, integrity, or availability of information or an information system; or constitutes a violation or imminent threat of violation of law, security policies, security procedures, or acceptable use policies."

       @@ -1764,6 +3879,61 @@       + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +       + + + + + + + + + @@ -1776,6 +3946,37 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -1792,6 +3993,79 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -1801,6 +4075,408 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

      This response must address all control sub-statement requirements.

       +       +       + + + + + +

      This response must address all control sub-statement requirements.

       +       +       +       + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

      This response must address all control sub-statement requirements.

       +       +       + + + + + +

      This response must address all control sub-statement requirements.

       +       +       +       + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

      This response must address all control sub-statement requirements.

       +       +       + + + + + +

      This response must address all control sub-statement requirements.

       +       +       +       + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -1811,112 +4487,1781 @@ + + + + + + + + + + + + + + + + - - - - - PL-8 Additional FedRAMP Requirements and Guidance - - -

      Significant change is defined in NIST Special Publication 800-37 Revision 2, Appendix F.

      -       -       + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

      This response must address all control sub-statement requirements.

       +       +       + + + + + +

      This response must address all control sub-statement requirements.

       +       +       +       + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + PL-8 Additional FedRAMP Requirements and Guidance + + +

      Significant change is defined in NIST Special Publication 800-37 Revision 2, Appendix F.

      +       +       +       + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +       + + + + + PL-10 Additional FedRAMP Requirements and Guidance + + +

      Select the appropriate FedRAMP Baseline

      +       +       +       + + + + + + + +       + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

      This response must address all control sub-statement requirements.

       +       +       + + + + + +

      This response must address all control sub-statement requirements.

       +       +       +       + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

      This response must address all control sub-statement requirements.

       +       +       + + + + + +

      This response must address all control sub-statement requirements.

       +       +       +       + + + + + + + + + + + + + + + + + + + + + + + + + + + + RA-3 Additional FedRAMP Requirements and Guidance + + +

      Significant change is defined in NIST Special Publication 800-37 Revision 2, Appendix F.

      +       + + +

      Include all Authorizing Officials; for JAB authorizations to include FedRAMP.

      +       +       +       + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +       + + + + + + + + + + + + + + + + + + + + + + + + RA-5 Additional FedRAMP Requirements and Guidance + + +

      See the FedRAMP Documents page> Vulnerability Scanning Requirements https://www.FedRAMP.gov/documents/

      +       + + +

      an accredited independent assessor scans operating systems/infrastructure, web applications, and databases once annually.

      +       + + +

      If a vulnerability is listed among the CISA Known Exploited Vulnerability (KEV) Catalog (https://www.cisa.gov/known-exploited-vulnerabilities-catalog) the KEV remediation date supersedes the FedRAMP parameter requirement.

      +       + + +

      to include all Authorizing Officials; for JAB authorizations to include FedRAMP

      +       + + +

      Informational findings from a scanner are detailed as a returned result that holds no vulnerability risk or severity and for FedRAMP does not require an entry onto the POA&M or entry onto the RET during any assessment phase.

      +

      Warning findings, on the other hand, are given a risk rating (low, moderate, high or critical) by the scanning solution and should be treated like any other finding with a risk or severity rating for tracking purposes onto either the POA&M or RET depending on when the findings originated (during assessments or during monthly continuous monitoring). If a warning is received during scanning, but further validation turns up no actual issue then this item should be categorized as a false positive. If this situation presents itself during an assessment phase (initial assessment, annual assessment or any SCR), follow guidance on how to report false positives in the Security Assessment Report (SAR). If this situation happens during monthly continuous monitoring, a deviation request will need to be submitted per the FedRAMP Vulnerability Deviation Request Form.

      +

      Warnings are commonly associated with scanning solutions that also perform compliance scans, and if the scanner reports a "warning" as part of the compliance scanning of a CSO, follow guidance surrounding the tracking of compliance findings during either the assessment phases (initial assessment, annual assessment or any SCR) or monthly continuous monitoring as it applies. Guidance on compliance scan findings can be found by searching on "Tracking of Compliance Scans" in FAQs.

      +       +       +       + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +       + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

      This response must address all control sub-statement requirements.

       +       +       + + + + + +

      This response must address all control sub-statement requirements.

       +       +       +       + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + SA-4 Additional FedRAMP Requirements and Guidance + + +

      The service provider must comply with Federal Acquisition Regulation (FAR) Subpart 7.103, and Section 889 of the John S. McCain National Defense Authorization Act (NDAA) for Fiscal Year 2019 (Pub. L. 115-232), and FAR Subpart 4.21, which implements Section 889 (as well as any added updates related to FISMA to address security concerns in the system acquisitions process).

      +       + + +

      The use of Common Criteria (ISO/IEC 15408) evaluated products is strongly preferred.

      +

      See https://www.niap-ccevs.org/Product/index.cfm or https://www.commoncriteriaportal.org/products/.

      +       +       +       + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +       + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - - - - - PL-10 Additional FedRAMP Requirements and Guidance - - -

      Select the appropriate FedRAMP Baseline

      -       -       + + + + + + + +

      This response must address all control sub-statement requirements.

       +       +       + + + + + +

      This response must address all control sub-statement requirements.

       +       - - - - - - - - - - - - RA-3 Additional FedRAMP Requirements and Guidance - - -

      Significant change is defined in NIST Special Publication 800-37 Revision 2, Appendix F.

      -       - - -

      Include all Authorizing Officials; for JAB authorizations to include FedRAMP.

      -       -       + + + + + + + + + - - - - - - RA-5 Additional FedRAMP Requirements and Guidance - - -

      See the FedRAMP Documents page> Vulnerability Scanning Requirements https://www.FedRAMP.gov/documents/

      -       - - -

      an accredited independent assessor scans operating systems/infrastructure, web applications, and databases once annually.

      -       - - -

      If a vulnerability is listed among the CISA Known Exploited Vulnerability (KEV) Catalog (https://www.cisa.gov/known-exploited-vulnerabilities-catalog) the KEV remediation date supersedes the FedRAMP parameter requirement.

      -       - - -

      to include all Authorizing Officials; for JAB authorizations to include FedRAMP

      -       - - -

      Informational findings from a scanner are detailed as a returned result that holds no vulnerability risk or severity and for FedRAMP does not require an entry onto the POA&M or entry onto the RET during any assessment phase.

      -

      Warning findings, on the other hand, are given a risk rating (low, moderate, high or critical) by the scanning solution and should be treated like any other finding with a risk or severity rating for tracking purposes onto either the POA&M or RET depending on when the findings originated (during assessments or during monthly continuous monitoring). If a warning is received during scanning, but further validation turns up no actual issue then this item should be categorized as a false positive. If this situation presents itself during an assessment phase (initial assessment, annual assessment or any SCR), follow guidance on how to report false positives in the Security Assessment Report (SAR). If this situation happens during monthly continuous monitoring, a deviation request will need to be submitted per the FedRAMP Vulnerability Deviation Request Form.

      -

      Warnings are commonly associated with scanning solutions that also perform compliance scans, and if the scanner reports a “warning” as part of the compliance scanning of a CSO, follow guidance surrounding the tracking of compliance findings during either the assessment phases (initial assessment, annual assessment or any SCR) or monthly continuous monitoring as it applies. Guidance on compliance scan findings can be found by searching on “Tracking of Compliance Scans” in FAQs.

      -       -       + + + + + + + + + - - - - - - - - SA-4 Additional FedRAMP Requirements and Guidance - - -

      The service provider must comply with Federal Acquisition Regulation (FAR) Subpart 7.103, and Section 889 of the John S. McCain National Defense Authorization Act (NDAA) for Fiscal Year 2019 (Pub. L. 115-232), and FAR Subpart 4.21, which implements Section 889 (as well as any added updates related to FISMA to address security concerns in the system acquisitions process).

      -       - - -

      The use of Common Criteria (ISO/IEC 15408) evaluated products is strongly preferred.

      -

      See https://www.niap-ccevs.org/Product/index.cfm or https://www.commoncriteriaportal.org/products/.

      -       -       + + + + + + + + + + + + + + + - - - - @@ -1927,6 +6272,50 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -1944,7 +6333,7 @@
    • Replication between availability zones
    • Transmission of backups to storage
    • From a load balancer to a compute instance
      • -
    • Flows from management tools required for their work – e.g. log collection, scanning, etc.
      • +
    • Flows from management tools required for their work - e.g. log collection, scanning, etc.

    The following applies only when choosing SC-8 (5) in lieu of SC-8 (1).

    @@ -1958,7 +6347,7 @@

    Hardened or alarmed PDS: Shall be as defined in SECTION X - CATEGORY 2 PDS INSTALLATION GUIDANCE of CNSSI No.7003, titled PROTECTED DISTRIBUTION SYSTEMS (PDS). Per the CNSSI No. 7003 Section VIII, PDS must originate and terminate in a Controlled Access Area (CAA).

    -

    Controlled Access Area (CAA): Data will be considered physically protected, and in a CAA if it meets Section 2.3 of the DHS’s Recommended Practice: Improving Industrial Control System Cybersecurity with Defense-in-Depth Strategies. CSPs can meet Section 2.3 of the DHS’ recommended practice by satisfactory implementation of the following controls PE-2 (1), PE-2 (2), PE-2 (3), PE-3 (2), PE-3 (3), PE-6 (2), and PE-6 (3).

    +

    Controlled Access Area (CAA): Data will be considered physically protected, and in a CAA if it meets Section 2.3 of the DHS's Recommended Practice: Improving Industrial Control System Cybersecurity with Defense-in-Depth Strategies. CSPs can meet Section 2.3 of the DHS' recommended practice by satisfactory implementation of the following controls PE-2 (1), PE-2 (2), PE-2 (3), PE-3 (2), PE-3 (3), PE-6 (2), and PE-6 (3).

    Note: When selecting SC-8 (5), the above SC-8(5), and the above referenced PE controls must be added to the SSP.

    @@ -1970,6 +6359,18 @@     + + + + + + + + + + + + @@ -1981,7 +6382,7 @@ -

    See M-22-09, including "Agencies encrypt all DNS requests and HTTP traffic within their environment"

    +

    See M-22-09, including "Agencies encrypt all DNS requests and HTTP traffic within their environment"

    SC-8 (1) applies when encryption has been selected as the method to protect confidentiality and integrity. Otherwise refer to SC-8 (5). SC-8 (1) is strongly encouraged.

     @@ -1994,6 +6395,15 @@     + + + + + + + + +     @@ -2013,6 +6423,18 @@ + + + + + + + + + + + + @@ -2059,6 +6481,26 @@     + + + + + + + + + + + + + + + + + + + + @@ -2070,6 +6512,23 @@ + + + + + + + + + + + + + + + + + @@ -2093,6 +6552,30 @@ + + + + + + + + + + + + + + + + + + + + + + + + @@ -2126,6 +6609,18 @@ + + + + + + + + + + + + @@ -2145,6 +6640,18 @@ + + + + + + + + + + + + @@ -2160,10 +6667,172 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

    This response must address all control sub-statement requirements.

     +     +     + + + + + +

    This response must address all control sub-statement requirements.

     +     +     +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2175,6 +6844,77 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2184,10 +6924,208 @@

    Service Providers must address the CISA Emergency and Binding Operational Directives applicable to their cloud service offering per FedRAMP guidance. This includes listing the applicable directives and stating compliance status.

     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

    This response must address all control sub-statement requirements.

     +     +     + + + + + +

    This response must address all control sub-statement requirements.

     +     +     +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2199,8 +7137,48 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2212,6 +7190,14 @@ + + + + + + + + @@ -2225,17 +7211,38 @@     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - - - diff --git a/src/content/rev5/baselines/xml/FedRAMP_rev5_MODERATE-baseline_profile.xml b/src/content/rev5/baselines/xml/FedRAMP_rev5_MODERATE-baseline_profile.xml index 2c66aa0d8..58b9850c8 100644 --- a/src/content/rev5/baselines/xml/FedRAMP_rev5_MODERATE-baseline_profile.xml +++ b/src/content/rev5/baselines/xml/FedRAMP_rev5_MODERATE-baseline_profile.xml @@ -1495,7 +1495,7 @@ -

    personnel screening criteria – as required by specific information

    +

    personnel screening criteria - as required by specific information

         @@ -2070,6 +2070,427 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

    This response must address all control sub-statement requirements.

     +     +     + + + + + +

    This response must address all control sub-statement requirements.

     +     +     +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2089,6 +2510,54 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2101,6 +2570,54 @@     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2112,6 +2629,17 @@ + + + + + + + + + + + @@ -2128,8 +2656,140 @@     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2140,6 +2800,64 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2151,8 +2869,60 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2164,6 +2934,22 @@ + + + + + + + + + + + + + + + + @@ -2187,6 +2973,45 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2206,6 +3031,22 @@ + + + + + + + + + + + + + + + + @@ -2214,34 +3055,413 @@ - - - - - AU-2 Additional FedRAMP Requirements and Guidance - - -

    Coordination between service provider and consumer shall be documented and accepted by the JAB/AO.

    -     - - -

    Annually or whenever changes in the threat environment are communicated to the service provider by the JAB/AO.

    -     -     + + + + + - - - - - AU-3 (1) Additional FedRAMP Requirements and Guidance - - -

    For client-server transactions, the number of bytes sent and received gives bidirectional transfer information that can be helpful during an investigation or inquiry.

    -     -     + + + + -     - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

    This response must address all control sub-statement requirements.

     +     +     + + + + + +

    This response must address all control sub-statement requirements.

     +     +     +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

    This response must address all control sub-statement requirements.

     +     +     + + + + + +

    This response must address all control sub-statement requirements.

     +     +     +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + AU-2 Additional FedRAMP Requirements and Guidance + + +

    Coordination between service provider and consumer shall be documented and accepted by the JAB/AO.

    +     + + +

    Annually or whenever changes in the threat environment are communicated to the service provider by the JAB/AO.

    +     +     +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + AU-3 (1) Additional FedRAMP Requirements and Guidance + + +

    For client-server transactions, the number of bytes sent and received gives bidirectional transfer information that can be helpful during an investigation or inquiry.

    +     +     +     + + + + + + + + + + + +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2252,6 +3472,33 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2275,8 +3522,179 @@     + + + + + + + + + + +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

    This response must address all control sub-statement requirements.

     +     +     + + + + + +

    This response must address all control sub-statement requirements.

     +     +     +     @@ -2288,6 +3706,61 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2299,10 +3772,53 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2318,6 +3834,22 @@ + + + + + + + + + + + + + + + + @@ -2329,6 +3861,50 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2349,8 +3925,115 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2362,6 +4045,24 @@ + + + + + + + + + + + + + + + + + + @@ -2374,10 +4075,161 @@ + + + + + + + + + + + - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

    This response must address all control sub-statement requirements.

     +     +     + + + + + +

    This response must address all control sub-statement requirements.

     +     +     +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2388,6 +4240,68 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2404,9 +4318,155 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2422,11 +4482,57 @@ -

    Compliance checks are used to evaluate configuration settings and provide general insight into the overall effectiveness of configuration management activities. CSPs and 3PAOs typically combine compliance check findings into a single CM-6 finding, which is acceptable. However, for initial assessments, annual assessments, and significant change requests, FedRAMP requires a clear understanding, on a per-control basis, where risks exist. Therefore, 3PAOs must also analyze compliance check findings as part of the controls assessment. Where a direct mapping exists, the 3PAO must document additional findings per control in the corresponding SAR Risk Exposure Table (RET), which are then documented in the CSP’s Plan of Action and Milestones (POA&M). This will likely result in the details of individual control findings overlapping with those in the combined CM-6 finding, which is acceptable.

    +

    Compliance checks are used to evaluate configuration settings and provide general insight into the overall effectiveness of configuration management activities. CSPs and 3PAOs typically combine compliance check findings into a single CM-6 finding, which is acceptable. However, for initial assessments, annual assessments, and significant change requests, FedRAMP requires a clear understanding, on a per-control basis, where risks exist. Therefore, 3PAOs must also analyze compliance check findings as part of the controls assessment. Where a direct mapping exists, the 3PAO must document additional findings per control in the corresponding SAR Risk Exposure Table (RET), which are then documented in the CSP's Plan of Action and Milestones (POA&M). This will likely result in the details of individual control findings overlapping with those in the combined CM-6 finding, which is acceptable.

    During monthly continuous monitoring, new findings from CSP compliance checks may be combined into a single CM-6 POA&M item. CSPs are not required to map the findings to specific controls because controls are only assessed during initial assessments, annual assessments, and significant change requests.

         + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +     + + + + + + + + + + + @@ -2438,8 +4544,47 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2450,8 +4595,46 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2463,8 +4646,73 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2473,6 +4721,55 @@

    FedRAMP does not provide a template for the Configuration Management Plan. However, NIST SP 800-128, Guide for Security-Focused Configuration Management of Information Systems, provides guidelines for the implementation of CM controls as well as a sample CMP outline in Appendix D of the Guide

     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +     @@ -2485,6 +4782,40 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2497,9 +4828,94 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

    This response must address all control sub-statement requirements.

     +     +     + + + + + +

    This response must address all control sub-statement requirements.

     +     +     +     + + + + + + + + + + + + + + + + + + + + + + @@ -2515,6 +4931,134 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2527,6 +5071,37 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2543,6 +5118,109 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2554,8 +5232,41 @@ - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + CP-7 (1) Additional FedRAMP Requirements and Guidance @@ -2565,6 +5276,39 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2576,6 +5320,45 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2599,8 +5382,54 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2612,8 +5441,94 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

    This response must address all control sub-statement requirements.

     +     +     + + + + + +

    This response must address all control sub-statement requirements.

     +     +     +     + + + + + + + + + + + + + + + + + + + + + @@ -2632,10 +5547,28 @@ -

    "Phishing-resistant" authentication refers to authentication processes designed to detect and prevent disclosure of authentication secrets and outputs to a website or application masquerading as a legitimate system.

    +

    "Phishing-resistant" authentication refers to authentication processes designed to detect and prevent disclosure of authentication secrets and outputs to a website or application masquerading as a legitimate system.

         + + + + + + + + + + + + + + + + + +     @@ -2655,6 +5588,16 @@ + + + + + + + + + + @@ -2674,6 +5617,28 @@ + + + + + + + + + + + + + + + + + + + + + + @@ -2689,6 +5654,25 @@ + + + + + + + + + + + + + + + + + + + @@ -2700,8 +5684,89 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2717,6 +5782,86 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2728,7 +5873,7 @@ -

    For cases where technology doesn’t allow multi-factor authentication, these rules should be enforced: must have a minimum length of 14 characters and must support all printable ASCII characters.

    +

    For cases where technology doesn't allow multi-factor authentication, these rules should be enforced: must have a minimum length of 14 characters and must support all printable ASCII characters.

    For emergency use accounts, these rules should be enforced: must have a minimum length of 14 characters, must support all printable ASCII characters, and passwords must be changed if used.

     @@ -2737,6 +5882,98 @@     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2748,6 +5985,13 @@ + + + + + + + @@ -2769,6 +6013,15 @@ + + + + + + + + +     @@ -2781,6 +6034,31 @@ + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2796,9 +6074,172 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

    This response must address all control sub-statement requirements.

     +     +     + + + + + +

    This response must address all control sub-statement requirements.

     +     +     +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2810,6 +6251,27 @@ + + + + + + + + + + + + + + + + + + + + + @@ -2817,7 +6279,7 @@ IR-4 Additional FedRAMP Requirements and Guidance -

    The FISMA definition of "incident" shall be used: "An occurrence that actually or imminently jeopardizes, without lawful authority, the confidentiality, integrity, or availability of information or an information system; or constitutes a violation or imminent threat of violation of law, security policies, security procedures, or acceptable use policies."

    +

    The FISMA definition of "incident" shall be used: "An occurrence that actually or imminently jeopardizes, without lawful authority, the confidentiality, integrity, or availability of information or an information system; or constitutes a violation or imminent threat of violation of law, security policies, security procedures, or acceptable use policies."

     @@ -2825,8 +6287,76 @@     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +     + + + + + + + + + + + + + + + + + + + + + + + @@ -2838,8 +6368,71 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2855,22 +6448,528 @@ - - - - - - - - MA-5 (1) Additional FedRAMP Requirements and Guidance - - -

    Only MA-5 (1) (a) (1) is required by FedRAMP Moderate Baseline

    -     -     + + + -     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

    This response must address all control sub-statement requirements.

     +     +     + + + + + +

    This response must address all control sub-statement requirements.

     +     +     +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + MA-5 (1) Additional FedRAMP Requirements and Guidance + + +

    Only MA-5 (1) (a) (1) is required by FedRAMP Moderate Baseline

    +     +     +     + + + + + + + + + + + + + + + + + + + + + + +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

    This response must address all control sub-statement requirements.

     +     +     + + + + + +

    This response must address all control sub-statement requirements.

     +     +     +     + + + + + + + + + + + + + + + + + @@ -2881,6 +6980,20 @@ + + + + + + + + + + + + + + @@ -2892,6 +7005,42 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2903,6 +7052,43 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2912,6 +7098,239 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

    This response must address all control sub-statement requirements.

     +     +     + + + + + +

    This response must address all control sub-statement requirements.

     +     +     +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2922,31 +7341,685 @@ + + + + + + + + + + + + + + + + - - - - - PL-8 Additional FedRAMP Requirements and Guidance - - -

    Significant change is defined in NIST Special Publication 800-37 Revision 2, Appendix F.

    -     -     + + + + + - - - - - - PL-10 Additional FedRAMP Requirements and Guidance - - -

    Select the appropriate FedRAMP Baseline

    -     -     + + + + + + + + + + + + + + + + + + +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

    This response must address all control sub-statement requirements.

     +     +     + + + + + +

    This response must address all control sub-statement requirements.

     +     +     +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + PL-8 Additional FedRAMP Requirements and Guidance + + +

    Significant change is defined in NIST Special Publication 800-37 Revision 2, Appendix F.

    +     +     +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +     + + + + + PL-10 Additional FedRAMP Requirements and Guidance + + +

    Select the appropriate FedRAMP Baseline

    +     +     +     + + + + + +     @@ -2954,10 +8027,384 @@ - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

    This response must address all control sub-statement requirements.

     +     +     + + + + + +

    This response must address all control sub-statement requirements.

     +     +     +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

    This response must address all control sub-statement requirements.

     +     +     + + + + + +

    This response must address all control sub-statement requirements.

     +     +     +     + + + + + + + + + + + + + + + + + + + + + + + + @@ -2972,45 +8419,623 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + RA-5 Additional FedRAMP Requirements and Guidance + + +

    See the FedRAMP Documents page> Vulnerability Scanning Requirements https://www.FedRAMP.gov/documents/

    +     + + +

    an accredited independent assessor scans operating systems/infrastructure, web applications, and databases once annually.

    +     + + +

    If a vulnerability is listed among the CISA Known Exploited Vulnerability (KEV) Catalog (https://www.cisa.gov/known-exploited-vulnerabilities-catalog) the KEV remediation date supersedes the FedRAMP parameter requirement.

    +     + + +

    to include all Authorizing Officials; for JAB authorizations to include FedRAMP

    +     + + +

    Informational findings from a scanner are detailed as a returned result that holds no vulnerability risk or severity and for FedRAMP does not require an entry onto the POA&M or entry onto the RET during any assessment phase.

    +

    Warning findings, on the other hand, are given a risk rating (low, moderate, high or critical) by the scanning solution and should be treated like any other finding with a risk or severity rating for tracking purposes onto either the POA&M or RET depending on when the findings originated (during assessments or during monthly continuous monitoring). If a warning is received during scanning, but further validation turns up no actual issue then this item should be categorized as a false positive. If this situation presents itself during an assessment phase (initial assessment, annual assessment or any SCR), follow guidance on how to report false positives in the Security Assessment Report (SAR). If this situation happens during monthly continuous monitoring, a deviation request will need to be submitted per the FedRAMP Vulnerability Deviation Request Form.

    +

    Warnings are commonly associated with scanning solutions that also perform compliance scans, and if the scanner reports a "warning" as part of the compliance scanning of a CSO, follow guidance surrounding the tracking of compliance findings during either the assessment phases (initial assessment, annual assessment or any SCR) or monthly continuous monitoring as it applies. Guidance on compliance scan findings can be found by searching on "Tracking of Compliance Scans" in FAQs.

    +     +     +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

    This response must address all control sub-statement requirements.

     +     +     + + + + + +

    This response must address all control sub-statement requirements.

     +     +     +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - - - - - RA-5 Additional FedRAMP Requirements and Guidance - - -

    See the FedRAMP Documents page> Vulnerability Scanning Requirements https://www.FedRAMP.gov/documents/

    -     - - -

    an accredited independent assessor scans operating systems/infrastructure, web applications, and databases once annually.

    -     - - -

    If a vulnerability is listed among the CISA Known Exploited Vulnerability (KEV) Catalog (https://www.cisa.gov/known-exploited-vulnerabilities-catalog) the KEV remediation date supersedes the FedRAMP parameter requirement.

    -     - - -

    to include all Authorizing Officials; for JAB authorizations to include FedRAMP

    -     - - -

    Informational findings from a scanner are detailed as a returned result that holds no vulnerability risk or severity and for FedRAMP does not require an entry onto the POA&M or entry onto the RET during any assessment phase.

    -

    Warning findings, on the other hand, are given a risk rating (low, moderate, high or critical) by the scanning solution and should be treated like any other finding with a risk or severity rating for tracking purposes onto either the POA&M or RET depending on when the findings originated (during assessments or during monthly continuous monitoring). If a warning is received during scanning, but further validation turns up no actual issue then this item should be categorized as a false positive. If this situation presents itself during an assessment phase (initial assessment, annual assessment or any SCR), follow guidance on how to report false positives in the Security Assessment Report (SAR). If this situation happens during monthly continuous monitoring, a deviation request will need to be submitted per the FedRAMP Vulnerability Deviation Request Form.

    -

    Warnings are commonly associated with scanning solutions that also perform compliance scans, and if the scanner reports a “warning” as part of the compliance scanning of a CSO, follow guidance surrounding the tracking of compliance findings during either the assessment phases (initial assessment, annual assessment or any SCR) or monthly continuous monitoring as it applies. Guidance on compliance scan findings can be found by searching on “Tracking of Compliance Scans” in FAQs.

    -     -     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - - - - - - @@ -3026,6 +9051,93 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -3038,6 +9150,47 @@     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +     @@ -3050,10 +9203,478 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

    This response must address all control sub-statement requirements.

     +     +     + + + + + +

    This response must address all control sub-statement requirements.

     +     +     +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -3064,8 +9685,167 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - @@ -3076,6 +9856,46 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -3084,7 +9904,7 @@

    For each instance of data in transit, confidentiality AND integrity should be through cryptography as specified in SC-8 (1), physical means as specified in SC-8 (5), or in combination.

    -

    +

    For clarity, this control applies to all data in transit. Examples include the following data flows:

    • Crossing the system boundary
      • @@ -3093,9 +9913,9 @@
    • Replication between availability zones
    • Transmission of backups to storage
    • From a load balancer to a compute instance
      • -
    • Flows from management tools required for their work – e.g. log collection, scanning, etc.
      • +
    • Flows from management tools required for their work - e.g. log collection, scanning, etc.
    -

    +

    The following applies only when choosing SC-8 (5) in lieu of SC-8 (1).

    FedRAMP-Defined Assignment / Selection Parameters

    SC-8 (5)-1 [a hardened or alarmed carrier Protective Distribution System (PDS) when outside of Controlled Access Area (CAA)]

    @@ -3104,21 +9924,33 @@

    SC-8 (5) applies when physical protection has been selected as the method to protect confidentiality and integrity. For physical protection, data in transit must be in either a Controlled Access Area (CAA), or a Hardened or alarmed PDS.

    -

    +

    Hardened or alarmed PDS: Shall be as defined in SECTION X - CATEGORY 2 PDS INSTALLATION GUIDANCE of CNSSI No.7003, titled PROTECTED DISTRIBUTION SYSTEMS (PDS). Per the CNSSI No. 7003 Section VIII, PDS must originate and terminate in a Controlled Access Area (CAA).

    -

    -

    Controlled Access Area (CAA): Data will be considered physically protected, and in a CAA if it meets Section 2.3 of the DHS’s Recommended Practice: Improving Industrial Control System Cybersecurity with Defense-in-Depth Strategies. CSPs can meet Section 2.3 of the DHS’ recommended practice by satisfactory implementation of the following controls PE-2 (1), PE-2 (2), PE-2 (3), PE-3 (2), PE-3 (3), PE-6 (2), and PE-6 (3).

    -

    +

    +

    Controlled Access Area (CAA): Data will be considered physically protected, and in a CAA if it meets Section 2.3 of the DHS's Recommended Practice: Improving Industrial Control System Cybersecurity with Defense-in-Depth Strategies. CSPs can meet Section 2.3 of the DHS' recommended practice by satisfactory implementation of the following controls PE-2 (1), PE-2 (2), PE-2 (3), PE-3 (2), PE-3 (3), PE-6 (2), and PE-6 (3).

    +

    Note: When selecting SC-8 (5), the above SC-8(5), and the above referenced PE controls must be added to the SSP.

    -

    +

    CNSSI No.7003 can be accessed here:

    https://www.dcsa.mil/Portals/91/documents/ctp/nao/CNSSI_7003_PDS_September_2015.pdf

    -

    +

    DHS Recommended Practice: Improving Industrial Control System Cybersecurity with Defense-in-Depth Strategies can be accessed here:

    https://us-cert.cisa.gov/sites/default/files/FactSheets/NCCIC%20ICS_FactSheet_Defense_in_Depth_Strategies_S508C.pdf

         + + + + + + + + + + + +     @@ -3130,7 +9962,7 @@ -

    See M-22-09, including "Agencies encrypt all DNS requests and HTTP traffic within their environment"

    +

    See M-22-09, including "Agencies encrypt all DNS requests and HTTP traffic within their environment"

    SC-8 (1) applies when encryption has been selected as the method to protect confidentiality and integrity. Otherwise refer to SC-8 (5). SC-8 (1) is strongly encouraged.

     @@ -3143,6 +9975,15 @@     + + + + + + + + +     @@ -3162,6 +10003,18 @@ + + + + + + + + + + + + @@ -3178,7 +10031,7 @@
  • Generation of one time passwords (OTPs) for MFA
  • Protocols such as TLS, SSH, and HTTPS
    • -

    +

    The requirement for FIPS 140 validation, as well as timelines for acceptance of FIPS 140-2, and 140-3 can be found at the NIST Cryptographic Module Validation Program (CMVP).

    https://csrc.nist.gov/projects/cryptographic-module-validation-program

    @@ -3208,6 +10061,26 @@     + + + + + + + + + + + + + + + + + + + +     @@ -3219,6 +10092,23 @@ + + + + + + + + + + + + + + + + + @@ -3242,6 +10132,30 @@ + + + + + + + + + + + + + + + + + + + + + + + + @@ -3275,6 +10189,18 @@ + + + + + + + + + + + + @@ -3294,6 +10220,18 @@ + + + + + + + + + + + + @@ -3309,6 +10247,15 @@ + + + + + + + + + @@ -3329,11 +10276,238 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

    This response must address all control sub-statement requirements.

     +     +     + + + + + +

    This response must address all control sub-statement requirements.

     +     +     +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -3345,8 +10519,167 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -3357,6 +10690,15 @@ + + + + + + + + + @@ -3369,10 +10711,126 @@

    Service Providers must address the CISA Emergency and Binding Operational Directives applicable to their cloud service offering per FedRAMP guidance. This includes listing the applicable directives and stating compliance status.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -3388,6 +10846,22 @@ + + + + + + + + + + + + + + + + @@ -3400,10 +10874,194 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

    This response must address all control sub-statement requirements.

     +     +     + + + + + +

    This response must address all control sub-statement requirements.

     +     +     +     + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -3415,8 +11073,48 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -3428,6 +11126,14 @@ + + + + + + + + @@ -3440,6 +11146,14 @@ + + + + + + + + @@ -3455,16 +11169,38 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - - -