Multi-tenancy

1. Multi-tenancy Presented by Pengfei Sun

2. Multi-tenancy • Multi-tenancy in cloud service models implies a need for policy-driven enforcement, segmentation, isolation, governance, service levels, and chargeback/billing models for different consumer constituencies. • Consumers utilize a public cloud provider’s service offerings and share infrastructure.

3. Multi-tenancy Threat • Isolation failure - includes the failure of mechanisms separating storage, memory, routing, and even reputation between different tenants of the shared infrastructure (e.g., so-called guest-hopping attacks and side channel attacks). • Resource sharing - means that malicious activities carried out by one tenant may affect the reputation of another tenant. For example, spamming, port scanning or the serving of malicious content from cloud infrastructure can lead to: a range of IP addresses being blocked, including the attacker and other innocent tenants of an infrastructure; confiscation of resources due to neighbour activities (neighbour subpoenaed).

4. In addition, take the case of two customers on a shared traditional network infrastructure. If one customer wishes the network firewall to block all traffic except for SSH, but another customer is running a web server farm and requires passage of HTTP and HTTPS, who wins? This same type of issue is raised by customers who have competing and conflicting compliance requirements.

5. Process as a Service - Distributed Multi-tenant Policy-based Process Runtime Governance • The business process execution needs to be governed as policy enforcement might differ between different clients. Since a process is deployed outside of the organizations and serves multiple process clients, distribution and multi-tenancy have become two requirements for runtime governance of service processes • a policy-oriented aspectual business process framework

6. Problem • Business process governance can be broken into design-time and runtime governance, focusing on runtime policies and governance. • Two requirements: • Distributed – the process allows itself to be governed by process clients remotely. • Multi-tenant – the process allows each client to governs its own process request instances without interfering with other clients. • Business policies change frequently and policies that apply to multiple services and processes can introduce redundancy and inconsistency within service logic and contracts

8. Business Policy category

9. A Negotiation Framework for Negotiation of Coalition Policies • Negotiation, in general, is the process of making proposals, trading options, offering concessions and obtaining mutual agreement. • In order to address many different types of negotiation goals and scenarios, there is a need for a flexible negotiation system that can incorporate various alternatives and that is easily extensible and configurable. • Provide a generic negotiation system that can support many types of negotiation protocols

10. Negotiation framework • Policy analysis or evaluation capabilities • Policy negotiation capabilities Issue Attribute Offers Value entities Accept or Reject

11. Negotiation parameters • Negotiation Procedure—separate, simultaneous and sequential • Agreement implemention—sequential and simultaneous • Information model—complete or incomplete • Agent interaction • Agent cooperation • Enforcement—rewards or penalties • Negotiation time frame—infinite or finite

12. Negotiation system architecture

13. A negotiation portal • Session management • Offer authoring • Offer submission • Offer evaluation • Offer suggestion

14. Detect if your program is running inside a Virtual Machine http://www.codeproject.com/kb/system/VmDetect.aspx

15. Thanks!