Welcome!

Cloud Security Authors: Yeshim Deniz, Liz McMillan, Elizabeth White, Ravi Rajamiyer, Pat Romanski

Related Topics: @DevOpsSummit, Agile Computing, @CloudExpo, Cloud Security

@DevOpsSummit: Blog Post

Make Security Part of Your Development Lifestyle | @DevOpsSummit #Cloud #DevOps #Security

It is my firm belief that developers today are not focused on security during periods of head-down development

It is my firm belief that developers today are not focused on security during periods of head-down development. I would love to know the percentage of web developers that know about the Open Web Application Security Project or OWASP. This non-profit organization is simply focused on the secure development of web applications. Their education and guidance is freely available to the public yet I do not read much about security in the public development circles, blogs, etc.

OWASP first published a book called the Code Review Guide in 2006. In 2006, I led a team on the development of a large web application for the administration of the Women, Infants, and Children (WIC) program for the state of Massachusetts. We were doing weekly code reviews and our focus was on best practice and quality development of the software. Quality code is secure code.

OWASP had noticed in their 2006 publication where organizations had implemented a proper code review function into their software development lifecycle (SDLC), they enjoyed remarkably better code from a security perspective. The team code review does not, however guarantee a security consideration or security focus on the architecture, designs, patterns, or methods being implemented. This consideration must come from the developers themselves.

Urgency
Throughout my career I have strived to create a sense of urgency where I have had the authority to bring about change in the organization. As a business owner, I receive about 10-15 whitepapers from various sources daily covering many IT subjects but most of these papers are communicating the need for more security in our IT infrastructures, products and services, on-premise or off. The education and intelligence of sorts is mostly marketing by organizations to provide security tools or consulting with the promise to make my business more secure. They are creating the sense of urgency here by using the psychology of fear in their publications.

Security of IT infrastructure, products, or services starts from within. Who creates these infrastructures, products, or service offerings? Your development staff, team, or group(s). They also define the level of security that protects your assets. We all need to create a sense of urgency across the entire IT department. And, it starts with you.

Culture
The culture of security is almost non-existent today. Early in my career the term DevOps did not exist. Network and development personnel were separated by the culture of the type of work they did. Networks administrators and help-desk employees protected everything. They opened and closed firewall ports. They enforced continual password changes. They required red-tape for employees that forgot those seriously secure passwords. They lived and operated within a culture of distrust. "Why do you need to change your password?", they asked. "You already have firewall access to port 80. Why do you need port 8080?", would be the question. They live a lifestyle of distrust. It seemed respectable at the time. Was the answer to security to choke the creativity of the development staff?

The development staff would operate within a culture of creativeness. If it can be done, we'll do it. The developers would figure out all the ways to bypass the in-place security practices and get the job done. In many cases, these practices were unknown to the software development manager or director. This culture still exists today within many organizations. DevOps is an attempt to place a trusted liaison between the distrusting network folks and those flip-flop-wearing, loose-cannon developers. It sounds promising. We now have a true mediating faction to resolve process conflicts between camps. Discrimination between the cultures will now be non-existent. This is not my belief.

Proposal
My proposal is a complement to DevOps. I propose we give the IT community one more acronym, and in this case, called SCALE or Security Consideration and Lifestyle Exchange. I'm going to hereafter refer to we as the shorts and flip-flops faction or software developers. We need to live a lifestyle of security consideration from now until eternity or until spoofing, tampering, repudiation, disclosure, denial of service, and elevation of privilege cease to exist, which ever comes first. The acronym SCALE was purposely spelled scale to help with conceptual thinking within this new lifestyle. If we don't always consider security vulnerabilities when we code, these inherent risks to the software, truly scale within the code-bases to which we commit. Much of the software written today is owned by an organization and not the individual developers. However, each developer needs to assume ownership of the code that she develops. And, we also need to exchange education about security as we do our code reviews and within any other discussions related to software development and security.

If you are a homeowner, you probably lock the doors at night. You take care of your home and you protect your investment. Your home is your shelter. It's safe and secure. I've had the mind-boggling opportunity to work with developers from around the world that assumed no ownership whatsoever of the code they were responsible for. That's ludicrous. This gives me the sense of urgency to correct this problem even though it's not my responsibility. It makes me want to add the bullet - accountable for the quality of your code to all these developer opportunities that ride the internet daily. Emails authored by senior talent recruiters and technical companies, that provide talent to our enterprises, and do not know what their clients really want in a software developer.

We need to consider security with every project start, code review, and subsequent release of the software. We should also do a threat model during the inception phase or just before we start development. We should do another threat model just before the first release and also discuss the model with each subsequent release. Security should be how we roll my friends. It should be our new lifestyle. Whether the code belongs to you or your employer, it should be the best that it can be. That depends on you solely.

