Understanding Software Vulnerabilities
 

Understanding Software Vulnerabilities

on

  • 153 views

This deck was presented during a webinar session yesterday by Joe Basirico, VP, Security Services with Security Innovation. ...

This deck was presented during a webinar session yesterday by Joe Basirico, VP, Security Services with Security Innovation.

I built it to: build on use cases presented in pt 1 session; present a five-step best practices approach to determining how you prioritize your software testing strategy; and then how you map SI's TeamMentor product to remediating vulnerable code with the prescriptive guidance and code snippets that ship as part of the content libraries in TeamMentor.

Statistics

Views

Total Views
153
Views on SlideShare
153
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Understanding Software Vulnerabilities Understanding Software Vulnerabilities Presentation Transcript

    • UNDERSTANDING YOURSOFTWARE VULNERABILITIESFrom Identification to Verification to Remediation (Part 2 in our 3-part series)
    • TODAY’S PRESENTERJoe BasiricoVP, Security ServicesSecurity Innovation
    • TODAY’S AGENDADevelopment and Security teams are looking for a better process to fix software vulnerabilities.1.Challenges organizations are facing in identifying, verifying and fixing vulnerable software code.2.Four defined use cases - where does your organization fit in?3.Five key best practices you should consider in determining your approach.4.Practical demonstration: ‣ A series of simulated tests ‣ Measuring the impact of those results ‣ Interpreting test results ‣ Correlation of results through TeamMentor for remediation
    • WHO WE AREApplication Security Experts • 10+ Years vulnerability research • Security Testing Methodology adopted by SAP, Microsoft, Symantec • Authors of 8+ booksProducts and Services • Standards - Best Practices • Education - CBT & Instructor-Led • Assessment - Software and SDLCReducing Application Security Risk • Critical Vulnerability Discovery • Secure SDLC Rollout • Internal Competency Development
    • OUR APPROACH• Standards: Create security policies, align dev activities with standards and compliance requirements, fix vulnerabilities.• Education: Create internal expertise through eLearning, Instructor-led and virtual classroom training.• Assessment: Assess software apps against online and other threats and recommend remediation techniques.
    • COMMON USE CASES1.Development teams don’t know where to go for best practices guidance on software vulnerabilities.2.There’s a need to communicate and share intelligence around specific vulnerabilities with your team.3.Teams need to fix vulnerabilities and map to internal policies.4.There’s a market need for making more sense of static analysis results to get to full-circle remediation.
    • WHERE CAN DEVELOPERS GO FOR THE GUIDANCE THEY NEED?Use Case 1- Security Team•A software vulnerability has been identified.• Youneed to verify it and need more information about it.• What do you do, and where do you go for guidance?
    • HOW CAN YOU SHARE THE INFORMATION?Use Case 1I - Security Team• You’veverified a software vulnerability.• You need to communicate the details of that vulnerability or set of vulnerabilities to your team.• How is this accomplished most effectively?
    • INTEGRATING WITH WHAT YOU ALREADY HAVEUse Case III - Development Team• You’ve verified a given vulnerability, and can now prioritize it.• You have knowledge internally, or security policies you need to map to.• How can I do this in a streamlined way?
    • DOING MORE WITH YOUR TEST RESULTSUse Case IV - Development Team with Tools• The tool reports findings.• Youneed to make more sense of the results.• Thefindings point to guidance specific to the findings.• Fix what you’ve found. Re-scan.
    • DETERMINE YOUR RISK TOLERANCE Understand your level of risk first. Determine your apps second.• Take an inventory of your high-risk applications.• Determine the business criticality of those applications.• What’syour attack probability and how do you define your attack surface?• Consider the overall business impact, security threats and compliance mandates.• Rank your applications accordingly.• Startthinking about the most effective set of testing tools.
    • DEFINE DATA AND APPLICATIONS Classify your data relative to sensitivity, usage and risk metrics. Then prioritize your applications.• How sensitive is your data in a given application(s)?• Does that data pertain to internal mandates or federal regulations?• Threat modeling can determine threats, attacks, and the frequency and severity they are executed with.• Rankand prioritize your applications accordingly.• Compile the most effective set of testing tools.
    • PRIORITIZE YOUR APPLICATIONSRank your applications using a formulaic approach to measuring risk. Application Criteria Threat Sensitive Compliance Customer- Lifespan Rating Data Stringency Facing Tier 1 Restricted Long High Yes Tier 2 Private Mid Medium Yes Tier 3 Public Short N/A No
    • MAP ACTIVITY TO YOUR CRITERIA Implement your security testing strategy. Depth, Breadth, FrequencyThreat Static Dynamic Manual Pen ThreatRating Analysis Analysis Test Modeling Complete/ Complete/ Complete/ Complete/ Frequency Frequency Frequency Frequency Required/Major Required/Major Required/Per Required/PerTier 1 code changes code changes Milestone Release Suggested/ Required/ Required/Per Suggested/PerTier 2 Monthly Quarterly Release Release Optional/ Required/ Optional/As Optional/AsTier 3 Quarterly Annually Needed Needed
    • SELECT YOUR TOOLS Selecting your tool(s) should be the final step before you start testing.• Apply your rankings to your tools selection.• Determineyour combination of automated vs manual tools. - Consider how many applications, how much code and time-to-result. - Do you need them to run on their own, or are they better used for a singular, manual purpose? - Assume that automated tools cannot target business logic attacks.• Interpret your scan results with remediation in mind
    • SECURE DEVELOPMENT GUIDANCEA Real-Time In-Practice Companion Containing 4500+ Articles of Prescriptive Guidance and Code
    • TRY TEAMMENTOR TODAY!Evaluation Version: • OWASP Guidance Library (Creative Commons content) • Install locally or use web version • Watch a video: http://bit.ly/Vra3OS • Download it: https://teammentor.net/Enterprise and Partner Versions: • Full set of guidance libraries (4500+ articles) • Single user, cloud instance, business unit, and enterprise-wide pricing available • Partner organization licensing • Contact us: getsecure@securityinnovation.com