How UP Tombou Digitally Transformed with Nebosystems (Presented at InfoSec SEE 2025)

Post Syndicated from Dora original https://nebosystems.eu/how-up-tombou-digitally-transformed-with-nebosystems/

About UP Tombou

UP Tombou is one of Bulgaria’s leading providers of food vouchers, gift cards and employee benefit solutions, serving thousands of businesses nationwide for over 30 years.

But despite their strong market presence, Tombou’s internal IT infrastructure was holding them back.

The Challenge: Legacy Systems and Poor IT Support

Prior to partnering with Nebosystems, Tombou faced serious IT hurdles:

  • Outdated and fragmented infrastructure
  • Inconsistent and slow internal IT support
  • Missed deadlines and operational delays
  • Poorly maintained documentation and weak security practices
  • No disaster recovery or business continuity strategy

These weaknesses posed serious risks — both to operations and compliance.

The Turning Point: Partnering with Nebosystems

In early 2024, Tombou signed a long-term contract with Nebosystems to fully manage and modernize their IT environment. The goal: build a secure, scalable and compliant digital infrastructure to support their expanding operations.

Infrastructure Modernization

Nebosystems began with a foundational rebuild:

  • Proxmox host cluster for virtualization and high availability
  • Enterprise-grade IBM storage systems
  • Local and offsite backup systems with automated disaster recovery
  • Regular disaster recovery testing to validate data integrity and recovery speed
  • Implementation of an ISO 27001-compliant Business Continuity Plan (BCP)
  • Modernized network with MikroTik routers, managed switches, and a Next-Gen Firewall

This laid the groundwork for operational resilience and compliance.

Endpoint Security with Bitdefender EDR

Security was a key priority. Bitdefender EDR was deployed across all Windows endpoints, enabling:

  • Real-time threat detection and prevention
  • Centralized policy control for compliance and auditing
  • Defense against ransomware, zero-days, and targeted attacks
  • Automatic alerting to security incidents

This fulfilled essential ISO 27001 requirements while raising the security baseline across the company.

Full Audit & Control with Netwrix

Visibility is everything in modern IT — and UP Tombou now has it. Netwrix Auditor was implemented to:

  • Track all changes in Active Directory
  • Monitor file access and modifications on Windows file servers
  • Deliver real-time alerts on high-risk actions (e.g., mass file deletions)
  • Provide daily reports to ensure proactive oversight and accountability

With Netwrix, Tombou now has a transparent and audit-ready IT environment.

Office 365 Migration & Unified Communication

The internal mail server was successfully migrated to Microsoft 365, improving communication, reliability and integration. A modern virtual phone system was also deployed to replace outdated telephony infrastructure.

24/7 Monitoring and Centralized IT Task Management

To maximize uptime and response speed, Nebosystems deployed:

  • Around-the-clock infrastructure monitoring
  • Automated alerts for hardware and disk issues
  • A centralized ticketing system for efficient IT task management and issue resolution

This success story was featured live at InfoSec SEE 2025, Southeastern Europe’s leading cybersecurity conference. Representatives from Nebosystems and UP Tombou shared the transformation journey with IT leaders and compliance experts from across the region.

InfoSec SEE 2025 Recognition – Netwrix Partner of the Year

Thanks to successful digital transformation projects like this one, Nebosystems was named:

Netwrix Partner of the Year 2025
This recognition affirms Nebosystems’ commitment to high-impact solutions and long-term client success.

The Results

  • Secure, high-availability IT systems
  • Full ISO 27001 technical alignment
  • Increased productivity and zero unplanned downtime
  • Regular backup validation and disaster recovery testing
  • Streamlined IT operations through a professional ticketing system
  • Ongoing partnership built on trust and performance

Ready to Transform Your IT?

If your business is struggling with outdated infrastructure, security concerns or compliance pressure — Nebosystems can help.

Get in touch to learn how we can build a modern, secure, and audit-ready IT environment tailored to your needs.

AWS Weekly Roundup: AWS Builder Center, Amazon Q, Oracle Database@AWS, and more (July 14, 2025)

