Bradfordly
commented
3 years ago Proactive security design sounds like I am dreaming - thank you for calling that out! On the architecture note is it safe to assume a cloud native design is desired? In my experience, cloud native presents a unique (and fun) challenge of building an app that is both cloud native and cloud agnostic. What this means is that the distributed services of the app should be capable of running in any public cloud using those public cloud's managed cloud services. This is accomplished in large part by containerization of the services but also is dependent on the design of the actual service. Abstracting up/downstream dependencies through extensible interfaces and keep configuration of all services orthogonal through environment variables are some fundamentals for doing this.
DrewMcArthur
jbwaclawski
Considering Discord is down and I need to get to bed soon (10:25p here and I'm up at 5:00am tomorrow) I want to gather some thoughts here.
We're building a brand new product here so we have a rare opportunity to do things RIGHT. By this I mean we have the opportunity to bake security directly into every step of the process from the ground up. I don't know about some of you, but in my experiences this is too rare to pass up; too many times I'm brought onto a project to mold security around an already built product only to be told to rip pieces out because of problems with efficiency (that would not have existed if security was a baseline requirement).
I believe that step 1 here is to cobble together an "Architecture and Security" team that consists of one or two members from each discipline involved that ultimately decide how the project ends up. I don't want to remove the democracy piece of this by any means, but I don't think there exists a positive outcome for this project if every architectural and security decision are chosen based on majority preference. If done right it should work in unison with the voice of the many by taking all of the ideas and options presented then choosing what fits together best and what's best for the product.
Once this team is brought together we need to start talking about processes we can put in place to help ensure that the core principals are followed every step of the way, that security is an integral part of the conversation in every decision, and that each line of code submitted is safe and positively contributes to the mission as a whole.
Please feel free to contribute your points of view as well or poke holes in my thoughts. Just want to get the engine churning.
FYI - I'm beeficecream in Discord, may be a different name soon if I can sign into my actual account any time soon.