✨ Don’t build your cloud home on shaky foundations

If you want to create your own or to contribute to an existing GitHub project you are on the right page.

You probably wouldn’t furnish a house you’re building with a state of the art entertainment system without first installing doors and an alarm system. Similarly, it isn’t advisable to put valuable applications and data used to run your business in the cloud without ensuring the proper foundational security and governance controls are in place.

Many organizations struggle with how they want their cloud home to look, often so anxious to move that proper planning is ignored. Whether adopting PaaS, IaaS, or SaaS, properly planned governance and security foundations are key to ensuring a protected and controlled environment.

Cloud home

Critical Design Areas

Key components

Cloud Adoption Framework (CAF)

Landing zone

Management groups

Policies

• Built-In vs custom
• Audit / Deny / If Not exist

Automation

• Azure DevOps vs GitHub

RBAC

• Least privileges

• Groups instead of direct user assigments

Naming convention

• Define a naming convention before any deployment
• Exemple of naming convention

Tagging

• Main tags (Env, CreationDate, ...)

Network

• Hub and spoke topology
• Ip adress plan
• Peering
• IPAM

VMS

• NAT

Extra tools

• Az Goviz

• Naming convention tool