Post Syndicated from Matheus Guimaraes original https://aws.amazon.com/blogs/aws/aws-weekly-roundup-aws-builder-center-amazon-q-oracle-databaseaws-and-more-july-14-2025/

Summer is well and truly here in the UK! I’m a bit of a summer grinch though so, unlike most people, I’m not crazy about “the glorious sun” scorching me when I’m out and about. On the upside, this provides the perfect excuse to retreat to the comfort of a well-ventilated room where I can focus on coding and curating the latest AWS releases to bring you the highlights.

I also managed to escape the heat for most of yesterday while recording an episode for the AWS Developers Podcast where the wonderful Sebastien Stormaq and Tiffany Souterre interviewed me about games development. If you haven’t discovered it yet, I highly recommend you give it a go as the episodes are full of interesting lessons and insights from not just AWS, but customers and community members who share their stories and expertise in a relaxed conversation.

Alright, ready to discover some of the new things we released last week? Here are the highlights.

AWS Builder Center
There is a new home for AWS builders and community members! AWS Builder Center is a new place where cloud builders can connect, share knowledge, and access resources to enhance their AWS journey. The platform enables users to join community programs, discover trending topics, access AWS Skill Builder courses, participate in technical challenges, and more, using a single Builder ID sign-in.

One the features that I’m personally most excited about is the Wishlist. You can now create wishes and tell AWS directly about ways to improve our products and services or share original ideas that you think could help you and your teams. You can also browse and upvote existing wishes to support any suggestions that you think should be prioritized. The AWS teams will keep an eye on this and if a wish has enough traction it may just be considered!

Read the news blog post for a quick tour through some of the most exciting features or head over to AWS Builder Center and start exploring!

AI
The world of AI keeps moving fast and changing our world, by providing new and exciting ways to do things and become more productive. Here are two releases from last week that caught my attention.

  • Amazon Q chat in the AWS Management Console can now query AWS service data – Amazon Q Developer expands its capabilities by enabling natural language queries of data stored across AWS services like S3, DynamoDB, and CloudWatch, directly from the AWS Console, Slack, Microsoft Teams, and AWS Console Mobile Application. This enhancement streamlines cloud management and troubleshooting by allowing users to access and analyze service data through conversational interfaces, with access controls managed through IAM permissions.
  • Amazon CloudWatch and Application Signals MCP servers for AI-assisted troubleshooting – AWS has released two new Model Context Protocol (MCP) servers – CloudWatch MCP and Application Signals MCP – that enable AI agents to leverage observability data for automated troubleshooting through conversational interfaces. These open-source servers allow AI assistants to analyze metrics, alarms, logs, traces, and service health data across AWS environments, streamlining incident response and root cause analysis without requiring developers to manually navigate multiple AWS consoles.

Oracle Database@AWS
It seems like yesterday when Andy Jassy announced our partnership with Oracle to create Oracle Database@AWS, a jointly offered service that runs Oracle databases on Exadata infrastructure directly within AWS data centers, providing a unified AWS-Oracle experience. Fast forward to last week and Oracle Database@AWS has reached a significant milestone with its general availability release. It is now available in US East (N. Virginia) and US West (Oregon) regions, with plans to expand to 20 additional regions globally.

In addition, VPC Lattice has added support for Oracle Database@AWS enabling seamless connectivity between applications in VPCs and on-premises environments to Oracle database networks. The integration simplifies network management and provides secure access from Oracle Database@AWS to AWS services like Amazon S3 and Amazon Redshift, without requiring complex networking setup.

So if you’re looking to migrate your Oracle database workloads, now is a great time to explore Oracle Database@AWS as it offers a compelling path forward with minimal modifications required.

