Customer Data and Security Breach Ligitation

At Zappos.com, Inc. Zappos.com's customers are detained due to the vague nature that they are not referring to the terms of use of the package and because they are in breach of the contract I judged that it was not done. Since running, Zappos specifies the right to change it at any time without notifying the customer. The court ruling above takes precedence over companies that use the Browse Packaging Agreement and include phrases in the contracts so that the contract can be changed at any stage.

Security - When using a single database, all the data is gathered. If a security violation occurs, this can be a big problem. If a single account is compromised, all of the customer's data may be vulnerable. In a multi-instance architecture, only one customer's data may be at risk. The recent increase trend is that end users attach their own domain name to the application. Even Kubernetes has a self-service level (pressing a button to direct the user's domain to the pod), there is a suitable tool to make this process easier. You can do this with a system like Nginx Ingress.

Recently, security infringement reports seem to be occurring almost every day, and customer data and personal identifiable information (PII) are infringed to some extent. For example, Verizon's report includes data loss for over 14 million customers. A cyber criminal attacked a major Equifax (probably the most severe data breach in history) of a credit research company and stealed 144 million information such as name, birth date, social security number, address, driver's license number, etc. It was. In a more secret case, theft occurs, such as obtaining information from the trash can. Alternatively, when you shop at a restaurant, the waiter either polish your credit card number or simply write it down. There are many laws concerning protection of customer information such as Sarbanes-Oxley, HIPAA, GLBA.