Johann Dettweiler | CISO, stackArmor
FedRAMP 20x, CR26, VDR, VER and the Rev. 5 transition can complicate your 2027 software roadmap. See how The Armory on Google Cloud helps teams plan around an established foundation and ongoing compliance operations.
The Armory brings the foundation and the ongoing operating work into the same delivery conversation.
The short answer. The Armory is stackArmor’s General Support System on Google Cloud, bringing together cloud infrastructure, security operations, compliance workflows, and applicable inherited controls. Its FedRAMP Marketplace listing identifies it as a Rev5 Agency, Class D (High) offering. For software providers planning federal delivery in 2027, that means starting with a reusable foundation and a simpler set of tasks to worry about focused on their application code.
For software providers evaluating FedRAMP 20x and federal delivery in 2027, the first decision is not simply which rule changes next. It is how to build an authorization and operating plan that keeps the application roadmap moving. The Armory provides a starting point for that conversation.
Your 2027 roadmap probably has a few things on it that matter: a capability an agency has been asking for, a better experience for the people using your product, perhaps the release that finally turns a promising pilot into something mission partners can depend on.
Then somebody opens the FedRAMP conversation. Twenty minutes later, the roadmap is buried under 20x, VDR, VER, CR26, and a debate about what “Rev. 5 retirement” actually means. Happy New Year. Your first deliverable appears to be a new acronym decoder.
Let’s give that meeting a better ending. The Armory on Google Cloud gives software providers a place to start from work already done: an established cloud foundation, security and compliance operating capabilities, and experienced people. The opportunity is to spend more of your effort on the application that brought you to the federal market in the first place.
FedRAMP High infrastructure: Build on a secure foundation
There is no special prize for rebuilding the same security foundation before you can deliver something useful. The Armory was built to make that foundation reusable. Its FedRAMP High authorization brings a common framework and applicable inherited controls to software providers deploying cloud-native, containerized, or virtual-machine-based applications on Google Cloud.
Inheritance has a practical purpose: it lets the team distinguish work already implemented in the supporting environment from work that belongs to its own application. That is a much more productive starting point for an architecture discussion than a blank page and a promise to figure out compliance later.
Underneath that approach, Google Cloud Assured Workloads provides controls for supported compliance boundaries, such as data location and access restrictions. The applicable control package, services, and configuration still matter. The Armory puts that foundation to work through deployment services, documentation support, continuous monitoring, and hosted or managed approaches matched to the provider’s needs.
The Armory combines reusable platform capabilities with operating support. Inclusion and ownership depend on the engagement.
FedRAMP 20x, CR26, VDR and VER: What changes in 2027?
These terms describe different parts of the job. FedRAMP 20x concerns the certification approach. CR26 is the consolidated rules framework that spans both 20x and legacy Rev5 offerings. VDR and VER address the ongoing work of finding, responding to, evaluating, and reporting vulnerabilities. Treating them as one giant migration obscures the decisions your team actually needs to make.
Definitions and schedules: FedRAMP 20x · VDR · VER · CR26 timeline. Confirm applicability to your offering.
The dates deserve precision, too. FedRAMP’s published schedules set December 7, 2026 as the VDR/VER adoption date and March 7, 2027 as the end of the existing-certification grace period, with a corrective action plan required when adoption is missed. The general January 1, 2027 CR26 milestone does not erase ruleset-specific dates or applicability. Check the CR26 timeline and the schedules for Rev5 or 20x against your offering.
And June 11, 2027 is a cutoff for new Rev5 efforts to have a complete package that meets the applicable CR26 requirements already in active FedRAMP PMO review, generally with an active agency ATO, subject to the stated exception. It is a specific entry milestone; existing Rev5 authorizations do not all expire that day. FedRAMP has said it expects to outline the broader Rev5 transition paths and timelines by the end of FY2027.
That changes the planning conversation. Identify your path, your operating obligations, and the evidence you must maintain. Then decide how much of the foundation you really need to build yourself.
Explore The Armory: Armory on Google Cloud
Planning a 2027 federal software release? Talk through your application boundary, applicable FedRAMP path, and operating responsibilities in an Armory briefing. Request an Armory briefing
FedRAMP continuous monitoring: The real test comes after authorization
An authorization milestone matters. So does the ordinary Tuesday that follows it, when a new vulnerability affects a component you use, the fix belongs to a vendor, and an agency needs to understand its exposure. Your architecture diagram is useful. Your operating process is about to become essential.
The Armory’s capabilities include vulnerability scanning, security logging and analysis, endpoint protection, access management, and continuous monitoring. Armory SecOps adds managed monitoring, threat detection, security visibility, and response capabilities within the High-authorized environment. The right combination depends on the workload and the agreed service scope.
This is where VDR and VER become real work. A finding needs to be connected to the affected component, the workload it supports, the exposure it creates, and the response somebody owns. A reviewer should be able to understand the mitigation, the approval, and what remains to be fixed.
We have published an example of that vulnerability workflow: evaluating exposure and exploitability, documenting mitigation, separating submission from approval, and keeping the finding open until the lasting fix is deployed. Those connected records support vulnerability evaluation and reporting. They also help the next person make a better decision without reconstructing the entire story from email.
That is the kind of operational substance worth asking a platform provider to show you. A changing rule should enter a process with owners, evidence, and a clear next action.
The next acronym should not get a veto over your roadmap.
Compliance automation: Put the operating model behind the AI
“We use AI” has become an extremely easy sentence to put on a website. The harder questions are operational. What job is the agent doing? Which system is it working on? What procedures can it use? Who gets to approve the result? And can you inspect what actually happened?
Inside The Armory, stackArmor’s published compliance automation model connects Task Definition → Playbook → Runbook → Profile → Skill. Those components define the job, the organization’s process, the execution steps, the system in scope, and the maintained procedure available to the agent. They give recurring work a structure that can be examined and improved.
The published example also distinguishes deterministic assessment results from AI-assisted explanation, retains workflow evidence, and keeps human review and decisions explicit. That is a more useful conversation about AI in compliance: the record remains inspectable, and authority remains assigned.
Imagine the question a customer will eventually ask: “Why did you reach this conclusion?” The answer should lead back to a defined requirement, relevant evidence, the work performed, and a responsible reviewer. If a rule changes, that chain gives the team somewhere concrete to investigate. If an assessment finds a gap, it gives the team somewhere concrete to act.
That is why the platform, the operating process, and the people belong in the same conversation. The cloud environment is where the application runs. The operating model is how the work keeps getting done.
Inherited controls and shared responsibility: Make ownership clear
Using The Armory does not automatically authorize your application. Your team remains accountable for its application—including its code, dependencies, images, and configuration. The engagement should identify who performs each security and remediation task, what evidence each party supplies, and the authorization or agency-use path the offering must follow.
That clarity is a benefit. It lets engineering plan around a defined boundary, security work with named owners, and leadership understand what still stands between the product and its intended mission. Google’s shared-responsibility guidance reinforces why configuration and workload requirements matter; the Armory engagement should turn those principles into responsibilities for your particular deployment.
Hosting and control inheritance support the application’s path; they do not automatically authorize the application.
Bring the difficult questions to the first conversation: which services fit the boundary, which controls are inherited, who changes the application, and what evidence each party supplies. A useful platform discussion ends with clearer ownership and a better next decision.
Your 2027 federal software roadmap should serve the mission
The federal market will keep changing. Your mission partners will keep needing software that solves real problems. A good 2027 plan has room for both realities.
The Armory on Google Cloud brings an established foundation, security operations, and accountable compliance workflows into that plan. Start with what can be reused. Assign the work that remains. Give your team a practical way to keep moving as the requirements evolve.
Then make the New Year’s resolution worth keeping: bring great software to the people doing the mission.
What could your team ship with a stronger starting point?
Bring your architecture, intended agency use, current authorization status, and 2027 delivery goal. Let’s discuss where The Armory can support your environment, which responsibilities your team retains, and the next steps for your path.
The Armory and FedRAMP: common questions
What is The Armory on Google Cloud?
The Armory is stackArmor’s General Support System on Google Cloud. It combines a reusable cloud foundation with security and compliance operating capabilities. Its current FedRAMP Marketplace profile is Rev5 Agency, Class D (High).
Does The Armory automatically authorize my application?
No. Applicable inherited controls can support your path, but the application’s boundary, responsibilities, evidence, and required authorization or agency-use decisions must still be addressed. Workload and service scope determine what can be reused.
How does The Armory help with VDR, VER, and CR26?
The Armory brings vulnerability management, continuous monitoring, compliance workflows, and retained evidence into an operating environment. Those capabilities can support the work required by the applicable rules. Confirm the requirements, reporting duties, and service responsibilities for your particular offering.
What should I bring to an Armory briefing?
Bring a high-level architecture, the agencies and use cases you intend to support, your current authorization status, and your delivery priorities. Use the conversation to explore control inheritance, workload gaps, ownership, and next steps.
Program details and product status checked November 19, 2026. Follow current FedRAMP guidance for the rules, dates, and certification path applicable to your offering.