The Ongoing Dilemma: Speed vs. Safety
For too long, organizations have faced a dilemma in building software, going fast, and delivering required functionality to market quickly while sacrificing security. Stay safe by performing manual threat modeling, risk assessments, and secure coding practices while slowing down development. The key question most organizations have is — how can we become “Fast and Safe”?
This is not just a technology issue.
It is a competitive issue. Many organizations are choosing the fast and risky approach to build digital products faster while sacrificing security. Others are doing all the right things by infusing security and compliance but can only build products at a snail’s pace and end up losing to irresponsible competitors.
In this cost savings guide, we will address the challenges faced by organizations that have adopted the “Fast and Risky” approach and want to move away from it to minimize the associated risks (and brand damage), and also those that have been taking the “Slow and Safe” approach and want to speed up time to market with safety.
Improve Time to Market While Staying Safe
Speed and security can work in unison.
Organizations can go “Fast and Safe” by using a new approach, balanced development automation, that helps them accelerate software releases while improving product security. It operationalizes security and privacy policies and regulatory standards, turning them into actionable controls or tasks that guide engineering through every step of development. Using this approach, developers can get security/privacy instructions as they write code.
Balanced development automation allows your organization to build secure products nearly as fast as if they were being built without security or compliance at all and as safely as if they were painstakingly built under the guidance of human experts.
HOW BALANCED DEVELOPMENT AUTOMATION WORKS
Balanced development automation helps organizations accelerate software releases while improving product security. It works by automating key portions of your proactive security processes, such as threat modeling, risk assessment, and privacy, by designing reviews and infusing secure development and best practices into your workflows. The system acts like a guide through every step of development, delivering security and compliance instructions for that part of the work. When the project is finished, the system can compile insights about what was done and what wasn’t so that your business leaders can get a view of risks across all applications.
Balanced development automation makes sure software gets built right in the first place. Ultimately, it enables you to push software to customers faster while giving you confidence that it is also safe.
WHY CLIENTS ADOPT SD ELEMENTS
Our clients have witnessed one or more of the following quantifiable benefits from implementing SD Elements within their organization:
In addition to the direct cost savings noted in the previous section, SD Elements also introduces new capabilities and benefits:
- Enables your organization to utilize security experts only for high-value security work by freeing up their time from manual processes.
- Drives efficiency in proactive security processes, which is particularly valuable when security teams are mandated to do more with the same budget
- Provides your organization with a better understanding of corporate risk and compliance posture related to applications.
- Reduces your risk of brand damage by decreasing the number and severity of security flaws in applications.
- Improves your team’s secure development knowledge as they implement automatically generated controls and consume just-in-time training.
- Improves relationship and collaboration between Security and Development teams to implement security measures while also reducing duplicate efforts and the need for meetings and in-person conversations.
- Drives consistency in your proactive processes, thereby improving the accuracy of reporting.
- Simplifies the audit process as our solution helps you with transparency and reporting
- Implement consistency in data between disparate systems as a result of automated integrations.
Cost Savings Framework: SD Elements Implementation
Processes to proactively embed security and compliance in software development vary by organization, and thus, results for adopting a balanced development automation solution like SD Elements will also vary. To drive consistency and efficiency in processes and outcomes, SD Elements distills key activities common in some proactive processes, such as threat modeling and secure coding, into four steps:
- Information Gathering: SD Elements guides users in a systematic way so that projects are onboarded efficiently. It gathers information about your project, such as its technology stack, deployment infrastructure, security testing tools, and compliance requirements.
- Expert Assessment: SD Elements analyzes the information and correlates it with regulations, policies, and best practices in the knowledge base.
- Recommendations: SD Elements makes intelligent decisions on risks, controls, just-in-time training, and even code samples specific to your technology and industry and can deliver these directly to your issue-tracking tools. It also rapidly classifies your project into relative risk grouping to help your teams manage projects by potential risk.
- Validation and Reporting: SD Elements tracks controls and can also validate the status of certain tasks automatically by capturing updates from security testing tools. This gives you a near real-time view of the risk status of your projects and the controls in scope for each at any time in the project life cycle.
SD Elements drives quantifiable benefits in four use cases: threat modeling, compliance, secure development, and risk assessment. In the following section, the key steps in certain use cases are summarized in the context of the four-step framework discussed above to help your organization think about and model the potential and actual value of SD Elements.
Many companies are now faced with a dilemma: Should they hire additional experts or outside consultants to address their threat modeling backlog or adopt a new way by automating key activities in threat modeling to help reduce overall risk?
Our research suggests that most organizations currently perform threat modeling using tools such as whiteboards or automated diagramming tools that require security expertise. Sounds familiar? While these tools may seem practical, they are very difficult to scale and require substantial human capital to use and maintain.
SD Elements distills the key steps in threat modeling to streamline and accelerate the process:
SECURE SOFTWARE DEVELOPMENT
Many organizations write code and then identify vulnerabilities using code scanners or penetration tests. Based on their risk tolerance, they make a decision to either:
- Remediate the vulnerabilities, which means spending a significant amount of time and thus delaying product releases.
- Accept the risks, which means allowing products with critical vulnerabilities to be released.
Because of the rising number of breaches and concerns about data privacy, more and more organizations are “shifting security left” and ensuring code is developed securely from the beginning.
The use of SD Elements freed up 40% of the security professionals’ time, resulting in savings equivalent to 14 FTEs and allowing them to work on other security initiatives. At an average burdened salary of $150,000, this translated to savings of $840,000 per year.
Further, based on a study conducted by Security Compass in 2019, SD Elements addresses at least 92% of the vulnerabilities found in penetration testing reports. Using SD Elements early in the process as a proactive security measure significantly reduces vulnerabilities and eradicates the need for remediation later.
Regulatory standards and internal corporate policies are constantly updated and complex to understand. Managing these requirements with disparate spreadsheets, email, and file storage solutions can get difficult as you scale your application portfolio.
SD Elements translates complex standards into easy-to-understand tasks and provides continuous visibility into the status of controls and evidence of adherence to compliance requirements.
With SD Elements as a key enabler, the software factory was able to reduce the time required to obtain an ATO from 12 months to 2 weeks, achieving an operational efficiency of roughly 96%.
Further, SD Elements allows the DOD software factory to achieve cATO for ongoing software delivery by enabling the assessment team to trace compliance with security standards easily.
SD Elements is used by other federal government agencies and programs in a similar manner, tailored to each assessment team’s requirements and technology stack.
Risk assessments are a core part of risk management in an organization. As digital transformations continue to grow, so will the need for risk assessments delivered at a pace that matches the speed and scale of development. This presents a challenge as scaling risk assessments requires the expertise of scarce and exhausted subject matter experts.
Risk assessments also rely on the knowledge and experience of the assessors, which can result in inconsistent results and lead to an incomplete view of risks. Moreover, risk assessments are typically manual and can take weeks, and in some cases months, to complete. Basically, it is an expensive process that slows time to market.
With SD Elements, organizations can streamline risk assessment processes, such as the identification of weaknesses and controls and automated delivery of controls to the issue tracking tool. The benefits for the customer? Savings in time and costs, increased velocity of assessments (i.e., number of assessments in a given period), and improved quality and consistency of risk assessment outcomes.
Gaining Buy-In from Business Leaders
Creating a program that balances the speed of software delivery and risk management is a critical competitive differentiator for businesses. Most organizations do not have an existing budget to pay for this initiative and often have to reallocate budget from other areas. We are listing some strategies our clients have used to gain buy-in for SD Elements.
Use Agile or DevOps program funds: Many organizations fund large-scale Agile and/or DevOps initiatives. SD Elements automates proactive processes, which is a critical success factor to these initiatives in security-conscious and/or heavily-regulated companies. Our clients have been successful in using discretionary funds from these programs to invest in SD Elements.
Reallocate contractor, services, and/or headcount budget for proactive security processes: Many organizations contract out or hire security analysts, architects, and consultants to perform proactive processes such as threat modeling, risk assessments, privacy by design, etc. Reallocate part of this budget for tools that automate these processes so that you are getting wider reach from your experts rather than having to hire more of them.
Look at your mix of proactive vs. reactive security processes: Most organizations have line items for several different reactive security testing processes. Contrast the budget you have allocated to “reactive” security testing tools vs. “proactive” security (i.e., before code is written). More and more companies are looking at balancing these activities by critically reviewing their reactive tools. For instance, how much value are you getting from dynamic analysis tools? How much overlap do you have between various tools? The end result may be a shift to proactive tools like SD Elements.
Use security awareness budget: Many organizations have separate budgets for security awareness training. SD Elements contains both instructions on security practices and embedded training videos with Just-In-Time Training (JITT). Security Compass can also bundle in e-learning offerings, including standard security awareness training. Companies can leverage the security education budget to pay for SD Elements.
Use compliance budget: Some organizations have more flexibility with allocating budgets to meet compliance needs. Consider your current compliance status with respect to security & privacy by design as they relate to PCI, GDPR, CCPA, FFIEC requirements, etc. If you are “out of compliance,” use this to obtain funding for SD Elements, as it will be a more cost-effective option, in most cases, than using additional personnel/contractors.
Use GRC budget: Governance, Risk, and Compliance (GRC) programs are often large and multi-faceted. Their primary value is better risk management. Considering the business value of SD Elements related to improved time to market and traceability of risk/compliance, find out if the GRC budget can be trimmed back to invest in SD Elements. SD Elements can be positioned to provide the “operational/day-to-day” components of DevSecOps that feed data into your GRC solution via configurable integration.
Introduce a chargeback model to the Line of Business: Large software development projects are often expensive. The true value of faster time to market through proactive process automation is of benefit to the business. Consider having each line of business pay for SD Elements for their applications. The cost for one application is typically a small fraction of their budget.