FedRAMPFedRAMPCommunity
← All weekly editions

From written rules to working systems

Monday, Sep 21, 2026 · Covers Sep 14, 2026–Sep 20, 2026 · Eastern Time

This week’s exchanges turn to interoperability, useful records and the boundary between future direction and current requirements.

Reconstructed prototype edition. Sources captured October 4; later replies are excluded from this week’s activity. Source wording may reflect edits made after the week ended.

JSON needs to be usable, too

A provider describes a public JSON delivery problem. The exchange explores the gap between schema-valid content and access from ordinary web applications, and acknowledges a need for clearer written expectations.

Keep the implementation concern and the proposed next steps distinct. The discussion itself does not establish that a proposed rule change has been published.

Make the source of an update identifiable

A question on the Certification Package Overview page asks how specific update attribution should be. The response describes flexibility for people, teams and automated systems.

This is useful implementation context to read alongside CPO-CSO-MTD, especially when designing automated records.

An assessor discussion about what comes next

A response following the assessor meeting explicitly describes future recognition expectations as advance context, not an official rule at that time.

Future direction can inform preparation without being mistaken for an effective requirement.

A small question about document size

A page-specific question about certification data sharing receives a practical answer: count the document, rather than constructing a special count of selected body text.

Small implementation questions can have reusable answers. The direct comment makes this easier to find than a long thread title.

A contributor checks the result

A participant follows up on the incident-evaluation page to confirm seeing the announced correction in the updated material.

This exchange provides a documented link from a report to a response and subsequent confirmation, rather than an assumed causal connection.

Meetings & recordings

Assessor and Advisor Community Update · Sep 16, 2026

Watch: Assessor and Advisor Community Update · Recording ↗

Recording dates refer to the meeting; upload dates were not supplied.

Also published this week

Across the other channels

No new items were captured this week for Blogs, Notices. Their earlier material remains available in the channel guide.

Explore all channels →

Looking ahead from this edition

Agency Support Group Meeting · Sep 23, 2026

A separate preview of the following week, based on the saved event schedule.

The complete captured week

Publications, meetings, new discussions, comments and edits. Short acknowledgments remain here even when they are not featured in the editorial summary.

Browse all 62 captured records

62 captured records

  1. RFC-0033 FedRAMP 20x Phase 4 Development Tracks for 20x Class D ↗

    Comment · @Santoshkumarpuppala · Community discussions

  2. Class ↗

    Comment · @LPT00-ctrl · CR26 page discussions

  3. Marketplace listing ↗

    Reply · @pete-gov · CR26 page discussions

  4. Marketplace listing ↗

    Comment · @williamaolson-dev · CR26 page discussions

  5. General Discussion on RFC-0033 (Phase 4) and RFC-0034 (TAG) ↗

    Reply · @pete-gov · Community discussions

  6. General Discussion on RFC-0033 (Phase 4) and RFC-0034 (TAG) ↗

    Comment · @bennett2606 · Community discussions

  7. RFC-0033 FedRAMP 20x Phase 4 Development Tracks for 20x Class D ↗

    Reply · @bennett2606 · Community discussions

  8. FRC-CSX-VVK - How does FedRAMP interpret "Automated Methods" for KSI Validation ↗

    Discussion opened · @jdettweiler · Community discussions

  9. Significant change notification ↗

    Reply · @pete-gov · CR26 page discussions

  10. Significant change notification ↗

    Comment · @williamaolson-dev · CR26 page discussions

  11. RFC-0033 FedRAMP 20x Phase 4 Development Tracks for 20x Class D ↗

    Comment · @bennett2606 · Community discussions

  12. Certification package overview ↗

    Reply · @pete-gov · CR26 page discussions

  13. Certification package overview ↗

    Comment · @VSQ22022 · CR26 page discussions

  14. Rules ↗

    Reply · @pete-gov · CR26 page discussions

  15. FedRAMP 3PAO Status Implications ↗

    Comment · @pete-gov · CR26 page discussions

  16. Rules ↗

    Reply · @ul7 · CR26 page discussions

  17. Rules ↗

    Comment · @ul7 · CR26 page discussions

  18. FedRAMP 3PAO Status Implications ↗

    Discussion opened · @khanssen · CR26 page discussions

  19. Does FedRAMP consider quantum vulnerable cryptography a vulnerability? ↗

    Comment · @sunstonesecure-robert · Community discussions

  20. RFC-0033 FedRAMP 20x Phase 4 Development Tracks for 20x Class D ↗

    Comment edited · @sunstonesecure-robert · Community discussions

  21. RFC-0033 FedRAMP 20x Phase 4 Development Tracks for 20x Class D ↗

    Reply · @sunstonesecure-robert · Community discussions

  22. Vulnerability detection and response ↗

    Reply · @pete-gov · CR26 page discussions

  23. Does FedRAMP consider quantum vulnerable cryptography a vulnerability? ↗

    Discussion opened · @robgil · Community discussions

  24. Vulnerability detection and response ↗

    Comment · @walkawaze · CR26 page discussions

  25. Oops! New Assessor Meeting Link for TODAY ↗

    Comment · @pete-gov · Community discussions

  26. Oops! New Assessor Meeting Link for TODAY ↗

    Discussion opened · @emu-gov · Community discussions

  27. Assessor and Advisor Community Update ↗

    Meeting / recording · FedRAMP · Events

  28. Assessor and Advisor Community Update · Recording ↗

    Meeting / recording · FedRAMP · Recordings

  29. Incident evaluation and communication ↗

    Comment edited · @tnnrjmsn-eit · CR26 page discussions

  30. Incident evaluation and communication ↗

    Reply · @tnnrjmsn-eit · CR26 page discussions

  31. RFC-0034 Technical Advisory Group Changes ↗

    Comment · @cb-axon · Community discussions

  32. Agency use ↗

    Reply · @mgcas-roxanne · CR26 page discussions

  33. Certification data sharing ↗

    Reply · @pete-gov · CR26 page discussions