Trust Center
- Provider
- Mog Network LLC
- System
- FCD Receipt
- Acronym
- FCDR
- FedRAMP ID
- Mog Network LLC FCDR
- Certification type
- 20x
- Certification path
- Program
- Certification class
- Class C
- UEI
- Service model
- SaaS
- Deployment model
- Public Cloud
- Business category
- System Administration
- Website
- https://mognet.work
- Logo
- Logo
- Security
- security@mog.network
- Sales
- Sales
- Assessor
- Next report
- Services
- FCD Receipt
- Description
- Processes text files in place of real federal customer data.
- Advisors
- Third-party resources
- Secure configuration guide
- Responsible official
- Version
- 1
- Collection time
- Update source
- Scheduled AWS Lambda function
3fail
2partial
41pass
155fail
5partial
7pass
Key Security Indicators
Recovery planning
TRCfailKSI-RPL-TRC fail. The capability to recover from incidents and contingencies aligned with defined recovery objectives is persistently tested.ABOpassKSI-RPL-ABO pass. The alignment of machine-based information resource backups with defined recovery objectives is persistently reviewed.ARPpassKSI-RPL-ARP pass. The alignment of recovery plans with defined recovery objectives is persistently reviewed.RROpassKSI-RPL-RRO pass. The desired Recovery Time Objectives (RTO) and Recovery Point Objectives (RPO) are defined and persistently reviewed for alignment with the provider's business needs and capabilities.
Service configuration
PRRfailKSI-SVC-PRR fail. Plans, procedures, and the state of information resources are persistently reviewed after making changes to limit and remove unwanted residual elements that would likely negatively affect the confidentiality, integrity, or availability of federal customer data.RUDfailKSI-SVC-RUD fail. Unwanted federal customer data is removed promptly when requested by an agency in alignment with customer agreements, including from backups if appropriate; this typically applies when a customer spills information or when a customer seeks to remove information from a service due to a change in usage.ACMpassKSI-SVC-ACM pass. The configuration of machine-based information resources is managed using automation and persistently reviewed for drift.ASMpassKSI-SVC-ASM pass. Management, protection, and regular rotation of digital keys, certificates, and other secrets is automated and persistently reviewed.EISpassKSI-SVC-EIS pass. Information resources are persistently evaluated for opportunities to improve security and those improvements are persistently made.SINpassKSI-SVC-SIN pass. Information is encrypted or otherwise secured from unwanted access or modification.VCMpassKSI-SVC-VCM pass. The authenticity and integrity of communications between machine-based information resources is persistently validated using automation.VRIpassKSI-SVC-VRI pass. Use cryptographic methods to validate the integrity of machine-based information resources.
Policy and inventory
RVDpartialKSI-PIY-RVD partial. The effectiveness of the provider's vulnerability disclosure program is persistently reviewed.GIVpassKSI-PIY-GIV pass. Authoritative sources are used to automatically generate real-time inventories of all information resources when needed.RESpassKSI-PIY-RES pass. Executive support for achieving the provider's security goals is persistently reviewed and demonstrated.RISpassKSI-PIY-RIS pass. The effectiveness of the provider's investments in achieving security goals is persistently reviewed.RSDpassKSI-PIY-RSD pass. The effectiveness of building security and privacy considerations into the Software Development Lifecycle and aligning with CISA Secure By Design principles is persistently reviewed.
Supply chain risk
MONpartialKSI-SCR-MON partial. Third party software information resources are automatically monitored for upstream vulnerabilities using mechanisms that may include contractual notification requirements or active monitoring services.MITpassKSI-SCR-MIT pass. Potential supply chain risks are persistently identified, reviewed, and mitigated.
Change management
LMCpassKSI-CMT-LMC pass. Modifications to the cloud service offering are logged and monitored.RMVpassKSI-CMT-RMV pass. Changes to machine-based information resources are executed through the redeployment of version controlled resources rather than direct modification wherever reasonable.RVPpassKSI-CMT-RVP pass. The effectiveness of documented change management procedures is persistently reviewed.VTDpassKSI-CMT-VTD pass. Persistent testing and validation of changes throughout deployment is automated.
Cloud native architecture
DFPpassKSI-CNA-DFP pass. The functionality and privileges for infrastructure and services are strictly defined.EISpassKSI-CNA-EIS pass. Automated services are used to persistently assess the security of all machine-based information resources and automatically enforce their intended operational state.IBPpassKSI-CNA-IBP pass. The use and configuration of third-party machine-based information resources is persistently compared against the original provider's best practices and guidance.MATpassKSI-CNA-MAT pass. Machine-based information resources are persistently reviewed to ensure they have a minimal attack surface and that lateral movement is minimized if compromised.OFApassKSI-CNA-OFA pass. Machine-based information resources are persistently reviewed to ensure they are appropriately optimized for high availability and rapid recovery.RNTpassKSI-CNA-RNT pass. Machine-based information resources are persistently reviewed to ensure they are appropriately configured to limit inbound and outbound network traffic.RVPpassKSI-CNA-RVP pass. The effectiveness of protection against denial of service attacks and other unwanted activity for machine-based information resources is persistently reviewed.ULNpassKSI-CNA-ULN pass. Logical networking and related capabilities are used and persistently reviewed to enforce traffic flow controls.
Cybersecurity education
RATpassKSI-CED-RAT pass. The effectiveness of relevant cybersecurity education and training is persistently reviewed, including at least general training for all employees, role-specific training for employees in high risk roles, training for development and engineering staff on secure software delivery, and training for staff involved with incident response or disaster recovery.
Identity and access management
AAMpassKSI-IAM-AAM pass. The lifecycle and privileges of all accounts, roles, and groups are securely managed using automation.APMpassKSI-IAM-APM pass. Secure passwordless methods are used for user authentication and authorization when feasible, otherwise strong passwords with phishing-resistant MFA is used.ELPpassKSI-IAM-ELP pass. Identity and access management measures are used and persistently reviewed to ensure each user or device can only access the resources they need.JITpassKSI-IAM-JIT pass. A least-privileged, role and attribute-based, and just-in-time security authorization model is used and persistently reviewed for all user and non-user accounts and services.SNUpassKSI-IAM-SNU pass. Appropriately secure authentication methods are used and persistently reviewed for non-user accounts and services.SUSpassKSI-IAM-SUS pass. Accounts with privileged access are disabled or otherwise secured in response to suspicious activity.
Incident response
AARpassKSI-INR-AAR pass. Incident after action reports are generated and lessons learned are persistently incorporated.RIRpassKSI-INR-RIR pass. The effectiveness of documented incident response procedures is persistently reviewed.RPIpassKSI-INR-RPI pass. Past incidents are persistently reviewed for patterns or vulnerabilities that were not previously apparent or identified.
Monitoring, logging, and auditing
ALApassKSI-MLA-ALA pass. A least-privileged, role and attribute-based, and just-in-time access authorization model is used and persistently reviewed for access to log data based on organizationally defined data sensitivity.EVCpassKSI-MLA-EVC pass. The configuration of machine-based information resources, especially infrastructure as code, is persistently evaluated and tested.LETpassKSI-MLA-LET pass. A list of information resources and event types that will be logged, monitored, and audited is maintained and persistently reviewed to ensure these activities occur.OSMpassKSI-MLA-OSM pass. A Security Information and Event Management (SIEM) or similar system(s) is used and persistently reviewed for centralized, tamper-resistant logging of events, activities, and changes.RVLpassKSI-MLA-RVL pass. Logs are persistently reviewed and audited.
FedRAMP rules
Addressing FedRAMP communication
CSO-INBfailAFC-CSO-INB fail. Maintain a FedRAMP Security Inbox. Providers MUST establish and maintain an email address to receive messages from FedRAMP; this inbox is a FedRAMP Security Inbox (FSI).CSO-NOCfailAFC-CSO-NOC fail. Notification of Changes. Providers MUST immediately notify FedRAMP of any changes to the email address for their FedRAMP Security Inbox.CSO-TFGfailAFC-CSO-TFG fail. Trust @fedramp.gov and @gsa.gov. Providers MUST treat any email originating from an @fedramp.gov or @gsa.gov email address as if it was sent from FedRAMP by default; if such a message is confirmed to originate from someone other than FedRAMP then the FedRAMP Security Inbox rules no longer apply.CSO-RCVfailAFC-CSO-RCV fail. Receive Email Without Disruption. Providers MUST receive and react to email messages from FedRAMP without disruption and without requiring additional actions from FedRAMP.CSO-CRAfailAFC-CSO-CRA fail. Complete Required Actions. Providers MUST complete the required actions in Emergency or Emergency Test designated messages sent by FedRAMP within the timeframe included in the message.CSO-EMRfailAFC-CSO-EMR fail. Emergency Message Routing. Providers MUST route Emergency designated messages sent by FedRAMP to a senior security official for their awareness.CSO-IMAfailAFC-CSO-IMA fail. Important Message Actions. Providers SHOULD complete the required actions in Important designated messages sent by FedRAMP within the timeframe specified in the message.CSO-ACKfailAFC-CSO-ACK fail. Acknowledge Receipt. Providers SHOULD promptly and automatically acknowledge the receipt of messages received from FedRAMP in their FedRAMP Security Inbox.
Collaborative continuous monitoring
OCR-AVLfailCCM-OCR-AVL fail. Report Availability. Providers MUST supply an Ongoing Certification Report to all necessary parties every 3 months, covering the entire period since the previous summary, in a consistent format that is human readable; this report MUST include high-level summaries of at least the following information (if applicable): Changes to FedRAMP Certification Data; Planned changes to FedRAMP Certification Data during at least the next 3 months; Accepted vulnerabilities; Transformative changes; Updated recommendations or best practices for security, configuration, usage, or similar aspects of the cloud service offering; A list of all agencies that are directly using the product; FedRAMP Reportable Incidents or an attestation that no such incidents occurred; Lessons learned and changes planned or made as a result of FedRAMP Reportable Incidents (if such occurred).OCR-NRDfailCCM-OCR-NRD fail. Next Report Date. Providers MUST supply the target date for their next Ongoing Certification Report with other public FedRAMP Certification Data.OCR-FBMfailCCM-OCR-FBM fail. Feedback Mechanism. Providers MUST supply an asynchronous mechanism for all necessary parties to provide feedback or ask questions about each Ongoing Certification Report.OCR-AFSfailCCM-OCR-AFS fail. Anonymized Feedback Summary. Providers MUST supply an anonymized and desensitized summary of the feedback, questions, and answers about each Ongoing Certification Report as an addendum to the Ongoing Certification Report OR in the next Ongoing Certification Report.OCR-LSIfailCCM-OCR-LSI fail. Limit Sensitive Information. Providers MUST NOT irresponsibly disclose sensitive information in an Ongoing Certification Report that would likely have an adverse effect on the cloud service offering.OCR-SORfailCCM-OCR-SOR fail. Spread Out Reports. Providers SHOULD establish a regular 3 month cycle for Ongoing Certification Reports that is spread out from the beginning, middle, or end of each quarter.OCR-RPSfailCCM-OCR-RPS fail. Responsible Public Certification Report Sharing. Providers MAY responsibly supply some or all of the information an Ongoing Certification Report to the public or other parties if the provider determines doing so will NOT likely have an adverse effect on the cloud service offering.QTR-MTGfailCCM-QTR-MTG fail. Quarterly Review Meeting. Providers with Class C Certifications MUST host a synchronous Quarterly Review every 3 months, open to all necessary parties, to review aspects of the most recent Ongoing Certification Reports that the provider determines are of the most relevance to agencies.QTR-REGfailCCM-QTR-REG fail. Meeting Registration Info. Providers MUST supply either a registration link or a downloadable calendar file with meeting information for Quarterly Reviews to all necessary parties.QTR-NRDfailCCM-QTR-NRD fail. Next Review Date. Providers MUST publicly supply the target date for their next Quarterly Review with other public FedRAMP Certification Data.QTR-NIDfailCCM-QTR-NID fail. No Irresponsible Disclosure. Providers MUST NOT irresponsibly disclose sensitive information in a Quarterly Review that would likely have an adverse effect on the cloud service offering.QTR-SARfailCCM-QTR-SAR fail. Schedule Around Reports. Providers SHOULD regularly schedule Quarterly Reviews to occur at least 3 business days after releasing an Ongoing Certification Report AND within 10 business days of such release.QTR-ACTfailCCM-QTR-ACT fail. Additional Content. Providers SHOULD supply additional information in Quarterly Reviews that the provider determines is of interest, use, or otherwise relevant to agencies.QTR-RTRfailCCM-QTR-RTR fail. Record/Transcribe Reviews. Providers SHOULD record or transcribe Quarterly Reviews and supply them to all necessary parties.QTR-RTPfailCCM-QTR-RTP fail. Restrict Third Parties. Providers SHOULD NOT invite third parties to attend Quarterly Reviews intended for agencies unless they have specific relevance.QTR-SRRfailCCM-QTR-SRR fail. Share Recordings Responsibly. Providers MAY responsibly supply recordings or transcriptions of Quarterly Reviews to the public or other parties ONLY if the provider removes all agency information (comments, questions, names, etc.) AND determines doing so will NOT likely have an adverse effect on the cloud service offering.QTR-SCRfailCCM-QTR-SCR fail. Share Content Responsibly. Providers MAY responsibly supply content prepared for a Quarterly Review to the public or other parties if the provider determines doing so will NOT likely have an adverse effect on the cloud service offering.
Certification data sharing
CSO-PUBpartialCDS-CSO-PUB partial. Public Information. Providers MUST publicly share up-to-date information about the cloud service offering in both human-readable and JSON formats, including at least the following information that is available and applicable: FedRAMP ID; Service Model; Deployment Model; Business Category; UEI Number; Sales Contact Information; Security Contact Information; Product Website Link; Link to Product Logo (must be a valid image link, properly named, that will display in a browser without processing - transparent PNG preferred); Overall Service Description; Detailed list of specific services and their security categories (see CDS-CSO-SVC (Public Service List) (Service List)); Link to Secure Configuration Guidance; Overview of documentation supplied by the provider for the cloud service offering; Link to Trust Center landing page that includes instructions on accessing information in the trust center; Next Ongoing Certification Report date (see CCM-OCR-NRD (Next Report Date)); Current FedRAMP Recognized independent assessment service.CSO-SVCfailCDS-CSO-SVC fail. Public Service List. Providers MUST publicly share a detailed list of specific services and their security categories that are included in the cloud service offering using clear feature or service names that align with standard public marketing materials; this list MUST be complete enough for a potential customer to determine which services are and are not included in the FedRAMP Minimum Assessment Scope without requesting access to underlying FedRAMP Certification Data.CSO-FIDfailCDS-CSO-FID fail. Always Include FedRAMP ID. Providers MUST always include the FedRAMP ID of the related cloud service offering in all FedRAMP Certification Data once assigned, including all reports, notifications, and other communication that results from FedRAMP rules.CSO-FRCfailCDS-CSO-FRC fail. FedRAMP Certification Reports. Providers MUST include FedRAMP Certification Reports with their FedRAMP Certification Data without inappropriate modifications, and make such reports available within 2 weeks of receiving the materials from FedRAMP.CSO-AVRfailCDS-CSO-AVR fail. Availability Reporting. Providers with Class C Certifications MUST maintain a web service, available to all necessary parties, that indicates current and historical availability of core services within the cloud service offering over at least the past 30 days, including availability incidents, in both human-readable and machine-readable formats; this service MUST be available even if the primary cloud service offering is unavailable.CSO-UTCfailCDS-CSO-UTC fail. Use Trust Centers. Providers MUST use a FedRAMP-compatible trust center to store and share FedRAMP Certification Data with all necessary parties.CSO-CBFpassCDS-CSO-CBF pass. Consistency Between Formats. Providers MUST use automation to ensure information remains consistent between human-readable and machine-readable formats when FedRAMP Certification Data is provided in both formats.CSO-RISfailCDS-CSO-RIS fail. Responsible Information Sharing. Providers MUST provide sufficient information in FedRAMP Certification Data to support agency authorization decisions but SHOULD NOT include sensitive information that would likely enable a threat actor to gain unauthorized access, cause harm, disrupt operations, or otherwise have a negative adverse impact on the cloud service offering.CSO-IRPfailCDS-CSO-IRP fail. Include Relevant Policies. Providers MUST supply all relevant policies and procedures in the FedRAMP Certification Data, including a human-readable and machine-readable reference that explains at least the following about each included policy and procedure: Name of policy or procedure; Name of file, document, web page, etc.; Brief summary of policy or procedure; Word count of document; Current version; Date of last update; Related FedRAMP Practices (if applicable).CSO-HADfailCDS-CSO-HAD fail. Historical FedRAMP Certification Data. Providers MUST supply snapshots of FedRAMP Certification Data aligned to Ongoing Certification Reports to all necessary parties; these snapshots MUST be available for the duration of FedRAMP Certification.CSO-PSMfailCDS-CSO-PSM fail. Per-Service Certification Materials. Providers with Class C Certifications MAY supply per-service FedRAMP Certification materials.CSO-RPSfailCDS-CSO-RPS fail. Responsible Public Package Sharing. Providers MAY responsibly share some or all of the information in a FedRAMP Certification Package publicly or with other parties if the provider determines doing so will NOT likely have an adverse effect on the cloud service offering.TRC-USHfailCDS-TRC-USH fail. Uninterrupted Sharing. Trust centers MUST share FedRAMP Certification Data with all necessary parties without interruption.TRC-PACpassCDS-TRC-PAC pass. Programmatic Access. Trust centers MUST provide documented programmatic access to all FedRAMP Certification Data, including programmatic access to human-readable materials.TRC-AAIpassCDS-TRC-AAI pass. Agency Access Inventory. Trust centers MUST maintain an inventory and history of federal agency users or systems with access to FedRAMP Certification Data and MUST make this information available to FedRAMP upon request.TRC-ACLfailCDS-TRC-ACL fail. Access Logging. Trust centers MUST log access to FedRAMP Certification Data and store summaries of access for at least six months; such information, as it pertains to specific parties, SHOULD be made available upon request by those parties.TRC-HMRfailCDS-TRC-HMR fail. Human and Machine-Readable Certification Data. Trust centers SHOULD make FedRAMP Certification Data available to view and download in both human-readable and machine-readable formats.TRC-SSMfailCDS-TRC-SSM fail. Self-Service Access Management. Trust centers SHOULD include features that encourage all necessary parties to provision and manage access to FedRAMP Certification Data for their users and services directly.UTC-AADfailCDS-UTC-AAD fail. Agency Access Denial. Providers MUST notify FedRAMP within 5 business days of denying an agency access request for FedRAMP Certification Data.UTC-AGAfailCDS-UTC-AGA fail. Agency Access. Providers SHOULD supply access to the FedRAMP Certification Package with agencies upon request.
Cryptographic module use
CSO-CMDfailCMU-CSO-CMD fail. Cryptographic Module Documentation. Providers MUST document the cryptographic modules used in each service (or groups of services that use the same modules) where cryptographic services are used to protect federal customer data, including whether these modules are validated under the NIST Cryptographic Module Validation Program or are update streams of such modules.CSO-UVMfailCMU-CSO-UVM fail. Using Validated Cryptographic Modules. Providers with Class C Certifications SHOULD use cryptographic modules or update streams of cryptographic modules with active validations under the NIST Cryptographic Module Validation Program when using cryptographic services to protect federal customer data.CSO-CATfailCMU-CSO-CAT fail. Configuration of Agency Tenants. Providers SHOULD configure agency tenants by default to use cryptographic services that use cryptographic modules or update streams of cryptographic modules with active validations under the NIST Cryptographic Module Validation Program when such modules are available.
Certification package overview
CSO-OVRfailCPO-CSO-OVR fail. Overview of the Cloud Service Offering. Providers MUST supply a Certification Package Overview within their FedRAMP Certification Package, in both human-readable and JSON formats, that includes at least all of the information required by the following rules: Certification Package Overview: CPO-CSO-MTD (Certification Package Overview Metadata); Certification Data Sharing: CDS-CSO-PUB (Public Information); Certification Data Sharing: CDS-CSO-SVC (Public Service List); Certification Data Sharing: CDS-CSO-IRP (Include Relevant Policies); Minimum Assessment Scope: MAS-CSO-IIR (Identify Information Resources); Minimum Assessment Scope: MAS-CSO-FLO (Information Flows and Security Categories); Minimum Assessment Scope: MAS-CSO-TPR (Third-Party Information Resources); Using Cryptographic Modules: CMU-CSO-CMD (Cryptographic Module Documentation); Independent Verification and Validation: IVV-CSO-ICP (Inclusion in Certification Package).CSO-MTDfailCPO-CSO-MTD fail. Certification Package Overview Metadata. Providers MUST also include the following basic metadata in their Certification Package Overview: Name, title, and contact information of official that is responsible and accountable for the FedRAMP Certification Package; Version; Date and time of last update; Source of update.CSO-OSAfailCPO-CSO-OSA fail. Overall Summary of Assessment in Certification Package. Providers seeking Class C Certification MUST also include the overall summary of their FedRAMP independent assessment, supplied by the assessor per IVV-IAS-OSA (Overall Summary of Assessment), in their Certification Package Overview.CSX-CPMfailCPO-CSX-CPM fail. Certification Package Maintenance for 20x. Providers with 20x Class C Certifications MUST persistently maintain their FedRAMP Certification Package to ensure it is up to date and complete at least once every 2 weeks.
FedRAMP certification
CSO-FCPfailFRC-CSO-FCP fail. FedRAMP Certification Profile. Providers MUST identify a target FedRAMP Certification Profile and apply all relevant FedRAMP Practices to the cloud service offering.CSO-PKGfailFRC-CSO-PKG fail. FedRAMP Certification Package. Providers seeking a Certification MUST supply a complete FedRAMP Certification Package to FedRAMP for initial certification; the FedRAMP Certification Package MUST include at least the following information: Information about the Cloud Service Offering following CPO-CSO-OVR (Overview of the Cloud Service Offering); Implementation, Validation, and Assessment information for each relevant FedRAMP requirement/control/ksi as defined in SDR-CSO-FRR (FedRAMP Rules); A real or example Ongoing Certification Report following CCM-OCR-AVL (Report Availability).CSO-JSNpartialFRC-CSO-JSN partial. FedRAMP JSON Schemas. Providers MUST supply machine-readable information in JSON documents that are valid against the corresponding JSON schema when a rule contains a FedRAMP JSON schema, UNLESS otherwise specified in the rule; public JSON data MUST be supplied in a manner compatible with modern web frameworks, including: Cross-Origin Resource Sharing (CORS) should allow web applications running on a different domain to access the public JSON data directly.; Proper web application headers should be supplied for public JSON data, including at least setting Content-Type to application/json and X-Content-Type-Options: nosniff..CSO-MRAfailFRC-CSO-MRA fail. Maintain Responsibility and Accountability. Providers MUST maintain responsibility and accountability for the accuracy and completeness of all information in the FedRAMP Certification Package, especially when they engage a third party (such as an independent assessor, advisory service, or external tools) to supply information on their behalf.CSO-POPpassFRC-CSO-POP pass. Pick One Program Certification Type. Providers MUST NOT seek both FedRAMP Rev5 Program Certification and FedRAMP 20x Program Certification for the same cloud service offering; pick one type.CLA-ASFfailFRC-CLA-ASF fail. Approved Alternative Security Frameworks. Providers seeking a FedRAMP Class A Certification MUST have completed a certification or equivalent process, including an independent assessment if applicable, from one of the following alternative security frameworks within the past 12 months: FedRAMP Rev5 (including FedRAMP Ready) at any historical Impact Level; SOC 2 Type II; GovRAMP at any Impact Level.CLA-EAMfailFRC-CLA-EAM fail. External Assessment Materials. Providers seeking a FedRAMP Class A Certification MUST supply the following materials from their alternative security framework assessment to all necessary parties: SOC 2 Type II: Complete report, bridge or gap letter (if applicable), verified audit engagement documentation, estimated schedule for upcoming report, supplemental compliance evidence (if applicable); FedRAMP Ready: Readiness Assessment Report, Security Assessment Plan, and any other materials required by FedRAMP.; GovRAMP: Readiness Assessment Report, Security Assessment Plan, and any other materials required by GovRAMP..CLA-MFRfailFRC-CLA-MFR fail. Mandatory FedRAMP Rules for Class A. Providers seeking a Class A FedRAMP Certification MUST address all rules in this FedRAMP Class A Certification subset (FRC-CLA) AND the following additional FedRAMP Class A rules; the appropriate artifacts or information mapping for all rules MUST be supplied in the FedRAMP Certification Package. FedRAMP Certification: FRC-CSO-PKG (FedRAMP Certification Package); FedRAMP Certification: FRC-CSO-JSN (FedRAMP JSON Schemas); FedRAMP Certification: FRC-CSO-POP (Pick One Program Certification Type); Minimum Assessment Scope: MAS-CSO-IIR (Identify Information Resources); Certification Data Sharing: CDS-CSO-PUB (Public Information); Certification Data Sharing: CDS-CSO-UTC (Use Trust Centers); Certification Data Sharing: CDS-UTC-AAD (Agency Access Denial); Addressing FedRAMP Communication: AFC-CSO-INB (Maintain a FedRAMP Security Inbox); Addressing FedRAMP Communication: AFC-CSO-RCV (Receive Email Without Disruption); Addressing FedRAMP Communication: AFC-CSO-CRA (Complete Required Actions); Incident Evaluation and Communication: IEC-CSO-EFR (Evaluate FedRAMP Reportability); Incident Evaluation and Communication: IEC-CSO-FIR (Final Incident Report); Vulnerability Detection and Response: VDR-CSO-DET (Vulnerability Detection); Collaborative Continuous Monitoring: CCM-OCR-AVL (Report Availability); Collaborative Continuous Monitoring: CCM-OCR-NRD (Next Report Date); Independent Verification and Validation: IVV-CSX-AIA (Annual Independent Assessments for 20x); Key Security Indicators: KSI-CMT-LMC (Logging Changes); Key Security Indicators: KSI-CNA-RNT (Restricting Network Traffic); Key Security Indicators: KSI-CED-RAT (Reviewing All Training); Key Security Indicators: KSI-IAM-AAM (Automating Account Management); Key Security Indicators: KSI-IAM-APM (Adopting Passwordless Methods); Key Security Indicators: KSI-INR-RIR (Reviewing Incident Response Procedures); Key Security Indicators: KSI-SVC-SIN (Securing Information).CLA-RFRfailFRC-CLA-RFR fail. Recommended FedRAMP Rules for Class A. Providers seeking a Class A FedRAMP Certification SHOULD address the following additional recommended FedRAMP Class A rules (if applicable): Certification Data Sharing: CDS-CSO-AVR (Availability Reporting); Certification Package Overview: CPO-CSF-CPM (Certification Package Maintenance for Rev5); Certification Package Overview: CPO-CSX-CPM (Certification Package Maintenance for 20x); Incident Evaluation and Communication: IEC-CSO-IIR (Initial Incident Report); Incident Evaluation and Communication: IEC-CSO-OIR (Ongoing Incident Reports); Vulnerability Detection and Response: VDR-TFR-MVX (Persistent Machine Verification and Validation for 20x); Vulnerability Detection and Response: VDR-TFR-PCD (Persistently Complete Detection); Vulnerability Detection and Response: VDR-TFR-PDD (Persistent Drift Detection); Vulnerability Detection and Response: VDR-TFR-PSD (Persistent Sample Detection); Vulnerability Detection and Response: VDR-TFR-PVR (Mitigation and Remediation Expectations); Vulnerability Evaluation and Reporting: VER-TFR-EVU (Evaluate Vulnerabilities Quickly).CLA-OFRfailFRC-CLA-OFR fail. Address Optional FedRAMP Rules for Class A. Providers seeking a Class A FedRAMP Certification MAY address the following additional optional FedRAMP Class A rules (if applicable): Collaborative Continuous Monitoring: CCM-QTR-MTG (Quarterly Review Meeting); Certification Data Sharing: CDS-CSO-PSM (Per-Service Certification Materials); Cryptographic Module Use: CMU-CSO-UVM (Using Validated Cryptographic Modules); FedRAMP Certification: FRC-APP-FIA (Fresh Independent Assessment); Independent Verification and Validation: IVV-CSO-FIA (FedRAMP Independent Assessments); Security Decision Record: SDR-CSX-KMT (Key Security Indicator Metrics); Vulnerability Evaluation and Reporting: VER-TFR-IRI (Internet-Reachable Incidents); Vulnerability Evaluation and Reporting: VER-TFR-MRH (Historical Activity); Vulnerability Evaluation and Reporting: VER-TFR-NRI (Non-Internet-Reachable Incidents).CLA-IVVfailFRC-CLA-IVV fail. Optional Independent Verification and Validation. Providers seeking a FedRAMP Class A Certification MAY have the FedRAMP Certification Package independently verified and validated by a FedRAMP Recognized assessor before submission to FedRAMP.APP-MLFfailFRC-APP-MLF fail. Marketplace Listing First. Providers MUST be listed in the FedRAMP Marketplace before applying for FedRAMP Certification, including: FedRAMP Marketplace: MKT-CSO-MLR (Marketplace Listing Requirements),; FedRAMP Marketplace: MKT-CSO-PML (Provider Marketplace Listing Requests); FedRAMP Marketplace: MKT-IIP-AGU (Agency Use Cases); FedRAMP Marketplace: MKT-IIP-DCP (Demonstrating Continuous Progress).APP-AFCfailFRC-APP-AFC fail. Applying for FedRAMP Certification. Providers MUST complete the FedRAMP Certification Application Form in full to request an initial assessment by FedRAMP.APP-FCPfailFRC-APP-FCP fail. Fresh FedRAMP Certification Package. Providers MUST supply a fresh initial FedRAMP Certification Package that shows the current status of the cloud service offering as verified and validated by the provider within the previous 7 days.APP-FIAfailFRC-APP-FIA fail. Fresh Independent Assessment. Providers seeking Class C Certification MUST supply a fresh initial FedRAMP independent assessment that was completed by a FedRAMP Recognized independent assessment service within the previous 3 months.APP-NTPpassFRC-APP-NTP pass. No Third-Party Applicants. Providers MUST NOT use a third party to apply for a FedRAMP Certification on their behalf; this includes independent assessment services.APP-USAfailFRC-APP-USA fail. Updating Stale Assessments. Providers MAY freshen a stale initial independent verification and validation assessment by having a FedRAMP Recognized independent assessment service review any changes between the original assessment and the current status of the cloud service offering in place of a full re-assessment, UNLESS the stale assessment is more than 9 months old.APS-ATOfailFRC-APS-ATO fail. Agency Authorization to Operate. Providers seeking a FedRAMP Rev5 Agency Certification MUST have completed the Authorization to Operate (ATO) process with their agency sponsor for the cloud service offering, concluding with a formal signed ATO letter that the agency has sent over official government channels to FedRAMP.CCL-UCCfailFRC-CCL-UCC fail. Upgrading Certification Class. Providers MUST apply for a new FedRAMP Certification to upgrade their Certification Class; all applicable requirements MUST be met in advance.CCL-DCCfailFRC-CCL-DCC fail. Downgrading Certification Class. Providers MUST apply for a new FedRAMP Certification to downgrade their Certification Class.CCL-DNPfailFRC-CCL-DNP fail. Downgrade Notification Period. Providers SHOULD notify all necessary parties at least 120 days in advance of an intended downgrade or cancellation of FedRAMP Certification.CSX-VVKfailFRC-CSX-VVK fail. Automated Verification and Validation of Key Security Indicators. Providers seeking 20x Class C Certification MUST implement automated methods to persistently verify and validate the accuracy and completeness of Key Security Indicators with at least 2 automated methods for each Key Security Indicator.CSX-VVRpartialFRC-CSX-VVR partial. Automated Verification and Validation of FedRAMP Rules. Providers seeking 20x Class C Certification SHOULD implement automated methods to persistently verify and validate the accuracy and completeness of the Security Decision Record for FedRAMP rules when applicable.CSX-MASfailFRC-CSX-MAS fail. Application within MAS. Providers SHOULD apply ALL Key Security Indicators to ALL aspects of their cloud service offering that are within the FedRAMP Minimum Assessment Scope.
Incident evaluation and communication
CSO-EFRfailIEC-CSO-EFR fail. Evaluate FedRAMP Reportability. Providers MUST promptly evaluate incidents to determine if they affect confidentiality or integrity of federal customer data or are likely to affect confidentiality or integrity of federal customer data; such incidents are FedRAMP Reportable Incidents and must be reported following the FedRAMP Incident Evaluation and Communication rules.CSO-DPRfailIEC-CSO-DPR fail. Default PAIN Rating. Providers MUST treat FedRAMP Reportable Incidents as if they have a Potential Agency Impact N-rating (PAIN) of 5 UNLESS they promptly estimate the PAIN rating following the rule in IEC-CSO-EFI (Estimate Federal Impact).CSO-IIRfailIEC-CSO-IIR fail. Initial Incident Report. Providers with Class C Certifications MUST responsibly notify all affected parties after identifying FedRAMP Reportable Incidents by providing an Initial Incident Report with as much of the following information that is available at the time of reporting and/or the current relevant status for each item: Contact information for the federal incident response coordinator.; Provider's internally assigned tracking identifier; Description of the incident; Timeline of the incident, including start time, time and source of detection, time of completed FedRAMP Reportable Incident evaluation, and other major incident milestones determined by the provider; Historically and currently estimated Potential Agency Impact N-rating (PAIN) of the incident, including an explanation of the evaluation following the requirements in IEC-CSO-EFI (Estimate Federal Impact) (if applicable); Functional impact to federal agency customers (include impact to confidentiality and/or integrity and the impacted federal customer data types); Estimated recovery plan, milestones, and timelines; List of likely affected customer agencies.CSO-OIRfailIEC-CSO-OIR fail. Ongoing Incident Reports. Providers with Class C Certifications MUST responsibly notify all affected parties of ongoing activity as new information becomes available during incident response for FedRAMP Reportable Incidents, including updates (or lack of updates) to all previously reported information and as much of the following additional information that is available and/or the current relevant status for each item: Observed incident activity; Indicators of compromise; Related Common Vulnerabilities and Exposures (CVE) identifier, if applicable; Root cause; Response and recovery activities.CSO-FIRfailIEC-CSO-FIR fail. Final Incident Report. Providers with Class C Certifications MUST responsibly notify all affected parties by providing a Final Incident Report once the incident has been resolved and recovery is complete, including final updates to all previously reported information.CSO-EFIfailIEC-CSO-EFI fail. Estimate Federal Impact. Providers SHOULD promptly estimate the likely adverse impact of an incident on agency customers to assign a Potential Agency Impact N-rating; this step is called Incident Rating. N1 for a likely minimal customer effect on 1 or more agencies.; N2 for a likely narrow customer effect on 1 or more agencies.; N3 for a likely disruptive customer effect on 1 agency.; N4 for a likely debilitating customer effect on 1 agency or a likely disruptive customer effect on more than 1 agency.; N5 for a likely debilitating customer effect on more than 1 agency..CSO-AIRfailIEC-CSO-AIR fail. Automated Incident Reporting. Providers SHOULD use automation to minimize human intervention in the process of reporting FedRAMP Reportable Incidents to all affected parties.
Independent verification and validation
CSO-FIAfailIVV-CSO-FIA fail. FedRAMP Independent Assessments. Providers with Class C Certifications MUST persistently complete an independent verification and validation assessment of all applicable FedRAMP rules with a FedRAMP Recognized independent assessment service OR FedRAMP at least once per year; this is a FedRAMP independent assessment.CSO-SEIfailIVV-CSO-SEI fail. Supply Evidence of Implementation. Providers MUST supply evidence to all necessary assessors of the implementation of the measures that have been documented to meet FedRAMP Practices; this evidence is the result of verification.CSO-SEEfailIVV-CSO-SEE fail. Supply Evidence of Effectiveness. Providers MUST supply evidence to all necessary assessors of the effectiveness of the measures that have been implemented to meet FedRAMP Practices; this evidence is the result of validation.CSO-ICPfailIVV-CSO-ICP fail. Inclusion in Certification Package. Providers MUST supply the results of FedRAMP independent assessments in their FedRAMP Certification Package without inappropriate modification.CSO-DUSfailIVV-CSO-DUS fail. Document Use of Representative Samples. Providers MUST document and explain the use of representative samples during verification and validation when using representative samples as allowed by IVV-CSO-USR (Use Representative Samples).CSO-STEfailIVV-CSO-STE fail. Supply Technical Explanations. Providers SHOULD supply all necessary assessors with technical explanations, demonstrations, and other relevant supporting information about the technical capabilities they employ to address FedRAMP rules; this SHOULD be supplied as necessary to ensure the assessor can effectively complete verification and validation.CSO-USRfailIVV-CSO-USR fail. Use Representative Samples. Providers MAY use representative samples as appropriate during verification and validation.CSO-RAAfailIVV-CSO-RAA fail. Receiving Assessor Advice. Providers MAY ask for and accept advice from their assessor during assessment regarding techniques and procedures that will improve their security posture or the effectiveness, clarity, and accuracy of their verification, validation and reporting procedures, UNLESS doing so is likely to compromise the objectivity and integrity of the assessment.CSX-AIAfailIVV-CSX-AIA fail. Annual Independent Assessments for 20x. Providers with 20x Class C Certifications MUST include all Key Security Indicators in a FedRAMP independent assessment at least once per year.
Minimum assessment scope
CSO-IIRfailMAS-CSO-IIR fail. Identify Information Resources. Providers MUST identify a set of information resources to assess for FedRAMP Certification that includes all information resources that are likely to handle federal customer data or likely to impact the confidentiality, integrity, or availability of federal customer data handled by the cloud service offering; this set of information resources is the cloud service offering.CSO-FLOfailMAS-CSO-FLO fail. Information Flows and Security Categories. Providers MUST clearly identify, document, and explain information flows and security categories for ALL information resources or sets of information resources in the cloud service offering.CSO-TPRfailMAS-CSO-TPR fail. Third-Party Information Resources. Providers MUST address the potential impact to federal customer data from third-party information resources used by the cloud service offering, ONLY IF MAS-CSO-IIR (Identify Information Resources) APPLIES, by documenting the following information about each applicable third-party information resource: General usage and configuration; Explanation or justification for use; Mitigation measures in place to reduce the potential impact to federal customer data; Compensating controls in place to reduce the potential impact to federal customer data.CSO-MDIfailMAS-CSO-MDI fail. Metadata Inclusion. Providers MUST include metadata (including metadata about federal customer data) in the Minimum Assessment Scope ONLY IF MAS-CSO-IIR (Identify Information Resources) APPLIES.CSO-SUPfailMAS-CSO-SUP fail. Supplemental Information. Providers MAY include additional materials about other information resources that are not part of the cloud service offering in a FedRAMP Certification Package supplement; these resources will not be FedRAMP Certified and MUST be clearly marked and separated from the cloud service offering.
Marketplace listing
CSO-MLRfailMKT-CSO-MLR fail. Marketplace Listing Requirements. Providers MUST address at least these FedRAMP rules to apply for a new FedRAMP Marketplace listing OR to request updates to an existing listing: Certification Data Sharing: CDS-CSO-PUB (Public Information).CSO-PMLfailMKT-CSO-PML fail. Provider Marketplace Listing Requests. Providers MUST notify FedRAMP using the FedRAMP Marketplace Providing Listing Request Form to request a listing in the FedRAMP Marketplace.IIP-AGUfailMKT-IIP-AGU fail. Agency Use Cases. Providers MUST demonstrate that a cloud service offering is intended for one of the following use cases: Direct Use: The product will be used directly by agency customers for integration into a federal information system that falls within the scope of 44 USC § 3506 and will receive an agency Authorization to Operate.; Indirect Use: The product will be included as a third-party information resource in other cloud service offerings that are directly used by agency customers..IIP-DCPfailMKT-IIP-DCP fail. Demonstrating Continuous Progress. Providers MUST demonstrate continuous progress towards a FedRAMP Certification, documented in their Trust Center or website and updated at least quarterly; progress is measured by the provider against documented goals and milestones.IIP-DLAfailMKT-IIP-DLA fail. Deadline for Assessment. Providers MUST demonstrate that an assessment for a FedRAMP Certification Class B, C, or D has been scheduled within 2 years of initial listing in the Initial Implementation Phase.
Secure configuration guide
CSO-RSCfailSCG-CSO-RSC fail. Recommended Secure Configuration. Providers MUST create, maintain, and make available recommendations for securely configuring their cloud services (the Secure Configuration Guide) that includes at least the following information: Required: Instructions on how to securely access, configure, operate, and decommission top-level administrative accounts that control enterprise access to the entire cloud service offering.; Required: Explanations of security-related settings that can be operated only by top-level administrative accounts and their security implications.; Recommended: Explanations of security-related settings that can be operated only by privileged accounts and their security implications..CSO-AUPfailSCG-CSO-AUP fail. Use Instructions. Providers MUST include instructions in the FedRAMP Certification Package that explain how to obtain and use the Secure Configuration Guide.CSO-PUBfailSCG-CSO-PUB fail. Public Secure Configuration Guidance. Providers SHOULD make the Secure Configuration Guide available publicly.CSO-SDFfailSCG-CSO-SDF fail. Secure Defaults. Providers SHOULD set all settings to their recommended secure defaults for top-level administrative accounts and privileged accounts when initially provisioned.ENH-CMPfailSCG-ENH-CMP fail. Comparison Capability. Providers SHOULD offer the capability to compare all current settings for top-level administrative accounts and privileged accounts to the recommended secure defaults.ENH-EXPfailSCG-ENH-EXP fail. Export Capability. Providers SHOULD offer the capability to export all security settings in a machine-readable format.ENH-APIfailSCG-ENH-API fail. API Capability. Providers SHOULD offer the capability to view and adjust security settings via an API or similar capability.ENH-MRGfailSCG-ENH-MRG fail. Machine-Readable Guidance. Providers SHOULD also provide the Secure Configuration Guide in a machine-readable format that can be used by customers or third-party tools to compare against current settings.ENH-VRHfailSCG-ENH-VRH fail. Versioning and Release History. Providers SHOULD provide versioning and a release history for recommended secure default settings for top-level administrative accounts and privileged accounts as they are adjusted over time.
Significant change notification
CSO-EVAfailSCN-CSO-EVA fail. Evaluate Changes. Providers MUST evaluate all potential significant changes to determine the type of significant change and follow the appropriate Significant Change Notification rules. Is it a significant change? --> Continue evaluation and follow the Significant Change Notification rules.; If it is, is it an FedRAMP Certification class change? --> This requires a new assessment and cannot be done under the Significant Change Notification rules.; If it is not, is it a routine recurring change? --> Follow the Routine Recurring Change rules (SCN-RTR Routine Recurring Changes).; If it is not, is it a transformative change? --> Follow the Transformative Change rules (SCN-TRF Transformative Changes).; If it is not, then it is an adaptive change --> Follow the Adaptive Change rules (SCN-ADP Adaptive Changes)..CSO-MARfailSCN-CSO-MAR fail. Maintain Audit Records. Providers MUST maintain auditable records of the significant change evaluation activities required by SCN-CSO-EVA (Evaluate Changes) and make them available to FedRAMP as requested.CSO-INFfailSCN-CSO-INF fail. Required Information. Providers MUST include at least the following information in Significant Change Notifications: Service Offering FedRAMP ID; Assessor Name (if applicable); Related Vulnerability (if applicable); Significant Change type and explanation of categorization; Short description of change; Reason for change; Summary of customer impact, including changes to services and customer configuration responsibilities; Plan and timeline for the change, including for the verification, assessment, and/or validation of impacted Key Security Indicators or Rev5 Controls; Copy of the business or security impact analysis; Name and title of approver.CSO-HISfailSCN-CSO-HIS fail. Historical Notifications. Providers MUST keep 12 months of historical Significant Change Notifications available with their FedRAMP Certification Data.CSO-HRMfailSCN-CSO-HRM fail. Human and Machine-Readable Notifications. Providers MUST make ALL Significant Change Notifications and related audit records available in human-readable and JSON formats.CSO-ARIfailSCN-CSO-ARI fail. Additional Relevant Information. Providers MAY include additional relevant information in Significant Change Notifications.CSO-NOMfailSCN-CSO-NOM fail. Notification Mechanisms. Providers MAY notify necessary parties in a variety of ways as long as the mechanism for notification is clearly documented in the FedRAMP Certification Package and easily accessible.CSO-EMGfailSCN-CSO-EMG fail. Emergency Changes. Providers MAY execute significant changes (including transformative changes) during an emergency or incident without following the Significant Change Notification rules in advance. In such emergencies, providers MUST follow all relevant procedures, notify all necessary parties, retroactively provide all Significant Change Notification materials, and complete appropriate assessment after the incident.ADP-NTFfailSCN-ADP-NTF fail. Notification Requirements. Providers MUST notify all necessary parties within 10 business days after finishing adaptive changes, also including the following information: Summary of any new risks identified and/or vulnerabilities resulting from the change (if applicable).RTR-NNRfailSCN-RTR-NNR fail. No Notification Requirements. Providers SHOULD NOT make formal Significant Change Notifications for routine recurring changes; this type of change is exempted from notification requirements.TRF-NIPfailSCN-TRF-NIP fail. Notification of Initial Plans. Providers MUST notify all necessary parties of initial plans for transformative changes at least 30 business days before starting transformative changes, including a summary of any likely security impacts or changes in risk.TRF-NFPfailSCN-TRF-NFP fail. Notification of Final Plans. Providers MUST notify all necessary parties of final plans for transformative changes at least 10 business days before starting transformative changes, including updates to all previously sent information.TRF-NAFfailSCN-TRF-NAF fail. Notification After Finishing. Providers MUST notify all necessary parties within 5 business days after finishing transformative changes, including updates to all previously sent information.TRF-NAVfailSCN-TRF-NAV fail. Notification After Verification. Providers MUST notify all necessary parties within 5 business days after completing the verification, assessment, and/or validation of transformative changes, also including the following information: Updates to all previously sent information; Summary of any new risks identified and/or vulnerabilities resulting from the change (if applicable); Copy of the security assessment report (if applicable).TRF-UPDfailSCN-TRF-UPD fail. Update Documentation. Providers MUST publish updated service documentation and other materials to reflect transformative changes within 30 business days after finishing transformative changes.TRF-TPRfailSCN-TRF-TPR fail. Third-Party Review. Providers SHOULD engage a third-party assessor to review the scope and impact of the planned change before starting transformative changes if human validation is necessary; such reviews SHOULD be limited to security decisions that require human validation.
Security decision record
CSO-FRRpartialSDR-CSO-FRR partial. FedRAMP Rules. Providers MUST supply a Security Decision Record, in both human-readable and JSON formats, that includes at least all of the following information for each applicable FedRAMP rule: Explanation of how the rule is followed, or an explanation of the reason and resulting risk to customers for not following the rule.; Verification that the implementation is appropriate for the rule, or that the reason for not implementing is accepted by a senior official.; Validation that the implementation is in place and working as intended, or that the reason for not implementing is accepted by a senior official.; Independent verification.; Independent validation.; Any responses or clarifications to the comments in the independent verification or validation.; Rule-specific artifacts (if applicable)..CSO-MTDpassSDR-CSO-MTD pass. Security Decision Record Metadata. Providers MUST also include the following basic metadata in their Security Decision Record: Version; Date and time of last update; Source of update.CSX-KSIpassSDR-CSX-KSI pass. Key Security Indicators. Providers MUST also include short and simple high-level summaries of at least the following for each applicable Key Security Indicator: Explanation of measures (and their objectives) that demonstrate the Key Security Indicator, or an explanation of the reason and resulting risk to customers for not having measures available for that Key Security Indicator.; Explanation of the cycle for any measures that are implemented persistently (if applicable).; Verification that the measures demonstrate the Key Security Indicator, or that the reason for not having them is accepted.; Verification that the automation in place is accurate and sufficient to demonstrate appropriate measures for the Key Security Indicator, or that automation is not necessary for each measure.; Validation that the measures are accurately produced and are in place and working as intended, or that the reason for not having them is valid..CSX-KMTpartialSDR-CSX-KMT partial. Key Security Indicator Metrics. Providers with 20x Class C Certifications MUST also include historical metrics in their Security Decision Record, supplying at least the following information for each applicable Key Security Indicator: Summary of each metric over the past 30 days; Summary of metric up to the past year (where available); All daily metric data (including status of persistent validation) up to the past year (where available).
Vulnerability detection and response
CSO-DETfailVDR-CSO-DET fail. Vulnerability Detection. Providers MUST systematically, persistently, and promptly discover and identify vulnerabilities within their cloud service offering using appropriate techniques such as assessment, scanning, threat intelligence, vulnerability disclosure mechanisms, bug bounties, penetration testing, incident response, automated control testing, supply chain monitoring, and other relevant capabilities; this process is called vulnerability detection. Vulnerability detection includes persistently verifying and validating that information resources and processes are operating as intended and documented for FedRAMP Practices.CSO-RESfailVDR-CSO-RES fail. Vulnerability Response. Providers MUST systematically, persistently, and promptly track, evaluate, monitor, mitigate, remediate, assess exploitation of, report, and otherwise manage all detected vulnerabilities within their cloud service offering; this process is called vulnerability response.CSO-FAVfailVDR-CSO-FAV fail. Failures Are Vulnerabilities. Providers MUST treat problems or failures with their vulnerability detection and response processes as vulnerabilities.CSO-DFRfailVDR-CSO-DFR fail. Design For Resilience. Providers SHOULD make design and architecture decisions for their cloud service offering that mitigate the risk of vulnerabilities by default AND decrease the risk and complexity of vulnerability detection and response.CSO-ADTfailVDR-CSO-ADT fail. Automate Detection. Providers SHOULD use automated services to improve and streamline vulnerability detection and response.CSO-DACfailVDR-CSO-DAC fail. Detect After Changes. Providers SHOULD automatically perform vulnerability detection on representative samples of new or significantly changed information resources.CSO-MSPfailVDR-CSO-MSP fail. Maintain Security. Providers SHOULD NOT weaken the security of information resources to facilitate vulnerability scanning, detection, or assessment activities.CSO-AKEfailVDR-CSO-AKE fail. Avoid KEVs. Providers SHOULD NOT deploy or otherwise activate new machine-based information resources with Known Exploited Vulnerabilities.CSO-SIRfailVDR-CSO-SIR fail. Sampling. Providers MAY sample effectively identical information resources, especially machine-based information resources, when performing vulnerability detection UNLESS doing so would decrease the efficiency or effectiveness of vulnerability detection.TFR-NMVfailVDR-TFR-NMV fail. Non-Machine Verification and Validation. Providers MUST verify and validate the status of non-machine-based information resources at least once every 3 months.TFR-PDDfailVDR-TFR-PDD fail. Persistent Drift Detection. Providers with Class C Certifications SHOULD persistently perform vulnerability detection on all information resources that are likely to drift, at least once every 14 days.TFR-PCDfailVDR-TFR-PCD fail. Persistently Complete Detection. Providers with Class C Certifications SHOULD persistently perform vulnerability detection on all information resources that are NOT likely to drift, at least once every month.TFR-PVRfailVDR-TFR-PVR fail. Mitigation and Remediation Expectations. Providers with Class C Certifications SHOULD partially mitigate vulnerabilities, fully mitigate vulnerabilities, or remediate vulnerabilities to a lower Potential Agency Impact N-rating within the timeframes from evaluation shown below, factoring for the current Potential Agency Impact N-rating as defined in VER-EVA-EPA (Estimate Potential Agency Impact), internet reachability, and likely exploitability:TFR-RMNfailVDR-TFR-RMN fail. Remaining Vulnerabilities. Providers SHOULD mitigate or remediate remaining vulnerabilities during routine operations as determined necessary by the provider.TFR-KEVfailVDR-TFR-KEV fail. Remediate KEVs. Providers SHOULD remediate Known Exploited Vulnerabilities according to the due dates in the CISA Known Exploited Vulnerabilities Catalog (even if the vulnerability has been fully mitigated) as required by CISA Binding Operational Directive (BOD) 26-04 or any successor guidance from CISA.TFR-PSDfailVDR-TFR-PSD fail. Persistent Sample Detection. Providers with Class C Certifications SHOULD persistently perform vulnerability detection on representative samples of similar machine-based information resources, at least once every 3 days.TFR-MVXfailVDR-TFR-MVX fail. Persistent Machine Verification and Validation for 20x. Providers of FedRAMP 20x Class C offerings MUST verify and validate the status of machine-based information resources at least once every 3 days.
Vulnerability evaluation and reporting
EVA-ELXfailVER-EVA-ELX fail. Evaluate Exploitability. Providers MUST evaluate detected vulnerabilities, considering the context of the cloud service offering, to determine if they are likely exploitable vulnerabilities.EVA-EIRfailVER-EVA-EIR fail. Evaluate Internet-Reachability. Providers MUST evaluate detected vulnerabilities, considering the context of the cloud service offering, to determine if they are internet-reachable vulnerabilities.EVA-EPAfailVER-EVA-EPA fail. Estimate Potential Agency Impact. Providers MUST evaluate detected vulnerabilities, considering the context of the cloud service offering, to estimate the likely potential agency impact of exploitation on government customers AND assign one of the following Potential Agency Impact N-ratings (PAIN): N0: Exploitation is extremely unlikely to have any adverse effects on agencies that use the cloud service offering.; N1: Exploitation could be expected to have minimal customer effects on one or more agencies that use the cloud service offering.; N2: Exploitation could be expected to have narrow customer effects on one or more agencies that use the cloud service offering.; N3: Exploitation could be expected to have a disruptive customer effect on one agency that uses the cloud service offering.; N4: Exploitation could be expected to have a debilitating customer effect on one agency that uses the cloud service offering OR a disruptive customer effect on more than one federal agency that uses the cloud service offering.; N5: Exploitation could be expected to have a debilitating customer effect on more than one agency that uses the cloud service offering..EVA-AIAfailVER-EVA-AIA fail. Assume It's Automatable. Providers MUST assume the exploitation of vulnerabilities can be automated UNLESS they have evidence proving otherwise.EVA-GRVfailVER-EVA-GRV fail. Group Vulnerabilities. Providers SHOULD evaluate detected vulnerabilities, considering the context of the cloud service offering, to identify logical groupings of affected information resources that may improve the efficiency and effectiveness of vulnerability response by consolidating further activity; FedRAMP Vulnerability Detection and Response rules are then applied to these consolidated groupings of vulnerabilities instead of each individual detected instance.EVA-EFPfailVER-EVA-EFP fail. Evaluate False Positives. Providers SHOULD evaluate detected vulnerabilities, considering the context of the cloud service offering, to determine if they are false positive vulnerabilities.EVA-EFAfailVER-EVA-EFA fail. Evaluation Factors. Providers SHOULD consider at least the following factors when considering the context of the cloud service offering to evaluate detected vulnerabilities: Criticality: How important are the systems or information that might be impacted by the vulnerability?; Reachability: How might a threat actor reach the vulnerability and how likely is that?; Exploitability: How easy is it for a threat actor to exploit the vulnerability and how likely is that?; Detectability: How easy is it for a threat actor to become aware of the vulnerability and how likely is that?; Prevalence: How much of the cloud service offering is affected by the vulnerability?; Privilege: How much privileged authority or access is granted or can be gained from exploiting the vulnerability?; Proximate Vulnerabilities: How does this vulnerability interact with previously detected vulnerabilities, especially partially or fully mitigated vulnerabilities?; Known Threats: How might already known threats leverage the vulnerability and how likely is that?.RPT-PERfailVER-RPT-PER fail. Persistent Reporting. Providers MUST report vulnerability detection and response activity (including persistent verification and validation) to all necessary parties persistently, summarizing ALL activity since the previous report; these reports are FedRAMP Certification Data and are subject to FedRAMP Certification Data Sharing rules.RPT-VDTfailVER-RPT-VDT fail. Vulnerability Details. Providers MUST include the following information (if applicable) on detected vulnerabilities when reporting on vulnerability detection and response activity, UNLESS it is an accepted vulnerability: Provider's internally assigned tracking identifier; Time and source of the detection; Time of completed evaluation; Is it an internet-reachable vulnerability or not?; Is it a likely exploitable vulnerability or not?; Historically and currently estimated Potential Agency Impact N-rating of exploitation; Time and Potential Agency Impact N-rating of each completed and evaluated reduction in Potential Agency Impact N-rating; Estimated time and target Potential Agency Impact N-rating of next reduction in Potential Agency Impact N-rating; Is it currently or is it likely to become an overdue vulnerability or not? If so, explain.; Any supplementary information the provider responsibly determines will help federal agencies assess or mitigate the risk to their federal customer data within the cloud service offering resulting from the vulnerability; Final disposition of the vulnerability.RPT-AVIfailVER-RPT-AVI fail. Accepted Vulnerability Info. Providers MUST include the following information on accepted vulnerabilities when reporting on vulnerability detection and response activity: Provider's internally assigned tracking identifier; Time and source of the detection; Time of completed evaluation; Is it an internet-reachable vulnerability or not?; Is it a likely exploitable vulnerability or not?; Currently estimated Potential Agency Impact N-rating; Explanation of why this is an accepted vulnerability; Any supplementary information the provider determines will responsibly help federal agencies assess or mitigate the risk to their federal customer data within the cloud service offering resulting from the accepted vulnerability.RPT-NIDfailVER-RPT-NID fail. Responsible Disclosure. Providers MUST NOT irresponsibly disclose specific sensitive information about vulnerabilities that would likely lead to exploitation, but MUST disclose sufficient information for informed risk-based decision-making to all necessary parties.RPT-HLOfailVER-RPT-HLO fail. High-Level Overviews. Providers SHOULD include high-level overviews of ALL vulnerability detection and response activities conducted during this period for the cloud service offering; this includes vulnerability disclosure programs, bug bounty programs, penetration testing, assessments, etc.RPT-RPDfailVER-RPT-RPD fail. Responsible Public Disclosure. Providers MAY responsibly disclose vulnerabilities publicly or with other parties if the provider determines doing so will NOT likely lead to exploitation.TFR-MHRfailVER-TFR-MHR fail. Monthly Activity Report. Providers MUST report vulnerability detection and response activity to all necessary parties in a consistent format that is human readable at least monthly.TFR-MAVfailVER-TFR-MAV fail. Mark Accepted Vulnerabilities. Providers MUST categorize any vulnerability that is not or will not be fully mitigated or remediated within 192 days of evaluation as an accepted vulnerability.TFR-MRHfailVER-TFR-MRH fail. Historical Activity. Providers with Class C Certifications SHOULD make all recent historical vulnerability detection and response activity available in JSON format for automated retrieval by all necessary parties (e.g. using an API service or similar); this information SHOULD be updated persistently, at least once every 14 days.TFR-EVUfailVER-TFR-EVU fail. Evaluate Vulnerabilities Quickly. Providers with Class C Certifications SHOULD evaluate ALL vulnerabilities as required by VER-EVA (Evaluation) within 5 days of detection.TFR-IRIfailVER-TFR-IRI fail. Internet-Reachable Incidents. Providers with Class C Certifications SHOULD treat internet-reachable likely exploitable vulnerabilities where Potential Agency Impact N-rating > 3 as a FedRAMP Reportable Incident until they are partially mitigated vulnerabilities at N3 or below.TFR-NRIfailVER-TFR-NRI fail. Non-Internet-Reachable Incidents. Providers with Class C Certifications MAY treat likely exploitable vulnerabilities that are NOT internet-reachable where Potential Agency Impact N-rating = 5 as a FedRAMP Reportable Incident until they are partially mitigated vulnerabilities at N4 or below.
Certification package
Machine-readable
System info
Current scores
Day list
Rules
Documents
Security decision record
Report date
Last updated . Public certification files on this site can be read without signing in.