Extyl. Web and mobile with unlimited warranty. Extyl-PRO
Адрес: Derbenevskaya street, 20, 115114 115114 Moscow,
Телефон:+7 495 995–23–37, Электронная почта: info@extyl-pro.ru
Every day from 9:30 till 20
array(1) { ["ID"]=> array(1) { [2433]=> string(4) "2433" }
}
string(34) "---------------------------------1"
array(1) { [2433]=> array(1) { ["ITEMS"]=> array(1) { [0]=> array(49) { ["DATE_CREATE"]=> string(19) "06/03/2020 16:57:42" ["~DATE_CREATE"]=> string(19) "06/03/2020 16:57:42" ["ID"]=> string(5) "16117" ["~ID"]=> string(5) "16117" ["IBLOCK_ID"]=> string(2) "46" ["~IBLOCK_ID"]=> string(2) "46" ["IBLOCK_SECTION_ID"]=> string(4) "2433" ["~IBLOCK_SECTION_ID"]=> string(4) "2433" ["NAME"]=> string(35) "#46. Security of client information" ["~NAME"]=> string(35) "#46. Security of client information" ["ACTIVE_FROM"]=> NULL ["~ACTIVE_FROM"]=> NULL ["TIMESTAMP_X"]=> string(19) "06/03/2020 17:00:00" ["~TIMESTAMP_X"]=> string(19) "06/03/2020 17:00:00" ["DETAIL_PAGE_URL"]=> string(52) "/library/security/46-security-of-client-information/" ["~DETAIL_PAGE_URL"]=> string(52) "/library/security/46-security-of-client-information/" ["LIST_PAGE_URL"]=> string(17) "/library/library/" ["~LIST_PAGE_URL"]=> string(17) "/library/library/" ["DETAIL_TEXT"]=> string(1062) "Customers give us access to their servers and other systems and the question arises: how to store this securely while having convenient and flexible access.
The worst option is to store such data in public sources, such as a wiki project.

A good option is to use specialized password managers. These are good and secure solutions, some of the solutions available on the market provide various integrations for embedding in your infrastructure.

However, if you need to store other data besides passwords, off-the-shelf software will not work. Plus, the problem of embedding in the current landscape. We solved the problem by writing our manager on top of Bitrix24, where we conduct projects.

The next problem is how to protect yourself from using passwords when you are fired, leaked, etc.?

The solution is quite obvious, and automation is quite simple. The secret storage system is able to dynamically change passwords on protected resources: once a stolen password will be invalid in a few hours.
" ["~DETAIL_TEXT"]=> string(1012) "Customers give us access to their servers and other systems and the question arises: how to store this securely while having convenient and flexible access. The worst option is to store such data in public sources, such as a wiki project. A good option is to use specialized password managers. These are good and secure solutions, some of the solutions available on the market provide various integrations for embedding in your infrastructure. However, if you need to store other data besides passwords, off-the-shelf software will not work. Plus, the problem of embedding in the current landscape. We solved the problem by writing our manager on top of Bitrix24, where we conduct projects. The next problem is how to protect yourself from using passwords when you are fired, leaked, etc.? The solution is quite obvious, and automation is quite simple. The secret storage system is able to dynamically change passwords on protected resources: once a stolen password will be invalid in a few hours. " ["DETAIL_TEXT_TYPE"]=> string(4) "text" ["~DETAIL_TEXT_TYPE"]=> string(4) "text" ["PREVIEW_TEXT"]=> string(244) "Customers give us access to their servers and other systems and the question arises: how to store this securely while having convenient and flexible access.
The worst option is to store such data in public sources, such as a wiki project." ["~PREVIEW_TEXT"]=> string(239) "Customers give us access to their servers and other systems and the question arises: how to store this securely while having convenient and flexible access. The worst option is to store such data in public sources, such as a wiki project." ["PREVIEW_TEXT_TYPE"]=> string(4) "text" ["~PREVIEW_TEXT_TYPE"]=> string(4) "text" ["PREVIEW_PICTURE"]=> NULL ["~PREVIEW_PICTURE"]=> NULL ["LANG_DIR"]=> string(1) "/" ["~LANG_DIR"]=> string(1) "/" ["CODE"]=> string(33) "46-security-of-client-information" ["~CODE"]=> string(33) "46-security-of-client-information" ["EXTERNAL_ID"]=> string(5) "16117" ["~EXTERNAL_ID"]=> string(5) "16117" ["IBLOCK_TYPE_ID"]=> string(4) "news" ["~IBLOCK_TYPE_ID"]=> string(4) "news" ["IBLOCK_CODE"]=> string(0) "" ["~IBLOCK_CODE"]=> string(0) "" ["IBLOCK_EXTERNAL_ID"]=> NULL ["~IBLOCK_EXTERNAL_ID"]=> NULL ["LID"]=> string(2) "en" ["~LID"]=> string(2) "en" ["EDIT_LINK"]=> NULL ["DELETE_LINK"]=> NULL ["DISPLAY_ACTIVE_FROM"]=> string(0) "" ["FIELDS"]=> array(1) { ["DATE_CREATE"]=> string(19) "06/03/2020 16:57:42" } ["PROPERTIES"]=> array(1) { [" "]=> &NULL } ["DISPLAY_PROPERTIES"]=> array(0) { } ["IPROPERTY_VALUES"]=> array(0) { } } } } } string(34) "---------------------------------2"
array(1) { [2433]=> array(6) { ["ID"]=> string(4) "2433" ["~ID"]=> string(4) "2433" ["NAME"]=> string(8) "Security" ["~NAME"]=> string(8) "Security" ["ACTIVE"]=> string(1) "Y" ["~ACTIVE"]=> string(1) "Y" }
}
string(40) "---------------------------------------3"
Security

#46. Security of client information

Customers give us access to their servers and other systems and the question arises: how to store this securely while having convenient and flexible access.
The worst option is to store such data in public sources, such as a wiki project.


Make a request
Specialist rates

Front-end: $25

Back-end: $25 (PHP), $35 (JAVA, C#), $35 (Ruby, Python)

Analytics: $35 — $45

Mobile: $30

Design: $25 (designer), $35 (Art Director)

DevOps: $30

Testing: $20