-
Notifications
You must be signed in to change notification settings - Fork 330
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update checklist log oriented backlog immutable storage , H02.04, G03.11, F03.21 #637
Update checklist log oriented backlog immutable storage , H02.04, G03.11, F03.21 #637
Conversation
…ements exceed seven years. Use immutable storage with a write-once, read-many policy to make data non-erasable and non-modifiable for a user-specified interval
…, real-time alerts
Hey @hgotar1 thanks for this! Please do let us know when this PR is ready for review |
Updated B01.01 to include how to check for service principals.
Updated more info link for macsec recommendation which was incorrectly pointing to NSG before
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed and approved, added changes for D02.01 and B01.01
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Making a change note on the duplicate of "G03.02"
Add 3 entries in the JSON check lists
H02.04
Establish a process for using code to implement quick fixes. Always register quick fixes in your team's backlog so each fix can be reworked at a later point, and you can limit technical debt.
https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/considerations/automation
G03.11
Use an Azure Event Grid-based solution for log-oriented, real-time alerts
https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/landing-zone/design-area/security
F03.21
Export logs to Azure Storage if your log retention requirements exceed seven years. Use immutable storage with a write-once, read-many policy to make data non-erasable and non-modifiable for a user-specified interval.https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/landing-zone/design-area/management-platform