To protect consumers against security and privacy (S&P) cyberthreats (attacks, abusive practices and inappropriate behaviours of digital services).
For Computer Emergency Response Teams (CERTs) and Authorities to ensure that digital products are transparent, secure and in compliance with regulation.
To foster S&P-by-design in software engineering by supporting developers and digital service operators with standards and certification methods.
TRUST aWARE mission is to provide a holistic and effective digital Security & Privacy (S&P) framework comprising a set of novel and integrated tools and services co-created by citizens and stakeholders (CERTs, DPAs, organisations, developers and policy-makers) to identify, audit, analyse, prevent, and mitigate the impact of the various S&P threats associated with citizen’s digital activities in a timely manner, while enhancing software trust and regulatory compliance.
The project addresses a complex socio-technical challenge that requires an interdisciplinary and transdisciplinary approach to be successfully addressed. The expertise brought by the partners forming this consortium reflects this multidisciplinary approach that will enrich the projects efforts, and the quality of outcomes.
For fostering the transfer of knowledge and exploitation of TRUST aWARE, a strong public-private partnership has been established among 12 partners from 7 European countries: 4 user associations, 3 industrial companies, 3 research organisations, 1 CERT body and 1 international platform.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
This cookie is set by Statcounter. It is used to determine whether a user is a first-time or a returning visitor and to estimate the accumulated unique visits per site.
This cookie is set by StatCounter Analytics. It is used to determine whether a user is a first-time or a returning visitor.
This cookie is set by the website that you visit. When it is first set, a random id is generated and stored in the cookie in order to avoid counting you as a visitor more than once. Similarly to the is_unique cookie, this cookie also stores a count of your returning visits.