Plain-English Summary
Utah cybersecurity requirements usually reach contractors through the contract, solicitation, statement of work, data-use terms, technology approval process, or statewide IT policy—not always through a standalone cybersecurity statute. For a contractor, the practical question is whether the work touches state data, state systems, cloud or software services, confidential records, personal information, or agency-managed technology.
This page separates binding sources from background guidance. A source matters to your company when it applies directly to vendors or when an agency incorporates it into a solicitation, purchase order, master agreement, statement of work, data-use agreement, security exhibit, or other contract document.
What Contractors Should Check First
Before bidding on or performing a Utah contract, confirm:
- whether the work involves state data, personal information, confidential records, cloud services, software-as-a-service, network-connected products, or access to a state system;
- which state Chief Information Officer (CIO), Chief Information Security Officer (CISO), technology-office, or procurement-office policies apply to the purchase;
- whether standard terms add cybersecurity, privacy, incident-reporting, audit, insurance, subcontractor, or flowdown duties; and
- what evidence the agency expects, such as a security plan, data inventory, access-control records, incident contact, vendor questionnaire, security assessment, approval record, or subcontractor flowdown.
How To Read This Page
Direct contractor duty means the source applies to vendors, service providers, contractors, or handlers of state data. Agency duty that affects vendors means the source binds the state agency but changes what the agency must require from contractors. Contract clause / flowdown means the duty usually becomes binding when it appears in the solicitation, contract, master agreement, data-use agreement, or statement of work. Background only means the source helps explain the state's cybersecurity or procurement environment but does not, by itself, impose a contractor duty.
At-a-Glance Contractor Map
| Area | What to verify | Evidence to keep |
|---|---|---|
| State data | Whether the work uses state data, personal information, confidential records, or agency records. | Data inventory, data-flow map, access list, return/destruction record. |
| State systems | Whether employees, subcontractors, tools, or cloud services connect to state systems. | Access approvals, account list, logging evidence, offboarding records. |
| Technology procurement | Whether the purchase requires IT approval, security review, architecture review, or procurement-office approval. | Solicitation questions, approvals, exceptions, security questionnaire, evaluation submissions. |
| Contract terms | Whether cybersecurity, privacy, incident reporting, audit, insurance, and subcontractor duties are incorporated. | Clause matrix, flowdown terms, subcontractor certifications, incident contact list. |
Cybersecurity statutes (background)
Utah source materials in the uploaded archive did not clearly identify a standalone contractor-facing cybersecurity statute for this page. Security requirements appear to flow primarily through procurement documents, IT policies, privacy/breach laws, or contract terms.
Regulations, Policies & Standards
These entries cover regulations, procurement manuals, IT policies, security standards, contract templates, terms and conditions, and agency guidance that may become binding when incorporated into a solicitation, purchase order, master agreement, statement of work, data-use agreement, or other contract document.
Attachment-B-IT-Standard-Terms-and-Conditions-11-Jan-2024-2-1
Category. `PROC-IT` Authority type. State government source. Contractor nexus. Contract clause / flowdown; direct vendor relevance when incorporated into the solicitation or contract.
In plain terms. This source explains how Utah buys technology, services, software, hardware, cloud offerings, or related support. For contractors, it tells you where security requirements may enter the deal: the solicitation, evaluation criteria, standard terms, approval process, or contract documents.
Who it applies to. It applies to state purchasing officials and agencies, and it affects vendors that sell technology, data services, software, equipment, professional services, cloud services, or support to the state.
What it requires. Contractors should read the solicitation and all incorporated documents together. Confirm security representations, privacy terms, audit rights, insurance, subcontractor approval, data ownership, return or destruction terms, and incident-notice provisions before submitting a bid or signing the contract.
Why it matters. Procurement rules and standard terms often create the real contractor-facing cybersecurity duties. They can affect eligibility, responsiveness, evaluation, award, contract administration, payment, and post-award oversight.
Citation. Attachment-B-IT-Standard-Terms-and-Conditions-11-Jan-2024-2-1
C63G-6a 1800010118000101 Utah Procurement Code
Category. `PROC-IT` Authority type. State government source. Contractor nexus. Contract clause / flowdown; direct vendor relevance when incorporated into the solicitation or contract.
In plain terms. This source explains how Utah buys technology, services, software, hardware, cloud offerings, or related support. For contractors, it tells you where security requirements may enter the deal: the solicitation, evaluation criteria, standard terms, approval process, or contract documents.
Who it applies to. It applies to state purchasing officials and agencies, and it affects vendors that sell technology, data services, software, equipment, professional services, cloud services, or support to the state.
What it requires. Contractors should read the solicitation and all incorporated documents together. Confirm security representations, privacy terms, audit rights, insurance, subcontractor approval, data ownership, return or destruction terms, and incident-notice provisions before submitting a bid or signing the contract.
Why it matters. Procurement rules and standard terms often create the real contractor-facing cybersecurity duties. They can affect eligibility, responsiveness, evaluation, award, contract administration, payment, and post-award oversight.
Citation. C63G-6a 1800010118000101 Utah Procurement Code
Data Privacy - Utah Design System
Category. `PRIV` · `ETXN` Authority type. State government source. Contractor nexus. Direct contractor duty may exist when the contractor handles covered data; also likely to flow through data-use or confidentiality terms.
In plain terms. This source governs personal information, privacy, or data-handling duties. For contractors, it matters when the contract gives the company access to personal information, resident data, employee data, program records, health information, education records, financial records, or other protected data.
Who it applies to. It may apply to state agencies, businesses, service providers, contractors, or data handlers depending on the text and the contract. A contractor should not assume it is exempt just because the source is not a procurement law.
What it requires. Contractors should identify what data the company receives, whether the data is personal or confidential, how the contract restricts use and disclosure, who may access the data, when notice is required, and how data must be returned or destroyed at the end of performance.
Why it matters. Privacy duties can create breach-notice, confidentiality, audit, indemnity, termination, or enforcement exposure. They also affect subcontractor management and the evidence a contractor should preserve.
Citation. Data Privacy - Utah Design System
DTS 2022-2025 Strategic Plan Final
Category. `PROC-IT` Authority type. State government source. Contractor nexus. Contract clause / flowdown; direct vendor relevance when incorporated into the solicitation or contract.
In plain terms. This source explains how Utah buys technology, services, software, hardware, cloud offerings, or related support. For contractors, it tells you where security requirements may enter the deal: the solicitation, evaluation criteria, standard terms, approval process, or contract documents.
Who it applies to. It applies to state purchasing officials and agencies, and it affects vendors that sell technology, data services, software, equipment, professional services, cloud services, or support to the state.
What it requires. Contractors should read the solicitation and all incorporated documents together. Confirm security representations, privacy terms, audit rights, insurance, subcontractor approval, data ownership, return or destruction terms, and incident-notice provisions before submitting a bid or signing the contract.
Why it matters. Procurement rules and standard terms often create the real contractor-facing cybersecurity duties. They can affect eligibility, responsiveness, evaluation, award, contract administration, payment, and post-award oversight.
Citation. DTS 2022-2025 Strategic Plan Final
R895-7 Acceptable Use of IT Resources
Category. `PROC-IT` Authority type. State government source. Contractor nexus. Contract clause / flowdown; direct vendor relevance when incorporated into the solicitation or contract.
In plain terms. This source explains how Utah buys technology, services, software, hardware, cloud offerings, or related support. For contractors, it tells you where security requirements may enter the deal: the solicitation, evaluation criteria, standard terms, approval process, or contract documents.
Who it applies to. It applies to state purchasing officials and agencies, and it affects vendors that sell technology, data services, software, equipment, professional services, cloud services, or support to the state.
What it requires. Contractors should read the solicitation and all incorporated documents together. Confirm security representations, privacy terms, audit rights, insurance, subcontractor approval, data ownership, return or destruction terms, and incident-notice provisions before submitting a bid or signing the contract.
Why it matters. Procurement rules and standard terms often create the real contractor-facing cybersecurity duties. They can affect eligibility, responsiveness, evaluation, award, contract administration, payment, and post-award oversight.
Citation. R895-7 Acceptable Use of IT Resources
TCAgencyGoods-7.20.23-RS
Category. `GOV` Authority type. State government source. Contractor nexus. Agency duty that affects vendors; may become a contractor duty through contract incorporation, system access, or technology approval.
In plain terms. This source identifies who in Utah government has authority over information technology, security policy, technology approval, or statewide digital operations. For contractors, that matters because the responsible office often controls the standards an agency must include in technology contracts.
Who it applies to. It primarily applies to state agencies and state technology officials. Contractors are affected when an agency uses that authority to set solicitation requirements, contract terms, security reviews, approval gates, or data-handling conditions.
What it requires. Contractors should use this source to identify the office that can require security documentation, technology approval, architecture alignment, data-protection terms, or compliance with statewide IT policies. Before bidding, map the solicitation to the responsible CIO, CISO, procurement, or technology office and preserve the approval record.
Why it matters. State IT governance sources often explain why a solicitation contains cybersecurity terms even when the statute does not mention contractors directly. Missing the governing office or approval path can create bid, performance, payment, or acceptance risk.
Citation. TCAgencyGoods-7.20.23-RS
TCAgencyGoodsServices-7.20.23-RS
Category. `GOV` Authority type. State government source. Contractor nexus. Agency duty that affects vendors; may become a contractor duty through contract incorporation, system access, or technology approval.
In plain terms. This source identifies who in Utah government has authority over information technology, security policy, technology approval, or statewide digital operations. For contractors, that matters because the responsible office often controls the standards an agency must include in technology contracts.
Who it applies to. It primarily applies to state agencies and state technology officials. Contractors are affected when an agency uses that authority to set solicitation requirements, contract terms, security reviews, approval gates, or data-handling conditions.
What it requires. Contractors should use this source to identify the office that can require security documentation, technology approval, architecture alignment, data-protection terms, or compliance with statewide IT policies. Before bidding, map the solicitation to the responsible CIO, CISO, procurement, or technology office and preserve the approval record.
Why it matters. State IT governance sources often explain why a solicitation contains cybersecurity terms even when the statute does not mention contractors directly. Missing the governing office or approval path can create bid, performance, payment, or acceptance risk.
Citation. TCAgencyGoodsServices-7.20.23-RS
TCAgencyServices-7.20.23-RS
Category. `GOV` Authority type. State government source. Contractor nexus. Agency duty that affects vendors; may become a contractor duty through contract incorporation, system access, or technology approval.
In plain terms. This source identifies who in Utah government has authority over information technology, security policy, technology approval, or statewide digital operations. For contractors, that matters because the responsible office often controls the standards an agency must include in technology contracts.
Who it applies to. It primarily applies to state agencies and state technology officials. Contractors are affected when an agency uses that authority to set solicitation requirements, contract terms, security reviews, approval gates, or data-handling conditions.
What it requires. Contractors should use this source to identify the office that can require security documentation, technology approval, architecture alignment, data-protection terms, or compliance with statewide IT policies. Before bidding, map the solicitation to the responsible CIO, CISO, procurement, or technology office and preserve the approval record.
Why it matters. State IT governance sources often explain why a solicitation contains cybersecurity terms even when the statute does not mention contractors directly. Missing the governing office or approval path can create bid, performance, payment, or acceptance risk.
Citation. TCAgencyServices-7.20.23-RS
TermsPOGoodsServices-7.20.23-RS
Category. `PROC-IT` Authority type. State government source. Contractor nexus. Contract clause / flowdown; direct vendor relevance when incorporated into the solicitation or contract.
In plain terms. This source explains how Utah buys technology, services, software, hardware, cloud offerings, or related support. For contractors, it tells you where security requirements may enter the deal: the solicitation, evaluation criteria, standard terms, approval process, or contract documents.
Who it applies to. It applies to state purchasing officials and agencies, and it affects vendors that sell technology, data services, software, equipment, professional services, cloud services, or support to the state.
What it requires. Contractors should read the solicitation and all incorporated documents together. Confirm security representations, privacy terms, audit rights, insurance, subcontractor approval, data ownership, return or destruction terms, and incident-notice provisions before submitting a bid or signing the contract.
Why it matters. Procurement rules and standard terms often create the real contractor-facing cybersecurity duties. They can affect eligibility, responsiveness, evaluation, award, contract administration, payment, and post-award oversight.
Citation. TermsPOGoodsServices-7.20.23-RS
Cross-State Procurement Context
NASPO and NASCIO materials are useful background for how states think about cybersecurity in public procurement. They support a practical approach: build security requirements into acquisition planning, solicitations, evaluation, contract terms, and post-award vendor oversight. They are not binding Utah law unless a Utah statute, regulation, policy, solicitation, or contract adopts them.
For GovConCyber implementation, use this callout to help readers understand why a state may ask for cybersecurity documentation even when the state code is not written like a federal cybersecurity clause. Do not cite NASPO, NASCIO, CIS, or StateRAMP materials as the source of a binding state requirement unless the specific state has adopted or incorporated them.
Cross-state procurement context
NASPO and NASCIO materials are useful background for how states think about cybersecurity in public procurement. They support a practical approach: build security requirements into acquisition planning, solicitations, evaluation, contract terms, and post-award vendor oversight. They are not binding Utah law unless a Utah statute, regulation, policy, solicitation, or contract adopts them.