FedRAMP RFI responsesAll questions

What questions do you have for the Government on the draft PWS? Please identify the specific section(s) if applicable.

Summary of responses

Recurring questions concern package volumes, review scope, supplied tools, staffing, access, and conflicts of interest. Several submissions offer acquisition or pricing proposals; eight provide no questions or answer N/A.

  • Assurit and Prudent favor small-business set-asides; Noblis favors full and open competition.
  • Navira proposes monthly management, per-review pricing, and surge labor; EY proposes performance-based fixed-price delivery.
  • TES, Excentium, and IBSS ask about the boundaries between package review, assessment, and testing.

Advanced Cybersecurity Experts, LLC (ACE)

AI comparisonLike RADIX, requests an automation role alongside workload and staffing details; its acquisition proposal specifies an SDVOSB set-aside.

1. Section 3.3. Which tools, schemas, APIs, and dashboards will the Government furnish? May the contractor build and maintain review scripts once the Government approves them? 2. Sections 5.0 and 6.0. Will you add an Automation / Data Engineer labor category? PWS 3.3 calls machine-readable review core work, and Section 6 names an Automation Lead. No labor category covers it today. 3. Section 7.0. Can you share expected package volume per year? A split by Class (A to D) and by Rev5 vs 20x would help offerors size teams and price. 4. Section 8.0. What share of staff must be on site, and how often? Will you allow hybrid work for reviewer and automation roles? 5. Section 9.0. How long an overlap with the current task order, 47QPCA24F0015, do you plan before it ends on 01/29/2027? 6. Section 10.0. What background check level, PIV, and Government devices will staff need? How long does onboarding take today? 7. Section 11.0. Will 3PAOs and firms that advise cloud providers be barred, or allowed with a mitigation plan? 8. Section 13.0. Will cycle-time standards differ by package Class? 9. Set-aside. Will GSA set this order aside for Service-Disabled Veteran-Owned Small Businesses (SDVOSB) under SIN 54151HACS? ACE asks that it do so. ACE is an SBA-certified SDVOSB on GSA MAS 47QTCA24D0082. Many HACS SDVOSBs do this work, so the Rule of Two can be met. A set-aside also counts toward GSA's SDVOSB goals.

ACE will gladly walk the FedRAMP team through how we test a KSI, end to end, at no cost.

Armavel LLC

AI comparisonShares ACE’s workload, staffing-location, and tool questions, focusing on surge demand, DC positions, and approved AI tools.

Can you please distinguish expected steady-state workload from maximum surge demand and identify any available historical review-effort data? Can you please clarify which positions must be DC-based? Regarding super-intelligence tools, can you please specify approved platforms and permitted use cases?

Assurit

AI comparisonShares Prudent’s preference for a small-business set-aside and broader comparable experience; also proposes fewer key-personnel requirements.

1. Set-aside: We recommend a total small business set-aside under SIN 54151HACS. Assurit is an 8(a) small disadvantaged business holding this SIN (GSA MAS 47QTCA18D00JZ). Small firms without cloud service provider or assessor business carry lower conflict-of-interest risk. 2. Contract type and surge (3.8, 7.0): Please state the contract type and how surge is ordered (for example, optional CLINs or ceiling hours) so offerors can plan bench capacity. 3. Workload assumptions (5.0, 13.0): Please publish expected package volume by 20x Class and pathway (20x and Rev5) and target review cycle times, including how the Rev5/20x mix will shift across the option years as Rev5 phases down. These drive the labor mix and price. 4. AI tools (2.0, 3.3): Please define "super-intelligence tools" and confirm whether they are Government-furnished, and whether contractor-provided AI tools may be used with package data. 5. Access and GFI (12.0): Please list required systems, repositories, and expected suitability and PIV timelines, since ramp-up depends on them. 6. Labor categories (5.0, 6.0): Consider adding a Machine-Readable Compliance / Automation Engineer category to match the Automation Lead key role. 7. Key personnel (6.0): Limiting key personnel to three roles (Task Lead, 20x Technical Lead, QA Lead) would broaden competition. 8. Comparable experience (6.0): Please treat independent federal security assessment, audit evidence review, and agency ATO package review as comparable to FedRAMP package review. 9. Transition (9.0): Please confirm the anticipated start date relative to the current task order's end so transition-in can be planned. 10. OCI (11.0): Please define disqualifying relationships (FedRAMP Recognized assessor work, CSP advisory, CSP resale), whether a lookback period like REC-IAS-SEP's two years applies, and the disclosure and mitigation path.

Cloud9 Security Services, Inc.

AI comparisonLike Softthink, asks how provider delays affect review timelines; also asks about provider communications and Rev5 scope.

1. Workload (Sec. 3.0, 7.0, 13.0): Please share historical and projected package volume by certification class (20x Class A to D and Rev5), current average review clock, and the draft SOP, so offerors can size the labor mix and surge capacity.

2. Rev5 scope (Sec. 6.0): With the Rev5 path open until June 11, 2027, will Rev5 package reviews remain in scope after that date? Will the "Legacy or Rev5 Security Lead" and "Automation Lead" named in Sec. 6.0 become labor categories in Sec. 5.0?

3. Tools and data (Sec. 2.0, 3.3, 10.0, 12.0): Sec. 2.0 references super intelligence (SI) tools, while Sec. 3.3 limits work to Government-furnished or approved tools. May contractors propose their own SI or validation tools if they run inside a Government-approved environment? Which repositories, ticketing system, schemas, and APIs will be furnished?

4. OCI (Sec. 11.0): What look-back period applies to prior provider-support work? Will the Government accept mitigation, such as a firewall and per-package recusal, rather than exclusion? Does the restriction extend to FedRAMP Recognized assessors on the offeror's team?

5. Place and screening (Sec. 8.0, 10.0): What portion of staff must be on-site at GSA headquarters, and how many days per week? What investigation tier is required, and may staff begin work on an interim determination?

6. Transition (Sec. 9.0): When does the incumbent task order end, and how long an overlap does the Government plan for transition-in?

7. Review standards (Sec. 3.4, 4.0, 13.0): Will the Government furnish severity categories, disposition criteria, and review gates, or should offerors propose them? Will the PRS measure contractor timeliness only for activities within contractor control, given provider response delays?

8. Provider communication (Sec. 3.4, 3.6): Will contractor reviewers exchange questions directly with cloud service providers and assessors through the official ticket, or only through the Government Task Lead?

9. Acquisition strategy (Cover, Sec. 7.0): Is the Government considering a small business set-aside under SIN 54151HACS? The HACS small business pool includes firms with FedRAMP, NIST RMF, and cloud security engineering depth.

Coretec LLC

AI comparisonLike WITS, asks for tools and standardized materials before delivery; specifically requests a sandbox and OCI templates.

• Section 3.3 (Machine-Readable Data and Automated Validation): What specific FedRAMP 20x schemas, data models, and validation rule sets will reviewers use, and will the Government furnish a sandbox/test environment to validate submissions before performance begins? • Section 4.0 (Expected Deliverables): What is the anticipated monthly/annual package volume and mix of package classes (new authorization vs. continuous monitoring, Low/Moderate/High) that will drive deliverable frequency and staffing ratios? • Section 5.0 (Labor Categories and Qualifications): Will specific FedRAMP-related certifications (e.g., 3PAO Technical Proficiency) or clearance levels be required for each labor category, and must all categories be co-located, or may roles such as Automation/Technical Writer support remotely? • Section 6.0 (Key Personnel and Comparable Experience): Will key personnel resumes require a minimum number of directly comparable FedRAMP/3PAO engagements, or will analogous cloud security assessment and continuous-monitoring experience be credited equally? • Section 7.0 (Period and Capacity): Will task orders be issued as FFP, T&M, or a hybrid structure, and how will surge capacity beyond the $8M/year planning estimate be funded and ordered? • Section 8.0 (Place of Performance): What minimum on-site presence is expected relative to remote work, and does this requirement vary by labor category or review phase? • Section 9.0 (Transition): What transition-in duration is anticipated, and will the incumbent be required to support a structured knowledge-transfer or shadow period? • Section 11.0 (Organizational Conflicts and Independence): Will the Government require a standardized OCI mitigation plan template, and should conflicts be disclosed at proposal submission, task order award, or per package? • Section 13.0 (Performance Management): What target cycle-time and rework-rate thresholds does the Government anticipate for the PRS/QASP, and will these vary by package complexity or authorization pathway? • Section 10.0 (Security and Data Handling) and Section 12.0 (Government-Furnished Information): What background investigation tier and onboarding timeline should offerors plan for, and will GSA furnish laptops, accounts, and access to package repositories and validation tools, since these drive how quickly a team can start supporting active reviews?

Customer Value Partners, LLC

AI comparisonShares Guidehouse’s questions about decision responsibilities; also asks how disagreements between contractor findings and PMO positions are handled.

Customer Value Partners, LLC (CVP) appreciates the opportunity to review this RFI’s Draft PWS and offers the following questions for Government consideration.

Regarding Section 3.1, will the Government provide standardized intake checklists or templates for package review initiation, or is the contractor expected to develop these artifacts independently?

Regarding Section 3.2, how does the Government define the boundary between contractor technical analysis and the official FedRAMP authorization decision, particularly where contractor findings conflict with PMO staff positions?

Regarding Section 3.3, will machine-readable validation schemas and automated tooling be provided as Government Furnished Information, or must the contractor independently develop validation capabilities aligned with FedRAMP 20x OSCAL requirements?

Regarding Section 3.8, how will surge requirements be defined and communicated, and will surge tasking carry modified delivery timelines or maintain standard SLA commitments? Regarding Section 5.0, will the Government accept equivalent experience in lieu of specific FedRAMP 20x experience given the nascent nature of the 20x framework, and how will equivalency be evaluated?

Regarding Section 6.0, will the Government define a minimum threshold for what constitutes comparable cloud security engineering experience for Key Personnel qualification purposes?

Regarding Section 8.0, what is the anticipated frequency and minimum notice period for on-site requirements at GSA, and will remote work be permitted during periods without scheduled on-site obligations?

Regarding Section 11.0, will the Government provide a list of current FedRAMP package holders or CSPs under active review to support pre-award OCI screening?

Regarding Section 13.0, how will performance be measured during periods of evolving FedRAMP 20x policy, where review standards may shift mid-performance period?

Cyber Management International Corporation

AI comparisonOffers no current questions, as do Secured IT Solutions and FITS.

No current questions for the Government

CyberStorm Defense

AI comparisonThis cell describes past experience, while Life Cycle Engineering and other submissions ask questions about the proposed work.

