From December 4, 2018, logging into the Treasury-Client Information System and signing digital signature documents will only be possible using NCALayer software. And judging by the number of visitors and comments, many issues still require improvement. Let's consider what and how...

1. open “Module management” by selecting the appropriate item in context menu NCALayer.

After that, click on the “Restart” button.

If after this a window appears asking you to install a certificate, agree.

now try to log into the treasury client login to the treasury client

typical mistakes:

"Error generating request"
"Error verifying certificate"

— Several certificates are installed on one external media (below are instructions for removing expired and ineffective certificates)

— The certificate is expired

— Certificate canceled

How to check the number of certificates installed on your external storage device and remove those that are not valid?

You can check this on the website http://pki.gov.kz .

Attention! Only 1 certificate per user should be stored on external media (1 certificate contains 2 GOST, RSA keys).

Go to the page “EDS key verification service”

A window with a list of keys will appear

Attention! If you have multiple certificates on the same external media, you must remove all expired and ineffective certificates. To do this, select the certificate and click on “Delete key”

After removing expired and non-valid certificates from the drop-down list, only 1 certificate with 2 keys (GOST, RSA) should be displayed.

If you use several keys on one computer

Each time you change the user, you must restart NCALAyer or use different keys on a different computer. For example, the Chief Accountant works on one, and the Director on another. And you don’t need to switch the token every time. All you need to do is move from one computer to another.

What should you do if you are working with the Internet Explorer browser, versions 8, 9, 10, and when you click “Login” nothing happens?

You need to update your browser to version 11. If you have windows 8.1 or 10, then everything is fine, it’s already there InternetExplorer 11 versions. In Windows 7 you can upgrade to version 11, but as a rule this is such a pain in the ass that it’s easier to reinstall the system to 8.1 or 10. I can add: Internet Explorer 11 is needed for the stat module and, as a rule, for one time. It’s easier to find a computer with the required version and use the stat module, and then, when the time comes, update...

What should you do if you are using the Mozilla Firefox browser, and when you click the icon to sign a document, a pop-up window opens and immediately closes?

