Security Hub at work in Tatarbunary

For two years now a Security Coordination Hub has been operating in the city of Tatarbunary, Odesa Oblast, searching for new resources and building up city security together with stakeholders.

The Human Rights Information Center took a look at what Tatarbunary has achieved so far.

All activities related to security development in Tatarbunary are based at the Security Coordination Hub. It was established in February 2017 by civil society activist Leonid Semenenko.

Igor Brynosh, deputy chairman of the Odesa regional  NGO "Committee of Voters of Ukraine", notes the activist’s important role in the Hub’s creation. This man had worked at the bodies of the Ministry of Internal Affairs and the Ministry of Justice since 1974, his career spanning from inspector of the child's room at the police to deputy head of the district department of the Ministry of Internal Affairs. In 1998, Leonid Semenenko retired in the rank of lieutenant colonel of the police. After that and until 2015 he was chief of district justice department, and today, according to Igor Brynosh, he carries great respect in the community.

Since the Hub’s inception two years ago, 20 security-related organizations in the city have signed memorandums of cooperation, to name a few: Tatarbunary Rayon Council, Tatarbunary Rayon State Administration, Tatarbunary City Council, Tatarbunary Police Department, State Emergency Service office, rayon office of the State Migration Service, as well as the Kosatska Varta (Cossack Guard) NGO created to uphold public order.

The Hub’s principle of operation is joint work and responsibility for security in the city, shared among the police, other government bodies, local authorities and residents.

© 2017 All rights reserved.
This site is created and operated with the support of the International Foundation Vidrodzhennia. The site is administered by the Human Rights Information Center.
WARNING! This site performs the informational and educational function. The site is not an analogue of the service "102" and does not fulfill the function of prompt response.