at least every 3 years
at least annually
significant changes
twenty-four (24) hours
eight (8) hours
eight (8) hours
quarterly for privileged access, annually for non-privileged access
Selection: disables
no more than 96 hours from last use
24 hours for user accounts
ninety (90) days (See additional requirements and guidance.)
for privileged users, it is the end of a user's standard work period
organization-defined need with justification statement that explains why such accounts are necessary
at a minimum, the ISSO and/or similar role within the organization
one (1) hour
all security functions
at a minimum, annually
all users with privileges
see additional Requirements and Guidance
see additional Requirements and Guidance
fifteen (15) minutes
at least quarterly
at least every 3 years
at least annually
significant changes
at least annually
at least annually
at least annually
at least annually
at least annually
at least one (1) year or 1 year after completion of a specific training program
at least every 3 years
at least annually
significant changes
successful and unsuccessful account logon events, account management events, object access, policy change, privilege functions, process tracking, and system events. For Web applications: all administrator activity, authentication checks, authorization checks, data deletions, data access, data changes, and permission changes
organization-defined subset of the auditable events defined in AU-2a to be audited continually for each identified event.
organization-defined subset of the auditable events defined in AU-2a to be audited continually for each identified event.
annually and whenever there is a change in the threat environment
session, connection, transaction, or activity duration; for client-server transactions, the number of bytes received and bytes sent; additional informational messages to diagnose or identify the event; characteristics that describe or identify the object or resource being acted upon; individual identities of group account users; full-text of privileged commands
overwrite oldest record
at least weekly
one second granularity of time measurement
a time period in compliance with M-21-31
all information system and network components where audit capability is deployed/available
at least every 3 years
at least annually
significant changes
at least annually
individuals or roles to include FedRAMP PMO
any FedRAMP Accredited 3PAO
the conditions of the AO in the FedRAMP Repository
at least annually and on input from AO
at least monthly
in accordance with OMB A-130 requirements or when a significant change occurs
to include AO
to include AO
at least annually
at least annually
at least every 3 years
at least annually
significant changes
at least annually and when a significant change occurs
to include when directed by the AO
Configuration control board (CCB) or similar (as defined in CM-3)
at least quarterly
at least quarterly
at least annually
at least quarterly or when there is a change
at least monthly
automated mechanisms with a maximum five-minute delay in detection
automated mechanisms with a maximum five-minute delay in detection
automated mechanisms with a maximum five-minute delay in detection
continuously
Continuously (via CM-7 (5))
Federal data and system data that must be protected at the High or Moderate impact levels
at least every 3 years
at least annually
significant changes
at least annually
all
time period defined in service provider and organization SLA
*See Additional Requirements
at least annually
at least annually
at least annually
functional exercises
functional exercises
daily incremental; weekly full
daily incremental; weekly full
daily incremental; weekly full
at least annually
at least annually
all backup files
at least every 3 years
at least annually
significant changes
local, network and remote
privileged accounts; non-privileged accounts
FIPS-validated or NSA-approved cryptography
privileged accounts; non-privileged accounts
at a minimum, the ISSO (or similar role within the organization)
at least two (2) years
contractors; foreign nationals
at least every 3 years
at least annually
significant changes
ten (10) days for privileged users, thirty (30) days for Incident Response roles
at least annually
at least annually
functional, at least annually
US-CERT incident reporting timelines as specified in NIST Special Publication 800-61 (as amended)
at least annually
see additional FedRAMP Requirements and Guidance
see additional FedRAMP Requirements and Guidance
see additional FedRAMP Requirements and Guidance
see additional FedRAMP Requirements and Guidance
at least annually
at least every 3 years
at least annually
significant changes
at least annually
the information owner
a timeframe to support advertised uptime and availability
at least every 3 years
at least annually
significant changes
all types of digital and/or non-digital media containing sensitive information
all types of digital and/or non-digital media containing sensitive information
no removable media types
organization-defined security safeguards not applicable
all types of digital and non-digital media with sensitive information
all types of digital and non-digital media with sensitive information
all types of digital and non-digital media with sensitive information
all types of digital and non-digital media with sensitive information
see additional FedRAMP requirements and guidance
see additional FedRAMP requirements and guidance
all media with sensitive information
prior to leaving secure/controlled environment: for digital media, encryption in compliance with Federal requirements and utilizes FIPS validated or NSA approved cryptography (see SC-13.); for non-digital media, secured in locked container
prior to leaving secure/controlled environment: for digital media, encryption in compliance with Federal requirements and utilizes FIPS validated or NSA approved cryptography (see SC-13.); for non-digital media, secured in locked container
techniques and procedures IAW NIST SP 800-88 Section 4: Reuse and Disposal of Storage Media and Hardware
techniques and procedures IAW NIST SP 800-88 Section 4: Reuse and Disposal of Storage Media and Hardware
techniques and procedures IAW NIST SP 800-88 Section 4: Reuse and Disposal of Storage Media and Hardware
at least every 3 years
at least annually
significant changes
at least annually
CSP defined physical access control systems/devices AND guards
in all circumstances within restricted access area where the information system resides
at least annually
at least annually or earlier as required by a security relevant event.
at least annually or earlier as required by a security relevant event.
at least monthly
for a minimum of one (1) year
at least monthly
near more than one egress point of the IT area and ensures it is labeled and protected by a cover to prevent accidental shut-off
service provider building maintenance/physical security personnel
service provider emergency responders with incident response responsibilities
consistent with American Society of Heating, Refrigerating and Air-conditioning Engineers (ASHRAE) document entitled Thermal Guidelines for Data Processing Environments
continuously
all information system components
all information system components
at least every 3 years
at least annually
significant changes
to include chief privacy and ISSO and/or similar role or designees
to include chief privacy and ISSO and/or similar role
at least annually
at least every 3 years
at least annually and when the rules are revised or changed
at least annually and when a significant change occurs
at least every 3 years
at least annually
significant changes
at least every three years
for national security clearances; a reinvestigation is required during the fifth (5th) year for top secret security clearance, the tenth (10th) year for secret security clearance, and fifteenth (15th) year for confidential security clearance.
For moderate risk law enforcement and high impact public trust level, a reinvestigation is required during the fifth (5th) year. There is no reinvestigation for other moderate risk positions or any low risk positions
for national security clearances; a reinvestigation is required during the fifth (5th) year for top secret security clearance, the tenth (10th) year for secret security clearance, and fifteenth (15th) year for confidential security clearance.
For moderate risk law enforcement and high impact public trust level, a reinvestigation is required during the fifth (5th) year. There is no reinvestigation for other moderate risk positions or any low risk positions
personnel screening criteria - as required by specific information
four (4) hours
twenty-four (24) hours
including access control personnel responsible for the system
twenty-four (24) hours
at least annually
at least annually and any time there is a change to the user's level of access
including access control personnel responsible for the system and/or facilities, as appropriate
within twenty-four (24) hours
to include the ISSO and/or similar role within the organization
24 hours
at least every 3 years
at least annually
significant changes
security assessment report
at least every three (3) years and when a significant change occurs
at least every three (3) years
monthly operating system/infrastructure; monthly web applications (including APIs) and databases
monthly operating system/infrastructure; monthly web applications (including APIs) and databases
high-risk vulnerabilities mitigated within thirty (30) days from date of discovery; moderate-risk vulnerabilities mitigated within ninety (90) days from date of discovery; low risk vulnerabilities mitigated within one hundred and eighty (180) days from date of discovery
within 24 hours prior to running scans
all components that support authentication
all scans
at least every 3 years
at least annually
significant changes
at a minimum to include security-relevant external system interfaces; high-level design; low-level design; source code or network and data flow diagram;
at a minimum, the ISSO (or similar role within the organization)
Appropriate FedRAMP Security Controls Baseline (s) if Federal information is processed or stored within the external system
Federal/FedRAMP Continuous Monitoring requirements must be met for external systems where Federal information is processed or stored
all external systems where Federal information is processed or stored
information processing, information or data, AND system services
development, implementation, AND operation
frequency at least annually
FedRAMP Security Authorization requirements
at least every 3 years
at least annually
significant changes
Protect against
at a minimum: ICMP (ping) flood, SYN flood, slowloris, buffer overflow attack, and volume attack
at least every 180 days or whenever there is a change in the threat environment that warrants a review of the exceptions
any systems
any network outside of organizational control and any network outside the authorization boundary
Host Intrusion Prevention System (HIPS), Host Intrusion Detection System (HIDS), or minimally a host-based firewall
confidentiality AND integrity
prevent unauthorized disclosure of information AND detect changes to information
no longer than ten (10) minutes for privileged sessions and no longer than fifteen (15) minutes for user sessions
In accordance with Federal requirements
FIPS-validated or NSA-approved cryptography
no exceptions for computing devices
confidentiality AND integrity
all information system components storing Federal data or system data that must be protected at the High or Moderate impact levels
At least hourly
http://tf.nist.gov/tf-cgi/servers.cgi
any difference
at least every 3 years
at least annually
significant changes
within thirty (30) days of release of updates
at least monthly
signature based and non-signature based
at least weekly
to include endpoints and network entry and exit points
to include blocking and quarantining malicious code
administrator or defined security personnel near-realtime
continuously
continuously
to include US-CERT and Cybersecurity and Infrastructure Security Agency (CISA) Directives
to include system security personnel and administrators with configuration/patch-management responsibilities
to include upon system startup and/or restart
at least monthly
to include system administrators and security personnel
selection to include security relevant event
selection to include security relevant event
selection to include security relevant event
at least monthly
at least monthly
at least monthly
to include the ISSO and/or similar role within the organization
to include chief privacy and ISSO and/or similar role or designees
to include chief privacy and ISSO and/or similar role or designees
at least every 3 years
at least annually
significant changes
at least annually
at least annually
notification of supply chain compromises and results of assessment or audits
all
Authenticators must be compliant with NIST SP 800-63-3 Digital Identity Guidelines IAL, AAL, FAL level 2. Link https://pages.nist.gov/800-63-3
SP 800-63C Section 6.2.3 Encrypted Assertion requires that authentication assertions be encrypted when passed through third parties, such as a browser. For example, a SAML assertion can be encrypted using XML-Encryption, or an OpenID Connect ID Token can be encrypted using JSON Web Encryption (JWE).
The fixed time period cannot exceed the limits set in SP 800-63. At this writing they are:
Only MA-5 (1) (a) (1) is required by FedRAMP Moderate Baseline
FedRAMP Logo