TX-RAMP
Texas TX-RAMP certification for cloud products
Get a cloud product ready for Texas state procurement. Confirm the required level with the buyer, choose a submission route, assemble evidence for the actual offering, and plan for reporting after award.
- Issuing authority
- Texas Department of Information Resources (DIR)
- Timing
- Work backwards from procurement and allow time for intake, evidence review and any queue. DIR’s FAQ gives a four week review goal from the start of review. Manual 4.0 expects vendors to answer clarification requests within 10 business days. It gives 12 months from grant for standard provisional certification, while the eligibility page describes up to 18 months. Use the award’s expiry and confirm any discrepancy with DIR. Full Level 1 and Level 2 awards generally last three years subject to continued compliance.
- Reviewed
- Inside this guide
- 5 steps · 5 templates
Who it applies to
Texas state agency cloud purchases and renewals subject to Government Code § 2063.408. The agency determines the impact of its intended use. Level 1 covers low impact and Level 2 covers moderate or high impact. Identify the exact product, hosting option and agency use. A certified hosting platform can supply evidence for inherited controls. The SaaS offering needs its own certification.
What you’ll produce
A DIR decision for a specific cloud service, matched to the agency procurement and recorded with the approved level, boundary, expiry and monitoring owners.
DIR charges no TX-RAMP certification fee. Budget internal evidence preparation, remediation, reporting and any third-party assessment you commission. Use the DIR certified products workbook to verify the specific offering and status, and cross-check the award or portal when details differ. The public workbook is a list of certified offerings and does not provide the application denominator for a pass rate.
Run the project
Go to the roadmapDecisions for leadership
- What do we need the certification to cover?
- Confirm the applicable edition, sites, products or service boundary and the certification route. Budget for assessment, changes needed to pass, and maintaining certification.
- Who will do the work and who can sign?
- Appoint a sponsor, a day-to-day lead and a named owner for every workstream. Set aside their time and decide who can approve the outcome, accept remaining risk or authorize a filing.
- Which deadlines can we promise?
- Separate fixed external dates from internal targets. Confirm dependencies such as a vendor, test lab or assessor, and approve a backup plan if their dates slip.
How to spend the first week
- Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
- Ask the appropriate assessor or program contact what scope they will review, what evidence they need, and which dates and fees they can confirm in writing.
- Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
What to review each week
Monitor unresolved scope questions, controls without evidence, findings that need a retest and the next assessment or renewal date.
Kickoff brief to share with your team
Fill this in with your sponsor and send it to the people who own the work.
TX-RAMP kickoff brief Business reason and required outcome [Contract, obligation or approval] Scope and exclusions [Entities, systems or activities, and reasons] Fixed deadlines and internal milestones [Date, source and owner] Executive sponsor and authorized signer [Names] Project lead and backup [Names] First workstream Confirm the buyer’s scope and level · Agency security and procurement + vendor product owner [Name and due date] People, effort and external costs [Estimate, owner and contingency] Evidence folder and reviewer access [Location, access owner and review date] Decisions and blockers [Item, options, owner and decision date] First week 1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work. 2. Ask the appropriate assessor or program contact what scope they will review, what evidence they need, and which dates and fees they can confirm in writing. 3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
How to hand off evidence
- Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
- Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
- Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
- Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
How this works in practice
Two questions to check scope
- Which agency is buying the service, and what impact level did it assign?
- What deployable product and environment does the contract name?
- Who can respond to DIR and submit recurring reports if the primary contact leaves?
Worked scenario
A Texas agency buys a case management SaaS. Its security office assigns moderate impact. The supplier’s SOC 2 Type 2 report covers its commercial environment, but the bid names a separate government deployment. The supplier checks the scope mismatch with DIR before promising Fast Track, begins gathering evidence for a standard Level 2 review, and asks procurement to confirm the planned award and any provisional deadline in writing.
Official milestones
See the deadline calendar- 12 Feb 2026
Program Manual 4.0
DIR revised continuous monitoring, significant change reporting and recertification.
Official reference (opens in a new tab)
- 01Confirm the buyer’s scope and level, Agency security and procurement + vendor product owner, about 5 days
- 02Choose the route and file the intake, Vendor compliance lead + legal + agency sponsor if applicable, about 7 days
- 03Build and submit the questionnaire, Security architect + control owners + assessment lead, about 20 days
- 04Answer review questions and verify the award, Provider compliance lead + DIR assessor + procurement, about 10 days
- 05Monitor, report and renew, Security operations + incident lead + contract owner, about 7 days
Step by step
Checklist, instructions and 5 templates.
View plan as a table
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Confirm the buyer’s scope and level | Agency security and procurement + vendor product owner | Before bid or renewal | Set a start date | Offering and procurement scope | Open |
| Choose the route and file the intake | Vendor compliance lead + legal + agency sponsor if applicable | Before requesting an assessment | Set a start date | Route decision and intake record | Open |
| Build and submit the questionnaire | Security architect + control owners + assessment lead | Before DIR review | Set a start date | Assessment response and evidence index | Open |
| Answer review questions and verify the award | Provider compliance lead + DIR assessor + procurement | Respond to DIR within 10 business days under Manual 4.0 | Set a start date | Review log and award handoff | Open |
| Monitor, report and renew | Security operations + incident lead + contract owner | After award and before expiry | Set a start date | Monitoring and renewal calendar | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
- 01
Confirm the buyer’s scope and level
Record the agency, contract, legal provider, product name, hosting option, intended data and impact decision. Draw the offering boundary and list components run by the vendor, buyer or subcontractors. Obtain the agency’s written classification decision.
What to produce
Offering and procurement scopeOne page approval memo and boundary diagram
Gather first
- Draft scope of work
- Agency data classification
- Product architecture
- Subprocessor inventory
How to prepare it
- Write the proposed legal provider and product name as they appear on the procurement documents. List production locations, processing components and support access.
- Mark each component vendor managed, customer managed or inherited. Identify the agency security and procurement approvers. Obtain their written classification and attach the scoped diagram.
- Add the issue date and diagram version to the memo. Record any excluded add-ons and agree who can approve a future scope change.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Fictional contract line
- Lone Star Case Desk, dedicated Texas agency tenant, U.S. hosted, production and backup included. Agency security assigns moderate impact. Proposed certification is TX-RAMP Level 2.
- Boundary exception
- The optional analytics connector sends records to a separate processor. Exclude the connector from the quote until scope and controls are reviewed.
Check before handing it over
The buyer and provider agree in writing on the service to be purchased and the required level.
Attach the approved scope to the request and procurement file.
- 02
Choose the route and file the intake
Compare a DIR assessment, eligible reciprocal status and Fast Track. For Fast Track, check Manual 4.0 section 15 for accepted assessment types and the preceding 24 month window. Match every artifact to the exact offering and confirm disclosure permission. Submit the route-specific request and complete the acknowledgment and inventory questionnaire where directed.
What to produce
Route decision and intake recordRoute memo with evidence crosswalk
Gather first
- Scope memo
- Existing award or independent report
- Report dates
- Disclosure terms
- DIR request form
How to prepare it
- Record each route, its prerequisites and your decision. For reciprocity, copy the external offering name, level and current status into the memo and check DIR’s mapping.
- For Fast Track, compare the report period and boundary with the intended service. Have legal confirm sharing rights because DIR says it cannot sign an NDA for the process. Submit the selected form and track the acknowledgment and inventory step.
- Save proof of intake and mark who will monitor the shared inbox. Set an internal follow-up date and verify the provisional award before the buyer relies on it.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Fictional decision
- A SOC 2 report dated six months ago covers only the shared commercial tenant. Choose standard Level 2 unless DIR accepts evidence covering the separate government deployment.
- Intake record
- Owner: vendor compliance. Backup: product assurance. Attach the submitted request, questionnaire receipt and any provisional award with its actual expiry.
Check before handing it over
The chosen route fits the product and the team can reproduce what was submitted.
Give the receipt and next deadline to the buyer and assessment lead.
- 03
Build and submit the questionnaire
Use the current SPECTRIM questionnaire and DIR resource workbook. For each control, say who performs it, what systems it covers, when it operates, and where supporting evidence lives. Separate inherited responsibility and service-specific proof. Submit the complete package and retain the receipt.
What to produce
Assessment response and evidence indexQuestionnaire and evidence spreadsheet
Gather first
- Current DIR workbook
- Assigned questionnaire
- Boundary diagram
- Policies
- Logs
- Inherited control evidence
How to prepare it
- Maintain one row per questionnaire item, with implementation owner, scope, procedure, evidence ID, date collected and reviewer.
- For shared controls, label the supplier or customer responsibility and attach proof for the part your team operates. Use dated extracts and remove unrelated tenant data before upload.
- Run a peer review against the current assessment questionnaire. Confirm all mandatory items have a response and that the assessor can open every referenced file.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Fictional evidence row
- Privileged access review, case management production tenant. Security Operations reviews privileged groups monthly. Evidence P-17 links the October group export, security sign-off and exception closure.
- Inheritance check
- Hosting provider controls data center entry. The SaaS team supplies its own administrator access approval and recertification evidence.
Check before handing it over
An assessor can reconstruct each control answer and its boundary from the evidence index.
Publish the reviewed package through SPECTRIM and retain the receipt with the submission version.
- 04
Answer review questions and verify the award
Assign reviewers and backups when the first request arrives. Map each issue to a corrected response, evidence and remediation plan where needed. Reconcile the issued certificate to the offering, level and expiration in the procurement file.
What to produce
Review log and award handoffIssue tracker and release memo
Gather first
- DIR clarification requests
- Submitted evidence
- Remediation tracker
- Issued decision
How to prepare it
- Log the request date, response deadline, control reference, accountable owner and backup. Have a second reviewer confirm each answer addresses the request.
- Match the certificate to the intended agency service, level and expiry. Confirm that procurement and operations hold the same award and contact details.
- Record the final decision, submission version and outstanding remediation due dates together. Retain the corrected certificate if DIR replaces it.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Fictional review item
- DIR requests evidence that a terminated administrator lost access. Assign Identity Operations, attach the dated removal ticket and identity audit log, and record the reply receipt.
- Award mismatch
- Award names the shared SaaS edition. Resolve the mismatch with DIR before presenting it as approval of a dedicated tenant.
Check before handing it over
Every clarification has a reply and every award field matches procurement records.
Send the approved award to the buyer and monitoring owner.
- 05
Monitor, report and renew
Schedule quarterly Level 2 or annual Level 1 vulnerability reporting for DIR assessed awards, including Fast Track. Manual 4.0 exempts qualifying reciprocal awards from submitting these monitoring artifacts to DIR. Keep obligations under the originating program and contract. Escalate significant changes and follow the manual’s 48 hour DIR breach notice requirement for a certified offering. Start recertification as early as 12 months before expiry.
What to produce
Monitoring and renewal calendarCompliance calendar and reporting log
Gather first
- Award
- Manual 4.0
- Contract
- Vulnerability report
- Change register
- Incident policy
How to prepare it
- Record the award route, level, confirmed expiry, reporting cadence, contacts and backups. Schedule review of reporting dates and record each submission receipt.
- Keep approved incident and significant change paths beside routine reporting. Assign the renewal lead and open a recertification task 12 months before expiry if the team is ready.
- During each reporting cycle reconcile the included assets against the approved boundary, identify missing scan coverage and retain a review sign-off.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Fictional calendar row
- Standard Level 2. Security Operations owns quarterly reporting. The September report shows counts by severity and lists remediation or mitigation for high and critical findings.
- Fictional escalation
- A significant change to covered hosting triggers a documented security impact review and the current DIR change request process.
Check before handing it over
Owners and backups can explain what goes to DIR, what goes to the agency and when each obligation is due.
Review with operations, counsel and procurement before each renewal.
Official sources
- DIR program and notices (opens in a new tab)
- DIR Program Manual 4.0 (opens in a new tab)
- DIR FAQ (opens in a new tab)
- DIR request forms (opens in a new tab)
- DIR eligibility overview (opens in a new tab)
- DIR templates and provider workbooks (opens in a new tab)
- DIR certified cloud products (opens in a new tab)