This text is in the original column. The apparent answer to this question is elsewhere in this submission.

Brackets and placeholders are part of the submitted answer.

CyberStorm Defense (CSD) supports HHS/FDA under task order 75F40125F19009, an active effort rated Exceptional. [INSERT 2-3 sentences, verified from the canonical past performance library: the system(s) reviewed, impact level, framework (NIST SP 800-53 / RMF / FedRAMP), and what CSD produced - e.g., control assessments, SSP/SAR review, evidence analysis, POA&M tracking, ConMon reporting.] [INSERT one measurable outcome, only if documented: packages reviewed, findings closed, ATOs supported, cycle time reduced.] CSD's CEO and CISO, a CISM and CASP+ holder, leads this work and would serve as FedRAMP Technical Lead oversight.

CYBERSTORM DEFENSE

AI comparisonLike Prudent, advocates small-business acquisition; also asks about automation harnesses, cooling-off periods, and hybrid work.

GSA HACS Task Order Structuring & Small Business Utilization: Given that FedRAMP 20x prioritizes automated, rapid, and scalable package reviews, will the Government structure task orders primarily under GSA MAS SIN 54151HACS (Highly Adaptive Cybersecurity Services) with small business set-aside preferences to drive innovation and leverage agile small businesses within the National Capital Region corridor?

FedRAMP 20x Automated Harnesses & OSCAL Ingestion APIs: Will the Government furnish participating contractors with access to proprietary FedRAMP 20x automated validation harnesses, standardized Open Security Controls Assessment Language (OSCAL) schemas, and ingestion APIs during onboarding, or will vendors be expected to integrate proprietary parsing engines for Security Decision Record (SDR) verification?

OCI Boundary Enforcement for Dual-Role Vendors: To preserve absolute objectivity under NIST SP 800-37 and FedRAMP independent assessment guidelines, how will the PWS enforce organizational conflict of interest (OCI) firewalls when a contractor provides both advisory engineering to Cloud Service Providers (CSPs) and independent 20x package reviews? Specifically, what mandatory cooling-off periods will be mandated?

Hybrid Execution & Classified/Sensitive Data Handling: Please clarify the exact cadence and physical facility requirements for on-site presence at GSA facilities versus secure remote telework, particularly regarding the handling of sensitive unclassified or controlled unclassified information (CUI) FedRAMP packages within cloud-native review environments.

Dekalb Solutions LLC (DBA CybertLabs)

AI comparisonOffers no questions, as do Graham and LDR.

None.

Deloitte Consulting LLP

AI comparisonAnswers “No,” as LDR also reports no questions.

No

Development InfoStructure, LLC (Devis)

AI comparisonLike RADIX, proposes a dedicated data/automation role; also asks about travel costs and package-level recusal.

1. PWS 5.0 labor categories: add a Compliance Data Engineer category. PWS 3.3 makes machine-readable validation "a core part of the FedRAMP review process," but no listed category owns it. 2. PWS 2.0 and 3.3: define "super-intelligence tools" and state whether offerors may propose their own analytic tooling or must use Government-furnished tools only. This affects staffing and price. 3. PWS 3.3: name the machine-readable formats in scope (for example, the FedRAMP Security Decision Record and Certification Package Overview JSON schemas published with the Consolidated Rules for 2026) and whether Rev5 packages are also in scope, so offerors can staff the right skills. 4. PWS 8.0: allow a hybrid model, with a DC-based core and remote surge staff, to widen the pool of qualified reviewers, and state whether travel is reimbursable when staff based outside the DC area are called on-site. 5. PWS 11.0: state the OCI lookback period and how prior independent assessment or advisory work for cloud service providers by individual employees will be treated. We recommend per-package disclosure and recusal for individuals, so experienced assessors stay eligible for packages they have no tie to. 6. PWS 4.0 and 13.0: publish expected package volume per year by class so offerors can size review cells.

Ernst & Young LLP

AI comparisonLike Navira, proposes a pricing approach; favors performance-based fixed-price delivery and asks about allocating work among providers.

1. [Section 3.0 Scope of Work] Please clarify the intended relationship and separation of duties between Independent Assessment Services (formerly 3PAO) and the contractor performing FedRAM 20x package reviews under this PWS. Does GSA envision the PWS contractor augmenting the independent assessment function for Cloud Service Offerings seeking FedRAMP 20x certification or will the contractor serve as a separate FedRAMP PMO review and assurance function? If separate, please delineate the anticipated responsibilities and handoffs among the Cloud Service Provider, Independent Assessment Services provider, PWS contractor, and FedRAMP PMO. 2. [Section 11.0 Organizational Conflicts and Independence] Does GSA anticipate a single contractor providing the package-review capability, or a multi-provider model in which packages may be allocated among multiple contractors? If multiple providers are contemplated, how does GSA envision package assignment, quality consistence, OCI-based recusal, and surge allocation operating across providers? 3. [Security 11.0 Organizational Conflicts and Independence] How will the Government identify and mitigate organizational conflicts of interest (OCIs) for offerors that also hold active Independent Assessment Services accreditation or perform FedRAMP assessments, advisory, or readiness services for cloud service providers? A firm that reviews packages it or its affiliates assessed, or that reviews packages from providers it competes with or advises, may face impaired objectivity or gain unfair access to competitors' security and architecture data. 4. [Section 8.0 Place of Performance] Will the Government consider allowing a hybrid place of performance, in which on-site presence is required only for designated roles or activities and Government-approved remote personnel may perform the rest? A hybrid model would give the Government the widest pool of qualified talent while keeping in-person presence for engagement, consequential reviews, and escalations. 5. [7.0 Period and Capacity] Will the Government consider structuring this as a Firm-Fixed-Price (FFP), performance-based contract, priced by defined deliverables or units of work rather than labor hours? Under FFP, the contractor carried delivery and cost risk, giving the Government predictable budgets and clear accountability for outcomes.

