AWP KBR-N - Day X will come soon, who did not prepare himself to blame

Transfer of Bank of Russia customers to new AWS - replacement of AWS KBR: The
planned deadline for migration to the new AWP KBR-N PC is 06/28/2019 .

After a non-smooth launch of the exchange through TSH KBR, he began to study the road map of the Bank of Russia more carefully in terms of new complexes.

The Bank of Russia has discarded some of the functions (in terms of supplying participants in the exchange of software to perform the entire range of exchange functions under the UFBS ).

On the website of the Bank of Russia , the documentation for new software packages has been posted.

As it turned out AWP KBR-N is a highly neutered publication.

Now, when exchanging through AWS of the CBD, it is possible to organize a fully functional exchange of packages, see the picture.



AWP KBR-N only encrypts (decrypts) and sends (receives) packets to (from) TSB KBR, see the picture.



There is a set of functions that will definitely not be implemented in the new PC complex AWP KBR-N:

• formation of signatures of the LC;
• formation of spacecraft signatures.

With these functionalities it’s easier, they have already been finalized or will be finalized by the AS-Client software developers.

What to do with those functions that have left the old AWS KBR and have not appeared in the new AWS KBR-N:

• storage during the operational day of transmitted and received ES
• linking sent ES and ES responses and changing the state of sent ES in accordance with the received ES;
• search for received ES, their display and printing (with electronic signature verification);
• visualization of ES processing processes.
• ... much more from the old workstation of the CBD

There is an Internet resource on the topic AWP KBR-N (I advise you to look) , but there are no links to software solutions to replace the missing functionality of AWP KBR.

I found three suitable candidates for replacing the old AWS KBR (complexes not integrated into the AC client):

• Astrasoft “ASTRA-KBR” and “ASTRA-KBR_GUI”;
• OTR PK “Interaction with BR”;
• QUORUM EDSmart;

There are links to NGOs Krista and Diasoft , but these are modules for the complexes existing in the client (their own development).

For some time it will be possible to work with the old AWP-KBR, but most likely the AWP-KBD complex will not be able to function after changing the UFBS formats.

The transition to additional software is definitely necessary; you can’t write packages in UFEBS formats in the “notepad”.

Maybe there are other, ready-made and tested solutions? I would be glad if someone reports links to them!

Along the way, more questions surfaced:

1. The purchase of domestic software will affect some customers trading in 44-FZ, the Unified Register of Russian programs for electronic computers and databases , something I did not find there.
2. Do developers have a FSB license for the development of cryptographic tools, or in this case it is not needed (as a requirement for the purchase)?
3. What is the order of acceptance into operation of software of unknown origin, according to 44-FZ it is not known what you will get - will you buy from someone who sells cheaper?
4. How to make it before 06/28/2019 based on p.1-3.