Additional highlights
Here are some other releases that I think many people will be happy about.

  • AWS Config now supports 12 new resource types – AWS Config has expanded its monitoring capabilities with support for 12 new resource types across services including BackupGateway, CloudFront, EntityResolution, Bedrock, and more. These additions are automatically tracked if you have enabled recording for all resource types, enhancing your ability to discover, assess, and audit AWS resources.
  • Amazon SageMaker Studio now supports remote connections from Visual Studio Code – Amazon SageMaker Studio now supports remote connections from Visual Studio Code, allowing developers to use their familiar VS Code setup while leveraging SageMaker’s scalable compute resources for AI development.
  • AWS Network Firewall: Native AWS Transit Gateway support in all regions – AWS Network Firewall now offers native integration with AWS Transit Gateway across all supported regions, enabling direct attachment and simplified traffic inspection between VPCs and on-premises networks. This integration eliminates the need for managing dedicated VPC subnets and route tables while providing multi-AZ redundancy for improved security and reliability.

Upcoming AWS Events
AWS Summit New York – this is definitely one to watch…literally! Registrations are closed due to capacity but you can tune in to watch live all the announcements and launches! No spoilers, but, trust me, there are a quite a few exciting things in store, so make sure to check it out.

AWS Gen AI Lofts – AWS Gen AI Lofts are multi-day events offering hands-on workshops, expert guidance, and networking opportunities for developers and business leaders looking to explore or advance their generative AI journey. These events are hosted across multiple global locations including San Francisco, Berlin, Dubai, Dublin, Bengaluru, Manchester, Paris, and Tel Aviv, providing accessible opportunities to accelerate your generative AI adoption.

And that’s it for this week! Come back next Monday for more highlights and keep your AWS knowledge up to date as we cover the latest releases.

Matheus Guimaraes | @codingmatheus

Managing Amazon Q Developer Profiles and Customizations in Large Organizations

Post Syndicated from Marco Frattallone original https://aws.amazon.com/blogs/devops/managing-amazon-q-developer-profiles-and-customizations-in-large-organizations/

As organizations scale their development efforts, AI coding assistants that understand organization-specific patterns and standards lead to more efficient development processes and higher quality software delivery. Amazon Q Developer Pro helps address this challenge by allowing organizations to customize the AI assistant with their proprietary code and development practices. Through Amazon Q Developer profiles, teams can efficiently manage access to Amazon Q customizations across different regions and AWS Identity Centers.

In this post, we will explore different approaches for implementing and managing Amazon Q Developer profiles and Amazon Q customizations across large organizations. Using an example with multiple business units, we will explore methods for managing access controls and customization governance while addressing security and compliance requirements.

Amazon Q customization is now available in both the US East (N. Virginia) and EU Central (Frankfurt) regions, giving teams more flexibility to create and deploy customizations closer to their operational hubs while meeting regional data residency requirements.

This blog is not intended to provide recommendations on how to structure your AWS accounts or divide Q Developer subscriptions. Rather, our aim is to explore the full capabilities of Q Developer Customizations in a comprehensive scenario that shows the current art of the possible.

A distributed Amazon Q Developer Pro subscriptions scenario

The following diagram illustrates a sample AWS Organizations structure with a Management Account and four Organizational Units (OUs). This is a common enterprise scenario with three business units, each business unit requiring their own Amazon Q Developer Pro subscription and customizations.

Diagram showing AWS Organizations structure with a Management Account at the top, containing AWS Organizations, IAM Identity Center, Amazon Q, Management Customizations, and AWS Cost & Usage Report. Below are four Organizational Units (OUs): Infrastructure, Alpha, Bravo, and Charlie. The structure illustrates the hierarchical relationship and resource allocation across different OUs and regions within an AWS organization.

Figure 1: AWS Organizations Structure and Resource Hierarchy

The Infrastructure OU has a Delegated Admin Account with delegated access to the AWS IAM Identity Center. There are three additional OUs: Alpha, Bravo, and Charlie, each with at least one Amazon Q Developer Pro subscription. Alpha account has Amazon Q Developer subscriptions both in US East (N. Virginia) and EU Central (Frankfurt) region.

Think of each business unit as its own ecosystem within your organization. When you provide dedicated Q Developer Pro subscriptions to different OUs, you’re essentially giving each unit its own personalized AI assistant. This separation is valuable because it allows each team to work independently while maintaining their specific requirements and workflows.