Excentium, Inc.

AI comparisonLike TES, asks where package review ends and testing begins; also asks about assessor eligibility and package-specific recusal.

1. Workload (Sections 3, 7, 13): What monthly package volume, class mix (20x Classes A-D and Rev5), and current backlog should we plan for, and when does the review clock start, pause, and stop?

2. Review depth (Sections 3.2-3.3, 5): Will contractor staff evaluate the independent assessor's results only, or also re-perform or sample technical testing, including penetration test and red team evidence? Should reviewers meet A2LA FedRAMP assessor qualifications?

3. Conflicts (Section 11): Will FedRAMP Recognized assessors be eligible with package-level recusal and firewalls, and what lookback period and future-business restrictions would apply?

4. Rules and tools (Sections 3.3, 3.7, 12): How will packages already in review be handled when the Consolidated Rules or schemas change? Which Government tools, validators, and repositories will be furnished, and may contractors use approved automation or AI for evidence analysis?

5. Access and location (Sections 8, 10): What suitability level, system access, and lead times apply, and what on-site cadence is expected? May approved remote SMEs support DC-based staff?

First Information Technology Services

AI comparisonOffers no PWS questions, as do Secured IT Solutions and Graham.

We have no questions regarding the PWS.

Graham Technologies, LLC

AI comparisonOffers no questions, as do CybertLabs and FITS.

No questions.

Guidehouse Inc.

AI comparisonLike Longevity, asks about performance baselines and decision authority; explicitly identifies decisions it would reserve for Government.

Guidehouse requests clarification of the following to align staffing, pricing, independence, and review quality: 1. Sections 3.1, 3.8, 7 and 13: What are the expected monthly intake, concurrent reviews, backlog, certification classes/pathways, technology mix, review cycles, and surge duration? What workload assumptions support the annual planning ceiling? 2. Sections 3.2-3.4 and 12: Which SDR schemas, SOPs, review gates, and evidence sufficiency criteria will govern at award? How will changes apply to packages already under review? 3. Sections 3.3 and 12: Which repositories, ticketing systems, APIs, validators, scripts, and dashboards will be furnished? Is contractor development or modification of automation expected? What does use of 'super-intelligence tools' encompass, and what approval, data-protection, and human-review controls apply? 4. Sections 3.2, 3.4 and 4: Is scope limited to evaluating submitted evidence, or does it include direct environment access, independent test execution, or reproducing provider/assessor results? Who authorizes testing and provider communications? 5. Sections 4 and 13: What are the deliverable templates, acceptance thresholds, severity categories, escalation triggers, turnaround targets, and clock-stop rules for missing evidence, provider responses, and Government decisions? 6. Sections 5-6: Which roles are key personnel, what minimum qualifications are required, and may compatible roles be combined while preserving independent QA? 7. Sections 8-10 and 12: What on-site frequency, notice, core hours, screening, citizenship, device, telework, and access requirements apply? What incumbent overlap, knowledge-transfer materials, and access lead times should transition planning assume? 8. Section 11: What disclosure scope and lookback period apply to company, affiliate, employee, and subcontractor relationships? How will package-specific recusals, mitigation plans, and reassignment be approved? 9. Sections 2-4: Please confirm the Government retains all policy interpretations, risk acceptance, certification, and Marketplace decisions, and identify the authorized disposition roles or officials.

International Business Sales And Services Corp (IBSS Corp)

AI comparisonLike Excentium, asks about conflict eligibility; specifically asks how agency-side work and CMMC assessment affect screening.

Q1. Section 11.0: Would agency-side authorization support, where a firm assesses or maintains a federal agency's own systems and reviews cloud offerings on the agency's behalf rather than for a provider, be treated as a conflict? Would serving as an authorized CMMC C3PAO, which involves no FedRAMP work, be treated as one? How are affiliates weighed, and how is a compliance-readiness service a firm markets treated?

Q2. Sections 7.0 and 13.0: What annual package volume and class mix (20x initial and ongoing, Rev5, by impact level) should respondents assume for sizing? Throughput for the last two years would help.

Q3. Sections 2.0 and 3.3: What does "super-intelligence tools" refer to, and are those tools Government-furnished? Section 3.3 limits personnel to Government-furnished or Government-approved tools; may a contractor submit its own validation scripts or AI-assisted review aids for approval, and under what data-handling conditions?

Q4. Section 3.0: What share of the workload is Rev5 versus 20x, and does the scope include continuous monitoring review of already certified offerings?

Q5. Sections 8.0 and 10.0: What personnel screening level and citizenship requirement apply, how often is on-site presence at GSA headquarters expected, and is telework permitted for reviewers outside a core on-site group?

Q6. Section 12.0: What lead time should be assumed for GSA system access and package-repository credentials, and does the transition-in period start before access is granted?

Q7. Section 6.0: Will key personnel be evaluated with resumes in the solicitation, and will the Section 5.0 labor categories be priced as fixed staffing or as ordered hours?

