Bring Your Own Team
It is easier when good Security is built in by design and default. The numbers of developers, system and network admins who incorrectly suppose they are well trained in good Information Security does not match with the breach statistics we experience.
So, Bring Your Own Cloud simply assumes quality built in by design and default that simply is not there unless, there is a team behind you. So, is BYOC that is nothing more than an increase in the speed of IT defects per second? Or, does it imply a great process and team that comes with that Cloud. Does good BYOC really mean Bring Your Own Team, BYOT?
But, wait, that smells of Fear, Uncertainty and Doubt, FUD, so it must come from an obstructionist. I could be a crank. All those years of IT and the humbling experience of Information Security could just have made me an obstructionist. Maybe, I just like putting the breaks on things. But, good breaks on your car could help you drive faster, less afraid to push the edge because you know you can control it when it matters.
What does decentralized control get us? Factions and asymetric warfare. What is Anonymous anyway beyond a BYOC organization? But, maybe its decentralized software we need. After all Java works right? It is safe, right? What language are drive by downloads written in? Or, is it near the top vulnerability for safe computing on the Internet, just short of persons presuming that "P@ssw0rd1" is a secure and cleaver idea.
But, why pick on Java.
1) Decentralized processing
2) Not Secured by Design or Default
3) Quick common use across a wide variety of platforms.
Is it a fair model for the future state of BYOC? Maybe, maybe not. Thoughts?