The Charlie OU maintains its own account instance of IAM Identity Center for Amazon Q Developer Pro. In most cases, we recommend using an organization instance of IAM Identity Center with Amazon Q Developer Pro, there are a few situations where member account instances might make sense, for example: when you do not have a single identity provider, or when you haven’t yet decided to deploy it to the whole organization and want to use Amazon Q just for the AWS account you control.

Note: When a developer has a user within an Amazon Q profile tied to two different IAM Identity Center instances (Bravo and Charlie), they will have two user subscriptions and be billed twice. However, if they belong to two different Amazon Q profiles in two different accounts (Alpha and Bravo) but under the same IAM Identity Center, they will only be billed once.

In our example, the Charlie OU requires additional operational overhead in managing separate credentials and authentication flows. Additionally, the dashboard and administrative settings will only be associated with users and groups within this account.
From an administrative perspective, instead of trying to manage one centralized configuration that attempts to serve everyone’s needs, you can distribute administration to each business unit and delegate responsibility to individual teams.

It’s like having different specialized departments in a hospital – while they’re all part of the same organization and can work together when needed, each department has its own specialized tools and protocols that help them perform their specific functions more effectively.

A strategic approach to Customizations through Q Developer profiles

A diagram illustrating the structure of an AWS IAM Identity Center organization with multiple Amazon Q Developer Pro subscriptions and customizations. Each Q Developer Pro Subscription has its own set of users representing developers. Team orange developers have access to Alpha Q Subscription and customizations, Team blue developers have access to Alpha, Bravo and Charlie Q Subscription and customizations, Team Grey developers have only access to Bravo Subscription and customizations. The organization has also an AWS IAM Identity Center instance, with separate Amazon Q Developer Pro subscription and customizations. Team bravo developers are duplicated between the two IAM Identity Centers.

Figure 2 Developers association to Amazon Q Developer Pro Subscriptions, Customizations and IAM Identity Centers

Amazon Q Developer profiles are the way developers connect to different Amazon Q Developer subscriptions through their IDE. Each profile represents a unique combination of an Amazon Q Developer subscription and its associated customizations. After authentication, developers can simply select or switch between profiles in their IDE to access different customizations.

Let’s walk through some scenarios in this architecture.

Scenario 1 – Users accessing two different customizations tied to a single IAM Identity Instance in the management account

Developers from the Orange team with access to Alpha account customizations can configure two different Amazon Q Developer profiles in their IDE:

  • A “US Profile” connected to the US East subscription in the Alpha account
  • An “EU Profile” connected to the EU Central subscription in the Alpha account

Switching between different sets of customizations involves selecting the relevant profile within their IDE.

Screenshot of IDE interface showing the Amazon Q Developer customizations panel. Developer switch between US and EU Profiles and their customizations

Figure 3 IDE showing customizations available for Team Orange developers switching between US and EU Profile and their customizations

Note: While developers can access multiple customizations through different Amazon Q Developer profiles, they only incur a single user subscription cost since they are using the organization instance of IAM Identity Center. This is because the subscription is tied to their user identity in the IAM Identity Center organization instance, not to the number of profiles or customizations they access.

Scenario 2 – Users accessing two different customizations tied to a single IAM Identity Instance in the management account
Similarly, developers from the Blue team can also configure multiple profiles:

  • One profile for accessing Alpha and Bravo customizations through the management account AWS IAM Identity Center instance
  • A separate profile for accessing Charlie customizations through the AWS IAM Identity Center member account Instance

When developers have access to multiple customizations within the same IAM Identity Center configuration and region, they can switch between profiles in their IDE without requiring reauthentication.

Screenshot of IDE interface showing the Amazon Q Developer customizations panel. When authenticated through the AWS IAM Identity Center Organization, Blue developers can see both Alpha and Bravo customizations.

Figure 4 IDE showing customizations available for Team Blue developers when authenticated to AWS IAM Identity center Organization

However, as demonstrated in the blue developers’ case, switching between profiles that use different IAM Identity Center configurations (Organization vs Account Instance) still requires reauthentication.

