K1
One-Page Campaign Page
Characteristics: A single page contains information about activities or programs, does not store data, has no user accounts, and is short-lived.
Examples: Event anniversary warning page, program assistance information page, event announcement page.
Prescribed technologyStatic pages (HTML and CSS) or static page generators such as Hugo or Astro, using official Regional Government templates. Content management systems are only permitted if they use an official theme.
Hosting locationShared hosting owned by Diskominfo
Data storageDoes not use a database
User sign-inNone; all content is open to the public
Security testingAutomated scanning before publishing
BackupsWeekly
Recovery time2 business days
Vendor workYes, or independently with a template
ApprovalHead of Telematics Division
Standard stackHugo or Astro static page result · regional identity template · without database · shared hosting · automatic certificate
Specific prohibitions
- Loading forms that collect population identification numbers or other personal data; if necessary, the category rises to K3 or K5.
K2
Standard Category Profile and News Portal
Characteristics: Contains profiles, news, agendas, galleries, and public documents; its content is regularly updated; does not serve transactions.
Examples: Official agency website, regional government news portal, public information disclosure page.
Prescribed technologyPrimary choice for a centralized agency portal managed by Diskominfo. If independent: WordPress version still supported, with themes and plugins from the approved list.
Hosting locationCentralized portal or shared hosting
Data storageMySQL 8.4 LTS or MariaDB 11.4 LTS on the Diskominfo database group
User sign-inOnly content managers; mandatory agency account and two-factor authentication
Security testingAutomated scanning before publishing and annual retesting
BackupsDaily, stored for fourteen days
Recovery time1 business day
Vendor workYes, for display only
ApprovalHead of Telematics Division
Standard stackLatest WordPress version · official regional theme · MariaDB 11.4 LTS on the database group · PHP 8.4 · Nginx · daily backup
Specific prohibitions
- Installing themes or plugins from unofficial sources or without licenses
- Modifying core system content management parts
- Disabling security updates
K3
Light Forms and Services
Characteristics: Collects one-way submissions without user accounts, data is not sensitive, and has a limited lifespan.
Examples: Activity participant registration, satisfaction surveys, proposal intake, activity file collection.
Prescribed technologyGovernment Regional Managed Service. If needs exceed the service capacity, it is built as a lightweight application following all K4 regulations.
Hosting locationManaged Service or Hosted Environment
Data storageDiskominfo Database Group, not files within the application server
User sign-inNone, or limited links
Security testingAutomated scanning; if personal data is loaded, it becomes K5.
BackupsDaily during activity operation
Recovery time1 business day
Vendor workYes
ApprovalHead of Telematics Division
Standard stackRegional Managed Form Service; if built independently, it follows K4 structure with the smallest resource package.
Specific prohibitions
- Using third-party online form services outside of Diskominfo supervision for personal data.
K4
Internal Information System for Regional Government Agencies
Characteristics: Used by employees for internal tasks, has user accounts, does not store personal citizen data, and does not directly serve the public.
Examples: Inventory recording, letter management, event scheduling, program achievement monitoring.
Prescribed technologyPHP Route: PHP 8.3 or newer with Laravel 12. JavaScript Route: Node.js 22 LTS with TypeScript. React 19 View with Vite 6 or built-in framework template.
Hosting locationSeparate server provided by Diskominfo, running in a managed container
Data storagePostgreSQL 17 as the primary choice, or MySQL 8.4 LTS, on database groups; not within the application server
User sign-inMandatory integrated agency account; user lists created only with dispensation
Security testingTesting before release and annual re-testing
BackupsDaily, stored for fourteen days, copied outside of the application server
Recovery time8 working hours
Vendor workYes, delivery through repository
ApprovalHead of Telematics Division
Standard stackPHP Route: PHP 8.4 + Laravel 12 + PostgreSQL 17 + Redis + Nginx in Docker container. JavaScript Route: Node.js 22 LTS + TypeScript + NestJS + PostgreSQL 17 + Redis. React 19 View + Vite · access through the integrated agency account
Specific prohibitions
- Passwords and keys written in code
- Database placed within the application server
- Development environment merged with the service environment
K5
Public and Transactional Services System
Characteristics: Accessed by the public, contains personal data such as population number and copies of documents, and generates official outputs in the form of letters, permits, or payment receipts. All K4 regulations apply.
Examples: Permitting service registration, community complaints, student enrollment, and trade fee payments.
Prescribed technologyK4 framework, plus three separate environments, data encryption, object storage for files, and electronic signatures on output documents.
Hosting locationSeparate server with three environments: development, testing, and production
Data storagePostgreSQL 17 with personal data encrypted when stored and transmitted
User sign-inIntegrated agency account for internal use and citizen accounts for the public
Security testingFull penetration testing before deployment, every major change, and annually
BackupsDaily with a six-month recovery test
Recovery time4 hours; data loss no more than 24 hours
Vendor workYes, with restricted data access
ApprovalHead of Telematics Division together with Head of Security and Communication Division
Standard stackK4 Framework · three separate environments · data encryption · file object storage · electronic signatures on output documents · 24/7 monitoring
Specific prohibitions
- Vendors holding copies of service data
- Citizen data stored on private cloud services
- Notifications sent via individual personal email accounts
- Citizen data copied to the development environment
K6
Cross-Agency Strategic System
Characteristics: Used by more than one agency, serving as a foundation for services or decision-making, or storing master data used by other systems. All K5 regulations apply.
Examples: Regional personnel system, planning and finance system, population and territory master data, shared use system between agencies.
Prescribed technologyK5 architecture, plus two load-balanced service servers, replicated database, and program interface gateways for data exchange between systems.
Hosting locationMore than one server with load balancing
Data storageReplicated PostgreSQL 17
User sign-inIntegrated agency account plus system-specific inter-system keys
Security testingSame as K5, plus program interface testing against user systems
BackupsDaily plus offsite backup
Recovery time2 hours, with notification to all using agencies
Vendor workYes, with business continuity plan
ApprovalHead of Office
Standard stackK5 Architecture · two load-balanced service servers · replicated database · program interface gateways for data exchange between systems
Specific prohibitions
- Data exchange via direct connections to the database
- Major changes without fourteen days prior notice
K7
Dashboard and Data Presentation
Characteristics: Presents data for leadership or the public, does not generate new data.
Examples: Development achievement dashboard, open data portal, monitoring display on a control room.
Prescribed technologyRegional data portal or dashboard application that complies with K4 regulations. Graph presentation using libraries included in the list are permitted.
Hosting locationData portal or separate server
Data storageSource from designated validators, not repeated manual copies
User sign-inOpen to public data; data is limited only after logging in with a department account
Security testingOnce a year, plus verification that restricted data cannot be accessed without permission
BackupsFollows the source
Recovery time1 business day
Vendor workYes
ApprovalHead of Statistics Division together with Head of Telematics Division
Standard stackK4 structure with emphasis on read-only · source data from validators · permitted graph libraries
Specific prohibitions
- Displaying individual data that can identify individuals on public dashboards.
K8
Mobile Companion Application
Characteristics: Supplementary to existing systems, built only when truly necessary with camera, location, or direct notification on the phone.
Examples: Field monitoring application, attendance scanning application, citizen reporting application.
Prescribed technologyFirst choice is a web application that can be installed on the main screen of the phone. If native development is required: Supported Flutter version, one code for two platforms.
Hosting locationOfficial app store owned by the Regional Government
Data storageDoes not have its own database; all data is taken from the master system through the program interface.
User sign-inFollowing the master system
Security testingFollowing the master system
BackupsNot applicable
Recovery timeFollowing the master system
Vendor workYes, publication by Diskominfo
ApprovalFollowing the master system
Standard stackInstallable web application; if native, latest stable Flutter release that calls the master system program interface
Specific prohibitions
- Publishing applications under a vendor or individual account
- Storing signing keys outside of Diskominfo
- Sharing installation files outside official channels without approval.