Brought to you by
❖Next event: May 2018 (TBD)
❖Application UX and Front-End Design
SOFTWARE SECURITY 101
❖ sponsored by:
Srinivasan Vanamali,
Olympus Infotech
Bilal Soylu,
Xcobee
Kate Kliebert,
Kliebert Law
Ben Wilson,
deliverypath
Meet the panel of experts
From An Idea to The Killer App
❖Idea
❖Validate it with Business Partners,
potential clients, colleagues & friends
❖Define the Requirements
❖Develop the App
❖Ready to go!
Typical Application Architectural Components:
Typical Mistakes: Client Tier
❖Issues in separation of Public / Private areas of the application
❖Some of the application resources that meant to be private get
exposed to the public
❖Authorization - issues in user rights
❖The user roles get messed up - wrong type of users get access to
the resources that they should not to
❖Securing Credentials
❖User credentials are stored & passed as CLEAR TEXT
Typical Mistakes: Web Tier
❖Data gets transferred through the INTERNET -
unprotected area
❖The connection is not encrypted
➢HTTP instead of HTTPS is used
➢Old and vulnerable versions of SSL/TLS are used
❖Other Vulnerabilities
Typical Mistakes: Web Tier❖No breaches monitoring for the software
installed on the servers
❖Common Software Vulnerabilities get
overlooked
❖The Server Software is not updated
promptly after the vulnerabilities get
discovered
❖I.e. 9 pages of vulnerabilities for Apache on
the screenshot:
Typical Mistakes: App Tier
❖Source Code Management
❖Public repositories instead of private
❖Access rights to the source code are not
managed
❖Developers do not have clear
understanding on what project they are
working on
❖Vulnerability in the code
❖Not following the best practices
❖Not following “Security by design” pattern
❖Not storing API keys securely
❖Breaches in the third-party components
and libraries
Typical Mistakes: Data Tier
❖Non-securing sensitive data (PII - personal
identifiable information: Name, Address, Date of
Birth, SSN, etc)
❖Storing data when you do not need to (i.e.
credit card data - very often!)
❖Not following the Regulatory Compliance when
needed:
❖PCI (credit card data)
❖HIPAA (medical data)
❖GDPR (when operating in EU)
❖etc
❖Not following right coding standards when
communicating with database
❖SQL injections possibility
❖Physical Server Security
❖Other vulnerabilities
Typical Mistakes: Team Collaboration Tools
❖Use of public team collaboration tools by
unexperienced users
❖Not enough training for the employees
❖Accidentally sharing information that is not
supposed to (i.e. everyone with the link can
open the google doc or DropBox document)
❖The users who are not employees any
more still have access
❖etc
Typical Mistakes: Third-Party Software
❖Opting for free software without checking for security
breaches & examining the code thoroughly
❖Not validating the vendors of third-party software (i.e.
when choosing payment processing gateway - is credit
card data going to be safe with that vendor?)
Resources
❖Common Vulnerabilities and Exposures
➢https://cve.mitre.org/
➢https://nvd.nist.gov/
❖https://www.us-cert.gov/
❖https://www.xcoobee.com/breach-cost-calculator/
❖https://www.csoonline.com/article/2130877/data-breach/the-biggest-data-
breaches-of-the-21st-century.html

TechTalks | Software Security 101: What Every Startup Needs to Know to Protect Their Business

  • 1.
    Brought to youby ❖Next event: May 2018 (TBD) ❖Application UX and Front-End Design
  • 2.
    SOFTWARE SECURITY 101 ❖sponsored by: Srinivasan Vanamali, Olympus Infotech Bilal Soylu, Xcobee Kate Kliebert, Kliebert Law Ben Wilson, deliverypath Meet the panel of experts
  • 3.
    From An Ideato The Killer App ❖Idea ❖Validate it with Business Partners, potential clients, colleagues & friends ❖Define the Requirements ❖Develop the App ❖Ready to go!
  • 4.
  • 5.
    Typical Mistakes: ClientTier ❖Issues in separation of Public / Private areas of the application ❖Some of the application resources that meant to be private get exposed to the public ❖Authorization - issues in user rights ❖The user roles get messed up - wrong type of users get access to the resources that they should not to ❖Securing Credentials ❖User credentials are stored & passed as CLEAR TEXT
  • 6.
    Typical Mistakes: WebTier ❖Data gets transferred through the INTERNET - unprotected area ❖The connection is not encrypted ➢HTTP instead of HTTPS is used ➢Old and vulnerable versions of SSL/TLS are used ❖Other Vulnerabilities
  • 7.
    Typical Mistakes: WebTier❖No breaches monitoring for the software installed on the servers ❖Common Software Vulnerabilities get overlooked ❖The Server Software is not updated promptly after the vulnerabilities get discovered ❖I.e. 9 pages of vulnerabilities for Apache on the screenshot:
  • 8.
    Typical Mistakes: AppTier ❖Source Code Management ❖Public repositories instead of private ❖Access rights to the source code are not managed ❖Developers do not have clear understanding on what project they are working on ❖Vulnerability in the code ❖Not following the best practices ❖Not following “Security by design” pattern ❖Not storing API keys securely ❖Breaches in the third-party components and libraries
  • 9.
    Typical Mistakes: DataTier ❖Non-securing sensitive data (PII - personal identifiable information: Name, Address, Date of Birth, SSN, etc) ❖Storing data when you do not need to (i.e. credit card data - very often!) ❖Not following the Regulatory Compliance when needed: ❖PCI (credit card data) ❖HIPAA (medical data) ❖GDPR (when operating in EU) ❖etc ❖Not following right coding standards when communicating with database ❖SQL injections possibility ❖Physical Server Security ❖Other vulnerabilities
  • 10.
    Typical Mistakes: TeamCollaboration Tools ❖Use of public team collaboration tools by unexperienced users ❖Not enough training for the employees ❖Accidentally sharing information that is not supposed to (i.e. everyone with the link can open the google doc or DropBox document) ❖The users who are not employees any more still have access ❖etc
  • 11.
    Typical Mistakes: Third-PartySoftware ❖Opting for free software without checking for security breaches & examining the code thoroughly ❖Not validating the vendors of third-party software (i.e. when choosing payment processing gateway - is credit card data going to be safe with that vendor?)
  • 12.
    Resources ❖Common Vulnerabilities andExposures ➢https://cve.mitre.org/ ➢https://nvd.nist.gov/ ❖https://www.us-cert.gov/ ❖https://www.xcoobee.com/breach-cost-calculator/ ❖https://www.csoonline.com/article/2130877/data-breach/the-biggest-data- breaches-of-the-21st-century.html