Note: In this scenario, developers will incur two separate user subscription charges since they are accessing customizations through two different IAM Identity Center configurations (organization and account instance). As mentioned above, this scenario is not recommended except for situations it might make sense and is shown here purely to illustrate how the authentication and profile switching mechanisms work across different IAM Identity Center configurations.

Screenshot of IDE interface showing the Amazon Q Developer customizations panel. When authenticated through the AWS IAM Identity Center Instance, Blue developers can see only Charlie customizations.

Figure 5 IDE showing customizations available for Team Blue developers when authenticated to AWS IAM Identity center Account Instance

One scenario for creating code customizations specific to each profile is that the developers on the Alpha team might need Q to understand specific libraries and internal coding conventions for Java, while Bravo team developers might need Q to be well-versed in your proprietary technologies and development standards with Python. With separate profiles and customizations, each team gets their own “flavored” version of Q that understands their context.

For Blue developers who have access to Alpha, Bravo and Charlie customizations, they need to set up separate profiles since these customizations belong to different IAM Identity Center configurations and AWS Regions. Switching between these profiles requires reauthentication due to the different IAM Identity Center configurations involved.

Developer Team AWS IAM Identity Center Customizations
Orange Organization instance Alpha customizations in US East (N. Virginia)
Alpha customizations in EU Central (Frankfurt)
Blue Organization instance Alpha customizations in US East (N. Virginia)
Bravo customizations
Account instance Charlie customizations
Grey Organization instance Bravo customizations

You can manage access to specific Amazon Q Developer Pro customizations by adding selected users and groups who already have access to Amazon Q Developer Pro subscriptions within the same Identity Center. This granular access control allows you to create targeted customizations that are only accessible to specific team members or groups within your organization.

Conclusion

In this post, we explored comprehensive strategies for implementing Amazon Q Developer customizations across large organizations. We demonstrated how Amazon Q Developer profiles provide a flexible way to manage access to different customizations across AWS regions and IAM Identity Center configurations. By integrating proprietary code repositories, establishing customization governance, and implementing continuous feedback loops, enterprises can maximize the value of their AI-powered development assistant while maintaining code quality and development standards.

The path forward depends on where you are in your Amazon Q Developer customization journey. If you’re just starting, begin with a clear assessment of your codebase and map out your customization approach before implementation. For existing users, review your current customizations and profile configurations to identify optimization opportunities.

In both cases, implement the customization governance we discussed, tailoring them to your specific development patterns and team structures. Remember that customization evolves with your codebase – regular refinements help ensure your AI assistant remains effective as your applications grow and development practices mature. Whether you’re new to Amazon Q Developer customizations or optimizing existing implementations, these practices can help develop an AI assistant that truly understands and aligns with your organization’s unique development environment.

Ready to get started? Visit the Amazon Q Developer guide to learn more about setting up profiles and customizations for your organization. If you need help planning your customization strategy, contact your AWS account team or find an AWS Partner in the AWS Partner Network.

About the authors:

Marco Frattallone

Marco Frattallone is a Senior Technical Account Manager at AWS focused on supporting Partners. He works closely with Partners to help them build, deploy, and optimize their solutions on AWS, providing guidance and leveraging best practices. Marco is passionate about technology and enables Partners stay at the forefront of innovation. Outside work, he enjoys outdoor cycling, sailing, and exploring new cultures.

Francesco Martini

Francesco Martini is a Senior Technical Account Manager at AWS. He helps AWS customers build reliable and cost-effective systems and achieve operational excellence while running workloads on AWS. He is a builder and a technology enthusiast with a background as a full-stack developer. He is passionate about sports in general, especially soccer and tennis.

Ако не можеш да нахраниш детето си

Post Syndicated from Надежда Цекулова original https://www.toest.bg/ako-ne-mozhesh-da-nahranish-deteto-si/

Ако не можеш да нахраниш детето си

В институциите за деца има непропорционално много деца от ромски произход. Понякога те попадат там с неубедителни аргументи. Държавата не събира данни за нито един етап от процеса, но изследване на Сдружение с нестопанска цел „Инициатива за равни възможности“ сочи, че от една страна, институциите са по-склонни да извеждат от семействата им именно ромските деца, а от друга, сред ромите най-често възниква един от основните рискове, водещи до раздяла между деца и родители – бедността. Изследователите събраха представители на общността и организации, работещи със семейства в риск, в търсене на решения.