You need to download and install root certificates on the NCA RK website (http://www.pki.gov.kz). To do this, click on the links “root_rsa”, “pki_rsa”.

If the “Download certificate” window appears, then check the box next to “Trust when identifying websites” and click “OK”. If not, download and save the file.

After installing the certificates from the links, you need to install the certificates from the files in the Mozilla Firefox browser. To do this, open “Settings” through the Firefox menu. Next, select “Privacy and Security”, and in the certificates section, click on “View certificates...”. The Manage Certificates window will open. In the “Certification Authorities” tab, click on “Import...” and select the previously downloaded KUTS certificate file - NEGIZGI KUOLANDYRUSHY ORTALYK (RSA). In the window that appears, check the box next to “Trust when identifying websites.” and click "OK".

Also import the NCA certificate - ULTTYK KUALANDYRUSHY ORTALYK (RSA), but in the window that appears, without selecting anything, click “OK”.

What should you do if, when you click the icon to sign a document, a certificate selection window opens, but your work computer cannot recognize your external media type (KazToken/eToken/JaCarta)?

If your work computer cannot recognize your external storage device, you need to reboot the computer with the dongle connected to it. Or try on another computer. Or use the Info Token utility

How to determine what external storage device you have? (Kaztoken, eToken, JaCarta)

The name of the external media (Kaztoken, eToken, JaCarta) is written on the body of the device itself.

If you have an operating system Windows 7 or higher, and July 1, 2017 has arrived and you still cannot log into the Treasury-Client IS and a message appears stating that it is impossible to display the page - do this: Shown using Internet Explorer 11 as an example

So, you need to go to the Tools menu - Internet Options

On the Advanced tab
Include items
"Use TLS 1.1"
"Use TLS 1.2"

That's it, you can try logging into the treasury client

The same settings must be made with JAVA for correct signing. As a rule, these protocols are already included in JAVA, but you can check them.

Launch a Java program through the Control Panel in Windows

Then, on the Advanced tab, look to see if the Use TLS 1.1 and Use TLS 1.2 items are checked. If not, mark as in the picture below

that's all for sure now

client kazynashylyk kz
client kazynashylyk kz entrance

Client treasury client kazynashylyk kz
client kazynashylyk kz 10443
https client kazynashylyk kz
client treasury client kazynashylyk kz entrance
client kazynashylyk kz 10443 tc auth
https client kazynashylyk kz 10443
https client kazynashylyk auth kz 10443
https client kazynashylyk kz 10443 tc auth
www client kazynashylyk kz
http client kazynashylyk kz
www client kazynashylyk kz login +login
client kazynashylyk kz oa html
https client kazynashylyk kz oa
www client kazynashylyk kz 10443
client kazynashylyk kz login +login 10443
www client kazynashylyk kz 10443 tc auth
client kazynashylyk kz 10043 tc auth
client treasury client kazynashylyk kz 10443
http www client kazynashylyk kz
client kazynashylyk kz download
http client kazynashylyk kz 10443

IT infrastructure

• Support for the IT infrastructure of the Federal Treasury of Russia

Import substitution of information systems in the Federal Treasury

Chronicle of informatization

2018

* Deputy Head of the Treasury Alexander Albychev on TAdviser SummIT - about the mega-project of moving government agencies to cloud accounting

Creation of IT infrastructure based on data centers of the Federal Tax Service

In July 2016, the structure of the Federal Tax Service of Russia "Nalog-Service" announced an auction for the creation of a hardware and software complex for the Federal Treasury in a reserve data center located in Gorodets in the Nizhny Novgorod region (RDDC No. 1). More details about the project can be found at the link.

2015: OTR-2000 and Lanit are the largest IT suppliers of the year

Every year, the Federal Treasury spends 7-8 billion rubles on informatization, occupying one of the leading positions among federal government agencies in terms of this indicator.

In September 2015, TAdviser analyzed the purchases of the Federal Treasury in order to determine its largest suppliers of IT products and services. Tenders from 2010-2015 were taken into account, the amount of which exceeds 50 million rubles.

Data: TAdviser analytical center, September 2015

The main IT contractors of the Treasury - OTR and Lanit companies, in addition to supplying ready-made equipment and software, are developing and maintaining the main information system

Information system "Treasury-client" (hereinafter referred to as IS KK, System) is an information system of the Treasury Committee of the Ministry of Finance of the Republic of Kazakhstan and its territorial divisions (hereinafter referred to as the Treasury), providing automation of functions for receiving and processing documents .

IS QC is a set of functional qualities that ensure effective and efficient management of the Government's financial resources and control over budget execution. The system covers all levels of the Treasury, and ensures functional interaction with government organizations, the National Bank, payment systems, ministries, akimats, budget program administrators and government agencies.

Clients of IS QC are government agencies, administrators of budget programs, and entities of the quasi-public sector.

Target

Increasing the efficiency of interaction between the Treasury and government agencies served by providing a modern, integrated and highly efficient information environment. It is a component of the Treasury Information Integrated System.

Tasks

• ensures effective and efficient management of the Government's financial resources and control over budget execution;
• increasing the speed of service to government agencies;
• effective management of public finances;
• monitoring the status of electronic documents submitted by government agencies to the Treasury;

System advantages

Connected to the CC IS 12 856 government agencies, including 315 quasi-public sector entities. 35 134 active users carry out operations in real time in the Treasury information system, performing procedures for crediting and spending state budget funds.

Data: Number of processed (paid) documents through the “Treasury - Client” IS system as of 01/01/2017:
29 184 110 accounts payable;
2 146 141 applications for registration of civil transactions ;
658 375 plans and certificates of changes;
152 071 payment orders of quasi-public sector entities;
235 806 payment orders of Territorial Tax Authorities, etc.

Conducted daily on average 30 thousand payments from the Kazakhstan Center for Interbank Settlements and on average 40 thousand budget revenues. At the end of the month, these indicators double, because during this period the main payments by government agencies (salaries, benefits, taxes, etc.) are made.

Since the main task of IS QC is the timely execution of financial transactions, even in conditions of increasing load on system performance, IS “Treasury - Client” provides the opportunity to collaborate in a unified information environment of the Treasury Committee. In self-service mode, government agencies fill out electronic document forms. After verification, approval and approval, these documents automatically become available in the integrated Treasury information system.

Thanks to the “Treasury - Client” IS:

• the speed of servicing government institutions has increased;
• administrative barriers have decreased;
• the “human factor” is minimized;
• reduced paper consumption
• time and transportation costs for government agencies have also been reduced.

Integration

In order to eliminate the repeated entry of electronic documents in State institutions, integration with the subsystem “Accounting”, “Budget Application” of the IAIS “e-MINFIN” has been implemented.

In 2016, the integration of the “Treasury - Client” Information System with the Automated Integrated Information System “Electronic Public Procurement” (AIIS “EGP”) was put into trial operation.

Integration of AIIS "EGZ" with the Information System "Treasury - Client" made it possible to structure data on each transaction completed within the framework of public procurement and ensure prompt receipt of data on payments under contracts. Thus, significantly expanding the possibilities for analyzing transactions.

Integration with the Information System for the receipt and processing of electronic invoices, and the Information System “Centralized Unified Personal Account (IS CULS of the Tax Committee of the Ministry of Finance of the Republic of Kazakhstan)” allows you to quickly accept invoices from the IS ESF and payment orders from the IS CULS for execution in the Treasury.

By providing government agencies with reliable and timely financial information for decision-making, the Treasury Information System is the basis for effective public financial management.

IS "Treasury - Client" will provide control over the implementation of budget procedures at all budget levels and stages of the budget process, including local budgets and executive bodies.

AND THE NATIONAL CERTIFICATION CENTER

REPUBLIC OF KAZAKHSTAN

Astana, 2012

Chapter 3. Application of digital signature 13

Chapter 4. Ensuring information security requirements 15

Chapter 5. Hardware and software requirements 16

Chapter 6. Division of responsibilities 17

Chapter 7. Procedure for resolving disputes between the Treasury and the Client related to the authenticity of electronic documents 18

8. APPENDICES TO THE ORDER:

20. Appendix 1. Agreement on the use of digital signature between the treasury and the Client.

20.1. Appendix 1.1. Power of attorney for transfer of digital signature to an authorized person who has the right to sign financial documents.

21. Appendix 2. Policy for the use of registration certificates and digital signatures of users of the “Treasury-Client” information system

22. Appendix 3. Additional agreement on the use of electronic digital signature between the treasury and the Client

23. Appendix 4. Act on the destruction of revoked registration certificates and private EDS keys

24. Appendix 5. User agreement on the use of electronic document management with the Client “Treasury-Client”.

Terms and definitions used in this Procedure
The terms used in the text of this Procedure are used in the following interpretation:

Information system “Treasury-Client” (hereinafter referred to as the System) is an electronic document management system of the Treasury Committee of the Ministry of Finance of the Republic of Kazakhstan and territorial divisions of the Treasury (hereinafter referred to as the Treasury) with government agencies, administrators of budget programs, authorized government bodies, entities of the quasi-public sector (hereinafter referred to as the Client );

Electronic document – ​​a document in which information is presented in electronic digital form and certified using an electronic digital signature;

Registration data – data required to obtain a registration certificate from the NCA, in accordance with the Policy for the use of registration certificates and digital signatures of users of the “Treasury-Client” information system;

Private (secret) EDS key - a sequence of electronic digital symbols known to the owner of the registration certificate and intended for creating an EDS using electronic digital signatures;

EDS public key – a sequence of electronic digital symbols, accessible to any person and intended to confirm the authenticity of the EDS in an electronic document;

Signatory – an individual or legal entity who legally owns the private digital signature key and has the right to use it in an electronic document;

System User - a person in whose name the right to use an electronic signature is registered with the NCA and who has the corresponding private digital signature key that allows signing electronic documents;

Authentication – establishing the authenticity of one or more aspects of information interaction: a communication session, its time, communicating parties, transmitted messages, data source, time of data creation, data content;

Identification – assigning an identifier to subjects and objects of access or comparing the presented identifier with the list of assigned identifiers;

A key container is a file on a key medium (disk, flash card, e-token, etc.) where public and private keys are located;

Certificate storage – a list of information characterizing the user of the cryptographic system (list of certificates) and lists of revoked certificates;

Confirmation of the authenticity of an electronic signature in an electronic document is a positive result of confirmation by an electronic signature tool that the digital signature contained in the electronic document belongs to its owner and the absence of distortion or forgery of the electronic document signed by this digital signature;

Digital signature tools - hardware and/or software used to create and verify the authenticity of digital signatures;

Registration certificate (Law of the Republic of Kazakhstan “On Electronic Documents and Electronic Digital Signatures” dated January 7, 2003 No. 307-II) is a document on paper or an electronic document issued by a certification center to confirm compliance of an electronic digital signature with the requirements established by this Law. The context uses a synonym for the expression “public key certificate”;

The National Certification Center of the Republic of Kazakhstan (hereinafter referred to as NCA RK) is a structural subdivision of the Joint Stock Company “National Information Technologies” (hereinafter referred to as JSC NIT), which certifies the compliance of the public key of the EDS with the private key of the EDS, as well as confirming the authenticity of the registration certificate in the relations “state body of the Republic of Kazakhstan - state body of the Republic of Kazakhstan" (G2G), "state body of the Republic of Kazakhstan - economic entity" (G2B), "state body of the Republic of Kazakhstan - citizen of the Republic of Kazakhstan" (G2C);

NTC Registration Centers (hereinafter referred to as RC NTC) are structural divisions of JSC NIT, carrying out, in accordance with the Rules, registration, issuance, storage, revocation (cancellation) of registration certificates, including their copies on paper and maintaining a register of registration certificates approved by order of the Chairman Agency of the Republic of Kazakhstan for Informatization and Communications dated December 8, 2005 No. 457-p, operations for identification, authentication, verification of the powers of registration certificate holders in the production, issuance and revocation of a registration certificate.

Chapter 1. Introduction

1. general information

1. System Participants

• 
  Treasury Department;
• 
  Client;
• 
  NCA, the main components of which are Certification Centers and Registration Centers;

1. Information about the purpose of the System

The subject of automation is the Treasury functions of receiving and processing documents provided by the Client. The function of providing the Treasury with data and reports to Clients is also subject to automation.

The system provides:

• 
  creation of electronic forms of documents submitted by the Client to the territorial divisions of the Treasury;
• 
  carrying out checks of format and logical control of the correctness of filling out electronic forms of documents;
• 
  use of digital signature to certify your authorship, as well as the integrity of electronic documents created by Clients;
• 
  sending by the Client electronic documents completed and secured with digital signature;
• 
  reception and primary processing of electronic documents provided by the Client to the Treasury;
• 
  transfer of received electronic documents to the integrated information system of the Treasury (hereinafter referred to as ICS);
• 
  monitoring the status of electronic documents provided by the Client to the Treasury;
• 
  presentation to Clients of data in the established format and reports within the competence of the Treasury;
• 
  exchange of electronic messages (Treasury-client, Client-treasury).

• 
  based on the use of modern highly efficient technologies for storing and processing information, unify, simplify and speed up automated data entry for documents processed in ISK;
• 
  increasing the efficiency, accuracy, reliability, and transparency of data related to the procedures for submitting documents to treasury authorities;
• 
  the use of modern electronic digital signature information security tools to confirm the authenticity of documents and simplify the process of document approval.

1. Electronic documents secured with digital signature and interaction between System users

All electronic documents created by the Client and sent through the System must be executed in accordance with the requirements of the current budget legislation in form, completeness and correctness of completion, and signed with the digital signature of the authorized Manager of the Client and the Head of the Client’s financial group (or an employee of the authorized body) who have the right signatures in accordance with samples of signatures and seal imprints stored in the Treasury in the file of the government institution (Client).

When receiving an electronic document through the System, the Treasury checks the presence of an electronic signature and verifies the ownership of the digital signature against the provided sample signatures. If the data matches, the document is recognized as having legal force and equivalent to a document on paper with handwritten signatures of the authorized Manager of the Client and the Head of the Client's financial group, sealed with an official seal. Such a document is subject to further verification for compliance with the requirements of the current budget legislation of the Republic of Kazakhstan in terms of form, completeness and correctness of completion. If any discrepancies are found, the electronic document is returned to the Client indicating the reasons for the return.

Attached files can only be in the following formats:

1. 
   pdf, txt
2. 
   doc, docx
3. 
   xls, xlsx
4. 
   graphic image format (jpeg, gif, tiff, bmp, png and others).

In this case, in accordance with the functional responsibilities performed, System users will be assigned the following roles:

ROLE00 – System Administrator;

ROLE10 – the Client’s manager, or a person authorized by him, who has the right to sign all financial documents of a government institution (hereinafter referred to as the GI);

ROLE11 – Client’s Manager, who has the right to sign invoices for payment, applications for foreign currency conversion, applications for reconversion of foreign currency, applications for transfer of money in foreign currency of the State Administration and applications for entering the recipient of money in the Directory of recipients of money in national and foreign currency;

ROLE12 – Client’s Manager, who has the right to sign applications for registration of civil transactions (hereinafter referred to as the Civil Transactions Register) of the Civil Code and applications for entering the recipient of money into the Directory of Recipients of Money;

ROLE13 – Client’s Manager, who has the right to sign State Funding Plans and certificates for amending them;

ROLE14 – Client’s Manager, who has the right to generate all financial documents (for a State Enterprise that does not have a financial service);

ROLE15 – Executive Secretary of the central executive body (Head of the Administrator of Budget Programs) for approval of State Funding Plans and certificates for making changes to them;

ROLE20 – Head of the Client’s financial group (chief accountant), or a person authorized by him, who has the right to sign all financial documents of the Client;

ROLE21 – Head of the Client’s financial group (chief accountant), who has the right to sign invoices for payment, applications for foreign currency conversion, applications for reconversion of foreign currency, applications for transfer of money in the Client’s foreign currency and applications for entering the recipient of money in the Directory of recipients of money in the national and foreign currency;

ROLE22 – Head of the Client’s financial group (chief accountant), who has the right to sign applications for registration of the State Registration Service and applications for entering the recipient of money into the Directory of Recipients of Money;

ROLE23 – Head of the Client’s financial group (chief accountant), who has the right to sign State Funding Plans and certificates for making changes to them;

ROLE27 – employee authorized by the head of a government agency to maintain accounting records (accountant, freelancer)

ROLE03 – authorized employee of the Tax Committee;

ROLE04 – authorized employee of the Accounts Committee for control over the execution of the Republican Budget;

ROLE05 – authorized employee of the Agency of the Republic of Kazakhstan for Combating Economic and Corruption Crime (financial police);

ROLE01 – Head of the Tax Authority or a person authorized by him, who has the right to sign on payment orders and on all financial documents of the State Administration;

ROLE02 – authorized employee of the Tax Authority who has the right to sign payment orders – head of a structural unit;

ROLE06 – authorized employee of the budget programs administrator;

ROLE07 – authorized employee of the local authorized body for state planning;

ROLE08 – authorized employee of the local authorized body for budget execution;

ROLE09 – authorized employee of the territorial tax authority;

ROLE28 – employee of the authorized body responsible for collecting budget revenues;

ROLE29 – authorized employee of the territorial division of the Customs Control Committee (CTC);

ROLE30 – authorized employee of the Financial Control Committee (FCC);

ROLE31 – authorized employee of the Tax Committee (TC) (reporting);

ROLE32 – authorized employee of the Tax Authority, without the right to sign on the payment order – respondent;

ROLE50 - Client's Manager, who has the right to sign all financial documents of a quasi-public sector entity (hereinafter - SCS);

ROLE51 – Head of the Client’s financial group (chief accountant), who has the right to sign all financial documents of a quasi-public sector entity;

ROLE52 – an employee authorized by the head of a quasi-public sector entity to maintain accounting records (accountant, freelancer).
Accordingly, System users must have DC fields equal to the corresponding System user role in the DN of the registration certificate name.

1. Procedure for accepting electronic documents

The Treasury accepts paper documents from the Client in the following cases:

For the period of production, re-issuance and revocation of the personal digital signature key of the System user;

Lack of technical ability to connect to the System.

Chapter 2. Operational requirements for the organization of life cycle processes of the registration certificate

1. Application for issuance of a registration certificate

To start working in the System, all applicants (Clients) must sign the form of the Agreement on the use of an electronic digital signature between the Treasury and the Client (hereinafter referred to as the Agreement) approved by the Treasury in 3 copies, in accordance with Appendix No. 1 to the Procedure, and also fill out the Template for providing data for each user of the System in accordance with Appendix 3 to the Policy for the Application of Registration Certificates of Authentication and EDS of users of the Information System “Treasury - Client” of the CC MF RK, (hereinafter referred to as PPRS). In this case, one original of the signed Agreement is stored in the Treasury in the file of a government agency/subject of the quasi-public sector (hereinafter referred to as the Client), the second is kept by the Client, the third original must be transferred to the operator of the CR NCA when submitting an application for the issuance of a registration certificate. The last two copies are stamped by the responsible executor of the general group of the territorial division of the treasury (hereinafter referred to as TPK).

The agreement must be signed by the head of the GU/SKS, who has the right of first signature according to the sample signatures provided to the TPK.

A government agency/SCS serviced in a TPK located closer in location and serving another administrative-territorial unit, and not in a TPK according to the administrative-territorial division (according to the Directory of government institutions/quasi-public sector entities), must:

1. 
   To work in the Treasury-Client IS, provide to the TPK according to the administrative-territorial division (according to the Directory of government agencies/quasi-public sector entities) the original Agreement and the original sample signatures and seal imprint;
2. 
   If documents are submitted on paper in accordance with paragraph 5 of this Procedure to the nearest TPK, provide a copy of the Agreement and the original sample signatures and seal imprint, which are filed in the dossier of the government agency

Re-production of EDS keys under this Agreement is possible only if there is a failure in the disk, or an operator error was made during the production of the EDS key.

The agreement is concluded:

1. 
   with persons who have the right to sign in accordance with the samples of signatures and seal impressions stored in the Treasury in the Client’s legal file;
2. 
   with persons who do not have the right to sign:

1. 
   employees authorized by the head of a government agency to maintain accounting records (accountant, freelancer)
2. 
   authorized employees of other government bodies in accordance with the functional responsibilities specified in paragraph 4 of the Procedure.

The agreement and the data presented in the Template are the basis for the further process of registration and production in the CR NUC, located at the Public Service Center, which consists of the following steps:

• 
  submission of an application for the issuance of a registration certificate to the CR NCA by the user of the System with the provision of documents proving the identity of the applicant;
• 
  authentication of the applicant by an authorized employee of the CR NCA;
• 
  in case of successful authentication, the information placed in the applicant’s request is checked and private signature keys and a registration certificate of the applicant’s public key are produced at the NCA of the Republic of Kazakhstan.

• 
  two private keys of the owner of the registration certificate (GOST 34.310-2004 for affixing an electronic signature and RSA for authentication);
• 
  two registration certificates in the form of an electronic document (GOST 34.310-2004 for affixing an electronic signature and RSA for authentication);
• 
  a copy of the owner's registration certificate on paper (at the request of the System user);
• 
  registration certificate of the Certification Authority - NCA RK (root certificate).

In case of expiration of EDS keys, the Client must:

Destroy the registration certificate, EDS private key and authentication, while the Client draws up an Act on the destruction of the revoked registration certificate and EDS private keys, in accordance with Appendix 4 to the Procedure;

Conclude an Additional Agreement on the use of an electronic digital signature between the Treasury and the Client, in accordance with Appendix No. 3 to the Procedure for the further re-issuance of the registration certificate and private EDS keys;

Provide the Additional Agreement to the Public Service Center with the Application for the issuance of a registration certificate, with identification documents of the applicant and a Template for providing data.

The above information is transferred to the applicant to the CR NCA against signature in a special journal for recording issued registration certificates.

In case of loss of digital signature keys, the Client must be guided by the second paragraph of clause 7 and the first paragraph of clause 6 of the Procedure.

After authentication in the “Treasury-Client” information system, the System user signs an electronic image of the User Agreement on the use of electronic document management with the Client (Treasury-Client) (hereinafter referred to as the User Agreement) in accordance with Appendix No. 5 to the Procedure.

The user agreement is formed only in electronic form and is not provided to the territorial divisions of the treasury.

1. Procedure for revoking a registration certificate

The System user, in the event of dismissal, exclusion from the order of persons who have the rights to sign in accordance with the sample signatures and seal imprints, a change in his job responsibilities or detection of the theft of an electronic digital signature, is obliged no later than the date of his dismissal, exclusion from his job responsibilities of the right to sign documents or detection the fact of theft of the digital signature, provide, in accordance with the PPRS, an application for the revocation of the issued registration certificate and the corresponding personal private key of the digital signature and destroy your private key after losing authority in this institution. The client, when destroying the private key of the system user, approves by internal order the composition of the commission for the destruction of the revoked registration certificate and the private digital signature key. When destroying the revoked registration certificate of the System user's private key (for authentication and digital signature), an Act on the destruction of the revoked registration certificate and private digital signature keys is drawn up, in accordance with Appendix 4 to the Procedure, a copy of which is submitted to the Treasury for storage in a separate folder, according to the nomenclature of cases.

To revoke the registration certificate of a public key, the System user fills out an application for revocation of the registration certificate in accordance with the PPRS and submits it to the NCA CR.

NCA RK, after receiving an application for revocation of the registration certificate, carries out its consideration and processing in accordance with the PPRS.

Registration certificates must be used as part of interaction with the regulatory documents of the Treasury.

1. Registration of the System in the world space of object identifiers (OID)

Logging into the System with a certificate that has a different OID is not possible.

Chapter 3. Application of digital signature

1. Terms of use of digital signature

Digital signature is the result of cryptographic transformation of information and has the following properties:

• 
  The digital signature is reproducible only by the owner of the signature key certificate;
• 
  The digital signature is inextricably linked with a specific electronic document in the System.

1. Conditions for the equivalence of the digital signature of a handwritten (personal) signature

• 
  the authenticity of the digital signature is verified using a public key that has a registration certificate;
• 
  the person who signed the electronic document lawfully owns the private EDS key;
• 
  The digital signature is used in accordance with the information specified in the registration certificate.

Private EDS keys cannot be transferred to other persons without the consent of the owners of these keys.

The System user has the right to transfer the authority to use the digital signature to his authorized representative, who has the right to sign financial documents, on the basis of the issued Power of Attorney in the prescribed form, in accordance with Appendix No. 1.1. to this Agreement, within one organization on the basis of an internal order of the Client. During the validity of the power of attorney, the System user (principal) must not use the private digital signature and authentication key. Upon expiration of the power of attorney, the System user (principal) automatically receives the right to use the private digital signature and authentication key. The Client must keep records of issued powers of attorney.

1. Electronic digital signature verification

1. 
   Verification that the certificate, the private key of which is signed by the document being verified, was issued by a trusted Certification Authority - NCA RK.
2. 
   Checking for revocation of a certificate whose private key is signed by a document. If a certificate is revoked, the certificate serial number will be missing.
3. 
   Checking the value of the “Certificate Application” field: “digital signature, non-repudiation” is written in the “Certificate Application” field.
4. 
   Checking for the presence of the System OID in the certificate, OID must have the value in the authentication certificate OID = 1.2.398.5.19.1.2.2.1.3, as well as in the digital signature registration certificate OID = 1.2.398.5.19.1.2.2.1.2.

Chapter 4. Ensuring information security requirements

1. General information

The objects of protection are EDS keys and electronic documents of the System.

To prevent theft, loss, distortion, forgery of electronic documents, and other unauthorized actions for their destruction, modification, copying by System users, the Client must take organizational measures to protect digital signature funds and electronic documents.

Private EDS keys must be stored on removable media and connected only when signing electronic documents.

1. Recommendations for ensuring safe operation in the System

1. 
   Log in only through the corporate website https://client.kazynashylyk.kz;
2. 
   It is strictly forbidden to respond to letters purporting to be on behalf of the System with demands (requests, offers) to go to a site that does not belong to the domain https://client.kazynashylyk.kz and send a secret key;
3. 
   Store EDS keys on two different removable media – primary and backup (USB tokens, floppy disks, flash drives, CDs). Do not store on your computer's hard drive;
4. 
   The procedure for storing removable digital signature media must exclude the possibility of unauthorized access to them by unauthorized persons;
5. 
   Do not allow unauthorized persons to access your personal computer with the system loaded or while it contains a removable drive containing a secret key;
6. 
   Remove removable media containing the secret digital signature key from the computer immediately after completing work in the System;
7. 
   Once a week, change the workstation login password, but it is prohibited to use a password containing personal data (date of birth, full name, etc.);
8. 
   Do not disclose the password to enter the workstation to unauthorized persons or other employees (regardless of their position);
9. 
   Use anti-virus protection tools on the workstation with the ability to automatically update anti-virus databases;
10. 
    Prevent access to computers used to work in the System by unauthorized persons and personnel of the organization not authorized to work in the System and/or maintain computers;
11. 
    On computers used to work in the System, exclude visiting all Internet sites except those used to log into the System, and also exclude the installation of entertainment and gaming programs;
12. 
    Use only licensed software (operating systems, office suites, etc.);
13. 
    Connect a medium with a private EDS key only at the time of signing electronic documents. Use the medium to store only the private EDS key, do not use the medium to store other files;
14. 
    When installing an authentication key on a computer, be sure to set a password; however, it is prohibited to use a password that contains personal data (date of birth, full name, etc.).

Chapter 5. Hardware and software requirements

1. Technical requirements

• 
  processor no less than Intel Pentium 1GHz:
• 
  RAM no less than 512 MB;
• 
  free part of the hard drive of at least 150 MB;
• 
  monitor with a screen resolution of at least SVGA 800x600.

1. Software requirements

Operating system:

• 
  Not lower than Microsoft Windows XP.

• 
  Sun JDK/JRE -1.6 Version 6 Update12 or higher;
• 
  Tumar CSP V4.2;
• 
  Internet Explorer 6 (SP1) or higher;
• 
  Microsoft Office 2003 or higher;
• 
  Adobe Acrobat Reader 7 or higher;
• 
  Scanner: 300 dpi extension and support for gif, jpg, png formats.

1. Data network requirements

The bandwidth of the local network used for data transfer for the user of the Treasury-Client software must be at least 128 Kbps, the recommended is 256 Kbps.

The capacity of the external Internet line must ensure sufficient speed of document transmission for all System users during peak hours.

Chapter 6. Division of Responsibility

1. Responsibility of the Treasury

The Treasury is responsible for the functioning of the System, as well as timely notification of the Client about all changes in the operation of the System.

The Treasury is not responsible for any damage, losses or other losses incurred by the Client due to the System User’s failure to comply with the requirements specified in paragraphs. 7, 10, and non-compliance with the requirements of paragraphs 13, 14, 15, 16 of this Procedure.

The Treasury is not responsible for any damage, loss or other losses incurred by the Client due to improper execution of the Procedure by the System user, manuals and instructions relating to work in the System, for the timely destruction of the EDS key by the User and the unlawful use of the EDS.

1. Responsibility of the System User

The System User is responsible for the proper storage of the issued certificate and key, and for the timely destruction of the key by the Digital Digital Signature User.

The System user, as the owner of the EDS key, in the event of unauthorized use of the EDS bears full responsibility in accordance with the legislation of the Republic of Kazakhstan.

Chapter 7. Procedure for resolving disputes between the Treasury and the Client related to the authenticity of electronic documents

1. Settlement of disputes

If both parties do not come to an agreement, the Client and the Treasury can contact the NCA of the Republic of Kazakhstan to issue an opinion on the current situation and provide evidence of the signature or resolve this issue in accordance with the legislation of the Republic of Kazakhstan.