Conclusion
I hope that you will add SCALE or Security Consideration and Lifestyle Exchange right next to the SDLC acronym in your minds. I also hope that you (we), the development community continue to move in this direction. Make the consideration of security part of your personal process. Think of it as a revolution. Don't rush the quality of your work. And, by all means, have it code reviewed. If you cheat yourself on testing code coverage, at least let a cube-mate look at it when you're done.Be a listener and learn from your seniors. Know that when you SCALE, your work doesn't add to the increasing risk of security vulnerabilities with the growth of your software repositories.

More Stories By David L. Whitehurst

David L. Whitehurst is Enterprise architect and Open-Source development expert. He has designed, implemented, and integrated enterprise IT systems, desktop applications, web applications, web services and maintained/tuned system infrastructures. David’s goal now is to further the use of continuous improvement practices where needed and to improve the continuing adoption and security of enterprise cloud-hosted infrastructure.

His IT career has spanned over 3 decades, and he has been exposed to broad business verticals or subject domains. He has worked on the engineering of nuclear submarines and has been responsible for the development of financial web service operations for a major bank. David leads his team or development staff by example. He gets it done. He has recently acquired the MuleSoft Certified Developer – Integration and API Associate license.

IoT & Smart Cities Stories
The deluge of IoT sensor data collected from connected devices and the powerful AI required to make that data actionable are giving rise to a hybrid ecosystem in which cloud, on-prem and edge processes become interweaved. Attendees will learn how emerging composable infrastructure solutions deliver the adaptive architecture needed to manage this new data reality. Machine learning algorithms can better anticipate data storms and automate resources to support surges, including fully scalable GPU-c...
Machine learning has taken residence at our cities' cores and now we can finally have "smart cities." Cities are a collection of buildings made to provide the structure and safety necessary for people to function, create and survive. Buildings are a pool of ever-changing performance data from large automated systems such as heating and cooling to the people that live and work within them. Through machine learning, buildings can optimize performance, reduce costs, and improve occupant comfort by ...
The explosion of new web/cloud/IoT-based applications and the data they generate are transforming our world right before our eyes. In this rush to adopt these new technologies, organizations are often ignoring fundamental questions concerning who owns the data and failing to ask for permission to conduct invasive surveillance of their customers. Organizations that are not transparent about how their systems gather data telemetry without offering shared data ownership risk product rejection, regu...
René Bostic is the Technical VP of the IBM Cloud Unit in North America. Enjoying her career with IBM during the modern millennial technological era, she is an expert in cloud computing, DevOps and emerging cloud technologies such as Blockchain. Her strengths and core competencies include a proven record of accomplishments in consensus building at all levels to assess, plan, and implement enterprise and cloud computing solutions. René is a member of the Society of Women Engineers (SWE) and a m...
Poor data quality and analytics drive down business value. In fact, Gartner estimated that the average financial impact of poor data quality on organizations is $9.7 million per year. But bad data is much more than a cost center. By eroding trust in information, analytics and the business decisions based on these, it is a serious impediment to digital transformation.
Digital Transformation: Preparing Cloud & IoT Security for the Age of Artificial Intelligence. As automation and artificial intelligence (AI) power solution development and delivery, many businesses need to build backend cloud capabilities. Well-poised organizations, marketing smart devices with AI and BlockChain capabilities prepare to refine compliance and regulatory capabilities in 2018. Volumes of health, financial, technical and privacy data, along with tightening compliance requirements by...
Predicting the future has never been more challenging - not because of the lack of data but because of the flood of ungoverned and risk laden information. Microsoft states that 2.5 exabytes of data are created every day. Expectations and reliance on data are being pushed to the limits, as demands around hybrid options continue to grow.
Digital Transformation and Disruption, Amazon Style - What You Can Learn. Chris Kocher is a co-founder of Grey Heron, a management and strategic marketing consulting firm. He has 25+ years in both strategic and hands-on operating experience helping executives and investors build revenues and shareholder value. He has consulted with over 130 companies on innovating with new business models, product strategies and monetization. Chris has held management positions at HP and Symantec in addition to ...
Enterprises have taken advantage of IoT to achieve important revenue and cost advantages. What is less apparent is how incumbent enterprises operating at scale have, following success with IoT, built analytic, operations management and software development capabilities - ranging from autonomous vehicles to manageable robotics installations. They have embraced these capabilities as if they were Silicon Valley startups.
As IoT continues to increase momentum, so does the associated risk. Secure Device Lifecycle Management (DLM) is ranked as one of the most important technology areas of IoT. Driving this trend is the realization that secure support for IoT devices provides companies the ability to deliver high-quality, reliable, secure offerings faster, create new revenue streams, and reduce support costs, all while building a competitive advantage in their markets. In this session, we will use customer use cases...