Изводът беше, че фокусираната подкрепа там, където е най-нужна, би могла да предотврати много раздели и да гарантира по-добър живот на децата. Когато я има не само на хартия, но и на практика. 

„Непосредствена опасност“

Наскоро се запознах с едно семейство. Бедни хора от малък град, мъжът години наред е работил, но неотдавна глаукома го оставя напълно сляп. 

Родителите живеели с малката си дъщеря в общинско жилище. Един ден обаче дошли социалните. Някой им се обадил, че детето се разхожда само̀ из града. Видели, че в апартамента няма ток. Че домът не е подреден, а детето не е изкъпано. Направили предписание. След два дни дошли отново и си тръгнали с детето. 

Според близките и семейството повечето от аргументите, с които момиченцето е взето от родителите му и пратено в център за настаняване от семеен тип в друг град, или са силно преувеличени, или са напълно неверни. „Не е оставяна сама, не е ходила гладна, не сме я били. Грижихме се за нея колкото можем“, споделя бащата и допълва сякаш на себе си: „Човек ако не може детето си да нахрани, защо да живее на тоя свят.“ Семейството било настанено в общинското жилище едва десетина дни преди социалните да ги посетят. „Бяхме подали вече документи, но още не беше пуснат токът, не бяхме оправили всичко, знаете как е“, разказва още бащата. 

Никой обаче не вярва на двама бедни и нискообразовани родители, нито на свидетелите, които ги подкрепят. Социалните служби издават заповед за извеждане на детето с мотива, че жилището, в което живее семейството, е неподходящо – без ток, с лоша хигиена, неподредено и без възможност за приготвяне на топла храна. Като допълнителен аргумент се посочва, че майката няма образование и има затруднения в общуването, което според социалните поставя под съмнение способността ѝ да полага адекватни грижи. В подкрепа на мярката е цитиран и сигнал, че детето е било забелязвано само̀ навън, както и фактът, че даденото предписание за подобряване на условията не е било изпълнено в кратък срок. На тази основа местната дирекция „Социално подпомагане“ разпорежда извеждане на детето поради предполагаема „непосредствена опасност“.

Така детето остава на грижите на държавата, а на родителите е определен график на свиждане по веднъж месечно, като им е намекнато, че е по-добре да не идват дори и в този един-единствен ден в месеца, защото после детето им… плаче.

От частното към общото

През последната година адв. Даниела Михайлова и колегите ѝ от „Инициатива за равни възможности“ изследват как децата попадат в институции и се натъкват и на други случаи като този. Почти винаги става дума за ромски семейства. 

Наистина значително по-често се предприема извеждане на дете от семейството, когато става въпрос за ромско семейство. Свръхпредставеността на ромски деца в институционалната грижа е ясно видима – дори когато няма официални данни, тя се доказва чрез теренни наблюдения и интервюта,

обяснява адв. Михайлова. 

Според доклада „Забравените надежди: ромските деца в институционалната грижа“ ромските семейства са по-често подложени на наблюдение, получават по-рядко подкрепа и значително по-често спрямо тях се прилага крайна мярка – извеждане на дете. Същевременно намирането на приемно семейство за ромско дете, особено ако е на по-голяма възраст, е значително по-трудно, а пътят към институцията се оказва най-достъпен. 

Проблемът в тези случаи е, че няма достатъчно ефективна социална работа за подкрепа на родителите между установяването на някакви проблеми и извеждането на детето,

коментира адв. Диян Данков от програма „Правен инкубатор“. 

Адв. Данков представлява няколко семейства в сходно положение и смята, че има повтарящи се проблеми: 

Често се оказва, че социалният доклад стои на пиедестал, съдът приоритетно взема под внимание този доклад и нищо не е в състояние да го обори. 