Q8. Section 3.4: Do contractor reviewers communicate directly with providers and independent assessors in the official ticket, or only through Government personnel?

Q9. Section 3.2: Will contractor responsibilities be limited to evaluating submitted certification evidence, or will they also include independent technical testing, configuration validation, and verification of implemented security controls?

Thank you!

Kapoor IT Consulting LLC (KITC)

AI comparisonLike ACE, asks for workload and staffing assumptions; additionally asks about sampling and remediation cycles.

1. Package Volume and Complexity (Sections 3.1-3.3, 7): What are the anticipated monthly and annual package volumes, expected concurrent reviews, and distribution by authorization pathway, complexity, and review type? Will the Government provide historical workload data or planning estimates?

2. Review Scope and Level of Effort (Sections 3.1-3.5): What constitutes a complete end-to-end package review? Will contractors review all submitted evidence or apply Government-defined sampling and risk-based review criteria? How many clarification, remediation, and revalidation cycles should be anticipated per package?

3. Performance Standards and Deliverables (Sections 4, 13): What turnaround times, review milestones, service levels, and acceptance criteria will apply? Will performance timelines exclude delays awaiting CSP responses, Government decisions, or system access?

4. Staffing and Surge (Sections 3.8, 6-8): Does GSA anticipate a dedicated minimum staffing level or workload-driven staffing? What surge capacity, response times, key personnel qualifications, and frequency of on-site attendance should offerors plan for?

5. Tools and Automation (Sections 3.3, 3.7, 12): Which Government-furnished platforms, repositories, schemas, validation tools, and automation capabilities will be available? Is the contractor expected to develop or maintain custom validation tools, integrations, or scripts, and to what extent?

6. Transition and Security (Sections 9-10, 12): What transition period, personnel screening, suitability or clearance requirements, training, and access lead times are anticipated before active reviews begin?

7. Pricing and Ordering (Section 7): What contract type and pricing structure does GSA anticipate (e.g., labor-hour/T&M, fixed-price, or hybrid)? Will the solicitation provide estimated labor hours, workload bands, or ordering assumptions to support consistent pricing across offerors?

LDR Security Solutions, LLC

AI comparisonOffers no questions, as do CybertLabs and Deloitte.

LDR has no questions for the Government on the draft PWS.

Life Cycle Engineering, Inc.

AI comparisonFocuses on package counts and system size, while KITC also asks about review depth, tools, and transition arrangements.

We request that the Government provide information about the number of packages expected per year and size of the systems? This information would help properly size, staff, and price this effort.

Longevity Consulting

AI comparisonLike Guidehouse, asks how review responsibilities and external dependencies affect deliverables and performance measures.

Longevity requests clarification on the following draft PWS provisions to establish defensible staffing, review criteria, and pricing: 1. Sections 3.1, 3.8, 7.0: What are the anticipated annual package counts, monthly peaks, certification classes, and proportions of initial reviews versus resubmissions? Will GSA provide complexity categories, turnaround targets, and surge-ordering procedures? 2. Sections 3.2, 3.3, 6.0: What share of reviews will use FedRAMP 20x versus Rev5 or other legacy requirements? Will GSA issue authoritative KSI interpretations, review checklists, Security Decision Record (SDR) standards, and technical escalation criteria? 3. Sections 3.3, 12.0: Which repositories, APIs, schema validators, and other tools will reviewers use? Will GSA provide access, representative test packages, and an approved process for handling rule or schema changes during an active review? 4. Sections 3.4, 3.5, 4.0: What responsibilities will reviewers, GSA officials, cloud service providers, and third-party assessment organizations have for questions, findings, retesting, and closure? What constitutes an accepted review deliverable? 5. Sections 5.0, 6.0, 8.0: What key positions and minimum qualifications are anticipated? How frequently will on-site support be required, with what advance notice, and may approved remote specialists support surge or niche reviews? 6. Sections 9.0-11.0: What are expected transition, access, screening, and data-handling timelines? What OCI disclosures and Government determinations must precede assignments involving prior CSP or assessor relationships? 7. Section 13.0: How will GSA establish throughput, timeliness, quality, and rework baselines while accounting for package complexity, provider response delays, and Government-controlled dependencies?

Navira Federal

AI comparisonProposes a combination of monthly, per-review, and surge pricing, while EY proposes performance-based fixed-price delivery.

1. Section 7: Would the Government structure pricing as a fixed monthly line for program management and intake, fixed prices per completed review by package type (20x Class B, 20x Class C, Rev5), and a labor-hour line for surge? If so, what annual volume by type should offerors assume?

2. Section 3.1 and 13: Should timeliness standards start at the contractor's intake-readiness determination, so incomplete packages returned to the provider do not count against review time?

3. Section 11: Would the Government adopt a package-level OCI standard, under which no firm or individual that performed assessment, advisory, implementation or provider-support work for a provider within a set lookback period may review that provider's package, with a screening record available to the Contracting Officer?

4. Section 3.3 and 12: Will offerors be allowed to propose automation and validation scripts that run only after Government approval and only in Government systems? Which tools, schemas and repositories will be furnished at award?

5. Section 3.2 and 3.3: Should offerors plan for reviews against the FedRAMP Consolidated Rules for 2026 and the published Security Decision Record schema from day one, and what share of the workload will remain Rev5?

