Current through Register Vol. 49, No. 8, August 19, 2024
Subdivision 1.Definitions.(a) For the purposes of this chapter, the following terms have the meanings given them.(b) "Information and telecommunications technology systems and services" means all computing and telecommunications hardware and software, the activities undertaken to secure that hardware and software, and the activities undertaken to acquire, transport, process, analyze, store, and disseminate information electronically. "Information and telecommunications technology systems and services" includes all proposed expenditures for computing and telecommunications hardware and software, security for that hardware and software, and related consulting or other professional services.(c) "Telecommunications" means voice, video, and data electronic transmissions transported by wire, wireless, fiber-optic, radio, or other available transport technology.(d) "Cyber security" means the protection of data and systems in networks connected to the Internet.(e) "State agency" means an agency in the executive branch of state government and includes the Minnesota Office of Higher Education, but does not include the Minnesota State Colleges and Universities unless specifically provided elsewhere in this chapter.(f) "Total expected project cost" includes direct staff costs, all supplemental contract staff and vendor costs, and costs of hardware and software development or purchase. Breaking a project into several phases does not affect the cost threshold, which must be computed based on the full cost of all phases.(g) "Cloud computing" has the meaning described by the National Institute of Standards and Technology of the United States Department of Commerce in special publication 800-145, September 2011.Subd. 2.Chief information officer's responsibility. The chief information officer shall: (1) design a strategic plan for information and telecommunications technology systems and services in the state and shall report on the plan to the governor and legislature at the beginning of each regular session;(2) develop and implement processes for review, approval, and monitoring and oversee the state's information and telecommunications technology systems and services;(3) establish and enforce compliance with standards for information and telecommunications technology systems and services that are cost-effective and support open systems environments and that are compatible with state, national, and international standards, including accessibility standards;(4) maintain a library of systems and programs developed by the state for use by agencies of government;(5) direct and manage the shared operations of the state's information and telecommunications technology systems and services; and(6) establish and enforce standards and ensure acquisition of hardware, software, and services necessary to protect data and systems in state agency networks connected to the Internet.Subd. 3.Evaluation and approval. A state agency may not undertake an information and telecommunications technology project or initiative until it has been evaluated according to the procedures developed under subdivision 4. The chief information officer or delegate shall record project approval as a part of the project.Subd. 4.Evaluation procedure. The chief information officer shall establish and, as necessary, update and modify procedures to evaluate information and communications projects or initiatives proposed by state agencies. The evaluation procedure must assess the necessity, design and plan for development, ability to meet user requirements, accessibility, feasibility, cost, and benefits of the project or initiative.Subd. 4a.Cloud computing services.The project evaluation procedure required by subdivision 4 must include a review of cloud computing service options, including any security benefits and cost savings associated with purchasing those service options from a cloud computing service provider. When projects involve cloud computing services, the state chief information officer shall, in consultation with the Technology Advisory Council, establish metrics to assess the progress of any cloud computing project for each state agency.
Subd. 5.Report to legislature. The chief information officer shall submit to the legislature, at the same time as the governor's budget required by section 16A.11, a concise narrative explanation of any information and communication technology project or initiative being proposed as part of the governor's budget that involves collaboration between state agencies and an explanation of how the budget requests of the several agencies collaborating on the project or initiative relate to each other.Subd. 5a.Cloud computing progress report.(a) No later than January 15, 2024, and annually thereafter, the state chief information officer shall, in consultation with the Technology Advisory Council, report on the progress of executive branch cloud adoption to the chairs and ranking members of the legislative committees with jurisdiction over executive branch information technology policy. The report shall include, but not be limited to, the following: (1) an accounting of each state agency's expenditures for cloud computing initiatives and software as service solutions; and(2) cost projections, timelines, and the names of any cloud provider selected for current computing projects that incorporate cloud computing solutions, and percentage of total cloud use.(b) This subdivision expires December 31, 2027.Subd. 6.System development methods.The chief information officer shall establish and, as necessary, update and modify methods for developing information and communications systems appropriate to the specific needs of individual state agencies. The development methods shall be used to define the design, programming, and implementation of systems.
Subd. 7.Cyber security systems.(a) In consultation with the attorney general and appropriate agency heads, the chief information officer shall develop cyber security policies, guidelines, and standards, and shall advise, implement, and administer state data security solutions and practices on the state's information technology services, systems, and applications consistent with these policies, guidelines, standards, and state law to ensure the integrity, confidentiality, and availability of information technology systems and services, and data and to ensure applicable limitations on access to data, consistent with the public's right to know as defined in chapter 13. The chief information officer is responsible for overall security of state agency networks connected to the Internet. Each department or agency head is responsible for the security of the department's or agency's data within the guidelines of established enterprise policy.(b) The state chief information officer, or state chief information security officer, may advise and consult on security strategy and programs for state entities and political subdivisions not subject to section 16E.016..Subd. 8.[Repealed, 2014 c 271 art 4s 7]
Subd. 9.Accessibility standards.(a) The chief information officer shall develop accessibility standards applicable to technology, software, and hardware procurement, with the exception of infrastructure hardware. The standards shall not impose an undue burden on the state.(b) The chief information officer shall require state agencies to adhere to the standards developed under this subdivision unless an exception is approved pursuant to subdivision 10. Except as provided in paragraph (c), the standards developed under this section must incorporate section 508 of the Rehabilitation Act, United States Code, title 29, section 794d, as amended by the Workforce Investment Act of 1998, Public Law 105-220, August 7, 1998, and the Web Content Accessibility Guidelines, 2.0. The chief information officer must review subsequent revisions to section 508 of the Rehabilitation Act and to the Web Content Accessibility Guidelines and may incorporate the revisions in the accessibility standards.(c) If the chief information officer determines that any standard developed under this subdivision poses an undue burden to the state, the chief information officer may modify the burdensome standard, provided written findings and rationale are made explaining the deviation.Subd. 10.Exceptions to accessibility standards.Exceptions to the standards may be granted by the chief information officer based upon a request by an agency.
Subd. 11.Technical support to legislature.The chief information officer, or a designee, must provide technical support to assist the legislature to comply with accessibility standards under section 3.199, subdivision 2. Support under this subdivision must include:
(1) clarifying the requirements of the accessibility standards;(2) providing templates for common software applications used in developing documents used by the legislature;(3) assisting the development of training for staff to comply with the accessibility standards and assisting in providing the training; and(4) assisting the development of technical applications that enable legislative documents to be fully accessible. The chief information officer must provide these services at no cost to the legislature.
1997 c 202 art 3 s 9; 1997 c 212 s 3, 4; 1998 c 359 s 15; 1998 c 366 s 42-45; 1999 c 250 art 1 s 114; 2005 c 107 art 2 s 60; 2005 c 156 art 5 s 9-12; 2008 c 318 art 1 s 9; 2009 c 101 art 2s 109; 2009 c 131s 8-11; 2014 c 271 art 4 s 2
Amended by 2024 Minn. Laws, ch. 123,s 17-20, eff. 8/1/2024.Amended by 2024 Minn. Laws, ch. 123,s 17-19, eff. 8/1/2024.Amended by 2024 Minn. Laws, ch. 123,s 17-18, eff. 8/1/2024.Amended by 2024 Minn. Laws, ch. 123,s 17-17, eff. 8/1/2024.Amended by 2024 Minn. Laws, ch. 123,s 17-16, eff. 8/1/2024.Amended by 2023 Minn. Laws, ch. 62,s 6-12, eff. 7/1/2023.Amended by 2023 Minn. Laws, ch. 62,s 6-11, eff. 7/1/2023.Amended by 2023 Minn. Laws, ch. 62,s 6-10, eff. 7/1/2023.Amended by 2021 Minn. Laws, ch. 31,s 2-8, eff. 8/1/2021.Amended by 2021 Minn. Laws, ch. 31,s 2-7, eff. 8/1/2021.Amended by 2021 Minn. Laws, ch. 31,s 2-6, eff. 8/1/2021.Amended by 2021 Minn. Laws, ch. 31,s 2-5, eff. 8/1/2021.Amended by 2019 Minn. Laws, ch. 10,s 5-2, eff. 8/1/2019.Amended by 2019 Minn. Laws, ch. 10,s 5-4, eff. 5/31/2019.Amended by 2019 Minn. Laws, ch. 10,s 5-3, eff. 8/1/2019.Amended by 2019 Minn. Laws, ch. 50,s 1-12, eff. 8/1/2019.Amended by 2019 Minn. Laws, ch. 50,s 1-11, eff. 8/1/2019.Amended by 2014 Minn. Laws, ch. 271,s 4-7, eff. 8/1/2014.Amended by 2014 Minn. Laws, ch. 271,s 4-2, eff. 8/1/2014.