В цитирания по-горе случай например, макар срещу твърденията в доклада на социалните да са приведени не само свидетелски показания, но и становища от личния лекар и здравния медиатор, работещи със семейството, съдът все пак приема, че най-добрият интерес на детето е да бъде изведено от дома му. 

В редица случаи бедността се възприема като „пренебрегване“, а лошите жилищни условия – като „непосредствена опасност“, макар в практиката на социалната работа това да не би трябвало да е достатъчно основание за отнемане на дете.

Адв. Даниела Михайлова си спомня случай от друг град, където представлява семейство с две деца. Там децата са описани „в риск“ заради счупена брава на врата, мръсни чинии в мивката и неизпрано пране, оставено на дивана. 

Дори описанието на фактическите обстоятелство в този случай не подкрепяше направения извод, че за децата има някакъв реален риск. Въпреки това съдът потвърди извеждането им за срок от пет години,

разказва тя.

Социологическото проучване, ръководено от доц. Алексей Пампоров, потвърждава косвено това наблюдение.

По приблизителни оценки между 60 и 70% от децата в резидентна грижа в България са от ромски произход, въпреки че ромите съставляват малко над 10% от населението.

В около 40% от изследваните случаи причините за извеждане са свързани с бедност в семейството, а повече от половината изведени от семействата си деца прекарват години в институции без реална работа за връщането им у дома, сочат наблюденията на изследователите.

Сред основните бариери пред т.нар. реинтеграция е отново бедността, прозираща зад административната формулировка за неподходящите битови условия. Предразсъдъците и възприятията за ромите, включително съмненията в родителския им капацитет и желанието им да се грижат за децата си в семейна среда, остават широко разпространени пречки пред системата и засягат близо 50% от работещите в нея, се отбелязва в доклада: 

По време на дискусиите във фокус групите за целите на това изследване повечето участници използваха дискриминационен език и дискурс, когато описваха опита си в работата по случаи, включващи родители и деца от ромски произход.

Подозренията обаче са взаимни – ромските респонденти споделят дълбоки притеснения, страх и намалено доверие в служителите на социалните служби, като делът на респондентите, споделящи опасение, че родителите в техния квартал често се страхуват децата им да не бъдат отнети, варира от 30 до 70%.

Какво значи „най-добрият интерес“?

Българското законодателство и международните стандарти поставят „най-добрия интерес на детето“ в основата на всяко решение, засягащо децата – включително и при настаняване извън семейството.

Законът за закрила на детето допуска извеждане на детето само когато всички други възможности са изчерпани.

За да се пристъпи в кратък срок към извеждане пък, трябва да съществува реална, непосредствена опасност за здравето или живота на детето. Експерти коментират, че тази мярка се прилага непоследователно от различните отдели за закрила на детето и така в едни общини има множество случаи със съмнително обосновано извеждане на деца, докато в други мярката не се прилага дори при доказан риск за живота и здравето на детето.

Докладът „Забравените надежди“ се фокусира върху казуси, в които крайната мярка – извеждане, се предприема, без да е предложена подкрепа и без да се търсят решения, които биха запазили връзката между дете и родители. Адв. Даниела Михайлова е категорична, че това противоречи на философията на Закона за закрила на детето: 

В някои случаи малка помощ за семейството навреме – с плащане на сметка, с временна социална услуга или чрез включване на близки или роднини – може да се постигнат добри резултати и детето да е у дома си.

Имаме случаи, в които индивидуалният план на родителите включва среща със социален работник, на която им се казва да си намерят работа или че трябва да поддържат емоционална връзка с децата си. Това практически не им помага,

дава пример адв. Данков. 

В същото време се определя режим за свиждане по веднъж в месеца, което допълнително засилва психическия натиск върху детето и затруднява запазването на тези емоционални връзки, подчертава юристът. 

Деинституционализиране на деинституционализацията

Описаните случаи далеч не изчерпват причините за свръхпредставянето на ромските деца в институционалната грижа, обаче поставят ясен акцент върху острия недостиг на превантивна работа и комплексна грижа за семействата. Зад сложните думи стоят действия, които на практика, а не на хартия да помогнат семейството да стане по-добър дом за децата си, а не на децата да се търси дом извън семейството. 

