![[lucas-gallone-uPk5aOtimUE-unsplash.jpg]] Photo by [Lucas Gallone](https://unsplash.com/@lucasgallone?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText) on [Unsplash](https://unsplash.com/s/photos/security?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText) Cloud Security is considered one of the biggest concerns related to Cloud Computing and has been identified by numerous Security groups such as Cloud Security Alliance (CSA) and Jericho Forum (Open Group). In line with continuing strategy for enabling secure business collaboration, the Jericho Forum defined The Cloud Cube Model consisted from 4 dimensions differentiated from each other and the manner of their provision. We connected these dimensions with Cloud Actors and adopt them as a 1st line of defense for our Cloud Business Privacy Layer Model. ![[Pasted image 20230709110053.png|Figure 1: Cloud security cube dimensions specified by Jericho Forum]] Dimensions are specified as: 1. Internal / External : Physical Location 2. Proprietary / Open : State of ownership and degree of interoperability and transportability 3. Parameterized / De-parameterized : Executing operations within or without IT Perimeter 4. Insourced / Outsourced : Service is provided by own staff or by 3rd party All Cloud Security Frameworks addressed security issues towards the Cloud Networks and Environments, which is correct approach considering the fact that we speak about massive scalability, virtual environments, complex orchestrations and advanced business collaborations. With increasing amount of business services, devices, sensors and various channels we identified new security layer concentrated around Service Consumer, indicating opposite service layer order (from Cloud towards Consumer). In the other words; from business perspective we care about Consumer Privacy affected by Security Dimensions, Information Channels, Business Services, Information Streams and Disposable Technologies (new Emerging Trends). The Spheres recognize two Business Security Layers depicted below, concentrated around Service Consumer showing “Privacy Level Meter” capability as a primary method for Privacy Measurement and also as a Capability Enabler for Privacy Configuration of Channels, Services, Devices and Categories. ![[Pasted image 20230709110116.png|Figure 2: Cloud business security layers view]] > Note: The “Demand your Dot Rights” Organization (ACLU) states: The Consumers of Cloud computing services have a simple message for their service providers: “Let's keep the data between us”. The outdated privacy laws, inadequate privacy policies, and lack of technological tools allowing for consumers to control their own information signal stormy skies for privacy. The **Privacy Level Meter** (PLM) measures calculated Privacy Score and provides Consumer Privacy Level as privacy intrusion indication for selected entity (particular person , person type or person role). ![[Pasted image 20230709110135.png|Figure 3: PLM - Consumer privacy intrusion level identified by Privacy Score]] Privacy Score can be calculated by device or as an overall Privacy Number and is specified as a calculation of: ![[Pasted image 20230709110155.png|Figure 4: Privacy score calculation]] **Here is the example for Privacy Score Calculation:**(510*16*80*2500*1010) = 1648320000000 / (100000 * 1000000) = 164.832 **Description:**(SMS+WAP)*(Push Information + Pull Information + Synchronize On Demand) * (Android Mobile) * (Facebook + Twitter) * (Farmville + Twitter Followers) / (Living on the Net * Pro Active) For Privacy Score 164.832, Consumer Privacy Level equals 1 = High PLM Intrusion Following tables are representing possible examples of Privacy Points (Constants used for Privacy Score Calculation): ![[Pasted image 20230709110221.png]] ![[Pasted image 20230709110246.png|Figure 5: Privacy Points]] In summary, consumer privacy model (you can use different interpretations or weights scenarios) is important part of **sustainable ecosystem**, serving as a configuration and monitoring indicator of **sharing / isolation levels** at specific entities or entity boundaries. Privacy indicator should be (in any form) essential part of any architecture, incorporated to personal and business ecosystems; as well as become an **omnipresent reality** across all environments leadings to consistent privacy experience for mission critical components and associated consumers. ## Related to [[The Cloud Social Influence Model]] [[SPHERES and Social Management - Motivation]] [[SPHERES and Social Management - Composition]] [[SPHERES and Social Management - Introduction]]