{"action":"created","issue":{"url":"https://api.github.com/repos/cn-security/safe/issues/106","repository_url":"https://api.github.com/repos/cn-security/safe","labels_url":"https://api.github.com/repos/cn-security/safe/issues/106/labels{/name}","comments_url":"https://api.github.com/repos/cn-security/safe/issues/106/comments","events_url":"https://api.github.com/repos/cn-security/safe/issues/106/events","html_url":"https://github.com/cn-security/safe/issues/106","id":381601300,"node_id":"MDU6SXNzdWUzODE2MDEzMDA=","number":106,"title":"Build a Guideline for LargeOrg Security Teams","user":{"login":"andrei821","id":2915659,"node_id":"MDQ6VXNlcjI5MTU2NTk=","avatar_url":"https://avatars3.githubusercontent.com/u/2915659?v=4","gravatar_id":"","url":"https://api.github.com/users/andrei821","html_url":"https://github.com/andrei821","followers_url":"https://api.github.com/users/andrei821/followers","following_url":"https://api.github.com/users/andrei821/following{/other_user}","gists_url":"https://api.github.com/users/andrei821/gists{/gist_id}","starred_url":"https://api.github.com/users/andrei821/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/andrei821/subscriptions","organizations_url":"https://api.github.com/users/andrei821/orgs","repos_url":"https://api.github.com/users/andrei821/repos","events_url":"https://api.github.com/users/andrei821/events{/privacy}","received_events_url":"https://api.github.com/users/andrei821/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-11-16T13:32:58Z","updated_at":"2018-12-22T18:39:31Z","closed_at":null,"author_association":"NONE","body":"[Some]Security teams working within large organizations have a traditional approach when designing security requirements for newly deployed cloud native environments. Usually this traditional approach is defined by creating firewalls around applications, filtering EGRESS traffic using corporate proxy, while manually managing access rules.\r\nHaving in mind that security is paramount for most organizations, security teams prefers to reduce agility by holding on legacy processes and procedures.\r\nI feel that a clear guideline describing basic cloud native security best practices and comparing them with the traditional aproach will have a great benefit. "},"comment":{"url":"https://api.github.com/repos/cn-security/safe/issues/comments/449590056","html_url":"https://github.com/cn-security/safe/issues/106#issuecomment-449590056","issue_url":"https://api.github.com/repos/cn-security/safe/issues/106","id":449590056,"node_id":"MDEyOklzc3VlQ29tbWVudDQ0OTU5MDA1Ng==","user":{"login":"pragashj","id":31199168,"node_id":"MDQ6VXNlcjMxMTk5MTY4","avatar_url":"https://avatars2.githubusercontent.com/u/31199168?v=4","gravatar_id":"","url":"https://api.github.com/users/pragashj","html_url":"https://github.com/pragashj","followers_url":"https://api.github.com/users/pragashj/followers","following_url":"https://api.github.com/users/pragashj/following{/other_user}","gists_url":"https://api.github.com/users/pragashj/gists{/gist_id}","starred_url":"https://api.github.com/users/pragashj/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pragashj/subscriptions","organizations_url":"https://api.github.com/users/pragashj/orgs","repos_url":"https://api.github.com/users/pragashj/repos","events_url":"https://api.github.com/users/pragashj/events{/privacy}","received_events_url":"https://api.github.com/users/pragashj/received_events","type":"User","site_admin":false},"created_at":"2018-12-22T18:39:31Z","updated_at":"2018-12-22T18:39:31Z","author_association":"COLLABORATOR","body":"This is an interesting idea. By traditional, do you mean standards or\nimplementation (architecture)?\n\nOn Fri, Dec 21, 2018, 10:34 AM Geri Jennings <notifications@github.com\nwrote:\n\n> It might be interesting to produce a whitepaper that compares the\n> cloud-native security landscape / the best practices that it highlights\n> with what traditional security might look like.\n>\n> —\n> You are receiving this because you are subscribed to this thread.\n> Reply to this email directly, view it on GitHub\n> <https://github.com/cn-security/safe/issues/106#issuecomment-449465015>,\n> or mute the thread\n> <https://github.com/notifications/unsubscribe-auth/AdwPwMek9cLpEl94JuE627iBGCUnncIVks5u7SnJgaJpZM4YmQz_>\n> .\n>\n"}}
{"actor":{"display_login":"pragashj"}}