Merge pull request #926 from GSA/sa-focusing-on-delivery-blog-1

focusing on delivery blog

_posts/2025-01-17-focusing-on-delivery.md

@@ -0,0 +1,39 @@
+---
+title: Focusing on Delivery 
+permalink: /2025-01-17-focusing-on-delivery/
+body-class: page-blog
+image: /assets/img/blog-images/2025-01-16-focusing-on-delivery.png
+author: FedRAMP
+layout: blog-page
+---
+
+FedRAMP has shifted to a more aggressive cadence for releasing draft updates for policies and directives. We expect to see [Requests for Comment (RFC)](https://www.fedramp.gov/rfcs) become a routine activity with multiple RFCs open at any given time as FedRAMP continuously works to improve. We’ve also added a [Policy and Guidance Updates page](https://www.fedramp.gov/updates/policy-and-guidance/) to our website that reflects the current status of policy and guidance that we’re working on.
+
+<p style="margin-top: 22px; margin-bottom: 0rem; padding-left:32px;">
+<b><a href="https://www.fedramp.gov/updates/docs/cryptographic-module/" target="_blank" rel="noopener noreferrer">FedRAMP Cryptographic Module Selection and Use Policy</a></b></p>
+<p style="margin-top: 22px; margin-bottom: 0rem; padding-left:32px;">This new policy takes a risk-based approach to navigating competing requirements for the use of FIPS-140 validated cryptographic modules by prioritizing the application of updates to remediate known vulnerabilities that can pose immediate risk to federal information. This policy was approved by the FedRAMP Board and published on January 16, 2025.</p>
+
+<p style="margin-top: 22px; margin-bottom: 0rem; padding-left:32px;">
+<b><a href="https://www.fedramp.gov/updates/rfcs/0004" target="_blank" rel="noopener noreferrer">FedRAMP Boundary Policy</a></b> (draft, request for comment)</p>
+<p style="margin-top: 22px; margin-bottom: 0rem; padding-left:32px;">The draft policy defines the FedRAMP boundary as all services that handle federal information and/or directly impact the confidentiality, integrity, or availability of federal information. It also limits the scope of the FedRAMP boundary to reduce listing of duplication or ancillary services. This draft policy was released for public comment on January 16, 2025.</p> 
+
+<p><a class="auth-resources-download1"  href="https://www.fedramp.gov/updates/rfcs/" target="_blank">Learn more and comment on our open FedRAMP RFCs</a></p>
+
+All priority FedRAMP initiatives now have dedicated sections on our website in the Updates & Priorities menu that will be updated regularly. We’ve also created a simple Changelog Page that we’ll continue to maintain as initiatives advance, announcements are made, or other significant changes happen within the program. 
+
+<p><a class="auth-resources-download1"  href="https://www.fedramp.gov/updates/changelog/" target="_blank">Bookmark https://www.fedramp.gov/updates/changelog/</a></p>
+
+FedRAMP’s developer team is hard at work enhancing the data, documentation, and tools to make digital authorization package submissions with [the FedRAMP Platform](https://www.fedramp.gov/2024-09-03-the-missing-piece-of-our-modernization-puzzle-the-fedramp-platform/) possible. The team runs several industry engagement touchpoints, including bi-weekly OSCAL Implementers meetings for [the Digital Authorization Pilot](https://www.fedramp.gov/updates/pilots/digital-authorization-package/); monthly briefings on all the automation initiatives; ad-hoc office hour sessions with developers; and troubleshoots real-time GitHub requests from the developer community.
+
+<p><a class="auth-resources-download1"  href="https://www.fedramp.gov/updates/pilots/digital-authorization-package/" target="_blank">Sign up to participate</a></p>
+
+<h3>In case you missed it</h3>
+Operating in the open with a focus on delivery means we’ve been publishing some key content (even over the holidays!) as quickly as possible without a lot of fanfare. That’s why we want to highlight our new [Requests for Comment (RFC) landing page](https://www.fedramp.gov/updates/rfcs/) and all the activity happening around our work towards improving FedRAMP policies and directives. We need your insight to ensure our changes have the greatest benefit with the least operational impact. Here’s what you can review and comment on today:
+
+- [Exploring new ways to scale FedRAMP](https://www.fedramp.gov/2024-12-20-exploring-new-ways-to-scale-fedramp/) - an opening discussion on charging industry fees to consistently scale and improve the quality of FedRAMP services based demand.
+- [RFC0001: A New Comment Process for FedRAMP](https://www.fedramp.gov/updates/rfcs/0001/) - we’re piloting the use of informal discussion forums in addition to the more formal letter-style submission process.
+- [RFC0002: Proposed Revisions to FedRAMP 3PAO Requirements](https://www.fedramp.gov/updates/rfcs/0002/) - we listened to a bunch of pain points from independent assessors and are proposing changes to address them. Are we on the right track?
+- [RFC0003: Review Initiation Checks (RICs)](https://www.fedramp.gov/updates/rfcs/0003/) - if a CSP had a (relatively) simple checklist they could follow to likely receive FedRAMP authorization on the first review… would they use it? You tell us.
+- [RFC0004: Boundary Policy](https://www.fedramp.gov/updates/rfcs/0004) - the most frequently requested policy update is out for the first of what is likely to be multiple rounds of comment to ensure we can get this right.
+
+Want to share your thoughts and experiences on something else? You can always reach out directly to the FedRAMP Director at [[email protected]](mailto:[email protected]) with a note or ask to schedule a chat.

_sass/_pages.scss

@@ -966,6 +966,25 @@ ol.training-step-sub {
 	}
 	}
 
+.auth-resources-download1 {
+	border-radius: 20px;
+	border: solid 1px $dark-gray;
+	padding: 4px 14px;
+	text-decoration: none;
+	cursor: pointer;
+	font-weight: 800;
+	cursor: pointer;
+
+	&:visited {
+		color: $mid-gray;
+	}
+
+	&:hover {
+		color: $red;
+		border: solid 1px $red;
+	}
+	}
+
 .training-sign-up.no-line {
 		border-bottom: none;
 	}
@@ -1325,4 +1344,4 @@ blockquote {
 	box-shadow: -2px 0 0 $lighter-teal,
 		-4px 0 0 lighten($lighter-teal, 40%),
 		-7px 0 0 $lighter-teal;
-}
+}