📜 ⬆️ ⬇️

ARM CBD-N - Day X will come soon, who did not prepare himself to blame

Transfer of Bank of Russia clients to new ARMs - replacement of the ARMKBB:
The planned deadline for the migration to the new PC ARM KBR-N is June 28, 2019 .

After a nonsmooth start of the exchange through the TSh KBR, I began to study the road map of the Bank of Russia more thoroughly, in terms of new complexes.

The Bank of Russia rejected some of its functions (in terms of supplying participants in software exchange to perform the full range of exchange functions in the UEFEBS ).

On the website of the Bank of Russia , there is documentation on new software packages.
')
As it turned out, the AWS of the CBD-N is a highly neutered edition.

Now when exchanging through the AWS of the CBD, you can organize a full-featured exchange of packages, see the picture.



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



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


With these functionals it is simpler, they are already finalized or will be finalized by the software developers of the AU-Client.

What to do with those functions that left the old AWP of the CBD and did not appear in the new AWP of the CBD-N:


There is an online resource on the AWP of the CBD-N (I advise you to look at it) , but there are no references to software solutions for replacing the missing functionality of the AWS of the CBD.

I found three suitable candidates for replacing the old ARM of the CBD (complexes not integrated into the AU-client):


There are links to NGOs Krista and Diasoft , but these are modules to the complexes existing at the client (of their own design).

For some time it will be possible to work with the old ARM -KBR, but most likely the complex of the ARM -KBR will not be able to function after a change in the format of the UBBS.

The transition to additional software is definitely needed, you cannot write packages for UBEBS formats in a “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. Purchases of domestic software, will touch the part of 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 to develop cryptographic tools, or in this case it is not needed (as a requirement for procurement)?
  3. What is the procedure for commissioning software of unknown origin, for 44-FZ it is not known what you will get - will you buy from someone who will sell cheaper?
  4. How to catch up to 06.28.2019 based on paragraphs 1-3.

Source: https://habr.com/ru/post/452980/


All Articles