Software from the register
Operating systems, office suites and mail from the register of trusted software. We plan the migration calendar so the institution never stops.
We handle both the hardware and the paperwork. One does not work without the other: equipment without the orders and policies leads an inspection straight to an enforcement notice.
Operating systems, office suites and mail from the register of trusted software. We plan the migration calendar so the institution never stops.
Selecting and configuring security tools, preparing for compliance testing, writing the threat model.
Documentation on processing citizens' data, hosting databases inside the country, permissions by role and logging of requests.
Servers and storage, internal networks and cabling, private channels between buildings and subordinate sites, data archives.
Websites with the sections required for publication, a separate low-vision version and integration with departmental systems.
We maintain the hardware fleet under contract, register tickets, close each month with acts and prepare reports.
Most of our help comes before the announcement: we write the technical specification, provide a price offer for the budget calculation and word the description so it does not have to be redone after the first request for clarification.
We count the hardware, go through the licences and assess the security. What has to change first is marked separately.
We write the description of the item without brand names and prepare a price offer for the budget calculation.
We enter tenders, auctions or requests for price offers and assemble the bid by the deadline.
We do the work under contract and hand over the as-built documentation together with the acts.
We do not charge for a price offer. Send us a draft specification or simply describe the need, and we will format it to the requirements for supporting materials.
After the work you are left with a folder of documents you can show both to an inspector and to your parent organisation.
Ready in five working days. Useful when planning the purchase and defending the budget.
Written before security tools are purchased. Required under the unified requirements and determines exactly what has to be purchased.
Assembled in ten working days. Every inspection starts with this folder.
Issued following compliance testing. Without this document the system will not be put into production use.
Every month. Needed for the institution's reporting and for accepting the work.
The documents belong to the institution, not to the contractor. The report, the threat model and the set of orders are written so anyone can follow them. That helps when another company wins the next procurement.
We will. We write the description without naming brands so the wording does not conflict with the public procurement law or give grounds for complaints.
We can. We select from the register of trusted software and, during the survey, check compatibility with your applications and hardware in advance so the migration does not stop work.
We do not run them ourselves. We prepare the system: review the paperwork, tune the safeguards and close the gaps found. The testing is done by an authorised body, and we handle the correspondence with them.
Yes, including cases with several organisations that need one template: identical kits, shared security rules and a consolidated report across all sites.
On completion of each stage, against signed acts and within the deadlines in the contract. We take an advance only where the procedure expressly provides for it.
Опишите задачу или пришлите проект технической спецификации. Подготовим предложение и расчёт для обоснования суммы закупки.
Request received
It is already with a manager. You will get an answer within the working day, and urgent requests go to the duty engineer immediately.
There is no such city in the list. Check the spelling.