6. Section 4: Would the Government define package readiness as an SDR that validates against the current schema, complete rule and KSI entries, independent verification and validation present, and all findings closed or dispositioned?

7. Section 6: Would key personnel be limited to the Task Lead, FedRAMP 20x Lead and Quality Assurance Lead, with other roles staffed to PWS qualifications?

8. Section 1 and 9: Which functions under task order 47QPCA24F0015 move to this requirement, and how long a transition overlap does the Government plan?

9. Section 8: Would a hybrid model meet the need, with leads, QA and program staff on-site as directed and specialist reviewers allowed to work remotely within the United States?

10. Section 10: What screening level applies (for example, Tier 2 public trust), and can onboarding start before the incumbent's order ends?

11. Set-aside: Is the Government considering a total small business set-aside under SIN 54151HACS, which would let small firms with complementary assessment and management capability team?

Noblis, Inc.

AI comparisonFavors full and open competition, whereas Assurit and Prudent favor small-business set-asides.

Would the Government please consider using 54151HACS SIN for the open solicitation, as well as this being a full, open solicitation as opposed to a Small Business Set Aside (SBSA)? This program is too vital to award to a company who is not already well-versed or experienced with the existing and emerging FedRAMP frameworks, including 20x.

Obsidian Global, LLC

AI comparisonLike Excentium, asks whether conflicts can be handled through package-specific mitigation rather than excluding the entire firm.

1. Sections 3 and 7 (Workload): Can the Government share current and projected package volumes per year by type (20x and Rev5), class (A-D), and stage, plus the current queue and average review hours per package?

2. Section 6 (Scope): The PWS mentions a possible Legacy or Rev5 Security Lead. Are Rev5 certification packages, including the agency path, in scope?

3. Section 11 (OCI): Will firms that provide FedRAMP advisory services to cloud providers be eligible if they mitigate through package-level recusal and firewalls, or will they be excluded? Will conflicts be evaluated per package or per company, and will the Government provide a list of in-scope providers so offerors can screen before award?

Paragon Technology Group, Inc.

AI comparisonLike Coretec, asks what tools will be available; distinguishes supplied automation from automation the contractor would develop.

1. Sections 3.1, 3.2, and 6.0: Review Scope. Will the scope include legacy FedRAMP Rev. 5 packages and transitions to FedRAMP 20x, or only FedRAMP 20x submissions? If both, what is the anticipated distribution? 2. Sections 3.1, 3.8, and 7.0: Workload. How many packages require review each month, and how many concurrent reviews does GSA expect? Please identify anticipated surge periods or workload fluctuations. 3. Sections 3.2, 3.3, and 4.0: Review Criteria. Will GSA provide standardized Key Security Indicator (KSI) assessment criteria, evidence requirements, and thresholds for determining package readiness? 4. Sections 3.3 and 12.0: Automated Validation. Which tools, schemas, scripts, and application programming interfaces does GSA intend to provide? Does the scope include developing new automation or primarily using existing tools? 5. Sections 3.4 and 3.5: Findings Management. Does GSA have an established system for documenting findings, tracking provider responses, and recording final dispositions? What criteria govern issue severity and closure? 6. Sections 5.0, 6.0, and 8.0: Staffing. What percentage of personnel must work on-site in Washington, DC? Does GSA require specific positions on-site regularly, or only for designated activities? 7. Sections 9.0 and 12.0: Transition. How much time does GSA anticipate allowing for transition, onboarding, personnel screening, system access, and required training? 8. Section 11.0: Organizational Conflicts of Interest. What restrictions apply to contractors with existing cloud security, assessment, or authorization support relationships? What mitigation measures does GSA consider acceptable?

Prudent Technology LLC

AI comparisonShares Assurit’s set-aside and staffing proposals; also asks that joint-venture and affiliate experience count.

Prudent Technology, LLC (UEI LKTJT6AMQHM4; CAGE 7AUP3) is an SBA-certified WOSB under NAICS 541519. It is headquartered in Aldie, VA, with a field office in McLean, VA. Prudent holds GSA MAS contract 47QTCA24D00F1, SIN 54151HACS, and an active Top Secret facility clearance. It delivers RMF assessment and authorization, ISSO support, security engineering, and 24x7 SOC operations under ISO and CMMI Level 3 (DEV/SVC) processes. Our joint venture, FedTec Ventures, LLC (Prudent and FedTec, LLC), holds ENCORE III SB and ITES-3S SB.

We recommend keeping this requirement on GSA MAS SIN 54151HACS as a small business set-aside. At about $8M per year, it is well within small business capacity. FedTec Ventures delivers an 86-FTE federal cybersecurity program with at least 200 security control assessments a year, and we deliver 40- to 58-FTE programs for DISA, Army Forces Command, and Army Cadet Command.

Because few firms have performed FedRAMP PMO-side review, we recommend that Section 6.0 define comparable experience to include independent security control assessment, A&A package review, FedRAMP package review for agency reuse, and IV&V of vendor-submitted artifacts. We also recommend that it allow joint venture and affiliate experience.

In Section 5.0, we recommend three changes:

Add an Automation/Data Validation Engineer category to match the Automation Lead in Section 6.0. Limit key personnel to the Task Lead and FedRAMP 20x Technical Lead. Clarify whether Rev5 packages are in scope.

To help offerors staff and price accurately, please share expected package volume by class, current queue size, and target review timelines (Sections 7.0 and 13.0). Please also specify the required investigation level and access approvals early, since they drive start-up time (Sections 10.0 and 12.0).

