Top Banner
BUILDING A PRODUCT SECURITY INCIDENT RESPONSE TEAM: LEARNINGS FROM THE HIVEMIND KYMBERLEE PRICE SENIOR DIRECTOR OF RESEARCHER OPERATIONS
24

[Webinar] Building a Product Security Incident Response Team: Learnings from the Hivemind

Jan 15, 2017

Download

Technology

bugcrowd
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: [Webinar] Building a Product Security Incident Response Team: Learnings from the Hivemind

BUILDING A PRODUCT SECURITY INCIDENT RESPONSE TEAM: LEARNINGS FROM THE HIVEMIND KYMBERLEE PRICE SENIOR DIRECTOR OF RESEARCHER OPERATIONS

Page 2: [Webinar] Building a Product Security Incident Response Team: Learnings from the Hivemind

WHOAMI?

•  Senior Director of a Red Team

•  PSIRT Case Manager

•  Data Analyst

•  Internet Crime Inves<gator

•  Security Evangelist

•  Behavioral Psychologist

•  Lawful Good

@kym_possible

Page 3: [Webinar] Building a Product Security Incident Response Team: Learnings from the Hivemind

AGENDA •  People

•  Process

•  Infrastructure and Technology

•  PiEalls

•  Free Resources

Page 4: [Webinar] Building a Product Security Incident Response Team: Learnings from the Hivemind

BUT WHAT ABOUT ISO STANDARDS!? •  In April 2016 ISO 29147 on Vulnerability Disclosure techniques was made free to the

public.

•  This is awesome

•  The related standard on vulnerability handling processes, ISO 30111 costs approx $60 USD.

Page 5: [Webinar] Building a Product Security Incident Response Team: Learnings from the Hivemind

PEOPLE

Page 6: [Webinar] Building a Product Security Incident Response Team: Learnings from the Hivemind

COMMON SIRT STRUCTURES

•  Technology •  Cloud/Service or Installed SoYware?

•  Resources •  $$$

Page 7: [Webinar] Building a Product Security Incident Response Team: Learnings from the Hivemind

COMMON SIRT STRUCTURES

•  Technology •  Cloud/Service or Installed SoYware?

•  Resources •  $$$

UserAc(onRequired

TechProgramManager

SecurityEngineer

Comms(op(onal)

UserAc(onNotRequired

TechProgramManager(op(onal)

SecurityEngineer

Page 8: [Webinar] Building a Product Security Incident Response Team: Learnings from the Hivemind

TYPICAL ROLE RESPONSIBILITIES

TechProgramManager

Triage Documenta(on Priori(za(on Repor(ng WriteAdvisories

SecurityEngineer TechnicalRepro POCExploit CodeReview&

VariantHun(ng ValidateFix ReviewAdvisories

Comms ReviewAdvisories

CustomerSupportLiaison

PressReleases&Response

Page 9: [Webinar] Building a Product Security Incident Response Team: Learnings from the Hivemind

PROCESS

Page 10: [Webinar] Building a Product Security Incident Response Team: Learnings from the Hivemind

SDL OVERVIEW

Training Requirements Design Implementa(on Verifica(on Release Response

Page 11: [Webinar] Building a Product Security Incident Response Team: Learnings from the Hivemind

INCIDENT RESPONSE PROCESS

Iden1fyIssue1 Assess

Impact2 Dev&TestFix3 Release

w/CVE4 PostRelease5

Soyou’reasoHwarevendor…

Page 12: [Webinar] Building a Product Security Incident Response Team: Learnings from the Hivemind

INCIDENT RESPONSE PROCESS

Iden1fyIssue1 Assess

Impact2 Dev&TestFix3 Release

w/CVE4 PostRelease5

Soyou’reasoHwarevendor…

Butwait!

Thevulnerability

was

inathirdpartylib

rary!

Page 13: [Webinar] Building a Product Security Incident Response Team: Learnings from the Hivemind

INCIDENT RESPONSE PROCESS

Iden1fyIssue1 Assess

Impact2 Dev&TestFix3 Release

w/CVE4 PostRelease5

Iden1fyIssue1 Assess

Impact2 Dev&TestFix3 Releasefix

(+advisory?)4 PostRelease5Soyou’reasoHware

vendor…

Butwait!

Thevulnerability

was

inathirdpartylib

rary!

Page 14: [Webinar] Building a Product Security Incident Response Team: Learnings from the Hivemind

INTERNAL POLICY

•  Define your Vulnerability Priori<za<on model •  CVSS or something else? •  What are your acceptable business risks?

•  What are your remedia<on SLAs? Escala<on paths?

•  When do you release a public advisory?

•  When is emergency response indicated?

Page 15: [Webinar] Building a Product Security Incident Response Team: Learnings from the Hivemind

INFRASTRUCTURE & TECHNOLOGY

Page 16: [Webinar] Building a Product Security Incident Response Team: Learnings from the Hivemind

PUBLIC DOCUMENTATION

•  Vulnerability Disclosure Policy •  Cri<cal for expecta<on se_ng •  Tells researchers how to report a vulnerability to you

•  Security Advisory Knowledge Base •  Where do customers go to quickly learn about security updates

•  Researcher Acknowledgements •  Recognize posi<ve behavior and build community

Page 17: [Webinar] Building a Product Security Incident Response Team: Learnings from the Hivemind

TOOLKIT

•  How do you want to receive external vulnerability reports? •  Unstructured: encrypted email •  Structured: secure web form

•  How do you want to capture inves<ga<on details?

•  Case management db (doesn’t have to be complicated, can be specific fields captured in Jira)

Page 18: [Webinar] Building a Product Security Incident Response Team: Learnings from the Hivemind

TOOLKIT

•  Do you use third party code?

•  Source code scanning tool to track what you use, where

•  Vulnerability Intelligence sources

•  HIGHLY RECOMMENDED: OSS SECURITY MATURITY: TIME TO PUT ON YOUR BIG BOY PANTS! Jake Kouns & Chris<ne Gadsby, Jasmine Ballroom, 2:30 pm

Page 19: [Webinar] Building a Product Security Incident Response Team: Learnings from the Hivemind

DATA MANAGEMENT FOR SIRTS

•  What Developers need to know to fix vulnerability

•  What Leadership needs to know about business risk

•  What Customers need to know about product security

•  DOCUMENT at <me of inves<ga<on even if you don’t use the data un<l much later

Page 20: [Webinar] Building a Product Security Incident Response Team: Learnings from the Hivemind

PITFALLS

Page 21: [Webinar] Building a Product Security Incident Response Team: Learnings from the Hivemind
Page 22: [Webinar] Building a Product Security Incident Response Team: Learnings from the Hivemind

PITFALLS

•  Failure to thoroughly document vulnerability details during inves<ga<on, leading to re-inves<ga<on just prior to fix release to remember what the issue was

•  Failure to priori<ze effec<vely •  Adopt a priori<za<on model that considers both technical and business impact •  Define your acceptable business risks

•  Failure to define clear stakeholders and roles in Incident Response Process

•  Failure to communicate effec<vely with product development

•  Failure to communicate effec<vely with external researchers

Page 23: [Webinar] Building a Product Security Incident Response Team: Learnings from the Hivemind

FREE RESOURCES

•  Disclosure policy basic template:

•  Inves<ga<ve data collec<on checklist

•  Advisory checklist

•  ISO 29147

hTps://pages.bugcrowd.com/best-prac(ces-for-security-incident-response-teams

Page 24: [Webinar] Building a Product Security Incident Response Team: Learnings from the Hivemind

QUESTIONS

Thanks for anending!

@[email protected]