The latest (and last) TRUST aWARE newsletter is out!

We are excited to bring you the final edition of the TRUST aWARE newsletter. While our project may be coming to a close, its impact on digital security will continue to be felt.

TRUST aWARE overview

Now that the TRUST aWARE project has come to an end, it is time to take a look back at the three years our consortium has been working hand in hand towards the achievement of common and exciting goals. These goals, altogether, were aimed to support and help our key stakeholders to effectively manage security & privacy (S&P) issues, with a special focus on citizens. Have we succeeded? Let’s see…

Valuable Achievements of the TRUST aWARE Project

The TRUST aWARE project has made significant strides in enhancing the security and privacy (S&P) ecosystem through active engagement with key stakeholders.

New infographics!

We are happy to share a couple of infographics that should support policy makers and stakeholders in the context of user-centric Security & Privacy (S&P) tools.

Valuing the benefits to society of improving online security and privacy

Beyond financial savings, security and privacy tools, such as those developed in TRUST aWARE, help foster social connections, enhance essential service access, and combat harmful content leading to substantial benefits to society.

The complexities of FOTA Apps in the Android ecosystem

Android firmware updates are typically managed by the so-called FOTA (Firmware Over-the-Air) apps. Such apps are highly privileged and play a critical role in maintaining devices secured and updated. The Android operating system offers standard mechanisms to vendors to implement their own FOTA apps, but such vendor-specific implementations could be a source of security and privacy issues due to poor software engineering practices. In a recent large-scale study, TRUST AWARE members performed a systematic analysis of the FOTA ecosystem through a dataset of 2013 FOTA apps detected with a tool designed for this purpose over 422,121 pre-installed apps. The findings include that 43% of FOTA apps are developed by third parties, that some devices can have as many as 5 apps implementing FOTA capabilities, and that some apps present behaviours that can be considered privacy intrusive, such as the collection of sensitive user data (e.g., geolocation linked to unique hardware identifiers), and a significant presence of third-party trackers.

TRUST aWARE Partners with RomeCup2024 to Advance Robotics and AI for Sustainable Solutions

We are pleased to announce that TRUST aWARE, a pioneering project under Horizon 2020, is joining forces with the #RomeCup2024 event. Scheduled to take place from March 20th to 22nd, the RomeCup will be held at the University of Tor Vergata and Campidoglio.

Banking Security Risks and Solutions: The TRUST aWARE Technical Meeting at the ABI Lab Forum

On March 27th, ABI Lab will host the second TRUST aWARE technical meeting, titled “Privacy and Security Threats: Analysis and Tools”.

Acceptance cybersecurity: A comprehensive look at attitudes towards data protection and security tool adoption

Research on citizens’ attitudes towards digital tools for data protection and privacy highlights the need for big data literacy and understanding of data protection, especially in e-government initiatives. This suggests a growing awareness of the need for digital tools to protect personal data. Understanding attitudes towards digital tools is crucial.

Understanding LOLBins, file-less attacks, and the power of Activity Monitor

The continuous evolution and appearance of new threats demand innovative approaches to protect against them. Two such sophisticated techniques that have gained prominence in recent years are LOLBins and file-less attacks. Individually potent, their combination poses a formidable challenge to traditional security measures. In this blog, we will delve into the intricacies of LOLBins and file-less attacks, explore their synergy, and introduce an advanced solution, Activity Monitor, designed to counteract these threats effectively.

error: Content is protected !!