From 7924b86ab54eb7b4259d82277c9ebf82f2f6d10b Mon Sep 17 00:00:00 2001 From: Rene Tshiteya Date: Fri, 8 Nov 2024 10:41:01 -0500 Subject: [PATCH] Move has-fully-operational-date to appropriate context --- .../constraints/fedramp-external-constraints.xml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/src/validations/constraints/fedramp-external-constraints.xml b/src/validations/constraints/fedramp-external-constraints.xml index e22663b6b..f2dc84691 100644 --- a/src/validations/constraints/fedramp-external-constraints.xml +++ b/src/validations/constraints/fedramp-external-constraints.xml @@ -104,11 +104,6 @@ A FedRAMP SSP MUST define its NIST SP 800-63 authenticator assurance level (AAL). - - Fully Operational Date - - A FedRAMP SSP MUST define the system's fully operational date. - Has Authorization Boundary Diagram @@ -400,6 +395,11 @@ A FedRAMP SSP MUST specify the system's fully operational data as a "full-date" per RFC3339 with the addition of a timezone. --> + + Fully Operational Date + + A FedRAMP SSP MUST define the system's fully operational date. +