We also recommend the following:

Define the “super-intelligence tools” in Section 2.0, state whether contractor-provided tools are permitted, and explain how AI-assisted review is used, since FedRAMP bars AI-generated output from serving as deterministic telemetry. State the expected on-site frequency (Section 8.0). Define the OCIs of concern, such as assessor, advisor, or provider employment, and allow mitigation plans (Section 11.0). Allow a transition-in period that reaches full operational capability before reviews transfer (Section 9.0).

Quzara LLC

AI comparisonAnswers N/A, while Secured IT Solutions and several others explicitly state that they have no questions.

N/A

RADIX International Consulting LLC

AI comparisonLike ACE, proposes an automation role and a small-business set-aside; describes schema, script, and API tasks for that role.

1. Sec. 5 Labor Categories: Add an Automation / Machine-Readable Data Engineer category; Sec. 6 lists an Automation Lead, but no matching labor category exists for the schema, validation-script and API work in Sec. 3.3. 2. Sec. 2 Objective: Define the "super-intelligence tools" contemplated and the rules for their use on CUI and provider-proprietary data, so offerors can price and staff for approved AI tooling. 3. Sec. 7 / 13 Capacity: Publish expected package volume by class (Rev5 vs 20x, Low/Moderate) and target cycle times. This is the main driver of staffing ratios and surge pricing. 4. Sec. 8 Place of Performance: State the expected on-site percentage and whether remote reviewers outside the DC metro are acceptable when using GFE. 5. Sec. 11 OCI: Specify the lookback period, which relationships trigger disclosure (CSP advisory, 3PAO, reseller, employment), and acceptable mitigation forms (recusal, firewall). 6. Sec. 10 / 12 Security & Access: Identify the required screening level and access approval lead times; they control how fast new reviewers become productive. 7. Sec. 4 Deliverables: Provide templates or examples for the review sheet, escalation package and draft certification scorecard to standardize quality across vendors. 8. Set-aside: Consider a small business set-aside under SIN 54151HACS; the work is labor-centric and well suited to specialized small businesses.

Secured IT Solutions

AI comparisonOffers no questions, as do FITS and Graham.

None at this time

Softthink Solutions Inc

AI comparisonShares Longevity’s questions about dependencies and performance measures, with additional questions about resolving rule ambiguity.

1. Sections 3 and 7: What monthly package volume, concurrent workload, certification-class mix, and surge demand should offerors use for staffing and pricing? 2. Sections 4 and 13: What review deadlines, escalation timelines, QA standards, and acceptance criteria will apply? Will timeliness measures exclude delays awaiting provider responses or Government access and decisions? 3. Sections 5, 6, and 8: Which roles require dedicated staff, what qualifications are mandatory, and what on-site cadence applies? May offerors combine roles and use approved remote specialists? 4. Sections 3.3 and 12: Which repositories, schemas, validation tools, APIs, and AI environments will GSA provide or authorize? 5. Sections 3.2, 3.4, and 3.7: How will GSA resolve rule ambiguities and approve changes affecting in-progress reviews? Who authorizes provider exchanges and package dispositions? 6. Sections 9 and 10: What transition overlap, screening, device, access, and incident-reporting requirements should offerors assume?

Stondoh Secure Digital Solutions

AI comparisonLike Guidehouse, asks about workload, tools, and access; also asks what integrity evidence is required for the certification-support record.

1. Sec 3.0/6.0: Is review of legacy Rev5 packages in scope, or only 20x? Which 20x classes/impact levels (Low, Moderate, High) are expected, and in what mix? 2. Sec 4.0/7.0/13.0: What is the estimated annual package volume, current backlog, and target review cycle time per package class? This drives staffing ratios and surge assumptions. 3. Sec 2.0/3.3: What “super-intelligence” or AI tools does the Government expect to furnish or approve? May contractors propose their own AI/automation tools for Government approval, and must they hold a FedRAMP authorization? 4. Sec 3.3/12.0: Which systems, repositories, schemas, validation tools, and ticketing platforms (e.g., GitHub, FedRAMP ticketing) will be Government-furnished, and what is the typical lead time for access approval? 5. Sec 8.0: How often is on-site presence at GSA HQ expected (days/week)? Will telework or remote staff outside the DC metro area be permitted for some roles? 6. Sec 10.0: What background investigation tier is required (e.g., Tier 2/Tier 4, Public Trust), and will GFE devices be issued? Is interim access allowed while investigations are pending? 7. Sec 11.0: Will firms (or affiliates/subcontractors) that perform 3PAO assessments, CSP readiness, or advisory work be excluded, or may an OCI mitigation plan (firewalls, recusal from specific CSP reviews) suffice? 8. Sec 7.0: What contract type is contemplated (T&M/LH, FFP, hybrid), single or multiple award BPA/task order, and is a small business set-aside under HACS SIN 54151HACS being considered? 9. Sec 9.0: Is there an incumbent task order? If so, what is its end date, and how long a transition-in period is anticipated before full operational capability? 10. Sec 5.0/6.0: How many key personnel positions are anticipated, and will equivalent experience be accepted in lieu of specific certifications (e.g., CISSP, CCSP, CISA)? 11. Sec 4.0: For the Certification-support record, what form of “hash or integrity evidence” is expected, and who owns final record updates? 12. Sec 3.8: How will surge be ordered and priced (optional CLINs, hours ceiling), and what notice period is expected?

