tag-security
tag-security copied to clipboard
cncf
Chaos Engineering Paper - App Delivery TAG looking for Security Contributors
Description: App delivery TAG is working on a Chaos Engineering White paper and will like to have contribution from tag Security. This will be exciting piece of work and integration with App Delivery TAG.
Initiative is just starting and details can be found at : https://docs.google.com/document/d/10l262yuX_Zj8ht1pqKlSZAk4-KxY1tc-PaVmbqIsoDw/edit
Impact: Chaos Engineering still needs to build security resiliency in their processes and ensure failures don't lead to security incidents and the apps/services can recover with security policies and controls in place, so its pertinent to build security into the Chaos engineering of apps/service
Scope: "not yet determined"
Additional info:
- Slack channel #chaoseng-cloudnative-whitepaper
Hello, I'd like to offer to help in some capacity, whether it's writing on security impact/challenges or as a security editor later in the process, reading through the recommendations and looking for security challenges in described practices.
@hyakuhei @pratiklotia Have you been hooked into this yet? if so how is it going?
This issue has been automatically marked as inactive because it has not had recent activity.
![stale[bot] avatar](https://avatars.githubusercontent.com/in/1724?v=4 "Published by a pub.dev verified publisher"){kind=small}
@achetal01 is this something that you're tracking, any update on this? if the paper is completed we can close this issue
This issue has been automatically marked as inactive because it has not had recent activity.
The paper still appears to be a WIP as of today the current version is 1.0 and in status Draft and can be found here.
This issue has been automatically marked as inactive because it has not had recent activity.
yes I am tracking this, let me follow up with the group and will update the issue.
Thank you
On Wed, Dec 1, 2021 at 7:41 AM Brandon Lum @.***> wrote:
@achetal01 https://github.com/achetal01 is this something that you're tracking, any update on this? if the paper is completed we can close this issue
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cncf/tag-security/issues/678#issuecomment-983766250, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARO764RFLFKXHJMP5HEYRK3UOY62NANCNFSM455KHEXQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
This issue has been automatically marked as inactive because it has not had recent activity.
It looks like the app delivery tag didn't get around the paper's publication. At least I couldn't find it. Does look from the google doc link that a number of tag security folks chimed in with feedback. Given that round of comment was completed, I'll proceed with closing the issue for now.
