Federal SSO Procurement Should Prioritize Predictable Pricing and Portability

A Federal News Network commentary argues that federal agencies should treat single sign-on (SSO) as critical infrastructure rather than a routine software feature. SSO supports access to multiple systems through a shared identity experience, making its reliability and terms of service important to agency operations. The commentary’s central procurement concern is cost predictability: agencies should favor capacity- or load-based pricing that makes the relationship between usage and cost understandable, instead of accepting opaque renewal terms that may make future expenses difficult to anticipate.

The article frames pricing transparency as one part of a broader effort to make SSO acquisitions and ongoing service management more accountable. Agencies developing requirements can describe expected capacity and service needs, then use those requirements to clarify how pricing changes as usage grows or shifts. This approach could give acquisition teams a stronger basis for comparing proposals and assessing renewal costs. The source does not report a specific solicitation, contract value, award, or procurement date, so the recommendations are planning considerations rather than notice of a current buying opportunity.

The commentary also recommends making technical and operational expectations explicit. Proposed areas for requirements include portability, upgrade testing, control over identity attributes, and risk-based multifactor authentication (MFA). These terms can help agencies evaluate how an SSO service would fit into existing environments, how changes would be tested, which identity information is managed, and how authentication requirements can respond to risk. The source identifies the National Institute of Standards and Technology (NIST) in the supplied agency information, but does not describe a specific NIST procurement or attribute particular recommendations to a NIST program.

For contractors, the recommendations point to the kinds of evidence and commercial explanations agencies may seek when shaping future SSO requirements. Providers should be prepared to explain how capacity- or load-based pricing is calculated and how customers can plan for renewals. They may also need to demonstrate portability, describe upgrade-testing practices, explain attribute-control capabilities, and show how risk-based MFA is supported. These are potential evaluation and contract-management considerations, not stated mandatory requirements or a published evaluation rubric. The source lists Skycloak as a vendor, but provides no company-specific announcement, award, or claim about its products.

• Pricing model: Agencies can consider capacity- or load-based SSO pricing to make usage assumptions and renewal costs more transparent.
• Requirement development: Acquisition teams can translate anticipated demand and service expectations into clearer solicitation language.
• Portability: Agencies can make it easier to assess how an SSO service fits with existing systems and future changes.
• Upgrade testing: Solicitations or contract-management plans can specify expectations for testing upgrades before operational deployment.
• Attribute control: Buyers can clarify how identity attributes are governed and managed within the service.
• Risk-based MFA: Agencies can identify authentication capabilities that adjust to risk as a technical and operational consideration.
• Contractor preparation: SSO providers should be ready to explain pricing mechanics and demonstrate relevant technical capabilities.
• Opportunity status: The commentary reports no specific solicitation, award, contract value, deadline, or open procurement.