Докладът „Забравените надежди“ обръща внимание на проблем, посочван неведнъж и от не един експерт и институция: недостатъчно ефективната „деинституционализация“ на децата у нас. Авторите я определят като „провал“ поради активната роля на съвременните „домове“ в системата за закрила на детето. 

За да бъде преодоляна системната грешка бедността да се наказва с отнемане на деца, експертите предлагат пет конкретни препоръки за промяна в публичните политики в сферата на закрилата. На първо място, те настояват за забрана на извеждането на дете само въз основа на аргументи, свързани с бедност. Вместо това социалните служби трябва да бъдат задължени първо да търсят решения в общността – чрез роднинска подкрепа, мобилни социални услуги и достъп до елементарни битови условия. 

Втората препоръка залага на засилване на превенцията, особено чрез ранна интервенция, достъп до детски градини, жилищна помощ и присъствие на социални работници в кварталите. Специално внимание е отделено на най-малките – според експертите е нужна забрана за настаняване на деца под 10 години в институции, освен в изключителни случаи. 

Отбелязана е и спешна нужда от повишаване на капацитета на социалните служби. Въвеждането на етнически чувствителен мониторинг е четвъртата ключова стъпка – за да се проследят и ограничат дискриминационни практики в системата. 

Накрая, експертите настояват за изграждане на реални механизми за реинтеграция на децата, излезли от институции – включително достъп до образование, психологическа подкрепа, посредничество със семейството и сигурно жилище. 

Ако трябва да изберем само една-две от най-основните мерки, които обаче да дадат осезаем резултат, това е да се въведе поне една, само една мярка за подкрепа на семейства в икономически уязвимо положение. И на следващо място – да се преструктурират социалните служби, защото в момента има отдели с еднакъв брой служители, но с десетки пъти разлика в броя случаи,

смята Даниела Михайлова.

Всички тези предложения имат една основна цел: децата да растат в сигурна семейна среда, а държавата да оказва ефективна подкрепа там, където е нужно. 

[$] Following up on the Python JIT

Post Syndicated from jake original https://lwn.net/Articles/1029307/

Performance of Python
programs
has been a major focus of development for the language over the last
five years or so; the Faster
CPython project
has been a big part of that effort.
One of its subprojects is to add an experimental just-in-time (JIT) compiler to
the language; at last year’s PyCon US, project member Brandt Bucher gave an introduction to the copy-and-patch JIT
compiler. At
PyCon US
2025
, he followed that up with a talk on “What they don’t tell you
about building a JIT compiler for CPython” to describe some of the things
he wishes he had known when he set out to work on that project. There
was something of an elephant in the room, however, in that
Microsoft
dropped support for the project
and laid off most of its
Faster CPython
team a few days before the talk.

Security updates for Monday

Post Syndicated from jake original https://lwn.net/Articles/1029764/

Security updates have been issued by Debian (redis and thunderbird), Fedora (cef, git, gnutls, httpd, linux-firmware, luajit, mingw-djvulibre, mingw-python-requests, perl, php, python-requests, python3.6, salt, and selenium-manager), Mageia (dpkg, firefox, gnupg2, and golang), Slackware (httpd and kernel), SUSE (afterburn, cmctl, git, go1.23, go1.24, k9s, liboqs-devel, libxml2, php8, python36, trivy, and xen), and Ubuntu (linux-xilinx-zynqmp and nix).

Kernel prepatch 6.16-rc6

Post Syndicated from corbet original https://lwn.net/Articles/1029716/

Linus has released 6.16-rc6 for testing;
it includes a fix for a somewhat scary regression that came up over the
week.

So I was flailing around blaming everybody and their pet hamster,
because for a while it looked like a drm issue and then a netlink
problem (it superficially coincided with separate issues with both
of those subsystems).

But I did eventually figure out how to trigger it reliably and then
it bisected nicely, and a couple of days have passed, and I’m
feeling much better about the release again. We’re back on track,
and despite that little scare, I think we’re in good shape.

The collective thoughts of the interwebz