All Projects → microsoft → Mcw Securing Paas

microsoft / Mcw Securing Paas

Licence: mit
MCW Securing PaaS

Projects that are alternatives of or similar to Mcw Securing Paas

Pci Paas Webapp Ase Sqldb Appgateway Keyvault Oms
Azure PCI PaaS Reference Architecture
Stars: ✭ 36 (+80%)
Mutual labels:  paas, pci-dss
Cadscenario personalisation
This is a end to end Personalisation business scenario
Stars: ✭ 10 (-50%)
Mutual labels:  paas
Laravel template with vue
laravel5.5和vue.js结合的前后端分离项目模板,后端使用了laravel的LTS版本(5.5),前端使用了流行的vue-element-template项目。作为程序的起点,可以直接以此为基础来进行业务扩展。模板内容包括基础的用户管理和权限管理、日志管理、集成第三方登录,整合laravel-echo-server 实现了websocket 做到了消息的实时推送,并在此基础上,实现了聊天室和客服功能。权限管理包括后端Token认证和前端vue.js的动态权限,解决了前后端完整分离的情况下,vue.js的认证与权限相关的痛点,已在本人的多个项目中集成使用。
Stars: ✭ 763 (+3715%)
Mutual labels:  rbac
Piku
The tiniest PaaS you've ever seen. Piku allows you to do git push deployments to your own servers.
Stars: ✭ 902 (+4410%)
Mutual labels:  paas
Tke
Native Kubernetes container management platform supporting multi-tenant and multi-cluster
Stars: ✭ 776 (+3780%)
Mutual labels:  paas
Express Boilerplate
A fast, simple Node.js/Express + MongoDB + Vue.js web app boilerplate project
Stars: ✭ 25 (+25%)
Mutual labels:  web-app
Rakkess
Review Access - kubectl plugin to show an access matrix for k8s server resources
Stars: ✭ 751 (+3655%)
Mutual labels:  rbac
Caprover
Scalable PaaS (automated Docker+nginx) - aka Heroku on Steroids
Stars: ✭ 7,964 (+39720%)
Mutual labels:  paas
Eeplat
EEPlat is a metadata-driven development platform, use configuration to instead of coding to develop enterprise application.
Stars: ✭ 9 (-55%)
Mutual labels:  paas
Webside
基于RBAC的完全响应式权限管理系统
Stars: ✭ 19 (-5%)
Mutual labels:  rbac
Siteshot
Website screenshot capturer written in Go.
Stars: ✭ 18 (-10%)
Mutual labels:  web-app
Convos
Convos 👥 is the simplest way to use IRC in your browser
Stars: ✭ 789 (+3845%)
Mutual labels:  web-app
Litecloud
User management system for the server (Home Cloud).
Stars: ✭ 26 (+30%)
Mutual labels:  web-app
Syspass
Systems Password Manager
Stars: ✭ 763 (+3715%)
Mutual labels:  web-app
Rbac
Hierarchical Role Based Access Control for NodeJS
Stars: ✭ 857 (+4185%)
Mutual labels:  rbac
Hackernews
HackerNews clone built with Nuxt.js
Stars: ✭ 758 (+3690%)
Mutual labels:  web-app
Edinote
Note taking web application for self-hosting. Offers tagging & Markdown support; can be used as a simple alternative to Evernote.
Stars: ✭ 17 (-15%)
Mutual labels:  web-app
Neural Neighbors
A simple web application for browsing similar images
Stars: ✭ 23 (+15%)
Mutual labels:  web-app
Jodel Web
[PHP] JodelBlue is a Web-App and Browser-Client for the Jodel App. No registration required! Browse Jodels all over the world.
Stars: ✭ 15 (-25%)
Mutual labels:  web-app
Php Casbin
An authorization library that supports access control models like ACL, RBAC, ABAC in PHP .
Stars: ✭ 865 (+4225%)
Mutual labels:  rbac

Securing PaaS

This workshop is archived and is no longer being maintained. Content is read-only.

Fourth Coffee is an American coffeehouse chain that was founded in Seattle, Washington in 1970. It currently operates over 20,000 locations worldwide.

The CEO has established a mandate to revamp their loyalty program that starts with their platform. Other than tracking the serial number of the gift card, its balance and purchase history, Fourth Coffee does not have any direct way to associate the purchase history with the customer. They feel this is a big opportunity for them to address, and in doing so will enable them to launch their worldwide customer loyalty program.

In designing and implementing this solution, Fourth Coffee is very concerned about security. They had already launched a customer profile microsite alongside their primary website in Azure using Azure App Services, they host the website in a Web App and all logic is provided thru an API App. They would like to keep this core approach for the gift card website but extend it as appropriate with other Azure PaaS services.

A primary concern for Fourth Coffee is figuring out how to secure access to sensitive customer profile data, particularly to limit and control access by their developers. They have put together a ""solution security"" team who works in the office of the CISO (Chief Information Security Officer) that should be the only group allowed to view the secrets and keys used in production.

In addition to securing access to sensitive data, they would like to gain visibility into the security health of their solution.

Target audience

  • Application developers
  • Cloud administrators
  • Cloud architects
  • Security architects

Abstract

Workshop

This workshop is designed to provide exposure to many of Microsoft Azure's Platform-as-a-Service (PaaS) security features. The goal is to show a secure end-to-end solution that addresses concerns around sensitive data, controlling access to sensitive stores of information, controlling access to production systems and enabling secure processes for developers.

In this workshop, you will learn how to build secure solutions end-to-end with Azure Platform-as-a-Service (PaaS) services, control access to PaaS service and how to manage secrets and keys used by PaaS services.

Whiteboard Design Session

In this whiteboard design session, you will work with a group to design an end-to-end PaaS solution that combines many of Azure's security features, while protecting sensitive data from both internal and external users.

At the end of this whiteboard design session, you will be better able to design secure PaaS-based solutions that protect your systems and data from both internal and external threats.

Hands-on Lab

In this hands-on-lab, you will design an end-to-end PaaS solution that combines many of Azure's security features, while protecting sensitive data from both internal and external users.

At the end of this hands-on lab, you will be better able to develop a secure solution that takes advantage of the security features provided by an App Service Environment (ASE). You will know how to use an Azure DevOps machine and Visual Studio to deploy to the ASE after creating an app service plan. You will know how to enable a Web Application Firewall to filter requests based on the OWASP 3.0 standard and see that those requests are in fact blocked. In addition, you will know how Azure Identity Access and Management (Azure IAM) works and how those access permissions are separate from policies that may live within the actual Azure resource (such as with Azure Key Vault). You will learn how to remove sensitive information from your various resources such as Azure Functions and Web Applications and place them in the Azure Key Vault for both deployment and runtime use. As a final step, you will learn how to perform queries against Log Analytics to populate a Power BI report based on your Web Application Firewall events.

Azure services and related products

  • Azure Key Vault
  • AAD
  • AAD B2C
  • Functions
  • Cosmos DB
  • Azure Search
  • Azure Security Center
  • Log Analytics
  • App Insights
  • Azure Monitor
  • App Service Environment
  • App Gateway with WAF
  • SQL Database
  • Azure Storage

Related references

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].