The state chief information officer is responsible for a planning framework to collaboratively develop and publish information technology standards and guidelines.
These standards guide architecture, design, engineering and procurement of solutions, software, networks, hardware and services.
The standards apply to North Carolina state agencies that fall under the authority given to the state chief information officer in N.C.G.S. 143B Article 15.
Other state agencies and local governments are also encouraged to use these standards and guidelines.
Current IT standard areas are:
- Desktop configuration
- Domain management
- Geographic information services
- Identity and access management
- IT project management
- Vendor engagement resources
For desktop configuration standards, please contact NCDIT Operations Support at ITS_Tier3_Operations@its.nc.gov.
The state chief information officer strives to simplify electronic transactions with North Carolina state government. The state CIO is required to ensure this happens in a secure manner. This is accomplished through authentication of users and controlled access to applications and services.
To achieve this, the state CIO requires all interagency and external-facing solutions and applications that create content use the state’s identity and access management solution, NCID.
NCID is used to integrate with numerous systems to synergize the end-user experience by providing authentication and authorization for state applications and solutions.
All solutions requiring NCID authentication must externalize identity and access management and support the following protocols:
- Security Assertion Markup Language (SAML v2)
- Lightweight Directory Access Protocol (LDAP)
- Web Services (SOAP/WSDL)
As existing solutions are upgraded or replaced, they will be required to support the above protocols.
A formal exception is required to use a solution other than NCID. The agency must provide just cause for the exception to be approved.
The exception form can be found on https://it.nc.gov/documents/exception-resources.