HALO's 20x Phase 2 pilot proposal: every Key Security Indicator as a ticket, with a goal of checks every three days or sooner
In a January 2026 FedRAMP video, HALO presented HALO GRC for the 20x Moderate pilot, saying its automated checks covered about 70% of Key Security Indicators. The FedRAMP Marketplace now lists Halo as FedRAMP Certified, Class C (Moderate).
By FedXchange ·
Play the video: FedRAMP 20x Phase 2 Pilot Proposal: HALOOn January 13, 2026, the Federal Risk and Authorization Management Program (FedRAMP) posted a recording of HALO's pilot proposal for FedRAMP 20x Phase 2. FedRAMP 20x is FedRAMP's newer process, built on Key Security Indicators (KSIs) and automated evidence. Phase 2 was a pilot at the Moderate impact level.
FedRAMP asked cloud service providers to apply for Phase 2 with a pilot proposal, and it posted recordings of the proposals on YouTube. Its December 10, 2025 announcement said FedRAMP would review proposals from January 5 to 9, 2026, and choose up to seven more participants.
The video came out before FedRAMP issued the FedRAMP Consolidated Rules for 2026. At the time, the speakers used "authorization." The current terms are "FedRAMP Certification" and "FedRAMP Certified," as the FedRAMP Marketplace and FedRAMP's What's Changing in 2026 page show.
In short:
- What HALO said. HALO GRC is a governance, risk, and compliance (GRC) workflow tool built for managed service providers. HALO uses it to track each KSI as a ticket. Its presenter said its library of automated checks covered about 70% of the KSIs.
- What FedRAMP asked. FedRAMP staff asked how HALO would track metrics over time instead of yes-or-no answers, and how it would cover information resources that are not machines, such as people and finances.
- Who it matters to. In our view, cloud service providers planning a 20x Certification, and agency staff who review their evidence.
- What happened next. The FedRAMP Marketplace lists Halo as FedRAMP Certified, Class C (Moderate), type "20x Pilot," since May 6, 2026.
Source: FedRAMP 20x Phase 2 Pilot Proposal: HALO (FedRAMP video, January 13, 2026). This is how HALO described its approach, not a FedRAMP rule.
Read the steps as text
- Queries as code. Steampipe queries, kept in GitHub and mapped to the technical KSIs, read the configuration of the infrastructure.
- Automation. Automations format the results and send them to HALO GRC through its application programming interface (API).
- KSI ticket. Each KSI has its own ticket, with a validation table that records the pass count, the fail count, and a status.
- Three-day check. A service-level target, to be set to three days, turns red when a KSI gets no new submission in time.
- Failure. HALO planned to turn a failed KSI into an issue with a deadline, assigned to the person who must fix it.
- Sharing. Agencies see KSI reports in a portal, limited by role, or pull them through the API.
How did HALO plan to meet the Phase 2 requirements?
HALO's presenter said HALO GRC is a multi-tenant platform designed for managed service providers. In this case, agencies act as the managed service provider. HALO already used it for its Revision 5 managed services and was adding 20x alongside.
The presenter said everything is a ticket. Each ticket has a status, an owner, and a full history, including conversations between people about a KSI. The KSI checks run as Steampipe queries stored in GitHub. About 30% of the KSIs were not yet automated. The presenter said those would be manual submissions every three months for now, and named cybersecurity training as an example to automate later.
The presenter walked through other Phase 2 areas:
- Vulnerabilities. Vulnerability data, such as alerts, is put into FedRAMP's formats. HALO adds threat information from outside feeds, such as an Exploit Prediction Scoring System (EPSS) score and whether a system can be reached from the internet. A daily check compares HALO's findings with the Known Exploited Vulnerabilities catalog from the Cybersecurity and Infrastructure Security Agency (CISA).
- Changes. Change requests, including significant changes, are tracked in HALO. Each change request lists the system's points of contact, who are notified. When a change becomes a significant change, the agencies and others who must be told are notified automatically.
- The FedRAMP security inbox. Email from FedRAMP becomes a ticket with a one-hour response target.
- Secure configuration. HALO GRC runs more than 30 configuration checks and warns administrators at sign-in.
- Encryption. The presenter said HALO uses strong encryption, but must still move to Federal Information Processing Standards (FIPS) mode and modules validated by the Cryptographic Module Validation Program (CMVP).
The presenter also named gaps: HALO still had to decide what counts as a pass or a failure for each KSI.
How would HALO's assessor check the automation?
HALO's third-party assessment organization (3PAO) described four goals and eight steps. The assessor said it would review documents, interview staff, get read-only access to all repositories and system assets it needs, and watch the automation run. It would check that the automation covers every component where required, test how HALO handles failures, and do some manual testing. It would give findings without an authorization recommendation.
The assessor said, in words from the video:
"We're going to validate that whatever is provided to us in an automated fashion is accurate." — HALO's assessor
A FedRAMP staff member praised that plan, in words from the video:
"you get a big shout out for testing failure handling" — FedRAMP staff member
What did FedRAMP ask HALO?
Metrics over time. A FedRAMP staff member said Phase 1, which focused on Low impact systems, leaned on yes-or-no answers. For Moderate, FedRAMP wanted depth: tracking activities and outcomes for each KSI over time, such as the minutes it takes to notify FedRAMP of an incident. HALO's presenter said tracking all work as tickets gives HALO the data. The next step is to turn that data into success measures. The presenter added that a Model Context Protocol (MCP) server inside the boundary lets staff ask questions of the database in plain language.
How often to validate. A FedRAMP staff member said three days is the longest allowed between validations, and that FedRAMP would expect stretch goals shorter than three days where appropriate. HALO's presenter said the goal is daily, so a failure leaves time to recover:
"So for a three-day window, we want to hit one day if not more." — HALO presenter
Information resources that are not machines. A FedRAMP staff member said some KSIs apply to all information resources, which can include people, finances, facilities, and locations. HALO said it would use data requests: scheduled tickets, tagged to a KSI, that a person answers. For annual security training, HALO would track each person's completion and phishing results.
What does this mean for agencies and cloud providers now?
The pilot is over. FedRAMP's 20x page says Phase 2 ran from November 18, 2025, through March 2026 and received 14 qualifying submissions. The FedRAMP Consolidated Rules for 2026 open 20x Certification Classes A through C. Providers could adopt them from July 4, 2026, and they become mandatory for all FedRAMP stakeholders on January 1, 2027.
Sources
- FedXchange tracker: FedRAMP 20x Phase 2 Pilot Proposal: HALO (January 13, 2026)
- YouTube: FedRAMP 20x Phase 2 Pilot Proposal: HALO
- FedRAMP: Announcing the initial 20x Phase 2 pilot participants and FedRAMP's next steps
- FedRAMP: FedRAMP 20x
- FedRAMP Marketplace: Halo
- FedRAMP: What's Changing in 2026
- FedXchange tracker: FedRAMP Consolidated Rules for 2026
- CISA: Known Exploited Vulnerabilities catalog
Get new posts and federal governance by email
A weekly email on Fridays, an alert on the day the watch finds something new, or both. Free.