The Enterprise Security Consultants, LLC (dba TES Consultants)

AI comparisonLike Assurit, proposes a set-aside and revised roles; specifies a WOSB set-aside and additional machine-readable scope fields.

1. Set-aside (cover page): Will the RFQ be set aside? We recommend a Women-Owned Small Business set-aside; qualified small HACS holders are available. 2. HACS subgroups: Will the RFQ restrict to specific 54151HACS subgroups? We recommend Risk and Vulnerability Assessments and High Value Asset Assessments, or all six. 3. Sections 3.0 and 7.0: What annual package volume, mix by certification class (20x Classes and Rev5), and number of concurrent reviews should offerors assume? 4. Section 5.0: Will the final labor categories combine Package Reviewer with Security Control and Evidence Analyst, fold Technical Writer into reviewer and QA roles, and add an Automation/Data Engineer? 5. Section 6.0: Which roles will be key personnel, and will resumes be evaluated? 6. Section 7.0: eBuy lists Firm-Fixed-Price and Labor Hour. Which work will be FFP (e.g., transition-in, recurring deliverables)? 7. Section 8.0: What on-site percentage is expected by labor category, and may specialist roles work remotely outside the DC area? 8. Sections 2.0 and 3.3: May contractors propose Super Intelligence (SI) review tools for Government approval, and what data-handling conditions apply? 9. Sections 3.2 and 3.3: Please confirm reviewers evaluate provider evidence and assessor IVV results and do not re-perform independent assessment. 10. Section 3.3: Will FedRAMP add CPO schema fields for Minimum Assessment Scope information resources, flows, and security categories, with resource references on each KSI validation, so coverage can be checked automatically? 11. Section 9.0: When does incumbent task order 47QPCA24F0015 end, and how long a transition overlap is planned? 12. Section 10.0: What personnel investigation level is required, and must it be adjudicated before start? 13. Section 11.0: How will the Government treat prior cloud service provider advisory, readiness, or 3PAO work, and will OCI mitigation plans be accepted? 14. Section 12.0: Which systems, repositories, and tools will be Government-furnished, and what is the expected access lead time?

Vertekal LLC

AI comparisonShares Excentium’s questions about direct testing versus review of assessment evidence, alongside access and attendance questions.

Workload and surge (Sections 3.8 and 7). What initial backlog, monthly package volume, package complexity, and concurrent review workload should contractors assume? What surge capacity and activation notice are anticipated?

Review scope (Sections 3 and 6). Will work include both FedRAMP 20x and legacy/Rev5 packages? Does technical analysis include direct testing in provider environments, or primarily evaluation of submitted evidence and assessment results?

Performance standards (Sections 4 and 13). What review milestones, acceptance criteria, and turnaround targets are anticipated? How will time awaiting provider responses, Government decisions, or system access be treated when measuring contractor performance?

Automation and AI (Sections 2, 3.3, and 12). Which tools, repositories, and validation capabilities will the Government provide? What capabilities are intended by “super-intelligence tools,” and what approval, data-handling, and human-review requirements will govern contractor-proposed AI tools?

Onsite support (Section 8). Which roles and activities require onsite attendance, at what frequency and notice? May qualified remote personnel outside the DC area support work that does not require physical presence?

Transition and access (Sections 9, 10, and 12). What transition overlap, incumbent knowledge transfer, training, and onboarding timelines are anticipated? When will required devices, credentials, and repository access be available relative to the expected start of active reviews?

Wits Solutions Inc

AI comparisonLike Cloud9, asks about provider communications and review timelines; also asks when templates will be available.

Section 2.0: Which Government-approved "super-intelligence tools" do you expect contractor staff to use, and what limits apply to provider data in those tools?

Sections 3.0 and 5.0: What package volume do you expect by year, and what is the expected mix of 20x classes and Rev5 packages? Section 6.0 mentions a Legacy or Rev5 Security Lead. Will Rev5 reviews fall within scope?

Section 3.3: Which validators, schemas, dashboards, and APIs will the Government furnish, and may contractor staff propose scripts for Government approval?

Sections 3.4 and 3.6: Will contractor staff communicate directly with providers and assessors under standing authorization, or case by case through the Government Task Lead?

Section 4.0: Does a current SOP or format exist for the review sheet, draft certification report, scorecard, and certification-support record, and will respondents see them before proposals are due?

Section 6.0: Which roles do you expect to designate as key personnel, and will the solicitation require named resumes?

Section 7.0: What contract type and ordering approach do you anticipate for variable labor, and how much notice would surge requests carry?

Section 8.0: How often do you expect staff to work on-site at GSA headquarters, which roles are most affected, and may any roles work outside the DC area with approval?

Section 9.0: When does the incumbent task order end, how long is the planned transition overlap, and when must the contractor reach full operational capability?

Section 10.0: What personnel screening level applies, and must staff have it at start of work? Will the Government furnish devices and system access, and how long do those approvals usually take?

Section 11.0: How far back should respondents look for assessment, advisory, implementation, or resale relationships with providers? Would package-level recusal and firewalls be acceptable mitigation?

Section 12.0: Which repositories, ticketing systems, collaboration tools, and training will the Government furnish at start of work?

Section 13.0: When will the Government define clock dates, rework rate, and other measures, and will baseline data be available to respondents?