{"id":1350,"date":"2022-02-14T10:06:21","date_gmt":"2022-02-14T10:06:21","guid":{"rendered":"https:\/\/community.5gasp.eu\/?p=1350"},"modified":"2023-03-29T20:49:13","modified_gmt":"2023-03-29T20:49:13","slug":"privacyanalyzers-transformation-to-a-netapp-supporting-5gasps-vertical-use-cases","status":"publish","type":"post","link":"https:\/\/community.5gasp.eu\/index.php\/2022\/02\/14\/privacyanalyzers-transformation-to-a-netapp-supporting-5gasps-vertical-use-cases\/","title":{"rendered":"PrivacyAnalyzer\u2019s transformation to a Network Application supporting 5GASP\u2019s vertical use cases"},"content":{"rendered":"

PrivacyAnalyzer by SME Lamda Networks www.lamdanetworks.com<\/a> offers the functionality for aiding the 5G\/IoT integrators to assess the privacy strength of their applications or services against confidential information disclosure before they can release their solutions to their clients.<\/p>\n

To achieve the above goal, PrivacyAnalyzer receives testing sessions\u2019 traffic stemming from the devices (UEs, IoT devices, etc.) participating in the integrator\u2019s test sessions. Then, PrivacyAnalyzer scans the sessions\u2019 message contents for privacy-sensitive content and reports the outcomes of the analysis to the end-user (integrator) with the goal to enable the end-user to resolve the privacy issues detected in the test sessions before releasing her application or service to her client, typically a network\/service operator or an IoT service provider. The software was initially developed as an extend open call project with the F-INTEROP project https:\/\/www.f-interop.eu\/<\/a> via a collaboration between Lamda Networks and Kings College London\u2019s Computer Science group specializing in anonymisation techniques<\/a>.<\/p>\n

Afterwards, the proof of concept of the software has been highly refactored by investing its own resources so that PrivacyAnalyzer operates as a Software as a Service (SaaS) handling large volumes of incoming messages for different devices. To that end, the Kubernetes framework has been used, together with a cluster running Kafka and a second cluster running mongoDB. The high-level architecture of the cloud version of PrivacyAnalyzer is depicted below. Note that the SaaS can run in the client\u2019s own cloud as well as we support running the SaaS in Google\u2019s and Amazon\u2019s cloud platforms and last, we allow the use of PrivacyAnalyzer to subscribed tenants to our private cloud, the latter being charged via a volume-based subscription fee.<\/p>\n

\"\"<\/p>\n

PrivacyAnalyzer has the potential to become an important service in both 5GASP\u2019s use cases as well as a service that could serve other verticals apart from Automotive and PPDR. For the latter verticals, the PrivacyAnalyzer Network Application shall cater for detecting the privacy vulnerability of relevant network devices, which are involved in automotive and\/or PPDR communications. As an example, our service might enhance the physical protection of the personnel of the involved authorities (e.g. First Responders) in PPDR operations and overall help the success of ongoing disaster recovery operations.<\/p>\n

The current status of the \u2018Network Application-ization\u2019 of PrivacyAnalyzer is that we have created the NS and VNF descriptor for OSM 10. Furthermore, we have defined the Helm chart so that our Network Application is able to be onboarded to a 5GASP testbed. We have successfully onboarded to the Patras testbed, using the Patras Harbor repo for uploading our Helm chart whilst the project-wide Helm repo is being established in the consortium with the purpose that each Network Application developer is a tenant, isolated from others, and is able to upload her Docker images and Helm charts in a private space within Harbor.<\/p>\n

As the next steps, we are continuing to work within the scope of WP4 and WP5. Our mode term goal is that until summer 2022, PrivacyAnalyzer is deployed (onboarded and instantiated) in three target testbeds (Patras, ININ, Bristol) in order to cater for used for the different usage scenarios of the Network Application as we have defined them within the scope of WP4. Below follows a summary of the roadmap for deployment on the three target testbeds.<\/p>\n

In Q1 2022, PrivacyAnalyzer shall be onboarded and instantiated on the Patras, ININ and Bristol testbeds using OSM 10 and their associated K8S VIMs.<\/p>\n

In Q2 2022, PrivacyAnalyzer -which we become by then a fully-fledged 5GASP Network Application – shall be deployed on Patras\u2019s, ININ\u2019s and Bristol\u2019s testbeds; the first two addressing the cross-vertical and PPDR use cases respectively and the latter employed for co-working with Bristol\u2019s MEC offloading Network Application.<\/p>\n

For any question regarding PrivacyAnalyzer and its transformation to Network Application, please email privacyanalyzer@lamdanetworks.io<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

PrivacyAnalyzer by SME Lamda Networks www.lamdanetworks.com offers the functionality for aiding the 5G\/IoT integrators to assess the privacy strength of their applications or services against confidential information disclosure before they can release their solutions to their clients. To achieve the above goal, PrivacyAnalyzer receives testing sessions\u2019 traffic stemming from the [\u2026]<\/p>\n","protected":false},"author":1,"featured_media":1351,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"pg_page_styles":[],"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"ngg_post_thumbnail":0,"footnotes":""},"categories":[12],"tags":[],"class_list":["post-1350","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog"],"_links":{"self":[{"href":"https:\/\/community.5gasp.eu\/index.php\/wp-json\/wp\/v2\/posts\/1350","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/community.5gasp.eu\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/community.5gasp.eu\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/community.5gasp.eu\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/community.5gasp.eu\/index.php\/wp-json\/wp\/v2\/comments?post=1350"}],"version-history":[{"count":2,"href":"https:\/\/community.5gasp.eu\/index.php\/wp-json\/wp\/v2\/posts\/1350\/revisions"}],"predecessor-version":[{"id":1693,"href":"https:\/\/community.5gasp.eu\/index.php\/wp-json\/wp\/v2\/posts\/1350\/revisions\/1693"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/community.5gasp.eu\/index.php\/wp-json\/wp\/v2\/media\/1351"}],"wp:attachment":[{"href":"https:\/\/community.5gasp.eu\/index.php\/wp-json\/wp\/v2\/media?parent=1350"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/community.5gasp.eu\/index.php\/wp-json\/wp\/v2\/categories?post=1350"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/community.5gasp.eu\/index.php\/wp-json\/wp\/v2\/tags?post=1350"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}