All playbooks

Government procurement

Sell a cloud service to the U.S. government

Distinguish cloud certification, system authorization and contract-specific cybersecurity obligations.

The situation

A small SaaS vendor wants to sell to a federal agency and separately to a defense prime contractor. The two buyers use similar security vocabulary but are asking about different parts of the business.

What to do first

Ask where federal information goes in each arrangement. Draw the cloud offering, the agency system and any company environment where contract information will be handled.

How to organize the work

  1. 1

    Confirm the FedRAMP route for the offering

    Confirm offering scope, class and path. Use current rules to check evidence needs and identify the agency’s remaining authorization work.

    Who
    Cloud program lead + federal customer owner
    Output
    Offering boundary and certification path
    FedRAMP
  2. 2

    Identify the agency system’s authorization decision

    Record what the agency can inherit from the provider. Identify the application and operational controls still owned and assessed by the agency.

    Who
    System owner + agency authorizing official
    Output
    Authorization package and residual-risk decision
    NIST Risk Management Framework
  3. 3

    Read the defense solicitation and contract

    Trace FCI or CUI and applicable contract clauses, including relevant subcontractors. Check the exact assessment status and continuing affirmation requirements.

    Who
    Contracting lead + security
    Output
    CMMC scope and required status
    CMMC

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes